Just realized, nightly backups of the repositories are probably a bad
idea because of the whole inconsistent state thing.
I'm guessing what I *should* be doing here is keeping the repositories
local and building a script to hotcopy each repository to the NAS on a
routine basis, and then having the NAS back *that* up to an external
drive.
Am I on the right track here? Perhaps you guys could share some of
your ideas for backups and svn?
On Oct 10, 4:34 pm, "Ian M." <i..._at_auricom.com> wrote:
> I just did a hotcopy to the local drive and I'll be switching the repo
> path and testing some big transfers this weekend to see if performance
> improves.
>
> The issue with leaving the repo on the local drive is that the NAS is
> a RAID and already backups to an attached usb disk that runs nightly.
> The repository itself is 10GB at this point and represents about 6
> months of work so the redundancy/backup is pretty important. There is
> probably some combination of internal mirrored drives and backup
> software that could be put in place to fix this IF this that turns out
> to be the issue but ideally I'd like to continue using the NAS for
> this.
>
> On Oct 10, 3:55 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
>
>
>
> > Ian M. wrote:
> > > Thanks for the response Andy.
>
> > > As for the hangups:
>
> > > I just checked the performance (its a Win 2003 server box) and it
> > > pages/sec shoots to over a thousand when doing an update/commit, but
> > > it still maintains a great deal of free ram (of an available 4GB). I'm
> > > not really sure how to gauge the pages/sec in terms of what is good
> > > and bad (especially after reading thishttp://support.microsoft.com/kb/139609
> > > ), but it does seem to max out the performance graph.
>
> > > One thing I should mention is that the Subversion runs on our server
> > > here but the repository location is actually a network path to a
> > > folder on the NAS. Would this potentially cause an issue? Its
> > > difficult for me to test against this as we only have a single
> > > mirrored drive in the server for the OS to run on and not enough space
> > > to hotcopy a repository there for testing.
>
> > Can't you put the repository on the local harddrive of the server?
>
> > > As for the poor speeds:
>
> > > I get about 60Mbps transferring files directly to the NAS that stores
> > > the repositories (Gigabit network, but my laptop has 100Mb onboard),
> > > so I'm lead to believe that I should be getting better speeds than 3Mb
> > > when using local hostnames with checkouts. Of course this may relate
> > > back to the performance issue.
>
> > When accessing the repository, Subversion requires a *lot* of file
> > accesses (the repository is basically a database, consisting of hundreds
> > of files). That's why you will never get the full speed (except when
> > transferring a very big file): for every file that svn accesses, there's
> > a big overhead and delay because of the whole authentication/access
> > control over the network (your NAS has to check whether the server
> > process is even allowed to access those files).
>
> > Stefan
>
> > --
> > ___
> > oo // \\ "De Chelonian Mobile"
> > (_,\/ \_/ \ TortoiseSVN
> > \ \_/_\_/> The coolest Interface to (Sub)Version Control
> > /_/ \_\ http://tortoisesvn.net
>
> > signature.asc
> > < 1KViewDownload
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr..._at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-h..._at_tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-10 22:42:58 CEST