Adds a new replication link to a container on the QoreStor, for which you need to define its name, role, peer IP address/hostname , peer name, peer group name, user name on the peer system, and encryption level to apply. The peer group name is the name of the remote container’s group to replicate to/from, and this parameter is applicable only if a remote container is not present.
There are three options for encryption:
If the username is a domain login (for example, domain\username), ensure that '\' characters and spaces are either escaped or in quotes.
|
NOTE: Make sure that the data container you intend to replicate already exists. If it does not, the following error message displays: Error: Container <container_name> does not exist. |
replication --add --name <name> --role <source | target> --peer <ip address | hostname> [--peer_name <name>] [--peer_group_name <name>] [--replication_traffic <ip address | hostname>] [--encryption <none || aes256>] [--username <user name>]
Where
--name Name of container to replicate. --role Role of container. --peer Peer appliance IP address/name of replication network interface(s). --peer_name Name of remote container to/from replicate. --peer_group_name Name of remote container's group to/from replicate. Only applicable if remote container is not present --replication_traffic IP address/name of local dedicated replication network interface(s). --encryption Type of encryption to use on the wire. --username Username on peer system.
Enter password foradministrator@10.250.240.192: Replication entry created successfully. Replication Container : backup Replication Role : Source Replication Target : 10.250.240.192 Replication Target IP : 10.250.240.192 Replication Target Mgmt Name : 10.250.240.192 Replication Target Mgmt IP : 10.250.240.192 Replication Local Data Name : QS2K-01 Replication Local Data IP : 10.250.208.232 Replication Target Container : backup Replication Enabled : Yes Replication Compression Enabled: Yes Replication Encryption : AES 128-bit
|
NOTE: To verify that you have successful added a replication link to the QoreStor (or to view the current status of existing containers), see replication --show. |
Updates an existing replication link to a container in a QoreStor and allows you to change the corresponding role, peer IP address or host name, the encryption being used, and user name based on the QoreStor CLI command options you specify.
replication --update --name <name> --role <source | target> [--peer <ip address | hostname>] [--replication_traffic <ip address | hostname>] [--encryption <none || aes256>] [--username <user name>]
Where
--name Name of the replication container to update. --role Current replication role of container. --peer Peer appliance IP address/name of replication network interface. --replication_traffic IP address/name of dedicated replication network interface. --encryption Type of encryption to use on the wire. --username Username on peer system.
|
NOTE: If you attempt to update a container that already has replication enabled, this displays the following message: Replication on backup is enabled and cannot be updated, please stop it first. |
When replication is enabled on the container, you must first disable it before you can update it. To disable replication on a container, enter the QoreStor CLI replication --stop command and define the container name and role:
replication --stop --name <name> --role <source | target>
|
NOTE: For more information about disabling replication, see replication --stop --name <name> --role <source | target>. |
Disables replication on a container:
replication --stop --name backup --role source Replication configuration updated successfully. Replication Container : backup Replication Role : Source Replication Target System : acme-85 Replication Target System IP : 10.25.192.5 Replication Target Container : acme85-S2 Replication Enabled : No Replication Compression Enabled : Yes Replication Encryption : AES 128-bit
Deletes an existing replication link to a container in a QoreStor.
|
NOTE: It is recommended that the replication be in an INSYNC state for this operation. If replication is not in an INSYNC state, this operation can potentially take a much longer time to execute. |
replication --delete --name <name> --role <source | target> [--force]
Where
--name Name of container. --role Role of container. --force Delete configuration even if peer container is unreachable. Replication must be stopped first even with force option.
If you attempt to delete a container that already has replication enabled, this displays the following message:
Replication on acme-59-replica is enabled and cannot be deleted, please stop it first.
|
NOTE: If the replication state of the link is enabled, you must use the replication --stop command to disable replication before you can delete the replication link. For more information, see replication --stop --name <name> --role <source | target>. |
Deletes the existing replication link to a container.
replication --delete --name acme-59-replica --role source
Successfully deleted replication entry.
|
NOTE: The QoreStor CLI --force command is optional, and this command allows you to force the deletion of an existing replication link (such as when communications between the source and target are not working). Before using the --force option, replication must be stopped with the replication --stop command. For more information, see replication --stop --name <name> --role <source | target> |
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
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center