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

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 address this issue, follow the steps below:
Case 1: Corrupted or Manually Removed Bitmap.dat File
1. Click on the backup job that encounters the error.
2. Edit the configuration and save it.
3. Perform an additional full backup for that job.
Case 2: Third-Party Application Deleting the Bitmap.dat File
1. Add the location of the `bitmap.dat` file (typically `<volume>\bitmap.dat`) for each configured volume to the exception list of your antivirus software.
  1. Alternatively, disable the antivirus temporarily.
2. Edit the configuration of the backup job and save it.
3. Run an additional full backup for that job.
If the issue persists despite following the above steps, please contact BDRShield support at vembu-support@vembu.com for further assistance.


    • Related Articles

    • 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 BDRShield. Cause This error arises when metadata files essential for ...

    • Issue with Incremental Change Tracking for Configured Drives

      KB ID: 103053 Description: When attempting to track incremental changes for configured drives, backups may fail with the following error: "Unable to track the incremental changes for drives configured." This error occurs when there is no bitmap ...

    • Troubleshooting - Error When Opening VMDK File

      KB ID: 105606 Summary: This knowledge base article provides guidance on resolving an error encountered while attempting to open a VMDK file, which is commonly associated with disk access from the datastore for read operations. Cause: The error ...

    • Troubleshooting Guide: BDRShield Backup Failed - Internal File System Error

      KB ID: 102180 Issue: Backup operations have failed due to an internal file system error within BDRShield. This error occurs when a specific backup job in BDRShield possesses a negative chunk file ID value, resulting in job failure. Cause: The failure ...

    • BDRShield - Release Notes

      BDRShield v9.1.0 Update 2 (Cloud) Release Date: May 25, 2026 Enhancement: Released platform-specific macOS backup agents optimized for Intel and ARM architectures. Bug Fixes: Improved file backup and restore operations by resolving issues related to ...