Thank you for the quick response! The current backup runs since 6h and it only uses around 1-2% of the CPU. There is also no gzip process running. So it might be something else...
- Jonas On 6/1/21 3:15 PM, Reio Remma wrote: > On 01.06.2021 16:12, Jonas Schöpf wrote: >> Hi all! >> >> I found out about rdiff-backup two weeks ago after I searched for a >> method to get incremental backups of my system. >> I experience some problems while doing my backup and I hope that >> somebody can tell me what I am doing wrong. >> >> I understand that the initial backup is really slow and took more than >> ~10h for my 400 GB. >> Now if I do another backup, I would expect that it is quite fast, but >> after it exceeded 8h and I just aborted the whole backup process. >> >> I use the following command: >>> rdiff-backup --terminal-verbosity 8 --print-statistics \ >>> --exclude-globbing-filelist $HOME/.excludes \ >>> $HOME $DRIVE >> Can anybody tell me what I am doing wrong? >> >> Thank you for your help! >> >> Cheers, >> Jonas > > Hello! A while ago I had a similar problem and I narrowed it down to > rdiff-backup compressing files that were already compressed. I would > suggest having a look at CPU usage etc when the backup is running. iirc > it uses gzip which is fairly processor hungry. > > Good luck! > Reio > -- GPG fingerprint: 0BF3 B30B F1D5 6556 795E F68F 8626 F794 FE62 BE1F
