Bill, Mark

I was very pleased using virtual volumes to keep my incremental DB dumps
together with the full backup.  You're right that it was difficult to set
up and by the time I moved one server to a new box, I forgot all the steps
that I took, so I'm still working on it.  But the results are well worth it.


At 10:03 AM 5/9/2002 -0400, you wrote:

Mark, I haven't done this but I think the virtual volumes feature
will provide what you want.  It involves making a 2nd tsm server
instance which can be on the same processor.

TSM will not append to any sequential volume that isn't in a storage
pool.  This covers db backups, full or incremental, exports, and backupsets.

When you set up the second server and connect both servers to each other with
the virtual volume commands (I don't know how to do it and I don't
think it is easy), you can direct your backupsets to virtual volumes.
These volumes are actually single archive files in the 2nd server.  Then
migrate these files to a sequential pool in the 2nd server which will of
course
fill the tapes.

Has anyone done this?  I hope I am not way off base because I am
thinking of doing this when I rehost (s390 to sun/aix/2k) later this year.

Bill Colwell

At 09:53 AM 5/8/2002 -0500, you wrote:
>Hello All,
>
>Is it possible to put multiple backupsets on one tape, I believe that the
>tape I am using has enough room for multiple sets. When the first backupset
>completed the activity log reported "ANR1361I Output volume 367ACRL1 closed"
>do I have to do something to reopen the volume. The volume errors in the
>activity log reported when I tried to force it to go to this specific tape
>are "ANR1409W Volume 367ACRL1 already in use - skipped." and "ANR3516E
>GENERATE BACKUPSET: Out of space on sequential media, scratch media could
>not be mounted."
>
>Server is TSM 4.1.30 on NT.
>
>Any help is appreciated.
>Mark B.

----------
Bill Colwell
C. S. Draper Lab
Cambridge Ma.