What is the best practice to create a scheduled task for coping or cloning a vm between deta centers. The concept is to create a copy into another data center to have a backup for testing. The process should run on a timed basis such as every week. Currently there is a task in ESX 3.5 VC 5.2 to clone the vm but this will not overwrite the vm if it exists.
~E
Best practice - to use Veeam Backup & Replication for this.
Otherwise you can schedule powershell script to
1) delete existing copy
2) make a clone of particular VM
---
MCSA, MCTS, VCP, VMware vExpert '2009
You might be able to use a combination of PowerShell and VMware Converter to accomplish this. Converter 4.0 supports scheduled migrations and then use PowerShell to clean up the original VM you're cloning or configure the new VM however you need.
We are also planing an upgrade to ESX 4 and vsphere for this client is there any thing in orchestrator that may help here?
~E
I didn't finish orchestrator installation - it's not near as simple as vCenter. But I doubt there is something like that.
---
MCSA, MCTS, VCP, VMware vExpert '2009
I haven't used Orchestrator yet (though I've been meaning to) but I believe it's possible it could do that. At VMworld in 2008 I saw them show how you can schedule and orchestrate ESX installations, so an upgrade is likely also. But unless you have a huge amount of hosts to upgrade I think performing a traditional upgrade with either VMware Update Manager or the Host Update Utility is the way to go.
Hey, VMware guys!
Can you make Orchestrator training course? I know it's a great tool, but it's damn difficult to deploy it.
---
MCSA, MCTS, VCP, VMware vExpert '2009