QoreStor supports replication seeding, which provides the ability to create a local seed and place it in a remote system. The seed backup is a process on the source QoreStor system, which collects all of the unique data chunks from the containers and stores them on the target device. This is helpful if you have a new replication target to set up, the amount of data to be replicated is very large, and the network bandwidth is low.
You can seed the target replica with the source data saved on a third party device, for example, a CIFS-mounted share, attach it to the target QoreStor and then get the data into the target QoreStor. Once the seeding is complete, replication is enabled between source and target and replication re-synchronization is done to complete any pending data transfers. Thereby, continuous replication can be done, which reduces network traffic significantly, and data can be replicated and synced with the target in a short amount of time.
|
NOTE: The following scenarios are not supported for seeding:
|
You can initiate seeding using the QoreStor command line interface (CLI), and the data to be seeded is gathered in an organized manner and stored in the target devices. Refer to the QoreStor Command Line Reference Guide for more information about replication seeding support.
In the QoreStor GUI, the Replication page displays current information about replication relationships for data containers in your QoreStor system.
To view replication information
Using the or toggle in the upper-right corner of the Replications pane, you may switch between tile and grid views.
The information below is displayed:
|
NOTE: These statistics refresh every 30 seconds. |
To add a new replication relationship, complete the following steps.
NOTE: The credentials used need to be either the admin or administrator account. |
|
NOTE: For information about starting and stopping replication, see the topic, Starting and stopping replication. For information about scheduling system operations such as replication, see Understanding system operation scheduling. |
By default, replication of any newly written files in the replicated container will occur when QoreStor detects three (3) minutes of idle time. If you wish to constrain replication activities to a specific schedule, you can configure replication schedules on a weekly basis for individual replication-enabled source containers.
|
NOTE: It is recommended that you do not schedule the running of any Replication operations during the same time period when Cleaner or data ingest operations will be running. If you do not follow this recommendation, the time required to complete the system operations or system performance might be affected. |
To configure replication schedules using the UI:
The Replications page is displayed, listing all configured replication relationships.
To configure replication schedules, complete the following steps.
schedule --add --day <Day of the Week> --start_time <HH:MM> --stop_time <HH:MM> --name --replication schedule --delete --day <Day of the Week> --name --replication
For full details on running the cleaner schedule commands, help is available by entering:
schedule --help
You can view replication details and status on the Replications page in the QoreStor GUI by selecting a replication and clicking to expand and view details.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center