Depends maybe also on what's running on the vm. I'd think Kurt's approach is a little safer. Op 23 okt. 2013 21:12 schreef "Kramer, Jack" <[email protected]> het volgende:
> I've done it both ways and had no issues with either. > > (sent from a mobile device) > > > On Oct 23, 2013, at 2:42 PM, "Kurt Buff" <[email protected]> wrote: > > > > Don't know of any particular issues, because I've never done it. > > > > Here's what I do: > > Down the VM. > > Copy the VM to the new location > > Register and fire up the new VM, and when it asks if it was moved or > > copied, say moved > > Verify correct functioning of VM - correct any issues with NICs, etc. > > Delete old VM > > Done > > > > Kurt > > > > On Wed, Oct 23, 2013 at 10:47 AM, Derrenbacker, L. Jonathan > > <[email protected]> wrote: > >> Does anyone have any good/safe methods to move a VCenter VM to a > different > >> Datastore without using Storage VMotion? > >> > >> > >> > >> My first thought is something like this: > >> > >> 1. Clone the VCenter VM with it powered on(set local admin password > first). > >> > >> 2. When Cloning, select the new Datastore as the destination for clone, > and > >> select to clone to a powered off state. > >> > >> 3. Power down the old VCenter VM > >> > >> 4. Log into the ESX host holding the new cloned VCenter and power it up. > >> > >> 5. Fix any network card issues inside of VCenter > >> > >> Done > >> > >> > >> > >> Can anyone think of any issues this would cause? > >> > >> > >> > >> > >> > >> Thanks, > >> > >> Jon > > > > > > >
