Hi HarryNair,
thanks for the procedure.
After I plugged the altinst_rootvg-disks into the target system, I got a
problem configuring them. :(
Here is what I've done (after I detached the disks from the source system):
1. plugged the disks into the target (running) system
2. # cfgmgr (ok ->...
Hi HarryNair...
thanks for the info.
I'll be able to test it first on monday... so I have to wait until then.
Meanwhile... do you know, whether there is a way to easily unplug/deactivate the "altdisks"?
(a way, which doesn'trequire to unmount all the mount points of altdisk_rootvg one by one/...
Hello everyone!
I would like to clone an AIX 5.3 system (p510) to a target
systemB, which is physc. identical to the source systemA (of
course except e.g. serial number) using alt_disk_copy-disks.
After alt_disk_copy -d "hdisk3 hdisk4"
the source systemA looks like this:
hdisk0 rootvg...
p5wizard..
Don't I have to varyon the disk first on systemB after the importvg command?
systemB
- cfgmgr => hdiskYY
- importvg -y transvg hdiskYY
- varyon hdiskYY <================ ???
BR, cipaera
Hello people,
I hope somebody can help me with this.
The system is p5 9110-510 with AIX 5.3.
I want to copy one big directory (about 10-30GB) to an unpluggable harddisk on system A,
which later will be attached to system B. And this system B should see the directory.
What I think I should do...
p5wizard: thanks for your tips. It is what I'm looking for.
Now I'm still trying to understand how to adapt the PATH
variable and is it the global path or tsm specific path.
If it is "tsm binary path" could you tell me, which/how to adapt?
Best regards,
cipaera
Hi p5wizard,
thanks for your suggestion.
I've almost used the trick, but there were more error outputs from "find", which I can't filter with
chexcludelist -a /var/__*
Some of the other error outputs are:
find: 0652-019 The status on ./var/spool/mqueue/xfl7AM0qC573578 is not valid.
find...
Dear all,
I hope someone can help me to resolve this problem.
We use TSM via script to backup some filesystems on AIX 5.3 systems.
Unfortunately as soon as an error was produced by "find" (0652-019) the backup process stopped.
My questions are:
How can the process finish the backup...
Well.. FYI... it was my fault.
I did edit only the S##script but forgot to edit the K##script.
/etc/rc.d/rc#.d/K90_all_of_scripts should also look like
/etc/rc.d/rc#.d/S90_all_of_scripts:
#!/bin/ksh
/etc/rc.d/init.d/script1 $1
sleep 300
/etc/rc.d/init.d/script2 $1
sleep 300...
Thanks MoreFeo,
But there is a situation, which I can't live with.
From the manual of 'shutdown':
If the script runs but fails with a non-zero return code, the shutdown stops.
I hope there is another way...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.