/opt/openv/netbackup/db/images/ utilizing more space

[RXZrider]

Hi Experts,

Recenlty twice our /opt (total capacity = 101GB) space filled up with 100% and the backups failed after NBU services went down.

Logs verbose = 0

However noticed that in /opt/openv/netbackup/db/images/ 2 clients size was huge

serverabc - fileserver - 21GB

serverxyz- exchange dag - 11GB

Is there any way i can run bpimage -[de]compress [-allclients | -client <name>]  & compress for the above 2 servers. Also need to know the side affects post doing this.

[RamNagalla · Accepted solution]

Hello,

101GB for catalog images is bit low.. but it again depends on the number of backups that you perfromed along with the retenciton..

you propably needs to estimate the size required for the catalog images and increse the space..

below tech note will expline how to estimated the catalog image space requiermentes.

http://www.symantec.com/business/support/index?page=content&id=HOWTO99765#id-SF0S0157290

you can also try catalog archinving to get the immediate space..

http://www.symantec.com/business/support/index?page=content&id=TECH36433

http://www.symantec.com/business/support/index?page=content&id=TECH49105

but for long term plan its better to increase the space.

[Marianne]

Nagalla is right - 101GB is relatively low. Even 200GB image size is considered as low/small.

As per HOWTO99765 in Nagalla's post, it is best to calculate image space up-front and provide adequate space.

Catalog compression may bring relief for now, but each time you need to browse images for restore, the images need to be uncomressed.

Other that catalog archiving, you can move images to another, bigger partition and link original location to new one.
How to to move the image catalog :  http://www.symantec.com/docs/TECH69970