5 2 0:SEP sesam Server Disaster Recovery with Bootstrap DB Export

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 (e.g., SESAM_BACKUP) that contains the keywords DISASTER or SESAM in its name triggers a full database export before the backup or the 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 backup task with DISASTER or SESAM in the name is executed or migrated.

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.

• 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. For more information, refer to SEP sesam Server Cloud-Based Disaster Recovery.

	Note
	The preparation and recovery procedures differ depending on the chosen option. This article describes the SEP sesam self-backup and recovery process using the Bootstrap database export, which is sent as an email attachment.

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 a backup task containing the keywords DISASTER or SESAM (case-insensitive) in its name is started, the self-backup process proceeds through the following automated steps:

• 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 SEP sesam configuration and metadata information on self-backups performed in the last 30 days. Additionally, the SBC archive of the configuration files (sesam.ini.{.}.sbc), which includes the public SSH key files, is stored in the same directory.
• The disaster interface is triggered and the sm_disaster script is executed, sending the bootstrap file and the SBC archive as an email attachment along with detailed recovery instructions.

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

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

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 and the bootstrap database file as an attachment.

3. Prepare storage for DR backups.

Regular data stores or tape libraries can be used to store SEP sesam Server self-backups. It is recommended to use a dedicated media pool for DR backups to ensure better organization and protection of disaster recovery data. Additionally, consider regularly migrating SESAM_BACKUP to tape. This provides an offline copy of the backup, ensuring availability even in the event of a security incident, such as a ransomware attack.

4. Configure storage for the bootstrap database file.

The bootstrap database file contains all the necessary data for disaster recovery. By default, the export includes the SEP sesam configuration and metadata for self-backups performed in the last 30 days.

For added security, it is recommended to keep the bootstrap database separate from your corporate environment. You can either forward disaster-related emails with the bootstrap database to a separate (e.g. cloud-based) email service, or regularly back them up to a removable storage device, such as a USB stick.

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

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

	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.

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.

The recovery procedure for the SEP sesam Server has changed with version 5.2.0 Artemis. If you upgraded from an earlier version, the existing disaster recovery script is not automatically updated. As a result, the recovery instructions included in the email may be outdated or incorrect. To resolve this, either manually recreate the script as described in Configuring SEP sesam Interfaces, or follow the updated recovery procedure described below.

SEP sesam Server recovery procedure

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

• Connect the backup storage hardware to the new host for the SEP sesam Server. The components will be detected and pre-configured during the SEP sesam Server installation.
• Retrieve the SEP sesam disaster recovery email. On the SEP sesam Server, save the bootstrap database file (sesam_bootstrap_db_[timestamp].sql.gz) and the configuration file (sesam.ini.[timestamp].sbc) locally. Both files must be saved to the same local directory (for example, /tmp/ on Linux, or C:\Temp\ on Windows).

The SEP sesam Server disaster recovery process starts with installing the SEP sesam Server and importing the bootstrap database file, which enables retrieving the list of available self-backups for restore.

On Windows, this process is integrated into the SEP sesam installation wizard:

1. Start the installation and select the SEP sesam Server Disaster Recovery option.
2. In the final step, Ready to Install SEP sesam Server version <number>, click Browse under Import SEP sesam Server database.
3. Select the saved bootstrap file and click Install to proceed.

Screenshots

On Linux, install the SEP sesam Server package. After the installation:

1. Open the SEP sesam GUI as the superuser Administrator.
2. Import the bootstrap file using the following command:

sm_db_update update -i <path to bootstrap file>

Screenshots

After importing the bootstrap data, decompress and restore the configuration files from the SBC archive. Use the following commands:

gzip -d -S gzip <path to the zipped SBC archive>

sbc -r -o over -s @<path to SBC archive> -R /

When these steps are completed, SEP sesam should retain the basic configuration (e.g., all existing drives). However, you should check the following on the newly installed server:

• Check the system settings to ensure that the restored SEP sesam configuration matches the current server environment. Verify library and drive device names, disk partition device names, mount points, and other relevant settings. If there are mismatches, update the SEP sesam settings accordingly.
• If recovery is performed from physical media, open the GUI and run a SEP sesam archive adjustment to synchronize media information with the physical tape library. Navigate to Main selection -> Components -> Tapes -> Libraries, select the required tape libary and click Archive Adjustment. For details, see Setting up Archive Adjustment.

Then, restore the SEP sesam Server self-backup and import the restored SEP sesam database. Starting with version 5.2.0 Artemis, the restore procedure via the GUI is no longer available and must be performed using the CLI. To enable running SEP sesam commands globally from a terminal or command prompt (CMD), set up a SEP sesam profile as described in FAQ: How can I set up a profile?

To restore the most recent SEP sesam Server self-backup, run the following command:

sm_cmd start restore -j SESAM_BACKUP -O o -a disaster_restore -R /

	Note
	To restore the SEP sesam Server from a specific backup, use the following command: sm_cmd start restore -s <saveset> -O o -a disaster_restore -R /

The database backup created during the SESAM_BACKUP will be restored to SESAM_VAR/db_pg/restore.

After the restore, the Complete the disaster restore dialog will open to import the database. Click OK to confirm.

Screenshots

If this dialog doesn't appear, import the database manually using the following command:

sm_db_update update -i <path to DB>

Replace <path to DB> with the actual location of the restored SEP sesam database, for example, /var/opt/sesam/var/db_pg/restore/sesam_db_20250319125703-20250319.sql.gz.

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 Cloud-Based Disaster Recovery — 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.