SunRed/snap-sync-scripts
1
0
Fork 0
Code Issues Pull requests Releases Activity

Reference specific line

Browse source
This commit is contained in:
Manuel 2022-10-15 21:11:30 +02:00
parent 104a8b8cfb
commit f354f97774
Signed by: Manuel
GPG key ID: 4085037435E1F07A
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -9,7 +9,7 @@ Based on this it's also possible to use a network target to simply replicate sna
## Config ## Config
You should have a subvolume present already on your backup drive using something like `snap-sync -c "root home" -d "latest incremental backup"` pointing to `snapshot_root` configured in [clean-snap-sync-external.sh](scripts/clean-snap-sync-external.sh). After first replication snap-sync automatically uses the same subvolume again so that you just have to set the UUID of your external drive you placed your initial snapshot on in the bash scripts in the [scripts](scripts) folder. You should have a subvolume present already on your backup drive using something like `snap-sync -c "root home" -d "latest incremental backup"` pointing to `snapshot_root` configured in [clean-snap-sync-external.sh](scripts/clean-snap-sync-external.sh#L16). After first replication snap-sync automatically uses the same subvolume again so that you just have to set the UUID of your external drive you placed your initial snapshot on in the bash scripts in the [scripts](scripts) folder.
If you are going to enable `snap-sync-cleanup.service`, edit the snapshot root and the amount of snapshots to keep on the external drive in `clean-snap-sync-external.sh` as well. If you are going to enable `snap-sync-cleanup.service`, edit the snapshot root and the amount of snapshots to keep on the external drive in `clean-snap-sync-external.sh` as well.