This write-only value triggers an asynchronous save of the device's configuration database to either the primary or secondary persistent store, chosen by the value set (saveToPrimary or saveToSecondary), while the SNMP agent keeps responding to other gets and sets during the save. An admin uses this to commit running configuration changes to non-volatile storage on a unit that maintains dual (primary/secondary) configuration images. For example, an admin sets this to saveToSecondary(2) to preserve a tested configuration on the backup store before making further risky changes to the primary.