- Newest
- Most votes
- Most comments
Thank you for your answer. We tried creating FSx B from the backup, but the interface would not let us create a SingleAZ Fsx from the FSx A MultiAZ backup. The interface forces a MultiAZ FSx. Is there a way to work around this limitation? Thank you again,
answered 2 years ago
ahh yes, you can only create a new FSx from a backup and that will mimic the cfg from the source system.. in your case FSx A is multi-az, so the newly created from backup FSx would also be multi az, sorry I missed that detail.
Also consider robocopy because you can take advantage of parallelism using multiple thread e.g. robocopy \source-fsx\share \destination-fsx\share /E /MT:16
I've seen people using up to 96 threads and if sufficient connectivity is available, it could result in drastic improvement in transfer speed.
It could be worth running a test using a subset of data to see the speeds achieved.
Hope this helps!
answered 2 years ago
Yes, this is also an avenue we have on our list, absolutely. Thank you very much for the suggestion.
We now have 3 options: 1-DataSync 2-Robocopy 3-In house custom application. We have in internal developer team that could develop something, but I'm trying to avoid this to "simply" copy 3TB of data.
Thank you again.
You should be able to create a backup of FSx A and restore it to FSx B. This can help reduce downtime, as the initial data transfer happens while FSx A is still running. The switch to FSx B would only require downtime during the final synchronization of any changes made after the backup.
https://docs.aws.amazon.com/fsx/latest/WindowsGuide/how-to-restore-backups.html
If this helped please remember to mark this answer as accepted. Thanks and good luck.
answered 2 years ago
Thank you again, so if we rule out the backup-restore solution, would the next best one be the use of the DataSync service?
answered 2 years ago
Considering you want to move from Multi AZ FsX to Single AZ, and you cannot restore a multi AZ FSx backup to a single AZ cfg, I would say DataSync is your best remaining solution.
If this helped please remember to mark this answer as accepted. Thanks and good luck.
answered 2 years ago
Relevant content
asked 3 years ago
asked 6 years ago
- AWS OFFICIALUpdated 2 years ago

Have you tried to replicate the existing filesystems using NetApp SnapMirror? Once synced you could break that replication and switch your applications to the other filesystem (FSx B). ref: https://docs.netapp.com/us-en/workload-fsx-ontap/clone-volume.html https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/scheduled-replication.html