![]() However, this means you must decide if the failover site only needs read access or would need read-write. Once you break the relationship and write new data to the destination volume, you can replicate the changes back to the source to ensure there is no data loss. ![]() This capability enables you to fail over your critical application if a zonal outage or disaster happens.īy default, a replicated destination volume will be read-only until you break the relationship. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one zone to another Azure NetApp Files volume (destination) in another zone using cross-zone replication. Timeouts can be configured to control how fast a retry to the new location occurs and how long an NFS mount will stay mounted when no activity is detected.īy configuring automounter to list a source and destination Azure NetApp Files volumes in the map file, autofs can switch from the source volume to the destination volume without any administrator interaction.Īzure NetApp Files provides data protection through volume replication between availability zones. Simply configure your automount files with multiple entries and autofs will try each one in order. A service (autofs) runs in the background of your client and references a set of configurable map files to mount external storage when you navigate to one of the specified paths in the files.įor instance, if you want to configure home directories to automount when your end users navigate to ~, automounter can do that.Īutomounter also provides advanced functionality, such as load balancing and failovers. Azure NetApp Files NFSv3 destination volume in availability zone AZ02Īutomounter is a package you can install on nearly any Linux distribution that does exactly what it says it does – provides automatic mount functionality.Azure NetApp Files NFSv3 source volume in availability zone AZ01.The following environmental configuration was used for this example. With automounter, it is possible to provide faster failovers to volume replicas in the event of an outage in your source volume’s availability zone. If there are many clients, remounts can be a challenging task to perform.īut what if you could automate the failover process to avoid requiring any admin interaction with a few simple configuration changes? There will also likely be different IP addresses in the Virtual Network (VNet), so in the event of a failover, a remount would be needed to gain access to the replicated volume. ![]() Only two volumes can be deployed in a region with Azure NetApp Files – even in different availability zones – and the names must be different. With Azure NetApp Files, volumes can be replicated across availability zones within a region to provide redundant copies of important datasets, but failover is a manual process with several steps that can take valuable time away from your application. Networks can fail, zones can go down, and then your application is left in a nebulous state waiting for the NFS mount to respond to read or write operations. When you are using NFS in the cloud for your business-critical applications, you can ill-afford outages. This article covers how to configure autofs for automatic mount failovers in Azure NetApp Files.Ĭo-authors: Justin Parisi, Azure NetApp Files Technical Marketing Engineer Looking for a way to automate NFS mount failovers when a network or availability zone becomes unavailable? Automounter can help. Manually reverse resync using the Azure NetApp Files commands from cloud shell Scripting out replication management tasks What happens when the source volume is available again? Providing write access after an NFS mount failover to a replicated destination
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |