Virtual DR and VMware Site Recovery Manager (Part 2)
In this second part on my series on SRM, I discuss where SRM might be going in future. Part one is here if you missed it
Command steps/PowerCLI support
In the SRM product, it’s possible to create steps that call-out other scripting engines, such as Microsoft PowerShell and VMware’s PowerCLI. It’s a must-have feature if you want to have a recovery plan that reflects all nuances of your organisation. The trouble with the command step piece, however, is that you can only place them in certain parts of your recovery plan — the main steps. They lack the granularity that allows you at any point to add a call-out to script….
RSS
iTunes
February 23rd, 2010 at 6:05 pm
Hi Mike,
have you ever used PowerCli to recover or to automate steps for physical servers, i.e, you invoke SRM to recovery the prod site that in it’s majority is based around virtual machines, but some are physical servers.
February 24th, 2010 at 10:36 am
Not really. I’m 100% virtual… from both a practical and ideological perspective. By which I mean, if I’m writing a book on SRM it’s too much to have to think about how SRM will interact with physicals… except to pause the plan whilst something happens in the physical world. I have done a little work on how to call PowerCLI scripts from with the recovery plans themselves – to change settings on VMs – such as reducing their RAM configuration or change their IP address using netsh…
As for triggering SRM events with PowerCLI – there’s no API or SDK model to that yet – but VMware are planning cmdlets for SRM for the next release… Beta programme opens in a couple of months time…