T4-2 issues meant replacing motherboard.
I thought the ldom config was automatically saved? Got the oracle document here.
At the moment, unable to get ldoms back - here is the output from a few commands:-
ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-c-- UART 128 261632M 0.0% 3h
ldom1 inactive ------ 96 192G
ldm list-spconfig
factory-default [current]
ldm list-spconfig -r
No autosave configurations
svccfg -s ldmd listprop ldmd/autorecovery_policy
ldmd/autorecovery_policy integer 1
---------- Post updated at 06:03 AM ---------- Previous update was at 05:53 AM ----------
Ah Looks like we've got v2.2 of ldom. I understand theres a bug. Does this mean none of the autosave has worked?
Where is the config saved? Maybe on a chip that must be transferred to the new board? Just an idea - I actually know nothing.
I'm no expert on this one either but it seems that the ldom configuration can be saved (backed up) from the service processor to a XML file.
If you have this XML file you can restore it after a rebuild.
Oracle VM SPARC - LDOM configuration Backup and Restore - UnixArena
1 Like
It is best practice to save configuration to XML as per document hicks mentioned.
This is the latest oracle document regarding :
Saving Domain Configurations -
Oracle(R) VM Server for SPARC 3.4 Administration Guide
Put this in in crontab, and save your configuration on external system, best on some NFS.
SP is on a chip, which you pull out for your old motherboard and plugin in new
Remove the Service Processor - SPARC T4-1 Server HTML Document Collection.
If you have other sparc servers on which virtual machines lived and those were on FC / ISCSI you can use other server LDOM configuration to import to serviced machine.
Do not import primary configuration from another server, just LDOM if on external storage.
Is there anything in /var/opt/SUNWldm on the machine ?
Also, a good practice which i endorse (if you use putty) is to save all your putty sessions to a file automatically (with timestamps for log files)
To reconstruct what you did or find data inside those log files can be gold sometimes, since we all make mistakes.
Hope that helps
Regards
Peasant.
2 Likes
Been awhile since I've done it but this is what I did
list configs
ldm list-spconfig
factory-default
initial
initial1
primary-config
srv1.20140622-00
srv1.20140627-00
srv1.13feb2015 [current]
Then save it
ldm add-spconfig srv1.20140627-00
And then remember to save your bindings
ldm list-constraints -x > /root/list-constraints.`date +%s`