Well I found out that this is not supported.  APAR IC35654 - "Virtual
Volumes with source and target servers residing on same server is not
supported."

-----Original Message-----
From: Rushforth, Tim [mailto:TRushforth AT WINNIPEG DOT CA]
Sent: May 29, 2003 1:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Create more then one backupset to one tape

Cool!  Thanks for this post Steven - I didn't realize that this could be
done with one server.  I want to use backupsets but never considered because
of the 1 volume per backupset limit.  For my purposes I wish backupsets
could use storage pools as a destination - this method gives me that.

I'm curious if anyone is using this method - ie one TSM server setup to send
Virtual Volumes to itself.  Is there anything to watch out for in this
configuration?

Now if only the client GUI could be used to restore individual files from a
backupset ....

Tim Rushforth
City of Winnipeg

-----Original Message-----
From: Steven Pemberton [mailto:stevep AT IBK.COM DOT AU]
Sent: May 15, 2003 5:45 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Create more then one backupset to one tape

On Friday 16 May 2003 00:46, Christian Svensson wrote:
> Hi Everyone!
> Do anyone know if is possible to create more then one backupset to one
> tape.
> Becuse each backupset is only 5 GB large and I only have AIT-3 tapes to
> send the backupset data to.
> And I going to use this backupset to send offsite.

Actually TSM uses a new *volume* per backupset. Normally this is equal to a
new tape, but by using server-to-server virtual volumes you can effectively
consolidate multiple backupsets onto a single physical volume.

This is best done between two TSM servers, where the on-site TSM server
sends
the backupset (virtual volume) to the off-site TSM server electronically via

the server-to-server communucations. Of course this requires that you have a

sufficiently fast WAN...

Alternatively you could define a "loopback" TSM server-to-server definition.

The TSM server then sends the backupset (virtual volume) to itself via the
server-to-server definition. The TSM server can then consolidate the
backupset (virtual volume) onto a single physical volume. Finally, if you
want to send this data off-site, you would need to either create a copypool
of the storage pool containing the backupset volumes, or simply checkout the

primary storage pool volumes and send them offsite.

One problem with this approach is that the backupsets are no longer
"external"
to TSM, and are actually stored in the normal storage pools.

Whether this is useful to you depends on why you need to create backupsets
in
the first place. If you are just creating backupsets for "monthly archival"
purposes, then it's probably acceptable. But, if you want the ability to
restore the backupsets via a locally attached tape drive on a client, then
you should not use this method.

Regards,
Steven P.

--
Steven Pemberton                                      Mobile: +61 4 1833
5136
Innovative Business Knowledge                   Office: +61 3 9820 5811
Senior Enterprise Management Consultant    Fax: +61 3 9820 9907