VERITAS Storage Foundation (tm) 4.1 for Windows Rollup Patch 1 - English and Japanese

Article:TECH34114  |  Created: 2004-01-27  |  Updated: 2011-10-25  |  Article URL http://www.symantec.com/docs/TECH34114
Article Type
Technical Solution


Environment

Issue



VERITAS Storage Foundation (tm) 4.1 for Windows Rollup Patch 1 - English and Japanese


Solution



Note: Do not install this rollup patch through Terminal Services or Remote Desktop session. Users should install this patch locally at the server by double-clicking the appropriate MSI file, or through Add | Remove programs. Installing through Terminal Services or Remote Desktop is not supported at this time.


With the release of VERITAS Storage Foundation 4.1 for Windows and Storage Foundation 4.1 HA for Windows, VERITAS has improved the maintenance process to better serve its customers and reflect the new packaging, integration, and product consolidation that took place in the 4.1 release. This new maintenance process includes replacing the previous "hotfix" per product model with a consolidated "rollup patch" model for all Storage Foundation for Windows products, agents, and options.

This rollup patch (RP) includes resolutions for a number of issues for the Storage Foundation for Windows product and all its applicable options including the Volume Replicator option, Microsoft Cluster Service (MSCS) option, Dynamic Multipathing (DMP) option, and the FlashSnap option.

This rollup patch should be installed only on servers running Microsoft Windows 2000 Server, Advanced Server, or Datacenter Server or Microsoft Windows Server 2003, Enterprise Edition, or Datacenter Edition. For Windows 2000, this rollup patch requires Microsoft Windows 2000 Service Pack 4.

This readme file has the following topics:
 
  • Installing the rollup patch
  • Uninstalling the rollup patch and VERITAS Storage Foundation 4.1 for Windows
  • Issues Resolved with the Rollup Patch

Installing the rollup patch
This section describes two methods for installing the rollup patch:
 
  • Installing the rollup patch using the GUI
  • Installing the rollup patch silently

Installing the rollup patch using the GUI
The installation files are downloaded from the Support page for Storage Foundation for Windows on the VERITAS Web site. The installation is started by double-clicking the rollup patch executable file. After the installation finishes, you must reboot to have the changes take effect.
Note: A cluster does not have to be brought down to install the rollup patch. A rolling upgrade can be done so that the cluster resources remain available during the installation (see steps 1 through 4 that follow).

 
1. Before installing the rollup patch to a cluster node, move all cluster resources to another cluster node
 
2. Install the rollup patch as directed above
 
3. Move the cluster resources back to the original node
 
4. Repeat steps 1 through 3 for each remaining node of the cluster
 

Installing the rollup patch silently
The commands below call the msi files needed to silently install the rollup patch. From the command window, navigate to the directory where the rollup patch files have been downloaded and then enter one of the following commands:

For Windows 2000:
msiexec.exe /q /i PATH VM_Reboot=YES where PATH is the path to the VM41RP01_W2K.msi file

For Windows Server 2003:
msiexec.exe /q /i PATH VM_Reboot=YES where PATH is the path to the VM41RP01_W2K3.msi file.
Note: You must reboot to have the changes take effect. If you don't want to reboot immediately after entering the last command, change the command to VM_Reboot=NO, then reboot later.

Uninstalling the rollup patch and VERITAS Storage Foundation 4.1 for Windows
If you are uninstalling the rollup patch and Storage Foundation 4.1 for Windows, the patch must be uninstalled first.

Topics in this section include:
Uninstalling the rollup patch using the GUI
Uninstalling the rollup patch silently
Uninstalling VERITAS Storage Foundation 4.1 after the rollup patch has been uninstalled

Uninstalling the rollup patch using the GUI
Follow these steps to uninstall the rollup patch using the GUI:

 
1. Open the Control Panel and select Add/Remove Programs
 
2. Select VERITAS Storage Foundation 4.1 - Rollup Patch 01 and then click Remove
 
3. A dialog box appears with two options--Repair and Remove. Select Remove and then click Next
 
4. Click the Remove button in the next screen
 
5. Click the Finish button to complete the wizard. After the process for uninstalling is complete, a message appears prompting you to restart your system.
 
6. Click Yes to restart the computer now or No if you plan to restart later. You must reboot to have the changes take effect.
 

Note: To repair the rollup patch, select Change instead of Remove in step 3. Select Repair  from the dialog box that appears and then click Next. The rollup patch repair option runs automatically. It will fix missing or corrupt files, shortcuts, and registry entries.

Uninstalling the rollup patch silently
From the command window, navigate to the directory where the rollup patch files have been downloaded and then enter one of the following commands:

For Windows 2000
msiexec.exe /q /x PATH REMOVE=ALL VM_Reboot=YES where PATH is the path to the VM41RP01_W2K.msi file.

For Windows Server 2003
msiexec.exe /q /x PATH REMOVE=ALL VM_Reboot=YES where PATH is the path to the VM41RP01_W2K3.msi file. Note: You must reboot to have the changes take effect. If you don't want to reboot immediately after entering the last command, change the command to VM_Reboot=NO, then reboot later.

Uninstalling VERITAS Storage Foundation 4.1 after the rollup patch has been uninstalled
After the rollup patch has been uninstalled, uninstall Storage Foundation 4.1 for Windows either through the GUI or the silent uninstall procedure

To uninstall VERITAS Storage Foundation 4.1 using the GUI:
Follow the steps described in the above section "Uninstalling the rollup patch using the GUI"; but in step 2, click on VERITAS Storage Foundation 4.1.
Note: You must reboot your system to have the changes take effect.

To uninstall VERITAS Storage Foundation 4.1 silently:
To uninstall VERITAS Storage Foundation 4.1 from the command window, navigate to the root directory of the product CD and enter one of the following commands:

Setup.exe /s INSTALL_MODE=5 SOLUTION=3 REBOOT=0
The command will uninstall the Storage Foundation for Windows client, and the system will not reboot at the end of the uninstallation.

Setup.exe /s INSTALL_MODE=5 SOLUTION=1 REBOOT=1
The command will uninstall the Storage Foundation for Windows server, and the system will reboot at the end of the uninstallation.

Note: You must reboot to have the changes take effect.

Issues resolved with the rollup patch
This section is divided into four topics:
 
  • General Issues
  • Cluster Issues
  • DMP Issues
  • Volume Replicator Issues

General Issues

VERITAS Incident Number- Description

117920-Unable to connect to local host after upgrading from Windows 2000 to Windows Server 2003 and reinstalling VSFW 4.1. If you upgrade the operating system and reinstall VSFW 4.1, you may be unable to connect to the local host when VSFW comes up initially. You can resolve the problem with the following workaround, which restarts the VERITAS Enterprise Administrator service:

 
1. Select Start>Settings>Control Panel>AdministrativeTools>Services
 
2. Look at the VERITAS Enterprise Administrator Service line entry. If its startup type is "Disabled," enable it by doing the following:
 
a. Double-click the Disabled entry to bring up a Properties window
 
b. Use the drop-down menu under Startup type to change the startup type to "Automatic" and click OK
 
3. You can now connect to any host, but a "Connection Error" message may appear. Click OK to close it
 

159311-If you install the Language Pack and change the system locale to a language that is not Japanese, the CLI does not display readable characters. This issue is resolved by the rollup patch.

209507-The file system of a volume, particularly a striped volume, may be corrupted after completing a subdisk move with active I/O. This issue is resolved by the rollup patch.

209701-Enhancement: The vxscrub utility is made available to remove unneeded registry entries resulting from adding and deleting volumes. A Windows system may not boot up or new volumes may not be created when the system hive of the registry becomes too large. Repeatedly adding and deleting volumes or disk devices will increase the size of the system hive. This rollup patch installs the vxscrub utility. The vxscrub utility will shrink the registry size and avoid these problems. Rebooting the system after running vxscrub is mandatory.
Caution: The vxscrub utility should be used only under the direction of VERITAS Technical Support. Use of this utility without supervision may cause performance problems when importing disk groups.

209889-The vxstat utility may terminate abnormally. This issue is resolved by the rollup patch.

212129-Sorting disks by size in the List view on a system that had its locale changed from English to a European language may not produce the correct sorted results. This issue is resolved by the rollup patch.

213397-Using Perfmon to monitor performance on a server with a large number of dynamic disks and volumes can cause the VERITAS Enterprise Administrator service (vxob, vxsvc.exe) to crash. This issue is resolved by the rollup patch.

216394-Enhancement: The APIs for VSFW 4.1 now provide improved integration with the Backup Exec product. After this rollup patch is applied, Backup Exec 10.0 will be more closely integrated with VSFW 4.1.

216734-Dell OpenManage Array Manager: SNMP alerts sent from Array Manager to a management console (such as HP OpenView) are disabled. After this rollup patch is installed, SNMP alerts can be sent from Array Manager version 3.4 or higher.

218218-Incorrect version of the SNMP MIB file. VSFW 4.1 did not have the most recent version of the SNMP MIB file for Windows 2000. The current version is included with this rollup patch.

219108-When processing large volumes, CLI commands that perform a mirror resynchronization, such as snap start or snap back, may exit successfully before mirror resynchronization completes. This issue is resolved by the rollup patch.

222265- Uninstalling Storage Foundation for Windows before uninstalling the rollup patch does not delete all product files. The recommended procedure for a clean uninstallation is to uninstall the rollup patch before uninstalling Storage Foundation for Windows.

223315-An error occurs when reinstalling Storage Foundation for Windows 4.1 after having upgraded from Windows 2000 to Windows Server 2003. This situation happens if you have Storage Foundation 4.1 for Windows and rollup patch 1 installed before upgrading. The error message indicates that the install utility is unable to locate the VxCMD.DLL file. Use the following workaround to resolve this problem:

 
1. Click OK in the error message window and let the installation complete
 
2. Reboot
 
3. Insert the Storage Solutions 4.1 product CD into your CD drive and navigate to the \Pkgs\W2K3 directory
 
4. Execute the one of the following commands to repair the install:
 
For systems without MSCS: msiexec /fp vm.msi
 
For systems with MSCS installed: msiexec /fom vm.msi VM_SERVER=1 VM_MSCS=1
 
5. Start the VERITAS Enterprise Administrator service. To do so, from the Windows command window type: net start vxob
 
Note: When Storage Foundation for Windows comes up, it may not be able to connect to the local host. If that is the case, see Incident 117920 for instructions on how to resolve that problem.
Note: After applying the steps given above (Incident 223315), "VERITAS Volume Manager 4.1" appears in Add or Remove Programs list, but the program cannot be removed or repaired from that listing.

Cluster Issues

212261-[MSCS] An abnormal termination of the MSCS service (clussvc) may cause the VERITAS Enterprise Administrator service (vxob, vxsvc.exe) to have an access violation. This issue is resolved by the rollup patch.

212504-[MSCS] A cluster disk group with a DCO volume cannot be added as a resource under Cluster Administrator. This issue is resolved by the rollup patch.

230429-[MSCS] With vxclus enabled on a dynamic quorum cluster disk group, the disk group cannot be onlined with MSCS Cluster Administrator. In Storage Foundation 4.1 for Windows, even after running the vxclus enable command (vxclus enable -g<DynamicQuorumClusterDiskGroup>) on a target cluster disk group that contains the dynamic quorum volume, the MSCS service cannot be started successfully. This issue is resolved by the rollup patch.

DMP Issues

207050-When moving a cluster disk group from node 1 to node 2, node 2 may encounter a fatal error (BSOD). This rollup patch resolves this issue.

209320-If BCV LUNs on an EMC Symmetrix array are not in a Ready state, all paths on a BCV LUN display as not healthy with a read error. The rollup patch resolves the problem by having DMP implement the Test Unit Ready command only when the BCV LUN is in Ready state.

211043-Disabling one DMP path may cause cluster resources to fail over. This rollup patch resolves this issue so that disabling one DMP path will not cause a failover.

213854-[EMC CX-600 array] If the tunable parameter for testing paths (TestPathRetryCount) is set to 1 or more retries, DMP displays a path status as healthy, even when the path is failed or disconnected. This issue is resolved by the rollup patch.

214059-[EMC arrays] The system may hang or take longer to reboot when two or more EMC arrays are connected to the server with two paths attached to each array and the EMC tunable retry value is set to a value other than zero. This issue is resolved by the rollup patch

216664-Enhancement: The command line utility vxemctune.exe is provided to set the tunable values for the EMC ASL without rebooting the system. This rollup patch installs vxemctune.exe in the Storage Foundation 4.1 for Windows main directory. The typical path for this directory is ..\Program Files\VERITAS\VSFW 4.1

Vxemctune can be used to trigger the DMP driver to reload the tunable parameters from the registry. The default values for the tunable parameters are:
TestPathDelay 200 milliseconds
TestPathRetryCount 3
TestPathTimeout 30 seconds
Caution: Increasing the retry count will increase the time to fail over when a path or port becomes disabled or is pulled. After installing the rollup patch, follow these steps to change the tunable parameters:

1. Change the values in the registry using Regedit.exe or Regedt32.exe. The ranges for the in-memory tunable minimum and maximum values are shown below:

 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxDMPEmc\Tunable
 
value name = TestPathDelay
 
data type = DWORD
 
value = in milliseconds, Min: 200 Max: 10000
 
value name = TestPathRetryCount
 
data type = DWORD
 
value = number of retries, Min: 3 Max: 50
 
value name = TestPathTimeout
 
data type = DWORD
 
value = in seconds, Min: 30 Max: 120
 

2. To display the current values, from the command window run vxemctune -d
3. From the command window, run vxemctune -r for the new tunable values to take effect immediately (without rebooting). To verify the new in-memory values, use vxemctune -d

217388-[EMC arrays] DMP takes longer to perform DMP path failover when the test path retry count is increased through the DMP tunable settings. This rollup patch resolves the problem by not retrying DMP path testing after a path is removed or disconnected.

218020-[IBM/STK/LSI FAStT storage arrays] I/O errors may occur during array controller failover. This issue is resolved by the rollup patch.

218100-Enhancement: Change the IBM and EMC tunable default values to make DMP more flexible. After this rollup patch is applied, the IBM and EMC tunable retry default value will be set to 3 retries and the time-out default value will be set to 30 seconds. Note: This rollup patch will not apply these default values if any of the tunable values have been modified before installing the rollup patch. The rollup patch will preserve all the existing tunable values even if only one of the values has been modified.

220203-New LUNs that were dynamically allocated arrive in Storage Foundation for Windows successfully, but they are not kept by the system and cannot be used. This issue is resolved by the rollup patch.
Note: If the system uses the Emulex full port driver, the options "Report unknown SCSI device" and "Look for disappearing device" must be checked when configuring the HBA.

221301-Storage Foundation for Windows does not send the SNMP trap for a DMP path failure to the recipient. This issue is resolved by the rollup patch.

223166-Enhancement: Add DMP support for the NETAPP arrays that have product IDs that begin with:
 
"FAS27"
 
"F8"
 
"FAS9"
 
"R"
 
"LUN"
 
After this rollup patch is applied, DMP will be able to support these arrays.

Volume Replicator Issues

160012-Volume Replicator may encounter problems when replicating across a Network Address Translation (NAT) environment. For example, during a takeover with fast-failback, the old secondary does not get converted to an acting secondary. The following workaround ensures that Volume Replicator works correctly in a NAT environment:
Create a registry key NATSUPPORT of type DWORD with value 1 under HKLM\System\CurrentControlSet\Services\Vxio\VVRParams\key
This key needs to be created only on machines that are outside the NAT setup.

216653-The VERITAS Volume Replicator Security Service Configuration Wizard may terminate abnormally during the discovery of candidate hosts in the "Host Selection" dialog. This issue is resolved by the rollup patch.

218598-When there is a very high rate of updates, the primary encounters a fatal system error (BSOD). This issue is resolved by the rollup patch

229245/229242-When setting up replication across a NAT, if the packet size is not set to 1400 bytes or 1 KB, you may encounter some errors. For example, autosync operation may not proceed as required. Also, trying to change the packet size later may display the following message:

"Error E5140226: Operation timed out. The configuration server may be busy or down."

In this case, you may want to delete the RDS and recreate it. However, before doing so, you must ensure that the firewall configuration is completed as required and the necessary ports have been opened. To avoid such problems, when creating an RDS, you must set the packet size to 1KB (the default is 8 KB) on the "Edit Replication Settings" page of the Create RDS wizard. If you are using the CLI to create the RDS, then the "packet_size" attribute should be changed to 1400 bytes with the vxrds set command, even before starting replication.

229274-When configuring the VxSAS service for Volume Replicator in a firewall setup, the VxSAS wizard may not be able to configure the machines that are across the firewall, although the "Host Selection" dialog may list These nodes. The workaround is to configure the VxSAS service locally on the machines that are across the firewall. You can launch the wizard by selecting Start>Programs>VERITAS>VVR Security Service Configuration Wizard or run vxsascfg.exe from the command prompt of the required machine.

Do not install through Terminal Services or Remote Desktop!
 

Attachments

SFW41RP01_271065.exe (14.4 MBytes)


Legacy ID



271065


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


Terms of use for this information are found in Legal Notices