Backing up www directory once a day and the DB dump hourly #511
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#511
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I want ot backup
/var/www/
once a day (at night) but the mysql DB on the same server every hour to borgbase. So after reading https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/ it seems like I have to create two almost identical config files. Fine. Still, I do not see how this would work and if would not rather have (also) to runborgmatic
from cron given my use case.Would I need two distinct lines in the crontab (https://projects.torsion.org/borgmatic-collective/borgmatic/src/branch/master/sample/cron/borgmatic) with e.g.
The docs only explain the retention but I fail to see how this would work without having different execution times for borgmatic with cron. Or can I achieve the same just with having two different config files? I am puzzled 🙃
That's correct. borgmatic doesn't handle scheduling itself, so if you have scheduling needs, you'll need to use an external tool like cron or systemd. And if you have two distinct scheduling needs, then you'll need two separate entries in cron (or systemd) as per your example. And that does mean two separate borgmatic configurations.
Does that answer your questions, or did I miss something?
I see. Thanks for clarifying. (Maybe the need for calling differently via cron could be mentioned in the docs though.)
This is no longer the case! As of borgmatic 1.6.0, you can easily share common configuration among separate borgmatic configuration files. See the documentation on include merging for details.