You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Dan Berger <db...@ix.netcom.com> on 2001/12/11 21:18:52 UTC
Re: question: repository backups?
No - it actually didn't. If anyone has any comments, I'd love to hear
them.
On Tue, Dec 11, 2001 at 02:02:35PM -0600, Karl Fogel wrote:
> Hey, did this old post of yours ever get answered?
>
> All traffic is on the `dev@subversion.tigris.org' list, I don't know
> if anyone's really reading `users' yet...
>
> -Karl
>
> Dan Berger <db...@ix.netcom.com> writes:
> > Hey folks - I've been watching subversion with much interest over the
> > past few months - and I've got a few questions. This may not be the
> > right forum - but it seemed the most logical place.
> >
> > 1. Operational Concerns: One of the nice things about CVS is that the
> > repository is transparent - you can tar it up, move it around, dump it
> > to tape like any other file system - do incremental backups, etc. Can
> > someone on this list discuss how subversion intends to address
> > day-to-day repository maintenance?
> >
> > 2. Client library language bindings: I seem to recall that there's been
> > discussion of client library bindings for C and Python - any plans for
> > Java? I've got a project in front of me that I'm starting to evaluate
> > revision control systems for - and one requirement is a set of Java
> > bindings. Any comment?
> >
> > Any information (even if it's RTFM - and a pointer to a FM that contains
> > these answers) would be appreciated.
> >
> > Cheers.
> >
> > --
> > Dan Berger [dberger@ix.netcom.com]
> > http://home.ix.netcom.com/~dberger
> > Inter arma silent leges
> >
> > "Experience should teach us to be most on our guard to protect
> > liberty when the government's purposes are beneficent. Men born to
> > freedom are naturally alert to repel invasion of their liberty by
> > evil minded rulers. The greatest dangers to liberty lurk in
> > insidious encroachment by men of zeal, well-meaning but without
> > understanding."
> > Justice Louis Brandeis, dissenting, Olmstead v US (1928)
> >
> > A982 E6B1 CB2F 7A49 843A 9297 DA73 4371 1F54 8D0C
--
Dan Berger [dberger@ix.netcom.com]
http://home.ix.netcom.com/~dberger
Inter arma silent leges
"Experience should teach us to be most on our guard to protect
liberty when the government's purposes are beneficent. Men born to
freedom are naturally alert to repel invasion of their liberty by
evil minded rulers. The greatest dangers to liberty lurk in
insidious encroachment by men of zeal, well-meaning but without
understanding."
Justice Louis Brandeis, dissenting, Olmstead v US (1928)
A982 E6B1 CB2F 7A49 843A 9297 DA73 4371 1F54 8D0C
Re: question: repository backups?
Posted by Philip Martin <ph...@codematters.co.uk>.
Ben Collins-Sussman <su...@collab.net> writes:
> "Jay Freeman \(saurik\)" <sa...@saurik.com> writes:
>
> > Additionally, there are sometimes cases where someone checks an
> > amazingly large file into the repository for no good reason; such as ncb
> > files (the Visual Studio class browser temporary files, which tend to
> > get quite large), but this also goes for large graphics files that they
> > were using to test). With CVS I can simply delete the file from the
> > server end without causing the clients problems (the CVS client
> > specifically supports "this file was removed from the repository" and
> > deletes the file locally). With Subversion I don't see a good way to do
> > this.
>
> $ svn rm http://path/to/big/ugly/file
>
> Poof, it's gone from the repository, and you didn't even need a
> working copy. Next time any client updates, it will be removed
> from their working copy.
I think Jay wants the 'svn obliterate' command see, issue #516.
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: question: repository backups?
Posted by Ben Collins-Sussman <su...@collab.net>.
"Jay Freeman \(saurik\)" <sa...@saurik.com> writes:
> Additionally, there are sometimes cases where someone checks an
> amazingly large file into the repository for no good reason; such as ncb
> files (the Visual Studio class browser temporary files, which tend to
> get quite large), but this also goes for large graphics files that they
> were using to test). With CVS I can simply delete the file from the
> server end without causing the clients problems (the CVS client
> specifically supports "this file was removed from the repository" and
> deletes the file locally). With Subversion I don't see a good way to do
> this.
$ svn rm http://path/to/big/ugly/file
Poof, it's gone from the repository, and you didn't even need a
working copy. Next time any client updates, it will be removed
from their working copy.
> Also, with CVS you can do archiving. At some point I can take bodies of
> files that are in attics and therefore not in usage anymore; and
> entirely remove them from the repository off to some backup location
> (saving the active server from having the "hard disk requirements
> _never_ get smaller, only bigger) problem. If that file ever _is_
> needed they can request that it get put back on the server. Subversion
> doesn't seem capable of this either.
That's because Subversion is a true time machine. If I say, 'show me
what this project looked like on 9/3/2000', I shouldn't get an error
telling me that some file needs to be restored in the repository. I
guess this is just a 'purist' view of what a repository should be.
> Best case scenario (to me) would be a system integrated as part of the
> version control for entirely removing revisions. So, if revision 5
> added a file, and revision 6 removed it, revision 5 could be entirely
> deleted, linking the information from 4 directly to 6, and if people
> requested version 5 they got back a nice information bubble about how it
> was removed from the repository.
Already planned -- see issue #516, 'svn obliterate'.
> As for archival, I would want to tell Subversion to transfer from one
> database revisions earlier than a certain point maybe to a separate
> database (understanding that Subversion would probably want to avoid its
> own file format).
This seems doable someday, I suppose. If we can someday support
cross-repository links, then a file's history might be able to point
backwards into a different 'backed up' repsository.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: question: repository backups?
Posted by "Jay Freeman (saurik)" <sa...@saurik.com>.
Additionally, there are sometimes cases where someone checks an
amazingly large file into the repository for no good reason; such as ncb
files (the Visual Studio class browser temporary files, which tend to
get quite large), but this also goes for large graphics files that they
were using to test). With CVS I can simply delete the file from the
server end without causing the clients problems (the CVS client
specifically supports "this file was removed from the repository" and
deletes the file locally). With Subversion I don't see a good way to do
this.
Also, with CVS you can do archiving. At some point I can take bodies of
files that are in attics and therefore not in usage anymore; and
entirely remove them from the repository off to some backup location
(saving the active server from having the "hard disk requirements
_never_ get smaller, only bigger) problem. If that file ever _is_
needed they can request that it get put back on the server. Subversion
doesn't seem capable of this either.
Best case scenario (to me) would be a system integrated as part of the
version control for entirely removing revisions. So, if revision 5
added a file, and revision 6 removed it, revision 5 could be entirely
deleted, linking the information from 4 directly to 6, and if people
requested version 5 they got back a nice information bubble about how it
was removed from the repository.
As for archival, I would want to tell Subversion to transfer from one
database revisions earlier than a certain point maybe to a separate
database (understanding that Subversion would probably want to avoid its
own file format).
Sincerely,
Jay Freeman (saurik)
saurik@saurik.com
-----Original Message-----
From: sussman@collab.net [mailto:sussman@collab.net]
Sent: Tuesday, December 11, 2001 3:55 PM
To: Dan Berger
Cc: kfogel@collab.net; dev@subversion.tigris.org;
users@subversion.tigris.org
Subject: Re: question: repository backups?
Dan Berger <db...@ix.netcom.com> writes:
> > > 1. Operational Concerns: One of the nice things about CVS is that
the
> > > repository is transparent - you can tar it up, move it around,
dump it
> > > to tape like any other file system - do incremental backups, etc.
Can
> > > someone on this list discuss how subversion intends to address
> > > day-to-day repository maintenance?
The svn repository is a directory full of Berkeley .db files and
scripts. You can tar it up, move it around, dump it to tape. You can
do 'hot backups' -- we have a script that does that already (in our
source tree.)
Read about Berkeley DB at www.sleepycat.com. The repository is really
just a berkeley 'environment'.
...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: question: repository backups?
Posted by Ben Collins-Sussman <su...@collab.net>.
Dan Berger <db...@ix.netcom.com> writes:
> > > 1. Operational Concerns: One of the nice things about CVS is that the
> > > repository is transparent - you can tar it up, move it around, dump it
> > > to tape like any other file system - do incremental backups, etc. Can
> > > someone on this list discuss how subversion intends to address
> > > day-to-day repository maintenance?
The svn repository is a directory full of Berkeley .db files and
scripts. You can tar it up, move it around, dump it to tape. You can
do 'hot backups' -- we have a script that does that already (in our
source tree.)
Read about Berkeley DB at www.sleepycat.com. The repository is really
just a berkeley 'environment'.
> > > 2. Client library language bindings: I seem to recall that there's been
> > > discussion of client library bindings for C and Python - any plans for
> > > Java? I've got a project in front of me that I'm starting to evaluate
> > > revision control systems for - and one requirement is a set of Java
> > > bindings. Any comment?
Alex Mueller is writing JNI bindings. He commits very frequently.
:-) Look in the bindings/ directory of our tree.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org