Storage gateway - volume keeps restarting bootstrapping

0

A new storage gateway keeps restarting bootstrapping of the volume - nevber getting beyond about 25%, despite no new data being added. This has been occuring for last 40h or so.

Metrics show every ~65min or so, the queud writes are reset to 500GB (size of the volume). I've tried restarting the gateway, but no change.

Any suggestions? Thanks

nickjp5
asked 2 years ago332 views
4 Answers
0

Hi Nick,

Sorry your experience was not up to expectations. If you can give me the storage gateway ID and region we could look at the metrics internally and, perhaps, be able to provide additional insight for you.

AWS
answered 2 years ago
  • Thanks Mike. Not sure how to DM, so.... sgw-74FE0B1D, ap-southeast-2

0

Nick, I took a look at the internal metrics of the gateway...and there aren't any. Based on the fact that no metrics were uploaded during this gateway's lifespan, I can only take an educated guess that the connection from your Storage Gateway device to the AWS cloud was not connecting properly. That would explain why the bootstrapping process never progressed and why metrics were never received. The cause is not knowable since the gateway is now defunct, but the culprits could have been misconfigured network, firewall blocking of required ports, severely inadequate bandwidth, or a TLS/certificate issue. There could have been other causes, but these are the ones that come to mind based on my experience with the service.

AWS
answered 2 years ago
0

Hello, I'm Mike with the Storage Gateway team.

It is important that you not restart the gateway during the bootstrapping process as this forces the gateway to begin the process over again starting at 0%. Even if the percent completed appears "stuck" at 25%, the process is still continuing and will eventually reach completion (as long as the process isn't interrupted by a reboot). The process is not linear in respect to the percentage completed and will appear stuck at times and will advance rapidly at other times.

You can shorten the time bootstrapping takes by providing the gateway with additional processors. The minimum number of processors is 4 CPUs, but if you increase to 8 processors (or more if you can spare the processing capacity), the bootstrapping will run faster. It will not, however, cut the time in half. We're talking 5-15% faster. Adding CPUs will restart the process again since you'll need to turn off the gateway to add the CPUs.

Let me know if you have any additional questions.

AWS
answered 2 years ago
0

Thanks Mike. I left it running for 10 days, during which time it never completed bootstrapping - continually restarting: https://ibb.co/gFTsg6L

It appears something was broken as attempting to detach or delete the volume returned an error. In the end I had to delete the whole gateway. Not a great experience.

nickjp5
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions