Chat now with support
Chat with Support

QoreStor 6.0.0 - Command Line Reference Guide

Introduction to the QoreStor Command Line Reference Guide Introducing QoreStor Managing QoreStor
Alerts Commands Authenticate Commands Email_alerts Commands OST RDA Sc_manager command Stats Storage Group commands System User
Managing QoreStor Storage Operations
Cloud_tier Connection Container iSCSI NDMP Performance_tier Replication Seed Schedule VTL
Maintaining QoreStor About us

replication --stop --name <name> --role <source | target>

Description

Stops the replication process on an existing replication link to a container in a QoreStor.

Syntax

replication --stop --name <name> --role <source | target>

Where

--name   Name of container.
--role   Role of container.

Result

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

replication --limit --speed <<num><KBps | MBps | GBps> | default> --target <ip address | hostname>

Description

Limits the bandwidth used during replication by defining a bandwidth limit using any of the following settings:

  • Kilobytes/second (KBps)
  • Megabytes/second (MBps)
  • Gigabytes/second (GBps)
  • Unlimited bandwidth (this is the default setting); minimum allowed bandwidth setting is 192 KBps

IMPORTANT: Bandwidth rules for all ports will be deleted. New rules will be applied by QoreStor with this command.

Syntax

replication --limit --speed <<num><KBps|MBps|GBps> | default> --target <ip address | hostname>

Where

--speed    Replication speed limit (eg. 10MBps).
--target   Replication peer IP address.

Result

Successfully updated replication limit for acme-60 to 10 GBps.
Changing traffic control policies ... done.

replication --resync --name <name> --role <source | target>

Description

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.

Syntax

replication --resync --name <name> --role <source | target>

Where

--name   Name of container.
--role   Role of container.

Result

Successfully initiated replication resync on container dataStorage3.

replication --troubleshoot --peer <ip address | hostname>

Description

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.

Syntax

replication --troubleshoot --peer <ip address | hostname>

Where

--peer   IP address or name of remote machine to troubleshoot.

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)
Related Documents