Problem evacuating extent in SOBR

[dkleeman]

We are running VBR 9.5.0.1922. We are having problems evacuating an extent in preparation for replacing the extent with different storage.

We have moved some files manually between extents but we have not knowingly deleted any backup files. There are no backup files left in the extent that is in maintenance mode. We have performed a rescan of all extents.

Although we have moved files manually and carried out a rescan, VBR believes that some files are still in the extent that is in maintenance mode. This is evident when one looks at the viewer in the Backups section of the Home tab.

Then, when we request to 'evacuate backups' the following errors result (some info redacted):

Code: Select all

02/02/2019 17:37:36          Starting backup files evacuation
02/02/2019 17:38:22 Error    Processed 0 out of 9 backup files (9 failed)
02/02/2019 17:37:58 Error    Failed to get storage file '<path>\Backup Copy Job D2018-04-03T000000_M.vbk' 
02/02/2019 17:37:58 Error    Failed to get storage file '<path>\Backup Copy Job D2017-11-05T000000_M.vbk'
02/02/2019 17:37:58 Error    Failed to get storage file '<path>\Backup Copy Job D2018-06-03T000000_M.vbk'
02/02/2019 17:37:58 Error    Failed to get storage file '<path>\Backup Copy Job D2018-02-04T000000_M.vbk'
02/02/2019 17:37:57 Error    Failed to get storage file '<path>\Backup Copy Job D2018-05-06T000000_M.vbk'
02/02/2019 17:37:58 Error    Failed to get storage file '<path>\Backup Copy Job D2017-12-03T000000_M.vbk'
02/02/2019 17:38:11 Error    Failed to get storage file '<path>\Backup Copy Job D2018-07-01T000000_M.vbk'
02/02/2019 17:38:10 Error    Failed to get storage file '<path>\Backup Copy Job D2018-03-07T000000_M.vbk'
02/02/2019 17:38:12 Error    Unable to evacuate Backup Copy Job D2018-12-06T000000.vib from <extent name>: failed to move the full backup file this increment is dependent on.
02/02/2019 17:38:23 Error    Backup file evacuation completed

Note: some of the VBK files exist on other extents and some do not seem to be anywhere. They are all evident in the job using the viewer.

- Is it safe to remove the extent and ignore the warning about the backup files still being in place?

- How can we get the job to be in sync with reality of where the files are (and that some seem to be missing). The missing files are not my primary concern.

Thanks in advance

Daniel

[nielsengelen]

Hi Daniel, I would suggest having support assist you here to assure everything is fine before removing the extent. They should also be able to assist you with aligning the files.

[dkleeman]

We raised a case and were advised to disable the copy jobs before repeating the rescan. This allowed the rescan to proceed normally and all the file references became consistent.

It appears that rescans on SOBR should only be done with all relevant jobs disabled.

[Gostev]

Thanks, Daniel.

Just for the record, we checked with the devs and normally, it's not a requirement to disable jobs before doing SOBR rescan, so perhaps it was something else that went wrong in your case.