Brian,

        nope, you shouldn't do that! Also because one of bugs of the 3.1.20 is
on import/export of nodes and data ... it works just fine but when you do
a restore 90% of the files cannot be restored!

        When I moved my server I restored the database on the new server having
installed previously the same version of ADSM, and then I redefined the
drives of the library it went really smoothly ... just remember to
migrates all the data on disk/file-class stgpools, which stay on the old
server!

        You asked for an advice ... the complete procedure is longer but isn't a
too big feat!

Ciao Mauro

> Hello everyone....
>
> I am preparing to move to a new ADSM server, and am wondering if anyone
> has some advice to make the transition easier.
>
> Our current configuration has a 3494 w/ 2x 3590B1A drives connected to
an
> RS/6000 J40 running AIX 4.2.1, ADSM 3.1.2.20.  The new system will have
> the same lib. and drives, but an RS/6000 H70 running AIX 4.3.2,
> ADSM 3.1.2.40.
>
> I've been reading up about import and export... do I really have to
copy
> (export) *all* of my data (nodes, admin, policies and backup/archive
data)
> onto empty tapes, then copy(import) it all back again?? With almost
2.5TB
> of data stored, this is quite a daunting task.  Seems to me there must
be
> an easier way, but I'm not sure what it is, and the docs I have don't
seem
> to be of much help.
>
> Any advice will be greatly appreciated.
>
> TIA.
>
> -
> Best regards,
> Brian
>
>
+-----------------------------------------------------------------------+
> | Brian T. Huntley                         Systems and Network Engineer
|
> | Campus Information Services, Clarkson University
|
> | Ph/FAX: 315.268-2292/6570
|
> | bth AT clarkson DOT edu                                 www.clarkson.edu/cis
|
>
+-----------------------------------------------------------------------+
>  UNIX *is* user friendly. It's just selective about who its friends
are.
>         PGP Public Key available. finger bth AT clarkson DOT edu