VERITAS Volume Manager (tm) 2.7 for Windows 2000

Article:TECH16320  |  Created: 2004-01-04  |  Updated: 2004-01-04  |  Article URL http://www.symantec.com/docs/TECH16320
Article Type
Technical Solution

Environment

Issue



VERITAS Volume Manager (tm) 2.7 for Windows 2000

Solution





VOLUME MANAGER 2.7 FOR WINDOWS 2000
README FILE:

June 29, 2001

This document contains information that may not be in the
User's Guide. The information in this document is more current
than information in the User's Guide. If the information in
this file conflicts with the User's Guide, the information in this file is correct.

This readme file has the following topics:

I.    REQUIREMENTS
II.   INSTALLATION
III.  ISSUES


I. REQUIREMENTS

- Must be running Windows 2000 Server or Advanced Server,
 which require Service Pack 1, or Windows 2000 Datacenter
 Server, which does not require a service pack. Volume Manager
 2.7 for Windows 2000 has been tested with Windows 2000 Server
 or Advanced Server Service Pack 2. Service Pack 2 is optional
 and is not required to run Volume Manager 2.7 for Windows
 2000.

 You may install Volume Manager 2.7 for Windows 2000 Client on
 Windows 2000 Professional, with Service Pack 1; however, Volume
 Manager 2.7 for Windows 2000 Server is not supported on
 Windows 2000 Professional.

- 37 MB disk space is required for the full installation.
 You must also have free space in your temp directory
 for Volume Manager 2.7 for Windows 2000 to install.
 In addition, the installation program has a requirement that
 in order for the installation to proceed, there must be at
 least 50 MB of space on the computer's system drive, regardless
 of what drive you plan to install the software on.
 (Incident 63649)

 The program checks for disk space before installing.

- Minimum requirement for system memory size is 128 MB.

- No minimum system processor speed (200 MHz or faster
 Pentium suggested).

- A minimum of two SCSI host adapters are required to use
 the Dynamic Multipathing (DMP) feature.

- A minimum resolution of 800 x 600 pixels is recommended
 for the monitor.

If you install only the Volume Manager 2.7 for Windows 2000
Client on a computer, no license is required. The Client can be
installed on a computer running any version of Windows
2000.

Licenses are required to install the server component of
Volume Manager 2.7 for Windows 2000. The license you purchase--
Server, Advanced Server, or Datacenter Server--allows
installation only on a machine with the matching version of the
Windows 2000 operating system. For example, a Volume Manager
2.7 for Windows 2000 Advanced Server license allows you to
install Volume Manager 2.7 only on a computer that is running
Windows 2000 Advanced Server.

If you have a Windows 2000 Professional system, the
Volume Manager 2.7 for Windows 2000 Client is the only version
of Volume Manager 2.7 that you can install on that machine.

Volume Manager 2.7 for Windows 2000 has not been tested with
the next version of the Microsoft Windows operating system,
Windows XP. Support for this unreleased operating
system will be in an upcoming version of Volume Manager for
Windows.


II. INSTALLATION

This section covers the following topics:

- INITIAL INSTALLATION
- UPGRADE PROCEDURES
- MODIFYING THE EXISTING INSTALLATION
- REPAIRING THE INSTALLATION
- UNINSTALLING THE PRODUCT

It is HIGHLY recommended that you exit all running
applications prior to running the Volume Manager 2.7 for
Windows 2000 installation program.

If you are running Windows 2000 Professional,
you may do only a Client install.

NOTE: If you encounter any installation-related
problems, see "Installation Issues," the first
topic in the "Issues" section.


        >> INITIAL INSTALLATION<<
   
If you are upgrading from Volume Manager 2.5 for
Windows 2000, Volume Manager 2.4, 2.6 or 2.7 for Windows NT,
or Dell Open Manager 2.6, 2.7, or 3.0, refer to the "Upgrade
Procedures" section before continuing with this
section.

If you plan to use Volume Manager cluster disk groups
with Microsoft Cluster Server (MSCS), make sure that
MSCS is running on the target system when you install
Volume Manager 2.7 for Windows 2000. For information
on installing MSCS after the installation of Volume Manager 2.7,
see "Options," Chapter 7 in the User's Guide. Also refer to
Chapter 7 of the User's Guide if you want to install DMP
and MSCS.


1. Insert the Volume Manager 2.7 for Windows 2000 CD into the
  CD-ROM drive.

  If the installation does not begin immediately, run launch.exe
  from the CD-ROM root directory.

2. When the installation wizard screen appears, click Next
  to start the installation.

  The Select Installation Type screen appears.

3. Choose an installation type.

  - Client

    Installs the Volume Manager Client and associated
    help files.

  - Client with Remote Cluster Support

    Installs a version of the Volume Manager Client,
    remote cluster support, and associated help files.

  - Server

    Installs the Client, the Server, associated help
    files, and any additional features that your license
    key permits.

  NOTE: If you are installing Volume Manager 2.7 for Windows
  2000 on a machine that is running Windows 2000
  Professional, you will see only the first and second choices
  in the Select Installation Type screen.

4. Click Next to continue.

5. If you chose a Client installation, go to step 6 for
  further instructions. For Server installation, go to
  step 9 to continue with the instructions.

6. For a Client installation, enter the appropriate
  information in the User Information screen, and click
  Next.

7. For a Client installation, the Destination Folder
  window appears. Choose a location to install the
  product and click Next to continue.

  The default location is recommended.

8. For a Client installation only, continue with step 12.  

9. If you chose the Server installation, enter your name,
  organization, and license key in the User Information
  screen that appears, and click Next.

  The license key is the serial number that is provided
  with the product.

10. In the Select Features screen that appears next,
  choose the features you wish to install. The features
  are:

  - Volume Manager Client (must be installed)
  - Volume Manager Help Files (must be installed)
  - Volume Manager Server
  - Volume Manager 2.7 MSCS Support
  - Volume Manager 2.7 DMP Support

  To choose a feature, click on the down arrow to the left
  of its name, then select "Entire feature will be installed
  on the local hard drive" from the drop-down list.

  If you have a license for Volume Manager 2.7 for Windows
  2000 Advanced Server or Volume Manager 2.7 for Windows
  2000 Datacenter Server, choose one or both
  of the optional advanced features--MSCS Support and DMP
  Support.

  Features that are not available for installation are marked
  with a red x.

  NOTE: If you select Volume Manager 2.7 MSCS support and you
  are installing on a system WITHOUT the Microsoft Cluster
  Server installed, the installation will assume that you want
  your target system to function as a remote cluster
  administrator. In a later step, you will be prompted to enter
  the name of the remote cluster you wish to administer.

  The installation files will be installed on the local
  hard drive in the folder listed at the bottom of this
  screen.  To install in a different folder, click the
  Browse button and select another folder.

11. When you are satisfied with the installation features
   selection and the installation files location, click Next.

12. If you selected the Client with Remote Cluster Support
   or the Server and Volume Manager 2.7 MSCS support and
   MSCS was not installed on the local machine, the Cluster
   Information screen appears. Enter the name of the cluster
   you want the program to manage and click Next.

13. The Ready to Install the Application screen appears.
   Click Next again to start the installation.

14. After a screen appears with the message that the program
   has been successfully installed, click Finish.

   If you are installing the Client only, the installation
   is now complete. You will not be asked to reboot.

15. If you are installing the Server version of the software,
   an additional screen comes up to inform you that the
   system must be rebooted. Click Yes to restart now or No
   to restart later.

   The Windows 2000 Plug and Play Manager will activate
   after the reboot, indicating that it has discovered new
   hardware. You may be required to perform a second reboot
   if dynamic volumes are present on your system. Volumes
   on basic disks will not require a second reboot.

   NOTE: If you have a cluster system with the Microsoft
   Cluster Server (MSCS) software installed but MSCS was not
   running at the time of Volume Manager 2.7 for Windows
   2000 installation, Volume Manager will not install
   the cluster support. To add cluster support,
   you will need to make sure that MSCS is running on
   the computer on which you installed Volume Manager 2.7
   and then follow the instructions in the next section for
   modifying the installation. Be sure to select Volume
   Manager 2.7 MSCS Support in the Select Features screen.


          >> UPGRADE PROCEDURES<<

This section's topics are:

- Upgrading from Volume Manager 2.4, 2.6 or 2.7 for
 Windows NT

- Upgrading from Volume Manager 2.5
 for Windows 2000 and Dell OpenManage
 Array Manager

UPGRADING FROM VOLUME MANAGER 2.4, 2.6 or 2.7
FOR WINDOWS NT

Volume Manager 2.7 for Windows 2000 Product Upgrades
are available for customers who are upgrading from
Volume Manager 2.4, 2.6 or 2.7 for Windows NT to Volume
Manager 2.7 for Windows 2000. These upgrades are
available for Windows 2000 Server, Advanced Server
or Datacenter Server.

To upgrade from Volume Manager 2.4, 2.6 or 2.7 for Windows NT
to Volume Manager 2.7 for Windows 2000:

1. Contact VERITAS to obtain a Volume Manager 2.7 for Windows
  2000 Product Upgrade SKU. These are currently offered at
  no charge.

2. Before or after upgrading your server to Windows 2000 operating
  system, uninstall Volume Manager 2.4, 2.6 or 2.7 for Windows NT
  from your server.

3. Run the VMUPGRADE utility located on the Volume Manager 2.7
  for Windows 2000 installation CD in the VMUpgrade_Utility
  subdirectory. You can run the executable from the CD or copy
  it to your machine and run it.

  a. Enter your existing permanent license key for Volume Manager
     2.4, 2.6 or 2.7 for Windows NT when prompted.
  b. Enter the Volume Manager 2.7 for Windows 2000 Product Upgrade
     license key when prompted.

4. The installation of Volume Manager 2.7 for Windows 2000 can
   now be started normally. Use the product upgrade key when
   prompted.

UPGRADING FROM VOLUME MANAGER 2.5 FOR WINDOWS 2000 AND DELL
OPENMANAGE ARRAY MANAGER

The upgrade procedure is included at the beginning of the initial
installation. If you are upgrading from Volume Manager 2.5 for
Windows 2000 or Dell OpenManage Array Manager 2.6, 2.7, or 3.0,
the initial installation program is able to detect the presence of
one of these products on your machine.  A screen will come up at the
beginning of the initial install to inform you that the currently
installed product will be uninstalled first before proceeding with
the installation. Any other upgrade tasks will also be done.  

It is important to read and follow the screen prompts carefully.
During the upgrade you will be asked to reboot two or three times,
depending on your configuration. Following the screen prompts
during the Volume Manager 2.7 for Windows 2000 installation may
help minimize the number of reboots you need to do.

IMPORTANT NOTES:

1) If you installed hotfix 03 for Volume Manager 2.5 for
  Windows 2000, you will be guided through uninstalling the
  hotfix before the upgrade process to Volume Manager 2.7 for
  Windows 2000. Specify NO when prompted for reboot during the
  uninstall. All of the issues in the hotfix are now resolved in
  Volume Manager 2.7 for Windows 2000. (Incident 60198)

  If you installed other hot fixes for Volume Manager 2.5 for
  Windows 2000, manually uninstall them before beginning
  the installation for Volume Manager 2.7 for Windows 2000.

2) If you are upgrading from Dell OpenManage Array
  Manager 2.6, 2.7, or 3.0, you must select Yes to reboot
  after the Array Manager program is uninstalled.  If you
  select No, the functionality that manages array controllers
  may not be transferred to Volume Manager 2.7 for Windows 2000,
  as it normally should be. (Incidents 65976 and 67117)

3) The  server and sub-features might not be enabled on the
  "Select Features" screen of the installer When upgrading from
  Volume Manager 2.5 for Windows 2000 to Volume Manager 2.7 for
  Windows 2000. (Incident 67365)

  To solve this problem, select the features to install. It is
  important that you specify the server during the initial
  installation because you can not modify the installation later
  to add the server. You can modify the installation to add
  sub-features.

4) When upgrading from Volume Manager 2.5 for Windows 2000 to
  Volume Manager 2.7 for Windows 2000, the "VERITAS Volume Manager
  detected a previous version" screen tells you to relaunch the
  installer if you do not reboot the machine after uninstalling
  Volume Manager 2.5. (Incident 62101)

  You do not need to relaunch the installer because it
  automatically relaunches.

5) After upgrading from Volume Manager 2.5 for Windows 2000 to
  Volume Manager 2.7 for Windows 2000, you may get an error
  message stating that the "Cluster is no longer available"
  the first time that you try to move a MSCS dynamic quorum to
  the upgraded node. (Incident 69219)

  To solve this problem, refresh the Microsoft Cluster
  Administrator display, then repeat the move request. It will
  succeed this time.


     >> MODIFYING THE EXISTING INSTALLATION <<

The Volume Manager 2.7 for Windows 2000 installation engine
allows the user to add or remove specific components. To
access this feature, follow these instructions:

1. Select Start>Settings>Control Panel.

2. Double-click Add/Remove Programs.

  A list of installed products appears, one of which
  will be Volume Manager.

3. Click to select VERITAS Volume Manager 2.7 for Windows
  2000, and then click the Change button.

  The Application Maintenance screen comes up with three
  options:

  a. Modify
  b. Repair
  c. Remove

4. Select Modify and click Next.

5. The Select Installation Type screen appears. Choose an
  installation type.

  - Client

    Installs the Volume Manager 2.7 for Windows 2000 Client
    and associated help files.

  - Client with Remote Cluster Support

    Installs a version of the Volume Manager 2.7 for Windows
    2000 Client, remote cluster support, and associated help files.

  - Server

    Installs the Client, the Server, associated help
    files, and any additional features that your license
    key permits.

6. For the Client only installation type, complete
  the following:
 
  a. The User Information screen appears. Enter  
     the appropriate information and click Next.

  b. The Destination Folder screen comes up. Select
     a destination for the program's files and
     click Next.

  c. The Ready to Modify screen appears. Click Next
     to start the modification process.

  d. Click Finish to complete the process.

7. The Client with Remote Cluster Support type has the
  same steps as listed for the Client only type except
  that an extra step is added before step c to allow you
  to enter the name of the cluster that will be remotely
  administered. The Cluster Information screen appears
  in this extra step.
 
8. For a Server installation, complete the following
  steps:

  a. The User Information screen appears. Enter the
     appropriate information, including the product
     license key (serial number), and click Next.

  b. The Select Features screen comes up. Select the
     desired features and click Next.
   
  c. The Destination Folder comes up. Select
     a destination for the program's files and
     click Next.

  d. If you selected Volume Manager 2.7 MSCS support
     and MSCS was not installed on the local machine,
     the Cluster Information screen appears. Enter the
     name of the cluster you want the program to manage
     and click Next.

  e. The Ready to Modify screen appears. Click Next
     to start the modification process.

  f. Click Finish to complete the process.

9. If you selected the Server installation type, an
  additional screen comes up to inform you that the
  system must be rebooted. Click Yes to restart now
  or No to restart later.

   
        >> REPAIRING THE INSTALLATION <<

If the installation fails to install the product properly or
there are errors when you start to use the product, a repair
of the existing installation may resolve the situation. To
repair your installation, follow the steps outlined below:

1. Select Start>Settings>Control Panel.

2. Double-click Add/Remove Programs.

  A list of installed products appears, one of which
  will be Volume Manager 2.7 for Windows 2000.

3. Click to select VERITAS Volume Manager 2.7 for Windows
  2000, and then click the Change button.

  The Application Maintenance screen comes up with three
  options:

  a. Modify
  b. Repair
  c. Remove

4. Select Repair and click Next.

5. Select Next again to start the repair.

  The installation program will now reinstall the product
  with the options that were chosen during the initial
  installation (installation type, destination path, and
  so forth).

6. Click Finish to complete the repair process.

  You may be required to reboot for the installation
  settings to take effect. If problems still persist,
  contact VERITAS Vsupport for technical support services.

  For contact numbers, see:

      http://support.veritas.com


         >> UNINSTALLING THE PRODUCT <<

To uninstall Volume Manager 2.7 for Windows 2000, follow the
steps listed below:


1. Select Start>Settings>Control Panel.

2. Double-click Add/Remove Programs.

   A list of installed products appears, one of which
   will be Volume Manager 2.7 for Windows 2000.

3. Click to select VERITAS Volume Manager 2.7 for Windows
  2000, and then click the Remove button.

  NOTE: If you uninstall Volume Manager 2.7, you may not be able
  to access all its dynamic volumes. Also, if the system
  functioned as part of a Microsoft Cluster, any Volume Manager
  Disk Group resources will NOT be accessible after the uninstall.

  A screen appears to confirm that you want to remove the
  program.

4. Click Yes to remove the program.

  At the end of the removal process, you are asked to reboot.

5. Click Yes to reboot.

  The system reboots to restore Disk Management, the default
  disk and volume manager that comes with Windows 2000. Any
  dynamic volumes that have advanced features that are not
  supported by Disk Management will not be accessible.


III. ISSUES

1) Installation Issues

  - The license cannot be installed correctly through
    the Terminal Server. (Incident 65668)

    You will need to install Volume Manager 2.7 for
    Windows 2000 locally.  The license does not
    install properly if you try to install the
    program remotely through the Terminal Server.

  - In the installation Select Features screen, not all
    options displayed in the drop-down list work.
    (Incident 61480)

    When you select a feature in the installation Select  
    Features screen, an options drop-down list displays.  
    In this list, the option "Feature will be installed
    when required" does not work. In every case, you need
    to select "Entire feature will be installed on local
    hard drive" when using this drop-down list.
   
  - A second reboot may be required after an initial
    installation of Volume Manager 2.7 for Windows 2000
    if dynamic disks already exist on the system.
    (Incident 33687)

    Plug and Play may request a second reboot after an
    initial install of Volume Manager 2.7 for Windows
    2000 if dynamic disks from another Volume Manager program
    or Disk Management are present on a system. If no dynamic
    disks are present, Plug and Play will not request another
    reboot.

  - If you upgrade from Volume Manager 2.5 for Windows 2000
    with Service Pack 1 installed and then install Volume
    Manager 2.7 for Windows 2000 Client only, Disk Management
    is not enabled on the local machine after the installa-
    tion. (Incident 67005)

    The workaround is to simply reboot the machine, and
    Disk Management functionality will be available.  

  - Installing the English version of Volume Manager 2.7
    for Windows 2000 on a machine running a Japanese
    version of Windows 2000:

    a. Insert the Volume Manager 2.7 for Windows 2000 CD into
       the CD-ROM drive.
   
    b. Use Cancel to cancel the automated installation
       process. The automated process installs the
       program in the same language version as the
       operating system that is installed on the machine.

    c. On the CD-ROM drive, change directories to the
       VM527\i386\ENG folder.

    d. Run SETUP.MSI to install the English version of the
       program.

  - If you uninstall a Volume Manager 2.7 for Windows 2000
    server sub-feature, then uninstall the server, you get an
    "error 1402" error message and Volume Manager 2.7 for Windows
    2000 will not run. (Incident 67409)

    To resolve this problem, do a complete uninstall of
    Volume Manager 2.7 for Windows 2000 and reboot the machine.
    Reinstall Volume Manager 2.7 for Windows 2000 and specify
    the server features to run on your machine.

  - Sometimes using the Back button can lock up the installation
    process. (Incident 65651)

    The solution to this problem is to exit the installation
    and begin a new installation.
 
2) You are denied access or get an error message when you
  try to connect to a remote computer.

  A) Most common situation

     If from within Volume Manager 2.7 for Windows 2000,
     you attempt to connect to a remote computer but are
     denied access, your situation probably falls under one
     of the two following  conditions:

     - You are logged onto a local server that is not in
       any domain.

     - You are logged onto a domain, but that domain does
       not contain the remote server. Also, your domain does
       not have a trust relationship with the domain that the
       remote server is in.

     The workaround in this situation is to create an account
     that has the same administrator name and password as the
     remote computer's and then use that account to log onto
     the local machine.

  B) "Connection Failed" message

      Occasionally, when you are attempting to connect to a
      remote computer, you may get the error message,
      "Connection Failed." Two situations exist where this
      message may come up: 1) the server you are trying to
      connect to is offline, or 2) you mistyped the server
      name and the Windows 2000 operating system cannot find
      the server.

  For more information on remote connection requirements, please
  refer to Chapter 6, "Additional Procedures," "Remote System
  Management" section, in the VERITAS Volume Manager 2.7 for
  Windows 2000 User's Guide or online help.

3) A hardware disk array is identified as a performance hot spot.

  A hardware disk array can be identified as a performance
  hot spot when it receives a majority of the disk I/O in the
  system. However, that does not necessarily affect performance
  since it may be able to handle more I/O than regular hard
  disks.

  It is recommended that if you have a storage configuration
  of disks of varying capabilities, you should compare the
  activities of disks with similar characteristics, for
  example, hardware RAID with hardware RAID, a regular disk
  with a regular disk.

  For more information on hot-spot detection, please refer
  to Chapter 6, "Additional Procedures," "Performance Tuning"
  section, in the VERITAS Volume Manager 2.7 for Windows 2000
  User's Guide or online help.

4) Problem that some cluster-aware applications do not recognize
  a Volume Manager cluster resource.

  Our testing has determined that some cluster-aware applications
  require additional configuration before utilizing Volume Manager
  cluster disk groups. These additional configuration procedures
  are addressed in the VERITAS Vsupport Knowledge Base for some of
  the more common cluster-aware applications. The Knowledge Base
  can be accessed at:

http://support.veritas.com

5) Volume Manager 2.7 for Windows 2000 can create cluster disk
  group resources on a local SCSI bus only if the bus does not
  have the boot volume on it. (Incident 46690)

  It is not possible to upgrade disks on the local bus containing
  the boot volume to cluster disk groups, but disks on any other
  SCSI bus on a cluster node can be upgraded. If multiple SCSI
  buses are present, the administrator must take care to use only
  those that are shared when creating Volume Manager disk group
  cluster resources.

6) The Volume Manager 2.7 for Windows 2000 MSCS support feature
  protects users from upgrading a cluster's basic quorum disk or
  other disks used as MSCS physical disk resources to a
  dynamic group. (Incident 62691)

  However, the protection is enabled only while MSCS is
  running. When MSCS is stopped, take special care not to
  upgrade basic disks that are Physical Disk resources used
  by MSCS.

7) If you have a boot volume that has been mirrored and then
  extended, the boot mirror can cause problems. (Incident 46940)

  If you intend to break a boot mirror, after having extended
  the volume, you must reboot before breaking the mirror.

8) JMR Fibre JBOD disk arrays will not be supported with
  DMP in this release. (Incident 57292)

  JMR Fibre JBOD disk arrays do not fail over properly.
  It is recommended for this release that the user not
  use this type of array.

9) With DMP, if you have a situation where only a single path
  is available to the disk storage and that path fails,
  restoring the path does not allow you to perform any
  operations on dynamic disks except revert to basic.
  (Incident 62683)
   
  In order to recover from this, stop the service by using
  the command net stop vxsvc, and then restart the Volume
  Manager console.

10) When you move a group that contains a physical disk resource,
   a rescan must be performed on both nodes to reflect the
   current ownership and correct state of the disks and volumes
   that are part of that resource. (Incident 55385)

11) It is recommended that no more than three Command Line windows
   perform Volume Manager operations at the same time. Doing so
   may result in latency issues and limited functionality.
   (Incidents 63169, 63248, and 63250)

12) Compaq's driver installation overwrites some DMP registry keys.  
   
   User must run the Repair option for Volume Manager 2.7 for
   Windows 2000 after installing, reinstalling, or upgrading
   the Compaq HBA driver.

13) Array Manager functionality is not available when you connect
   remotely from a Volume Manager 2.7 for Windows 2000 Client
   that is in a different language than the server machine.
   (Incident 65648)
 
   If you connect a Volume Manager 2.7 Japanese Client to a server
   with Array Manager and right-click Array Manager storage
   objects, no context menus are displayed. You will need to
   run a Volume Manager 2.7 for Windows 2000 English Client with
   the Array Manager program, which is available only in English.

14) The Volume Manager 2.7 for Windows 2000 service may take a
   while to come back up again after it is stopped from the
   command window while the console is running. (Incident 52598)

   If you use the command window to stop the Volume Manager 2.7
   for Windows 2000 service (with the command net stop vxsvc)
   while the Volume Manager 2.7 console is running and then close
   the console and try to bring up the program again, it may not
   function properly. To solve the problem, simply reboot the
   system.
   
15) With DMP, when removing both paths, the SCSI miniport freezes
   and paths that are added back are not recognized.
   (Incident 66188)

   To solve the problem:

   a) Access the Device Manager and locate the SCSI and RAID
      controllers.

   b) Right-click each controller individually to bring up a
      context menu and select the command to disable each one.

   c) Reenable the cards.

      The drives will show up again in the Volume Manager
      2.7 for Windows 2000 GUI.
   

16) With DMP, when Path 1 to a basic disk is in a failed state, the
   user is unable to create, delete, or format volumes on the disk.
   The disk also cannot be upgraded to dynamic. I/O is not
   affected; data on the volume is still accessible.
   (Incident 51673)

   To solve this problem, repair or replace Path 1.

17) Basic disks that are set up as MSCS physical disk resources
   should not be upgraded to dynamic disks. (Incident 62691)

   When the Volume Manager 2.7 for Windows 2000 GUI is managing
   a local MSCS system, the user is unable to upgrade basic
   disks that are used as physical disk  resources. However,
   when the Volume Manager 2.7  GUI is managing an MSCS system
   from a remote machine, the program cannot prevent the user
   from upgrading these basic disks. When upgrading a basic
   disk to dynamic from a remote machine, the user must make
   sure the disk is not used as an MSCS physical disk resource.
   Failure to do so will cause the physical disk resource to fail.

18) Memory.dmp file is missing or contains corrupted data when
   a system with mirror boot drives crashes. (Incident 65595)

   In this situation, the Memory.dmp file is either missing or
   has an error message. The fix has been made so that the
   Memory.dmp file works correctly after a system with a
   mirrored boot drive has crashed.

19) The "Reconnect at next start of application" option does not
   work if the Volume Manager 2.7 for Windows 2000 server is
   not installed on your machine. (Incident 67492)

   When you connect to a server, you can specify the
   auto-reconnect option, but you will not be automatically
   reconnected to the server the next time that you start the
   application. (See Volume Manager 2.7 for Windows 2000
   Users Guide, Chapter 6, "Connecting to a Remote Computer"
   section).

   There are 2 solutions for a machine with only the Volume
   Manager 2.7 for Windows 2000 client installed:
   A) Do not specify auto-reconnection. You can manually connect
      to the appropriate server whenever you start the
      application, or
   B) Specify auto-reconnection. Connecting to any server causes
      the machine to be automatically connected to the server for
      which you specified the auto-reconnect option.
   
20) Occasionally Volume Manager incorrectly reports that one or
   more volumes in a disk group are in use and does not allow
   deporting of the disk group. (Incident 65987)

   In the Volume Manager GUI, sometimes the user is prevented
   from deporting a disk group even though its volumes are not
   in use by any application. Volume Manager returns the error
   message "One of the volumes of this dynamic group is
   currently in use. Please close applications and try again."

   This situation occurs with certain servers and disk arrays.

   To provide a fix for the situation, now when Volume Manager
   determines that one or more volumes in a disk group are
   in use, it allows the user the capability of force deporting
   the disk group.  The following message comes up:

   One or more volumes are in use. You can force deport the
   disk group by choosing the "Yes" button below.

   The force deport operation can also be done through a new
   command line force option, vxdg deport -g<diskgroupName> -f.

   In the command line, when you try to deport a disk group
   with one or more volumes apparently in use, Volume
   Manager will fail the operation, as shown in the example
   below.

   vxdg deport -gDynamicGroup
   Failed to complete the operation...

   You can then force the deport by using the force option as
   shown in the next example.

   vxdg deport -gDynamicGroup -f
   Successfully deported disk groups DYNAMICGROUP

   You can also use:

   vxassist deport -gDynamicGroup -f

   NOTE: Before deporting the disk group, the user should try to
   make sure that the disk group is not actually being used by
   any application.

21) MSCS Cluster failover may take an extended amount of time
   when a disk in the cluster disk group containing the Quorum
   is offline, followed by a loss of power on the controlling
   server. (Example: A plex fails in a 3 way mirror, which is
   part of the dynamic Quorum disk, power is then lost to the
   controlling server.

22) Some corrections or updates for printed documentation text

   - Minor changes were made in the installation procedures after
     the User's Guide and Quick Installation Guide were sent
     for printing.  This Readme has an accurate description of
     the installation procedures.

   - The User's Guide states that you can create 32 logical drives
     on an extended partition. You actually can create 64
     logical drives.

   - The User's Guide states that you can extend only an NTFS
     volume. You actually can extend any dynamic spanned volume
     that has no file system on it.

   - In the User's Guide, there are some references where the
     Windows 2000 Professional operating system and mirroring are
     discussed. In previous versions of Volume Manager for
     Windows, you could install Volume Manager Server software
     on a Windows 2000 Professional machine and create dynamic
     volumes.  In Volume Manager 2.7 for Windows 2000, only the
     Volume Manager Client can run on a Windows 2000 Professional
     machine, so these references to mirroring on a Professional
     machine no longer apply.

   - The section "Partitioned Shared Storage," in Chapter 6 of
     the User's Guide describes a sample script and an
     associated readme file, which are located in a
     Sample_Script subdirectory in the directory where the
     Volume Manager files are installed. There is no Sample_Script
     subdirectory.  (Incident 68494)

     The sample script and the readme file that accompanies it
     are on the Volume Manager 2.7  for Windows 2000 installation
     CD in the Sample_Script subdirectory. You can run the script
     from the CD or copy it to your machine and run it.


   
NOTES

Portions of the program code related to the grid control
in the Statistics View were provided by Chris Maunder,
(c) Chris Maunder, 1998.

Some cryptographic code in this product is derived from the SSLeay
library, copyright 1995-1997 by Eric Young (eay@cryptsoft.com).
All rights reserved.


Attachments

VM2K27_240496.exe (15.1 MBytes)

Supplemental Materials

SourceiTools
Value60198
DescriptionInstall procedure must remove any hotfixes present on target system

SourceiTools
Value65976
DescriptionArrays icon disappeared in tree view after Marble 3.0/2.71 is upgraded to VM527

SourceiTools
Value67117
DescriptionMisleading instructions displayed in VM527 upgrade setup screen after entering license key information

SourceiTools
Value67365
Description5.25SP1 'upgrades', key only enables client/help files, not server files at install

SourceiTools
Value62101
DescriptionINSTALLER: after removing 5.25, MSI auto-launches to continue but screen says user must manually restart

SourceiTools
Value69219
Descriptioncluster fails when moving dynamic quorum after upgrade from VM525 to VM527

SourceiTools
Value65668
DescriptionLicense is not installed correctly via terminal server

SourceiTools
Value61480
Description'Feature will be installed when required' does not install server

SourceiTools
Value33687
Description'cmd' statements for default attributes, and '-default' option for hacf

SourceiTools
Value67005
Description'selected feature is not available as a service' on client only installs after 'upgrading from 5.25GASP1

SourceiTools
Value67409
Descriptioninstall full server, remove DMP then remove server renders '1402 could not access key' error [Registry][dmp]

SourceiTools
Value65651
DescriptionINSTALLER: clicking on back will loss all functionality during install & no longer able to install

SourceiTools
Value46690
DescriptionA local disk can be upgraded to cluster dynamic disk

SourceiTools
Value62691
DescriptionNeed to prevent upgrade physical disk resource from a remote amconosole.

SourceiTools
Value46940
DescriptionBlue screen when you break a mirror with system and boot on same volume after it has been extended

SourceiTools
Value57292
Descriptionemulex LP8000 are not failing over on jmr fiber jbod

SourceiTools
Value62683
Descriptionfailing a path to a dynamic group only gives the option to revert to basic

SourceiTools
Value55385
DescriptionMSCS basic quorum disk shows as unreadable/unknown in amconsole

SourceiTools
Value63169
DescriptionCLI: stripe creation in command line takes excessive time and reports false failure even though it was successful.

SourceiTools
Value63248
DescriptionCLI: creating five RAID5 volumes at command line level will auto assign 1 volume with a drive letter without asking for it

SourceiTools
Value63250
DescriptionCLI: command line creating of RAID5 vol will report false failure in CLI window, but GUI will show all vols created

SourceiTools
Value65648
DescriptionMenu options do not popup when right clicked on array group when VM527J remotely connected to Marble2.5 server

SourceiTools
Value52598
DescriptionVxSvc hangs when being stopped gracefully while amconsole alive

SourceiTools
Value66188
DescriptionWhen removing both paths the scsi miniport freezes

SourceiTools
Value51673
DescriptionFormat fails when primary path is removed to basic disk but not in Dynamic disk

SourceiTools
Value65595
DescriptionMemory Dump file is not created or corrupted if boot volume is mirrored

SourceiTools
Value67492
DescriptionClient-only does not reconnect automatically until manually connected to server

SourceiTools
Value65987
Descriptionin-use error pops-up during deporting a disk group

SourceiTools
Value68494
DescriptionOld files installed into Sample Script directory


Legacy ID



240496


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


Terms of use for this information are found in Legal Notices