cancel
Showing results for 
Search instead for 
Did you mean: 

NBU 6.0 catalog questions

Patrick_De_Gior
Level 2
Hi All,

We are using NBU 6.0 MP2 and since a few month we had size problems with our catalogs.

Our catalog policy is configured as follow :

Full catalog backup every Sunday from 8PM to midnight. Multiples copies. 1 to disc (folder d:\catalog) and the other to tape.
Retention for the disc is 1 month and 1 day for the tape copy.

Differential Incr. catalog backup after each backup session. Multiples copies. 1 to disc (folder d:\catalog) and the other to tape.
Retention are both set to 1 week.

The disc catalog size is currently 111 GB.
It contains 4x 27GB files (the full catalog) + a tons of "small" other file.

Do we really need to keep the full catalog for 1 month ?

What are the best practices for the catalog backup retention ?

We are struggling with the d: drive to gain spaces.....but we will soon loose the war...

Thanks for any help
Patrick
5 REPLIES 5

Taqadus_Rehman
Level 6
The NetBackup catalog resides on the disk of the NetBackup master server. The catalog 
consists of the following parts

Image database 
NetBackup data stored in relational databases
NetBackup configuration files

you can not delete the catalog backup files untill the retention expire. you can manually expire it but i would not recommend you.

As you are running out of disk space what you can move image DB to another partition on your hard disk of SAN disk. this document will help you in relocation image db
http://seer.entsupport.symantec.com/docs/269996.htm

 

Srikanth_Gubbal
Level 6
Certified
hi,

Page no 23 give the details of calculating size required for catalog and best practises;
Page no 55 shows the details of Netbackup Catalog Stratagies.

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/307083.pdf

Admin Guide 1 gives details about Catalog archiving.

Andy_Welburn
Level 6
Excerpt from the "Help Topics":
"...
The image catalog has information about all client backups and is accessed when a user lists or restores files. NetBackup allows you to compress all portions of the catalog or only older portions of the catalog. No method selectively compresses image-catalog files other than by age.

Control image-catalog compression by setting the Global Attributes property, Compress catalog interval. Use this property to specify how old the backup information must be before it is compressed. Specify the number of days to defer compression information, thus users who restore files from recent backups are unaffected. By default, Compress Catalog Interval is set to 0 and image compression is not enabled.

When numerous compressed image-catalog files must be processed, the backup session is extended until compression is complete. The additional backup time is especially noticeable the first time you perform the compression. To minimize the impact of the initial sessions, consider compressing the files in stages. For example, begin by compressing the records for the backups older than 120 days. Continue to reduce the number of days over a period of time until you reach a comfortable setting.

Compressing the image catalog can accomplish two objectives:

•To reduce greatly the disk space that is consumed.

•To reduce the amount of media that is required to back up the catalog.

The amount of space that is reclaimed varies with the types of backups you perform. Full backups result in a larger percentage of catalog compression than incremental backups. Normally, more data is duplicated in a catalog file for a full backup. Using catalog compression, a reduction of 80% is possible.

This reduction in disk space and media requirements is achieved at the expense of performance when a user lists or restores files. Since the information is uncompressed at each reference, performance degradation is in direct proportion to the number and size of compressed files that are referenced. If the restore requires numerous catalog files to be uncompressed, you may need to increase the time-out value that is associated with list requests. Change the time-out value by changing the List Files Timeout General property setting on the client.
..."

Stumpr2
Level 6

Do we really need to keep the full catalog for 1 month ?

No
Catalog backups are only of value for the day that they are created. An incremental backup is only of value if it has the ability to access the last full and its incremental siblings. Therefore since you only need the last full backup and not the previous three, I suggest changing the retention of the full backup to match the length of time that the incrementals will need to access it.


 

Patrick_De_Gior
Level 2
Thanks a lot for all your answers !

Regards,
Patrick