File Services on Azure: 10-Day Implementation

It is a very common requirement or is a business/IT problem to centralize and manage their file servers. For SMB, they want to have a proper replica of their one or two file servers in cloud. For enterprises, they struggle with maintenance and backup of file servers in branch offices. With Mismo Managed File Services, we help you centralize & consolidate your file servers using the power of Microsoft Azure

Why Azure File share?

• Centralize the file shares in cloud and do not worry about the branch file servers
• Replace on-premises file share with Azure file share without any compatibility issues as Azure file share uses SMB & NFS protocols
• Serverless file share which means no hidden IaaS VMs or NAS filers
• Choose from different performance tiers according to requirement for optimized TCO
• Azure files enables both Classic and Hybrid Lift and Shift scenarios
• Azure file shares can be used as persistent volumes for stateful containers
• Applications running in Azure can access data in the file share
• Store hot data on-premises and rest on Azure file in a hybrid model
• Can choose from different Redundancy options (LRS, ZRS, GRS, GZRS, and RA - GRS)

Steps for implementation:

(Day1-2): Assessment/Discovery

• Assessment of environment
• Assessment of business requirement

(Day3-5): Planning/Design

• Planning the cloud file server environment
• Planning the Single-Sign-On (SSO) and access management
• Preparing the design
• Identifying issues, risks, and dependencies
• Test cases and rollback plan
• Preparing runbook for execution

(Day 6-8): Deployment/Test & Pilot

• Creating Azure file services on cloud
• Configuring the services as per design
• Integration with the identity provider
• Testing and pilot
• Organization wide deployment

(Day9-10): Transition/Support

• Documentation
• Support, Training and Handover

Note

• Cost is limited to design and implementation of 3 File Servers
• Configuration, testing, and sample data migration is in scope (completement data movement will be done by the customer)