browse failed to open metadata file

Last post 02-06-2012, 8:48 PM by Watson. 10 replies.
Sort Posts: Previous Next
  • browse failed to open metadata file
    Posted: 01-03-2012, 11:49 AM

    I am trying to do a browse of a virtual machine to do file level restore. However, the browse failed to drill down the volume and errors with "browse failed to open metadata faile".

     

    What should I do?

     

  • Re: browse failed to open metadata file
    Posted: 01-09-2012, 10:04 AM

    Are you sure metadata collection succeeded for that VM?  If you run a job summary report with details, you should see if metadata collection failed for that volume.  If you desperately need data off that volume, you could restore the entire VMDK, mount it and copy the necessary data.

  • Re: browse failed to open metadata file
    Posted: 01-09-2012, 11:40 AM

    Yes, I can do the restore the VMDK and then extract the files. But I want the file level retore to work as well.

     

    I will check with you suggestion to check with Job summary report. However, the job history shows the job completed successfull without errors.

     

  • Re: browse failed to open metadata file
    Posted: 01-09-2012, 11:43 AM

    OK I will try your suggestion to check job summary report.

     

     

    We did VMDK restore and extracted files required, but I need file level restore to work

  • Re: browse failed to open metadata file
    Posted: 01-09-2012, 1:11 PM

    If you view the events associated with the backup job, do you see an event like "Metadata collection failed for Virtual machine..."?

  • Re: browse failed to open metadata file
    Posted: 01-17-2012, 9:37 PM
    • zzz is not online. Last active: 12-03-2015, 7:57 PM zzz
    • Top 50 Contributor
    • Joined on 07-06-2010
    • Adept
    • Points 261

    Hi Sameer,

    Which OS does your VMware server have? Did you get this error while you were browsing other servers?

  • Re: browse failed to open metadata file
    Posted: 02-06-2012, 5:55 PM

    sameer try this

    For Linux Metadata Collection please add the below to the VSA

    Location
    Windows HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\<Instance>\
    Unix Not Applicable
    NetWare Not Applicable
    Key VirtualServer (standard)
    Value LinuxMetadataSupport (optional)
    Value Type (Windows only) DWORD
    Valid Range 0 - Default
    1 - To enable Metadata collection

    Default Value 0
    Created in Client computer on which the Virtual Server iDataAgent is installed
    Description This registry key provides the facility to explicitly collect Metadata while running Linux virtual machine backups. Note that if this key is not added, Metadata collection will not be collected though Enable Granular Recovery option is checked.
    Applies To Virtual Server iDataAgent

    Note EXT4 is currently not supported for metadata collection.

    For Windows

    Metadata collection to work the bytes per cluster needs to be 1024
    MetaData Collection is not supported for a Cluster size of 512
    You can check this using fsutil fsinfo ntfsinfo c:\
    The bytes per cluster needs to be at least 1024 bytes (e.g. 1mb)

     

  • Re: browse failed to open metadata file
    Posted: 02-06-2012, 6:17 PM

    KiwiRail01:

    sameer try this

    For Linux Metadata Collection please add the below to the VSA

    Location
    Windows HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\<Instance>\
    Unix Not Applicable
    NetWare Not Applicable
    Key VirtualServer (standard)
    Value LinuxMetadataSupport (optional)
    Value Type (Windows only) DWORD
    Valid Range 0 - Default
    1 - To enable Metadata collection

    Default Value 0
    Created in Client computer on which the Virtual Server iDataAgent is installed
    Description This registry key provides the facility to explicitly collect Metadata while running Linux virtual machine backups. Note that if this key is not added, Metadata collection will not be collected though Enable Granular Recovery option is checked.
    Applies To Virtual Server iDataAgent

    Note EXT4 is currently not supported for metadata collection.

    For Windows

    Metadata collection to work the bytes per cluster needs to be 1024
    MetaData Collection is not supported for a Cluster size of 512
    You can check this using fsutil fsinfo ntfsinfo c:\
    The bytes per cluster needs to be at least 1024 bytes (e.g. 1mb)

     

     

    Nice post. I was about to post the samething.

  • Re: browse failed to open metadata file
    Posted: 02-06-2012, 6:53 PM
    Smile
  • Re: browse failed to open metadata file
    Posted: 02-06-2012, 8:35 PM

     

    What Operating System is the Virtual Machine?

    Version 8 does not support Linux Metadata collection.

    EXT 4 is currently not supported.

    The below registry key applies to Commvault Version 9

    For Linux Metadata Collection please add the below to the VSA

    Location

    Windows HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\<Instance>\

    Unix Not Applicable

    NetWare Not Applicable

    Key VirtualServer (standard)

    Value LinuxMetadataSupport (optional)

    Value Type (Windows only) DWORD

    Valid Range 0 - Default

    1 - To enable Metadata collection

     

  • Re: browse failed to open metadata file
    Posted: 02-06-2012, 8:48 PM

     

    On the schedule or scheduled policy is Enable Granular Recovery enabled?

    On a Windows Operating System at command line can you please run the command

    fsutil fsinfo ntfsinfo c:

    Repeat command for each drive.

    What is the bytes per cluster?

    The bytes per cluster must be 1024 bytes or higer. Bytes per cluster 512 is not supported.

    You can update the cluster size with a third party tool or to retrieve files perform a container level restore and copy the files. You can also install a file system agent on the client.

    File-level restores from disk or volume-level backups should be performed only with small files. For example, restoring a 2GB file from a disk-level backup is not recommended.

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