If you use NIM and create node images using mksysb on the nim servers then
you can use adsm to backup up the images
and nim to rebuild a server when needed.




Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>@VM.MARIST.EDU> on
01/29/2000 12:24:07 PM

From: Steven P Roder <tkssteve AT REXX.ACSU.BUFFALO DOT EDU>@VM.MARIST.EDU> on
      01/29/2000 12:24 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Sysback & ADSM, Howto?


> We set this up at a customer.  We created a storage pool called sysback
and
> defined tape volumes to this pool.  Then we used these volumes for
sysback.
> Actually, we did it the other way around: we created the sysback tape and
> then defined it to the pool.  Once defined to the pool, *SM won't try to
> grab the tape for something else.  You can even check the tape out and
> update its access to off-site if you would like.

We are also thinking about sysback and adsm.  Why not make the adsm server
the sysback server, and backup to a disk volume that ADSM then backs up?
I recovery would mean restoring the sysback image to disk first.  Or is
this not possible?  I do not know much about how sysback works at this
point...

Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
(tkssteve AT buffalo DOT edu | (716)645-3564 |
http://ubvm.cc.buffalo.edu/~tkssteve)