"Remember kids, the only difference between Science and screwing around is writing it down" -Alex Jason (made popular by Adam Savage)
This was a fun one. I’ve posted in the past about changing and removing a SATP rule. That post, however, only works if the SATP rule is valid and you want to change or remove it for whatever reason. I am going to re-use the same image I made for that previous post, because it still holds true:
Anyway. The issue: Continue reading “Removing an incorrect SATP Rule”
Starting to mess around with vRealize Orchestrator and just deployed the 6.0.3 vRO appliance. A few gotchas, many of which are well denoted by other blog posts:
One of the first issues I ran into was registering it with my SSO. My setup has two vCenters with two separate but federated Platform Services Controllers. I wanted to authenticate my vRO instance with SSO, not my Active Directory to keep user management a bit more central to VMware. Ran into some fun gotchas. Continue reading “vRealize Orchestrator and vSphere 6 SSO Authentication”
Quick post here. I recently updated my environment to vCenter 6.0 Update 1 and VMware Site Recovery Manager 6.1 and after my first attempted test failover (and subsequent ones) the test would always fail when it tried to power on the virtual machines. Some powered-on and some didn’t. The following errors appeared for about half of my VMs:
Continue reading “VMware SRM and the PBM & PreCloneCheckCallback error”
Quick post here. So I have been reviewing some great posts from @vmKen and @BenMeadowcroft about automating Site Recovery Manager operations with PowerCLI and wanted to give it a try myself. They outlined the process rather clearly in their blogs so it was a breeze to get most of the stuff up and running. But when I went to actually execute a test recovery or a recovery etc. it kept failing! The PowerCLI command to start the recovery was $VMrp.Start($RPmode)–the $VMrp being my recovery plan and the $RPMode being the recovery plan mode of a recovery. The command was accepted but the recovery plan never started.
I got the following error in vCenter:
Unable to start the requested operation. Another operation may be in progress. Please wait for it to finish and try again.
Hmm…weird. I could kick off a test from the GUI with no issue so nothing was “interfering” from what I could tell. I thought maybe since I was using Site Recovery Manager 5.8 maybe something had changed so I tried it with my 5.5 environment and got the same result.
After I was about to lose my mind it finally occurred to me that I was connecting to the protected vCenter and the protected SRM server (I did enter in remote credentials for the recovery SRM server though). While I could query the recovery plan etc without issue from here, maybe SRM didn’t allow a recovery plan to be started unless you directly connected to the recovery vCenter/SRM server.
So I reconnected to the recovery site and it worked! So I guess it makes a difference, so FYI. Now there might be a workaround to this and it is definitely possible I missed something that allows this but this seems to be what you need to do. If you find this isn’t true please let me know!
Thanks Ken and Ben for getting me started!! Cool stuff. Kens posts:
http://blogs.vmware.com/vsphere/2014/05/automate-failover-with-srm.html
http://blogs.vmware.com/vsphere/2014/05/srm-powercli-reporting.html
http://blogs.vmware.com/vsphere/2014/05/powercli-and-the-srm-api.html