VSA Metadata collection failed ... Offset out of range

Last post 05-03-2017, 8:49 AM by johanningk. 8 replies.
Sort Posts: Previous Next
  • VSA Metadata collection failed ... Offset out of range
    Posted: 03-10-2016, 9:43 AM

    We have a single VM that is generating an event during every backup:

    Event

    Metadata collection failed for virtual machine [VMNAME-t], Guest file browse will not be available for this virtual machine.  [Initialization from Disk failed, error=One or more errors occurred while processing the request., Offset out of range (W32.774)]

    Log vsbkp_1.log

    9108  1b50  03/10 04:44:01 764245 vsBkpDiskConfig::doLVMProcessing() - CLVM::InitializeFromDisk() call failed, error=0x80070306:{..\..\..\CommClient\VirtualServer\VMInfo\LVM.cpp[CLVM::InitializeFromDisk(193)]} + {..\..\..\CommClient\VirtualServer\VMInfo\LVM.cpp[CLVM::ReadVolumeData(551)]/W32.774.(One or more errors occurred while processing the request.)-Offset out of range}
    9108  1b50  03/10 04:44:01 764245 VSBkpWorker::CollectGranularMetadata() - LVM processing failed for VM [VMNAME-t], [Initialization from Disk failed, error=One or more errors occurred while processing the request., Offset out of range (W32.774)]
    9108  1b50  03/10 04:44:01 764245 VSBkpWorker::ProcessVM() - Guest size of VM [VMNAME-t] is not available after LVM processing. Setting VM guest size as [50162302976] bytes

    • We have two other VMs that are identicle builds that backup without any error.
    • We have performed check disk operations on the VM and found no issues.
    • We have Storage vMotioned the VM to another datastore.
    • We have tried backups via SAN and NBD mode.

    Environment:

    • CommVault Simpana 10 R2 (SP12)
    • ESX 5.1.0
    • VM Guest: Red Hat Enterprise Linux 5.11
    • CommServe/MediaAgents: Windows 2012 R2 Datacenter

    Any ideas, I have an open incident but we aren't getting very far.


    -J. Mills
    Customer, Senior Systems Engineer
    Enterprise Storage and Data Protection
    CommVault Certified Master (V10/V11)
  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 03-17-2016, 11:09 PM

    Few log lines above will say , what is the partition we are procesing. Can you please give us the partition type and name?

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 09-30-2016, 12:58 PM

    Did you ever get an answer to this.  Running into the same situation.

    v11 SP4+

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 04-21-2017, 4:49 AM

    Hello,

    how went this further? I have the same Issue with an linux VM with three Disks on V11 SP6+ and VMware:

    Disk 1 (four partitions):

    1: Linux native Partition
    2: Linux Swap
    3: Linux LVM
    4: Linux LVM

    Disk 2:

    - Linux LVM

    Disk 3:

    - Linux LVM

    Hopefully anyone has an idea, which disc/partition causes the problem and why.

    Best Regards

    Christoph 

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 04-21-2017, 11:17 AM

    Have you tried the newer Live Browse method for performing file-level browse and restore operations? This method does not require metadata collection during the backup so backups are faster and additional filesystems are also supported. Here is more information: Metadata Collection, Granular Recovery, and Live Browse.

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 04-24-2017, 8:09 AM

    Hi,

    yes, we implemented the FBR and different Subclients (Diskfilter, Linux/Windows with GRT) and it is still working but we see meta data collections warnings for some VMs. Some VMs we are not able to browse, most VMs are ok.

    Since we have the VM with the marked "Initialization from Disk failed" Error the Subclient Jobs is yellow, becaue completed with Error.

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 04-24-2017, 9:33 AM

    Is the subclient set to quiesce the VM and is the schedule setup for granular recovery?

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 04-24-2017, 9:45 AM

    Yes, quiesce is enabled and the LinuxVM-Schedule has GRT disabled for the Linux Subclient. We build Windows/Linux and Diskfilter Subclients with own Schedules and disable GRT on Linux and implement the FBR.

    Normally you can see File system metadata ceollection warnings in the Job-Details but green completed Jobs. But this error change the Jobstatus to completed with Errors.

  • Re: VSA Metadata collection failed ... Offset out of range
    Posted: 05-03-2017, 8:49 AM

    I remember a restriction w/ virtual VSA (using hotadd), that says, that the VSA's VM must reside on a datastore w/ the same Cluster/Block size as the target VM to backup for a successful granular backup. (But I might be wrong on that)

    what about backing up w/o the granular recovery information gathered at backup time, but on browse time using the FREL instead ?

    Backups are way faster, but you loose the ability to search for files since no single file index has been created ...

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.
Close
Copyright © 2017 Commvault | All Rights Reserved. | Legal | Privacy Policy