ADSM-L

Re: Failed client backup

1999-03-12 23:52:04
Subject: Re: Failed client backup
From: Bruce Elrick <belrick AT HOME DOT COM>
Date: Fri, 12 Mar 1999 21:52:04 -0700
David, Joel,

It does remove cached files, before the file is sent based on the size estimate.
When the size exceeds the estimate, then it is too late in the algorithm.  You
could ask why don't they change the algorithm, but since we all don't have 
access
to the source code, we don't know whether such a change could cause other
problems.

You may want to ask: why is the client giving wrong estimates for the file size?

Is it the regular backup/archive client with compression=yes and
compressalways=yes and you are backing up precompressed files?  If so, consider
changing compressalways to no, since applying a compression algorithm to
pre-compressed data may inflate the file.

Is it a database backup application using the ADSM API?  Look for the ability to
hand-set the size estimate.  You could increase it to prevent the aforementioned
error.

Cheers...
Bruce

Joel Fuhrman wrote:

> It's even more annoying if you use caching.  I would like to know why it
> won't remove cached files.
>
> On Fri, 12 Mar 1999, Sanders, David wrote:
>
> > Have a client that gets a failed backup of a file and I find this message in
> > the Server log.
> >
> >  ANR0534W                         ) Copyright IBM Corp. 1993, 1997
> >                                           Topic lines 17 to 28 of 28
> > If pool name is a random access storage pool with caching enabled,
> > it is also possible that additional space can be made available in
> > this storage pool by eliminating cached files.  When the server
> > allocates space based on the size estimate provided by the client,
> > it frees space occupied by cached files if this space is needed to
> > obtain the estimated space.  However, if the server later
> > determines that the file size estimate was too low, it attempts to
> > obtain additional space that is not utilized, but does not delete
> > cached files to do so.  If you believe that pool name contains
> > additional space occupied by cached files, you can turn caching
> > off.  To free space that is already occupied by cached files, use
> > the MOVE DATA command for the volumes in pool name.
> >
> > I do have cache on the disk storage pool.  I can understand all of the words
> > above but can't figure out why this doesn't recover from the "wrong guess"
> > and adjust and then "backup" the file successfully!
> >
> > Comments?
> > Dave Sanders
> > Sr. Technical Consultant
> > MassMutual / The Blue Chip Company
> > 1295 State St, E060, Springfield, MA 01111
> > 413-744-5095
> >

--
Bruce Elrick, Ph.D.
Bruce Elrick, Ph.D.
mailto:belrick AT home DOT com
http://members.home.net/belrick/
<Prev in Thread] Current Thread [Next in Thread>