Description
Resynchronizes the replication process between a source and target container in a replication relationship on a DR Series system. This command should only be used in an emergency situation with the help of Technical 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.
Syntax
replication --resync --name dataStorage3 --role source
Result
Successfully initiated replication resync on container dataStorage3.
Description
Troubleshoots the replication connections between a source and target container on a DR Series system.
|
|
NOTE: This command only reports 9915 and 9916 as succeeding against a replication peer that has native DR Series replication configured to another system. If the peer is not currently using any replication ports, 9915 and 9916 will report as connection refused (by the DR Series system). |
Syntax
replication --troubleshoot --peer 10.25.19.5
Result
The following examples shows both successful and unsuccessful replication connection attempts:
Testing connection to port 9904... Connected!
Testing connection to port 9911... Connected!
Testing connection to port 9915... Connected!
Testing connection to port 9916... Connected!
Replication troubleshooting completed successfully - Connection to all ports is OK!
replication --troubleshoot --peer acme-205
Testing connection to port 9904... Connected!
Testing connection to port 9911... Connected!
Testing connection to port 9915...
Unable to connect to socket - Connection refused
Could not connect to acme-205 on port 9915 - (Connection refused)
Testing connection to port 9916...
Unable to connect to socket - Connection refused
Could not connect to acme-205 on port 9916 - (Connection refused)
Description
Displays the list of all replication-related options that can be used as a reference when using the DR4000 system CLI.
Result
Usage:
replication --show [--name <name>]
[--role <source | target>]
[--verbose]
[--limits]
replication --add --name <name>]
--role <source | target>
--peer <ip address | hostname>
[--peer_name <name>]
[--username <user name>]
[--encryption <none | aes128 | aes256>]
replication --update --name <name>
--role <source | target>
[--peer <ip address | hostname>]
[--encryption <none | aes128 | aes256>]
[--username <name>]
replication --delete --name <name>
--role <source | target>
[--force]
replication --start --name <name>
--role <source | target
replication --stop --name <name>
--role <source | target
replication --limit --speed <<num><kbps | mbps | gbps | default>
--target <ip address | hostname>
replication --resync --name <name>
--role <source | target>
replication --troubleshoot --peer <ip address | hostname>
replication --help
replication <command> <command-arguments>
<command> can be one of:
--show Displays command specific information.
--add Adds a replication link to a container.
--update Updates a replication link to a container.
--delete Deletes a replication link from a container.
--start Starts replication.
--stop Stops replication.
--limit Limits bandwidth consumed by replication.
--resync Initiates a replication re-sync.
--troubleshoot Troubleshoots replication connection.
For command-specific help, please type replication --help <command>
For example:
replication --help show
The DR Series system seed operations allow for exporting data on the source to a portable seed device to then import the seed data to a primary target, and, if required, a secondary target as well. Replication seeding is an alternative to using network bandwidth for the initial re-synchronization of the source and target(s). After the target(s) are seeded, continuous replication can be started, which will keep the target(s) up to date by sending only unique data.
The DR Series CLI seed commands support the following operations:
- Create a job to perform seeding export or import.
- Delete an existing seeding export or import job.
- Specify containers for seeding export.
- Add a device to be used for seeding.
- Remove a device which is already added for seeding.
- Start seeding process (export/import).
- Stop running seeding process (export/import).
- Start cleaner to process seed ZL logs on target.
|
|
NOTE: The seeding device must be a CIFS share: a USB device connected to a Windows or Linux system and shared for import as a CIFS-mounted folder. |
|
|
NOTE: The following scenarios are not supported for seeding:
- Import AND export from one share/device cannot occur at the same time.
- Import from one share/device cannot be completed from multiple locations at the same time.
- Export to a mount point can be completed only from one seed job. Multiple seed export jobs cannot send data to a single mount point.
|
See the white paper, Seeding from a DR Series System to an External Device using CLI, at support.quest.com/DR-Series for more information.
