Starts the replication process on an existing replication link to a container in a QoreStor.
replication --start --name <name> --role <source | target>
Where
--name Name of container. --role Role of container.
Replication configuration updated successfully. Replication Container : container2_replica Replication Role : Source Replication Target System : acme-85 Replication Target System IP : 10.20.22.20 Replication Target Container : acme85-S2 Replication Enabled : Yes Replication Compression Enabled : Yes Replication Encryption : AES 128-bit
Stops the replication process on an existing replication link to a container in a QoreStor.
replication --stop --name <name> --role <source | target>
Where
--name Name of container. --role Role of container.
Replication configuration updated successfully. Replication Container : acme59 Replication Role : Source Replication Target System : acme-85 Replication Target System IP : 10.20.22.20 Replication Target Container : acme85-S2 Replication Enabled : No Replication Compression Enabled : Yes Replication Encryption : AES 128-bit
Limits the bandwidth used during replication by defining a bandwidth limit using any of the following settings:
|
IMPORTANT: Bandwidth rules for all ports will be deleted. New rules will be applied by QoreStor with this command. |
replication --limit --speed <<num><KBps|MBps|GBps> | default> --target <ip address | hostname> [--air]
Where
--speed Replication speed limit (eg. 10MBps). --target Replication peer IP address. --air Auto Image replication enabled.
Successfully updated replication limit for acme-60 to 10 GBps. Changing traffic control policies ... done.
Resynchronizes the replication process between a source and target container in a replication relationship on a QoreStor.
|
IMPORTANT: This command should only be used in an emergency situation with the help of Quest Support. Do not mistake this command as an ability to start a replication sync outside of the schedule window. If your intention is to start a replication outside of the window, you can either delete the schedule, or add a temporary replication window to the current schedule and delete it when the systems are in sync. |
replication --resync --name <name> --role <source | target>
Where
--name Name of container.
--role Role of container.
Successfully initiated replication resync on container dataStorage3.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center