It is necessary to save the OVM configuration information in XML format before performing server switchover in an OVM for SPARC environment. It can be saved from the GUI, the CLI or automatically.
For details on the save status of OVM configuration information in XML files, refer to "18.1 Status Display".
OVM configuration information XML files are stored in the following location on the control domain:
[Control domain]
/etc/opt/FJSVrcvat/config
ovm_config.xml
Note
Saving the OVM configuration information in the XML format can only be performed for the primary server. When using a spare server as an OVM for SPARC environment, the saving of XML files is possible, but incomplete configuration during the switchover process is overwritten.
Therefore, the resulting XML file cannot be used for recovery of the spare server.
Use the ldm list-constraints command to save the OVM configuration information of spare servers.
For details, refer to the "Oracle VM Server for SPARC Administration Guide".
Point
OVM configuration information can be saved as an XML file when both of the following conditions are met:
The server is powered on
The server status is "normal"
OVM configuration information can be saved using the GUI.
In the server tree of the ROR console, right-click a VM host in the target control domain, and select [Save OVM Configuration Information XML] from the displayed menu.
Save the OVM configuration information as an XML file in the control domain.
The OVM configuration information is not saved to the service processor.
OVM configuration information can be saved using the CLI.
Execute the rcxadm server backup command to save the OVM configuration information to the control domain as an XML file.
The OVM configuration information is not saved to the service processor.
For details on the command, refer to "3.4 rcxadm server" in the "Reference Guide (Command) VE".
OVM configuration information is saved at the following timings:
Automatic saving performs both saving of OVM configuration information to the service processor and saving of the XML file to the control domain.
When the following operations are performed from Resource Orchestrator
Power control operations (Power ON/ Power OFF/ Forced power OFF /Reboot/ Forced Reboot) of VM Guests
Migration of VM Guests between servers
When the following operations are performed for a guest domain on a control domain
Creation/deletion of guest domains
bind/unbind operations of resources
stopping/starting of guest domains
Changing of the number of virtual CPUs and memory size
Attaching/detaching of virtual disks
Migration of guest domains
Note
As a time lag of several minutes occurs during saving of OVM configuration information, do not perform server switchover immediately after performing the above operations.
The saving status of OVM configuration information can be confirmed from Resource Details.
For details, refer to "A.6.3 Physical OS, VM Host, and VM Guest Attributes".
