<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DR SPECS in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dr-specs/m-p/4662233#M615566</link>
    <description>For designing any DR site two points are important i.e. how long can you afford to wait to recover, and how much data can you afford to lose.&lt;BR /&gt;</description>
    <pubDate>Fri, 16 Jul 2010 09:24:17 GMT</pubDate>
    <dc:creator>VVS</dc:creator>
    <dc:date>2010-07-16T09:24:17Z</dc:date>
    <item>
      <title>DR SPECS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dr-specs/m-p/4662232#M615565</link>
      <description>Hai,&lt;BR /&gt;&lt;BR /&gt;Before we setup a DR at client site what are the specs we need to know from client side assuming they are going for oracle data guard for DR and HP-UX as their OS immediate reply would be helpful.&lt;BR /&gt;&lt;BR /&gt;-regards&lt;BR /&gt;Srinivas Bitra</description>
      <pubDate>Fri, 16 Jul 2010 07:24:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dr-specs/m-p/4662232#M615565</guid>
      <dc:creator>Nivas_1</dc:creator>
      <dc:date>2010-07-16T07:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: DR SPECS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dr-specs/m-p/4662233#M615566</link>
      <description>For designing any DR site two points are important i.e. how long can you afford to wait to recover, and how much data can you afford to lose.&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Jul 2010 09:24:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dr-specs/m-p/4662233#M615566</guid>
      <dc:creator>VVS</dc:creator>
      <dc:date>2010-07-16T09:24:17Z</dc:date>
    </item>
  </channel>
</rss>

