A copy of the current configuration is automatically saved on the control domain whenever the domain configuration is changed. This autosave operation does not explicitly save the configuration to the SP.
The autosave operation occurs immediately, even in the following situations:
When the new configuration is not explicitly saved on the SP
When the configuration change is not made until after the affected domain reboots
This autosave operation enables you to recover a configuration when the configurations that are saved on the SP are lost. This operation also enables you to recover a configuration when the current configuration was not explicitly saved to the SP after a system power cycle. In these circumstances, the Logical Domains Manager can restore that configuration on restart if it is newer than the configuration marked for the next boot.
You can automatically or manually restore autosave files to new or existing configurations. By default, when an autosave configuration is newer than the corresponding running configuration, a message is written to the Logical Domains log. Thus, you must use the ldm add-spconfig -r command to manually update an existing configuration or create a new one based on the autosave data. Note that you must perform a power cycle after using this command to complete the manual recovery.
For information about how to use the ldm *-spconfig commands to manage configurations and to manually recover autosave files, see the ldm(1M) man page.
For information about how to select a configuration to boot, see Using Oracle VM Server for SPARC With the Service Processor. You can also use the ldm set-spconfig command, which is described on the ldm(1M) man page.