StorSimple 8100 replacement

Mark Robson 41 Reputation points
2021-03-29T10:29:55.147+00:00

Hi all, We are planning the replacement/migration from StorSimple to Azure File Sync as it's going EOL next year. So I know that there's a well trodden upgrade path and nicely documented (thanks MS). So we need to replace the SS hardware with some other storage device. We need to leverage the local caching functionality on recently accessed data as a must. But what I'm struggling to figure out is this: How do we calculate local caching storage requirements? I need to figure out how much disk storage we'll need. TIA. Mark.

Azure StorSimple
Azure StorSimple
A Microsoft hybrid cloud storage solution that combines on premise hardware storage and cloud storage.
25 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sumarigo-MSFT 43,801 Reputation points Microsoft Employee
    2021-03-30T17:14:17.337+00:00

    @Mark Robson Welcome to Microsoft Q&A, Thank you for posting your query!

    Typically we recommend a dedicated cache volume of 10 -20% of data size and then monitor cache hit ratio to fine tune. Towards the top end of that range for very hot data with more random access patterns and less than 10% for archive (for archive you do not expect to hit cache anyway). For sizing guidance on the hardware see Planning for an Azure File Sync deployment | Microsoft Learn but in the migration scenario ignore the initial sync memory guidance.

    Hope this helps!

    Kindly let us know if the above helps or you need further assistance on this issue.

    ----------------------------------------------------------------------------------------------------------

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Mark Robson 41 Reputation points
    2021-04-01T08:20:01.443+00:00

    Thanks very much for the help Sumarigo. Much appreciated.
    Mark.

    0 comments No comments