It doesn't rename the actual datastore name, it just renames the name you see 
in vcenter.  What I did was put a restored copy of the vm back out there, 
grabbed the file and deleted the restored copy of the vm.  I didn't have to 
bring the running vm down.

-----Original Message-----
From: Eugene Vilensky [mailto:evilensky AT gmail DOT com] 
Sent: Tuesday, August 23, 2011 1:14 PM
To: EMC NetWorker discussion; Chester Martin
Subject: Re: [Networker] VADP "redirected" restore

On Tue, Aug 23, 2011 at 12:20 PM, Chester Martin <cmartin AT spp DOT org> wrote:
> I just did something like this yesterday, it's a little tricky to do, but by 
> doing this you can get a file level restore from a vadp image level backup of 
> linux:
>
> 1) rename the original vm inside of vcenter console (this is just a 
> "friendly" name), you do not have to shut it down
> 2) Restore the image to a different datastore, the restore will not 
> start the vm
> 3) Right click on the "restored" vm and choose "edit settings"
> 4) In the network adapters properties make sure the "connected" and 
> "connect at power on" are unchecked
> 5) start the vm
> 6)Rename the OS and re-ip it the restored vm 7)Check the options that 
> were unchecked in step 4 8)Copy your files wherever you want


Sounds great and straightforward.  I hesitate about renaming virtual machines 
in vcenter, as last I checked (ESX 3.5) it didn't rename the 
/datastore/[vmname]/[vmname].vmx or .vmdk filenames, which may be
tricky to do if the machine is running.   Do you have any tips on this
aside from directly editing .vmx configuration files and manually renaming 
files?

Thanks again,
Eugene

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER