Summary
Block backup fails with "Failed to flush the journal for vol ... rc(0xfffff355 : Journal Repository dtabase is corrupt)
Symptoms
Block level backup for a Windows client failed with this error message in the job log:----------
xxx.xx.162.155 sssnap Thu Jun 14 11:05:50 2018 SNBSNP3069E 3888: Failed to flush the journal for vol(\\?\Volume{9d1b1e23-4cb0-11e3-94e8-f01fafd87267}\) genrc(0x1) osrc(0x3a0020) rc(0xfffff355 : Journal Repository dtabase is corrupt)
xxx.xx.162.155 sssnap Thu Jun 14 11:05:50 2018 SNBSNP3069E 3888: HotSpotSnapShot::do_pre_snapshot_settings:create_chkpoint_flush rc(-1)
xxx.xx.162.155 sssnap Thu Jun 14 11:05:50 2018 SNBSNP6200E 3888: Failed to perform the pre snapshot setting for volume(F:\); rc (-3)
Resolution
The job is failing due to the change journal driver repository being corrupted, and it needs to be reset.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