Azure File Sync Webinaari 12.3.2018
Agenda Why use Azure? Moving to the Cloud Azure Storage Backup and Recovery Azure File Sync Demo Q&A
What is Azure? A collection of cloud services from Microsoft that enables you to: Create and operate cloud applications Host workloads on PaaS services and IaaS virtual infrastructure Integrate cloud services with on-premises infrastructure
Why Azure? Elastic Self Service Scalability Efficient Rich Hybrid Single identity Management Careless Secure Global
Moving to the cloud Cloud technology satisfies: CEO s desire for greater business agility CFO s desire for operational efficiency CMO s desire for innovative ways to engage customers
42 Data center regions Azure is generally available in 36 regions around the world, with plans announced for 6 additional regions
Security & Management Platform Services Hybrid Cloud Security Center Portal Azure Active Directory Azure AD B2C Multi-Factor Authentication Media Services API Management Logic Apps Media Analytics BizTalk Services Service Bus Content Delivery Network Web Apps API Apps Service Fabric Mobile Apps Cloud Services Notification Hubs Functions SQL Database SQL Server Stretch Database SQL Data Warehouse Redis Cache Storage Tables CosmosDB Cognitive Services Bot Framework Cortana Azure Search Azure AD Health Monitoring AD Privileged Identity Management Domain Services Backup Automation Operational Analytics Scheduler Key Vault Store/ Marketplace VM Image Gallery & VM Depot Container Service Batch VM Scale Sets RemoteApp Visual Studio VS Team Services Application Insights Mobile Engagement Xamarin HockeyApp Infrastructure Services HDInsight IoT Hub Data Catalog Event Hubs Machine Learning Data Lake Analytics Service Data Factory Stream Analytics Data Lake Store Power BI Embedded Import/Export Azure Site Recovery StorSimple
Azure Storage Racks form into a Storage Cluster In a storage rack or chassis some of the servers are replaced with storage units JBOD Storage media can be either spinning disks (SAS) or SSD disks Storage is controlled using a distributed system Forms of storage BLOB page blod or block blob Tables Queues File Shares Storage is grouped under storage accounts
Azure Storage Durability GRS 6 replicas, 2 regions (3/region) Protects against major regional disasters Asynchronous to secondary
Azure Storage types IaaS PaaS Storage Virtual machines Networking Existing frameworks Web and mobile Microservices Serverless Compute Queues Reliable queues at scale for cloud services
Recovery Services Azure Backup Provide for backup services in the cloud Virtual Machine snapshot backups for Azure virtual machines Data backup from both cloud and OnPrem servers (Azure Backup Agent, Azure Backup Server, System Center DPM) Azure Site Recovery Use Azure as a backup datacentre for your OnPrem Datacenter Replication of VM s or physical servers from OnPrem to cloud Failover of VM s to Azure Optional failback to OnPrem DC
Azure Backup Azure Backup service has two roles Receiving and storing data backups from OnPrem or cloud These backups are made using the Azure Backup Server or DPM Taking backups from Azure IaaS VM s Backed up data is stored into Azure Storage (Backup or Recovery Vault) 3 copies or 6 copies (GeoRedundant) Data can be stored for a maximum of 99 years Some other backup vendors have support for Azure Veeam Veritas BackupExec
Deployment Models Workload backup with Azure Backup Server (D-D) or (D-D-C) On-premises infrastructure Hyper-V VMware Physical SQL SharePoint Exchange Windows Server Windows On-premises disk backup Microsoft Azure Backup Server Azure Backup Service On-premises infrastructure Files Folders Volumes Windows Server 2008 -> 2012 R2 Windows Client 7 -> 10 File/Folder backup to Azure (D-C)
Azure Site Recovery Azure Site Recovery allows backing up whole servers VMWare or Hyper-V VM s Physical servers The target can be another datacenter or Azure (Recovery Vault) Backing up a DC to another DC site Backing up a DC to Azure Recovery process has two steps Replication: Virtual disks (or physical disks) are replicated into Azure and stored into the recovery vault At this point the admin would also create the configuration for the VM s in Azure Failover: When the source servers are not available, the replicated disks can be spinned up as VM s in Azure Using the defined configuration Requires active components in the source environment Depending on the source environment virtualization (VMWare, Hyper-V with SCVMM, Hyper-V with no SCVMM) Allows for failback of the servers
Microsoft Azure Site Recovery Replication Replication SAN SAN Replication Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Hyper-V to Microsoft Azure Microsoft Azure VMware or physical Replication VMware or physical to VMware (on-premises) VMware VMware or physical Replication VMware or physical to Microsoft Azure Microsoft Azure Microsoft Azure to Microsoft Azure
Azure Migrate Gives you migration suitability of on-premises VM s to Azure, with: Performance-based sizing Cost estimations Lift-and-shift migrations Only for VMware Hyper-V coming soon!
Azure Files Reform Variety of clients SMB 2.1, 3.0, REST Windows, Linux, Mac OS Application Virtual machine Azure and on premises access Secure Encryption at rest Secure communication over SMB Sync Client Azure Files \\<account>.file.windows.net\<share> Multi-site access Cloud tiering On Premises SMB: Port 445 outbound Azure
Azure File Sync
Azure File Sync Centralize your organization's file shares in Azure Files without giving up the flexibility, performance, and compatibility of an on-premises file server. It does this by transforming your Windows Servers into a quick cache of your Azure File share. You can use any protocol available on Windows Server to access your data locally (including SMB, NFS, and FTPS) and you can have as many caches as you need across the world. Azure File Sync may be used to MIGRATE DATA into an Azure File share, even if the sync mechanism isn't desired for long-term use.
PaaS West Europe East US Azure Backup Vault File Share File Share Work Folders Branch Office SMB NFS Users Applications HQ Server! Branch Office
Scenarios Multi-site sync Keep a data set in sync across multiple locations Cloud tiering Turn a server into a lightweight, performance cache for Azure Files Direct cloud access Native file format with SMB or REST access Integrated cloud backup Point-in-time recovery and retention policies without redundant data transfer Rapid file server DR Fast namespace sync with no need to wait for data restore
Requirements Azure Subscription Azure Storage Windows Server 2012 R2, 2016 Only NTFS volumes are supported Supported features: ACLs NTFS compression Sparse files Mount points(partially supported) ReFS, FAT, FAT32, and other file systems are not supported
Terminology Storage Sync Service The Storage Sync Service is the top-level Azure resource for Azure File Sync. Sync group A sync group defines the sync topology for a set of files. Endpoints within a sync group are kept in sync with each other. Registered server The registered server object represents a trust relationship between your server (or cluster) and the Storage Sync Service. You can register as many servers to a Storage Sync Service instance as you want. However, a server (or cluster) can be registered with only one Storage Sync Service at a time. Azure File Sync agent The Azure File Sync agent is a downloadable package that enables Windows Server to be synced with an Azure file share. Server endpoint A server endpoint represents a specific location on a registered server, such as a folder on a server volume. Cloud endpoint A cloud endpoint is an Azure file share that is part of a sync group. The entire Azure file share syncs, and an Azure file share can be a member of only one cloud endpoint. Cloud tiering Cloud tiering is an optional feature of Azure File Sync in which infrequently used or accessed files greater than 64 KiB in size can be tiered to Azure Files.
Encryption solutions Support for encryption solutions depends on how they are implemented. Azure File Sync is known to work with: BitLocker encryption Azure Rights Management Services (Azure RMS) (and legacy Active Directory RMS) Azure File Sync is not to work with NTFS Encrypted File System (EFS)
Antivirus solutions Because antivirus works by scanning files for known malicious code, an antivirus product might cause the recall of tiered files. Because tiered files have the "offline" attribute set, we recommend consulting with your software vendor to learn how to configure their solution to skip reading offline files. The following solutions are known to support skipping offline files: Symantec Endpoint Protection McAfee EndPoint Security Kaspersky Anti-Virus Sophos Endpoint Protection TrendMicro OfficeScan F-Secure Server Antivirus
Backup solutions Like antivirus solutions, backup solutions might cause the recall of tiered files. Use a cloud backup solution to back up the Azure file share instead of an on-premises backup product.
Failover Clustering, Dedup and DFS Windows Server Failover Clustering is supported by Azure File Sync for the "File Server for general use" deployment option. Failover Clustering is not supported on "Scale-Out File Server for application data" (SOFS) or on Clustered Shared Volumes (CSVs). The Azure File Sync agent must be installed on every node in a Failover Cluster for sync to work correctly. For volumes that don't have cloud tiering enabled, Azure File Sync supports Windows Server Data Deduplication being enabled on the volume. Currently, interoperability between Azure File Sync with cloud tiering enabled and Data Deduplication is not supported. Azure File Sync supports interop with DFS Namespaces (DFS-N) and DFS Replication (DFS-R). DFS Replication (DFS-R): Since DFS-R and Azure File Sync are both replication solutions, in most cases, we recommend replacing DFS-R with Azure File Sync. Not every on-premises server which needs a copy of your file data can be connected directly to the internet.
Azure File Sync agent update policy Updates to the Azure File Sync agent will be released on a regular basis to add new functionality, and to address any issues that were discovered. For deployments that use earlier versions of the Azure File Sync agent: The Storage Sync Service honors the preceding major version for three months after the initial release of a new major version. For example, the Storage Sync Service would support version 1.* until three months after the release of version 2.*. After three months have elapsed, the Storage Sync Service begins to block Registered Servers that are using the expired version from syncing with their Sync Groups. Within the three months for a preceding major version, all bug fixes go only to the current major version. You will get notification in the Azure portal if you are using a version of Azure File Sync that will expire within the next three months.
Snapshot Similar to previous versions (WS2003->)
DEMO
Arto Roth Microsoft Certified Trainer MCSE Private Cloud MCSE Server Infrastructure MCSE Cloud Platform and Infrastructure Microsoft MVP Cloud and Datacenter management
Q&A