This section describes how to install the latest service packs for SQL Server 2012 or SQL Server 2014 in a InfoScale disaster recovery environment.
Consider the following points before you proceed with the upgrade:
Ensure that you have installed and configured SQL Server in an InfoScale environment.
Ensure that the logged on user has administrative privileges to the SQL instance that you want to upgrade.
Ensure that you have taken a recent backup of your system, user databases, and the SQL Server directories, from the shared storage.
Refer to the Microsoft documentation for prerequisites related to SQL Server Service Pack installation.
Consider a three-node disaster recovery cluster setup; Node A, Node B and Node C. Node A and Node B are on the primary site while Node C is on the secondary site. The SQL service group is online on Node A.
The upgrade involves upgrading SQL Server on all the nodes at the primary site first and then on the nodes at the secondary site. Veritas recommends that you perform the upgrade in the specified order, one node at a time.
To upgrade SQL Server to a service pack, perform the following steps:
If using Volume Replicator for replication, from the VEA Console right-click the Secondary RVG and select Stop Replication from the menu that appears.
Using the VCS Cluster Manager (Java Console), on the Service Groups tab, right-click the resource and then click Offline.
Take the RegRep resource offline.
On the Service Groups tab, right-click the RegRep resource and then click Offline from the menu that appears. Click Yes in the confirmation pop-up box to take the RegRep resource offline.
Disable the RegRep resource.
On the Service Groups tab, right-click the RegRep resource and then click Disabled from the menu that appears.
Except the storage resources (MountV and VMDg) take all the resources offline.
Freeze the service group.
On the Service Groups tab, right-click the service group and then click Freeze > Persistent.
The SQL Server data files available on the shared storage are upgraded during the SQL upgrade on Node A. Before you begin to upgrade SQL on Node B, you must rename the folders containing the upgraded SQL data files and restore the initially backed up SQL Server directories. If you do not restore the initially backed up SQL Server directories, then the SQL upgrade on Node B may fail indicating that the SQL Server data files are already upgraded.
From the Cluster Manager (Java Console), on the Service Groups tab, right-click the service group and then click Switch To > Remote Switch.
Except the storage resources (MountV and VMDg) take all the resources offline.
Disable the RegRep resource and freeze the service group.
Rename the SQL folders from the shared storage and copy the backed up directories to the shared storage.
Install Microsoft SQL Server Service Pack.
Verify if a FILESTREAM share exists on the node and then delete it using the following command:
net share share_name /delete
Unfreeze the service group and enable the RegRep resource.
This completes the SQL Server upgrade.