Resolving Metadata File Processing Errors During Restore

Resolving Metadata File Processing Errors During Restore

KB ID: 106074

Issue Overview

The error "Unable to process metadata files, so cannot proceed with restore" occurs during tree or disk listing operations while attempting a restore in BDRSuite.

Cause

This error arises when metadata files essential for the restore process are either incomplete or inaccessible. Common reasons include:

  • Network drop during the writing of metadata files.
  • Socket interruption during metadata data transfer.
  • Insufficient permissions for BDRSuite to open or write metadata files.
  • File corruption or missing files in the backup storage location.

Resolution

Follow these steps to address and resolve the issue:

Verify File Permissions

Ensure that the BDRSuite service has the necessary permissions to access or open metadata files at the storage location.
  1. Verify user permissions for the storage location and grant access if required.

Check File Integrity

Run a disk integrity check on the storage location to ensure the files are not corrupted.
Use the chkdsk command:
chkdsk <drive_letter>: /f /r
Replace <drive_letter> with the appropriate drive where backup data is stored.

Ensure File Availability

Verify that all necessary metadata files are present in the backup storage location. Review the restore logs for any errors indicating missing metadata files. The logs can be found at:
InstallationLocation\log\ClientName\BackupJobName\Restore\Restore.log
If the issue persists, contact BDRSuite Support for assistance.

Resolve Network or Socket Issues

Investigate and resolve any network stability issues that might disrupt data transfer during metadata processing. Consider:
  1. Checking the network logs.
  2. Ensuring sufficient bandwidth and connectivity during backups.

Conclusion

By ensuring permissions, checking file integrity, and addressing network issues, you can resolve the error and proceed with the restore. If the issue persists or metadata files are unavailable, reach out to BDRSuite Support for advanced troubleshooting.


    • Related Articles

    • Resolving "Tracking MetaData file for drive D is empty or inaccessible" Error

      KB ID: 115106 Cause: This error may occur when the `bitmap.dat` file, associated with the configured backup volume, is either inaccessible, corrupted, manually removed, or deleted by a third-party application, such as antivirus software. Solution: To ...

    • Troubleshooting Checkpoint Creation Errors in KVM Environment

      KB ID: 221004 Cause: The KB article focuses on problems that occur specifically within the KVM hypervisor environment during the creation of a checkpoint for a virtual machine. These errors can disrupt normal operations and may signify underlying ...

    • Causes of VM Restore Failures in BDRSuite

      KB ID: 53 Cause: VM restore failures occur without an error message in the restore report. Solution: Typically, a proper error message is available in the restore report for VM restore failures. However, in rare scenarios where the exact error is not ...

    • File-Level Recovery: Restore Individual Files & Folders from VM Backup

      With the File Level Recovery option from the BDRSuite Backup Server, you can instantly restore individual files/folders from the backed-up VM(s) without restoring the entire VM. Step 1: Choose Host and Restore Type Choose a VM/ Host that you wish to ...

    • File-Level Recovery: Restore Individual Files & Folders from Disk Backup

      With the File Level Recovery option from the BDRSuite Backup Server, you can instantly restore individual files/folders from the backed-up VM(s)/ Disk(s) without restoring the entire VM(s)/ Disk(s). Step 1: Choose Host and Restore Type Choose a VM/ ...