http://en.wikipedia.org/wiki/RAID
remember..your most valuable data "is" your source-code. Put the O/S on it's own separate physical disk. I'd recommend against using a single drive and breaking it into separate logical drives. Put your source code on the most reliable disk setup you can. you can reinstall an o/s easily, the o/s partiton is "disposable", you can reformat & reinstall it without losing your data. my "ideal" world is... 6 "fast" (10k+ rpm) physical disks in the server. first 2 drives are a mirrored pair for the O/S last 4 drives are RAID5. however you're looking at a few grand just in disks there, so it all depends on what you have available. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Frans Bouma Sent: Friday, February 15, 2008 4:15 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] OT: Back up strategy > On Fri, 15 Feb 2008 09:37:22 +0100, Frans Bouma <[EMAIL PROTECTED]> wrote: > > > > What I am thinking is that our subversion server should be RAID 5 > > > > Subversion is just a bunch of files, [...] any backup software can > > pick them up, and restoring it is easy. > > Is it really that simple? Wouldn't you run into problems with the repo being > modified while xcopy (which falls under "any backup software") is reading > from it? > > Also, since there are many reports of svn repo backups becoming corrupted a > bit too easily, which has made many people test their backups automatically > or manually after a backup (see my previous post, for example), would you > attribute all these to ID-Ten-T Error? After your post I was curious (because why would there be ANY need for a script for this) and I checked the svn manual on repository backup. It has a full section about backing up a repository, the various different ways to do it etc.! (So OP should RTFM! ;) ) It indeed says that if you use xcopy-style backup you could get corrupted repositories if there's a transaction going on, as you copy the intermediate state of the db. This is similar to backing up a regular database file. So I stand corrected, it's best to use the build-in tool, which is a handy python script shipped with svn, which simply creates a working backup repository for you. We use the xcopy backup style at night as no-one checks in files at that time (the local backups) but I'll change our open source repository online's backup style to use the build in approach, thanks for that! :) > > you should have a disk-setup with mirrorring in raid, > > Well, OP already suggested RAID 5. Would you care to elaborate as to why a > mirroring scheme would be better? Any mirrorring scheme is best, I wasn't sure if raid 5 had any mirrorring, but it seems it does have (albeit it costs more disks), so indeed raid 5 is ok too, as long as there's a seemless way to insert a new disk and continue working. FB =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
