0

We have a MSSQL database which has two nodes and is using Always On FCI for High Availability purpose at our on-premise location.

As most of you aware FCI SQL requires the two nodes to share the same storage. At our on-premise facility we use a shared SAN storage and it works great. We run it on a VM with Windows Server where the SAN drives are mapped to as a local disks. All of our database including the master db are stored on these SAN disks.

enter image description here

We are trying to migrate to AWS and I'm facing an issue. AWS does not support Shared SAN so we utilize their FSx service which act like a SAN. I found this article that talks about setting one up from scratch but not migration.

enter image description here

We copied the data files over to AWS FSx and we also copy the VM over and convert it to EC2 instance but I cannot bring up the database services because all of our mapped drives are no longer there since SAN drives are not part of the VM. Is there a method or steps I need to do before or after so that I can at least bring up the SQL master database and start updating the data file and log file path of the rest of my databases to AWS FSx?

enter image description here

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.