Restore To | |
Original Location: | [Default] Restores files to the original location from which they were backed up. |
Alternate Location: | Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server. |
Dump to (Microsoft SQL) | This field shows the location for the database dump. Click >> to change the specified path. • This brings up the "Select share & path for the database / data dump screen". |
Database Mapping List | Shows a list of the selected items for restore, and their restore destination(s). You can change the restore destination by modifying the appropriate column. • Icon - Shows an icon to indicate the type of restore item. • Source - Shows the source item's name. • Destination - Shows the database where the backup will be restored. Double Click on this cell to open a drop down list of all the available databases on the specified restore database server. |
Restore Options | |
Restore only the dump file(s) (Windows DS-Client) | This option will only restore the dump file to the specified location. The dump will not be loaded to the database. (This option is not available if DS-Client Buffer or DS-Client Pipe is specified in the Dump To field.) |
Restore as Pure Files (Linux DS-Client) | This option is available if "Alternate Location" is selected. It will restore only the data. This option will only restore the dump file to the specified location. The dump will not be loaded to the database. |
Restore Path | When restoring to an alternate location, you can specify the path for the log and data files separately. Opens the "Select Restore Path screen". |
Preserve original database file location | This option only applies to restores to the original location. • Off (default) - The restored files will be placed on the target instance's default path(s). • On - The restore files must be placed in their original path(s). If the original path(s) do not exist, the restore will fail. |
Ask for Network Credentials | Prompts you to enter a valid user name and password for the selected computer. • This option is available for BLM and Disc/Tape restores, since the original backup set may no longer be on the DS-Client. If you do not select this option, DS-Client uses its own (service) credentials to access the network location. |
Ask for Database Credentials (Databases only) | Prompts you to enter a valid user name and password for the database server. • This option is available for BLM and Disc/Tape restores, since the original backup set may no longer be on the DS-Client. • For Microsoft SQL: If you do not select this option, DS-Client uses its own (service) credentials to access the database server. • For MySQL and PostgreSQL: You must select this option and provide credentials to access the database server. |
Restore to a local database file (Salesforce.com - Table Restore) | This option will restore the dump file to the specified location. • The file will be in *.fdb format, visible using Flame Robin. • Click [>>] to open the “"Select Directory"” screen and specify the destination. |
Restore to multiple data files (CSV) (Salesforce.com - Table Restore) | This option will restore the database to the specified location in CSV format. Each table will be a standalone CSV file in the destination folder. • The primary use for this option is the restore of backed up Salesforce.com System Table. Because these System Tables are not restorable to the Salesforce.com online database, this feature provides an alternate method to obtain this data. • Click [>>] to open the “"Select Directory"” screen and specify the destination. |
Please select the path to put the database (Salesforce.com - Item-Level Restore) | In the first step of a Granular (Item-Level) Restore, you must select the location where you restore the Salesforce.com database file. For performance, it is preferable that this is a location on the DS-Client. • Click [>>] to open the “"Select Directory"” screen and specify the destination. |
Notes | |
1 | If restoring to an alternate location, the database and table must exist on the database server where you are restoring. |
2 | Table restores will not restore indexes. |