I am by no means an SRA expert, but I have looked at the perl scripts that make it up. The SRA and SRM need to look for the same thing on both sides, so FC to FC, NFS to NFS. Without this, compliance is going to be a gamble. We have a nested export on an NFS volume with no datastores, but SRA/SRM knows that is an issue if we did have NFS datastores and it causes a bit of grief by failing to update SRM groups(there is a workaround, it stinks, but it works).
This ensures that the process can be followed, imagine how complicated an automated system would have to be to search every protocol in the middle of a disaster event to make that happen. Your time would HAVE to go way up, just to check for all the permutations. It couldn't verify exports from an FC to NFS datastore is just the first issue I could think of.
One major thing I would look at is that there is a "time" issue if you are using 64bit aggrs and qtree replication to 32bit aggrs when you split the mirrors. Here is a LINK to the discussion. I know it exists going from 32bit to 64bit, not sure about the opposite direction.
- Scott