Replication of Sharing Links between DR and Production

I would like to formally submit a feature request based on an ongoing issue we've encountered with our Cerberus Enterprise Plus deployment in a High Availability (HA) and Disaster Recovery (DR) configuration.

Issue Summary:

During our recent DR tests, we observed that sharing links created on the DR server do not replicate back to the production server when we fail back. This creates a significant gap in our operational continuity and user experience.

Current Workaround:

As per the communication with your support team, there are no workarounds available for this issue. The synchronization manager does not currently support the replication of sharing links created on DR nodes back to the primary production nodes.

Business Impact:

This limitation affects our ability to maintain seamless file sharing and user access across failovers. Given the critical nature of this functionality, we are evaluating other solutions but would prefer to continue leveraging Cerberus for its other robust features.

Feature Request:

We propose the following enhancements to be considered for a future release of Cerberus:

1. Automatic Replication of Sharing Links:
   • Implement a mechanism to ensure that any sharing links created on the DR server are automatically replicated back to the production server upon failback.
2. Real-Time Synchronization:
   • Enhance the synchronization manager to support real-time or near-real-time synchronization of sharing links between DR and production environments.
3. Conflict Resolution:
   • Develop a conflict resolution strategy to handle any potential conflicts that may arise during the replication process.

Expected Benefits:

• Improved operational continuity and user experience.
• Enhanced reliability of Cerberus in HA/DR configurations.
• Increased customer satisfaction and retention.

We believe that addressing this gap will greatly benefit not only our organization but also other enterprises utilizing Cerberus in similar configurations.

Thank you for considering this feature request. We look forward to your response and any potential timelines for implementation.