Best practices for S3 File Storage Gateway for storing the backups

Some of the best practices are:

• Make sure you deploy your storage gateway closer to your client systems on which you will mounting the file share
• Have enough network bandwidth between your storage gateway and AWS Endpoints for both data & control plane communication
• If you have direct connect we highly recommend to use VPC endpoints for Storage Gateway & S3 (for S3 file type gateways) or have virtual public interface created on your direct connect. Refer the link: https://docs.aws.amazon.com/filegateway/latest/files3/using-dx.html
• If you are creating SMB file shares and for AD user authentication, make sure storage gateway is joined into Domain using Active Directory servers which are closer to Storage Gateway
• Allocate root & cache disks from high performance datastore disks for optimum performance
• Before deploying, ensure that network & firewall port requirements are in place. Please see here: https://docs.aws.amazon.com/filegateway/latest/files3/Resource_Ports.html
• We do not recommend having multiple sources of data write to S3 bucket prefix where the file share is configured and storage gateway uploading the data
• For all other best practices, refer here: https://docs.aws.amazon.com/filegateway/latest/files3/best-practices.html