Backing up CS Linux configuration files

CS Linux automatically backs up the node, domain, TN3270 device data (tn3270dev.dat), and TP configuration files whenever you make changes that affect those files (using any of the CS Linux administration tools). For example, when you make a change that affects the node configuration file (sna_node.cfg), CS Linux creates a backup file named sna_node.bkn, where n is either 1 or 2:

• The first time you change the file, the existing configuration is saved to sna_node.bk1.
• The second time you change the file, the existing configuration is saved to sna_node.bk2, leaving sna_node.bk1 unchanged.
• The third time you change the file, and any subsequent times, sna_node.bk1 is discarded, sna_node.bk2 is renamed to sna_node.bk1, and the existing configuration is saved to sna_node.bk2.

This process means that there is a maximum of two backup files for the node configuration file at any time. The same process is used to generate filename extensions for other backup files.

In addition to automatic backups, you should back up configuration files to protect against loss of data under any of the following conditions:

• Before installing a new level of the Linux operating system
• Before installing a new release of CS Linux
• After you create a new configuration

You can back up configuration files using the following commands: