[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: (--incremental ) was backup strategy - and unrecoverable databases.

From: Alan Knowles <alan_at_akbkhome.com>
Date: 2004-05-27 04:12:44 CEST

unfortunately --incremental didn't really help that much.. - I think it
had a similar effect as
#svnadmin dump -r 4900 /var/subversion/svn

in that it dumped the full contents of the changed files. (rather than
the changelog + diff..) - so the file sizes where still pretty huge..

Quite a few of the projects I work on use code generators
(lex/treecc/jay etc.) -which regenerate 3000+ line files on each
revision. - it quickly adds up.. (although only 10-50 lines actually
change on each commit..)


Kirill Lapshin wrote:
> Alan Knowles wrote:
>> ## then this in the cronjob.
>> #svnadmin dump -r 4900 /var/subversion/svn | gzip >
>> /var/backup/$DATE.svn.gz
>> (eg. all changes since the 'base' backup)
>> however it appears that this dumps the current state of the file each
>> time it was changed in the repository, rather than using diff's....
>> hence it is also very large.. (looking at the line count about 4000
>> lines change in the last 90 revisions. however the file is 915273
>> lines long..)
> You can use --incremental
> Quoting svn book:
> By default, Subversion will not express the first dumped revision as
> merely differences to be applied to the previous revision. For one
> thing, there is no previous revision in the dump file! And secondly,
> Subversion cannot know the state of the repository into which the dump
> data will be loaded (if it ever, in fact, occurs). To ensure that the
> output of each execution of svnadmin dump is self-sufficient, the first
> dumped revision is by default a full representation of every directory,
> file, and property in that revision of the repository.
> However, you can change this default behavior. If you add the
> --incremental option when you dump your repository, svnadmin will
> compare the first dumped revision against the previous revision in the
> repository, the same way it treats every other revision that gets
> dumped. It will then output the first revision exactly as it does the
> rest of the revisions in the dump rangeómentioning only the changes that
> occurred in that revision. The benefit of this is that you can create
> several small dump files that can be loaded in succession, instead of
> one large one
> --Kirill
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

Can you help out?
Need Consulting Services or Know of a Job?
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 27 04:11:52 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.