Leftover VM from surebackup question

[backupquestions]

For whatever reason, Surebackup job left one of its VMs in vcenter. vmname_483323kl42jl etc... That vm has a snapshot on it labeled "veeam_surebackup_snapshot".

Am I "ok" to just right click this and remove from inventory, or is there a better way? This is the first time it has left a VM registered that was from the surebackup testing. Usually these are removed automatically.

[foggy]

Hi Alabaster, this might be the snapshot used during replica testing to protect it from changes while SureBackup (well, SureReplica actually) job is running. Could this be the case?

[backupquestions]

Hi Foggy,

I do not use replicas or surereplica. This is just a surebackup job which has one primary backup job as its source. There are over 70 vms in the job but only this one seems to have been left behind.

I am tempted to right click and remove from inventory in vcenter? Or maybe Veeam would automatically clean it next surebackup job run?

[PetrM]

Hi Alabaster,

I don't believe an orphaned VM will be removed on the next SureBackup job run.
I would recommend to contact our support team and ask them to check if you can safely remove this VM manually from inventory.

Thanks!

[foggy]

Ok, then it is a write cache redirection consequences. Feel free to remove this VM from VI.

[backupquestions]

Thanks guys. I went ahead and right clicked the orphan vm and removed from inventory, since I knew it is not the "real" vm and just the one that veeam surebackup spun up. Seemed to go away and no issues so we'll see if the next surebackup job runs ok.

Thanks!