2011-02-15 12:58 PM
I'm testing restoring a single VM after it's been deleted from VMware vCenter. When i restore the VM it's restored to the datastore and i can then add it to inventory without issue. The problem i find is that i have to reassign the network label to that VM. This isnt a big deal when restoring 1 VM but what happens if we need to restore an entire datastore?!?
Does anyone else have this issue? Is this normal behavior?
2011-03-10 05:26 PM
I wasn't able to replicate this.
I tried 2 different backup jobs, 1 at the datastore/datacenter level, and 1 at the vm level. In both cases, after doing the restore and re-adding the vm to the inventory, my non-default network group was retained.
Maybe some of the VM specifics caused this in your case? What were you testing?
2011-03-11 09:48 AM
Thanks for the info. Glad to know it's not normal behavior.
I was testing a windows 2003 vm. We had issues with datastores being named the same but in different datacenters (luckily renaming them has no impact), so that may have been the cause. I'll have time next week to test some more, different OSs, different datastores.. etc. I'll post my results.
Just out of curiousity, what version of vmware and NetApp are you running?
2011-03-11 10:12 AM
ESX 4.0.0 208167
vCenter 4.1 258902
3040 using a p release of 7.3.4
NFS (of course, we love nfs!)
Win xp vm
Which I can see is probably not a good test. I'll back my system down to 7.3.3 and see if I get similiar results.
Interesting that you say you were able to rename a vm without issue. I was testing another problem yesterday where if I did a backup, then renamed a vm, it could cause smvi to spin when trying to restore it.
Edit: Oh I see, you renamed the datastore, not the vm. Ok, gotcha.
2011-03-11 10:57 AM
Well... had to edit the backup jobs with the new names... then go back the next day and recreate them all again because i forgot to adjust the date to a future date, hate that.
2011-03-14 02:45 AM
Ok, I staged all this again with no issues.
ESX 4.1 260247
vCenter 4.1 258902
Ontap 18.104.22.168 and 7.3.3
Win2k3 32-bit and 64-bit versions both tested
- Created a 2nd VM Machine Port Group
- Changed the network label of both machines to this 2nd group
- Performed a backup
- Deleted both vm's in question
- Did an individual restore of each machine
- Checked the network label of both machines, which were correctly setup to this 2nd group
2011-03-14 06:24 AM
Thanks for the effort Tucker, very much appreciated.
We've had two esx hosts crash in the past week shortly after snap shots occured. We may have more serious underlying issues.
So i might not be able to get around to troubleshooting the network label issue until later in the week. I'll post my findings then.
2011-03-15 08:55 AM
Tucker, I havent had a chance to test yet, but i was curious if you have to browse your datastore and add the restored vm to inventory after the restore is complete. The documentation isnt clear on wheather or not it should automatically add the vm to inventory.
2011-03-15 09:08 AM
On a vm that has been deleted and you do a restore from inside vsc, it needs to be reregistered. Normally, the idea is to right click a vm, and do a restore from there (like snapshots). Of course then it doesn't need to be reregistered.
Sent from my iPhone(please excuse typos/spelling)
2011-03-15 09:57 AM
Well, it looks like this is strickly a vmware issue. When i delete a VM from inventory and re-add it, the network label isnt there.
Now that i have this narrowed down to vmware it should be a bit easier to figure out. I'll post what i find.