add node about inode usage of backups
This commit is contained in:
parent
1d0b6049c4
commit
47bd8b85fc
|
@ -49,7 +49,9 @@ This is used for creating timelapses, see the cmd help to know how
|
|||
same as historyDownload, just that its designed for running on the storage server by copying the chunks. Also instead of time you define the amount of days you want to make a timelapse of.
|
||||
|
||||
## backupSync.sh
|
||||
shell script that can be launched with backup.js to sync to a storage server after every backup. It uses rsync which is much faster than ftp, sftp or any other methode
|
||||
shell script that can be launched with backup.js to sync to a storage server after every backup. It uses rsync which is much faster than ftp, sftp or any other methode.
|
||||
### Note:
|
||||
Backups aka historical view does use lots of files and might eventually hit the inode limit of your file system, consider to use mksquashfs to compress past backups into one image
|
||||
|
||||
## liveLog.sh
|
||||
shell script that watches the pixel.log file and outputs the stats of the current IPs placing there
|
||||
|
|
Loading…
Reference in New Issue
Block a user