-
Notifications
You must be signed in to change notification settings - Fork 4
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: pre-run/post-run options #6
Comments
Thank's for reporting, @githubjsorg! Actually I like the idea. But there are two things in my mind about that.
But I'll think about it anyway and maybe just integrate it. |
"I'm already working on a successor to this tool which already has support for this." Nice. What is the name of this and do you have an ETA for it? As for the pre/post run stuff, for my current project, I have been just wrapping rsync_tmbackup in another SSH script for each backup job. Not as elegant but does the job. |
There is no name nor ETA yet. But I'll announce any news on that project in this repo. |
Hi. I haven't used this or the related rsync-time-backup tools yet but am planning on doing so.
A feature that would be extremely useful in this wrapper is pre/post-backup/restore commands similar to pre/post-up/down options in debian /etc/network/interfaces config.
Ex.
PRE_BACKUP=SOME COMMAND
POST_BACKUP=SOME OTHER COMMAND
Example Use Case:
Make sure a Databases files are synced to disk before backup. Either by shutting the DB down PRE_RUN and starting it back up POST_RUN. Or using lock/unlock commands pre/post run, etc.
Or alternatively do a dump so that also gets backed up.
The text was updated successfully, but these errors were encountered: