Troubleshoots the replication connections between a source and target container on a QoreStor.
|
NOTE: This command only reports 9915 and 9916 as succeeding against a replication peer that has native Qorestor or 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. |
replication --troubleshoot --peer <ip address | hostname>
Where
--peer IP address or name of remote machine to troubleshoot.
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)
Displays the list of all replication-related options that can be used as a reference when using the QoreStor CLI.
replication --help
Usage: replication --show [-air] [--name <name>] [--role <source | target>] [--verbose] [--limits] 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 | aes128 | aes256>] [--username <user name>] [-air] replication --update --name <name> --role <source | target> [--peer <ip address | hostname>] [--replication_traffic <ip address | hostname>] [--encryption <none | aes128 | aes256>] [--username <user 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> [-air] 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 Delete existing bandwidth rules for all ports and set new throttling limits. --resync Initiates a replication re-sync. --troubleshoot Troubleshoots replication connection. For command-specific help, please type replication --help <command> eg: replication --help show
The QoreStor 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 QoreStor CLI seed commands support the following operations:
|
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:
|
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center