Save named config

[pink-panther]

I am fairly new to Palo Alto so please forgive me for asking dumb question. With respect to backing up config before upgrade, if I save it as 'mybackup.xml'  and something goes wrong with upgrade and I import it back in to restore, does the Palo Alto replace the running-config.xml file with my 'mybackup.xml' automatically ? Also what is the difference between saving as named config file with a generic name and saving running-config.xml? Is it purely the name.

[SebRupik]

Hi there,

The restoration sequence would be to load 'mybackup.xml' and then commit it. It is the commit action that would cause the existing running-config to be replaced with your backed up version.

A named config as you point out is simply that, and allows you to give it some meaningful name referencing its state for example, so long as it is within the character limit!

cheers,

Seb.

[Mick_Ball]

probably teaching you to suck eggs here but perhaps also export the named config.....   just in case.......

[pink-panther]

Many thanks Seb. Following the example mentioned, I assume PA updates 'candidate-config.xml' file with changes in 'mybackup.xml' first before updating 'running-config.xml' when commit happens?  

[OtakarKlier · Accepted solution]

Hello,

So first backup the config:

Device Tab ->Setup -> Operations subtab

Save the named config

Export the named config

To Restore from exported config:

Device Tab ->Setup -> Operations subtab

Import named config

load named config

commit changes

its the simplified steps.

Hope this helps.

[SebRupik · Accepted solution]

Yes, when you load your backup config it will become the candidate config. Once the commit completes it will become the running config.

cheers,

Seb.