IC66105: WINDOWS MOUNT POINTS IN VMWARE GUESTS MAY NOT BE ACCESSIBLE DURING VCB BACKUPS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Filesystems that have Windows drive letters assigned are
    enumerated by the B/A client, but GUID based filesystems, such
    as mount points, are not.
    
    Customer/L2 Diagnostics:
    If vcbmounter is used to mount a VM on the VCB proxy system,
    Windows Explorer can be used to access the VM through the
    vcbmounter provided mountpoint.
    
    The drives and mounts will be displayed in the following
    directories within the mountpoint on the VCB proxy system:
    
    (vcbmounter mountpoint)\letters\
    (vcbmounter mountpoint)\numbers\
    
    Filesystems that have drive letters assigned to them will appear
    in the letters subdir, whereas all filesystems that have a GUID
    associated with them will appear in the numbers subdir. Mount
    points that appear only in the numbers directory will not be
    accessed by the B/A client during a proxied backup.
    
    Initial Impact: Low
    
    Additional Keywords: TSM
    

Local fix

  • Convert the mountpoint to a mapped drive or to assign the
    mountpoint a drive letter as documented earlier in the PMR.
    Additionally, an include statement with a "$" character may be
    needed.
    
    Example: (Where testmount is a mountpoint on the D: drive.)
    d$:\testmount
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Tivoli Storage Manager for Windows       *
    *                 Backup-Archive Clients                       *
    *                 Installation and User's Guide                *
    *                 for V55, V61, and V62                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: File systems that have Windows drive    *
    *                      letters assigned are enumerated by      *
    *                      the backup-archive client, but GUID     *
    *                      based filesystems, such as mount        *
    *                      points, are not.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    *
    

Problem conclusion

  • For version 5.5, in Chapter 4. Backing up your data
    at the end of the section: Using VMware Consolidated Backup,
    insert the restriction:
    
    and for version 6.1, in Chapter 4. Backing up your data
    at the end of the section: Preparing your system to use VMware
    Consolidated Backup, after Step 11 insert the restriction:
    
    Restriction:
    Windows mount points in the VMware guest are not accessible
    with VMware consolidated backups. To backup Windows mount
    points, convert the mount point to a mapped drive or assign a
    drive letter to the mount point. When a mount point is mapped
    to a drive, it might also be necessary to use the following
    syntax when adding an include statement for that volume:
         D$\testmount\...\file.one
    
    For version 6.2, Chapter 4. Backing up your data
    in section: Backing up off-host VMware virtual machine data,
    after Step 14 insert the restriction:
    
    Restriction:
    The original names of Windows mount points in the VMware guest,
    which do not have a drive letter assignment,  cannot be
    determined when running a Tivoli Storage Manager VMware off-host
    
    backup using the BACKUP VM command.  These mount points are
    backed up to a filespace name. The name includes a number
    assignment that is provided by the VMware vStorage APIs. The
    filespace names, created for mount points, do not correspond to
    
    the actual volume mount points. Therefore, restoring these
    backups require selecting an alternate restore location. To
    support a restore to the original location from within the
    guest machine for these Windows mount points, convert the mount
    
    point to a mapped drive or assign a drive letter to the mount
    point.
    
    When using mount points without drive letter assignments,
    use the following syntax when adding an include statement for
    that volume:
      exclude \\machine\3$\dir1\...\*.doc
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC66105

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    61W

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-07

  • Closed date

    2010-03-30

  • Last modified date

    2010-03-30

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

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

Publications Referenced
SC32014601 SC23979200 SC23979203    

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC66105

Modified date:

2010-03-30

Translate my page

Machine Translation

Content navigation