4 4 3 Beefalo:SEP Si3 Replication

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2020. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo/4.4.3 Beefalo V2. 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), which can also be SEP sesam Servers. This is advantageous in terms of redundancy for disaster recovery as well as in providing additional source for ordinary data restore.

SEP Si3 replication is used together with Si3 target deduplication, an inline block-level data deduplication solution that writes data directly from the SEP sesam Server or Remote Device Server (RDS) to the backup media. Storing only one instance of the data on backup media results in a reduced amount of data backed up on storage. SEP Si3 target deduplication can be easily configured by creating the Si3 deduplication data store type. For details, see Configuring Si3 Deduplication Store. Combined with SEP Si3 replication, it provides faster backup cycles and better SEP sesam performance.

Note that SEP sesam provides different replication types: the basic Si3 replication, replication based on HPE Catalyst store and HPE Cloud Bank Storage, and replication to S3 cloud storage. For more details on these types, initial replication and scheduling, see About Replication.

Prerequisites

To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

  • SEP sesam replicates data between a SEP sesam Server and an RDS or between two RDSs. Therefore, on a SEP sesam Server either two RDSs or one RDS in addition to the SEP sesam Server must be configured. For details on installing RDS, see How to configure Remote Device Server.
  • Both, SEP sesam Server and/or RDS (or more of them) must have the same SEP sesam version ≥ 4.4.3 Beefalo installed. You can configure more than one RDS, but their SEP sesam version must match the SEP sesam Server version. Check Hardware requirements for SEP sesam Server.
  • Java must be installed on RDS and on deduplication clients. For details on the required Java version, see Java Compatibility Matrix.
  • A valid replication license Si3R is required for each Si3T node (SEP sesam Server or Remote Device Server). For details, see Licenses.
  • The same amount of disk space is required for source and target data stores. Ensure that enough disk space is available for both data stores, always keeping in mind that horizontal scaling might be necessary.
  • You have to ensure sufficient amount of memory and CPU, reliable network connection and bandwidth, etc., as described in Replication Best Practices.

Configuring SEP Si3 replication

To configure SEP Si3 replication, proceed as follows.

  1. Configure Si3 deduplication store on SEP sesam server. Before you begin, check the system requirements and recommendations. Again, make sure that you have enough disk space and that your storage can be extended for the needs of deduplication.
    Information sign.png Note

    Only one Si3 deduplication store can be configured on a server. For each Si3 deduplication store a valid license is required.
    You can also use initial seed for setting up new Si3 deduplication store for the purpose of replication. For details, see Seeding Si3 Deduplication Store.

  2. Configure media pool(s) for your Si3 deduplication store. As the retention time is set on a media pool level, create media pools accordingly, 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.
  3. Add one or more RDS as ordinary SEP sesam Clients: In the Main selection -> Components -> Topology, click New Client. Make sure that you correctly specify the client's short name or FQDN in the Interfaces field (in the New Client dialog) to establish DNS connection between SEP sesam Server and SEP sesam RDS. For details, see FAQ: Which are SEP sesam default TCPIP ports and How to check DNS configuration.
  4. Now configure a remote Si3 deduplication store on each SEP sesam RDS based on the same system requirements and recommendations.
  5. Configure media pools for your remote Si3 deduplication store.
  6. Test both Si3 deduplication stores by executing a backup on each of them.
    • Create a new backup task: In the Main Selection -> Tasks -> By clients, select your RDS client and then click New Backup Task. Configure your backup task and save it. For details, see Creating a Backup Task.
    • Test the backup on the source Si3 deduplication store: From the menu bar, select Activities -> Immediate start -> Backup. In the Immediate start: Backup dialog, select the source_dedup media pool as your backup target media pool. Click Start and check if your backup performed successfully.
    • Test the backup on the target Si3 deduplication store: From the menu bar, select Activities -> Immediate start -> Backup. In the Immediate start: Backup dialog, select a target_dedup media pool as your backup target media pool. Click Start and check if your backup performed successfully.
  7. Create a replication task: In the Main selection -> Tasks -> Replication Tasks, click New Replication Task. The New Replication Task window is displayed.
  8. In the Name field, enter a meaningful name for the replication task, e.g., rep-source_mediapool-to-target_mediapool.
  9. Under the Parameters, specify the following:
    • Media pool
      • Pool: Enter the name of the source media pool from which the data will be replicated, e.g., source_mediapool.
      • Drive: Select the drive number of the drive that will be used to read the data.
      • Interface: Optionally, specify the network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS.
    • Destination
      • Pool: Enter the name of the target media pool to which the data will be replicated, e.g., target_mediapool.
      • Drive: Select the drive number of the drive that will be used to write the data.
      • Interface: Optionally, specify the network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS.
    • To define the time frame for the backups that will be replicated, select Relative backup date (recommended) and select the appropriate values for the from/to fields. These fields specify the number of days in the past that are considered for replication, meaning all data in the source media pool that was backed up within a given period of time is going to be considered for replication to the remote pool. For example, to replicate all data from the past week, the Relative backup date is set to -7 and to is set to 0. Because the replication will always replicate only new blocks of data, you can specify a really high number in the from field, such as -99.999. This way all backups since the initial replication will always be checked, but only the changed data is going to be replicated.
    • Information sign.png Note

      You cannot replicate savesets with errors. It is possible to replicate savesets with status successful, savesets with warnings (status successful or with warnings) or partially restorable savesets (containing data from cancelled backups).

    • In the drop-down list based on, the Sesam days option is selected by default. Sesam day is a backup day you define according to your backup routines. For example, your backups can run after midnight but retain the backup date of the prior day. Sesam day/backup day is defined by time set in the NEWDAY event. For details, see SEPuler: SEP sesam backup day.
    • Replications Beefalo.jpg


  10. Click Save to save your replication task.

After configuring a replication task, schedule a replication job or start the process manually.

You can check the status of your replication jobs in Main Selection -> Job state -> Migrations and Replications. For details, see Checking replication status.