Summary
When running a Windows block level backup job the job fails with error "Failed to get the bitmap for vol"
Symptoms
When running a DPX Block level backup job the job fails with errors:
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: Failed to get the bitmap for vol(\\?\Volume{33079f76-722a-4607-9347-c9e075745712}\) rc(0xfffff358 : The timestamp provided were not correct)
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: HotSpotSnapShot::do_post_snapshot_settings:get_cj_fname failed vol(\\?\Volume{33079f76-722a-4607-9347-c9e075745712}\) rc(-201)
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: Failed to do postsnapshot settings for volume (E:) rc(-3)
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: MsSnapShot::backup_components:find_and_update_snapshot_properties error(-6)
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: BACKUP::backup_components failed rc(-11)
Tue Mar 06 02:08:39 2018 SNBSNP3069E 9380: Failed to backup the applications / disk ( RC(-16)
Tue Mar 06 02:08:39 2018 SNBAPH_381E Exception in message (BACKUP_VSS) to module (sssnap), reqrc (-16)
Tue Mar 06 02:08:39 2018 SNBAPH_126E Func(backup_): Exception (AHException: <AHException.AHException instance at 1731222740> )
Tue Mar 06 08:08:40 2018 SNBSVH_990E APPH backup request failed with exception: An error occurred in BACKUP message processing. (rc = 21001).
Resolution
To resolve this issue a reset of the DPX Change journal on the volume in question is required in order to do this please follow these steps:
How to reset Change journal on drive for DPX:
- Open a DPX command prompt in Administrator mode ( right click run as administrator) on the failing server.
- Run disklist.exe from the DPX tools directory
- Look for the volume serial number that is failing in the job log and note the drive letter it is associated to
- Start bexsnapmgr.bat
- Select Change journal configuration
- Select the <insert drive letter> and press disable
- There is no need to enable it again as the first backups will automatically perform this operation
- Run the backup twice to make sure a new base is created and the next incremental runs correctly
If the issue continues to occur please open a case with the Catalogic Technical Support team: Open a case