On Mar 12, 2007, at 11:10, Jiho Han wrote:
>>> Technically speaking, tar on 1 machine/untar on aonther should work,
>>> right?
>>
>> If you're running the same version of Subversion, and the
>> repositories
>> are FSFS-based, then yes. If the repositories are BDB- based, then I
>> believe you must also be sure that the version of BDB is the same,
>> and
>> that the processor architecture endianness is the same. If it
>> isn't, or
>> you're not sure, the safe way that would always work is to
>> svnadmin dump
>> the old repo on the old machine, and svnadmin load it into a new
>> repo on
>> the new machine.
>
> So if tar/untar is enough to relocate a svn repository, then would
> this
> work as a very simple backup strategy as well?
> Basically, zipping up the repo on an interval? (assuming my repo isn't
> huge)
In a situation where you're moving from one machine to another, the
repository will be offline while this is happening, so transferring
the data with tar is fine. But as a backup strategy for a running
repository, to which people may be committing while the backup is
happening, it's less-good... It may still work but it's important to
back things up in a particular order. If tar handles the files
alphabetically, then I believe it's fine, but I don't know if tar
always does that.
There are a number of backup solutions written for Subversion:
svnadmin hotcopy, hot-backup.py, svn-fast-backup and svnadmin dump.
(Check the contrib and tools directories of the Subversion source
distribution.) All of those are designed to correctly back up
Subversion repositories, so if it were me, I would feel safer
trusting my repositories to one of those solutions.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 13 10:52:31 2007