Source:About Replication - Jaglion: Difference between revisions

From SEPsesam
(Corrected typo.)
(Updated, ready for review.)
Line 11: Line 11:
| rowspan="2" style="padding:0px 10px 0px;" |   
| rowspan="2" style="padding:0px 10px 0px;" |   
<translate>
<translate>
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:Configuring_Si3_Replication]]</translate>
[[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |   
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |   
<translate>
<translate>
See also: [[Special:MyLanguage/4_4_3_Beefalo:Configuring_Si3_Replication|Si3 Replication]] – [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]]</translate>  
See also: [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]] – [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]]</translate>  
|}
|}


Line 43: Line 43:
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Replication|documentation archive]].</translate>
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Replication|documentation archive]].</translate>
|}</div>
|}</div>
<translate>SEP sesam provides different replication methods. The '''Si3 replication''' enables you to replicate the data between SEP sesam Remote Device Servers. You can also use '''HPE Catalyst stores''', '''HPE Cloud Bank Storage''', or '''S3 cloud storage''' for replicating your data.   
<translate>SEP sesam provides different replication type. The '''SEP Si3 replication''' enables you to replicate the data between SEP sesam Remote Device Servers. You can also use '''HPE Catalyst stores''', '''HPE Cloud Bank Storage''', or '''S3 cloud storage''' for replicating your data.   


<!--T:2-->
<!--T:2-->
Line 55: Line 55:


*SEP sesam Server v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] or higher. Check [[Special:MyLanguage/Hardware_requirements|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate>
*SEP sesam Server v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] or higher. Check [[Special:MyLanguage/Hardware_requirements|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate>
<translate>* The valid license(s) are required for the replication. Depending on the replication method, you might need different licences for your systems and/or stores, i.e., ''Si3R'', ''HPE StoreOnce VSA'', ''Cloud Storage'', etc. For details, see [[Special:MyLanguage/List_of_Licenses|List of Licenses]].</translate>
<translate>* Depending on your environment (''Si3R'', ''HPE StoreOnce VSA'', ''Cloud Storage''), a proper license is required to use the replication. For details, see [[Special:MyLanguage/List_of_Licenses|List of Licenses]].</translate>
<translate><!--T:56-->
<translate><!--T:56-->
* A ''reliable network connection'' between servers. Note that NAT (Network Address Translation) infrastructure is not supported.</translate>
* A ''reliable network connection'' between servers. Note that NAT (Network Address Translation) infrastructure is not supported.</translate>
Line 61: Line 61:
* ''Bandwidth'' can affect replication performance. Test SEP sesam replication processing to determine how much workload can be managed by your network.</translate>
* ''Bandwidth'' can affect replication performance. Test SEP sesam replication processing to determine how much workload can be managed by your network.</translate>
<translate><!--T:58-->
<translate><!--T:58-->
* It is important that you ensure ''sufficient amount of memory and CPU''.</translate>
* If replicating to Si3 deduplication store, it is important that you ensure ''sufficient amount of memory and CPU''; check the [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|system requirements and recommendations]].</translate>
<translate><!--T:59-->
<translate><!--T:59-->
* 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.</translate>
* 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.</translate>
Line 68: Line 68:
{{<translate><!--T:61-->
{{<translate><!--T:61-->
note</translate>|<translate><!--T:62-->
note</translate>|<translate><!--T:62-->
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.</translate>}}
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.</translate>}}


<translate>== {{anchor|configuration}}Configuring replication ==  
<translate>== {{anchor|configuration}}Configuring replication ==  


To configure a replication, you first have to configure the data stores. Depending on the replication method, you have to select the relevant ''data store type'':</translate>  
The first step in configuring replication is to configure the data stores. Depending on the replication type, select the relevant ''data store type'':</translate>  
*<translate>'''''Si3 deduplication store''''': Enables you to replicate the data between SEP sesam Remote Device Servers ([[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]), which can also be [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]] or to S3 cloud.</translate>
*<translate>'''''Si3 deduplication store''''': Enables you to replicate the data between SEP sesam Remote Device Servers ([[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]), which can also be [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Servers]], or to S3 cloud.</translate>
*<translate>'''''HPE StoreOnce''''': Enables you to replicate the data between SEP sesam and Catalyst store, or between one Catalyst store to another.</translate>  
*<translate>'''''HPE StoreOnce''''': Enables you to replicate the data between SEP sesam backup server (SEP sesam Server or RDS) and Catalyst store, or between one Catalyst store to another.</translate>  
*<translate>'''''HPE Cloud Bank Store''''': Enables you to replicate the data between Catalyst store and Cloud Bank store.  
*<translate>'''''HPE Cloud Bank Store''''': Enables you to replicate the data between Catalyst store and Cloud Bank store.  


Afterwards, you have to create media pools, test your backups and create a replication task. You can [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#initial|start your replication manually]] or [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#scheduling|schedule a replication]].  
Afterwards, you have to create media pools, test your backups and create a replication task. You can [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#scheduling|schedule a replication job]] or [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#initial|start the process manually]].  


The replication configuration is pretty straightforward and does not differ much on the selected replication method. However, each replication method has its own requirements, e.g., specific pre-configuration steps, data store type, special licences, etc. Depending on which replication method you want to use, see [[Special:MyLanguage/4_4_3_Beefalo:Configuring_Si3_Replication|Si3 Replication]], [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] and [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]].
The replication configuration is pretty straightforward and does not differ much between the different replication types. However, each replication type has its own requirements, e.g., specific license and pre-configuration steps, data store type, etc. Depending on which replication type you want to use, refer to [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]], [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] or [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]].


=={{anchor|initial}}Initial replication == <!--T:21-->
=={{anchor|initial}}Initial replication == <!--T:21-->


An initial transfer of data will replicate all data from the source to target server, therefore it will require a bigger amount of CPU, network bandwidth and time to successfully complete. You should start initial replication manually. For all following replication cycles you can create different schedules, because after the initial replication the process will transfer only data that has changed on the source server.
An initial transfer of data will replicate all data from the source to target server, therefore it will require a bigger amount of CPU, network bandwidth and time to successfully complete. You should start initial replication manually. After the initial replication is completed, the replication process will transfer only data that has changed on the source server, therefore all following replication cycles can be scheduled to start automatically (see [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#scheduling|Scheduling replication below]]).
 
<!--T:22-->
<!--T:22-->
To start replication manually, proceed as follows:
To start replication manually, proceed as follows:
Line 90: Line 89:
<!--T:23-->
<!--T:23-->
#From the menu, select '''Activities''' -> '''Immediate start''' -> '''Migration'''.  
#From the menu, select '''Activities''' -> '''Immediate start''' -> '''Migration'''.  
#In the '''Immediate Start: Migration''' window, from the '''Task name''' drop-down list, select the replication task you want to start and click '''Start'''.  
#In the '''Immediate Start: Migration''' window, from the '''Task name''' drop-down list select the replication task you want to start and click '''Start'''.  


<!--T:24-->
<!--T:24-->
To make sure that your replication finished successfully, check its status. For details, see [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#state|Checking replication status]].
To make sure your replication is working correctly, check its status. For details, see section  [[Special:MyLanguage/4_4_3_Beefalo:About_Replication#state|Checking replication status]].


== {{anchor|scheduling}}Scheduling replication == <!--T:25-->
== {{anchor|scheduling}}Scheduling replication == <!--T:25-->
Line 118: Line 117:
From the '''Task name''' drop-down list, select the task you want to link to the schedule. Optionally, under ''Sequence control'', set up the '''Priority''' of your replication event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler - an event calendar#event_priority|Setting Event Priorities]]. You can also enable the '''Blocking date'''. This option should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the backup to be processed in case other backups are scheduled at the same time.</translate></li>
From the '''Task name''' drop-down list, select the task you want to link to the schedule. Optionally, under ''Sequence control'', set up the '''Priority''' of your replication event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEPuler - an event calendar#event_priority|Setting Event Priorities]]. You can also enable the '''Blocking date'''. This option should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the backup to be processed in case other backups are scheduled at the same time.</translate></li>
<translate>Click '''OK''' to link the event to the schedule.
<translate>Click '''OK''' to link the event to the schedule.
[[Image:Replication_event_Beefalo_V2.jpg|700px|link=]]</translate>
[[Image:Replication_event_Beefalo_V2.jpg|700px|link=]]</translate>
<br clear=all>
<br clear=all>
Line 123: Line 123:
<translate>== {{anchor|state}}Checking replication status == <!--T:31-->
<translate>== {{anchor|state}}Checking replication status == <!--T:31-->


The status of your replication jobs is logged together with the migration jobs. Go to the '''Main Selection''' -> '''Job state''' -> '''Migrations and Replications''' and check your replication task in the first column ''Migration Task''. The other columns provide details on status, start and end time, and media pools used for the task.
The status of your replication jobs is logged together with the migration jobs. Go to the '''Main Selection''' -> '''Job state''' -> '''Migrations and Replications''' and look for your replication task in the first column ''Migration Task''. The other columns provide details on status, start and end time, the amount of data being transferred, etc. For example, you may be replicating 100 GB of data (column ''Data Size''), but only 1 GB is transferred physically (column ''Transferred'') over the network as only a small amount of data is changed.
 
By default, the replication tasks are listed in the tree view. Expanding the replication task by clicking plus ('''+'''), shows the status of individual replication tasks grouped together in a hierarchical view.  


<!--T:101-->
You can view the details of a specific migration or replication task by double-clicking it (or by selecting it and clicking the ''Properties'' button). You can also check the log file for details by selecting the ''Main Log'' tab, and then send or download the log(s).  
You can also examine the progress of the replication and see how much data is being transferred; you can check data size, physical and nominal data in the columns ''Data Size'', ''Transferred'', ''Transferred (Brutto)'' and ''Progress'', respectively. For example, if you are replicating 100 GB of data, just 1 GB needs to be transferred physically over the network because this data has changed.


<!--T:32-->
<!--T:32-->
Line 140: Line 141:
<div class="noprint">
<div class="noprint">
== See also ==  
== See also ==  
[[Special:MyLanguage/4_4_3_Beefalo:Configuring_Si3_Replication|Si3 Replication]] – [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]]
[[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]] – [[Special:MyLanguage/4_4_3_Grolar:S3_Cloud_Storage_Backup|S3 Cloud Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]]
</translate>
</translate>

Revision as of 11:36, 17 January 2020

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.
Other languages:

Template:Copyright SEP AG en

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 sesam provides different replication type. The SEP Si3 replication enables you to replicate the data between SEP sesam Remote Device Servers. You can also use HPE Catalyst stores, HPE Cloud Bank Storage, or S3 cloud storage for replicating your data.

SEP sesam replication only searches for new blocks of data in the source media pool and replicates these changes to a target media pool according to a defined schedule. Replication means that only changed data blocks are sent over a network and replicated to the target server. This reduces the data transferred over the network and gives you the ability to control your network usage by scheduling replication.

To optimize replication performance, 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).

Prerequisites

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

  • SEP sesam Server v. 4.4.3 Beefalo or higher. Check Hardware requirements for SEP sesam Server or RDS.
  • Depending on your environment (Si3R, HPE StoreOnce VSA, Cloud Storage), a proper license is required to use the replication. For details, see List of Licenses.
  • A reliable network connection between servers. Note that NAT (Network Address Translation) infrastructure is not supported.
  • Bandwidth can affect replication performance. Test SEP sesam replication processing to determine how much workload can be managed by your network.
  • If replicating to Si3 deduplication store, it is important that you ensure sufficient amount of memory and CPU; check the system requirements and recommendations.
  • 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.
  • Determine the type of data that is going to be replicated. You can reduce network load by elaborate scheduling and replication scenarios.
Information sign.png 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.

Configuring replication

The first step in configuring replication is to configure the data stores. Depending on the replication type, select the relevant data store type:

  • Si3 deduplication store: Enables you to replicate the data between SEP sesam Remote Device Servers (RDS), which can also be SEP sesam Servers, or to S3 cloud.
  • HPE StoreOnce: Enables you to replicate the data between SEP sesam backup server (SEP sesam Server or RDS) and Catalyst store, or between one Catalyst store to another.
  • HPE Cloud Bank Store: Enables you to replicate the data between Catalyst store and Cloud Bank store.

Afterwards, you have to create media pools, test your backups and create a replication task. You can schedule a replication job or start the process manually.

The replication configuration is pretty straightforward and does not differ much between the different replication types. However, each replication type has its own requirements, e.g., specific license and pre-configuration steps, data store type, etc. Depending on which replication type you want to use, refer to SEP Si3 Replication, S3 Cloud Replication or HPE StoreOnce Replication.

Initial replication

An initial transfer of data will replicate all data from the source to target server, therefore it will require a bigger amount of CPU, network bandwidth and time to successfully complete. You should start initial replication manually. After the initial replication is completed, the replication process will transfer only data that has changed on the source server, therefore all following replication cycles can be scheduled to start automatically (see Scheduling replication below). To start replication manually, proceed as follows:

  1. From the menu, select Activities -> Immediate start -> Migration.
  2. In the Immediate Start: Migration window, from the Task name drop-down list select the replication task you want to start and click Start.

To make sure your replication is working correctly, check its status. For details, see section Checking replication status.

Scheduling replication

You can add your replication task to one or more schedules to automate your replication.

  1. From Main Selection -> Scheduling -> Schedules, click New Schedule. The New Schedule window appears.
  2. Scheduling replication Beefalo V2.jpg
  3. Configure your schedule and click OK. For details, see Creating a schedule.
  4. Right-click the schedule you have just created and select New Replication Event. The New Replication Event window opens.
  5. From the Task name drop-down list, select the task you want to link to the schedule. Optionally, under Sequence control, set up the Priority of your replication event. SEPuler always executes the schedules with higher priority first. Default priority level is 1, which is the lowest priority (the highest is 99). The only exception are the schedules with priority 0, which override all other priorities and are always executed. For details, see Setting Event Priorities. You can also enable the Blocking date. This option should be used together with high priority for special events. If checked, the blocking event will block events of the same type of a lower priority, ensuring the backup to be processed in case other backups are scheduled at the same time.
  6. Click OK to link the event to the schedule. Replication event Beefalo V2.jpg

Checking replication status

The status of your replication jobs is logged together with the migration jobs. Go to the Main Selection -> Job state -> Migrations and Replications and look for your replication task in the first column Migration Task. The other columns provide details on status, start and end time, the amount of data being transferred, etc. For example, you may be replicating 100 GB of data (column Data Size), but only 1 GB is transferred physically (column Transferred) over the network as only a small amount of data is changed.

By default, the replication tasks are listed in the tree view. Expanding the replication task by clicking plus (+), shows the status of individual replication tasks grouped together in a hierarchical view.

You can view the details of a specific migration or replication task by double-clicking it (or by selecting it and clicking the Properties button). You can also check the log file for details by selecting the Main Log tab, and then send or download the log(s).

Migrations by state Beefalo.jpg

Information sign.png Note

If the replication is scheduled, but there is nothing to replicate because the data has not changed since the last run, the displayed status in the column State is successful with remark no savesets found.

As of 4.4.3 Beefalo V2, you can also monitor your replications online by using new Web UI. For details, see SEP sesam Web UI.