Core issue
This may be required to keep up-to-date startup configurations on both Supervisor's non-volatile RAM (NVRAM) and Slot0: cards at the same time since with a write memory command, you may not have a copy to all places. For example, it is not possible to save the configurations to passive Supervisor's NVRAM and Slot0:.
Resolution
During normal operation, the startup-config and config-registers configurations are synchronized by default between the two Supervisor Engines. In a switchover, the new active Supervisor Engine uses the current configuration. It may be required to synchronoze the startup configurations on both Supervisor's NVRAM and Slot0: cards at the same time since with a write memory command it is not possible to copy the configurations to a redundant Supervisor's NVRAM and Slot0.
In order to copy the configuration, use the copy command as explained in these examples:
In order to copy a file to the disk0: device on a redundant Supervisor Engine:
Router#copy source_device:source_filename slavedisk0:target_filename
In order to copy a file to the bootflash: device on a redundant Supervisor Engine:
Router#copy source_device:source_filename slavesup-bootflash:target_filename
In order to copy a file to the bootflash: device on a redundant MSFC3:
Router#copy source_device:source_filename slavebootflash:target_filename
