-
Notifications
You must be signed in to change notification settings - Fork 25
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
rsnapshot support #6
Comments
Note: using the myserver-DATE-TIME format would be rotation-tolerant. Usefuly if it is not just a one-time import, but regularly used. Backups that were already imported would map to same name again and would be rejected (assuming that mtime isn't touched), only backups with unseen timestamps would get processed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rsnapshot creates a dir structure like this under its root directory:
alpha, beta, gamma, delta is the snapshot-kind name (high frequency to low frequency, e.g. alpha is every 4 hours, beta daily, gamma weekly, delta monthly - via cronjob).
.N (0..N) is just a number - 0 is newest snapshot of its kind.
Below these directories, there is another layer of directories with the "backup set" (e.g. the hostname can be used as a backup set name), e.g. .../alpha.0/myserver/.
For borg, the archive name could be
myserver-alpha.0
and the timestamp for the borg archive is taken from rsnapshot directory mtime.Alternatively, we could use myserver-DATE-TIME as archive name, but then the relationship "all these archives are in same snapshot" is less clear as the DATE-TIME slightly differs when taken from the backupset dir (we could also take it from snapshot dir, then it would be the same).
The text was updated successfully, but these errors were encountered: