(Not speaking from experience here, yet...)
(Assuming AIX, though the original question didn't say.)
Any devices that use TSM-provided drivers will need to be redefined
after the upgrade. The note below from Shekhar suggests it would be
wise to delete the devices in SMIT before installing the new version
of TSM, then recreate the devicves after.
Devices using TSM-independent drivers should be fine left alone.
>From the Tivoli Storage Manager for AIX Quick Start manual (chapter
1, section on Before Performing a Migrate Install):
-----
TSM device definitions are not saved during a migrate install. To install
the new TSM drivers, you must have the output from the following
commands:
lsdev -Cc tape
lsdev -Cc library
This is not required for the IBM 3494, 3495, 3570, 3575, or 3590, which
use drivers supplied with the devices.
-----
Good luck!
=Dave
Shekhar Dhotre wrote:
>
> I have experienced this before , upgrade deletes all drive info , and =
> if you
> try to reconfigure it ,
> using smit tivoli ..you can`t
> you have to
> 1) delete drives from ODM use odmdelete .. (#rmdev -dl rmtx --does =
> not work
> )
> 2) run cfgmgr
> 3)smit tivoli-add -tape-add drives .will give you mt0--mt6 available (S=
> TK9710)
> 4)define drives to Tivoli by define drive
>
>
> Shekhar ..
>
>
> Dirk Billerbeck <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 03/15=
> /2001
> 10:37:08 AM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>
> To: [EMAIL PROTECTED]
> cc:
>
> Subject: Re: TSM 3.7 to 4.1 Upgrade
>
>
> Hello Alex,
>
> this is not always true. As far as I remember the AIX readme you have t=
> o
> redefine your devices because the update will delete them. So write the=
> m
> down first...
>
> Mit freundlichen Gr=FC=DFen,
> Met vriendelijke groeten,
> With best regards,
> Bien amicalement,
>
> CU/2,
> Dirk Billerbeck
>
>
> [EMAIL PROTECTED]@VM.MARIST.EDU on 15.03.2001 15:46:40
>
> Please respond to [EMAIL PROTECTED]
>
> Sent by: [EMAIL PROTECTED]
>
>
> To: mailbox.dekelnsm
> cc:
> Subject: TSM 3.7 to 4.1 Upgrade
>
>
> ----------------------------------------------------------------------=
> ----
>
>
>
> Hi Roy
>
> You should be able to install the code with almost no intervention. The=
>
> drives wont need reconfiguring, it would be as simple as upgrading from=
>
> 3.7.0 to 3.7.1 for instance
>
> Regards
>
>
> Alex
>
>
> Roy Lake
> <RLake@AXIAL- To: [EMAIL PROTECTED]
> TBG.COM> cc:
> Sent by: Subject: TSM 3.7 to 4.1
> Upgrade
>
> Hi Chaps,
>
> Its coming to that time of the year where we have to think about upgrad=
> ing
> our TSM server from 3.7.x to 4.1.x.
>
> Can you please confirm what this process involves?.
>
> I understand that we have to re-define the licences, but do we also hav=
> e to
> re-define the library, and drives, etc?.
>
> Anywhere where I can find out more as the docs are as usual very unhelp=
> ful.
>
> Kind Regards,
>
> Roy Lake
--
Hello World. David Bronder - Systems Admin
Segmentation Fault ITS-SPA, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm. [EMAIL PROTECTED]
