Target Issue

VMware specific discussions

Target Issue

Veeam Logoby Zew » Mon Mar 13, 2017 5:02 pm

I thought this problem had been fixed but appears to still be an issue... :S

Deleted VM due to a mistake made, restored entire VM with option to restore VM Tags.

Ran Active Full on job a vew days later, says target has been delted or does not exist. (This this not the point of the checkbox restore VM Tags???!)

Had to edit job, re-select VM (same name as original) and now Backup job states "13/03/2017 11:58:26 AM :: This-VM is no longer processed by this job. Make sure this change is intentional." When I run the job?

How does one recover a VM fully while keeping the dang backup job intact?

My Old post about this issue was about Instant VM restore, this Time I did a full VM restore, with the Tags option, so a bit different, but expected my Backup job to be unaffected. Which it clearly was...
vmware-vsphere-f24/restore-vm-without-breaking-backup-chain-t36490.html
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby gollem » Mon Mar 13, 2017 5:15 pm

Do the following:
- Delete the job
- Rescan your vcenter from the backup infrastructure tab
- Create a new job
- Do an active full

That should resolve it for you.
gollem
Influencer
 
Posts: 16
Liked: never
Joined: Sat Jun 16, 2012 7:26 pm
Full Name: Erik E.

Re: Target Issue

Veeam Logoby Zew » Mon Mar 13, 2017 5:18 pm

Mmm, thanks Gollem, the easier solution is to open the job, select the target VM, delete, click add, re-add the VM, click Finish.

That however is not the answer to the question...

"How does one recover a VM fully while keeping the dang backup job intact?"

Just to clarify that got my VM working on the backup job, you solution is probably to clear the existing warning, which I posted, that was not a huge concern as it was more of an FYI notice, and more of an annoyance then a problem.
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby mma » Tue Mar 14, 2017 7:33 am

Hi

To keep it short & simple:

Restore of a VM = New VM = new VM ID.
Restore VM Tags has nothing to do with your VM ID.
Ask Google about vSphere Tags :-)

vCenter, ESX Hosts, Veeam... don't care about the VM Name. Ech VM has a unique ID which is also used for the VM selection in your job settings.
Just remove and re add the VM to your job. Don't delete the job, there is no need for it.
If you delete the Job, you have an "orphaned" backup in your repository.

Regards
Marcel
mma
Service Provider
 
Posts: 64
Liked: 10 times
Joined: Thu Dec 22, 2011 9:12 am
Location: Lucerne, Switzerland
Full Name: Marcel

Re: Target Issue

Veeam Logoby foggy » Tue Mar 14, 2017 12:08 pm

Marcel is correct, this comes down to the new ID the restored VM (similarly to instantly recovered VM) gets upon registration in VI, which makes Veeam B&R to treat it as a new one.
foggy
Veeam Software
 
Posts: 15078
Liked: 1110 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Target Issue

Veeam Logoby Delo123 » Tue Mar 14, 2017 2:09 pm 1 person likes this post

As Marcel said it will always be a new vm since it has a new id. However if you do not want to change jobs in the future after restoring a VM you could backup your vm's by using "VMs and Templates" in the add objects screen for backup instead of choosing individual VMs), also in case of adding a new VM in the same "folder" it will be automatically picked up by Veeam
Delo123
Expert
 
Posts: 351
Liked: 101 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Target Issue

Veeam Logoby Zew » Thu Mar 16, 2017 3:41 pm

It be nice if Veeam implemented a checkbox that says the old VM is forever gone, when you restore this VM, replace the existing jobs VM ID with the newly restored one. Bam call it a day. everyone's happy.
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby Delo123 » Thu Mar 16, 2017 3:48 pm

How should Veeam know what the old vm is? Just by the name? In theory you could restore every vm to that name and Veeam would never know it actually isn't the same etc... But yeah, maybe something they could think about in some way...
Delo123
Expert
 
Posts: 351
Liked: 101 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Target Issue

Veeam Logoby Zew » Thu Mar 16, 2017 7:05 pm

Delo123, it would know the old VM by it ID? the exact problem that exists now. They could even add an algo to look to see if the existing VM ID exists within vSphere, if not have a pop up or something stating "Hey, noticed you are restoring a VM that doesn't seem to currently exist in your vSphere. Is the restored VM replacing the old VM ID?" Click yes, the backup job runs I guess a new chain for the newly recovered VM (Although it be nice if it still be able to keep the old source and still do CBT) but that may not be teh case or possible.
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby mma » Fri Mar 17, 2017 9:40 am 1 person likes this post

Why not change your job setup?
You can select Folders, Tags, vCenters, Hosts.... as Job source. Your job setup with selection by VM name / VM ID is a bit outdated.
mma
Service Provider
 
Posts: 64
Liked: 10 times
Joined: Thu Dec 22, 2011 9:12 am
Location: Lucerne, Switzerland
Full Name: Marcel

Re: Target Issue

Veeam Logoby blithespirit » Sun Mar 19, 2017 10:22 pm

The simple answer to your question is around vCenter, you deleted the vm and vCenter deleted the data and iDs (MoRefs) from the database, when you recovered it using Veeam it does not recover the ID to vcenter database as that is not part of the backup file, so, when you recover the vm and Veeam checks vCenter for your ID when the job starts it does not exist anymore hence the error but it does find the name and a new ID so you get the request for confirmation.

In this circumstance it is as designed in vCenter. When you do an emergency recovery the ID is still within the VCenter database so you don't have any issue all pointers are functional.

Does that answer why it does it and why Veeam does not see it again?

Methods to change the job have been discussed.

Cheers
blithespirit
Veeam Software
 
Posts: 47
Liked: 8 times
Joined: Tue May 03, 2016 2:06 pm
Full Name: Paul Szelsi

Re: Target Issue

Veeam Logoby Zew » Mon Mar 20, 2017 2:58 pm

MMA,

If the souce job was set via a vCenter VM folder instead. I delete the VM, I do a full restore of the VM. Then Veeam picks this up as the same VM and continues the job with a normal forward incremental VIB? Or does the job simply create a whole new chain for said VM?
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby foggy » Mon Mar 20, 2017 3:02 pm

It will pick it up as a new VM and perform a full backup of it during the next incremental job run (entire VM data will be read and written into the corresponding VIB file).
foggy
Veeam Software
 
Posts: 15078
Liked: 1110 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Target Issue

Veeam Logoby Zew » Fri Mar 31, 2017 3:57 pm

basically if you ever have to recover a VM, you can never use the old chain?
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby foggy » Fri Mar 31, 2017 4:01 pm

You can map to the old chain, but entire VM will be read during the next job run anyway.
foggy
Veeam Software
 
Posts: 15078
Liked: 1110 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Next

Return to VMware vSphere



Who is online

Users browsing this forum: Majestic-12 [Bot] and 34 guests