[OpenAFS] Replication on User Vol

Tue, 24 Apr 2007 21:45:42 +0800

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78676.DA175278
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi,

I understand that replication is not suitable for volumes that change
frequently like user volumes. Does this means that if I have the user
volumes spread across many fileservers and if one of the fileserver
dies, users whose data is in that fileserver will have no access to it
until I recover from backup? Is there a recomended way to maintain large
user volumes with any downtime? For example how does a university
maintain these large user volumes for her students?

tks,

melvin

------_=_NextPart_001_01C78676.DA175278
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>I understand that replication is not suitable for =
volumes that
change frequently like user volumes. Does this means that if I have the =
user
volumes spread across many fileservers and if one of the fileserver =
dies, users
whose data is in that fileserver will have no access to it until I =
recover from
backup? Is there a recomended way to maintain large user volumes with =
any
downtime? For example how does a university maintain these large user =
volumes
for her students?<o:p></o:p></p>

<p class=3DMsoNormal>tks,<o:p></o:p></p>

<p class=3DMsoNormal>melvin<o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C78676.DA175278--