Redeploy is the best practice.
That gateway VM is (mostly) stateless and outside of a few settings, such as local network configuration, all data is stored in AWS:
Restoring from a backup or a snapshot can be problematic for a number of reasons. First you could end up with 2 gateways that are identical clones, both talking to the service backend claiming to be the authority for the files/volumes/tapes. Second, restoring just the OS will result in the gateway needing to be reset since the cache/upload drives it expected are no longer there or have been replaced with new drives.
What is best practice around backing up the on-prem Storage Gateway VM ApplianceAccepted Answerasked 4 years ago
API Gateway and a FW Appliance will one do allasked 5 months ago
Storage Gateway (FileGateway) Security & Direct ConnectAccepted Answerasked 3 years ago
Is VMware SR-IOV supported or recommended on the AWS Storage Gateway appliance?Accepted Answerasked 2 years ago
Storage Gateway VTL experiencing slow uploadasked 4 years ago
What is the best practice and downtime for migrating an existing AWS environment to use the Transit Gateway?Accepted Answerasked 3 years ago
Storage Gateway ApplianceAccepted Answerasked 8 months ago
Remote shut down (not stop) gateway appliance VM?asked 4 years ago
Looking for a best-practice for building serverless application with amplify and api gateway and lambdaAccepted AnswerMODERATORasked 3 years ago
How can I get out of the local console of the AWS storage gateway?Accepted Answerasked 3 months ago