Configuring systems and IBM Spectrum Virtualize 3-Site Orchestrator for HyperSwap configurations
To set up 3-site replication with a HyperSwap® configuration, ensure that IBM Spectrum Virtualize 3-Site Orchestrator and all systems within the configuration meet specific requirements and that all configuration tasks are completed. After you complete these tasks, you can convert existing HyperSwap consistency groups or add existing HyperSwap relationships to the configuration.
The IBM Spectrum Virtualize 3-Site Orchestrator is a separate command-line based application that is hosted on a separate Linux® virtual machine or server. The 3-Site Orchestrator coordinates replication between three systems that are defined in partnerships and responds automatically during outages and connection issues with limited intervention by administrators.
- Each system in the configuration has a unique name.
- All planning steps are complete. For more information, see Planning for IBM Spectrum Virtualize 3-Site Orchestrator.
- Ensure that you install the correct installation package for HyperSwap configurations. For more information, see Installing IBM Spectrum Virtualize 3-Site Orchestrator.
- As part of the configuration, you must configure a HyperSwap system topology on your system before you set up the IBM Spectrum Virtualize 3-Site Orchestrator. For more information about configuring HyperSwap and any prerequisites, see HyperSwap system configuration details.
To configure HyperSwap configurations that span three sites, the management GUI supports setting up IBM Spectrum Virtualize 3-Site Orchestrator and the necessary system objects. Before you configure the systems and the 3-Site Orchestrator, ensure that a HyperSwap topology is configured at the near-sites. The management GUI guides you through each necessary task and provides simplified management of 3-site configuration objects with detailed status graphics both for synchronous and asynchronous copy operations.
- Remove the existing configuration by running the following
command.
rm3siteconfig
This command removes the configuration object on the host, but does not remove related objects, such as partnerships, on the system.Note: You cannot use the rm3siteconfig command if the standby orchestrator is configured on 3-site orchestrator. - To ensure that the management GUI can access 3-Site
Orchestrator objects, add the public SSH key to the authorized keys by entering the following
command on the 3-Site Orchestrator
host.
ssh-copy-id -i ~/.ssh/<id_rsa.pub> root@<ORCH-HOST>
- Enter the following command:
where x.xxx.xxx.xx represents the management IP addresses the HyperSwap system at the near sites and the system at the Auxiliary Far site. The -keyfile value is the file path where the SSH private key is on the Orchestrator host. The -username value specifies the name of the user that has 3-Site Orchestrator administrator privileges. The value in the -port parameter is the starting address of the two port numbers, one for the HyperSwap system that is split between the master and auxiliary-near sites, and the second for the auxiliary-far site. For example, if 6000 is set as -port, then the master port and the auxiliary-near port (master_port and auxnear_port) is set at 6000 and the auxiliary-far port (auxfar_port) is set at 6001.[root@ORCH-HOST ~]# mk3siteconfig -ip1 x.xxx.xxx.xx,x.xxx.xxx.xx -keyfile / 'root/.ssh/id_rsa' -username tsuser -port 6000 -topology hyperswap
Note: The mk3siteconfig command generates a tar file at location /opt/ibm/SpectrumVirtualize/rc3site/config.tar. - Log in to the management GUI, select Refresh under Refresh GUI cache. and select
- After the cache is refreshed, select . Verify that the 3-site partnership displays.
- Select .
- Under Partnerships, select .
- On the Create 3-Site Partnership page, complete each of the following tasks.