5 1 0:About Restore
Overview
|
|
Visit SEP sesam YouTube Channel for latest videos and webinars. |
|
Check FAQ to find the answers to most common questions. |
|
Problems? See the Troubleshooting Guide. |
|
If you are using an older SEP sesam version, refer to Documentation archive. |
SEP sesam is a powerful enterprise restore solution designed to recover data from a wide array of operating systems, applications, email systems, databases, and virtual platforms. In data management, the restore process is as important as the backup. SEP sesam ensures that your file system and application data is safely retrieved from secondary storage and restored to its original state, whether it resides on disk, tape, the cloud, or at physical or remote locations.
The restore process involves retrieving data from a specific point in time and returning it to its original state. It consists of two main elements: a restore task, which defines the scope and parameters of the restore process (what), and a restore event, which determines the time of the restore process execution (when). Typically, a restore is a one-time event that is triggered immediately after the task is configured. However, SEP sesam offers the flexibility to schedule a restore for data that has not yet been backed up, providing a proactive approach to testing and verifying data recovery. For example, a restore can be set up to run at the end of the daily backup routine and restore the most recently backed up files to a new directory to enable effective data validation.
With SEP sesam generational restore, data can be restored for any backup point in time using the entire backup chain. A backup chain is a sequence of full, differential, and incremental backups. In a generational restore, all necessary backups in the backup chain are merged, enabling users to browse and select backed up files. When a restore operation is initiated for a specific file or data set, SEP sesam reconstructs the data by applying the relevant differential and incremental backups to the full backup, thereby restoring the data to the specified point in time.
Key features
SEP sesam can be effectively integrated into a wide range of environments, making it a versatile choice for comprehensive data protection and recovery. It offers a range of key features and benefits to implement restore solutions that meet specific requirements:
- Generation restore: When a restore operation for a specific file or data set is initiated, SEP sesam reconstructs the data using the required backups in the chain. It starts with the full backup and then applies the necessary differential and incremental backups to restore the data to the specified point in time.
- Selective restore (Single File Restore in virtual environments): Only specific parts of data, such as individual files and directories, can be restored from the saveset. SEP sesam provides multiple methods to access and browse the saveset, including the standard backup browser or the option to mount a backup or attach the virtual disk containing the backup.
- Complete restore (Virtual Machine restore in virtual environments): The entire saveset or a full virtual machine is restored. While selecting individual files is not possible, SEP sesam provides control over how files or virtual machines are overwritten during the restore process.
- System state restore with Microsoft VSS: System state restore uses the Microsoft Volume Shadow Copy Service (VSS) to recover system state components, including core files and registry settings. This enables restoring a fully functional Windows operating system. System state components are typically restored as a group, however, SEP sesam also allows restore of individual components when needed.
- Disaster Recovery: SEP sesam offers comprehensive disaster recovery options, including bare metal recovery on Linux and BSR Pro recovery on Windows. Disaster recovery for the SEP sesam Server is also provided, ensuring minimal downtime and data loss in the event of a disaster.
- Broad compatibility and versatility: SEP sesam covers a wide array of applications, databases, virtual environments, groupware systems or various other systems, and supports different hardware and cloud-based storage solutions, making it adaptable to diverse infrastructures and storage requirements.
Interfaces
SEP sesam provides different interfaces that can be used to configure the restore process, allowing for flexibility and customization based on your specific requirements:
Web-based Restore Assistant: The web-based Restore Assistant is a modern and intuitive option. It offers a simple configuration of the restore process, and provides additional advanced options for customizing the restore to your specific needs. New functionalities are continually introduced in the Restore Assistant, making it the preferred choice. Note that when starting the restore from GUI, it is opened by default.
Standard GUI (Graphical User Interface): The original GUI restore is deprecated and should therefore no longer be used. However, there are still some older task types for which the GUI restore can be used. If you want to use the GUI restore, change the restore settings under Configuration -> Defaults/General.
SBC CLI (sesam Backup Client Command Line Interface): The SEP sesam SBC (sesam backup client) component provides a set of commands and options that facilitate the collection and consolidation of backup data on the client system, ensuring efficient data transfer to the SEP sesam Transfer Protocol Daemon (STPD). During a restore operation, SBC CLI is responsible for receiving the required data and restoring it to the target system. SBC CLI is primarily used for backing up and restoring data locally on the host and is especially useful automation and test scenarios.
Restore procedure
The restore procedure in SEP sesam follows a standard process for file systems and application data, with some variations for SEP sesam extensions that involve different options. SEP sesam provides preset task types for various restore scenarios, such as common file system restore (type Path), Exchange, MySQL, SAP HANA, and more, as well as task types designed for virtual environments that enable image-level restores and single-file restores (SFR).
Specific restore procedures correspond to the data you intend to recover, as different methods are employed for different data types. For comprehensive information on supported extensions, their features, and associated restore procedures, refer to SEP sesam Extensions and the SEP sesam OS and Database Support Matrix.
Similarly to the backup procedure, the restore procedure also follows these general steps:
- Creating a restore task: Initiate the restore process by selecting the data that needs to be restored. This involves selecting the scope, source and target systems that are to be included in the restore operation, and specifying other options to customize the restore.
- Creating a restore schedule: Define the restore schedule based on your requirements. Specify the frequency, timing, and recurrence of the restores to ensure a systematic and effective data recovery process.
- Creating a Restore Event: Determine when and how you want your data to be restored. Select the restore destination and configure specific options or parameters for the restore process.
|
Note |
| Typically, restore tasks are executed immediately once configured. However, SEP sesam also offers the flexibility to save a restore task and schedule it for a later time, allowing you to plan and optimize your data recovery procedures. |
For detailed information, refer to Standard Restore Procedure.
Scheduling restores
SEP sesam provides an option to schedule a restore task to run at a specific time. By scheduling restores during off-peak hours or times of lower system activity, you can minimize the impact on regular operations. In addition, regularly scheduled restores can be used to verify the integrity of backup data and ensure that the restored data matches the source data. This is particularly important in critical environments to identify and address potential issues with backups or the restore process. Some industries or organizations require periodic data validation and restoration to comply with regulatory standards or auditing requirements.
To schedule a restore, a restore event is created in the SEP sesam graphical user interface (GUI). Restore events can be configured as stand-alone instances or set to repeat at regular intervals within a defined schedule. For a specific restore task, multiple events can be created across different schedules, each with its own set of customized parameters and configurations.
For more information see Creating a Restore Event.
Advanced uses for restore
SEP sesam enables you to incorporate restore operations into your backup processes, reduce manual tasks, and enhance the reliability and efficiency of your data management.
With SEP sesam you can customize your data management procedures, enhance data consistency, and improve the efficiency of your backup and restore operations. To accommodate various use-cases and scenarios, SEP sesam offers the pre/post interfaces, allowing you to configure restore as a post-execution action for backups or as a follow-up action for backups and commands.
By pre-configuring restore actions, you can reduce manual intervention and simplify data recovery processes. In cases where backup operations are part of a broader data management strategy, this ensures that your data is in a consistent and recoverable state, making it more reliable.
Restore as a post-exec
You can use the SEP sesam CLI commands to set up a post-exec script that defines specific actions to be taken after a successful backup. For example, you might want to automatically restore specific data to its previous state immediately following a backup operation. This advanced use case streamlines data management by ensuring that you always have access to the most up-to-date information.
To use the post-exec script, you have to activate the post interface and configure post-exec commands within the GUI. In the menu bar, navigate to Configuration -> Interfaces and select the interface you want to activate. The interface script window opens, allowing you to define the actions you want to execute. The configured interface is saved to the <SESAM_ROOT>/bin/sesam directory for easy access and management. For more details, see Using Pre and Post Scripts.
Restore as a follow-up
Setting up restore as a follow-up action allows a specific event to be triggered on the SEP sesam Server after the completion of an initial event, such as a backup or a command. This feature is especially useful for scenarios where data consistency needs to be ensured or when you want to automate your backup and restore processes. For more details, see Follow-up Events.
Extensions and module support
SEP sesam offers a wide range of extensions that cover various systems and environments, ensuring comprehensive backup and restore capabilities. These extensions cover various databases, such as Oracle, MS SQL, IBM DB2, Informix, SAP R/3 and more, applications like SAP, groupware systems such as MS Exchange and IBM Domino, virtualization environments like VMware vSphere, Hyper-V, Citrix Hypervisor, RHV and more, and different storage solutions, like NetApp and HPE StoreOnce, or cloud storage.
Each of these extensions is designed to address the specific requirements and features of the systems or platforms it covers. The restore procedures may vary for each extension. For detailed information on how to perform restores for specific extensions, refer to the extensions list and select the relevant extension documentation.
See also
Restore (main page) - Standard Restore Procedure – Backup (main page)