@scottalanmiller said in Bookstack Backup to S3:

@wrx7m said in Bookstack Backup to S3:

@dbeato said in Bookstack Backup to S3:

@wrx7m said in Bookstack Backup to S3:

@dbeato Are you running bookstack in AWS?

Not at the moment. I am just backing up to S3.

Look at Wasabi for S3 compatible object storage. Significantly cheaper.

Yup, can't think of any reason to use S3 unless you are hosted on AWS and aren't using it for backup but for production storage. And even then, not the majority of the time. S3 is too expensive and doesn't really offer anything except locality that is of any specific value. B2 and Wasabi beat it a lot.

Sorry, I posted this as S3 but I should change it to Wasabi. It is the same Idea for both.

@Dashrender said in Make an osTicket Database Backup:

Total DB Admin noob here - so bare with me.

Does this include the username/password setup for this DB? or does that need to be maintained separately?

i.e. you have to rebuild from this backup - do you just create a brand new SQL user and grant them rights to this DB upon import, then use that new account to give access to the app?

In typing out my question I kinda assume the answer is the second bit - you just create a new user and assign them rights.

Correct. The user and the database are separate things.