<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Reload</title>
	<atom:link href="http://blogs.appliedconsultancy.com/reload/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://blogs.appliedconsultancy.com/reload</link>
	<description>Thoughts, comments and ideas from ACS Staff</description>
	<lastBuildDate>Fri, 14 Mar 2008 15:59:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on N&amp;S Alert: Server Failure Notice by Darren Waller</title>
		<link>http://blogs.appliedconsultancy.com/reload/?p=36&#038;cpage=1#comment-48</link>
		<dc:creator>Darren Waller</dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.appliedconsultancy.com/reload/?p=36#comment-48</guid>
		<description>All customer services have been restored folowing this server error.  If any customers are still experiencing problems, please report them via our support site in the usual way as these may be unrelated to the server issues.

Over the last 3 months, ACS has been implementing a program to upgrade of all our ISP servers and this server was to be one of the last to be replaced.  It had been planned to move all customers off the server and retire it in the near future, but we had to bring these plans forwards following the server un-recoverable hardware fault.

Most customer services were restored within 4 hours of the server failure thanks to our policy of having redundant capacity on our backup servers, but a few customers (typically those for whom we do not control domain name nameservers) suffered longer outages for which we apologise and thank clients for their patience.  It does, unfortunately, take a finite amount of time (24-48 hours) for nameserver changes to filter though the whole of the internet.

All customer websites and email services are now hosted on our new generation of servers which have enhanced efficiency, redundancy and monitoring designed-in.  Although the server failure we experienced was an unusual occurence (infact, it has happened to only 3 web servers across our network in the last 10 years), servers, like all other PCs do occasionally suffer such problems, but our policy of continually upgrading servers and building-in resilience does try to reduce the risks of this happening.

Thanks once again for the patience of all those affected.</description>
		<content:encoded><![CDATA[<p>All customer services have been restored folowing this server error.  If any customers are still experiencing problems, please report them via our support site in the usual way as these may be unrelated to the server issues.</p>
<p>Over the last 3 months, ACS has been implementing a program to upgrade of all our ISP servers and this server was to be one of the last to be replaced.  It had been planned to move all customers off the server and retire it in the near future, but we had to bring these plans forwards following the server un-recoverable hardware fault.</p>
<p>Most customer services were restored within 4 hours of the server failure thanks to our policy of having redundant capacity on our backup servers, but a few customers (typically those for whom we do not control domain name nameservers) suffered longer outages for which we apologise and thank clients for their patience.  It does, unfortunately, take a finite amount of time (24-48 hours) for nameserver changes to filter though the whole of the internet.</p>
<p>All customer websites and email services are now hosted on our new generation of servers which have enhanced efficiency, redundancy and monitoring designed-in.  Although the server failure we experienced was an unusual occurence (infact, it has happened to only 3 web servers across our network in the last 10 years), servers, like all other PCs do occasionally suffer such problems, but our policy of continually upgrading servers and building-in resilience does try to reduce the risks of this happening.</p>
<p>Thanks once again for the patience of all those affected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N&amp;S Alert: Server Failure Notice by Darren Waller</title>
		<link>http://blogs.appliedconsultancy.com/reload/?p=36&#038;cpage=1#comment-46</link>
		<dc:creator>Darren Waller</dc:creator>
		<pubDate>Tue, 11 Mar 2008 22:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.appliedconsultancy.com/reload/?p=36#comment-46</guid>
		<description>A number of the affected websites are now live again, leaving only a small number plus email services to be re-connected in the morning.

We apologise for the disruption caused and can assure you that we are ensuring that our data centre treats the replacement of the server as a priority (even though the majority of customers have been temporarily moved off it onto one of our fallback servers).

If you need further information or want an update, please do not telephone us (as all engineers will be busy getitng sevices resumed).  Please visit the Our Status link at our support site https://support.namesandspace.net instead.  The latest updates will always be posted her first.</description>
		<content:encoded><![CDATA[<p>A number of the affected websites are now live again, leaving only a small number plus email services to be re-connected in the morning.</p>
<p>We apologise for the disruption caused and can assure you that we are ensuring that our data centre treats the replacement of the server as a priority (even though the majority of customers have been temporarily moved off it onto one of our fallback servers).</p>
<p>If you need further information or want an update, please do not telephone us (as all engineers will be busy getitng sevices resumed).  Please visit the Our Status link at our support site <a href="https://support.namesandspace.net" rel="nofollow">https://support.namesandspace.net</a> instead.  The latest updates will always be posted her first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sometimes it goes wrong for us too. by darrenwaller</title>
		<link>http://blogs.appliedconsultancy.com/reload/?p=13&#038;cpage=1#comment-2</link>
		<dc:creator>darrenwaller</dc:creator>
		<pubDate>Mon, 11 Jun 2007 23:28:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.appliedconsultancy.com/reload/?p=13#comment-2</guid>
		<description>It&#039;s worth noting that, despite our internal email being down, we were still receiving support messages via our permanent back-up system (onto a blackberry running on someone else&#039;s network).  This is one of a number of permanent and hot-standby systems we have in place to allow us to continue business in the event of a minor hiccup or something much more devastating happening.  

We have a formal disaster recovery plan covering eventualities such as this, right up to the loss of premises and key staff members - I would advise all customers, regardless of their size to consider having their own.  

The easiest way to approach this is to consider what would be the most devastating thing that could effect your business network (Loss of a server ?  A denial-of-service attack ? An ex-staff member selling your secrets to a competitor ?) and then double it.  Then make sure you have systems in place to ideally prevent it happening in the first place or to deal with it if it does.  

If you need help with this, contact our consultancy department who offer fixed-price Disaster recovery/Business Continuity consultancy services for the smaller business and more bespoke services for our larger customers.</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth noting that, despite our internal email being down, we were still receiving support messages via our permanent back-up system (onto a blackberry running on someone else&#8217;s network).  This is one of a number of permanent and hot-standby systems we have in place to allow us to continue business in the event of a minor hiccup or something much more devastating happening.  </p>
<p>We have a formal disaster recovery plan covering eventualities such as this, right up to the loss of premises and key staff members &#8211; I would advise all customers, regardless of their size to consider having their own.  </p>
<p>The easiest way to approach this is to consider what would be the most devastating thing that could effect your business network (Loss of a server ?  A denial-of-service attack ? An ex-staff member selling your secrets to a competitor ?) and then double it.  Then make sure you have systems in place to ideally prevent it happening in the first place or to deal with it if it does.  </p>
<p>If you need help with this, contact our consultancy department who offer fixed-price Disaster recovery/Business Continuity consultancy services for the smaller business and more bespoke services for our larger customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
