On Thu, 25 Apr 2002, Les Mikesell wrote:

> > From: D. Hageman [mailto:[EMAIL PROTECTED]]
> > Subject: Re: File::Redundant
> > 
> > Interesting ... not sure if implementing this in this fashion would be 
> > worth the overhead.  If such a need exists I would imagine that 
> > would have 
> > choosen a more appropriate OS level solution.  Think OpenAFS.
> 
> This is off-topic of course, but you often don't get
> unbiased opinions from the specific list.  Does anyone
> have success or horror stories about AFS in a distributed
> production site?  Oddly enough the idea of using it
> just came up in my company a few days ago to publish
> some large data sets that change once daily to several
> locations.  I'm pushing a lot of stuff around now with
> rsync which works and is very efficient, but the ability
> to move the source volumes around transparently and keep
> backup snapshots is attractive. 

I haven't personally used AFS on a large scale.  I have setup several 
small tests beds with it to test the feasibility of using it at my job.  I 
work for the EECS Department at the Universty of Kansas, so we have a 
fairly large hetergenous computer environment.  My tests showed that at 
the time, support for Windows wasn't quite up to par yet.  The *nix code 
base performed quite well.  I say at the time because since then, the 
OpenAFS project has pushed out several more versions of the code base so 
support might be better.  I did have the pleasure of talking with a guy 
from the University of Missouri that was telling me they have AFS deployed 
on a very large scale there and were very pleased with it (I think they 
were using the commercial version to support the Windows side).  AFS 
definately has some promise and if it weren't for the hetergenous issues 
(and a few non-technical issues) we would be using it here.

To avoid being completely off topic - I should point out that AFS modules 
exist for Perl and a mod_afs exist for Apache. ;-)

-- 
//========================================================\\
||  D. Hageman                    <[EMAIL PROTECTED]>  ||
\\========================================================//

Reply via email to