Hi Steve,
That is the correct behavior for SMVI in release 1.0.1 when a VM has been deleted from disk or removed from the VC inventory. If the VM exists at time of restore all you'll have to do is power it up once the restore is complete, if it's gone you must do exactly as you described below, browse the datastore, right click on the .vmx file and add it back to the VC inventory.
Automatic registration of deleted virtual machines post backup, and along those same lines, optional automatic power on of a virtual machine after restore will be included in a future release.
Best regards,
John Lockyer
-----Original Message----- From: steve klise [mailto:klises@caminomedical.org] Sent: Monday, February 23, 2009 4:26 PM To: toasters@mathworks.com Subject: SMVI 1.0.1
I have ESX 3.5 rev2 (don't quote me on the rev, but we are 1 rev back from the latest esx 3.5.x), running SMVI 1.0.1 on our Virtual Center host (windows 2003 R2 sp2). We are testing SMVI 1.0.1 on our 6030's running ontap 7.24 via FCP. We are able to take snapshots at the datastore level. When we go to restore, here is what we are doing: taking a snapshot (love snapshots, they work real fast, etc) Once completed, we snapmirror to another filer via SMVI (no big deal so far) We delete a windows VM (again, simulating OH NO YOU DIDN"T delete that vm....) Go to do a restore of a vm via thees instructions: http://now.netapp.com/NOW/knowledge/docs/SnapManager/relsmvi_10/html/sof tware/admin/restore5.htm#1180308 successfully completed :jumping: wait, no VM appears in my VIC :,(
I can go to the vmdk and right click and add to inventory, but our VAR said this is not how it should work. I called support, and they said it should be fixed in version 2. Sounded fishy, but support is usually right on.
Any suggestions?