Google Drive Backup Followup

[sjarrell]

My previous thread has been looked so I decided to post a followup here. My scheduled Google Drive backup on a new installation was failing 100% of the time. I could do a manual backup perfectly at anytime so I knew my settings were correct.

Based on input from the forum, I changed my backup time from 2AM to 5:30AM and everything started working perfectly. Makes no sense to me at all but there must be something going on at my Google Drive at 2AM ET that makes the backup fail. I'm certainly not doing anything at that hour!

 

[AWS2P]

To avoid surprises like yours, since a moment, I set ramdom hours instead of 2 AM , I would set 2:04AM

 

[sjarrell]

Thanks. That's a good idea. Perhaps this will help someone in the future!

 

[cobaltit]

So I don't believe the API throttling is account specific so much as ingress node specific. So 2am might work for some folks and not others based on which node/server the Backup API hits but you don't really have any control over that so adjust the time is the easiest.

 

[sjarrell]

So I don't believe the API throttling is account specific so much as ingress node specific. So 2am might work for some folks and not others based on which node/server the Backup API hits but you don't really have any control over that so adjust the time is the easiest.

Makes sense. Thanks.