On 11/01/2016 02:07 PM, Adam Goryachev wrote: > On 1/11/16 21:59, Gandalf Corvotempesta wrote: >> 2016-11-01 11:35 GMT+01:00 Johan Ehnberg <[email protected]>: >>> Changes in BackupPC 4 are especially geared towards allowing very high >>> full periods. The most recent backup being always filled (as opposed to >>> rsnapshots hardlink pointing to the first), a full backup is not >>> required to maintain a recent and complete representation of all the >>> files and folders. >> So, with the current v4, deleting a full backup doesn't break the >> following incrementals? >> In example, with Bacula, if you delete a "full" backup, all following >> backups are lost. >> In rsnapshot, you can delete whatever you want, it doesn't break >> anything as long as you keep at least 1 backup, obviosuly
Correct, if by full you mean what in v4 is called filled (also correct for both full and incremental). _backupDelete should merge it properly. This is specifically mentioned in the documentation. > Ummm, silly question, but why would you want to delete a backup? > BackupPC supports automatic removal of old backups based on the schedule > you provide, you shouldn't be manually messing with the backups. If you > need a different schedule, then adjust the config, and let backuppc > handle it for you. > > So, can you explain the need to delete random backups manually? > Generally, if you need to do something weird like that, then either you > are doing something wrong, or you are using the wrong tool. I can think of many scenarios: - An otherwise small client has an error that fills the logs with gigabytes or terabytes, the error was fixed, new backup run manually, no need to save the bad one for an eternity - When setting up a client, maybe the first backup contains a lot of installation files that unecessarily were backed up - you want to delete just that one, but not change the overall retention periods - A mount was temporarily unavailable on the client when the backup ran so the backup is not representative of how the client is normally - You shorten the retention times and want to free up some space asap - With v3, I've seen some partial backups that had problems causing everything to be transferred again over a slow link and thus needed to be deleted. It seems v4 won't have that thanks to pool matching before transfer but deleting sure would be handy if it does. Best regards, Johan ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
