On 2009-10-15, Ryan Schmidt wrote:
> Yes, the backup will preserve anything that exists between revisions
> 600 and HEAD, regardless when those items were initially created. But
> it will not keep the history of any changes (the diffs, or the log
> messages) of events that occurred before 600.
> I strongly recommend you continue to back up your entire repository,
> and not attempt to cut out revisions to save space. Cutting out
> revisions does not always save space; sometimes it increases your disk
> space requirement.
> In addition, if you were to restore this partial dump into a new
> repository, it would be a totally different repository than before.
> You would have to give it a new UUID, and would therefore have to
> delete and re-checkout any working copies you had and manually move
> over any uncommitted changes you still had in them. It would not be a
> seamless operation. I'm sure that, if you're in a situation where
> you've just had to restore your repository, due to hard drive
> malfunction or whatever, you'll already have enough to deal with
> without also having to deal with recreating all your working copies.
I don't have any uncommitted changes in working copies. I'm the only
user and I keep them tidy. ;-)
> Old revisions never change. (Though old revision properties might
> change, if you allow it with a pre-revprop-change hook.) So consider
> creating a dumpfile of the first 600 revisions and burning them to a
> CD or DVD. Then your regular backup routine can still just back up
> revision 600 through HEAD, and you can still restore the entire
> history by first loading the first 600 revisions from the CD or DVD,
> then loading the current backup. You may or may not want to create
> your 600-through-HEAD dump using the --incremental switch.
OK, that sounds sensible. Thanks.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-19 14:17:07 CEST