Drive Allocation with FSx

  • We're in the process of planning the migration of our whole platform into AWS. The current thinking is that we will host our instances on EC2 and use FSx as the file system. However, I can't find anything about whether a separate FSx instance is recommended for each drive needed by SQL Server. It's good practice to split data files, log files and tempdb out on to different drives to minimise contention but I'm really not clear about how this split is best managed with FSx. I've seen the EC2 instance storage recommended for tempdb but should I use a different share from a 'central' FSx instance or is a discrete instance for each drive best.

    The extension to this is whether a single large FSx instance for all EC2 instances is okay or is it best to use a discrete FSx for each EC2? I expect all of this will crash on the rocks of cost but I'm struggling to get my head around it.

    On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
    —Charles Babbage, Passages from the Life of a Philosopher

    How to post a question to get the most help

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply