We use an external SQL Server database for our stash instance. It isn't totally clear in this configuration whether or not the database must be backed up separately, and what preparation must be done to restore stash from a backup generated by the client.
I have attempted to test a restore from a stash backup, starting with an empty stash-home and database (on our SQL server), which the stash-backup.properties file has been modified to reflect. The restore ran for a few seconds, then issued a statement to the effect of "verifying the database before restoring". It's been sitting in this state for over an hour.
Any guidence on how I would need to verify a backup would be greatly appreciated.
We ultimately had to move away from the backup client due to the size of the stash filesystem, and the amount of time it was taking to back it up. We couldn't afford to have stash locked for that duration.
We now backup the stash filesystem and database separately using traditional backup technologies, coordinating the time of the backups
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs