08-03-2018 01:02 PM - last edited on 08-03-2018 02:15 PM by Marianne
08-04-2018 10:53 AM
08-06-2018 12:16 AM
Things that can cause increase in NetBackup catalog size
1. Accelerator backups. If you have configured accelerator full backup to run on daily basis, it will consume lot of catalog size.
2. Bare Metal Restore / True Image Restore (TIR) backups. There were some issues in the past with TIR pruning that caused growth in catalog.
3. Automatic Image Replication (AIR). All NetBackup versions are affected by this issue, It will be fixed in future release. When an AIR backup image expires, it does not delete/remove files file (.f file, these are the large files in NetBackup catalog) from NetBackup catalog which causes unwanted growth in catalog size.
08-06-2018 12:43 AM
@Anshu_Pathak, it seems that @IsrBla00 is saying that there is a problem with "catalog backup folder increasing".
(Although this post was originally tagged onto a post about the catalog size increasing.)
It would be great if we can get more info about what exactly is increasing.
08-06-2018 10:53 PM
@Marianne Thank you for pointing that out, I love such issues where (example) catalog size is 200GB but catalog backup is 400GB. Enable bpbkar logs on master with high verbosity, take catalog backup. Now run this againt bpbkar log files.
cd /usr/openv/netbackup/logs/bpbkar
grep PrintFile <bpbkar_log> | sort | uniq -c
Count value should be 1 for each file however if that is not the case then same file is getting backed up multiple times. Once you figure out which client it is, you can check for ALTPATH file presence.