Permissions (File system backup sets) | |
Yes | Restores permissions of the backed up files. |
Skip | Skips restoring file security information (if any) for the selected files and directories. Newly created files and directories will assume the security of the parent directory. Notes: If you have been assigned ownership of another person's backup set(s) and you want to restore files from those sets with ACL, the following will occur: 1 – DS-User will check whether you have access rights to Take Ownership and Change Permissions of the restore file. 2 – If you do not have access rights, you will not be able to restore the ACL. You must choose Skip Permissions Restore to restore the file. 3 – If you have the access rights, but the file ownership is not yours, the file will be restored without ownership, and a corresponding error message will appear in the event log, describing the security error. |
Only | Will restore permissions for the selected files and directories only. This will only apply permissions to existing files on the destination volume. |
Method | |
Save | Restores files to a temporary location first. If the file is restored successfully, then the original file is overwritten with the temporary file. This prevents partially restored files from overwriting an existing file. • For Linux DS-Client restores of Hard Links, this is the default restore method. The restore will only link those hard linked files that are selected in the same restore session. For more information, see the “Hard Links” sections in the Knowledge Base article in “Backup / Restore of UNIX File Systems”. |
Use buffer | Restores files to the DS-Client buffer first. Then, the files are transferred to the restore destination. This ensures that the files are restored as fast as possible, given the speed of your LAN. Notes: The DS-Client Buffer will inherit the permissions of its parent directory. For example, if you specify C:\TEMP as the buffer, then the C:\TEMP\buf directory will inherit the permissions of the \TEMP directory. All files copied to the \buf directory will be accessible by users with permissions to \TEMP. You must have sufficient disk space in the DS-Client buffer to accommodate the entire restore amount. |
Fast | Files are restored on a 'write-data-as-received' basis. Files are overwritten upon receipt of the first byte of data. • For Linux DS-Client restores of Hard Links, choosing this method allows you to restore a single hard linked file while preserving the existing hard links on the restore target. For more information, see the “Hard Links” sections in the Knowledge Base article in “Backup / Restore of UNIX File Systems”. |
Locked Files (Windows) | |
Rename | A locked file will be renamed while still in use (intended for System files). The renamed file will be registered with the operating system for delete, on reboot. (This feature is necessary when restoring system files that are opened before the operating system has the chance to replace the locked file.) |
Don't rename | A locked file will be restored as a temporary file. This temporary file will be registered with the operating system to replace the locked file on reboot. • For important information on this option refer to the DS-Client Knowledge Base article in “Restoring Locked Files on Windows”. |
Skip | Skips restores of any files that are locked. An error will be reported in the Activity Log. |
Skip offline files (stubs) (Windows) | Skips restores of any backed up “stub” files. • Skips restore if the online file is a stub (a small placeholder/link file to the full file which was moved to other media). |
Do not drop existing DB before restore (Linux DS-Client) | • OFF (Drop database) - If a database selected for restore already exists on the restore server, DS-Client will drop the existing database before performing the restore. • ON (Do not drop database) - If a database selected for restore already exists on the restore server, DS-Client will restore to that existing database. This option is useful if you want to keep any extra tables (and replace all existing tables) in the existing database. |
Overwrite junction point | Replaces any junction points of the same name. Junction points are special directories (like shortcuts) that link to another location. |
Load Cluster Quorum (Windows 2000 & up) | (This check box only appears if you are restoring a System State with a Cluster Quorum.) Automatically loads the Cluster Quorum after restore. |
Detailed Log | Records all files that are restored. |
Skip Pre/Post | Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. |
Restore Reason | Depending on the backup set type, this field may appear on this page or on a subsequent Restore Wizard page. • You must supply a reason for this restore request by selecting one from the drop-down list. |
Restore Schemas (Salesforce.com databases) | This check box appears if you are restoring a ‘Backup from the Cloud’ (Salesforce.com) backup set’s database. Restore Schema is performed at Table-Level only (not at database level). This option is useful if you have made changes to a table’s structure since the backup session you are restoring. • If selected, the restore will wipe the entire table(s) selected for restore from the Salesforce.com database, then rebuild the table(s) with the backed up schema(s), then populate the table with the restore data. |
Authoritative Restore (System State) | This option forces authoritative restore for Active Directory. • For more information, refer to the DS-Client Knowledge Base article in “Bare Metal Restore of Windows (ALL VERSIONS)”. |
Compression Options | This list only appears if the backup source and restore destination support file level compression (ex: NTFS, NetWare). • Default Compression: Specifies that the restored files take on the compression attribute of the parent directory where they are restored. • Preserve Compression: Specifies that the restored files retain their original compression setting (as when they were originally backed up). • Force Compress: Specifies that the restored files are compressed using the destination file system's compression. • Force Expand: Specifies that all restored files are to be expanded (no compression). |
Encryption Options (Windows File System only) | If this list appears, you can instruct DS-Client how to handle backed up files encrypted with Windows File Encryption. • Include Encrypted Files: (Default) Specifies that the restore process will attempt to restore any files encrypted with Windows File Encryption. • Skip Encrypted Files: Specifies that the restore process will skip any files encrypted with Windows File Encryption. This option may be useful if the target restore destination does not support this feature. • Restore Encrypted Files only: Restores only those files that are encrypted with Windows File Encryption. |
Force Compress (Check Box) | (This check box only appears if the original volume does not support file level compression, but the restore destination does.) Compresses the restore files using the destination file system's compression. |
Restore NDS Object(s) from (NetWare NDS Restore) | Specify the object (container or leaf) that you want to restore. The object name should be typeless and fully qualified from the Root (distinguished). (The default is to restore the whole NDS). |
Restore Permissions from (Permissions only restore) | Leave this field empty to restore all permissions backed up. Restores file and directory permissions for the specified path only. (e.g. \dir_path\(file_name) - where file_name is optional). You must know the specific path name to use this option. |
Skip Subdirectories (Permissions only restore) | Skips restore of subdirectory permissions from the directory listed in the Restore Permissions from field. |
Keep Replica ID (IBM Domino Server only) | This option is only applicable when restoring a Lotus Domino Server database in a clustered environment. • Additional steps are required. Please refer to the Knowledge Base article in “Backup / Restore of IBM Domino Server Databases”. |
Local Storage Restore Options This section only appears if this backup set has data stored in Local Storage and off-site on DS-System. DS-Client always tries to restore from Local Storage first, but these options deal with the specific scenario where the DS-Client also needs to restore some data from DS-System. • (Default) Stop, if connection to DS-System not available when needed. • Continue, even if connection to DS-System not available. • Try to connect to DS-System first. If connection fails, stop. | |
Additional Restore Options (Linux - Permissions only backup sets) | |
Restore files that match | Allows you to specify a filename pattern whose permissions will be restored. |
Exclude files that match | Allows you to specify a filename pattern to exclude from the permissions restore. |
Additional Restore Options (Linux DS-Client - VMware VADP backup sets) • The available restore options depend on the selected destination VMware server. • For each virtual machine selected for restore, you can specify additional restore options to be performed. | |
Power on VM after restore | Starts each virtual machine that is successfully restored. Currently, this option is available only when you are configuring a Full virtual machine restore. |
Unregister VM after restore | After successful restore, the virtual machine will be unregistered from the vCenter Server. |
Add timestamp to VM name | Appends the restore time to the end of the virtual machine’s name. For example, a virtual machine named “RestoreVM” will be restored as “RestoreVM_[yyyy-mm-dd-hh:mm:ss]” in the vCenter Server. Currently, this option is available only when you are configuring a Full virtual machine restore. |
Use SAN with all disk types | If this option is selected and the configuration supports this option, DS-Client will try to restore the virtual machine using SAN Transport mode. • For more information, see the Knowledge Base article in “VMware Transport Libraries”. |