On 01/20/10 10:51, Andras Spitzer wrote: > Hi, > > If I understand correctly, the autosave functionality added in LDOM 1.2, is > not intended to replace the manual command (ldm add-spconfig) to save the > configuration on the SC, is this correct?
Yes, that's correct. > If I understand correctly the standard operation still is to manually save > the configuration to the SC (using ldm add-spconfig) after any change you > want to keep, and the autosave is a safety-net in case you forgot to do it > manually. Yes, that's correct. > The reason why it's confusing if I set "autorecovery_policy=3", which > automatically updates the config on the SC in case the autosaved > configuration is newer than the one on the SC. Can we use this as an "auto > save" feature which keeps the config on the SC up-to-date, and just forget to > save tha config manually? It's at best a partial safety net in case you've forgotten to do the manual update and LDoms manager daemon (ldmd) has restarted for some reason (e.g. reboot or 'svcadm restart ldmd'). The autorecovery_policy isn't checked on every change to the config, only on ldmd restart. > The actions of autorecovery_policy takes place at which phase, only once > during a system/ldm startup, or after any change in the configuration? Currently the autorecovery_policy is only checked on any restart of ldmd. So, you could automatically force the update if you did a 'svcadm restart ldmd' (with autorecovery_policy set to 3). One problem with doing an update on every change is that ldm add-spconfig's take some time to do (typically 15-30 seconds), and it would probably be unpleasant to do those updates whenever the config changes. For example, when you're building a new domain, there are a lot of interim config's that you're probably not really interested in temporarily saving. Mike > Could anyone clarify this? > > Regards, > sendai
