Jane, here is an e-mail and it's response.
Can you explain what they are talking about?
Why does ADSM write the data to different tapes instead
of appending the data?

Backup Boy



Robert Klein wrote:
>
> I ran into this same problem and was told that's how it works.  The way I 
> managed to get around it, somewhat, was to use sequential files on disk and 
> set the maxcap parameter for the device class at an appropriate value.  I 
> have one device class for the full backups and one for the incremental, just 
> so that I can specify different maxcap values.
>
> With every DB backup, ADSM wants a new, fresh backup tape to write that
> information.  How does one configure ADSM to keep appending to a previous
> tape.  This is eating media left and right and only taking up a fraction
> of the capacity.
>
> _______________________________________________________________
> Joe Morris  -  morris AT unc DOT edu  -  http://sunsite.unc.edu/morris
> Academic Technology and Networks (formerly OIT), Development
> University of North Carolina at Chapel Hill
>
>     ---------------------------------------------------------------
>
>                 Part 1.2       Type: application/ms-tnef
>                            Encoding: base64