Advanced Job Options
Last updated
Last updated
By default, DPX will restore the files or volumes specified in the File Browsing step to their original location. You may override this setting by indicating a directory on the same or another node.
Specify the Node Name. This may be the same node the data were backed up from, or another machine.
Restrictions. Agent-Based File Restore only handles alternate destinations with similar operating systems. E.g. restoring Linux files on a Windows node or vice versa is not supported.
In all previous steps of creating a restore job, the available selections were based on the backup metadata stored on DPX. This means that DPX is aware of all backups made by the user and where they are stored. If, during backup or at a later stage, the backup data have been replicated to a secondary location and the primary location becomes corrupt or inaccessible, you can choose to restore your data from such secondary location using this option.
Select the Secondary Node from the drop-down list.
Select the volume where the alternate backup is stored.
DPX will attempt to identify the files or directories specified in previous steps. If this proves impossible, the following warning will be displayed:
See also. For more information, see Creating vStor Partnerships in vStor documentation.
Schedule the restore job. The time field is using your browser’s time zone. For example, if you have DPX in London and access the DPX web interface from New York, specify the time in US Eastern Time.
Important. When specifying a schedule, make sure the Delete the restore job on successful completion toggle is switched off. Otherwise, the job will be deleted upon its first successful completion.
Also please note that in the current version of DPX, restore jobs cannot be edited. This also includes job scheduling.
As with backup jobs, you can add script options for this restore job.
Enter the name of a script to execute prior to the actual job.
Basic usage: <script>@<node_name> <argument_list>
The action be taken if the Pre-Job Script fails to complete:
Run Job/Run Post-Job Script
Skip Job/Run Post-Job Script
Skip Job/Skip Post-Job Script
The action to be taken if the Job fails to complete:
Run Post-Job Script
Skip Post-Job Script
Enter the name of a script to execute after the actual job.
Basic usage: <script>@<node_name> <argument_list>
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see Pre-Scripts and Post-Scripts.
Controls the routing of NDMP server-generated log messages to the job log file.
Toggle on | All NDMP server log messages will be routed to the master server’s job log file. Yes is the default. |
Toggle off | 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. |
This option only takes effect when you restore an entire SnapVault filer-to-filer backup instance to its original location.
Toggle on | Immediately after restore, DPX resynchronizes the restored backup instance as the most recent backup. |
Toggle off | Do not resynchronize the restore. |
This option comes into play if a job does not get an indication of “active” status during the data transfer phase of the job. Catalogic DPX initiates job cancellation after this interval, specified in minutes, has lapsed.
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 |
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. |
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 2000+ 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. Non-Authoritative Restore is the default. |
Attention! When there are replication partners, selecting Authoritative Restore can result in unexpected behavior. For more information, see Creating vStor Partnerships in vStor documentation.
To perform an authoritative restore on the Active Directory, you must run the Microsoft Ntdsutil utility after you have restored the System State data but before you restart the domain controller. For more information about the Ntdsutil utility and authoritative restore, refer to your Microsoft documentation.
If your Enterprise contains clusters, you can choose whether to restore the cluster quorums as part of the Windows 2000+ System State restore.
Do Not Restore Cluster Quorum | DPX does not restore the cluster quorum. Do Not Restore Cluster Quorum is the default. |
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. |
Specify the absolute path within the node. If the specified path does not exist, DPX will create it. Alternatively, use the icon to open the tree view and select the target folder from the machine’s folder structure. Note that the tree view does not allow the creation of new folders.
