Reduce Catalog size

What data do you have that needs to be held until 2038 ???

800GB is abouyt the max limit that is 'recommended' (well, if you speak to Symantec Engineering) - archieving is OK, but there is always a risk on 'recovery' (so make multiple copies).

Perhaps it's time to consider a new master server and split the clients ...

The problem with the catalog size is really the recovery time - if you lose the server, you have a 'long' wait to get things working.  If you have two servers, the load is spilt, and if you lose a server, you still can run 50% of the backups.

 

That has changed with NBU 7.6.x:

The amount of data that is held in the online catalog should not exceed 2 TB. Archiving can be used to keep the online portion of the catalog below this value.

The recommendation is due to the time that you will need to backup and recover the catalog.

 For the original question you have two possibilities:

1. Catalog Archiving: http://www.symantec.com/docs/TECH36433
2. Catalog Compression:  http://www.symantec.com/docs/HOWTO105948

Also, review this TN: Recommendation for sizing the catalog http://www.symantec.com/docs/HOWTO99788

I forgot to mention that I changed the retention policy to 3 months and saw that image cleanup was done.But still  even couldn't removed expired images

1- I manualy deleted files from last year so it means I will not have any restore point from last year?

2- If I change the Catalog saving location to another drive can I still able to restore data from old images?
 

Tx

Manually deleted without expire the image from the catalog? 

You can move the cataloig to another drive following this TN (you'll be able to restore old images):

 http://www.symantec.com/docs/HOWTO105947

No I don't need data for that long. I am new to NetBackup and figured out that it was in Infinite state.

From now onward I will be selecting only 1 to 2 months retention.

Thanks

Change of retention will not change backup already made with a infinity backup. To apply a new retention you need to use the bpexpdate -recalgulate command.

See symtax for bpexpdate here :

http://www.symantec.com/docs/HOWTO103811

From the technote 

# bpexpdate -recalculate -backupid host_123467 -ret 4 

Be ware that bpexpdate is a dangerous command, use it with caution. The retention level need to be adjusted to your configuraiton (see bpretlevel -l).

Yes .

For moving the catalog I will try it on my test server.

Thanks

So, there might be the answer.

Adjust the times backups are held for, adjust the exsisting backups already taken, which will mean some expire - thus reducing the catalog size.

Then, see if there is still an issue.

If you have deleted the files from the image database without expiring the image, you will be able to find the image in NBU GUI but the restore can not be done.

You should find that images and expire from the command line or the GUI.