From: Fresel M. - hi c. e.U. <m.f...@hi...> - 2011-03-23 14:52:47
|
hi just signed onto that list :) RE for a Post by Jeffrey J. Kosowsky <backuppc@ko...> - 2011-03-03 15:43 > Conversely, I would like to raise a suggestion I mentioned a while > back with reference to 3.x. I think it would be great to have the > ability to mark a backup to be saved and not automatically deleted > based upon the expiry rules. Currently, I can fake it by renaming the > backup (+/- adding a symlink to the original name). But it would be > really nice to have an officially-supported convention that allows > individual backups to be protected. My recommendation would be to add > a suffix (e.g., .save) to the backup number. The particular use case I > have in mind is when you upgrade a system (or otherwise make major > changes) and specifically want to save the last backup of the > pre-upgrade version. ACK - It would be great to mark a single one as "undeletable" by any kind cleanup-mechanims Sometimes we create multiple backups in small timeframes (i. e before, during after some system changes) Some kind of "protect this backup from deletion" would be really nice .... |