It should be ok to use BackupPC_backupDelete as Michael suggested, even without taking a new full backup. I recommend using the -r option, which will re-run BackupPC_refCountUpdate:
su backuppcUser
BackupPC_backupDelete -h HOST -n 134 -r
It will merge changes into the prior backup #133 so that viewing #133 will look the same. But it should remove references to the additional files since they are not present in #133 (if people want to know the details, #133 has delete attributes for the new top-level directories in 134, so the merging will not copy them). After two nights of BackupPC_nightly runs the extra pool files should be removed.
BackupPC_backupDelete also supports the option of deleting just a portion (ie: a list of directories) of a backup rather than the whole backup. That should also have the desired effect - the files shouldn't be merged into the prior #133 since they weren't present in #133.
let me try full backup first and then wait for night maintenance. but i'm sure that pool size will be same as that not needed files was backed up and now will be in pool for history.
for me it's not big problem as i have free size in pool and can wait 8 weeks (our backup policy) until files will be deleted. but may be we need to find solution to help other users in future
Ah, ok. I would run a Full backup (now considered "Filled"). That's the safest move prior to removing 134. The most recent backup is always Filled, but were talking about important data so I don't see a problem with doing on more Full (Filled) backup to ensure safety.
Craig - anything wrong with my logic here?
Cheers,
mph
On 2017-05-21 20:29, Alexey Safonov wrote:
Thanks for quick reply.
but as i understan in V4 full backup in last folder. My question is related to bug in 4.1.2 (that is now fixed). But because of that bug i have regular backup 133 , abnormal backup 134 (it's huge in size) and again normal backup 135
i need to really cleanup my NFS storage. So if i delete 134 it will not help? is it correct?
I would strongly suggest the use of BackupPC_backupDelete -n 134 to properly remove the backup. It should be fine to remove. You'll lose whatever changes occurred between 133 and 134.
Cheers,
mph
On 2017-05-21 19:36, Alexey Safonov wrote:
Hi, All
I'm usinv V4 backuppc. is it safe to delete one intermediate backup? for example we have in /pc/litspc123 dirs 133 135 and 135
is it safe to delete backup 134 directly from nfs?
Alex
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
