It sounds to me that you've run into some unusual situation which will be best 
addressed by TSM for Sysback support.

David

>>> RvanDenzel AT SLTN DOT NL 05/24/05 1:48 AM >>>
Goran,

I've first tested it a couple of months ago and it all went fine. Now I'm
setting it up for production and the tsmdev is missing from the SysBack
boot menu.

Richard.





goc <goran.k AT VIP DOT HR>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
23-05-2005 18:08
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU 
        cc:
        Subject:        Re: Using SysBack integration with TSM


hi,
i believe nothing is wrong you first choose the net interface
and then you'll automaticaly have tsm option,
at least that's what i got when testing restore from tsm
with sysback
keep up
peace

goran


----- Original Message -----
From: "Richard van Denzel" <RvanDenzel AT SLTN DOT NL>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, May 23, 2005 2:28 PM
Subject: Using SysBack integration with TSM


> Hi All,
>
> I've setup SysBack on three clients to use TSM as a backup device
(virtual
> tape device tsm0). When I make a sysback of these clients all works fine
> and the image is stored in TSM.
>
> For the ultimate test I want to restore a client (one of them can be
used
> for the test). When I boot the system (which is actually an LPAR) the
> system will actually boot into the SysBack boot menu. But when I access
> the Change Installation Device menu I can see all network interfaces,
but
> not the virtual TSM device.
>
> Anyone got a clue to what is going wrong where?
>
> Environment:
>
> TSM Server 5.3.1.2
> TSM Client 5.3.0.0
> SysBack 5.6.6.1
>
> Regards,
>
> Richard.
>