Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup databases #394

Open
tobiasBora opened this issue Sep 11, 2024 · 2 comments
Open

Backup databases #394

tobiasBora opened this issue Sep 11, 2024 · 2 comments

Comments

@tobiasBora
Copy link

tobiasBora commented Sep 11, 2024

Is your feature request related to a problem? Please describe.

It is common to backup databases, but saving the folder of the database itself may lead to inconsistencies, hence it is better to backup a dump of the database.

Describe the solution you'd like

Other tools like borgmatic provide options to backup directly a database https://torsion.org/borgmatic/docs/how-to/backup-your-databases/ and it would be great to have this in autorestic as well:

postgresql_databases:
    - name: all
mongodb_databases:
    - name: messages
      hostname: database5.example.org
      port: 27018
      username: dbuser
      password: trustsome1
      authentication_database: mongousers
      options: "--ssl"

Some people also suggested to allow backing up from stdin, which I also find it very interesting: #8 but in any case it would be nice to allow a more high-level support for databases.

@guest20
Copy link
Contributor

guest20 commented Sep 11, 2024

How does recovery work for these things? should autorestic also recover the dumped files and blast them back at the running dbms?

@tobiasBora
Copy link
Author

I guess it makes sense yes. Some users might also prefer to just read it from stdin and do something with it, so I guess it would be nice to provide both an automatic restore and a more manual one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants