Forum Discussion

Arun_K's avatar
Arun_K
Level 6
11 years ago

nbu catalog

HI Champs,

 

1.How can I check if My catalog is compressed?

2.Why when i run bplist,or bpimagelist of a particular client or browse images,Why that client images is decompressed?

3.why we uncompressed a particular client using bpimage -decompress client name.What is the use of that? I mean NBU is uncompressing the images of a client when we are browsing the images.so why this decompress command?


http://www.symantec.com/connect/forums/should-i-compress-my-catalog

 

NBU 7.1

SOLARIS

  • 1. Correct.

    2. No. Next time catalog maintenance runs, it will compress all images older than 10 days.

    Best to ensure that the master has enough disk space so that catalog compression is not needed.

10 Replies

  • Check Global Attributes in host properties on your master server.

    If you read through About image catalog compression in chapter 18 of NBU Admin Guide I, you will find answers to all your questions.

    Please read though this section and then come back with the answers.
    I will happily mark your post with your own answers as solution as that will show us that you are putting some effort into finding answers yourself....

  • About image catalog compression
    The image catalog contains information about all client backups. It is accessed
    any time a user lists or restores files. NetBackup lets you 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.
    See “Global Attributes properties” on page 138.
    Note: 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. When users list
    and restore files, the results can be incorrect.
    If you choose to compress the image catalog, NetBackup uses the compress
    command on the server to perform compression after each backup session. It does
    Protecting the NetBackup catalog
    Estimating catalog space requirements
    not make a difference to NetBackup if the backup session was successful. The
    operation occurs while NetBackup expires backups and before it runs the
    session_notify script and the backup of the NetBackup catalogs.
    The time to perform compression depends on the server speed and the number
    and size of the files being compressed. Files are compressed serially, and temporary
    working space is required in the same partition.
    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 effect 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 accomplishes the following objectives:
    ■ Reduces greatly the disk space that is consumed.
    ■ Reduces the 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, increase the timeout value
    that is associated with list requests.
    Change the timeout value by changing the LIST_FILES_TIMEOUT option in the
    bp.conf file of the client.
    See “Uncompressing the NetBackup catalog” on page 769.
    See “Indexing the catalog for faster access to backups” on page 767.
    Uncompressing the NetBackup catalog
    You may find it necessary to uncompress all records temporarily that are
    associated with an individual client. Uncompress the records if you anticipate
    large or numerous restore requests, for example.
    Perform the following steps as root on the master server to uncompress the
    NetBackup catalog.
    769
    770
    Protecting the NetBackup catalog
    Estimating catalog space requirements
    To uncompress the NetBackup catalog
    1 Verify that the partition where the image catalog resides has enough space
     to uncompress the client’s image records.
    2 Stop the request daemon, bprd, by running:
    /usr/openv/netbackup/bin/admincmd/bprdreq -terminate
    3
    Make sure that bpdbm is running:
    /usr/openv/netbackup/bin/bpps
    4
    Expand Host Properties > Master Servers. Open the properties of a host. On
    the Global Attributes properties, clear the Compress Catalog Interval check
    box.
    See “Global Attributes properties” on page 138.
    5 Set the Compress Catalog Interval Global Attributes property to 0.
    6 Change your working directory to /usr/openv/netbackup/bin and run the
     command:
    admincmd/bpimage -decompress -client name
    7
    Restart the request daemon, bprd, by running:
    /usr/openv/netbackup/bin/initbprd
    8 Perform the file restorations from the client.
    9 Set the Compress Catalog After Global Attributes property to its previous
     value.
    The records that were uncompressed for this client are c
     

  • 1.How can I check if My catalog is compressed?
    in global atributes section.

    2.Why when i run bplist,or bpimagelist of a particular client or browse images,Why that client images is decompressed?

    not found.


    3.why we uncompressed a particular client using bpimage -decompress client name.What is the use of that? I mean NBU is uncompressing the images of a client when we are browsing the images.so why this decompress command?

    not found.


    4..if my interval is 10 days.what that means?

  • You really need to read carefully and not just copy and paste. That only tells us that you found the section in the manual.

    2.  Tell me, if you manually compress a normal text file, can you read it in that compressed format?
    Is it true that you need to uncompress it before you can read it?
    The same is true for NetBackup!

    It is perfectly clear from the following lines in the manual that NBU is unable to read a compressed image file :

    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 referenceperformance degradation is in direct proportion
    to the number and size of compressed files that are referenced.

    3.
    The above lines is also your answer, along with the following:

    You may find it necessary to uncompress all records temporarily that are 
    associated with an individual client. Uncompress the records if you anticipate 
    large or numerous restore requests

    4:

    See “Global Attributes properties” on page 138.

    Read through Compress catalog interval in this section on page 140.

  • compress catalog interval This property specifies how long NetBackup waits after a backup before it compresses
                            the image catalog file.

     

     

    1..if it is 10 days.So all image catalog will be compressed but not new 10 days data.Correct?

     

    2.After decompress with the command,I also have to compress it after restore?
     

  • 1. Correct.

    2. No. Next time catalog maintenance runs, it will compress all images older than 10 days.

    Best to ensure that the master has enough disk space so that catalog compression is not needed.

  • Sigh...........

    Yes....

    You have asked SOOOOO many catalog questions over the last 2 years that I assumed you will know that catalog maintenance happen during the Image Cleanup job.

    If you REALLY need confirmation, read the bpdbm log on the master server after the next Image Cleanup job.