Can you give the errors you are receiving?
Error - Cannot unmount datastore 'my_test_station' from host 'x.x.x.x'. The resource 'my_test_station' is in use. Cannot unmount datastore 'my_test_station' from host 'x.x.x.x'. The resource 'my_test_station' is in use.
Once SIOC is unchecked recovery works fine.
SIOC cannot be used when doing a planned migration, because datastore with SIOC enable cannot be unmounted.
I believe it is a documentation bug if this is not documented.
OK so after re-reading all the guides for (SRM, SIOC, NetApp SRA) and what you sent over it seems the docs aren't clear as to why Planned SRM recovery plans fail when SIOC is enabled, but I'm guesing the fact that SIOC writes to the disk every 4 seconds = busy disk for the unmount process.
Thanks for pointing me to the right resources.
SRM tries to unmount the datastore on the protected side after it brings stuff up at the recovery site. You cannot unmount a datastore with SIOC enabled.
It seems like SRM should be able to handle disabling SIOC first.
That said, you should be able to just manually disable storage io control on all the volumes in question prior to the planned migration. As implied above, this should not effect a real disaster or forced takeover because SRM will not have to worry about cleaning up the protected side since your datacenter is on fire, was hit by an asteroid, underwater, or without power.