Thursday, 22 May 2014

Oracle VM SPARC – LDOM configuration Backup and Restore


Saving Domain Configurations for Future Rebuilding
 The basic process is to save the resource constraints information for each domain into an XML file, which can then be re-issued to the LogicalDomainsManager, for example, after a hardware failure to rebuild a desired configuration.
 Recently we had an activity where we have to shutdown the /SYS or the control domain. We have forgot to save the configuration to SP so when /SYS was brought up we lost the configuration. It was huge configuration so we had tried to recover it in different ways. We had a back up copy but that didn't work and gave file corruption errors. It is very important to remember that every time explorer runs it saves a copy of the domain configuration. We recovered it from explorer.

1. Login to control Domain and list the current configuration file.
-bash-3.2# ldm list-spconfig
factory-default
config_new [current]
-bash-3.2#

2.To take the complete LDOM configuration backup,use below command.
# ldm list-constraints -x >config.xml

3.You can also  take the configuration backup for specific LDOM,
# ldm list-constraints -x ldom_name > ldom_name.xml

How to restore the system to factory default ?

1. Login to the control domain console and remove the spconfig profile.
bash-3.2# ldm ls-spconfig
factory-default
config_new [current]
bash-3.2# ldm  remove-spconfig config_new
bash-3.2# ldm ls-spconfig
factory-default [next poweron]
bash-3.2#

2.Power cycle the server to take the changes effect.
bash-3.2# init 5
bash-3.2# svc.startd: The system is coming down.  Please wait.
svc.startd: 101 system services are now being stopped.
Feb 18 10:00:49 sol10-11 syslogd: going down on signal 15
svc.startd: The system is down.
syncing file systems... done

Serial console stopped.

-> show /SYS
  Properties:
        type = Host System
        ipmi_name = /SYS
        keyswitch_state = Normal
        product_name = T5140
        product_part_number = 4613802-42
        product_serial_number = FML1015013
        product_manufacturer = SUN MICROSYSTEMS
        fault_state = Faulted
        power_state = Off
-> start /SYS
Are you sure you want to start /SYS (y/n)? y
Starting /SYS

->
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.                                                                                                  

Done
0:0:0>Master CPU Tests Basic....Done
0:0:0>Init MMU.....
0:0:0>L2 Tests....Done
0:0:0>Extended CPU Tests....Done
0:0:0>Scrub Memory....Done
0:0:0>Functional CPU Tests....Done
sol10-11 console login:
3. Login to the system and see whether factory default settings has been restored or not .
sol10-11 console login: root
Password:
Feb 18 10:10:58 sol10-11 login: ROOT LOGIN /dev/console
Last login: Tue Feb 18 01:19:27 on console
Oracle Corporation      SunOS 5.10      Generic Patch   January 2005
You have new mail.
-bash-3.2#

-bash-3.2# ldm list-spconfig
factory-default [current]
-bash-3.2#
 Restoring the sp-config :

1.Once the system has restored to the factory default,then you can restore the system backup using the XML files which we have created. Login to the control domain and restore it.
 # ldm init-system -i config.xml
 # ldm add-spconfig unixarencfg1
 # ldm list-spconfig
factory-default
unixarenacfg1 (current)
2.To restore the specific ldom/primary domain configuration
# ldm init-system -i ldom_name.xml
# ldm add-spconfig unixarencfg2
# ldm list-spconfig
factory-default
unixarenacfg1
unixarenacfg2 (current)
3.To restore only the virtual service,
# ldm init-system -s -i filename.xml
-bash-3.2# ldm list-spconfig
factory-default
unixarenacfg1
unixarenacfg2[active on Reboot]
-bash-3.2# ldm add-spconfig unixarencfg3
-bash-3.2# ldm list-spconfig
factory-default
unixarenacfg1
unixarenacfg2
unixarenacfg2 (current)


+++++++++++++++++

1.ldm ls-config
2.ldm ls-config -r
3.find /var/opt/SUNWldm/ -type f -name \*timestamp\* -ls
4.cd /var/opt/SUNWldm/bootsets ; ls -ltr (Check for latest time stamp) 


+++++++++++++++++++++++


No comments:

Post a Comment