AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 5: Configure Namespace for Multi AZ FSx for Windows

As replication is now setup and working, we need to configure a namespace path for our users to use. This will allow end users to use a single UNC path and automatically be directed to whichever copy of the filesystem is available and failover to the other automatically without intervention.

Continue reading “AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 5: Configure Namespace for Multi AZ FSx for Windows”

AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 4: Configuring FSx for Windows Cross AZ Replication

As we are now able to access both the FSx filesystems individually from the client machine, the next stage is to configure replication between them in order to ensure that data is kept in-sync across both. Microsoft DFS-R implemented on the managed FSx filesystems will deal with the replication once its setup and configured.

Continue reading “AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 4: Configuring FSx for Windows Cross AZ Replication”

AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 3: Configure AWS FSx for Windows using a Self-Managed Active Directory

In this section, we will setup and configure FSx for Windows filesystems in multiple availability zones within AWS’s infrastructure. These FSx filesystems are fully managed by AWS, all OS updates and maintenance tasks of the instances are dealt with by AWS with no end user intervention needed.

Continue reading “AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 3: Configure AWS FSx for Windows using a Self-Managed Active Directory”

AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 2: Nameserver Launch and Initial Setup

For our highly available FSx implementation, firstly we will launch and setup (including domain join) our EC2 instances that will become our DFS servers. As the setup for this is similar for both instances, I will only run through the initial launch and domain join once, but indicate the different variables for each DFS server.

Continue reading “AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 2: Nameserver Launch and Initial Setup”

AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 1: Overview

Overview

When looking to use AWS’s new managed file service, FSx for Windows, its important to understand that AWS make sure that this is highly available within a single AZ. This is done by replicating your data across this AZ (which includes one or more discrete datacenters) seamlessly in the background. This availability will generally be enough for mainstream use and the majority of your data, however what about business critical data? What happens in the highly unlikely event of large service disruption (or full outage) within a AZ? What would the cost of not having access to these files be to your business or users? This is where the benefits of running services in a Multi AZ (that is regionally distributed) configuration becomes clear.

Continue reading “AWS – Making AWS FSx for Windows Highly Available through Multi AZ Resilience – Part 1: Overview”