Veritas InfoScale 7.0 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- Installing the Infoscale products
- About installing Veritas InfoScale products
- About InfoScale products co-existence
- Installing the server components using the product installer
- Installing the server components using CLI
- Available product options and supported DMPW DSMs
- Registering 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 Windows Server Failover Cluster environment
- Reconnecting DMPW DSM paths after the upgrade
- Re-configuring the Veritas Scheduler Service
- Re-configuring the VxSAS service
- Importing the configured rules
- Upgrading the dynamic disk group version
- Reinstalling the custom agents
- Including custom resources
- 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
- Preupgrade tasks for upgrading SQL Server 2008 to SQL Server 2008 R2 in a disaster recovery environment
- Upgrading SQL Server 2008 to SQL Server 2008 R2 on the first cluster node
- Upgrading SQL Server 2008 to SQL Server 2008 R2 on additional failover nodes
- Modifying the SQL Server 2008 service group configuration
- Deleting the SQL Server 2008 service group and creating the SQL Server 2008 R2 service group
- 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
Preupgrade tasks for upgrading SQL Server 2008 to SQL Server 2008 R2 in a disaster recovery environment
Before you proceed to upgrade the cluster nodes in a disaster recovery (DR) configuration, perform the following tasks on the secondary site for the SQL Server instances that you want to upgrade:
Freeze the service group using the VCS Cluster Manager (Java Console).
Obtain the drive letter on which the system database and the analysis service reside using the following command:
hadiscover -discover SQLServer2008 StartUpParams:InstanceName
The following is a sample output:
<Discovery> <Attr_Name> StartUpParams:INSTANCE2K8 </Attr_Name> <Discover_value> <Scalar_value> SQLDataPath: E:\Program Files\Microsoft SQL Server\ MSSQL10.INSTANCE2K8\MSSQL\DATA\ </Scalar_value> </Discover_value> <Discover_value> <Scalar_value> SQLErrLogPath: E:\Program Files\Microsoft SQL Server\ MSSQL10.INSTANCE2K8\MSSQL\LOG\ERRORLOG </Scalar_value> </Discover_value> <Discover_value> <Scalar_value> OLAPDataPath: E:\Program Files\Microsoft SQL Server\ MSAS10.INSTANCE2K8\OLAP\Data </Scalar_value> </Discover_value> </Discovery>
Attach a temporary disk and create a volume with the drive letter same as that for the instance on which the system database resides.
Note:
If you are upgrading more than one SQL Server instance that have the system database path and the OLAP data path on separate volumes, you must complete the upgrade of each instance on both the sites and then proceed to upgrade the next instance.
Review the
SQLDataPath,SQLErrLogPathand theOLAPDataPathdirectories and create the same directories on the temporary disk.Note:
In case the directory path exists on different volumes, create the similar volumes first and then create the required directory paths.
Copy the following files from the primary site to the data path that you created on the secondary site:
master.mdf
mastlog.ldf
model.mdf
modellog.ldf
MSDBData.mdf
MSDBLog.ldf
tempdb.mdf
templog.ldf