Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: dry-run plus #1

Open
bitwombat opened this issue Sep 6, 2016 · 0 comments
Open

Feature request: dry-run plus #1

bitwombat opened this issue Sep 6, 2016 · 0 comments

Comments

@bitwombat
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant