third-party-mirrors/zfs_autobackup
1
0
Fork 1
mirror of https://github.com/psy0rz/zfs_autobackup.git synced 2025-05-30 01:19:16 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix linter isue

Browse Source
This commit is contained in:
Edwin Eefting 2020-03-15 23:02:03 +01:00
parent 6f8c73b87f
commit 4ed53eb03f
1 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -101,11 +101,11 @@ On the server that runs zfs-autobackup you need to create an SSH key. You only n
Use the `ssh-keygen` command and leave the passphrase empty: Use the `ssh-keygen` command and leave the passphrase empty:
```console ```console
root@backup:~# ssh-keygen root@backup:~# ssh-keygen
Generating public/private rsa key pair. Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase): Enter passphrase (empty for no passphrase):
Enter same passphrase again: Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa. Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub. Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is: The key fingerprint is:
@ -122,10 +122,9 @@ The key's randomart image is:
| .+o**| | .+o**|
| .. +B@| | .. +B@|
+----[SHA256]-----+ +----[SHA256]-----+
root@backup:~# root@backup:~#
``` ```
#### Copy SSH key to `pve` #### Copy SSH key to `pve`
Now you need to copy the public part of the key to `pve` Now you need to copy the public part of the key to `pve`
@ -137,14 +136,14 @@ root@backup:~# ssh-copy-id root@pve.server.com
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub" /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
Password: Password:
Number of key(s) added: 1 Number of key(s) added: 1
Now try logging into the machine, with: "ssh 'root@pve.server.com'" Now try logging into the machine, with: "ssh 'root@pve.server.com'"
and check to make sure that only the key(s) you wanted were added. and check to make sure that only the key(s) you wanted were added.
root@backup:~# root@backup:~#
``` ```
### Select filesystems to backup ### Select filesystems to backup
@ -183,7 +182,7 @@ rpool/swap autobackup:offsite1 false
### Running zfs-autobackup ### Running zfs-autobackup
Run the script on the backup server and pull the data from the server specfied by --ssh-source. Run the script on the backup server and pull the data from the server specfied by --ssh-source.
```console ```console
[root@backup ~]# zfs-autobackup --ssh-source pve.server.com offsite1 backup/pve --progress --verbose [root@backup ~]# zfs-autobackup --ssh-source pve.server.com offsite1 backup/pve --progress --verbose
@ -251,7 +250,7 @@ Or just create a script and run it manually when you need it.
* Use ```--clear-mountpoint``` to prevent the target server from mounting the backupped filesystem in the wrong place during a reboot. * Use ```--clear-mountpoint``` to prevent the target server from mounting the backupped filesystem in the wrong place during a reboot.
* Use ```--resume``` to be able to resume aborted backups. (not all zfs versions support this) * Use ```--resume``` to be able to resume aborted backups. (not all zfs versions support this)
### Speeding up SSH ### Speeding up SSH
You can make your ssh connections persistent and greatly speed up zfs-autobackup: You can make your ssh connections persistent and greatly speed up zfs-autobackup: