Backup location not being used by dietpi-update

General Discussion
1

When running dietpi-update and selecting backup before update the preconfigured location that is saved in dietpi-backup is not being used and instead the backup goes to /mnt/backup.

I probably could symlink /mnt/backup to point to the nfs folder, any problems that could arise from this?

2

hmm something I can’t confirm.

I created a demo backup at /mnt/dietpi-backup-test/

Afterwards I was running dietpi-update. Selecting the backup part automatically updated the existing backup at /mnt/dietpi-backup-test/. There was no new backup created at /mnt/backup

root@DietPiOPi5:/boot/dietpi# dietpi-update

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Checking for available DietPi update

[  OK  ] DietPi-Update | Checking IPv4 network connectivity
[  OK  ] DietPi-Update | Checking DNS resolver
[ INFO ] DietPi-Update | Getting latest version from: https://raw.githubusercontent.com/MichaIng/DietPi/master/.update/version
[  OK  ] DietPi-Update | Got valid latest version: 9.3.0
[  OK  ] DietPi-Update | Update available:
[ INFO ] DietPi-Update | Current version : v9.2.0
[ INFO ] DietPi-Update | Latest version  : v9.3.0

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Checking for update pre-requirements

[  OK  ] DietPi-Update | DietPi-Userdata validation: /mnt/dietpi_userdata
[  OK  ] DietPi-Update | Free space check: path=/ | available=110742 MiB | required=100 MiB
[ SUB1 ] DietPi-Backup > Backup
[ SUB2 ] DietPi-Services > stop
[  OK  ] DietPi-Services | stop : cron
[ INFO ] DietPi-Backup | Checking for required APT packages: rsync
[ INFO ] DietPi-Backup | Backup to /mnt/dietpi-backup-test in progress, please wait...
sending incremental file list
         48,063   0%   27.92kB/s    0:00:01 (xfr#2, to-chk=0/57874)

sent 1,777,368 bytes  received 5,096 bytes  712,985.60 bytes/sec
total size is 2,778,990,283  speedup is 1,559.07
[  OK  ] DietPi-Backup | cp -a /etc/debian_version /mnt/dietpi-backup-test/data/etc/debian_version
[  OK  ] DietPi-Backup | touch /mnt/dietpi-backup-test/data
[ SUB2 ] DietPi-Services > start
[  OK  ] DietPi-Services | start : cron
[  OK  ] DietPi-Backup: Backup | Completed

you can verify backup location as follow

cat /boot/dietpi/.dietpi-backup_settings | grep FP_TARGET
3

First thanks for the quick reply, oddly though,

cat /boot/dietpi/.dietpi-backup_settings | grep FP_TARGET
FP_TARGET=/mnt/backup/dietpi-backup

after running the update yesterday, now the nfs backup location had to be manually re selected in dietpi-backup to the nfs location. It remained selected after a reboot test.

cat /boot/dietpi/.dietpi-backup_settings 
FP_TARGET=/mnt/nfs_client/dietpi-backup

I assume one can directly modify FP_TARGET in /boot/dietpi/.dietpi-backup_settings for future installs?

4

yes that should be possible.

or you call it interactively with your desired target location

dietpi-backup -1 /path/to/target = Restore
dietpi-backup  1 /path/to/target = Backup
1 Like