Restoring VM to NEW location also deletes original?

Discussions specific to VMware vSphere hypervisor

Restoring VM to NEW location also deletes original?

Veeam Logoby YoMarK » Mon Jan 04, 2016 7:49 pm

Today I created an issue restoring multiple VM's from backup(actually to create a temporary test environment)

I've used the option "Restore to a new location, or with different settings" . The restore location was a different geographical location , different vcenter datacenter, different ESX server and different storage.
The restore started and it went fine. The VM's where restored to the new ESX servers. But then I saw that the original VM's where powered of and deleted. No warning, nothing.
I've done similar things multiple times already, and never had problems. It's worth noting that the other times I did this I probably rename the VM's, and this time I didn't. However, having the same VM name on another Vmware Datacenter is absolutely fine in Vmware vpshere.

Now: I've logged a support case(# 01256668) for this . Long story short: this is "by design".
Really?

It's not needed for VMware(same name different datacenter is perfectly fine), it's not needed for the storage(filename issues) as it is on different storage, it's not needed for ESX. Actually the name is not important, at all, in my opinion as all the VM's are referenced by GUID. SO There is absolutely NO technical reason to delete the original VM. I'n my opinion there is no logic in this as well.

Now if Veeam still thinks it's the right thing to do, then a WARNING should be very helpful. Also in the manual there is no indication that it's going to delete the original when selecting a NEW location: http://helpcenter.veeam.com/backup/80/v ... overy.html

I think this is so stupid that I question the person handling this case telling the truth. That's why I created this thread.

My questions:
- So it's not possible to restore VM's to another separate location without destroying production, UNLESS you do not forget to give every single VM in the job another name?
- Is it logical that the name being the same(although perfectly fine in Vmware) should be the only reason to delete the original with any further user interaction.
- Do you think, as I am, that this "design" is flawed(or at least need refinement such as a big warning and/or a proper manual mention)?
YoMarK
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Mon Jul 13, 2009 12:50 pm
Location: The Netherlands
Full Name: Mark

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby YoMarK » Mon Jan 04, 2016 7:54 pm

The thing is also....I've done so many restores for tests and things like that(probably giving them a proper other name), that I wasn't expecting something like this at all.
YoMarK
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Mon Jul 13, 2009 12:50 pm
Location: The Netherlands
Full Name: Mark

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby foggy » Tue Jan 05, 2016 11:44 am

Mark, have you specified different location for VM configuration file during restore?
foggy
Veeam Software
 
Posts: 15386
Liked: 1141 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby YoMarK » Tue Jan 05, 2016 11:53 am

Foggy: Thanks for responding!
Yes, completely different Fysical datacenter/Vmware datacenter/ESX host/storage.
(Freshly installed ESX host with local storage)

Edit: complete logs for the restore are in the support case.

I'm no expert on Veeam logfiles, but there are references in there with:
- the source "original" hosts esxpabiestxx with original "datastores" esxpabiestxx-local
- the target "new" restore host esxpahaarenxx with new datastore esxpahaarenxx-local
- deleting the, as it's called there "old" VM's on the source host.

Did a sort of check/test a few minutes ago, just pulling VM's from backup, and put it on a completely new location(only thing that's the same is the vCenter server and the display name of the VM), and not a single warning is given to me that it's going to delete the original source.

I think more and more that this is a major bug, and it's not "by design" at all.
YoMarK
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Mon Jul 13, 2009 12:50 pm
Location: The Netherlands
Full Name: Mark

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby YoMarK » Tue Jan 05, 2016 12:31 pm

FYI: If you mean I specifically changed the VMX file(config files) location: It was a multiple VM restore, changing host, ResourcePool, Datastore and Folder.
The File location of the VM configuration files then defaults to the first datastore on the new server, I did not change that specifically on the "datastore" page of the wizard as it was fine.
YoMarK
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Mon Jul 13, 2009 12:50 pm
Location: The Netherlands
Full Name: Mark

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby YoMarK » Thu Jan 07, 2016 9:45 am

Installed the latest update, and this fixes the issue.
So luckily this "deleting the original" behavior was not by design.
YoMarK
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Mon Jul 13, 2009 12:50 pm
Location: The Netherlands
Full Name: Mark

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby Delo123 » Fri Jan 08, 2016 9:15 pm

Hi Mark,

which update was that? This Sound scary and i am not Aware of any "new" Veeam updates. You are on 8? Update 3 was the update?
Delo123
Expert
 
Posts: 355
Liked: 103 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby alanbolte » Fri Jan 08, 2016 10:05 pm 1 person likes this post

If this was the problem I think it is, it was resolved in Update 2a.
alanbolte
Expert
 
Posts: 635
Liked: 172 times
Joined: Mon Jun 18, 2012 8:58 pm
Full Name: Alan Bolte

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby mkaec » Mon Jan 11, 2016 1:21 pm

Wow! That is scary. I just did a restore to a different location the other day to test something. Thank goodness we are on update 3.
mkaec
Expert
 
Posts: 196
Liked: 48 times
Joined: Thu Jul 16, 2015 1:31 pm
Full Name: Marc K

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby adrianmejia » Mon May 15, 2017 7:12 pm

Hi everyone,
It seems that the first version of 9.5 has the problem, I am looking for the complete release notes for SP1 o SP2 to know if there mention something like this.
adrianmejia
Novice
 
Posts: 7
Liked: never
Joined: Mon May 15, 2017 7:08 pm
Full Name: Adrian Mejia

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby foggy » Tue May 16, 2017 9:59 am

Hi Adrian, do you mean the issue is back in Veeam B&R v9.5? This thread was discussing v9 and its update 2a issued more than a year ago...
foggy
Veeam Software
 
Posts: 15386
Liked: 1141 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby utixo » Sun Jun 04, 2017 11:31 pm

I confirm the problem is there again in version 9.5 and it's crazy ! if you restore a VM in a totally different location different datastore different all but same name the original gets turned OFF and deleted. very scary !
utixo
Lurker
 
Posts: 1
Liked: never
Joined: Sun Jun 04, 2017 11:27 pm
Full Name: utixo

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby v.Eremin » Mon Jun 05, 2017 10:18 am

What's your support ticket number? Thanks.
v.Eremin
Veeam Software
 
Posts: 13868
Liked: 1038 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby foggy » Mon Jun 05, 2017 11:01 am

Also, are you restoring to a completely different virtual environment (different vCenter)? Otherwise, the behavior is expected, since you cannot have two VMs with similar name under the same vCenter and Veeam B&R should warn you twice in restore wizard that the original VM will be deleted.
foggy
Veeam Software
 
Posts: 15386
Liked: 1141 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Restoring VM to NEW location also deletes original?

Veeam Logoby jprovost » Mon Jun 19, 2017 3:40 pm

Veeam Backup & Replication Version 9.5.0.711

I lived the same problem at my job. I started to use Veeam in January, I had no problem at all to create backup and restore in the original point or other location until those next events:

- Friday, June 2nd I did exactly the same procedure as the previous weeks. (Procedure that I use since January, without any issue.)
- Each Friday & Saturday I make a backup of all the VM of the company to a storage unit. (9 VM's to back up, 4 are done on Friday, 5 are done Saturday)

-Monday, June 5th in the morning, I toke a look to all my backup files create by Veeam.
--I have a third server in the company dedicate especially for test purposes and to create new environment or development. This server has it's own NAS, NIC, Network and cannot interfere with the live environment of the company.
--Veeam is installed on my computer at work. To back up or restore VM, I configure Veeam to access the vCenter.
--So, Monday, June 5th, I did the same as the previous weeks, test my backup file by restoring to my test ESXi server and confirm that everything works properly. (I need to specify, everybody in the company are on their computer and work on the business ERP.) I start the VM restoration, after a few minutes, I received a lot of calls for "Server unavailable" and then I notice that the "live" VM was deleted. That MAJOR issues cause a downtime in the business for 1h (because it was the first time we had this situation, we searched for a reason, solution and why.), finally it was better to put it back the restore (backup in date of Friday, June 2nd) and put back on the server.
--All the week, I search for the cause of that situation.

- Friday, June 16th, the same procedure to back up VM's.
- Monday, June 19th in the morning, I start a restore from my backup files to the test server. Same problem happens again. With this situation, I started to search on Veeam web site for an explanation (alert, warning, procedure,etc.) but nothing is mentioned clearly. I finally found your post, with the exact issue.
-- From some reply in this post, it mentions that if we change the name of the VM (when we restore) it doesn't make this unbelievable delete without asking... But I tried today (I completely isolate my test server, install a new instance of Veeam Backup & Replication) and the problem happens 1 time on 3. The best way is to completely isolate your environment... what I want to say is:
* You have a Server A and Server B.
* I want to create a copy of a VM present on Server A to Server B.
* I backup VM on Server A to a storage unit.
* In my test environment, I use my new Veeam installation. The only connection I have to my live network is the storage unit.
* I start the restore to the test server.
* Everything works properly.

I printed the entire post and advertised all my colleagues in my department about the bug.
jprovost
Lurker
 
Posts: 1
Liked: never
Joined: Mon Jun 19, 2017 1:09 pm
Full Name: Jonathan Provost

Next

Return to VMware vSphere



Who is online

Users browsing this forum: Google [Bot] and 1 guest