User Tools
backup_script
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| backup_script [2025/05/17 17:21] – final ver. in prod on 2 backupserv. - 1 and 2 T. rout. respectively thilo | backup_script [2025/06/20 19:06] (current) – [Goals] thilo | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| \\ | \\ | ||
| - | - You want to schedule a backup done via a cron job. | + | - You want to schedule a backup |
| - | - You want the script initiated from, and stored in a safe location | + | - You want the script initiated from, and stored in a safe location |
| - You do not wish to install SFTP just for these backups. | - You do not wish to install SFTP just for these backups. | ||
| Line 13: | Line 13: | ||
| The script at the bottom of this page will create and download the backup without needing to have SFTP enabled on the router. | The script at the bottom of this page will create and download the backup without needing to have SFTP enabled on the router. | ||
| - | We could, of course, create the backup as a cron job on the router itself, and then use the mechanism applied in the script below to download the backup file. However, let's assume you want everything done in just one run of the script. To achieve this, the script covers creation of the backup in an individual file with timestamp and download. | + | You could, of course, create the backup as a cron job on the router itself, and then use the mechanism applied in the script below to download the backup file. However, let's assume you want everything done in just one run of the script. To achieve this, the script covers creation of the backup in an individual file with timestamp and download. |
| In this way, just one run of the script on the backup server will create the backup and download it to to a safe location. | In this way, just one run of the script on the backup server will create the backup and download it to to a safe location. | ||
| - | |||
| - | 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 the GUI using the following steps (last tested at 22.04.2025): | + | You may cross-check that the backups are identical to the ones via the GUI using the following steps (last tested at 2025-04-22): |
| \\ | \\ | ||
| Line 28: | Line 26: | ||
| - Create a backup via a script | - Create a backup via a script | ||
| - Copy both files to router | - Copy both files to router | ||
| - | - Convert both files via the command "//nvram convert// < | + | - Convert both files via the command: \\ '' |
| - Perform a diff between the two resulting text files. | - Perform a diff between the two resulting text files. | ||
| \\ | \\ | ||
| - | The script then archives the resulting data in a tar file and sends it through the netcat command, transferring it over the network. | + | The script then archives the resulting data in a tar file and sends it through the netcat command, transferring it over the network. Restore a backup file uses the same procedure as restoring |
| - | Restore a backup file is the same procedure as resorting | + | |
| \\ | \\ | ||
| Line 44: | Line 41: | ||
| - The netcat command must be available on the backup server. | - The netcat command must be available on the backup server. | ||
| - | - The router' | + | - The router' |
| \\ | \\ | ||
| Line 52: | Line 49: | ||
| \\ | \\ | ||
| - | - Command line arguments: backup directory, id-file and router (eg. as IP). If provided, these will be used, else defaults apply (Router IP from `ip r`) | + | - Command line arguments: backup directory, id-file and router (as IP address). \\ If provided, these will be used. Otherwise, the defaults |
| - | - Sometimes tar fails. - cover this error by just cleaning, next cron run may do it | + | - Sometimes tar may fail. You can solve this by just cleaning. The next \\ cron run may do that. |
| - All earlier backups from the same day are abandoned. | - All earlier backups from the same day are abandoned. | ||
| - | - A total number of backups is kept. This number is configurable. Older ones are deleted. | + | - A total number of backups is kept. This number is configurable. |
| \\ | \\ | ||
| Line 107: | Line 104: | ||
| # take date from localhost (i.e. backupserver) into backup filename | # take date from localhost (i.e. backupserver) into backup filename | ||
| | | ||
| + | |||
| pushd ${DIR2BACKUP} > /dev/null | pushd ${DIR2BACKUP} > /dev/null | ||
| Line 163: | Line 160: | ||
| fi | fi | ||
| popd > /dev/null | popd > /dev/null | ||
| - | | + | |
| \\ | \\ | ||
backup_script.1747498888.txt.gz · Last modified: by thilo
Page Tools
