After upgrading in a non-clustered environment where Volume Replicator replicates data from a primary site to a secondary site, you must re-enable Volume Replicator.
In the procedure for preparing the primary site for upgrade, you migrated the primary role to the secondary site.
After both the primary and secondary sites have been upgraded, you may want to migrate the role of the primary back to the original primary site. To do this, you perform a migrate operation again as described in the following procedure.
To migrate the applications back to the original primary
vxprint -lVP [-g diskgroup_name]
This command lists the RLINK and RVG records.
vxrlink [-g diskgroup_name] status rlink_to_secondary
This command displays the replication status of the secondary represented by the specified RLINK.
Verify that the data volumes on the secondary site are consistent and up-to-date with the primary before proceeding to the next step.
From the VEA, right-click the primary RVG and select the Migrate option. Select the required secondary host from the Secondary Name option list. Click OK to migrate the primary role to the secondary.
The primary and secondary roles will be interchanged.
From the command line, type:
vxrds [-g diskgroup_name] migrate local_rvg new_primary_hostname
Where the secondary host is specified by the new_primary_hostname parameter.