Deleted job, Orphaned disk file

[ziceman]

I did a one-off backup of a specific disk on a VM. Once completed, the resulting size of the file was going to be unmanageable for the purposes needed. I subsequently deleted the backup Job and neglected to select "Delete from Disk".

Now, under my Home panel Backups listing, I have Disk (Orphaned) - and the .vmb and the big .vbk file are still in the repository under the named job folder.

I just chose "Delete" (not Delete from Disk), so the specific job is no longer listed under Jobs > Backup. There is now a Disk ?(Orphaned) under Backups, and the folder w/backup data is still in the Repository under the original (deleted) job name folder.


The original backup job is now not listed anywhere at all in the Veeam product interface.

The only remnant is the "unamed" Orphaned disk listing under Backups. Right-clicking on this gives no option to delete or delete from disk.

[mjr.epicfail]

You can just delete the data from the disk manually.
then rescan the repository.

If its still listed, try right clicking it with the "CTRL" key pressed. It will keep you an extra option, delete from configuration.

[ziceman]

CTRL-clicking on the Orphaned disk does not give me any more options.

I was thinking that I could just delete the data from the disk manually at this point - but I am always wary of doing this with Veeam. Seems to be a no-no, in most cases.

If I delete from disk and re-scan the repo, will the Orphaned item go away?

[mjr.epicfail]

hmm, okay.

The way this works is, you have data on your repository.
Veeam does an inventory and saves this in the configuration database.
If the file does not exist anymore, this should give you a warning that it doesnt exist anymore. For orphaned data I would expect this to just disappear because there is no relationship to anything anymore.
If unsure, you could always open a supportcase.

[ziceman]

Yeah. It was a bonehead move for me to just Delete the job instead of Delete from Disk. Some prompt came up that referenced "orphaned", but I did not give a crap about this particular one-off backup. So, I stupidly ignored it.

Seems, however, that this would not be an entirely unprecedented condition - so I was thinking there would a known fix.