<?xml version="1.0" ?>
<!--
  RSS generated by Inquira Information Manager
-->
<rss version="2.0">
<channel>
<title><![CDATA[Hexagon Safety &amp; Infrastructure - Post to topic Disaster Recovery Failover]]></title>
<link>http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=home</link>
<description>Post to topic Disaster Recovery Failover</description>
<language>en</language>
<copyright>Copyright © 2002, 2012, Oracle and/or its affiliates. All rights reserved.</copyright>
<generator>Oracle Knowledge Information Manager</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
 

 
<item>
        <title><![CDATA[Disaster Recovery Failover]]></title>
        <link><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=507202533d666291015808cfc6be005e8f&actp=RSS]]></link>
        <description><![CDATA[<p>Just wondering what other utilities do for DR - especially around test failovers. Our DR failover including round trip connection testing is about an hour. During this time we don&#39;t have any OMS/dispatching available. This is an issue when we want to do an annual DR test - our operators aren&#39;t able to be without bring able to see a single line/seeing off-normals/creating tags, etc&nbsp;for that long. To be clear, this is not an issue with normal windows patching as we use Oracle FSFO and the Intergraph A/B failover so our users don&#39;t even see a blip. I&#39;m curious if our DR failover time is unusual and what feedback (or work arounds) you usually get from your control centers if you plan outages of an hour or more.</p>
]]></description>
        <pubDate>2016-10-31 20:53:44 Etc/GMT</pubDate>
        <guid isPermaLink="true"><![CDATA[http://support.hexagonsafetyinfrastructure.com/infocenter/index?page=forums&topic=507202533d666291015808cfc6be005e8f&actp=RSS]]></guid>
</item>
</channel>
</rss>
