Agreed, but I'm looking at specific instances, where the catalog
compression might be skipped, despite netbackup database backup
running regularly.

-ravi

On Tue, 17 Apr 2001, Bob Bakh wrote:

>Usually this has to do with the Catalogue backup not running, the
>compression takes place after the catalog backup.
>
>Bob
>
>-----Original Message-----
>From: Ravi Channavajhala [mailto:ravi.channavajhala AT csfb DOT com]
>Sent: Wednesday, April 11, 2001 12:13 PM
>To: Norm Szcyrek
>Cc: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: Re: [Veritas-bu] How do I force an image to be compressed?
>
>
>Tru /usr/openv/netbackup/bin/admincmd/bpimage -compress -allclients.
>As for why the backup images are not being compressed, I personally
>ran into the same situation, but couldnt isolate a pattern.  Be
>careful not to run compression while backups are active, selectively
>you can run compression on certain backup images too.
>
>What I also noticed is, when you request a recover, and the recover
>file is indexed in one of the compressed catalogs, it will uncompress
>it, but never compresses it back again until the netbackup db cycle
>kicks in.
>
>-ravi
>
>On Wed, 11 Apr 2001, Norm Szcyrek wrote:
>
>nszcyr>I have a number of image files which are not being compressed by the
>NBU
>nszcyr>daemons, even though I've configured a 2 day interval via the GUI. Is
>nszcyr>there a way to manually force a compression to some of the images to
>nszcyr>save some disk space? Yes I am out of disk space, which is why I'm
>nszcyr>asking this question.  I suspect that the
>/usr/openv/netbackup/bin/tar
>nszcyr>command with the '-x' parameter is the way to go, but I'd like to ask
>nszcyr>the experts first before I try it.
>nszcyr>
>nszcyr>NBU details: Solaris 2.6, NBU v3.1.1GA [yes I'll be upgrading to DC
>3.4
>nszcyr>soon]
>nszcyr>
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>