Red Hat Bugzilla – Bug 238158
fwbackups: RFE: rsync enhancements
Last modified: 2008-07-03 14:55:27 EDT
Description of problem:
Moved from bug #433772.
For rsync backups, please give the ability to not use dated directories.
That way, a fast sync can be setup that just snapshots the data defined in the
backup job. Also, the ability to use rsync over ssh would be superb.
Version-Release number of selected component (if applicable):
As an example, do you mean the user could input a directory name, such as
"MyBackup" and rather than dated directories just have it replace the contents
of "MyBackup" each run?
Not replace, (one-way) synchronize (but I think that's what you meant). And I
don't necessarily care about naming the directory, it could be the same name
(minus the date) that you currently use.
Then each time the backup runs, it updates a snapshot in time of the system it's
In fact, it might be good to keep the date in the directory name and just rename
it at each run. This way you would instantly know when it ran last.
I'm working on fwbackups a bit today, and I'm still unclear as to what you mean
- As in change the options to use (update) snapshots rather than a full copy?
As it works right now, if you specify for example 3 days of rsync backups, each
backup directory will be dated and contain a full backup of the system.
What I am suggesting is the ability to keep a backup directory in sync with the
system when it's run.
When you run the backup the first time, it creates a full set of backed up files
Then, each successive run updates only the files needed (using rsync) to bring
the /backup/target/dir/myname completely up to date with the files on the system.
This essentially gives you an updated set of backed up files from the system
each time that the program is run (a snapshot in time), but at the expense of
only updating the files that have changed (rsync).
Okay I see what you mean - The folder can be renamed to include the date of the
most recent run but the directory contents should never be removed, only updated
with file changes.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Sorry, I know it's been a while but this is being worked on.
Adding FutureFeature keyword to RFE's.
fwbackups-1.43.2-0.1.rc2.fc8 has been submitted as an update for Fedora 8
fwbackups-1.43.2-0.1.rc2.fc9 has been submitted as an update for Fedora 9
fwbackups-1.43.2-0.1.rc2.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update fwbackups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-4809