This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
backup_script [2025/04/25 15:50] – typos and minor iomprovements thilo | backup_script [2025/04/28 18:23] (current) – [Goals] hogwild | ||
---|---|---|---|
Line 11: | Line 11: | ||
\\ | \\ | ||
- | The script | + | The script |
- | \\ One option would be to create the backup as a cron job on the router itself. Then, in a second step, use the mechaism | + | We could, of course, |
- | In this way, just one run of the script on the backup server | + | In this way, just one run of the script on the backup server |
Action is based on using a here doc to execute commands on the router. | Action is based on using a here doc to execute commands on the router. | ||
- | The backup is created using the "// | + | \\ \\ The backup is created using the "// |
- | You may cross-check that the backups are identical to the ones via web interface by a) download backup via GUI b) create backup by script, c) copy both files to router d) convert both files by "nvram convert < | + | You may cross-check that the backups are identical to the ones via the GUI using the following steps: |
- | The script then archives the resulting data in a tar file and sends it through the netcat command, which transfers it over the network. | + | \\ |
- | A configurable number of backups is kept, older ones are deleted. | + | - Download the backup via the graphical interface |
+ | - Create a backup via a script | ||
+ | - Copy both files to router | ||
+ | - Convert both files via the command "// | ||
+ | - Perform a diff between the two resulting text files. | ||
\\ | \\ | ||
- | Prerequisites: | + | The script then archives the resulting data in a tar file and sends it through the netcat command, transferring it over the network. |
+ | |||
+ | A configurable number of backups is kept. Older ones are deleted. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | ==== Prerequisites | ||
\\ | \\ |