Recommendations for Setting up a DR Site

Question

Hello Experts,

I’m fairly new to MS SharePoint and need some help and recommendations regarding disaster recovery (DR) setup and potential migration to SharePoint Online.

Current Setup:

• We have two SharePoint servers at our HQ, being used as a Document Management System (DMS) for robust file-sharing and comprehensive document management.

Integrated with Dell Unity NAS storage for internal file storage, we currently have 10 TB of data stored, with about 40% of our storage capacity utilized.

A Load Balancer is also part of the architecture for high availability.

Management’s Request:

My management has asked me to create a DR site for the existing SharePoint infrastructure.

Questions:

What would be the best approach to setting up a DR site for this environment (keeping in mind the current architecture)?

What steps should I follow to ensure high availability and proper data synchronization between the main and DR sites?

What are the potential challenges I should be aware of when implementing a DR strategy for SharePoint?

If we decide to migrate to SharePoint Online, what are the steps and considerations I need to take into account for a smooth transition, especially with 10 TB of data?

I’d really appreciate your expert recommendations, tools, and best practices for both setting up the DR site and possibly migrating to SharePoint Online.

Thanks in advance

Answer 1

For setting up a DR site:

• Approach for DR Site:
  • Implement SQL Server Always On Availability Groups to replicate SharePoint databases to the DR site. This ensures data consistency between the primary and DR sites.
  • Set up a secondary SharePoint farm at the DR site. Use identical configurations to ensure compatibility, including server roles, customizations, and features.
  • Replicate your file storage (Dell Unity NAS) to the DR site using a solution like Dell RecoverPoint or native replication features of Unity NAS.
  • Ensure your Load Balancer is configured to switch traffic to the DR site in case of primary site failure.
• Steps for High Availability and Synchronization:
  • Use a backup solution such as Veeam or AvePoint for regular backups of both SharePoint databases and configurations.
  • Schedule regular testing of failover procedures to validate synchronization and DR readiness.
  • Enable continuous monitoring and alerts to detect synchronization or replication issues early.
  • Document and test the DR runbook, detailing steps to bring the DR site online during a disaster.
• Challenges:
  • Keeping customizations, third-party solutions, and configurations consistent between sites.
  • Ensuring near real-time synchronization with minimal latency for large datasets like 10 TB.
  • Managing cost and complexity of maintaining a full secondary farm and replication solution.

For migrating to SharePoint Online:

• Migration Steps:
  • Assess your existing environment for readiness, including customizations, third-party integrations, and features that may need modification or replacement in SharePoint Online.
  • Use tools like SharePoint Migration Tool (SPMT) or third-party tools like AvePoint or ShareGate for large-scale migration.
  • Organize your data into manageable chunks and plan the migration in phases to minimize disruption.
  • Verify network bandwidth and plan for throttling limits during migration, especially for large data volumes like 10 TB.
• Considerations:
  • Evaluate your current storage usage and adopt Microsoft’s best practices for SharePoint Online, such as flattening folder structures and utilizing metadata for organization.
  • Account for costs associated with storage in SharePoint Online, especially if additional space is required.
  • Train users on differences between on-premises SharePoint and SharePoint Online features to ease adoption.
  • Plan a hybrid strategy if immediate migration is not feasible for all content.
• Potential Challenges:
  • Migrating large files or custom solutions that aren’t supported in SharePoint Online.
  • Handling permissions, user mapping, and ensuring no data is lost during the migration process.
  • Minimizing downtime during cutover to SharePoint Online.

Both paths require proper planning, testing, and user training. If your focus is primarily on resilience and redundancy, the DR approach is essential. However, if you aim for modernization and reduced infrastructure management, migration to SharePoint Online might be the better long-term solution.

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin