On-Prem Storage To Azure Storage - Part-3

-

Technical Setup and Configuration Blueprint

3. Provision File Server 

The next step involves provisioning a dedicated file server that hosts the Azure Storage Sync Agent to synchronize with Azure File Shares. To enhance functionality and manageability, I expanded the file server’s capabilities by configuring DFS Namespace, enabling Shadow Copies, and setting up Data Deduplication on each volume.


As a best practice, deduplication was enabled only after the final cutover, ensuring that all data was fully synchronized before optimization. This approach helps prevent potential sync inconsistencies during the migration phase.

Additionally, I fine-tuned the file server performance following Microsoft’s recommended guidelines:

Finally, to support modern file structures, I enabled long file path support through registry modifications as outlined in Microsoft documentation:

4. Provision Azure File Sync Services

Azure Files can be used in two distinct ways, depending on organizational needs and infrastructure strategy.

Deployment Options

Option 1: Direct SMB Mount

You can mount Azure file shares directly by using the Server Message Block (SMB) protocol.

Option 2: Azure File Sync (Hybrid Cache) - Opted for Fisher Funds

In contrast, Azure File Sync allows you to synchronize an Azure file share with on-premises Windows Servers. This model centralizes file storage in Azure while retaining on-premises access and performance.

Key Benefits:

  • Centralized storage in Azure with local caching on-premises.

  • Retains NTFS permissions, ACLs, and SMB features like DFS-N, Shadow Copies, and File Server Resource Manager.

  • Reduce on-premises storage footprint with cloud tiering, which keeps only recently accessed files locally.

  • Supports multi-site sync—multiple branch offices can share the same dataset.

You can follow the video and documentation to plan your deployment - 
🔗 Plan for an Azure File Sync deployment

Since you are migrating the data from one location to another, you need to install the agent on both the source and destination file servers. Please check my configuration. 


5. Deployment and Validation

  • UAT Plan (will provide template)

    • Pilot testing with key departments (e.g., Finance, Investments) 

    • Validation of permissions, performance, macros, and sync behavior

  • Deployment Plan (will provide template)

    • Cutover sequencing and user communication 

    • Sync monitoring and rollback procedure

Once the data synchronization began, it took approximately one month to sync around 10 TB of data to Azure and then replicate it across the new file server. After completing extensive internal testing, I was ready to proceed to the next phase. Since the Intune configuration was already prepared during the assessment stage, I was able to initiate the User Acceptance Testing (UAT) process immediately.

The UAT plan was designed to validate both functionality and performance from an end-user perspective. Each department was assigned to test specific scenarios aligned with their day-to-day operations, ensuring comprehensive coverage and real-world validation of the new setup.

Below are the Intune configuration screenshots and the detailed UAT plan. Focus on the yellow-highlighted drives; other drives eventually faded out as part of another data cleanup project. 



5. Backup, Restore, and Business Continuity

  • Azure Backup Configuration

    • Azure Shares Backup


    • Azure VM Backup


4. Data Integrity and Performance Optimization

  • Deduplication

    • Reviewing legacy dedup chunk store and rehydration before sync

    • Verifying post-sync data integrity and space optimization

  • Shadow Copy (VSS)

    • Reviewing retention configuration and restoring capability within Azure File Share

    • Aligning snapshot policies with backup schedules

  • M365 Integration

    • Whitelisting Azure File Shares within Office settings (for macros and linked workbooks)

    • Ensuring Excel and other Office apps handle UNC paths properly

  • FAQ

    • Post migration user issues and unknown findings. 

Popular posts from this blog

On-Prem Storage To Azure Storage - Part-2

-
Image
Technical Setup and Configuration Blueprint First and foremost, before proceeding any further, the most critical step is to ensure that the underlying network is properly configured to establish seamless communication between the Azure and on-premises environments. Fortunately, the majority of the network configurations were already in place; however, there were still a few intricacies that needed to be addressed—such as configuring private endpoints, DNS entries, and Cloudflare traffic routing.  Once networks and communication are configured, we can initiate building other elements as follows -  The diagram below provides an overview of the Azure setup and illustrates how the environment is structured. I will try as much as possible to explain more thoroughly - 1. Azure Storage and Azure File Shares Azure Storage and Azure Files Configuration  We begin by creating the Azure Storage and Azure Files with the following configuration. Certain details have been blurred out ...
Read more

On-Prem Storage To Azure Storage - Part-1

-
Image
Project requirements  Designed and implemented a cost-effective, end-to-end Azure-based storage solution, successfully migrating users and associated application dependencies with zero downtime . The project involved the seamless transfer of 10TB of data while preserving NTFS permissions and ACLs and ensuring that critical Excel macros remained fully functional.  This was particularly vital as Fisher Funds manages investments across bonds and equities via Bloomberg integrations. The resulting solution delivered modern security, enhanced reliability, and operational resilience, all while maintaining optimal cost efficiency. Challenges and Preparation 1. NTFS/ACL Enumeration and Access During the assessment phase, I identified that file share access across all departments was configured using direct user-based permissions rather than AD group-based access. I initiated a comprehensive access remediation project to align permissions with best practices. To achieve this, I ...
Read more

Secure Boot vCenter Deployment

-
Image
Fully automated PowerShell script to replace expiring Secure Boot certificates  across hundreds of Windows Server VMs — eliminating the need for manual EFI console interaction, FAT32 disks, or per-VM operator involvement.  If you need the full deployment files -  https://github.com/cloudmigrator/vMware 01 // The Problem Microsoft's Boot Certs Are Expiring Every Windows Server VM with Secure Boot enabled in our VMware environment trusts a set of cryptographic certificates that Microsoft issued back in 2011. On 24 June 2026 , those certificates begin to expire — and if we do nothing, those VMs silently fall out of Microsoft's Secure Boot servicing boundary forever. ⚡ Hard Deadline The Microsoft Corporation KEK CA 2011 and Microsoft UEFI CA 2011 both expire on 24 June 2026 . The Windows Production PCA 2011 — which signs the Windows bootloader itself — expires in October 2026 . The good news, per Microsoft's official documentation: machines will not immediately fail to boo...
Read more