Bug 8790 - rsync stream file type
Summary: rsync stream file type
Status: RESOLVED WORKSFORME
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.0.6
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-03 23:02 UTC by Dave Yost
Modified: 2013-06-02 23:37 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Yost 2012-03-03 23:02:36 UTC
Give rsync the ability to write/read its stream to/from an archive file. Almost certainly the best option would be for rsync to maintain its own archive file format.

Why do this? Because rsync is awesome, we have learned all of its options by now, and unlike tar, cpio, etc., rsync captures all metadata, and rsync streams across a connection.

A future enhancement would be the ability to append an update to the end of the file.

Another enhancement would be optionally to append an index, so that files could be retrieved quickly from the archive.

This enhancement could be useful for versioned backups.
Comment 1 Kevin Korb 2012-03-04 04:40:50 UTC
Is --write-batch or --only-write-batch what you are looking for?

If it is and you are trying to do backups I suspect you probably want rdiff-backup instead.  But then you will be back here eventually for performance reasons.
Comment 2 Wayne Davison 2013-06-02 23:37:40 UTC
Yeah, the batch stuff already allows streaming of the protocol, which can batch up some changes into a single file.  It doesn't allow appending, and really I think we should not complicate it further.