When the various virtual machine products have something as mature as
channel and device drivers that run in usermode, then the time will
be right for running a backup server on them.

As long as virtual machines are a panacea for can't-run-more-than-one-
app-on-a-Windows-instance-sprawl and a way to sell new hardware, they
won't be a good choice for a TSM environment.

Where is that "Its all about I/O." tagline?

[RC]

On Feb 2, 2010, at 9:36 PM, Roger Deschner wrote:

Remember, TSM (a.k.a. WDSF, ADSM) was originally _invented_ as a
virtualized application, under the system now known as z/VM, and was
supporetd there until V3.7. It should still have the fundamental
design
to deal with running in a virtual machine. It does need resources such
as tapes to be dedicated to it, and it may take some work to get those
resources connected right. But a virtual machine should actually be
considered TSM's historic native environment.

Roger Deschner      University of Illinois at Chicago
rogerd AT uic DOT edu
"We all live in a virtual machine, a virtual machine, a virtual
machine"
--from the SHARE songbook,
  sung to the tune of the Beatles' "Yellow Submarine"


On Wed, 3 Feb 2010, Xav Paice wrote:

Quoted from the IBM link, the table refers to virtualisation where
"the resources are then purely virtual (not dedicated) and/or are
not discrete".  My confusion, and I'd love someone to clear this
up, is where we have RHEL running KVM.  Red Hat clearly stated in
their customer seminar on RHEV-M that if an app is supported on
RHEL 5.4, it's supported under KVM on RHEL 5.4.  If I add a PCI
card (e.g. multi port HBA with tape attached) to a virtual
machine, that is discrete and dedicated, that could be supported
but it's a pretty grey area.  Anyone care to confirm or deny?

As Wanda put very accurately (off list), "when they say something
is supported, it means if you call and report a problem, they will
work on the problem" - that's the application vendor's support
rather than the OS vendor's view of what's certified. Any software
vendor is going to want to limit the support to things they can
test in the lab - Tivoli might test TSM on RHEL, but maybe not
RHEL under RHEV/KVM.

That link also mentions non i386 virtualisation - such as LPARs
and DSD.

My apologies to the OP if this hijacks the conversation - I think
it's on topic as you didn't mention which hypervisor you will select.


----- "Wanda Prather" <wprather AT JASI DOT COM> wrote:

From: "Wanda Prather" <wprather AT JASI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Wednesday, 3 February, 2010 6:13:05 AM (GMT+1200) Auto-
Detected
Subject: Re: [ADSM-L] Virtual TSM

Yes, you can restore a TSM data base to a new TSM server.

However, think twice before virtualizing - Tivoli doesn't support
the
TSM
server on a VM if you have tape drivers (i.e., physical tape or
VTL).
See
below.

http://www-01.ibm.com/support/docview.wss?
rs=663&context=SSGSG7&q1=server+support
+vmware&uid=swg21239546&loc=en_US&cs=utf-8&lang=en


On Tue, Feb 2, 2010 at 12:06 PM, Micka <tsm-forum AT backupcentral DOT com>
wrote:

Hi,

I'm looking at virtualising our TSM server.