VERITAS Volume Manager (tm) 2.7 for Windows NT Hotfix01 - English

Article:TECH16799  |  Created: 2001-01-26  |  Updated: 2004-01-23  |  Article URL http://www.symantec.com/docs/TECH16799
Article Type
Technical Solution

Environment

Issue



VERITAS Volume Manager (tm) 2.7 for Windows NT Hotfix01 - English

Solution



VERITAS Volume Manager 2.7 for Windows NT Hotfix01 Readme File
October 20, 2001

***************************************************************
*PLEASE READ THIS README FILE CAREFULLY,  
*ESPECIALLY IF YOU ARE  USING THE VOLUME    
*MANAGER IN A CLUSTER ENVIRONMENT.          
***************************************************************

This Readme file has the following topics:

I.   INSTALLING THE HOTFIX
II.  UNINSTALLING THE HOTFIX
III. ISSUES RESOLVED IN THIS HOTFIX


I. INSTALLING THE HOTFIX
IMPORTANT: If you have a cluster, install the hotfix on each node of the cluster. See the NOTE below for details.  

Use the following steps to install this hotfix:  

1. Obtain the hotfix package by clicking on the "Download Now" link below (file name VMNT27HF01ENU_241478.exe). When prompted, select "Save This Program  To Disk" and click OK.  
2. When the download completes, extract the contents by double clicking the downloaded package. The hotfix package contains three files; a package ID, a readme.txt file, and the hotfix executable.  
3. Copy the extracted hotfix executable, VMNT27HF01.EXE, to any directory on the computer where Volume Manager is installed
4. Double-click the hotfix executable, VMNT27HF01.EXE, to start the installation. The Setup progress will display.  
5. An informational box will display prompting you to read the included readme file. Click OK to continue. The hotfix readme will display. Read through it and close the readme.  
6. The installation will now stop all associated Volume Manager services.  
7. Click Next at the installation welcome screen to continue installation. The hotfix install runs automatically and will install the files modified by the hotfix to the appropriate directories. A message will appear, prompting you to reboot your system.  
8. Click Yes to restart the computer. You must reboot to have the changes take effect.

II. UNINSTALLING THE HOTFIX
IMPORTANT:

1. If you have a cluster, uninstall the hotfix from each node of the cluster. See the NOTE below for details.  
2. Remember to uninstall the hotfix before uninstalling Volume Manager  

Normally you would not need to uninstall the hotfix,  but if it becomes necessary to do so, here are the steps:  

1. The installation of this hotfix will create a menu item under Start | Programs | VERITAS | Volume Manager 2.7 | HotFix | HotFix_Uninstall. Click on this to start the uninstallation.  
2. The changes made by the installation of the hotfix will be removed and the machine will come back to its original configuration.  
3. Remember to reboot for the changes to take effect

NOTE: FOR INSTALLING/ UNINSTALLING THE HOTFIX IN A CLUSTER ENVIRONMENT:
--------------------------------------------
A cluster (VCS) does not have to be brought down to install/ uninstall the hotfix. A rolling upgrade can be done so that the cluster resources remain available during the installation (see steps a through e below).  
a. Before installing/ uninstalling the hotfix to/ from a cluster node, move all cluster resources to another cluster node  
b. For VERITAS Cluster Server clusters: Stop the HAD service of Cluster Server from the node on which you are installing/ uninstalling the hotfix.  
c. Install/ uninstall the hotfix as directed above  
d. Move the cluster resources back to the original node or to another node in the cluster  
e. Repeat steps a through d for each remaining node of the cluster  

III. ISSUE RESOLVED IN THIS HOTFIX

This hotfix resolves the following issues:

1. When running backups with either Backup Exec for Windows NT or NetBackup, and Open File Option is used, the backups hang at loading media when Volume Manager for Windows NT is installed and dynamic multipathing (DMP) is enabled. This has been fixed with an updated DMP driver.  
2. When a server gives up ownership of a disk group, disk reservations may not be freed, preventing other servers from being able to reserve those disks.  This has been resolved by this hotfix. The fix was to remove a 'wait' call and grab the disk reservations right away.  Then the other node would notice a loss of majority, free any reservations, and stop its thread.

Attachments

VMNT27HF01ENU_241478.exe (2.4 MBytes)

Legacy ID



241478


Article URL http://www.symantec.com/docs/TECH16799


Terms of use for this information are found in Legal Notices