Backing Out With backout_mu

To back out the Solaris 7 MU2 software on a diskless client or AutoClient from a server using backout_mu:

1. Halt the diskless client or AutoClient.

2. If you are running the Solaris 7 operating environment on your system and have installed special patches on a diskless client or a Solstice AutoClient, as described in "Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server," then you must back out patches individually, as described in "Backing Out Special Patches on a Diskless Client or Solstice AutoClient from a Server."

3. On the server, run the backout_mu script located in the local product directory, with the client's root directory as the argument.

   • From a local copy of the MU2 image that corresponds to the client platform, type:

     # cd local_directory # ./backout_mu -R /export/root/client_name

     where client_name is the hostname of the diskless client or AutoClient.

   • From the MU2 CD, mount the CD and type:

     # cd /cdrom/s7_maintenance_update_2_platform # ./backout_mu -R /export/root/client_name

     where platform is sparc or x86 and client_name is the hostname of the diskless client or AutoClient.

4. Repeat this process for each diskless client or AutoClient being served.

5. If you are running the Solaris 7 operating environment on your system and have installed special patches on a server's service area, as described in "Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server," then you must back out patches individually, as described in "Backing Out Special Patches on a Diskless Client or Solstice AutoClient from a Server."

6. Back out the Solaris 7 MU2 software on the server's service area. From a local copy of the MU2 image that corresponds to the server platform, type:

   ---

   Note -

   If you are backing out the MU2 from a server's service area on a SPARC server that has x86 clients, refer to bug ID 4228999 in "Backout Bugs".

   ---

   # cd local_directory ./backout_mu -S Solaris_2.7

   ---

   Note -

   If a service area is shared by the server, you also need to remove the same Maintenance Update patch set from the server's root area. Failure to do so will result in an improperly patched and unstable server.

   ---

7. Boot the diskless client or AutoClient.