You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, something important at my source isn't available - maybe it isn't mounted, or maybe I've blown it away accidentally (half the point of backups). When I rsync with --delete, away it goes. Sometimes I catch this halfway through the damage by watching rsync's stdout, but usually I've now got a few GB of re-rsyncing to look forward to.
Other times, I've created something massive that isn't covered by my exclude patterns. If I'm lucky I manually spot this, if I'm unlucky I walk away only to find a simple incremental backup took 2 hours and sent 3 GB.
I've written crude wrappers around rsync --dry-run to cough up statistics about what's going to be done - how many files are going to be deleted or sent, how many GB are going to be deleted or sent.
The intention is to help me catch something costly before it costs.
Would be great if encsync helped with this!
The text was updated successfully, but these errors were encountered:
Sometimes, something important at my source isn't available - maybe it isn't mounted, or maybe I've blown it away accidentally (half the point of backups). When I rsync with --delete, away it goes. Sometimes I catch this halfway through the damage by watching rsync's stdout, but usually I've now got a few GB of re-rsyncing to look forward to.
Other times, I've created something massive that isn't covered by my exclude patterns. If I'm lucky I manually spot this, if I'm unlucky I walk away only to find a simple incremental backup took 2 hours and sent 3 GB.
I've written crude wrappers around rsync --dry-run to cough up statistics about what's going to be done - how many files are going to be deleted or sent, how many GB are going to be deleted or sent.
The intention is to help me catch something costly before it costs.
Would be great if encsync helped with this!
The text was updated successfully, but these errors were encountered: