M-Welsch / backup-server

Backup Server (BaSe)

Apache License 2.0

3 stars 1 forks source link

file synchronization works #15

Closed M-Welsch closed 8 months ago

M-Welsch commented 8 months ago

Description

we want to synchronize the data from the NAS to the backup-hdd to have a backup of the files on the NAS

What happens if we don't do it (aka Why is it important)?

we don't have a backup

Definition of Ready

[x] #10
[x] #14

Key Tasks

[x] compose a command like rsync -avh NAS::backup_source_data <backup target>
[x] call this command from python

Acceptance Criteria

[x] when we execute that command, the synchronization happens and finishes successfully

M-Welsch commented 8 months ago

synchronization log looks kinda wreid. read only filesystem after a full backup has already worked

Jan 07 21:10:04 raspberrypi python3[707]: mount: /media/BackupHDD: must be superuser to use mount.
...
Jan 07 21:10:04 raspberrypi python3[318]: 2024-01-07 21:10:04,460 INFO: __main__: Fehlerausgabe: rsync: [Receiver] mkdir "/media/BackupHDD/backups/current" failed: No such file or directory (2)
Jan 07 21:10:04 raspberrypi python3[318]: rsync error: error in file IO (code 11) at main.c(787) [Receiver=3.2.3]

M-Welsch commented 8 months ago

Since everything that concerns the MVP milestone works now (kind of), I set the wake-interval to 1 minute and let it run for a while.

Test 1

Setup

set wakeup interval to 1 minute
small set of 10x 1MiB or so. With the raspi3 everything bigger would take eternities
data was always the same. Since rsync needs to connect anyway I think it tests the whole system sufficiently

Results

looking at the logfile: logfile.log

we had about 11 runs (logfile has 229 lines, each run occupies around 20 lines)
4 runs had errors like rsync: [Receiver] mkdir "/media/BackupHDD/backups/current" failed: No such file or directory (2), see #19