Restore Job Destination Options

The Set Job Destination Options dialog allows you to set options related to restore destinations. The options displayed depend on the restore mode. An explanation of each field in the dialog and the available choices is provided in this section.

To open the dialog, go to the Restore tab in the desktop interface and select a restore mode. Then do one of the following:

• From the task panel, click Set Destination Options.
• From the menu bar, select Restore > Set Destination Options.
• Right-click the Enterprise name or icon in the destination pane and select Set Destination Options from the context menu.

Note.

Block Restore uses a separate Restore Destination Options dialog, opened from the Block Restore window, which also includes application-specific options for Oracle and Microsoft SharePoint Server restores.

General Options

Existing File Handling

Tells DPX how to behave if it finds a file at the destination with the same name as the file that it is restoring.

Skip Existing Files and Directories	Does not write over the existing file or directory if it has the same name as the one being restored.
Replace Existing Files	Restores the file to a temporary file, ensures that the restore is successful, and then writes over the existing file with the like-named file being restored.
Replace Existing Files and Directories	For existing directories, restores directory characteristics only, such as date, time, and owner. For existing files, restores file to a temporary file, ensures that the restore is successful, then writes over the existing file with the like-named file being restored.
Delete Existing Files Before Restore	Deletes the existing file before restoring the like-named file. Use this option when disk space limitations prohibit using Replace Files.
Rename Restored Files	Renames the file being restored to a name derived from the existing file. On NTFS and UNIX, DPX appends .R01 to the filename. If filename.R01 exists, DPX uses .R02 and so on. On FAT, a file extension .R01 is used. For example, the file ABCD.TXT is restored as ABCD.R01. If ABCD.R01 exists, ABCD.R02 is used, and so on.

Note.

For Image Restore and NDMP Restore jobs, only the Replace Existing Files and Delete Existing Files Before Restore options are available.

Missing Directories

Controls how DPX behaves if it tries to restore a file to a directory and discovers that the directory does not exist.

Use Full Privileges	Uses the file privileges the file possessed when it was originally backed up.
Use Parent Privileges	Applies the file privileges of the parent directory into which the files are being restored.
Use Root Privileges	Applies the file privileges of the root directory into which the files are being restored.

Destination Path

This field applies only when you are restoring data to a new location. It allows you to choose whether to preserve the original directory structure or to restore all files to a single specified directory.

Absolute Path	Maintains the original directory structure upon restoration. For instance, if you backed up from C:\NewPrjs\Dev\Bin and restore to C:\NewPrjs\Test, the restored path will be C:\NewPrjs\Test\NewPrjs\Dev\Bin.
Relative Path	Strips the parent directories, placing the files directly into the new restoration directory. For example, backing up from C:\NewPrjs\Dev\Bin and restoring to C:\NewPrjs\Test results in the files being restored to C:\NewPrjs\Test\Bin.

Skip Incomplete Files

Specifies the action to take with files that were not fully restored.

No	Keep the partially restored file.
Yes	Delete the partially restored file.

Restore Security

Determines whether DPX restores security information associated with each file or folder.

Yes	Restores all security information associated with the files and directories, including NTFS security properties, UNIX/Linux ACLs, and trustee settings in NetWare or OES environments. This is the default setting.
No	Does not overwrite security information in the restoration destination directories.

Retry Failed File

Determines how to handle files that fail when you attempt to restore them. This applies only to Windows.

No	Does not retry restoring files that failed during the initial attempt. This is the default setting.
Retry Open File	Attempts to restore files that were open and failed in the initial restore attempt. A system reboot is required after the restore to access the files.
Retry All Failure	Retries the restoration of all files that failed during the initial attempt, including open files. A system reboot is necessary post-restore to access the files.

Windows-Specific Options

Mount Point Handling

This setting governs the restoration of data from backups made through Windows volume mount points, detailing both the restoration location and the reassignment of mount points.

To ensure a mount point's content is backed up, activate the Back Up Content of Mounted Drive option in the Set Job Source Options. For instance, if C:\mnt\driveD is a mount point for D:, you would select C:\mnt\driveD for the backup instead of D:.

Restore Data (no Mount Point)	Restores data to the current directory structure, regardless of previous mount points. If a directory was a mount point at backup and remains so at restoration, data is restored to the current volume it mounts.
Restore Data and Mount Point; Skip Existing Mount Point	Reestablishes the mount point and restores data to the mounted volume unless the directory now mounts a different volume, in which case the mount point is not reestablished.
Restore Data and Mount Point; Replace Existing Mount Point	Always reestablishes the original mount point and restores data to the mounted volume, even if the directory mounts a different volume at restoration. This setting is the default during reconstructive restores.

Note.

If a directory was a mount point during backup but is now a standard directory with local files at the time of restoration, the mount point will not be recreated. Instead, the data will be restored to the directory that previously functioned as a mount point.

Note.

Be aware that for Reconstructive Restores, DPX will default to the Restore Data and Mount Point; Replace Existing Mount Point option, regardless of the initially selected setting.

Example: the effect of Mount Point Handling under various circumstances

In this example, C:\mnt\driveD is a volume mount point to D: during backup. Data is backed up by selecting C:\mnt\driveD while the Back Up Content of Mounted Drive field is set to Yes in the Set Job Source Options dialog.

Situation at restore	Restore Data (no Mount Point)	Restore Data and Mount Point; Skip Existing Mount Point	Restore Data and Mount Point; Replace Existing Mount Point
C:\mnt\driveD is still a volume mount point to the same volume D:	Data is restored to D:.	Same as the first option.	Same as the first option.
C:\mnt\driveD is an empty directory that is not a volume mount point to anywhere	Data is not restored to D:. Data is restored to C:\mnt\driveD, which no longer is a volume mount point to D:, but now contains the data that was on D:.	Data is restored to D:. C:\mnt\driveD is reestablished as a volume mount point to D:.	Same as the second option.
C:\mnt\driveD is not a volume mount point to anywhere, but is a normal directory containing local files	Data is not restored to D:. Data is restored to C:\mnt\driveD, which no longer is a volume mount point to D:, but now contains the data that was on D:.	Same as the first option.	Same as the first option.
C:\mnt\driveD does not exist	Data is not restored to D:. C:\mnt\driveD is created and data is restored directly to it.	Data is restored to D:. C:\mnt\driveD is created and established as a volume mount point to D:.	Same as the second option.
C:\mnt\driveD is a volume mount point to E:, a different volume	Data is restored to E:, the new volume mount point. C:\mnt\driveD remains a volume mount point to E:.	Same as the first option.	Data is restored to the original volume D:. C:\mnt\driveD is reestablished as a volume mount point to D:.

DPX keeps track of both volumes and drive letters, so if drive letters change, data is still restored to the correct volume.

Restore Disk Quota

Using disk quotas, administrators can limit the amount of data each user can store on a Windows NTFS or NSS volume. This field determines whether to restore disk quotas.

No	Disk quota settings are not restored.
Yes	Disk quota settings are restored.

Note.

Backing up an entire volume is not a prerequisite for preserving disk quota settings. Any backup operation from a supported volume will automatically include this information. Similarly, when restoring, it is not mandatory to restore the entire volume to recover disk quota settings.

If you are restoring to a new location, disk quota settings will only be reinstated if the new location is the root directory of a similar volume, and the Destination Path is configured to Absolute Path.

SYSVOL Handling

If the Enterprise has more than one domain controller, you can choose whether to replicate SYSVOL files and folders to the other controllers as part of the Windows System State restore.

Authoritative Restore	Restores SYSVOL files and folders in a primary manner and forces that data to be replicated to the other primary domain controllers.
Non-Authoritative Restore	Restores SYSVOL files and folders locally and allows that data to get updated via the normal replication process. This is the default setting.

Attention!

When there are replication partners, selecting Authoritative Restore can result in unexpected behavior.

To execute an authoritative restore of the Active Directory, it is necessary to run the Microsoft Ntdsutil utility. This step should be performed after the System State data has been restored but before rebooting the domain controller. For detailed guidance on using the Ntdsutil utility and performing an authoritative restore, please consult the Microsoft documentation.

Cluster Handling

If your Enterprise contains clusters, you can choose whether to restore the cluster quorums as part of the Windows System State restore.

Do Not Restore Cluster Quorum	DPX does not restore the cluster quorum. This is the default setting.
Restore Cluster Quorum	DPX restores the cluster quorum. However, if other cluster nodes are active or if the cluster quorum has changed since backup, the cluster quorum restore may terminate.
Restore Cluster Quorum (Force the Recovery)	DPX restores the cluster quorum even if other cluster nodes are active or if the cluster quorum has changed since backup. Any changes made to the cluster quorum after the backup will be lost.

Microsoft Exchange Server Options

The following options apply when restoring Microsoft Exchange Server data.

Restart Exchange Service

Controls whether the Exchange Service is restarted when the restore is complete.

Yes	Restart the Exchange Service after the restore.
No	The Exchange Service is not interrupted by DPX.

Exchange Point-in-Time Recovery

Controls whether the restore will delete Exchange logs to restore Exchange to a point-in-time.

Yes	DPX will delete existing transaction logs before restore and then perform a point-in-time restore, which brings the database back to the state when it was backed up. This option is commonly used when you are restoring a backup instance that is not the latest. This option is strongly recommended whenever a restore is needed to nullify an incorrect or maliciously altered transaction.
No	This is the default. DPX will not delete existing transaction logs before restore. DPX performs an up-to-the-minute restore by retaining the existing transaction logs and rolling forward all new transactions from the existing logs. This option is commonly used when you lose a database without losing its transaction logs and you choose to restore from the latest backup instance.

Exchange Handling

Determines how Exchange databases are handled after restore completes.

Commit Restore and Mount Database	This is the default. After the restore completes, commit the changes (transaction logs) to the database and mount the Exchange database. The Exchange administrator does not have to manually intervene before the database is available for clients.
Commit Restore Only	After the restore completes, commit the changes (transaction logs) to the database but do not mount the Exchange database. The Exchange administrator will need to manually mount the database to make it available to clients.
Do Not Commit Restore	After the restore completes, neither commit the changes to the database nor mount the Exchange database. The Exchange administrator will need to either commit or roll back the changes (transaction logs) and mount the database for use.

Microsoft SQL Server Options

The following options apply when restoring Microsoft SQL Server data.

Note.

DPX does not support restoring the master and model databases to a new location because it is not supported by SQL Server.

MSSQL With Replace

When restoring a SQL Server database that exists, SQL Server performs tests to ensure that it is the appropriate place to restore the data. These tests are not always accurate and sometimes cause a restore to fail.

No	Performs tests before overwriting an existing database.
Yes	Overwrites an existing database without tests.

MSSQL New Location

This option allows you to restore the database to a different location than the original. It is essential when the original location is not available or when you want to restore the database for testing purposes. Enter the name of a new location where you want to restore a SQL Server database.

MSSQL New Location Logs

Enter a directory path to restore the transaction logs to a different location than that specified in the MSSQL New Location field. If you do not specify a directory, the transaction logs will be restored to the same location as the database.

MSSQL Standby

Prepares the Microsoft SQL Server database to be restored in a standby/read-only mode. This is particularly useful for situations where the database needs to be online during the restore process but should not be modified.

No	Does not restore the SQL Server database to a standby server. This is the default setting.
Yes	Restores a SQL Server database to a standby server.

MSSQL Standby Undo Directory

SQL Server creates an undo directory when a database is restored to a standby server. If you do not specify a directory, undo files will be created in the product-directory/logs directory.

Point-in-Time Restore

Fill in the Point-in-Time Restore field if you are recovering to a point-in-time other than the present. Enter the date and time (to the second) of the desired point-in-time recovery in the following format:

mm/dd/yyyy hh:mm:ss

The hour is based on a 24-hour clock. For example, for 11:00 p.m. on March 1, 2013, enter:

03/01/2013 23:00:00

Note.

If you are recovering to the present time, be sure the Point-in-Time Restore field is empty.

Additional NDMP and Image Restore Destination Options

The following options are available for NDMP Restore and Image Restore jobs.

Recover Mode

Determines the type of recover operation to perform. Depending on the restore mode, this field is displayed as NDMP Recover Mode or Image Recover Mode.

Extract	Only the selected files and/or directories are restored.
Direct	Direct Access Recovery (DAR) is performed. Select this option only if the NDMP server supports DAR.
True Image	Rebuilds an entire file system or subtree if base and incremental backups are restored in order. This option is available for NDMP Restore only.

Enable NDMP Server Logging

Controls the routing of NDMP server generated log messages to the job log file.

Yes	All NDMP server log messages will be routed to the master server's job log file. This is the default setting.
No	The NDMP server log messages will be logged locally in the NDMP client node log file instead of in the master server's job log file.

Additional NDMP Environment

This option allows you to introduce any additional NDMP environment variables that are necessary for the restore task. Specify your environment variables as an ASCII string with environment variable name and value pairs using the following syntax:

env1name=value,env2name=value,...

Note that syntax validation is not performed on the specified value at job definition time, but rather at run time. Only valid entries are added to the NDMP operation environment.

Do not specify any of the following NDMP environment variables in your variable string because DPX controls these specifically:

• BASE_DATE
• DEBUG
• DIRECT
• DUMP_DATE
• EXTRACT
• FILES
• FILESYSTEM
• HIST
• LEVEL
• PREFIX
• RECOVER_FILEHIST
• SINCE_TIME
• TYPE
• UPDATE
• VERBOSE

Specifying the variables above may cause unexpected results due to unpredictability of the order in which they are evaluated.

NDMP servers from different vendors may support different NDMP environment variables. Except for a few well-known environment variable names, there is currently no standardized set of such variables. This option allows you to add environment variables specific to your NDMP server.