Hi Folks, After we have upgraded 7.5.0.1 suddly database image growth is increaed and we have increase file system size 100GB last month but within one month again it reached 95%...Please let us know any other modifcation required on 7.5.0.1 datagrowth reduction.. Thanks, Susi.S

It does seem extreme to be deleting backup images due to lack of space on the NBU server Would it not be better to add disk space rather than deleting your backups?

Why suddenly increased /opt/openv/db/image frowth is increasing after 7.5 upgradation

sksujeet
Level 6
12 years ago
The upgrade should not cause the space to be filled up in the images folder. The db/images directory has a list of directories for clients and if you have recently added new clients or changed the retention of your policies this might be causing the space to be filled up. Have you changed the policy to be full backups every day with long retention periods? You should have considered the space requirement while doing the upgrade.If your environment is very big you might need to do some analysis. You can either increase the space of your disk again after doing a good analysis or check the client in the images folder and find out which client is taking the space. Catalog Compression http://www.symantec.com/business/support/index?page=content&id=HOWTO34441 Catalog Archiving http://www.symantec.com/business/support/index?page=content&id=TECH36433 Also you can read NBU Admin Guide for Windows, Volume I catalog sizing If you can't increase the space then below is the link to move the images to different drive https://www-secure.symantec.com/connect/forums/tech-note-68160-moving-netbackupdbimages-different-path
Marianne
Level 6
12 years ago
NBU 7.5 actually stores a bit less in images folder because the header files are moved into EMM database.

The biggest space consumers remain the '.f'' files - same as previous versions.
Factors that play a role (extract from NBU 7.5 Admin Guide I):

■ Number of files to be backed up

■ Frequency of full and incremental backups

■ Number of user backups and archives

■ Retention period of backups

■ Average length of full path of files

■ File information (such as owner permissions)

■ Average amount of error log information existing at any given time

■ Whether you have enabled the database compression option.

I have highlighted the biggest 'culprits':
lots of files, lots of backups (especially full) with long retention periods.

Please see the sample calculations in chapter 17 of Admin Guide I under this topic: Estimating catalog space requirements.

Also verify that Image Cleanup is running at least twice a day (every 12 hours and after successful catalog backup) and that cleanup job completes with status 0.
mph999
Level 6
12 years ago
Adding to Mariannes excellent post, you could have some files left in the tmp directories eg:

/usr/openv/netbackup/db/images/<client>/<ctime>/tmp

Files go in there during backup, and get moved up a level if it completes successfully, and should be deleted if it fails. If the system has an unclean shoutdown, files could be left behind, but, I wouldn't expect this to be a regular occurance, so it not likely to be the issue - however, worth checking.

As Marianne said, NBU 7.5.x does noy use more catalog space, in fact it uses slightly less - I'm not aware of any known issues with it, so sussect the most likely cause is one of those listed by Marianne.

Martin
Mark_Solutions
Level 6
12 years ago
Can you tell us the Operating System you are using and if you have identified which area is suing up the disk space?

Is it the /images/ directory or somewhere else (tmp / temp etc.)?

Thanks
susindran_surul
Level 6
12 years ago
Hi Marianne,

We found some of client incremental backup size is more than 300GB for daily basis.Those client images utilizing much more size...Is the any way to compress image size of those clients alone ???
susindran_surul
Level 6
12 years ago
Its solaris and windows client...under /image/client only utilizing much more size....
susindran_surul
Level 6
12 years ago
Hi Martin,

under /tmp is not utlizing much more size..I could see /usr/openv/netbackup/db/images/<client>/<ctime>/catstore utlizing much more size...Is there any way to compress it?
sksujeet
Level 6
12 years ago
We found some of client incremental backup size is more than 300GB for daily basis.Those client images utilizing much more size...Is the any way to compress image size of those clients alone ???

That is normal the more the data the image would be bigger, we have incrementals more than 500 GB in our environment. You can do the archiving or compression on complete catalog as per my first post but not for some clients. Please consider again your retention If you have longer retention then this will happen. You have to plan accordingly as per you environment
susindran_surul
Level 6
12 years ago
Actually we have expired most of the incremental backup of the particular client but still its not removing from /opt/openv/netbackup/db/images/client/time-stamp..Please let us know how we will remove those files under /opt/openv/netbackup/db/images/client/time-stamp..
Mark_Solutions
Level 6
12 years ago
If they are on tape then use bpexpdate -deassignempty -force

If on disk use nbdelete -allvolumes

Followup using bpimage -cleanup -allclients

If you have already expired them then the last command above should do the trick for you