Sal,
Thanks for the post.
I had considered most of what you said. There is not enough disk on the
new server to migrate some of the clients so it looks like I will need
to do mass migration by recabling the small atl to the new server.
To answer some of your questions. RSC/6000 and AIX support is too
expensive. All apps running there are being moved to Linux or NT. As =
far
as I know there is no TSM server for Linux so it has to be NT. TSM
server and client will be the only apps on the NT box so reliability
should be better than a multi-app NT.
Thanks
sal Salak Juraj wrote:
>
> Interesting changes you plan, my son,
> the upgrade to an expensive tape technology with
> maybe the best reliability available at all
> and downgrade to an cheap OS with arguable lower
> availability (at least in the terms of up-time)
> than your current OS has.
> Anyway, I still am sure this combination
> will work good enough, if set-up correctly,
> I am just a bit surprised
> an curios about the reason for such a tandem.
>
> I see no or little problem with the migration you
> are planning.
> Your 2 servers do share a common media,
> the one of the type "shared disk". As long this
> ressource is large enough to hold either
> backup or archive data of your largest node,
> the usage of device class=3Dfile
> is a *very* comfortable way to export/import data.
>
> Maybe you could check how problematic would it be to
> attach your old library to the NT server for the time
> of migration? In this case you only had to export/import
> server (dump/load), connect old library to the NT,
> update drives definition so that they match
> new scsi connection,
> define additional library with 3590,
> define storage pools within 3590,
> and issue "move data" from
> one library to another one.
>
> I strongly suggest migration of one client at time.
> This processes are not restartable, so any error leads
> to a new start, which can cost a plenty of time lost.
>
> By the way, you can see the task as a part of disaster
> recovery practise as well - and - it will work, do not worry.
> At least if you will have read
> parts of administrators reference before the start.
> In this sense you may want to use the 8mm drive,
> temporarily attached to NT, to "restore stg" to
> your NT server, instead of using export/import.
> It would be slower, but it would test
> your disaster recovery ability.
>
> Good Luck!
> Salak Juraj
>
> KEBA AG
> Softwareentwicklung Bankautomation
> Gewerbepark Urfahr 14 - 16
> Postfach 111
> A-4041 Linz
> Vsterreich
>
> Tel. ++43/732/7090-7461
> Fax ++43/732/730910
> e-mail: sal AT keba.co DOT at
> www.keba.co.at
>
> -----Urspr|ngliche Nachricht-----
> Von: Steve Bennett [mailto:steve_bennett AT ADMIN.STATE.AK DOT US]
> Gesendet am: Dienstag, 18. April 2000 01:22
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: moving adsm server from aix to nt
>
> We currently run adsm v3.1.2.50 server on a 7015-r40 using aix 4.2.1.
> Recently it was decided that we should migrate that sever to a Win NT
> platform. I am looking for ideas as to best accomplish this.
>
> The current adsm server has a 15gb disk storage pool and a scsi =
library
> with four tape drives for the tapepool. 20 of 80 slots are in use and
> native capacity is 20gb per slot. ADSM db backup and offsite copypool =
is
> 8mm 5gb tape using the 7015 internal tape drive.
>
> The new Win NT server is to be configured with 20 to 50gb of disk
> storage pool and a scsi attachment to a new 3494 library with two =
3590
> tape drives.
>
> These two platforms do not share a common media to use for =
export/import
> however they are both attached to the same network and server to =
server
> may be possible.
>
> There are two choices for migration, one client at a time or all at
> once.
>
> Since there is no common media I am hoping that I could install the =
new
> Win NT adsm and then use the network connection to export from the =
old
> server to the new server. Then import from the new server to itself.
>
> Am I on the right track or is there a better way? Point me in the =
right
> direction please.
>
> --
>
> Steve Bennett, (907) 465-5783
> State of Alaska, Information Technology Group, Technical Services
> Section
--
Steve Bennett, (907) 465-5783
Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section
|
