Re: Require a means of performing AIX makesysb remotely.

        We use our NIM server in much the same way Steve describes. We have 
each AIX host dump a mksysb image to the NIM server once a month. It actually 
NFS mounts a filesystem from the NIM server and does a mksysb to it. Since we 
have about 100 AIX servers and not enough disk space, we have processes in 
place to archive/delete the mksysb to TSM and retain it for a couple months.
        If we need to restore that OS image, we restore it to the NIM server, 
define it as a resource and have the client restore it. We've only had to do it 
a couple of times, but it worked pretty slick.

        As for our Solaris clients, we don't have quite as good a system. On 
Solaris we have the jumpstart services, but to install a host it takes hours, 
as it adds the data package by package to the host. We recently started using
flash archives. It is similar to a mksysb in that it's an installable snapshot 
of the OS. When used in conjunction with the jumpstart server (and it's bootp 
services), it can be used to reinstall the OS on a Solaris host in about 10 
minutes, much faster than a jumpstart.
        Currently we don't have a flash archive of all 200+ Solaris hosts, but 
we do have a collection of standard installation images (web server, DB server, 
LDAP server, compute server, etc), that we use to "flash" new hosts and then 
customize as needed.

        From the 1000 foot level, our DR plan is to get the jumpstart (and NIM) 
servers restored, start flashing hosts and then restore the few specific system 
config files from the most recent TSM backups. That gets us the OS, client data 
then comes along shortly thereafter.

Thanks,
Ben


-----Original Message-----
From: Steve Harris [mailto:Steve_Harris AT HEALTH.QLD.GOV DOT AU]
Sent: Thursday, April 10, 2003 5:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Require a means of performing AIX makesysb remotely.


Jim,

See the TSM 5.2 announcement for the integration of SYSBACK for AIX with TSM.  
(look in the archives at www.adsm.org earlier this week for a link)
However, you don't really need it for AIX boxes.

AIX comes standard with NIM, a rather nifty product which allows you to install 
operating systems, apply maintenance etc etc across the network.
You can take an AIX mksysb to disk on the NIM server (which is just an 
additional function on one of your AIX boxes) and then use NIM to restore it.  
Just use TSM to keep the mksysb images backed up on tape until you need them.

There is also jumpstart for Solaris which performs a similar function in that 
environment but my Solaris knowledge is limited so I'll leave others to comment.

Regards

Steve.

AIX and TSM Administrator
Queensland Health, Brisbane Australia

>>> jimtsm AT HOTMAIL DOT COM 11/04/2003 8:41:41 >>>
My client is presently a NetBackup shop.  They are not to happy with the
solution.  One of their main problems is that their AIX and some SUN boxes
do not have external tape drives or operations staff on site.

I think I can convince them on bringing in TSM if I can come up with, even a
partial, solution to this problem.  What is the closest I can get to
providing these system backups and using TSM.

Most AIX is at 4.3.3 some at 5.1.  Present library is a IBM LTO
358(something) with 10 drives on a SAN with 2 ESS(Sharks).

Thanks

JT





_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963



**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.

Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited.  It may be subject to a statutory duty of
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail.  You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************