Veritas InfoScale 7.3 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- Installing the Veritas InfoScale products
- About installing the InfoScale products
- About the co-existence of InfoScale products
- Installing the server components using the installation wizard
- Applying the selected installation and product options to multiple systems
- Installing the server components using the command-line installer
- Parameters for Setup.exe
- Available product options and supported DMP DSMs
- Registering the InfoScale Storage resource DLLs
- Installing the client components
- Upgrading to InfoScale products
- Performing the post upgrade tasks
- Deployment scenarios and applicable post upgrade tasks
- Re-enabling Volume Replicator in a non-clustered environment
- Re-enabling Volume Replicator in a Microsoft failover cluster environment
- Reconnecting DMP DSM paths after the upgrade
- Reconfiguring the Veritas InfoScale Messaging Service
- Importing the configured rules
- Upgrading the dynamic disk group version
- Upgrading clusters for stronger security
- Reinstalling the custom agents
- Including custom resources
- Administering the InfoScale product installation
- Uninstalling the InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Appendix A. Services and ports
- Appendix B. Migrating from a third-party multi-pathing solution to DMP
Re-enabling Volume Replicator in a non-clustered environment
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
- On the current primary site, stop the application that uses Volume Replicator to replicate data between the sites.
- From the command line, type:
vxprint -lVP [-g diskgroup_name]
This command lists the RLINK and RVG records.
- Verify that the data on the Replicator Log is written to the secondary site by running the following command on the primary:
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.
- To migrate the primary RVG perform one of the following procedures:
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.
- Perform any necessary steps to start the applications on the new primary (old secondary).