4 4 3 Beefalo:Replication Tasks

From SEPsesam
Revision as of 08:57, 10 June 2019 by Sta (talk | contribs)
Other languages:
<<<Back
Migration Tasks
User Manual
Next>>>
Tasks as List


Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.


Replication tasks (Si3)

Replication tasks are managed under Main selection -> Tasks -> Replication Tasks (previously Si3 Replications). For detailed explanation on how to configure replication, its advantages and limitations, see Replication.

Replications Beefalo.jpg
When configuring a replication task, you can set the following options:

  • Name: Enter a meaningful name for the replication task, e.g., rep-source_mediapool-to-target_mediapool.
  • Media pool: Specification of the source 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. By selecting the source media pool, the drive number is set automatically, however, you can select another drive from the drop-down list (mandatory field).
    • 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: Specification of the target for the replication.
    • Pool: Enter the name of the target media pool to which the data will be replicated, e.g., target_mediapool.
    • Information sign.png Note

      With v. 4.4.2, the EOL (end-of-life) of the target media pool will be ignored. If a saveset is deleted from the source media pool, it will also be deleted from the target media pool. It is recommended to upgrade to the latest version, which solves this issue.

    • Drive: Select the drive number of the drive that will be used to read the data (mandatory field).
    • Interface: Optionally, specify the network interface of the RDS through which the data transfer will be executed, e.g., the name of the RDS.
  • Backup date: The time frame of the backups that will be replicated is defined.
    • Date: Define the time frame of the backups that will be replicated. It is recommended that you use the option Relative backup date instead.
    • Relative backup date: Define the time frame of the backups that will be replicated by specifying 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 while 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

      Only the savesets with status successful and with warnings are selected for replication, while savesets with errors and only partially restorable savesets (containing data from cancelled backups) are not replicated.

    • 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 NEWDAY Event.
  • Note: Optionally, add additional information about the replication.

After you have configured your replication task, click Save or Cancel.

See also

Replication


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.