Host-based backup of VMware vSphere VMs.
Post Reply
Novox
Expert
Posts: 129
Liked: 24 times
Joined: Jul 12, 2016 12:51 pm
Location: Vermont, U.S.A.
Contact:

Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Novox »

I moved the Replica Metadata as described here: https://www.veeam.com/kb2165, then I retargeted the Replica Metadata destination for my replica jobs, now all of my replica jobs are failing with:

"Processing {vm name} Error: The name '{vm name}_replica' already exists."
Dima P.
Product Manager
Posts: 14726
Liked: 1706 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Dima P. »

Hello Novox,

Any change you have a case ID to share? Can you please double check that you do not have any other VMs with the same name (i.e. with the _replica postfix) as stated in this KB article - Replication Error: The name '{vmname}' already exists. Thanks!
Novox
Expert
Posts: 129
Liked: 24 times
Joined: Jul 12, 2016 12:51 pm
Location: Vermont, U.S.A.
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Novox »

I am "Configuring Replica Mapping" by re-seeding my replica jobs now.

Unfortunately, https://www.veeam.com/kb2165 doesn't mention any of this is required when moving Replica Metadata.
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by foggy »

Mapping replicas after changing the metadata location is not generally required. I'd recommend contacting support for a closer look.
Novox
Expert
Posts: 129
Liked: 24 times
Joined: Jul 12, 2016 12:51 pm
Location: Vermont, U.S.A.
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Novox »

All my replica jobs definitely started failing with "Processing {vm name} Error: The name '{vm name}_replica' already exists." after I moved the replica metadata.

This also doesn't make sense to me because if I moved the metadata properly, then one assumes the destination hasn't changed and Veeam shouldn't have been surprised to see an existing {vm name}_replica...
Novox
Expert
Posts: 129
Liked: 24 times
Joined: Jul 12, 2016 12:51 pm
Location: Vermont, U.S.A.
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Novox »

Trying to run my replica jobs now, but it seems inexorably slow... 1.5 hours to calculate 42% of digests on a single 750GB hard drive.
Novox
Expert
Posts: 129
Liked: 24 times
Joined: Jul 12, 2016 12:51 pm
Location: Vermont, U.S.A.
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by Novox »

Update:

I called Veeam support and spoke to Gary who indicated that somehow the replica metadata became detached or disconnected and that for the first run of all replica jobs going forward, Veeam would have to recalculate ALL digest information (between my running VM, and the existing/remapped/re-seeded replica) which would basically regenerate the lost/disconnected CBT data.

Gary indicated that yes, this would take a very long time, but after these job runs, everything should return to normal.
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Moved Replica Metadata, now, Processing Errors and Replica jobs failing

Post by foggy »

Thanks for the update. That was what I suspected though I wasn't sure what could cause that. Anyway, yes, after re-calculating the digests your jobs will continue normally so just wait patiently.
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Bing [Bot] and 58 guests