VSA VCB Mounter issue with LSI Logic SAS scsi controller

Last post 11-01-2010, 3:08 PM by mscherer. 4 replies.
Sort Posts: Previous Next
  • VSA VCB Mounter issue with LSI Logic SAS scsi controller
    Posted: 11-01-2010, 12:37 PM

    Was getting some VCB Mounter errors on a few machines and have been struggling to determine why.  To provide some environmental info, we're running the VSA agent on virtual machine proxies using hotadd mode.  All machines are HW version 7.  The only correlation I've found so far is that the VM backups that show the VCB mounter error all appear to be Windows Server 2008 R2 machines with a LSI Logic SAS SCSI controller.  Other 2008 R2 VMs that have an LSI Logic Parallel SCSI controller are backed up by the same VSA proxies without issue.  Has anybody else encountered this?  It appears that it doesn't matter if the VSA proxy server has a LSI Logic SAS controller on it or not - the VCB mounter error still appears.

  • Re: VSA VCB Mounter issue with LSI Logic SAS scsi controller
    Posted: 11-01-2010, 12:40 PM

    @mscherer - We have seen this when ESX version 4.1 is used as well. Please follow the following procedure using the vSphere Client.


    If this is VADP on 4.1 this has to do with windows 2008 application level quiescing.

    Application consistent quiescing of Windows 2008 virtual machines is only available when those virtual
    machines are created in vSphere 4.1. Virtual machines created in vSphere 4.0 can be updated to enable
    application consistent quiescing by modifying a virtual machine’s enableUUID attribute.

    Since application level VSS quiescing is not available in VDDK 1.1.1 (need 1.2 per the 1.2 release notes) I believe the “enableUUID” parameter is causing the quiesce to fail (thus the access rights error)

     (so we need to disable the “disk.EnableUUID” feature to get this to work)

    Disable Windows 2008 Virtual Machine Application Consistent Quiescing
    1 Start the vSphere Client, and log in to a vCenter Server.
    2 Select Virtual Machines and Templates and click the Virtual Machines tab.
    3 Right-click the Windows 2008 virtual machine for which you are enabling the disk UUID attribute, and
    select Power > Power Off.
    The virtual machine powers off.
    4 Right-click the virtual machine, and click Edit Settings.
    5 Click the Options tab, and select the General entry in the settings column.
    6 Click Configuration Parameters...
    The Configuration Paramters window appears.
    Sort by name
    If the row disk.EnableUUID is listed it will be set to true
    Highlight true and change to false

    If not listed:

    7 Click Add Row.
    8 In the Name column, enter disk.EnableUUID.
    9 In the Value column, enter FALSE.
    10 Click OK and click Save.
    11 Power on the virtual machine.


    Client Team Supervisor - Focus on Virtualization
    Follow me on Twitter - @wfarinella
  • Re: VSA VCB Mounter issue with LSI Logic SAS scsi controller
    Posted: 11-01-2010, 1:57 PM



    Thanks for your response.  Do you know if the CommVault VSA proxy supports VDDK 1.2?  If so, would updating the VSA proxies to VDDK 1.2 resolve the issue rather than disabling the disk.EnableUUID parameter?

  • Re: VSA VCB Mounter issue with LSI Logic SAS scsi controller
    Posted: 11-01-2010, 2:53 PM

    CV does support VDDK 1.2.   The key line in the VMware KB is is that these VMs need to be created in 4.1.  If they are then VDDK 1.2 may resolve the issue, otherwise the attribute change will be required.

  • Re: VSA VCB Mounter issue with LSI Logic SAS scsi controller
    Posted: 11-01-2010, 3:08 PM

    Thanks, Vincenzo.  We're only seeing this issue with Server 2008/2008 R2 VMs created in 4.1.  We've had no issue backing up existing Server 2008/2008 R2 VMs created in 4.0 using the CommVault VSA agent and VDDK 1.1.1, without needing to make the attribute change.  I'd prefer no to have to power off production VMs to make an attribute change to make VDDK 1.1.1 work if instead I can install VDDK 1.2 to get these machines backed up.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy