Managing replication with IBM Spectrum Virtualize 3-Site Orchestrator
To update a 3-site consistency group, add a relationship to a 3-site consistency group,
or to recover from a link failure or site disaster, use the information in the topics that
follow.
Changing configuration settings in the IBM Spectrum Virtualize 3-Site Orchestrator
You can modify the IP addresses, the SSH key file, or other configuration values in the IBM Spectrum Virtualize 3-Site Orchestrator .
Converting a Metro Mirror consistency group to a 3-site consistency group
Before you convert an in-production 2-site Metro Mirror consistency group to a 3-site consistency group, verify the state of the consistency group.
Adding a Metro Mirror relationship to an existing 3-site consistency group
To add a 2-site Metro Mirror relationship to an existing 3-site consistency group, you create an empty volume. If you are using Orchestrator 3.0, you must create empty volumes before you can adding a 2-site Metro Mirror relationship to a 3-site consistency group. Orchestrator 4.0 supports the ability to add a 2-site remote-copy relationship with data to a stopped 3-site consistency group.
Adding a Metro Mirror relationship with data to a 3-site consistency group
If you are using Orchestrator 4.0, you can add a remote-copy relationship with data to a stopped 3-site consistency group.
Converting a HyperSwap consistency group to a 3-site consistency group
Before you convert an in-production 2-site HyperSwap® consistency group to a 3-site consistency group, verify the state of the consistency group.
Adding a HyperSwap relationship to an existing 3-site consistency group
You can add existing HyperSwap relationships that are configured between the near sites to an existing 3-site consistency group. If you are using Orchestrator 3.0, The HyperSwap relationship must be empty and cannot contain volumes with active data. HyperSwap relationships must be in the consistent synchronized state before they can be added to a 3-site consistency group.
Adding a HyperSwap relationship with data to 3-site consistency group
If you are using Orchestrator 4.0, you can add a HyperSwap relationship with data to a stopped 3-site consistency group.
Reverting a 3-site consistency group to a 2-site consistency group
You can take an existing 3-site consistency group and convert it to a 2-site consistency group for both Metro Mirror or HyperSwap configurations.
Removing and reverting relationship from 3-site consistency group
If you are using Orchestrator 4.0, you can take an existing 3-site consistency group and remove 3-site relationships for both Metro Mirror or HyperSwap configurations and revert them to stand-alone 2-site relationships. However, data that is replicated on the volumes on the system at auxiliary-far site is not deleted.
Migrating or reinstalling IBM Spectrum Virtualize 3-Site Orchestrator
3-Site Orchestrator migration might be necessary if the host system fails and cannot be recovered, or if it becomes necessary to migrate the 3-Site Orchestrator instance to another host.
Updating IBM Spectrum Virtualize 3-Site Orchestrator installation package
You can upgrade the currently installed version of the IBM Spectrum Virtualize 3-Site Orchestrator to newer version of the 3-Site Orchestrator.
Rolling back IBM Spectrum Virtualize 3-Site Orchestrator installation package
You can go from higher version of the IBM Spectrum Virtualize 3-Site Orchestrator installation package to an earlier version. For example, if you need to roll back your system software to an earlier version, you can move to an earlier version of the installation package, if necessary.
Changing the cycle period
You can change the cycle period of a 3-site consistency group. A cycle period is the minimum time, in seconds, between copy cycles in a 3-site consistency group.
Changing the periodic source
You can change the periodic or asynchronous source only in the 3site_consistent
, 3site_inconsistent
, and stopped
states.
Changing the primary site
Verify that the current primary site is in the stopped
state before you change the primary site in a 3-site consistency group.
Stopping replication on an auxiliary-far site for maintenance
Before you can complete maintenance on a system at the auxiliary-far site in a 3-site configuration, you must stop replication. After the maintenance tasks are complete, you can restart replication in the 3-site configuration.
Stopping replication on a HyperSwap topology system or an auxiliary-far site for maintenance
Before you can complete maintenance on a HyperSwap system or the system at the auxiliary-far site in a 3-site configuration, you must stop replication. After the maintenance tasks are complete, you can restart replication in the 3-site configuration.
Excluding a near site for maintenance
If the system at the near site needs maintenance or an update of system software, you must exclude that site from the 3-site consistency group. After you complete the maintenance, you can join the system at that site back into the 3-site configuration.
Updating the system software in a Metro Mirror 3-site configuration
If you are updating the IBM Spectrum Virtualize software on any of the systems in a 3-site configuration that uses Metro Mirror, you must complete several tasks in IBM Spectrum Virtualize 3-Site Orchestrator before and after you update the software.
Updating the system software in a Metro Mirror 3-site configuration with clustered systems
Depending on which systems you are updating the software on in your configuration, different steps can be necessary.
Upgrading the system software in a HyperSwap 3-site configuration
If you are updating the IBM Spectrum Virtualize software on any of the systems in a 3-site configuration that uses HyperSwap and systems, you must complete several tasks in IBM Spectrum Virtualize 3-Site Orchestrator before and after you update the software.
Maintaining the hardware on a HyperSwap 3-site configuration with clustered systems
When you are maintaining the hardware on any of the systems in a 3-site configuration that uses HyperSwap, you must complete several tasks in IBM Spectrum Virtualize 3-Site Orchestrator .
Managing replication with Metro Mirror configurations
To update a 3-site consistency group, add a relationship to a 3-site consistency group, or to recover from a link failure or site disaster, use the information in the topics that follow.
Managing replication with HyperSwap configurations
To update a 3-site consistency group, add a relationship to a 3-site consistency group, or to recover from a link failure or site disaster, use the information in the topics that follow.
Changing configuration settings in the IBM Spectrum Virtualize 3-Site Orchestrator
You can modify the IP addresses, the SSH key file, or other configuration values in the IBM Spectrum Virtualize 3-Site Orchestrator .
Reverting a 3-site consistency group to a 2-site consistency group
You can take an existing 3-site consistency group and convert it to a 2-site consistency group for both Metro Mirror or HyperSwap configurations.
Updating IBM Spectrum Virtualize 3-Site Orchestrator installation package
You can upgrade the currently installed version of the IBM Spectrum Virtualize 3-Site Orchestrator to newer version of the 3-Site Orchestrator.
Managing replication with HyperSwap configurations
To update a 3-site consistency group, add a relationship to a 3-site consistency group, or to recover from a link failure or site disaster, use the information in the topics that follow.