Restore Options | |
Detailed Log | Records all files that are restored. |
Skip Pre/Post | Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. |
Pre/Post | Opens the Pre & Post Execution screen (see "Pre & Post Execution screen"). |
Leave Database(s) in ‘RESTORING’ state • (Microsoft SQL Server backup sets only. Not valid for ‘dump file only’ restores.) • Off: (DEFAULT) The database will be brought online after the restore. • On: DS-Client will not bring the database online after the restore has finished. Instead, it will leave the database in ‘RESTORING’ mode to allow users to continue performing restore operations on the restored database. | |
Do not drop existing DB before restore • (MySQL backup sets only.) • 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. | |
Restore Private Authorities. • (System i backup sets only.) • Restores Private Authorities for objects (if they were backed up). • This works for System i objects with the Private Authority (PVTAUT) parameter (This parameter was introduced since IBM i 6.1). When PVTAUT is set to *YES, you will be able to restore the private authorities attached to your saved objects. | |
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. | |
Salesforce.com Restore options For more information about Salesforce.com restores, see the Knowledge Base article in “Backup from the Cloud (Salesforce.com)”. • Restore Schema: Same as above for Table Restores. • Use Bulk API: This option minimizes the number of API call counts made by the restore process and is selected by default. When files are uploaded via Bulk API, a file size limit of 10 MB is enforced by Salesforce.com. NOTE: Ensure that this check box is cleared if the data to be restored contains files that are larger than 10 MB. • Restore with automatic relationship fix: If you restore multiple tables at the same time, with this option selected, DS-Client will try to trace the ID change and fill the foreign key with the new ID that was inserted, thereby maintaining the relationship between those tables. If this option is not selected, after the data has been restored into those tables, the relationship between the tables will be broken because all new inserted rows will have a new ID. • Include all referenced tables automatically: Includes all the backed up tables that are related to the table being restored. • Additional relationship fix based on name comparison: If this option is selected, DS-Client will try to find any missing referenced records based on a comparison of “Name” columns. • Detect duplicate records by name comparison: Prevents data that already exists from being restored and duplicated. For more information, see "Preventing duplicate records in a table-level restore". • Save temporary database file in local storage for resume: Select this option if you want to the Salesfores.com data restore process to be resumable in the event that it is stopped during the uploading stage. See “Resuming a Salesforce.com data restore process” for more information. • Delete all records before restoring: Empty the selected tables from the online Salesforce.com database, before performing the restore to re-populate those tables. | |
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) | |
Force pipe library path (Oracle) | If you are using DS-PIPE, this field appears. • RMAN requires the Media Management Library “libobk.so” to backup / restore using a PIPE. • The exact library name will be slightly different, depending on the platform. For more information, refer to the “Oracle Server Requirements” section of the Knowledge Base article in “Backup / Restore of Oracle Database Servers”. • You can specify the exact path (including filename) to the corresponding “libobk.so” for the Oracle server’s platform. These library files can be found in the DS-Client installation directory. • If you do not specify a path, the default path will be used: “$ORACLE_HOME/lib/libobk.so” • Make sure Oracle has full rights to read and execute in the library path. • Note: DS-Client does not validate this path. It simply forwards it to RMAN. |
Do not execute ‘RECOVER’ commands (Oracle) | This option will not issue the RECOVER command. This means the DS-Client will only restore the control file, archive logs and tablespaces back to the Oracle server. You must use RMAN to perform the DBPITR manually. Refer to the Knowledge Base articles: |
‘RECOVER DATABASE’ at: (Oracle) | This option will automatically recover database to the target time specified and open the database with the ‘Resetlogs’ option. Refer to the Knowledge Base articles: |
PITR of pluggable database(s) (Oracle 12 only) | This checkbox appears if the restore selection qualifies for PDB PITR. If selected, you must also select ‘RECOVER DATABASE’ at. • For more information, refer to the Knowledge Base article in “Oracle 12c Database Point-In-Time Recovery (PITR)”. |