5 1 0:Configuring Replication

Welcome to the latest SEP sesam documentation version 5.1.0 Apollon. For previous documentation version(s), check documentation archive.

Overview

Additional resources

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.

Configuring replication in SEP sesam involves establishing a consistent and reliable data duplication process across different storage environments, such as software-based, hardware-based, or cloud-based storage systems. While the configuration process varies based on the selected replication type, it shares common prerequisites, configuration steps, testing procedures, and monitoring practices.

Prerequisites

Note that some additional prerequisites may apply for your selected configuration and replication type. Refer also to specific articles that describe the replication environment you are configuring.

To ensure optimal performance of SEP sesam replication, the following prerequisites apply:

SEP sesam Server and RDS must have the same SEP sesam version installed.
Java must be installed on RDS and deduplication clients. For details on the required Java version, refer to Java Compatibility Matrix.
Valid licenses are required, depending on your environment (Si3R, HPE StoreOnce VSA, Cloud Storage) For details, see Licensing.
A reliable network connection is required between the servers. Note that the NAT (Network Address Translation) infrastructure is not supported.

	Note
	Antivirus programs may disrupt network communication and cause SEP sesam processes, such as backup and replication, to fail. One program that is known to cause SEP sesam processes to terminate is Sophos Firewall with IPS (Intrusion Prevention System) enabled. Make sure that there are no antivirus, firewall, IDS or IPS programs preventing interaction with SEP sesam.

Common configuration procedure

To configure and set up the replication process, follow the steps described below:

Select replication environment. Choose the replication environment that best suits your data protection strategy. SEP sesam supports various environments, including software-based, hardware-based, or cloud-based storage systems.
Review replication best practices. Before starting configuration, it is recommended to consult the Replication Best Practices. This helps your replication setup follow recommended practices, optimizing performance and reliability.
Fulfill the prerequisites for your replication type. Ensure that common prerequisites, such as matching SEP sesam versions, Java installation, and proper licensing, are met. Depending on the selected replication type (SEP Si3 or HPE StoreOnce), fulfill specific prerequisites associated with the selected environment. Refer to documentation for your replication type to understand any additional requirements or limitations.
Configure your replication environment based on the selected replication type. This involves setting up SEP sesam Server and Remote Device Servers (RDS), defining media pools, and configuring other relevant settings.
Test the sequence of operations to ensure that all systems are communicating properly and that replicated files are accessible and not corrupted.

	Note
	It is strongly recommended to also test your backups, because failed or partially restorable backups cannot be replicated.

Setting up the replication process

After successful configuration, set up the replication process. This ensures that only changed data blocks are sent over the network during replication. This involves the following steps:

Create a replication task.
Define source and target media pools, specify the network interface, and set the time frame for the backups to be replicated. For detailed instructions see Creating a Replication Task.
Run the initial replication.
Transfer all data from the source to the destination. Keep in mind that the initial replication process requires significant CPU resources, network bandwidth, and time for successful completion. For detailed instructions see section Initial replication.
Schedule replication.
Decide on the schedule for replication cycles and then create and schedule a replication event. This ensures that subsequent replications occur automatically at specified intervals. For detailed instructions see Creating a Replication Event.

Initial replication

During the initial replication, all data is transferred for the first time from the source to the destination. This process requires substantial CPU resources, network bandwidth, and time to complete successfully.

The initial replication should be started manually. After a successful first replication, subsequent replication cycles should be automated. In the process of replication, SEP sesam transfers only the data that has changed on the source server.

To start the initial replication manually, perform the following steps:

From Main Selection -> Tasks -> Replication Tasks, click New Replication Task. The New Replication Task window opens.
Configure the replication task and parameters. Specify the source and target media pools, network interface, drive numbers, and backup date criteria. For details, see Creating a Replication Task.
In the GUI menu, select Activities -> Immediate start -> Replication.
In the Immediate Start: Replication window, select the replication task you want to start in the Task name drop-down list and then click Start.

Screenshots

	Note
	To ensure that the replication is successful, you can monitor the progress and check the status of the replication. For details, refer to Monitoring replication below.

Testing backups

Testing backups is important for validating the reliability of your replication process. Before configuring replication, run test backups to ensure that your data is backed up properly. Use the SEP sesam GUI to create a backup task and verify its success. It is also recommended to test the replication process periodically, to make sure the data is successfully stored and accessible for restore.

It is only possible to replicate savesets with status successful and savesets with warnings (status successful or with warnings). To optimize replication performance, savesets with errors or partially restorable savesets (from cancelled backups) cannot be replicated.

Monitoring replication

Monitoring replication is important to ensure the ongoing success of your data protection strategy. Use the SEP sesam Web UI for real-time monitoring, checking replication statuses, and tracking progress.

You can view the status of your replications in the SEP sesam Web UI (Monitoring -> Migrations/Replications) or in the GUI (Job State -> Migrations and Replications).

The status of the replication jobs is logged together with the migration jobs. Go to Monitoring -> Migrations/Replications, and look for your replication task. The view provides details on status, start and end time, the size of source data and amount of transferred data, etc. For example, you may be replicating 100 GB of data (column Data Size), but only 1 GB (column Transferred) is transferred physically over the network, as only a small amount of data is changed.

In Web UI separate views are available for reviewing individual tasks and grouped tasks. You can switch between the views by clicking Migrations/Replications or Grouped Migrations/Replications links above the available filters.