IT23255: DOCUMENTATION LACKS DETAILS ON LOGICAL VOLUME LAYOUT RESTRICTIONS WHEN INDEPENDENT DISKS ARE USED

APAR status

• Closed as program error.

Error description

• The current Data Protection for Virtual Environments
  documentation stipulates that independent disks are not included
  in snapshots, and the data stored on those disks are not backed
  up. The documentation does not explain that having volume
  groups split across both dependent and independent disks will
  result in recovery failures for the data which was stored on the
  dependent disks. This is because the operating system will be
  unable to mount the volume group due to the missing independent
  disk.
  
  For example, an environment has a volume group named 'datavg'.
  This volume group has two disks, /dev/sdd which is dependent and
  /dev/sdc which is independent. The volume group has a mount
  point, /opt/IBM, spread across these two disks. When an attempt
  is made to either restore the VM, or mount the backup, the
  operating system will attempt to vary on the volume group and
  mount the filesystem which fails due to the missing disk.
  
  Versions Affected:
  IBM Tivoli Storage Manager for Virtual Environments v7
  IBM Spectrum Protect for Virtual Environments v8
  
  Initial Impact: Low
  
  Additional Keywords:tsmve lvm spve
  

Local fix

• Do not split logical volumes between dependent and independent
  disks.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Data Protection for VMware versions 7.1.0-7.1.8 and          *
  * 8.1.0-8.1.4  running on Linux x86 platforms.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A VE mount operation or a File Restore operation of a backup *
  * performed with "vmprocessvmwithindependent" option will fail *
  * with ANS3108W / ANS3101E if independent disks are excluded   *
  * and LVM volumes are striped across dependent and independent *
  * disks.                                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * This issue is projected to be fixed in the Data Protection   *
  * for VMware Data Mover version 8.1.6 on Linux x86 platform.   *
  * Note 1: This is subject to change at the discretion of IBM.  *
  ****************************************************************
  

Problem conclusion

• The behavior does not fundamentally change, but the improved
  ANS3108W message text will help users and support more quickly
  understand why it was issued and what next steps are possible.
  The documentation updates for IBM Spectrum Protect
  Backup-Archive Clients Installation and User's Guide V8.1.x  and
  V7.1.x improves understanding of the considerations for using
  the vmprocessvmwithindependent option.
  
  See following websites:
  http://www-01.ibm.com/support/docview.wss?uid=swg27048955
  (Version 8.1: Updates for IBM Spectrum Protect for UNIX and
  Linux Backup-Archive Clients Installation and User's Guide)
  
  http://www-01.ibm.com/support/docview.wss?uid=swg27048956
  (Version 8.1: Updates for IBM Spectrum Protect for Windows and
  User's Guide)
  
  http://www-01.ibm.com/support/docview.wss?uid=swg27039351
  (Version 7.1: Updates for IBM Tivoli Storage Manager for UNIX
  and Linux Backup-Archive Clients Installation and User's Guide)
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg2703935
  (Version 7.1: Updates for IBM Tivoli Storage Manager for Windows
  Backup-Archive Clients Installation and User's Guide)
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM FOR VE DP V

• Fixed component ID

  5725TVEVM

Applicable component levels