Running urbackup server 2.0.38 and on 3/6/17 upgraded to 2.1.19
This urbackup server has close to 50 client servers running incremental image backups only without issue, except for one.
Starting on 3/6/17 the incremental image backups for one volume (H:) started failing because the urbackup server could not find the parent vhd file. All of the other volumes backup successfully.
I attempted to perform a full image backup so that the incremental chaining would start fresh. Here is the output of the server log:
2017-04-07 00:36:27: ERROR: Error opening VHD file
2017-04-07 00:36:27: ERROR: Error opening Parentvhdfile "/mnt/urbackup/SERVER6/Image_H_170305-0127.vhd"
2017-04-07 00:36:27: ERROR: Error opening parent VHD
2017-04-07 00:36:27: ERROR: Error opening VHD file "/mnt/urbackup/SERVER6/170407-0036_Image_H/Image_H_170407-0036.vhd"
2017-04-07 00:36:27: ERROR: Backup failed
Server6 is 2012R2 server running the 2.1.15 urbackup client.
Do I need to move all of the backed up data for the H drive out of the urbackup data location, run a urbackupsrv remove-unknown and then run a full image backup? Or is there a way I can keep the data that is backed up (in case we need it) and get a fresh full backup?