ML backout plan

[Mag0007]

Just curious:

I have never done this before, but what is the procedure to backout of a MaintenceLevel?

Example: If I have 5.2 ML 2 running, and I updated to ML 5. How would I go back to ML2?

I did a Save and Replace filesets.

TIA

 

[mrn]

Take a mksysb and restore if need be.

You can do a dry run by selecting Preview Only = yes

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

http://www.airport-parking-site.co.uk/

 

[columb]

A ML upgrade is really just installing a number of filesets. When you run 'smitty update_all' set the commit flag to no so that your screen looks like

             Update Installed Software to Latest Level (Update All)
 
Type or select values in entry fields. 
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* INPUT device / directory for software               . 
* SOFTWARE to update                                  _update_all
  PREVIEW only? (update operation will NOT occur)     no                     +
  COMMIT software updates?                            no                     +
  SAVE replaced files?                                no                     +
  AUTOMATICALLY install requisite software?           yes                    +
  EXTEND file systems if space needed?                yes                    + 
  VERIFY install and check file sizes?                no                     + 
  DETAILED output?                                    no                     + 
  Process multiple volumes?                           yes                    + 
  ACCEPT new license agreements?                      no                     + 
  Preview new LICENSE agreements?                     no                     +

Then you can roll back the changes using the smitty option off

                       Software Maintenance and Utilities 
 
Move cursor to desired item and press Enter.
 
  Commit Applied Software Updates (Remove Saved Files)
  Reject Applied Software Updates (Use Previous Version)
  Remove Installed Software 
   
  Copy Software to Hard Disk for Future Installation
   
  Check Software File Sizes After Installation
  Verify Software Installation and Requisites
   
  Clean Up After Failed or Interrupted Installation

OK?

Columb Healy

 

[Mag0007]

Wow..cool.

Healy:
How did you get the second screen? What smit panel is that?

 

[hfaix]

smit maintain

 

[RodKnowlton]

If you have the disks available in the rootvg, alt_disk_install is great for this, also.

Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+