You'd better get up to (at least) 3.1.2.40 --- 3.1.2.30 was a bad release of
the server;  expiration process was deleting objects prematurely due to a
bug in the new multi-process feature.

Don

Technical Architect, P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037




> -----Original Message-----
> From: Herfried Abel [mailto:ha7 AT DAIMLERCHRYSLER DOT COM]
> Sent: Wednesday, January 05, 2000 2:23 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: dbbackups on the same volume
>
>
> It is.
> Works as designed - for safty reasons:-)
>
>
>
>
> Andrew Vasilevskiy <andrey AT BTC.MINSK DOT BY>@VM.MARIST.EDU> on 05.01.2000
> 10:09:26
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
>
> Subject:  dbbackups on the same volume
>
>
> Hi!
> We are using ADSM 3 1 2 30 for WinNT and SCSI optical
> libr.3995C68. The
> current ADSM database  size is smth like 100Mb. We are using 5.2Gb RW
> cartridges for database backup. Is it really so:
> 1. 5.2Gb cartridge is used as dbbackup volume (less then 2%)
> only (until
> next dbbackup version appear and previous expired)?
> 2. Next version (full dbbackup) can not be placed on this volume?
> 3. Every new dbbackup, full or incremental, can be done only on new
> (scratch) volume?
> The product is new for us and the documentation seemes to be not
> corresponding. That's why detailes are needed.
> Thanx for all.
> Andrey Vasilevskiy
> andrey AT btc.minsk DOT by
> ICQ: 38144461
> P.S.:If smth is wrong with my questions, then I wonder why could not I
> write ADSM dbbackups on the same volume day after day.
>