On  Mon, 5 May 1997 12:41:14 EST Bob Mueller Wrote:

>>I would also like to see if this could be done "Neatly". I have a
>>similar problem, and have been using the following work-around:
>>
>>My back-up normally takes two hours. When I stream the back-up job,
>>I also stream a job (scheduled to start in 2-1/2 hours) that does an
>>ABORTJOB on the back-up. It's a little dangerous, but our SOP is to
>>abort the back-up anyway (If it's hung-up), so users can get on the
>>system ASAP.
>>
>>Bob Mueller, MIS Manager
>>[log in to unmask]

On Tue, 5 May 1997 12:14 pm EST Jon Diercks wrote:

>Is there any way to force :STORE (including TurboStore/iX 7x24) to
>*not* ask for a second reel if the first one fills up?  We have
>slightly more disc space than what will fit on a tape, and we arrange
>the sequence of files in such a way that the least important ones
>will be last.  For a lights-out weekend backup, if the tape fills up
>we want the store to quit and complete. Haven't been able to find a
>way to accomplish this.  I even thought of setting up a "sequential"
>storeset with the first device being the DDS and the second device
>being $NULL, but :STORE doesn't like that, it insists that devices
>must be all DDS or no DDS.  Any other ideas?
>
>Jon Diercks
>[log in to unmask]

I have worked around this problem by creating two backups.  A
Fullback that stores all production files and databases excluding
test accounts, software accounts etc (@[log in to unmask]@ - @[log in to unmask], @[log in to unmask]).  A
Fullother backup job that only includes what was excluded.  The
Fullback job runs at night unattended and the Fullother is run by the
first person in the morning that removes the production cartridge and
puts in the non production (so to speak) cartdrige.  This has many
other side benefits (like programmers still working during the
Fullback, restoring files, etc).  Only draw backs are that it does
take 2 tapes per day and someone could accidentally make the store
sets different.

Chuck Duncan
[log in to unmask]