|
|
Sponsored Content
Operating Systems
AIX
Upgrade AIX 5.3 to AIX6.1
Post 302858745 by rbatte1 on Tuesday 1st of October 2013 09:20:35 AM
10-01-2013
Moderator
This might seem like a great way to do it, but it depends what you are starting with. Do you have a NIM server for a starter?
I think that the unmirrorvg will not split you off a copy that you can boot from later, it simply removes the mirror and leave the disk free to be re-used.
I do not beleive that you can just boot from this disk. It will be empty.
What current resources do you have? If you have 4 local disks that you can boot from (and all your data elsewhere) it might be better to make an alternate boot pair. Assuming the local disks are hdisk0-3 and hdisk0 & 1 are on one controller and hdisk2 & 3 are on another, you would be best to first spread your risk. Make the rootvg from hdisk0 & 2 for instance so you are protected from a controller failure. If you need to move disk contents from one to another, use migratepv, but be aware that this can take a long time. Additionally, you will need to recreate the boot image and correct the boot-list as stated by ibmtech
If you can do this process and it leave you two disks free, then you can use the smit panels:-This should build an alternate boot pair that you can revert to should your upgrade/migration have undesirable effects.
After this, you should test that you can boot from the alternate pair. You will need to get into SMS during the power-on process for this.
Another simpler approach would be to create and test a mksysb backup and restore to a separate machine. You would then be able to recover to your existing server if you need to. Of course you would need hardware to test this on, although good DR service suppliers will allow you testing time for this anyway. I'm presuming that you have DR provision already? Now is a good time to test it!
I'm hoping that I haven't scared you, and I'm open to being corrected if I'm wrong. I just don't want anyone to assume that an unmirrorvg will give you a split off boot disk.
I hope that this gives you something to consider and that it helps in your planning.
Robin
Liverpool/Blackburn
UK
I think that the unmirrorvg will not split you off a copy that you can boot from later, it simply removes the mirror and leave the disk free to be re-used. I do not beleive that you can just boot from this disk. It will be empty. What current resources do you have? If you have 4 local disks that you can boot from (and all your data elsewhere) it might be better to make an alternate boot pair. Assuming the local disks are hdisk0-3 and hdisk0 & 1 are on one controller and hdisk2 & 3 are on another, you would be best to first spread your risk. Make the rootvg from hdisk0 & 2 for instance so you are protected from a controller failure. If you need to move disk contents from one to another, use migratepv, but be aware that this can take a long time. Additionally, you will need to recreate the boot image and correct the boot-list as stated by ibmtech
If you can do this process and it leave you two disks free, then you can use the smit panels:-
- smit
- Software Installation and Maintenance
- Alternate Disk Installation
- Software Installation and Maintenance
After this, you should test that you can boot from the alternate pair. You will need to get into SMS during the power-on process for this.
Another simpler approach would be to create and test a mksysb backup and restore to a separate machine. You would then be able to recover to your existing server if you need to. Of course you would need hardware to test this on, although good DR service suppliers will allow you testing time for this anyway. I'm presuming that you have DR provision already? Now is a good time to test it!
I'm hoping that I haven't scared you, and I'm open to being corrected if I'm wrong. I just don't want anyone to assume that an unmirrorvg will give you a split off boot disk.
I hope that this gives you something to consider and that it helps in your planning.
Robin
Liverpool/Blackburn
UK
|
|
10 More Discussions You Might Find Interesting
1. AIX
Hi guys
I have joined a new department and one of my tasks is to investigate the feasibility of upgrading our current AIX v 4.3 to V5.3.
I do not know anything about AIX and any actual work will be done by an outside consultant until such time as I have built up my own knowledge.
The system we... (3 Replies)
Discussion started by: JDM
3 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09
this is the first time iam going to do it.
are there any command i have to keep in mind??
thanks! (1 Reply)
Discussion started by: karthikosu
1 Replies
3. UNIX for Dummies Questions & Answers
Does anyone know any gotcha's on upgrading AIX from 5.1 to 5.3? Any interim steps on needs to do or ??? (3 Replies)
Discussion started by: capeme
3 Replies
4. AIX
I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
Discussion started by: bashtonmcse
1 Replies
5. AIX
We are going from UDB DPF 8.2 to 9.5 and changing HW from P4+ to P6 and moving from 5.2 to 5.3. Anyone out there gone through this upgrade? Any words of wisdom, warnings, or other gotchas you could pass on. TIA.
ART (0 Replies)
Discussion started by: ArtF
0 Replies
6. AIX
Hello Folks,
i am facing some weired issues.
case is like this :-
initially i was on AIX 5.3
i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO)
Then i have taken lslpp -l| grep -i <apps name>
in that i confirmed whether the filesets are... (1 Reply)
Discussion started by: harsh_mulay
1 Replies
7. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
8. AIX
i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r
shows out put, again 5.3.2.1-- where should i chek???
2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
Discussion started by: nayyer
2 Replies
9. Emergency UNIX and Linux Support
Hello Team,
Am trying to upgrade the AIX 6.1 TL 7 to TL 8. My rootvg is mirrored so i have unmirrored and taken out the secondary disk and trying to install the update via smitty alt_clone.
The filesets has been installed and finally when making the updated disk as bootable bosboot... (6 Replies)
Discussion started by: gowthamakanthan
6 Replies
10. AIX
Hi all,
I'm getting errors while booting AIX 7.1 after upgrade
I have used FLRT tool for the process with the following input values shown in the attached photo. titled FLRT
After reboot for the upgrade process system hangs and no response as shown in screenshot named AIX7.1-NormalBoot
I... (13 Replies)
Discussion started by: h@foorsa.biz
13 Replies
LEARN ABOUT CENTOS
systemd-readahead-done.service
SYSTEMD-READAHEAD-REPLAY.SERVICE(8) systemd-readahead-replay.service SYSTEMD-READAHEAD-REPLAY.SERVICE(8) NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd- readahead - Disk read ahead logic SYNOPSIS
systemd-readahead-replay.service systemd-readahead-collect.service systemd-readahead-done.service systemd-readahead-done.timer /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE] DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process. systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead. Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot be stored, it might be a good idea to disable systemd-readahead-collect.service. On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it, systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times. OPTIONS
systemd-readahead understands the following options: -h, --help Prints a short help text and exits. --max-files= Maximum number of files to read ahead. Only valid for thes collect command. --file-size-max= Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands. --timeout= Maximum time in microseconds to spend collecting data. Only valid for the collect command. COMMANDS
The following commands are understood by systemd-readahead: collect [DIRECTORY] Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the read-ahead data. replay [DIRECTORY] Perform read-ahead on the specified directory tree. analyze [FILE] Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read ahead by the replay command. SEE ALSO
systemd(1) systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)