Interactive Upgrade - CommServe - Clustered Environment

Non Cluster

Cluster

Overview

Upgrade Requirements

Upgrade Procedure

SQL Server Upgrade

CommServe Cluster Upgrade

Post-Upgrade Considerations

Overview

The procedure in this page describes the steps involved in upgrading the CommServe in the cluster group servers (active and passive nodes) in a clustered environment.

Upgrade Requirements

Review the following before upgrading the software:

Verify that the latest Service Pack of previous release is installed on the CommServe computer before upgrading the CommServe.
The CommServe upgrade must be physically performed on the CommServe computer and cannot be upgraded from a remote computer.
Verify that there are no VaultTracker pending actions. If there are any, manually Abort these actions from the CommCell Console.

If a CommNet Agent was installed on a CommServe that was registered with a CommNet Server, the CommNet Agent is automatically upgraded to current version during the CommServe upgrade.

It is strongly recommended that you perform a Disaster Recovery Backup from the CommCell Console before upgrading the CommServe.

Upgrade Procedure

SQL Server Upgrade

In the clustered CommServe upgrade, the Microsoft SQL Server 2008 database instance must be upgraded first.

The SQL Server instance needs to be manually upgraded on all passive nodes of the cluster first. Then manually upgrade the active node.

1.	Run the Setup.exe from the following location: <Software Installation Disc>\<CPUType>\SQL2008\SQL_Enterprise_Edition\
2.	You will be prompted to update the Microsoft .Net Framework. Click OK to continue with setup.
3.	Click Install.
4.	Select I Agree. Click Next.
5.	Click Finish.
6.	Click OK to reboot.
7.	Run the Setup.exe from the following location: <Software Installation Disc>\<CPUType>\SQL2008\SQL_Enterprise_Edition\
8.	Click Installation to continue with the setup.
9.	Click Upgrade from SQL Server 2000 or SQL Server 2005.
10.	Click OK.
11.	Click Next.
12.	Select I accept the license terms and Click Next.
13.	Click Install to setup support components.
14.	Click Next.
15.	Select the SQL Server instance to upgrade. Click Next.
16.	View the list of features being upgraded. Click Next.
17.	Select the instance to upgrade. Click Next.
18.	Click Next.
19.	Enter Account Name and Password details to allow administrative access to the SQL Server instances. Click Next.
20.	Select Import. Click Next.
21.	Click Next.
22.	Click Next.
23.	Click Next.
24.	Click Upgrade.
25.	Review that all features are upgraded successfully. Click Next.
26.	Click Next.
27.	Upgrade Complete Successfully. Click Close.
28.	Install Microsoft SQL Server 2008 Service Pack 1 on all nodes.	See Installing SQL Server Service Pack for step-by-step instructions.

CommServe Cluster Upgrade

Follow the steps described below to perform CommServe upgrade in clustered environment:

Verify and ensure that you have permanent license before upgrading the CommServe. You may encounter irrecoverable failure, if you upgrade using an evaluation license.

1,	Verify that the computer in which you wish to upgrade the software satisfies the minimum requirements specified in System Requirements - CommServe.
2.	Select the required languages. Click Next.
3.	Select the option to install software on this computer. NOTES The options that appear on this screen depend on the computer in which the software is being installed.
4.	Click Next.
5.	Click OK.
6.	Select I accept the terms in the license agreement. Click Next.
7.	Select Configure a Virtual Server. Click Next.
8.	Select the disk group in which the cluster group resides. Click Next to continue.
9.	Click Next to continue with the upgrade. NOTES The older version number depends on the version in the computer and may look different from the example shown.
10.	Click Yes to continue. NOTES The upgrade process deletes and replaces this folder with newer files. To preserve this, move them to another location before clicking Yes. Note that the upgrade process does not save any files such as command line scripts or folders from the <software installation path> folder. Clicking No will exit the upgrade program.
11.	Select the option to specify from which the database upgrade scripts should be copied for use during the upgrade process or use the default location. The upgrade program copies the necessary database scripts to the install location before running them. NOTES Select Download latest scripts from the software provider website, if you want to download and install the software using the latest software package. Make sure you have internet connectivity when you are using this option. Select Use the scripts contained on the installation media to continue the upgrade from the current location. Select Use scripts from an alternate location, if you have the software package in an alternate location. Type the location of the software package directory, or click Browse to choose the location. Click Next.
12.	Specify the SQL Server System Administrator password. Click Next. NOTES This is the password for the administrator's account created by SQL during the installation.
13.	Select Setup Software Cache option to download the software updates automatically. Select Schedule FTP Download of Automatic Updates option to schedule automatic FTP downloading of software updates. Click Next.
14.	Click Next. NOTES The upgrade program now starts the upgrade process. This step may take several minutes to complete.
15.	To upgrade the software on the remaining nodes of the cluster, click Yes. To complete the install for this node only, click No.
16.	Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list. NOTES The list of Preferred Nodes displays all the nodes found in the cluster; from this list you should only select cluster nodes configured to host this cluster group server. Do not select nodes that already have multiple instances installed. For more information, see Multi Instancing. When you have completed your selections, click Next to continue.
17.	Type the User Name and Password for the Domain Administrator account, so that the installer can perform the remote upgrade of the cluster nodes you selected in the previous step. Click Next.
18.	The progress of the remote upgrade for the cluster nodes is displayed; the upgrade can be interrupted if necessary. Click Stop to prevent upgrade to any nodes after the current ones complete. Click Advanced Settings to specify any of the following: Maximum number of nodes on which Setup can run simultaneously. Time allocated for Setup to begin executing on each node, after which the upgrade attempt will fail. Time allocated for Setup to complete on each node, after which the upgrade attempt will fail. NOTES If, during the remote upgrade of a cluster node, setup fails to complete or is interrupted, you must perform a local upgrade on that node. When you do, the upgrade begins from where it left off, or from the beginning if necessary. For procedures, see Manually Upgrading the Software on a Passive Node.
19.	Click Next. NOTES If the passive node upgrade fails, you must manually upgrade the passive node once the active node upgrade is complete. (See Manually Upgrading the Software on a Passive Node for step-by-step instructions.)
20.	Click Finish.

Post-Upgrade Considerations

CommServe Specific

Review Upgrade Considerations after upgrading the software.

If the CommServe Software Cache for the Automatic Update feature is located within the CommServe install folder, the cache will be lost after the upgrade. Make sure to repopulate the CommServe Software Cache after the upgrade.
If the bCHECK_AUTOUPDATES registry key was defined in the previous release, its settings (enabled or disabled) will carry over to the current release. If enabled, the CommServe CVD will contact the configured Automatic Updates FTP site at six-hour intervals (360 minutes) to check if the CommServe Software Cache is up-to-date. If there are missing updates, they will be downloaded as per the Automatic Update Configuration.

Upon upgrade, if you had configured a UNIX share for the CommServe Software Cache in the previous release, the software will automatically point all clients associated with the configured share to the CommServe Software Cache as the source for updates. A UNIX share can no longer be configured for the CommServe Software Cache. Instead, UNIX Clients can be designated as software caches as part of Automatic Updates Multicache Configuration. Once designated as an software cache, a UNIX client can be configured to push out the latest software packages it receives from the CommServe Software Cache to the clients within the CommCell that are selected to receive their updates from this UNIX software cache. For more information, see Setup Remote Cache.
Upon upgrade, if you had enabled the Get Updates From Share option in the previous release, the software will automatically point all clients associated with the configured share to the CommServe Software Cache as the source for updates.

Interactive Upgrade - CommServe - Clustered Environment

Table of Contents

Overview

Upgrade Requirements

Upgrade Procedure

SQL Server Upgrade

CommServe Cluster Upgrade

Post-Upgrade Considerations

CommServe Specific