Hi.. Thank you so much for your kind response...
I got a requirement like for one of the application i have to exclude OS datastore from replication after the initial replication to secondary site.
Are there any other VMs on that datastore that need to be protected?
-No.
So first I want to know is it possible to exclude OS datastore from replication to secondary site as VMware SRM (through SRA) controls the replication?
You need to stop / unconfigure the replication of the LUN manually on the storage array. SRM can only "see" what LUNs are replicated and stop the replication when doing a failover. - SRM fully manages the replication (like start, check status, stop) using SRA? Also please clarify whether SRM at DR needs to communicate with any of the VMware server (like DC SRM, vCenter, etc) at DC during failover?
What you can do to protect that VM is to start "Configure Protection" wizard and on storage options screen select the non-replicated VMDK and mark it as detached. This will allow you to complete the wizard despite the VM has non-replicated disk. But take into account that in case of failover / test recovery you will have to manually present the datastore to the hosts and attach the OS VMDK to that VM.
If it is possible is it recommended to exclude the OS datastore from replication?
Of course it cannot be a common recommendation. What about application settings / OS settings / event logs / some other things? Do you want to replicate the datastore manually every time something is changed in OS? - Yes we replicate it through Mirror View when any manual changes commited.
What is the particular reason to not replicate the OS? -My client feels if some OS/application level corruptions happends the same will also get replicated to DR (as Mirror view is configured to Synchronous replication). So they planning to replicate working copy OS LUN frequently to DR manually when some changes commited.
