You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Paul Klepac <pk...@io-informatics.com> on 2009/02/06 23:56:15 UTC
Moving FreeBSD to a new server
Hello,
I'm new to UNIX but I've been given the task of moving our existing
TortoiseSVN
to a new server. Basically what is going on is that our existing
FreeBSD/TortoiseSVN
server is starting to have some disk problems and so we want to build a
new server
(install FreeBSD, Apache, and SVN) and move the Berkeley Database.
So as I understand it, I need to install:
* FreeBSD OS: 7.1-RELEASE-i386-disc1.iso
* Apache version 2.2.x : httpd-2.2.11.tar.gz
<http://apache.mirrors.tds.net/httpd/httpd-2.2.11.tar.gz>
o Double-click on the Apache2 installer
o Test the installation: http://localhost/ (a preconfigured website
should appear)
* Subversion (this is the part I'm not sure about)
o Go to http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/
&
Click on "Download this directory in tarball
<http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/subversion
.tar.gz?tarball=1> "
o Which will download subversion.tar.gz & un-tar the files
# tar xvfz subversion.tar.gz
o cd /usr/ports/devel/subversion;
o make install
This will install Subversion & create the BDB
o find the files /httpd/mod_dav_svn.so and mod_authz_svn.so.
Copy these files to the Apache modules directory
o Copy the file /bin/libdb*.dll and /bin/intl3_svn.dll from the
Subversion installation directory to the Apache bin directory.
o Edit Apache's configuration file ( e.g., \Apache
Group\Apache2\conf\httpd.conf) with a text editor
and make the following changes:
Uncomment (remove the '#' mark) the following lines:
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_module modules/mod_dav.so
Add the following two lines to the end of the LoadModule section.
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
o At the end of the config file add the following lines:
1. <Location /svn>
DAV svn
SVNListParentPath on
SVNParentPath D:\SVN
#SVNIndexXSLT "/svnindex.xsl"
AuthType Basic
AuthName "Subversion repositories"
AuthUserFile passwd
#AuthzSVNAccessFile svnaccessfile
Require valid-user
</Location>
This configures Apache so that all your Subversion repositories are
physically located below D:\SVN. The repositories are served to the
outside world from the URL: http://MyServer/svn/ . Access is restricted
to known users/passwords listed in the passwd file.
2. Create the passwd file, open the command prompt again, change
to the apache2 folder (e.g., .../apache group/apache2) and create the
file by entering
Bin/htpasswd -c passwd <username>
This will create a file with the name passwd which is used for
authentication. Additional users can be added with
Bin/htpasswd passwd <username>
3. Restart the Apache service again.
4. Point browser to http://MyServer/svn/MyNewRepository (where
MyNewRepository is the name of the Subversion repository you created
before). If all went well you should be prompted for a username and
password, then you can see the contents of your repository.
Haven't not installed it yet (still waiting for the server to arrive
from Dell), I've taken some liberty with guessing what the commands are;
so if I'm wrong, please, correct me.
Can I just copy the database repository directory from the Old SVN
server to the new one and it'll all work?
Thanks in Advance,
Paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1115354
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Moving FreeBSD to a new server
Posted by Toby Thain <to...@telegraphics.com.au>.
On 6-Feb-09, at 6:56 PM, Paul Klepac wrote:
> Hello,
>
> I’m new to UNIX but I’ve been given the task of moving our
> existing TortoiseSVN
> to a new server. Basically what is going on is that our existing
> FreeBSD/TortoiseSVN
> server is starting to have some disk problems and so we want to
> build a new server
> (install FreeBSD, Apache, and SVN) and move the Berkeley Database.
...
>
> Can I just copy the database repository directory from the Old SVN
> server to the new one and it’ll all work?
I would strongly recommend you take a complete dump of your
repository to reload on the new server, and take the opportunity to
update to the latest Subversion server version.
--Toby
>
> Thanks in Advance,
> Paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1116480
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Moving FreeBSD to a new server
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 6, 2009, at 18:10, Alec Kloss wrote:
> On 2009-02-06 15:56, Paul Klepac wrote:
>
>> I'm new to UNIX but I've been given the task of moving our
>> existing
>> TortoiseSVN
>>
>> to a new server. Basically what is going on is that our existing
>> FreeBSD/TortoiseSVN
>>
>> server is starting to have some disk problems and so we want to
>> build a
>> new server
>>
>> (install FreeBSD, Apache, and SVN) and move the Berkeley Database.
>>
>>
>>
>> So as I understand it, I need to install:
>>
>> * FreeBSD OS: 7.1-RELEASE-i386-disc1.iso
> [chop]
>
> If you're able to tolerate a bit of down time, it might be easier
> to dump all the filesystems from the old server and restore them
> on the new server. If you're really replacing the machine, this
> will guarantee you get every last detail right. If you try to
> reconfigure a new installation to match an existing one, you're
> almost certain to miss some mundane detail that you'll wish you
> hadn't. With dump/restore, the only things you have to reconfigure
> is *maybe* the network interface configuration in /etc/rc.conf.
>
> (If you can't tolerate a bit of down time, you can do
> do level 0s while the respository is active and then do level 1s
> with the repository machine isolated from access. If you practice
> a few times and have less than a few hundred committers I bet you
> can do it with less than five minutes down without too much
> difficulty.)
Another possibility is to use svnsync to replicate the old repository
onto the new server. The new repository will be built from scratch so
it'll be like a dump and load in that respect, but the sync can
happen while the old server is online. When it's done, you can
disable connections to the old server, run svnsync again to catch any
last commits from the old server, and then switch to the new server.
You'll also have to copy your hook scripts and conf files from the
old server, if applicable; svnsync does not copy these. (Neither
would a dump/load.)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1115477
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Moving FreeBSD to a new server
Posted by Alec Kloss <al...@oracle.com>.
On 2009-02-06 15:56, Paul Klepac wrote:
> Hello,
>
>
>
> I'm new to UNIX but I've been given the task of moving our existing
> TortoiseSVN
>
> to a new server. Basically what is going on is that our existing
> FreeBSD/TortoiseSVN
>
> server is starting to have some disk problems and so we want to build a
> new server
>
> (install FreeBSD, Apache, and SVN) and move the Berkeley Database.
>
>
>
> So as I understand it, I need to install:
>
> * FreeBSD OS: 7.1-RELEASE-i386-disc1.iso
[chop]
If you're able to tolerate a bit of down time, it might be easier
to dump all the filesystems from the old server and restore them
on the new server. If you're really replacing the machine, this
will guarantee you get every last detail right. If you try to
reconfigure a new installation to match an existing one, you're
almost certain to miss some mundane detail that you'll wish you
hadn't. With dump/restore, the only things you have to reconfigure
is *maybe* the network interface configuration in /etc/rc.conf.
(If you can't tolerate a bit of down time, you can do
do level 0s while the respository is active and then do level 1s
with the repository machine isolated from access. If you practice
a few times and have less than a few hundred committers I bet you
can do it with less than five minutes down without too much
difficulty.)
Just my $0.02. If I were doing it, that's what I'd do.
--
Alec.Kloss@oracle.com Oracle Middleware
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x432B9956