Microsoft SQL Server Restore

This restore mode allows the restoration of Microsoft SQL Server databases from backups created with DPX. The restore process is designed to be flexible, allowing for the recovery of selected databases to their original location or a new one. With DPX, you can also perform point-in-time restores, leveraging SQL Server's transaction logs to recover databases to a specific moment before an incident occurred.

Creating a SQL Server Restore Job

  1. In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.

  1. Select Application Restore and Click Next.

  1. The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Find the Node that contains the SQL Server you want to restore and click Next.

Tip. Restoring a SQL object will include all local volumes referenced by the SQL object, potentially increasing the restore size.

  1. Choose the appropriate recovery point from the available backups of the selected node.

  1. In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.

  1. In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.

  2. Specify job options. You can use the following options:

Basic Job Options

Delete the restore job on successful completion

Job e-mail notification

E-mail Notification Fields

Subject

The subject of your message. The subject line usually contains a combination of straight text and variable elements. Variables, which must begin with %, are replaced with actual corresponding values. If you enclose variables in double quotation marks, those variables are treated as literal values. You can embed the following variables:

  • %JOBNAME

  • %JOBID

  • %JOBTYPE

  • %RC

Use %RC to include the return code in the message for this run of the job, when applicable.

To

The email address of the primary recipient of your message. Only one “To” address is permitted.

Cc

Carbon Copy. The email address(es) of the secondary recipient(s) of your message. Use a semicolon to delimit multiple email addresses.

Bcc

Blind Carbon Copy. The email address(es) of the secondary recipient(s) not identified to other recipients. Use a semi-colon to delimit multiple email addresses.

Note. Note that the following characters are invalid in all fields: < > ; and '.

Note. DPX emailing must be enabled when you first configure your Enterprise. At that time, you supply general system information, including SMTP Host Name and SMTP Port. See the Administrator E-mail Settings section.

MSSQL Options

MSSQL with Replace

When this option is enabled, DPX will overwrite an existing database without performing the usual SQL Server pre-restore tests. This can be useful when you are certain that the restore should proceed, but it bypasses SQL Server's built-in safety checks, so use it with caution1.

MSSQL New Location

This option allows you to restore the database to a different location than the original. It's essential when the original location is not available or when you want to restore the database for testing purposes.

MSSQL New Location Logs

If you're restoring the database to a new location and want to specify a different location for the transaction logs, use this option. This is particularly useful for separating data files from log files1.

MSSQL Point in Time Restore

This option enables you to restore the database to a specific point in time, using the transaction logs. Ensure that the necessary transaction log backups are available for the point in time you wish to restore to.

See also. To learn more about other available options, see Advanced Job Options.

  1. Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.

  1. Click Yes to run the job immediately or No if you want to run it later from the Job Manager.

Last updated