Veritas InfoScale 7.0 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- Installing the Infoscale products
- Installing the server components using the product installer
- Installing the server components using CLI
- Upgrading to InfoScale products
- Performing the post upgrade tasks
- Administering InfoScale product installation
- Uninstalling InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading SQL Server 2008 to SQL Server 2008 R2
- Upgrading to later versions of SQL Server
- Upgrading SQL Server 2008 to SQL Server 2008 R2
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Upgrading Microsoft SQL Server
- Appendix A. Services and ports
- Appendix B. Migrating from 3rd party multi-pathing solution to Dynamic Multi-pathing
General preparations
Perform the following general pre-upgrade checks or tasks on all the systems:
The following table lists the general pre-upgrade checks.
Table: General pre-upgrade checks
Tasks | Applicable for | |||
---|---|---|---|---|
InfoScale Foundation | InfoScale Availability | InfoScale Storage | InfoScale Enterprise | |
Back up configuration and application data | ✓ | ✓ | ✓ | ✓ |
Review licensing details | ✓ | ✓ | ✓ | ✓ |
Review the installation requirements and perform the required pre-installation tasks | ✓ | ✓ | ✓ | ✓ |
Ensure there are no parallel scheduled snapshots in progress | ✓ | ✓ | ✓ | ✓ |
Verify that the systems in your environment meet the requirements to upgrade the cluster. Run the Windows Data Collector that is available on the SORT website to perform these checks. | ✓ | ✓ | ✓ | ✓ |
Ensure that there are no parallel installations, live updates, or Microsoft Windows updates in progress | ✓ | ✓ | ✓ | ✓ |
If the systems have NetBackup version 6.0 or 6.5 installed and running, then shut down the OpsCenterServer service. Both, NetBackup and InfoScale products share the same AT broker and client. | ✓ | ✓ | ✓ | ✓ |
Save and close the cluster configuration. This operation saves the latest configuration to disk and changes the configuration state to read-only mode To save the cluster configuration, perform one of the following tasks:
| X | ✓ | X | ✓ |
Take the backup of custom agent binaries During the product upgrade, a backup of the main.cf and other configuration files is taken. However, it does not take the backup of any agent binaries. During the upgrade, the contents of %VCS_home% folder are removed. As a result, all the binaries of all the enterprise agents and custom agents that were installed are removed. After the upgrade is complete, all the binaries of enterprise agents are installed again. However, the binaries of a custom agent are not installed again. The main.cf that is restored after the upgrade shows that the custom agent resources are configured. However, the binaries are not present in the %VCS_home% folder. You must manually install the custom agents after the upgrade is complete. | X | ✓ | X | ✓ |
To perform parallel upgrade, take the service groups offline To take the service groups offline
| X | ✓ | X | ✓ |
Close client applications If you are running any of the following client applications on the systems where you plan to upgrade the product, stop and exit all the application instances.
| ✓ | ✓ | ✓ | ✓ |
Export the configured rules If you have configured any rules for event notification messages and actions, you must export them into XML format before you begin with the upgrade. To export the configured rules
| ✓ | X | ✓ | ✓ |