No restore points found

[Zew]

I'm having this issue and I have no clue why...
I found this thread,: veeam-backup-replication-f2/no-restore- ... 64413.html
Old, no good info as it retains to the old copy method.

Info: Veeam Build 12.3.1.1139
Everything was working fine, 2 ESXi servers, 1 vCenter, 1 Veeam VM, one USB passthrough HDD for backup copy job targets. Everything was working fine.

What happened?
vCenter needed to be rebuilt, so vCenter was rebuild, same hostname, same IP, ESXi hosts readded. I am well aware of the MoreFID, and since my Veeam build is upgraded from still uses MS SQLExpress.
Did my usual trick to update the VM-ID in Veeam DB using the trick I posted about in my blog, test and run all regular backup jobs and they run great. Wooo
Plug in my USB drive, enable the backup copy job, asks if I want all points or just latest, I pick just latest, job ends with "warning no restore points found."
I run the regular backup job, runs fine, backup job is triggered... "no restore points found"... Really Veeam? What triggered the job BRO!?!! Man...
I pick all.. no restore points found. I create a whole new backup copy job, point to regular backup job, run active full "no restore points found."

Seriously... what gives?!?!?!

[Zew]

*Update* It seems something wrong with BCJ pointing to the original jobs with VM-IDs changed. If I create a whole new regular backup job and a brand new BCJ everything works as expected.
I deleted the original job leaving the backup data intact, created a new job, mapped the job to the old data, ran it, success. Created BCJ to newly created original job "no restore points found.".
Yeeeeeha as long as I'm OK with a whole new original backup chain only then BCJ works fine.. this is fun...

[Zew]

So even after creating a whole new Veeam server, exporting/importing the config. main job runs fine, BCJ pointing to original jobs always say no restore points found.
My only solution is I have to forfeit my original backup chain and build a new primary job for the BCJ to succeed. interesting breakage...

[Mildur]

Hi Zew

We cannot comment on the „unsupported“ methods. I can just assume that something went wrong with the manual database edits and our copy jobs. Most likely the copy jobs are still trying to copy „the VMs with the old MoRefIDs“.

Next time, I strongly recommend to use our supported cmdlet for such vCenter migrations when VMs have new MoRef IDs:
- https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[Zew]

Did you not read my comment on the other thread about vCenter migration where I asked if you had used that exact tool? and what the syntax of the expected file is?

[Gostev]

@Zew clearly you're facing an environment-specific issue after making some significant changes to your production environment. The forum rules displayed when you click New Topic specifically request that you don't bring environment-specific issues to this community, as this is not a support forum. Please respect the forum rules for your future contributions here and kindly work directly with our Customer Support to try and resolve your current situation. Thank you for understanding.