We're looking at ANS to solve a number of problems, including the
depolyment of a large-scale WWW-hosting service. With this in mind, I
have a few questions:
1. How does AFS 3.4 handle the loss of a database server? Can
read-only volumes continue to be read, as long as they are accessible?
What experience have users had with this? AFS read-only volumes could
solve some of our data availability requirements if the implementation is
robust.
2. Does anyone have experience with AFS 3.4 and Sun Online Disk Suite
under Solaris 2.4? High availability of rw volumes is important. How
about AFS and RAID?
3. What tools are out there to assist in AFS backups? We'd need to
backup a relatively large amount of data, and a tape jukebox solution
with minimal physical intervention would be ideal for the fileservers.
4. Has AFS 3.4 improved on the caching access model? That is to say,
does 3.4 still have the "one user, one workstation" access pattern in
mind? Would it be acceptable in terms of performance and reliability to
have the HTTP clients read off of read-only volumes, or would it be
preferable to simply use a utility like synctree to copy the read-only
data to local disk on each server? Disk is cheap, so I am leaning
towards the latter, unless someone can demonstrate otherwise.
Answers to these questions would help me considerably.
Thanks,
-brian
--
Brian W. Spolarich - ANS CO+RE Systems - [EMAIL PROTECTED] - (313)677-7311
"Ever been sued for patent infringement? You will!
And the company that will stick it to you? RSA." - Hal Finney
