What you want to do is called cloning, and is a common thing in AIX,
BUT...
SP's are a little tricky because they have no tape drive attached to the
node itself with which to create a mksysb tape. I think the most direct
way to do what you want is to mimic what the SP itself does "under the
cove
We built a non-priveleged admin ID called BATCH, with
password JOB, in the ADSM server, making sure that
this admin ID was premised in the server such that
it could query only. Using this ID in your script
now mitigates some of the risk associated with
advertising the name+password combo.
HTH,
The answer to your question is no, the image itself
will not be bootable. Think about it. You are
storing a system image in a filesystem that cannot
be mounted until the OS is restored and running. It's
a classic catch-22.
NIM is the solution you are looking for. SP systems use
NIM under the co
the dark at this point, but maybe that
might help.
Cheers,
Dan
Gyula Bereczky wrote:
>
> On Thu, Oct 12, 2000 at 08:12:40PM -0700, Dan Jennings wrote:
> > I support a bunch of 3575 tape lib's on AIX servers
> > and all of them always return an errno 46 when closing
> >
I support a bunch of 3575 tape lib's on AIX servers
and all of them always return an errno 46 when closing
a drive device with tapeutil. Usually this has no
relationship to readiness from a *SM point of view,
though.
Since it sounds like you are a veteran AIX'er, I guess
I don't have to tell you
In UNIX (AIX Korn shell used as an example...):
Here's one way to get it done. You can use a shell script
to evaluate the current date, then write out a file that
contains the "generate" command with the date string embedded
in it. This would probably have to get run from cron,
and an example m
I did this too... fortunately it was before I had any data
in the library. I had to delete and redefine the 3575
library device (/dev/smc0 in AIX) in order to make the
problem go away. I don't think I had to delete the library
or drives to ADSM, just remove the device and re-run
cfgmgr.
HTH,
D
