Disaster Recovery FAQ

Disaster recovery for file shares is the plan and tooling to restore access to files, permissions, and availability after an outage, ransomware event, or site failure.

Disaster recovery is important for enterprises because outages and regional failures can interrupt access to files and services, and recovery planning is what defines how quickly systems can be restored and how much data loss is acceptable through RTO and RPO targets.

MyWorkDrive integrates with Azure File Sync by connecting to the local Windows Server that hosts the synced copy of the Azure file share so existing NTFS permissions and file locks are preserved, rather than using a dual-writer design against the same Azure file share.

To preserve NTFS permissions in recovery, restore files using tools that retain security descriptors and ensure your domain identities and group memberships are recovered or still available.

MyWorkDrive provides file access over HTTPS with identity and permission enforcement, so users can reach approved shares without broad network VPN access.

Remote file access during outages is enabled by serving the synchronized file share through MyWorkDrive over HTTPS from an available server, while Azure File Sync supports recovery by restoring the namespace first and recalling file content in the background.

Because MyWorkDrive is an access layer, disaster recovery focuses on your underlying file storage backups and restoring the MyWorkDrive server configuration so users can reconnect quickly.

Active Directory and Microsoft Entra ID are identity systems used to manage users and access, and they are commonly integrated with file access solutions to enforce authentication and group-based permissions.

Disaster recovery should be tested on a regular cadence and after major changes, with recurring runbook rehearsals and failover drills to confirm recovery steps, timings, and data integrity.