Difference between revisions of "Lab Manager"

Jump to navigation Jump to search
1,538 bytes added ,  16:17, 19 October 2010
Added "Move to a new Datastore"
(→‎Troubleshooting: Added "Unable to Enable Datastore")
(Added "Move to a new Datastore")
Line 52: Line 52:
* '''Network''' - Update the deployed VM's config through vCentre
* '''Network''' - Update the deployed VM's config through vCentre
* ''Disk - Can't be changed, a deployed template is a delta from the original template (think snapshotting), you must reconfigure the template''
* ''Disk - Can't be changed, a deployed template is a delta from the original template (think snapshotting), you must reconfigure the template''
== Move to a new Datastore ==
If you need to move off an old datastore, you need to get your templates (and so also the machines deployed from them) off it.  Therefore to do it in a nice, graceful (and gradual fashion).  Templates would need to be re-provisioned on new storage, and workspaces re-deployed using the new templates, which is likely to take time.  In order to get off old storage quickly (because its unstable maybe) you can...
* Migrate templates and their deployed child VM's using VMware SSMove tool - [http://kb.vmware.com/kb/1006694 VM KB 1006694] (not successfully tested)
* Clone deployed child VM's to new storage (you take a full fat copy, through the Lab Manager interface)
To clone child VM's to new storage
# Action '''Undeploy - Save State''' on the entire workspace
# Once completed, go to '''Clone...'''
#* In ''Clone to:'', select '''Existing Configuration''' and select the workspace you're currently in
#* In ''Create:'', select '''Full Clones...'''
#* In ''Clone:'', select '''Selected Virtual Machines:''', tick the VM's you want to clone and select the destination Datastore
#* Click '''OK'''
# Once completed, go into the workspace, and rename VM's so that...
#* Source VM's are given new names
#* Clone VM's are given names of the machines they were cloned from
# For the entire workspace, select '''Move...'''
# Move all the old source VM's into a new (temporary) workspace
# Redeploy the original workspace
# Assuming the original workspace spins up OK, the new temporary workspace can be deleted


== Troubleshooting ==
== Troubleshooting ==
Line 60: Line 81:
# Locate the problem network and go to '''Properties'''
# Locate the problem network and go to '''Properties'''
# Update the '''Physical Network Bindings''' for the relevant ESX
# Update the '''Physical Network Bindings''' for the relevant ESX


'''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br>
'''Unable to deploy VM ''VM'' in VirtualCenter. The session is not authenticated.'''<br>

Navigation menu