VERITAS Volume Manager (tm) 2.7 for Windows NT - Readme

Article:TECH15252  |  Created: 2001-01-06  |  Updated: 2004-01-13  |  Article URL
Article Type
Technical Solution



VERITAS Volume Manager (tm) 2.7 for Windows NT - Readme


NOTE: The version of Volume Manager mentioned below is no longer generally available. Users are strongly encouraged to upgrade their systems.



- You must have at least 128 Mbytes of system memory.

- You must have at least 55 Mbytes of free disk space to install this product.

- A minimum of two SCSI or HBA controllers are required to use the Dynamic Multi-Pathing (DMP) feature.

- You must be running Windows NT4 Workstation, Server, or Enterprise with a minimum of Service Pack 6a installed.

- Internet Explorer 4 or above must be installed on your system, to install this product. The product's online help will not function with earlier versions of Internet Explorer.

- If you want to use Microsoft Management Console (MMC), you need to install MMC version 1.1.  This product comes with an installable version of MMC 1.1.  Using MMC is optional.



**It is HIGHLY recommended that you exit all running applications prior to running the Volume Manager setup program.


1. Make sure that you have the license key you were provided so that you can enter it at the appropriate point in the installation procedure. Note: The installation validates the license key. If the license key is invalid, the install will NOT proceed.
2. Start the Volume Manager 2.7 setup by double-clicking the setup.exe program on the CD.
3. Select the default destination path to copy files to your target system. Although you may choose any location, it is recommended that you select the default path while installing.
4. Allow the file transfer to proceed. When prompted, reboot your system. You MUST reboot prior to using the application!


For users who currently have Dell OpenManage Array Manager 2.6, 2.71 or 3.0 installed on their PCs, Volume Manager 2.7 is designed to replace the Dell application. You will retain all existing configuration and array management features, but the two products (Volume Manager 2.7 and the Dell OpenManage Array Manager) cannot coexist on the same machine.

If any one of Dell OpenManage Array Manager 2.6, 2.71 or 3.0 is loaded on the target computer, the Volume Manager installation will detect it and inform the user that the Dell product will need to be uninstalled before proceeding. Select "Yes" to uninstall the Dell application. The uninstall is done automatically by the Volume Manager 2.7 installation program. After the Dell product has been uninstalled, the Volume Manager 2.7 installation resumes.

This product does not support an upgrade from Dell OpenManage Array Manager 2.5 or earlier.  You will first need to upgrade to Dell OpenManage Array Manager 2.6, 2.71 or 3.0 and then to Volume Manager 2.7. Please refer to the User's Guide for further details.


You may rerun the Volume Manager 2.7 installation at any time you choose. This may be necessary to repair a damaged installation, to upgrade to a new version of the product, or to put in a new license key to extend the usage of the product or activate all advanced features.

To accomplish the above:

1. Rerun the installation by double-clicking setup.exe. The installation will inform you that it has detected a previous version of Volume Manager on the system and will ask you if you wish to replace that version. If you choose "Yes," setup will continue. Selecting "No" will abort the installation.
2. You will need to reinput your license key to reinstall the application. Use the key provided to you at time of purchase. If you have acquired a new key, you may use it instead. Note that only valid keys are accepted by the installation!
3. Allow the installation to proceed. Reboot when prompted.


III.  VERITAS(r) Dynamic Multi-Pathing (DMP)

Dynamic Multipathing is a feature now available with VERITAS Volume Manager.

The major features of Dynamic Multipathing are:

a) Fault tolerance: Provides fault tolerance to your disk system by configuring and managing multiple controller paths to the attached disks.
b) Load balancing: Dynamic Multipathing switches I/O operations between paths to provide load balancing. Path sets can be either configured Automatic or Manual.
c) Support for unlimited number of I/O paths: A path can be a SCSI bus connection to one or more SCSI disks or a fiber optic channel connected to a hub or switch. You can set up as many I/O paths as your system box can accommodate.
d) Dynamic recovery: When a path to a disk fails, all Input/Output (I/O) operations are shifted to the other active paths. Path status is automatically updated on the user display when a path fails or is restored to service.
e) Dynamic path recognition: If you add a path to your storage system, running a rescan or rebooting your system causes Dynamic Multipathing to detect the new path and display its status. If a failed or disabled path is restored to service; Dynamic Multipathing automatically updates the display.
f) Single point administration: All Dynamic Multipathing functionality is set up and managed from a single window in Volume Manager.
g) Maintenance mode support: User can disable a given path or paths in the disk storage system.


Browse to the Volume Manager on NT page and click on the option "Device Support List". This page will give you the updated hardware compatibility list.

Currently, this version of Volume Manager supports Dynamic Multi-Pathing with the following combinations of Arrays and HBAs:

i. Compaq RA8000: QLA2200, JNI-116x
ii. EMC Symmetrix: QLA2200, JNI-116x
iii. HDS 5800: QLA2200, JNI-116x
v. HP XP256: QLA2200, JNI-116x
vi. Andataco GigaRAID 8000: 29160 UW PCI SCSI, 39160 UW PCI SCSI, Advansys ASB-3940U2W
vii. Generic SCSI JBOD: 29160 UW PCI SCSI, 39160 UW PCI SCSI, Advansys ABP-3040U2W
iv. HDS 7700E: QLA2200, JNI-116x



IV. Software Issues

1. Cannot Upgrade disks with FT Volumes to Dynamic disks

FT volumes are volumes created by the NT4.0 Disk Administrator.  Upgrading (also called "Encapsulating") a disk containing all or parts of an FT volume is not supported in the release of the product.  In order to upgrade these disks, you will need to back up all the data on the FT volumes, delete the original FT volume, then upgrade the disk to dynamic, create the appropriate dynamic volume and finally restore the data from the backup.

2. DMP - Disabling all paths to a dynamic disk - CAUTION

By double-clicking a disk and then right-clicking on the path, you can disable all paths to a disk or set of disks from the context menu. You should hit RESCAN after this operation. If this disk is a dynamic disk, you will then see a Missing disk associated with the disk.  You can not re-enable any paths to this disk until you hit RESCAN once again.  After that, you will see an Unknown disk associated with disks that were originally online. You can double-click that disk and then right-click on the path to bring up the context menu and re-enable the path, and bring the disk online.

Caution: If all paths to the disk on which Volume Manager is installed are disabled, no Volume Manager operations will be possible after that. You will not be able to restart Volume Manager since the disk is inaccessible.

3. WARNING! Using two or more SCSI or HBA controllers connected to a single device


DATA CORRUPTION or LOSS is extremely likely to occur if multiple paths are connected to a single device and the DMP feature is not enabled and controlling the device. The risk to data is highly increased if the default Windows NT Disk Administrator is used to create fault tolerant partitions such as Mirror Sets, Stripe Sets, Stripe Sets with Parity, or Volume Sets. VERITAS does not recommend the use of any Windows NT Disk Administrator fault tolerant configurations on systems where multiple paths to a single device are configured.

Make sure that DMP is enabled and controlling all devices configured with multiple paths prior to accessing the devices. Furthermore, it is strongly recommended that the default Windows NT Disk Administrator not be used to view or manage partitions when multiple paths are being used.

In the event the DMP driver does not load you will see two or more devices in Volume Manager for every real device. This is a limitation of the Operating System. Should this occur, do not open the default Windows NT Disk Administrator and do not attempt to access data on the device. If the default Windows NT Disk Administrator is executed while the DMP driver is not controlling all devices with multiple paths configured the program will notify you that the disk configuration has changed. A prompt will then be displayed asking to write disk signatures to the new disks. DO NOT CHOOSE YES WHEN PROMPTED TO WRITE DISK SIGNATURES TO DISKS, LOSS OR CORRUPTION OF DATA WILL OCCUR AND CAN NOT BE RECOVERED. If you are unable to configure DMP to control all devices with multiple paths configured, shut down the Windows NT machine and disconnect all but one path to the device to help ensure data loss or corruption does not occur.

4. Some disk operations must be completed before using the disks with a clustering product, such as with the VERITAS Cluster Server

High Availability or clustering products, such as the VERITAS Cluster Server, can make disks and their volumes highly available by sharing the physical disk connections among a cluster of servers, and passing the exclusive I/O access rights around the cluster as necessary.   However, in this environment the disks are expected to always be online.  

Since some Volume Manager operations require I/O to stop temporarily to disks, those operations are not allowed on volumes or disks that are being used in a clustered environment. These Volume Manager operations include changing a drive letter and extending a volume.  Please see the Volume Manager's User's Guide for a detailed explanation of these operations. Because the Volume Manger provides a special type of disk group to be used in clustered configurations, called "Clustered" disk groups, specifically extending a volume is not permitted on a clustered disk group if the volume on these disks are in use, presumably by the clustering software.

Because of this, all Extend Volume operations should be performed before the disks are added to the clustered configuration, that is under clustering software control.  

Alternatively, the extend operation can be performed on a volume previously used in a clustered environment if the clustering software is temporarily suspended. At that point, the volume can be extended, after which the control can again be returned to clustering software.

5. Primary partitions cannot be deleted

If you are not be able to delete primary partitions on basic disks, it is likely that you might be running anti-virus software or other such monitoring software. To delete these partitions, you may have to temporarily stop the interfering service and then delete them.

6. Disks Will Not Upgrade as Expected and an "Internal Error" Message May Be Displayed

By default, most SCSI HBA's come configured with the BIOS enabled and INT13 BIOS extensions enabled.  If the extensions or BIOS are disabled, it is possible that the disk geometry and partitions on disks configured with Disk Administrator on Windows NT 4.0 systems will prevent upgrading the disks to dynamic.

There are no issues if the disks are new or if the existing partitions can be deleted. Clean disks will upgrade correctly and can be used to hold volumes without any problems.

WARNING:  Should you encounter this situation, immediately exit Volume Manager 2.7 and stop the Disk Management service.  This can be done from a command prompt by typing "net stop vxsvc". Start Volume Manager again, and the correct partitioning will again be displayed.  Failure to immediately exit and stop the service could result in lost data on these volumes.

7. Sometimes the Modify option will provide disks with insufficient space to create a Volume

The Modify option on the fourth screen of the Create Volume wizard lets you customize the selection of the disk(s) to be used in the newly created volume. Because of limitations with this release version, sometimes the disk(s) provided in Modify Disk Selection screen will not have sufficient space to create the volume.

This can be remedied by choosing disk(s) that are known to have sufficient space to create volume.  Available space on disks can be identified by using the General tab view.

8. Cannot use Custom mode of Move Subdisk to move one subdisk to multiple subdisks

Move Subdisk is the operation where a part of a volume (called a subdisk) is physically copied to a new location on another disk.  The new location is then used in the volume and the old location is deleted.

In some cases, you may not have enough contiguous free space on other available disks to move the subdisk to just one location. However, if the total available free space on all the other disks is enough and spanning the volume is allowed, you can use the Express Mode of Move Subdisk to move the subdisk. This operation (move with spanning) cannot be done with the Custom mode of Move Subdisk.  

9. Cannot use Custom mode of Extend Volume to span a simple volume across multiple disks

Extend Volume is the operation where the size of a volume is increased or extended.

In some cases, you may want to extend a simple or spanned volume across multiple disks. This operation is called spanning. You can use the Express Mode of Extend Volume to span volumes across disks with space available. However, you cannot use the Custom Mode of Extend Volume for spanning.

10. Foreign disk that cannot be merged

A foreign disk is a dynamic disk that was previously created and/or used on another system and is now attached to the target system. Typically, you must use the Import Foreign Disk feature to start  using that disk on the target system. In very unusual circumstances, a Foreign Disk cannot be merged into a target system. You have the option of attempting to Merge the Foreign disk on another system containing VERITAS Volume Manager for Windows NT or delete all Volumes from the disk after taking a backup and convert it to a Basic disk. You can do the latter by running the Windows NT 4.0 Disk Administrator tool and deleting the "Unknown" partition on this disk.

11. Events are not displayed if logged onto Windows NT as a domain user

If you are logged onto your Windows NT system as a domain user without administrator rights to the target system on which you wish to use the Volume Manager, you will be prompted to provide a user name with administrator rights when connecting to that target system. After the proper user name is entered, you can manage the disks and volumes on that target system; however, events will not be displayed in the Events tab.

This situation can be remedied by logging onto your Windows NT system as a domain user with administrator rights for the target system, or by logging onto your Windows NT system as the administrator of that system.

12. File systems may temporarily unavailable after moving a basic disk to another machine

If you take a Basic disk with partitions to another machine, sometimes the partitions may come up as RAW and will lose their drive letters temporarily.  If this happens, you will need to reboot the machine to access the partitions and the data.

13. A Missing disk will become Offline after returning it to a cluster disk group

To return any Missing disk into a disk group, you must hit Rescan.  If you return a Missing disk into a cluster disk group, the disk will be shown incorrectly as Offline, instead of Online.  If this happens, deport the cluster disk group and import it again on the same node.  This will give the SCSI reservation to all the disks in the disk group including the newly returned disk.

14. RAID-5 volumes may not be Online after upgrading to Microsoft Windows 2000

If you are upgrading your Operating System containing the Volume Manager 2.7 to Microsoft Windows 2000 (Win2k), RAID-5 volumes may not be automatically provided Online.  This is an issue with the default Win2k Volume Manager (LDM).  You can use the "Reactivate Disk" menu command to bring the RAID-5 volumes Online.  You should then also run CHKDSK on the volumes, to verify file system integrity.   Note that this problem will not arise if you upgrade LDM to the VERITAS Volume Manager for Windows 2000.

15. Cluster disk group names must be unique

You must use cluster disk groups When sharing disks or arrays in a clustered environment.  Make sure that cluster disk group names are unique among all shared disks in the cluster.   Non-unique cluster disk group names may lead to unexpected problems when a disk group fails over to another node in the cluster as they will confuse the Volume Manager in determining which disks belong to which disk group.

16. Only Active-Passive connectivity is supported while working with VCS and DMP together

The disk reservation commands issued by VCS lock the connection between a specific HBA on the host and the storage.  These reservations cannot be altered by the DMP software.  Therefore, Active-Active connectivity cannot be supported in such configurations.

Full Active-Active connectivity is supported if there is no clustering software running on the system.

17. RAID 5 volume comes up in failed state when imported

This can happen when a disk from a cluster disk group with a column of a RAID 5 volume becomes offline and the node on which that cluster disk group is switched off abruptly (not shut down).  If the cluster disk group is now imported on another node, the RAID 5 volume will come up in a "Failed" state instead of "Failed Redundancy".

If this happens, you will have to import the disk group manually and reactivate the volume.  Please consult the Users' Guide for how to do this.

18. AMConsole shows only one path to a cluster disk group after reboot

If you reset a node on which a cluster disk group with multiple paths was imported, the cluster disk group may show only one path when it is imported back on that node.  To circumvent this problem, close the AMConsole, issue the command "vxassist resetbus" from a DOS shell and restart the AMConsole.


V. Support

1. For product assistance, contact VERITAS Customer Support:

U.S. and Canadian Customers: 1-800-634-4747 or 407-531-7200, FAX: 407-531-7750
United Kingdom Customers: 44 (0) 870-243-1010, FAX: 870-243-1020
Any other country: 1-407-531-7200, FAX: 1-407-531-7750
Email:, or go to

2. This product includes a tool that will assist VERITAS Technical support in determine the cause of problems you may encounter.  It is called SupportNow.  SupportNow will allow an authorized VERITAS technical support engineer to connect to your system remotely, view the desktop, and troubleshoot.  Once you have contacted technical services for any problem related to Volume Manager operations, a technician might suggest the use of VERITAS SupportNow to help solve the problem you have called in about.

To start SupportNow, click on the Help menu, and select Get Support.  This will begin to install    SupportNow when you select this menu item for the first time, and will invoke SupportNow every time you choose this menu item thereafter.


VI. Sales

For information on purchasing other VERITAS products, contact your sales representative:

U.S. and Canadian Customers: (800) 327-2232
International Customers:     (650) 527-8000

For information on VERITAS training courses, consulting services, trade shows, and seminars, visit our Web site at


Copyright (c) 2000 VERITAS(r) Software Corporation. All rights reserved.

VERITAS, Volume Manager, and the VERITAS logo are trademarks of VERITAS Software Corporation.

Other products mentioned in this document are trademarks or registered trademarks of their respective holders.

VERITAS Software Corporation
1600 Plymouth Street
Mountain View, CA 94043
(650) 335-8000

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices