Hi,
I'd agree with you, having a 20TB CIFS share that is replicated and potentially has a high rate of file change for snapshots\snapmirror lag is less than ideal.
Here are some options for you to consider:
- Migrate data (root folder in the existing share) to a new volume and mount it to the namespace using a junction path
- Abstract the UNC path from the users and implement DFS in which case it could be on an idependant volume on the same vserver but logically accessible as a DFS link within the DFS namespace.
- Split the share into multiple shares by migrating data into different volume (perhaps accross multiple vservers) and potentially use multiple DFS namespaces based on logical business unit access
Are you using ABE to limit visibility at the root of your share? I guess it really depends on your RTO\RPO but i think you might struggle to meet that during a DR failover event given your current configuration and I'd be suggest that could be the driving factor for you to remediate the issue before you a DR failover is required.
P.S...I sure hope you have removed the default NTFS permissions of Everyone full control from the root of that volume\share!
/Matt