<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"> We had an incident where our library server was not communicating with our application servers for a time. Users were all logging into the library server and all seemed fine until the library server got overloaded, we saw
what was happening, and got all servers communicating again.<o:p></o:p></p>
<p class="MsoNormal"> During the time when activity was only happening on the library server, some course problems were edited and republished. When we re-connected all servers and students were then re-routed to the application servers, we learned
that the students were not seeing the updated problem versions. The updated problems were not pushed to the application servers as they would have been during normal circumstances.<o:p></o:p></p>
<p class="MsoNormal"> We found that if the problems were re-published, once all servers were connected, then the version push happened as it should. To rectify our issue, we went in and manually republished any problems that were edited during
the “dark” period.<o:p></o:p></p>
<p class="MsoNormal"> Is there an easier way to handle this situation if it should happen again? Is there a way to “refresh” a whole course, re-publishing any content currently used in that course? Could we have just copied the affected .problem
and .problem.meta files from the library server over to the application servers?<o:p></o:p></p>
<p class="MsoNormal"> The authorspace directories that we pull from have unpublished resources in them (works in progress), so republishing at the directory level wouldn’t work for us. Any advice or ideas would be appreciated. We don’t expect
this to happen again, but it would be nice to have a plan in place in case it does.<o:p></o:p></p>
<p class="MsoNormal"> Thanks,<o:p></o:p></p>
<p class="MsoNormal"> Joyce Young<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black">Joyce Young<br>
Programmer/Analyst<br>
ITAS - Student Systems Competency Center <br>
Purdue University<br>
3495 Kent Avenue</span><span style="font-size:10.0pt;color:#1F497D">,</span><span style="font-size:10.0pt;color:black"> Suite 100<br>
West Lafayette, IN 47906<br>
Phone: (765) 427-6340<br>
Fax: (765) 464-2233 <br>
Campus Mail: ROSS<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"><a href="mailto:young257@purdue.edu"><span style="color:blue">young257@purdue.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>