5 1 0:Configuring Si3 Replication

From SEPsesam
Revision as of 14:12, 8 December 2023 by Jus (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Other languages:


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


Overview


SEP Si3 replication is designed to consistently replicate data between SEP sesam Remote Device Servers (RDS), or between an RDS and a SEP sesam Server. This offers redundancy for disaster recovery and serves as an additional source for ordinary data restore operations.

SEP Si3 replication is used together with Si3 target deduplication, an inline block-level data deduplication solution that directly writes data from the SEP sesam Server or Remote Device Server (RDS) to the backup media. By storing only one instance of the data on the backup media, there is a notable reduction in the amount of data backed up on storage.

When combined with SEP Si3 replication, this setup provides faster backup cycles and better SEP sesam performance.

  • SEP Si3 target deduplication can be configured by creating an Si3 deduplication data store.
  • Use the Si3 deduplication data store when storing data in S3 Cloud.

Prerequisites

Before you start configuring Si3 replication, ensure that your environment fulfills the following prerequisites:

SEP sesam environment:
Disk space and resources:
License:
  • Valid Si3R replication license for each Si3T node (refer to Licensing).

Configuration procedure

Follow these steps to configure SEP Si3 replication:

  1. Configure the SEP sesam Server and RDS systems as required.
  2. Add the RDS systems as ordinary SEP sesam Clients: In the Main selection -> Components -> Clients, click New Client. Make sure you correctly specify the short name or FQDN of the client in the Interfaces field to establish a DNS connection between SEP sesam Server and SEP sesam RDS. For details, see List of Ports Used by SEP sesam and How to check the DNS configuration.
  3. Configure the first Si3 deduplication store. For detailed instructions, refer to Configuring Si3 Deduplication Store.
  4. Configure the media pools for this Si3 deduplication store. Set up the media pools according to the proposed retention time, for example, source_dedup_daily (proposed retention time: 7 days), source_dedup_weekly (proposed retention time: 30 days), source_dedup_monthly (proposed retention time: 200 days) media pool. For details, see Configuring media pools for data stores.
  5. Configure the second, remote Si3 deduplication store and media pools for this data store. Follow the same instructions as in the previous two steps.
  6. Test both Si3 deduplication stores. Create a backup task and execute a backup on both Si3 deduplication stores to ensure proper configuration.

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:

  1. 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.
  2. 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.
  3. 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.


See also

Configuring Replication - Creating a Replication Task - Creating a Replication Event

Copyright © SEP AG 1999-2024. 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 AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.