Re-register Restore Points where the 'Forget' option was used

[rleon]

Hi all,
We have a VMware backup job that backs up multiple VMs.
The Repository has "Use Per-VM backup files" enabled, so we can see the individual .vbk and .vib files of the different VMs.

For some reason, someone from our team moved a single VM's .vbk and .vib files (aka its entire backup-chain of files) away.
The "Forget all unavailable backups" option was then used on this VM's missing Restore Point files, per the steps from:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

We have since found the moved VM's .vbk and .vib files and have placed them back into the backup job's folder where they were originally located.
I.e.: together with the other .vbk .vib files of the other VMs from the same job, as well as the .vbm file.
We tried rescanning the Repository, but the returned VM's Restore Points just don't seem to want to reappear in Backups > Disk > Job, this would cause the next backup for this VM to become a .vbk instead of .vib, which is not what we currently want.
Is there a procedure to "re-register" a "forgotten" VM's Restore Points back with its original Job's folder in the Repository?

Thanks for the help!

[HannesK]

Hello,
are the backups in disk -> imported now? If not, manual import should work. Once that is done, map backups connects a job to existing backups

Best regards,
Hannes

[rleon]

Hi Hannes,

No, said VM's Restore Point does not appear in Disk > Imported.
But I went ahead with Job > Storage > Map backup anyway.
I map the job back to itself. It gives a warning "Selected backup is already in use by the following job: <name of the same job itself>. Do you want to map it to this job instead?"
I clicked yes.
When I go back to Disk > Job, the Restore Points for that VM is still not registered. In short, nothing changed, still the same status as the opening post.

Short summary of the entire issue again:
1. .vbk of a single VM is cut-and-pasted away from Job's folder. Other VM's .vbks in the same folder are left alone.
2. Told Veeam to "Forget" those Restore Points.
3. Move the .vbk back to the Job's folder.
4. Rescan Repo, nothing. Remap Job back to itself, still nothing.

Need to find a way to tell Veeam to "un-forget" what we did, so that the backup-chain of that VM can continue when the Job next runs.

Thanks!

[HannesK]

I'm missing the "import backup" in the list.

[rleon]

Hi Hannes,

I see what you mean now. This time, after the step where we move the VM's .vbk files back to the Job's folder, we ran manual import.
The VM's Restore Points now appear as "Disk (Imported)" > "JobName_imported".
From here, we tried Rescan Repo, and also Remap the Job back to itself, but this VM's "imported" status remains. Aka, it is still not "welcomed back" or "reintegrated back" in to the original place, which is "Disk" > "Jobname".
Inside the Job's "Map backup" screen, nothing really stands out as "I'm the imported backup of that single VM, select me and let me rejoin this job!". We just get a list of Jobnames, including the same job itself.

[foggy]

Looks like the VBM file for this job doesn't contain information about this VM anymore.

[rleon]

Some might even say... that the VBM file has forgotten this VM.

[rleon]

I heard from a local Veeam associate that v12 has something that allows vbk/vib files to migrate between jobs that already have VMs of their own, while allowing the migrated backup-chains to continue their incrementals.
Sounds like that could be the official solution to this VBM problem.
Meanwhile, with v11, it appears that I might have to solve this problem with some VBM tinkering voodoo.