Cant compress Netbackup Catalog DB

What is the value in Host Properties -> Master -> Global Attributes -> Compress catalog interval ?

Only images older than the value in this field will be compressed.

Compression will automatically be done next time Image Cleanup job runs (default is every 12 hours).

Hello,

HOWTO34441 talks about just this. Please note that Symantec discourages manually compressing or decompressing catalog backups using bpimage -[de]compress or any other method. Manually compressing or decompressing a catalog backup while any backup (regular or catalog) is running results in inconsistent image-catalog entries.

As Marianne said, Control image-catalog compression by setting the Global Attributes property, Compress Catalog Interval

Thanks for your response Marianne

Compress Catalog Intervel is set to 1 and several image cleanup jobs ran as well, we had moved images on last friday (11th July14). still image folder size is uncompressed on the new Disk drive.

Please create bpdbm log folder under netbackup\logs and restart NBU Database Service.

After next Image Cleanup job, please copy bpdbm log file to bpdbm.txt and upload as File attachment.

PS:
If images have been moved to a new drive with more space, why do still need to compress images?

Size of the folder at source location was 470GB in size and compressed size was around 170GB.

Size of the new drive is 500GB only.

Hi, Raghav_tv

Here are my suggestions:

1. If possbile, please restart NBU services. Not sure if it's necessary after setting Compress catalog interval property.

2. Please try to run manually the following command to kick off the compression operation. From job detail, you could see some info related to image compression.

bpimage -cleanup -allclients

---cleanup
Deletes expired images, compresses the images that are scheduled to be
compressed, and prunes the TIR information from the specified images.

3. Please check related compress tool on master server, as netbackup will use compression command on OS, if no any compression tool on OS, it should not compress image actually, though you'll see compression info in step 2. e.g. gzip, ncompress, zip, etc.

Please share it, if you have any progress.

Thanks

 

We did restarted NBU services and ran bpimage cleanup -allclients as well but there is no change in size of images folder on the new Disk. Both Size and Size on Disk are still same (470GB in Size)

Before we moved the image folder, size and size on Disk were different. Size was around 470GB and size on Disk was 170GB in size.

 

Compress catalog is set since long time and no changes were made to it.

And its not the complete image folder that was moved to newly allocated Disk, but only one image folder from c:\program files\veritas\netbackup\db\images was moved to new Disk.

Hi, Raghav_tv As Marianne said, could you post bpdbm log? where it explicitly log why (or why not) we are compressing an image Run "bpimage -cleanup -allclients" or wait next image cleanup job, and collect bpdbm log on master. In addition, if compression image is successful, all *.f files will be stored as *.f.Zl, Zl means the image was compressed. do you see this type of files? for 76, it uses embedded tool to compress image. for 75, it uses OS' tool or external tool. in my 7602 environment, the images older than 86400 seconds have been compressed to *.Zl on new location. Thanks

Hello Walker,

I do see some errors in BPDBM log file. I've enclosed the attachment.

And compressed image files are still being stored as *.f only.

Thanks