|
|||
Part I Upgrading With Solaris Live Upgrade 1. Where to Find Solaris Installation Planning Information 2. Solaris Live Upgrade (Overview) 3. Solaris Live Upgrade (Planning) 4. Using Solaris Live Upgrade to Create a Boot Environment (Tasks) 5. Upgrading With Solaris Live Upgrade (Tasks) 6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks) 7. Maintaining Solaris Live Upgrade Boot Environments (Tasks) Overview of Solaris Live Upgrade Maintenance Displaying the Status of All Boot Environments To Display the Status of All Boot Environments Canceling a Scheduled Create, Upgrade, or Copy Job To Cancel a Scheduled Create, Upgrade, or Copy Job Deleting an Inactive Boot Environment To Delete an Inactive Boot Environment Displaying the Name of the Active Boot Environment To Display the Name of the Active Boot Environment Changing the Name of a Boot Environment To Change the Name of an Inactive Boot Environment Adding or Changing a Description Associated With a Boot Environment Name To Add or Change a Description for a Boot Environment Name With Text To Add or Change a Description for a Boot Environment Name With a File To Determine a Boot Environment Name From a Text Description To Determine a Boot Environment Name From a Description in a File To Determine a Boot Environment Description From a Name Viewing the Configuration of a Boot Environment To View the Configuration of a Boot Environment 8. x86: Locating the GRUB Menu's menu.lst File (Tasks) 9. Upgrading the Solaris OS on a System With Non-Global Zones Installed 10. Solaris Live Upgrade (Examples) 11. Solaris Live Upgrade (Command Reference) |
Updating a Previously Configured Boot EnvironmentYou can update the contents of a previously configured boot environment with the Copy menu or the lumake command. File Systems from the active (source) boot environment are copied to the target boot environment. The data on the target is also destroyed. A boot environment must have the status “complete” before you can copy from it. See Displaying the Status of All Boot Environments to determine a boot environment's status. The copy job can be scheduled for a later time, and only one job can be scheduled at a time. To cancel a scheduled copy, see Canceling a Scheduled Create, Upgrade, or Copy Job. To Update a Previously Configured Boot EnvironmentThis procedure copies source files over outdated files on a boot environment that was previously created.
In this example, file systems from first_disk are copied to second_disk. When the job is completed, an email is sent to Joe at anywhere.com. # lumake -n second_disk -s first_disk -m [email protected] The files on first_disk are copied to second_disk and email is sent for notification. To cancel a scheduled copy, see Canceling a Scheduled Create, Upgrade, or Copy Job. |
||
|