![]() Which means after seven days the Crashplan snapshot will be ignored and unless that ignoring is a different kind of ignoring than the one triggered by the -ignore option, which, I understood, means that that snapshot risks losing some of its chunks.īut at the same time, you confirmed above that No wait, the seven day period will eventually apply:ĭuplicacy by default will ignore repositories that have no new backup in the past 7 days. In this scenario, there is, by definition, always going to be an inactive repository, which means no fossils will ever be deleted. the OP), because Nelvin’s ingenious solution won’t really work, unless I am fine with fossils piling up in my story for ever:įirst do a full backup with it’s own snapshot, then create a new, active one, do the full backup again (which should not waste any storage due to deduplication) and then use that one as your active archive Okay, so basically, you only want to use the -ignore option if you have such an inactive repository and you don’t mind the backups from that repo to be be potentially destroyed, right?īut that also means that we’re basically back to square zero (i.e. It’s a bit less flexible and users are forced to use that specific tag, but its so much easier to implement (and simpler to use)… protected) as marking an undeletable snapshot.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |