You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our backup scheme is such that individual machines run attic to back up their files to a common NFS repo. I then want to back up the entire collection of backups offsite using tarsnap. Unfortunately, occasionally the attic backup kicks off after a tarnsnap backup has started. Often this causes tarsnap to error.
What I would like is a feature where if attic detects a certain file is will wait to begin it's back up until that file is gone. There would need to be a timeout on this behavior obviously. This would let be get reliable offsite backups while maintaining hourly backups via attic.
As a workaround I can wrap attic to create the behavior I want.
The text was updated successfully, but these errors were encountered:
Basically it would be an additional lock mechanism. And locking has some gotchas. It would be far easier if this is handled in some external logic - even better by tarsnap to only start attic when it is not working. :-)
Our backup scheme is such that individual machines run attic to back up their files to a common NFS repo. I then want to back up the entire collection of backups offsite using tarsnap. Unfortunately, occasionally the attic backup kicks off after a tarnsnap backup has started. Often this causes tarsnap to error.
What I would like is a feature where if attic detects a certain file is will wait to begin it's back up until that file is gone. There would need to be a timeout on this behavior obviously. This would let be get reliable offsite backups while maintaining hourly backups via attic.
As a workaround I can wrap attic to create the behavior I want.
The text was updated successfully, but these errors were encountered: