how does NBU uses/interpret hd space?
NBU 7.6.0.3
a few days back, i have 3TB free in my master where backup images are stored. today. i found i only have 600GB free!
upon checking, i found the pending duplication images are waaay more than my available partition size for NBU backup images:
[root@ovmmanager admincmd]# ./nbstlutil report
Backlog of incomplete SLP Copies
In Process (Storage Lifecycle State: 2):
Number of copies: 8605
Total expected size 64615866 MB
SLP Name: (state) Number of copies: Size:
Daily_Policy (active) 7977 11515412 MB
Dec31_Policy (active) 51 529501 MB
Exchange_Daily_Policy (active) 36 15424821 MB
Oracle_Daily_Policy (active) 520 37102487 MB
SLP-PureDisk-to-Tape (active) 5 4001 MB
Weekly_Policy (active) 16 39643 MB
Total: 8605 64615865 MB
here is from my master server space issue:
[root@ovmmanager admincmd]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 77G 30G 44G 41% / tmpfs 24G 112K 24G 1% /dev/shm /dev/sda1 504M 61M 418M 13% /boot /dev/sda3 68G 448M 64G 1% /opt /dev/sda7 32G 176M 30G 1% /u01 /dev/sda5 68G 678M 64G 2% /var /dev/mapper/mpathlp1 9.8T 9.2T 678G 94% /NBU_DSU1
i can't understand why my pending duplication is 37TB just for Oracle alone!?
It's called deduplication...
In Job details you should see something like this:
... scanned: 493776469 KB, CR sent: 11777370 KB, dedup: 97.6%
In above example, the image size is 493GB, but only 11GB is written on the MSDP pool due to 97.6% data that already exisits.
Data is rehydrated when written to tape, therefore the full image size is reported in nbstlutil output.
All explained in NetBackup Deduplication Guide
You may also want to read up on this topic in the same manual:About MSDP storage capacity and usage reporting
And this recent post:
https://vox.veritas.com/t5/NetBackup/How-to-clean-up-storage-on-the-DSU-for-puredisk-linux-storage/m-p/824442Do not delete the bhd container files. They contain chunks of finger-printed and deduped backup image data. See this post:
If you manually delete them then you will definitely corrupt at least one backup image, but possibly all of your backups.
Where you say "regarding the bhd containers, while i may agree they may refer to backups on tape"... this is perhaps not quite the best way to describe it.
The bhd container files do not refer to tape. The the entire set of bhd container files contain the entire set of "copies of backup images" residing within the dedupe disk pool. The copies of backup images on tape are completely separate copies. And, it is the "NetBackup Catalog" which knows about all backup images, and so... it is the NetBackup Catalog which therefore knows which backup images have copies within disk pools, and which backup images have copies on tape.
