The Restore 4.4
SEP sesam provides three restore types: complete restore (all files of a saveset), selective restore (selected files) and generation restore. Restore is triggered from the menu bar -> Activities -> Restore. Restore wizard guides you through the process of restoring your data. For step-by-step procedure, see Standard Restore Procedure.
Restore tasks can be saved, scheduled and run automatically in continuous intervals to check and control the data integrity. For details, see SEPuler.
As of SEP sesam 4.4.3. Tigon V.2, it is possible to restore savesets online with the Self-Service Restore Assistant, if you are granted appropriate permissions. For details, see Self-Service Restore Assistant.
The following restore types are available:
- Complete restore
- A process by which an entire saveset is restored - all the files of a saveset are selected and restored.
- Selective restore
- Only a subset of a saveset's files is selected - only selected parts of data on the saveset, such as individual files and directories, are restored.
- Generation restore
- All generations of backed-up files, including differential or incremental backup files, can be browsed for and selected for restore. SEP sesam automatically switches to the generation view in which all the generations of the files are presented. The selection list displays all files since the last full backup.
Scheduled restores are performed by creating an event or task. It is also possible to schedule a restore for data that has not yet been backed up. The selective restore can be set to run at the completion of the daily backup routine, e.g., the last backed up file can be restored, preferably to a new directory and the data validity established.
Restore wizard is triggered from the menu bar -> Activities -> Restore. The following restore options are available in the restore wizard to define how your data will be restored.
Step 1: Welcome page By default, the welcome page is not displayed when starting the wizard. It provides only general information on specifying restore process.
Step 2: Filter You can select how you want to search for your backed up data. Savesets can be searched by task name in the saveset, or by filename or path.
All task for which backups are available can be selected from the Task drop-down list, or a regular expression can be entered into the Search pattern field to search for files by their name or path. In the latter case, if all tasks should be searched, use the All button. Note that searching might take some time (depending on the amount of processed tasks). Saved in period allows searching for savesets only within the specified time frame. Show external results extends the search to the savesets generated with supplementary backup tools and interfaces, such as BSR Pro, MySQL, DB2, etc.
Step 3: Select task The results of the search are displayed in the table.
You can enable any of the following options:
- Complete restore of selected task will restore everything in the task.
- Hide migrated means that the savesets that have been moved with a migration task will not appear in the results.
- Broken tasks will also display the savesets with the status cancelled.
- Generation restore must be enabled if you are restoring from an incremental or differential backup.
- Disaster restore should be enabled if you are restoring a server from a disaster scenario.
For details on disaster recovery, see SEP sesam Server Disaster Recovery. If a client server is being recovered, simply select the server’s disaster recovery backup task.
Option Mount saveset – Cross-Platform Recovery File System Layer (XPRFS)
As of SEP sesam v. 4.4.2, a checkbox Mount saveset under the Single File Restore becomes available after selecting the saveset for restore. You can mount any non-compressed and non-encrypted file-based saveset stored to default data store Path or to Si3 data store. Mounting is not possible if the savesets are stored to tapes. For more details, see Cross-Platform Recovery File System Layer.
It is recommended that this option is enabled for restoring specific data, such as Exchange, Hyper-V and V-Sphere backups, because it provides faster restore time and performance. The target saveset is mounted to the SEP sesam home directory var\tmp\mnt, e.g., C:\Program Files\SEPsesam\var\tmp\mnt\save_set_ID. This way the saveset is instantly accessible for browsing and searching before the actual restore is even triggered, providing you with quick access to your data, such as single mailboxes. The mounted saveset is basically a virtual read-only file system, therefore it cannot be altered or otherwise damaged.
Step 4: Select files
Individual files can be specified for restore.
The file explorer is used to specify the files to be restored.
The Search button below provides an additional option to search for files within the target saveset.
Step 5: Save and start
The final step of the restore wizard provides an overview of the restore task. In the table above the saveset that is selected for restore is displayed with its attributes. In the Name field, the name of the task is assigned automatically and can be modified.
Most of the following options already have default values or are enabled by default and can be used in most cases. Some provide fine-tuning needed for more specific data restore.
Drive: The number of the drive with backed up data (more relevant for tape backups without a loader). Optionally, select the drive number of the drive that will be used to read the data. Typically, you use this if you have configured additional drives and you want to assign dedicated drives for the restores. For details, see the option Create second drive (introduced in SEP sesam 4.4.3 Tigon) in Configuring a Data Store.
Interface: The name of the server FROM which the files are being restored. This is either a Remote Device Server (RDS) or the SEP sesam server.
Target node : The name of the server where the files are being restored TO.
Preferred media pool: If the data was migrated or replicated and different media pools were used for the process, the source media pool to restore from can be selected from the drop-down list of available media pools.
Used media | Barcode: If the data was migrated, the migrated copy is stored to another media. Here the source media to restore from can be selected from the drop-down list of available media.
Target path settings provides the following options:
- Restore to original path is selected by default and restores the data to the same location from which it was backed up. Note that this only applies if the target node is the same server from which the data was backed up, i.e. when source and target server are the same.
- Original tree structure is enabled by default when restoring to original location. The directory structure of the restored files is the same as the original directory structure of the backed up data. If this option is disabled, the directory structure is not recreated and only the files are restored (flat structure).
- New restore target should be selected when restoring files to some other location. The path to the directory to which the data should be restored can be entered manually or by using the Browser button to open the file explorer.
Execution options provides the following options:
- Do not overwrite existing files is selected by default. Files will be restored only if they are not already present on the target system.
- Overwrite existing files will replace files on the target system with their restored version.
- Create a new version will restore files under a new name.
Clicking the button Expert options will open a new window, where more specific options and actions can be defined.
Verbose level allows user to change the verbosity of the main log to display more information than the default logging mode. Verbose logging is divided to levels 0 to 6.
- 0: Print only standard and error messages together with summary.
- 1: Add a line for every item when its processing starts: sbc-3008: Info: Processing item: [xxx]...
- 2: Add a line when processing for item is finished: sbc-3108: Info: Item processed successfully: [xxx]
- 3: Add backup module processing information (with DB_API modules).
- 4: Add underlying module processing XBSA and detailed DB_API modules.
- 5: Add packing data (mtf, cpio, sidf) trace messages.
Restore options text box allows for other specific options to be entered.
Based on the specification in the previous parts of the wizard, one of the following is already selected: Restore the complete saveset , Restore according to composed list or Disk_info disaster recovery. Changes of these restore options will override the specification made in the restore wizard.
- Restore the complete saveset will restore all files of the saveset.
- Restore according to the composed list will create a selective restore according to the regular expressions used in filter (see Filter tab below).
- Disk_info disaster recovery will restore disk info, for example a master boot record and registry during disaster recovery.
Relocation tab By default, no relocation is selected, restoring files to original path . If with relocation is enabled, a new target location can be specified for restored files. Individual files can be restored to separate paths.
Filter tab Files for a selective restore can be defined using regular expression-based filtering.
Task type tab By default, the task type according to which the data is backed up is selected (default is Path; other task types are, for example, Hyper-V, SAP Hana, Exchange Server, Lotus Notes, MySQL, VMware vSphere etc.).
When you have backed up data with task type other than default Path, for example Hyper-V, you can still use the option As path backup. This option allows you to restore your data directly to the file system without any additional action, for example, files from a Hyper-V backup, rather than restoring according to your special type, for example, restoring (and importing) Hyper-V data to the Hyper-V manager.
The option Write saveset into file allows you to restore the entire saveset into a single file.
|To use a pre/post interface, you have to activate it first and create your own commands. Interfaces can be activated in GUI: in the menu bar, click Configuration -> Interfaces -> select the interface you want to activate and the client. The interface script window opens, allowing you to configure the desired action. Once done, click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory. For more details, see Using Pre and Post Scripts.|
EOL tab Specifies for how long (in days) this restore task will be kept and can be accessed using GUI. Default is 7 days. The value 0 means that a restore task will be kept permanently unless you manually delete it.
Start time tab
- Instead of starting your restore immediately, you can specify the Start time by entering the desired date and hour.
- In the Delay start for up to, the maximum allowed startup time (the amount of time an event can be in the queue) can be specified in days and/or hours. The actual event startup depends on the processor load of the system. At the starting time of the event, every event is forwarded into the queue, where it might wait until jobs with a higher priority are finished. For jobs with the same priority, the FIFO rule (first in first out) applies. If the event cannot be executed within this specified time frame, it will not be executed at all.
- Stop task if it runs longer than can be defined by setting the amount of time (days and/or hours) after the event's scheduled start time at which the event will be cancelled.
- Additionally, Stop task at can be used to define the exact date and time when the task should be stopped.
- A Follow Up event can be specified to trigger the predefined event on the SEP sesam Server once the restore is completed. For details, see Follow-up Events.