5 2 0:SEP sesam Server Cloud-Based Disaster Recovery

Overview

A computer disaster refers to a system failure, disk failure, or other serious event that prevents access to critical data. Disaster recovery (DR) is a set of procedures designed to restore essential technological infrastructures and systems following such an event. Standard backups are not sufficient, for disaster recovery specialized backup is required to recover server data and restore the backup system to a functional state.

SEP sesam disaster recovery feature enables users to effectively prepare for unexpected failures and restore their systems with minimal downtime. Several disaster recovery options are available, BSR Pro for Windows clients, Bare Metal Recovery for Linux clients, and disaster recovery of the SEP sesam Server.

SEP sesam Server disaster recovery function provides self-backup mechanisms to preserve essential system configuration, database information, and logs. These self-backups are critical for restoring the SEP sesam Server in the event of a failure.

To support disaster recovery of the SEP sesam Server, SEP sesam includes three key components:

• SEP sesam Server self-backup: To back up SEP sesam Server's configuration files, logs, and database, a dedicated backup task must be configured. During installation, SEP sesam automatically creates the task SESAM_BACKUP, which is set up to back up all essential components required for server recovery. This task must be executed regularly to maintain an up-to-date recovery point. Alternatively, you can configure a custom backup task for SEP sesam Server self-backup. It is recommended to include the keywords DISASTER or SESAM (case-insensitive) in the task name so that SEP sesam recognizes it as a disaster recovery task.
• SEP sesam database export: To preserve configuration details and backup history, SEP sesam automatically exports its internal database for the SEP sesam Server self-backup. The self-backup task with the keywords DISASTER or SESAM in its name (e.g., SESAM_BACKUP), triggers a full database export before the backup or migration of the backup starts.
• SEP sesam Disaster Interface (sm_disaster): The disaster interface collects all necessary disaster recovery data and sends it via email. It requires a configured "sesam" email account with a valid SMTP address and server settings. The interface is triggered automatically when a self-backup task with DISASTER or SESAM in the name is run.

SEP sesam self-backup options

Starting with SEP sesam version 5.2.0 Artemis, there are two disaster recovery deployment options, depending on the target storage type for the SEP sesam Server self-backup:

• Self-backup with DB dump file via email: The SEP sesam Server self-backup task triggers full export of the SEP sesam database and then performs backup of SEP sesam configuration files, logs, and database. To ensure recovery if the backup server is lost, SEP sesam also creates a bootstrap database export that includes configuration data and backup history from the last 30 days. This file is sent as an email attachment via the disaster interface, along with detailed restore instructions. This option supports all types of storage targets, including tape. For more information, refer to SEP sesam Server Disaster Recovery with Bootstrap DB Export.

• Self-backup with DB in cloud-based Si3 storage (recommended): If you are using the Si3 deduplication store, you can back up your SEP sesam Server to S3 or Azure cloud storage. This option enables direct access to a full SEP sesam database export in cloud storage. The sesam_dr_info.ini file, sent as an email attachment via the disaster interface, includes all required information for disaster recovery, including a secure download link to the database export in the cloud. This ensures high resistance against attacks on backups and helps protect your SEP sesam Server.

	Note
	The preparation and recovery procedures differ depending on the chosen option. This article describes the cloud-based self-backup and recovery procedure for the SEP sesam Server, which uses a full database export.

SEP sesam self-backup process

To be prepared for a potential failure of the SEP sesam Server, you must maintain an up-to-date self-backup of your SEP sesam installation. The default self-backup task, SESAM_BACKUP, is preconfigured to back up the following components:

• SEP sesam configuration files
• the var directory, including all listings
• the daylog files
• the database
• the INI-files

For a consistent recovery process, it is recommended to run self-backups daily in COPY or FULL mode.

When the cloud-based disaster recovery option is properly configured, the self-backup process proceeds through the following automated steps:

• When SESAM_BACKUP task is started, the entire SEP sesam database is exported to <SESAM_ROOT>/var/db_pg/backup. Export files are named using the following convention: sesam_db_<timestamp>.sql.gz.
• Backup of the SEP sesam Server (SEP sesam Server self-backup) is performed to the selected media pool. It is recommended that you configure a SEP sesam DR-dedicated media pool for storing all your SEP disaster recovery savesets.
• After successful backup, a bootstrap database file (e.g., sesam_bootstrap_db_<timestamp>.sql.gz) is created in <SESAM_ROOT>/var/db_pg/backup. This file contains the full SEP sesam database export. Additionally, the SBC archive of the configuration files (sesam.ini.{.}.sbc), which includes the public SSH key files, is stored in the same directory.
• Finally, the sm_disaster script is executed. If the backup target is linked to an Si3 deduplication store, the two files from <SESAM_ROOT>/var/db_pg/backup are stored on the Si3 store in the same media pool used for the SEP sesam Server self-backup. If cloud storage is configured for the Si3 deduplication store, these files are also replicated to the connected cloud storage. The disaster recovery email, sent by the interface, includes a sesam_dr_info.ini file as an attachment. This file contains all the necessary information for recovery, including direct download links to the database file and the SBC archive.

If a migration task is configured for the SESAM_BACKUP task, the migration will also trigger the last two steps of this process.

	Note
	If the target media pool is not located on an Si3 store, the disaster interface runs as described in SEP sesam Server Disaster Recovery with Bootstrap DB Export.

Preparing for Disaster Recovery

To ensure a successful disaster recovery process, complete the preparation tasks, described in this section.

1. Configure the 'sesam' email account.

The disaster interface relies on email notifications to send critical recovery information. To configure an email account in SEP sesam, follow the procedure described in Configuring Email Accounts. Make sure to use sesam (must be lowercase) as the account name.

Screenshots

For added security, it is recommended to keep disaster-related emails separate from the corporate environment. You can use a cloud-based email service or regularly back up DR emails to an external storage device.

2. Activate the disaster interface.

The disaster interface (sm_disaster) enables disaster recovery by generating and sending DR-related information. To activate it, follow the procedure described in Configuring SEP sesam Interfaces.

Screenshots

When the disaster interface is triggered, it sends a SEP sesam disaster recovery email containing the information required to recover the SEP sesam server. The sesam_dr_info.ini file attached to the email contains all relevant information, including the correct URLs for accessing the cloud storage.

3. Prepare storage for DR backups.

For SEP sesam Server self-backup, the local or cloud-based Si3 deduplication store can be used.

Using an Si3 deduplication store, the DR backup can be securely stored in a cloud storage (e.g., S3, Azure). This ensures high resistance against attacks on backups and helps secure your SEP sesam Server.

4. Configure storage for the bootstrap database file.

SEP sesam database is exported to a bootstrap database file, containing all the important data for disaster recovery. The export format is controlled by the global variable key:

sm_conf_bootstrap_format <small|full>

• small (default): Exports only the minimal data required for disaster recovery. This is recommended when sending the bootstrap as an email attachment.
• full: Exports a complete SEP sesam database dump. This option is recommended when storing the bootstrap file in an Si3 deduplication store.

With SEP sesam version 5.2.0 Artemis, the DR functionality enables automatic storage of the SEP sesam bootstrap database in the Si3 deduplication store. The bootstrap database is saved to the same media pool that is defined in the SESAM_BACKUP task.

To enable this feature, set the following global variable key:

sm_conf_bootstrap_upload_sds=1

For more information on setting the global variables, refer to Configuring System Settings.

5. Configure the SESAM_BACKUP task and schedule regular backups.

The SESAM_BACKUP task is a self-backup task that ensures all necessary disaster recovery data is available. When you install or update the SEP sesam Server, the SESAM_BACKUP task is already preconfigured, and the required directories are included in the source. You can create an exclude list to exclude directories such as work, log, or others as needed, and configure additional settings and options. For detailed descriptions of the available options, see the standard backup procedure.

Screenshots

	Tip
	Disaster recovery is performed with log level 0. If required, you can set a higher log level for the restore in the properties of the backup task SESAM_BACKUP -> Options tab -> Restore options field. For details, see Setting log level for a task.

Follow the standard backup procedure to schedule this task. It is recommended to run the backup daily in COPY or FULL mode.

Recovering SEP sesam from disaster

The disaster recovery procedure for SEP sesam Server involves multiple steps. The two key components required for successful recovery are the bootstrap database and the SEP sesam Server self-backup (SESAM_BACKUP). For restore, all backups that contain DISASTER or SESAM in the name should be checked to select and restore the last known good copy of the data.

If the entire system has failed and needs to be recovered, replace the host server system. Set up the new server with the same OS version, hostname, and IP address as the original server. Then, prepare the SEP sesam Server installation package for your OS.

	Note
	Make sure to set up the server with the same hostname and IP address, and use the same SEP sesam version that was installed on the original server.

Starting with SEP sesam version 5.2.0 Artemis, disaster recovery enables storing the SEP sesam Server self-backup and bootstrap database file in an Si3 deduplication store, either local or cloud-based. This feature enables a full export of the SEP sesam database to a bootstrap file, making the recovery process faster, simpler, and more reliable.

SEP sesam Server cloud-based recovery procedure

Before you start the recovery, make sure to meet the following prerequisites:

• Retrieve the SEP sesam disaster recovery email with the sesam_dr_info.ini file that contains the correct URL addresses for accessing the cloud storage, and save it locally on the host for the SEP sesam Server (for example, /tmp/sesam_dr_info.ini on Linux, or C:\Temp\sesam_dr_info.ini on Windows).
• Enable running SEP sesam commands globally from a terminal or command prompt (CMD) by setting up a SEP sesam profile as described in FAQ: How can I set up a profile?
• Perform a clean installation of the SEP sesam Server to provide the required environment for restoring the server configuration and backup data. For detailed instructions, refer to the SEP sesam Quick Install Guide.

The SEP sesam Server disaster recovery process is initiated using the sm_pysesam sesam_recover command, which reads recovery information from the sesam_dr_info.ini file. This file contains the required configuration and URLs to access backup data from the Si3 deduplication store.

To start the recovery, run the following command:

sm_pysesam sesam_recover -f <path to sesam_dr_info.ini>

Replace <path to sesam_dr_info.ini> with the actual location of the file, for example, /tmp/sesam_dr_info.ini on Linux or C:\Temp\sesam_dr_info.ini on Windows.

	Note
	If you only want to download the necessary bootstrap files (DB export and configuration) without starting the recovery, use the -⁠n (no recovery) option: sm_pysesam sesam_recover -f <path_to_sesam_dr_info.ini> -n

During the SEP sesam Server disaster recovery procedure, the following steps are performed automatically:

• The SEP sesam database (DB) export file is downloaded from the Si3 deduplication store.
• The SEP sesam configuration (INI files archive) is downloaded from the Si3 deduplication store.
• The SEP sesam Server is shut down.
• The Queue Manager (QM) and SEP sesam database are started in recovery mode.
• The SEP sesam database structure is recreated.
• The database content is imported from the bootstrap file.
• The configuration files (INI archive) are extracted and applied.
• The SEP sesam Server is started with the restored configuration and database.
• The most recent SESAM_BACKUP is restored to ensure that LIS files, required for selective restore, are available.

This approach ensures that SEP sesam Server is fully operational again with minimal downtime after a disaster.

After the recovery

After completing the recovery process, restart the SEP sesam service.

Once the SEP sesam Server is running again, it is recommended to verify that the hardware is properly connected and perform a test backup and restore on the available devices. If the recovery date does not match the date of the last SESAM_BACKUP, run a NEWDAY event to reinitialize the execution queue.

Some backup results may appear incorrect in the job status views. This is due to the time gap between the last SESAM_BACKUP and the recovery, as the scheduled jobs that were supposed to run during the server downtime were not executed. The number of displayed errors depends on the duration of the server downtime and the number of missed scheduled backup jobs.

See also

SEP sesam Server Disaster Recovery with Bootstrap DB Export — Bare Metal Recovery Linux — SEP sesam BSR Pro for Windows — Configuration Files

Copyright © SEP GmbH (formerly SEP AG) 1999-2025. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP GmbH. When compiling and designing user documentation SEP GmbH uses great diligence and attempts to deliver accurate and correct information. However, SEP GmbH cannot issue a guarantee for the contents of this manual.