<?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: Windows 2003 server - Production in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576118#M2011</link>
    <description>Hi Srinivasan,&lt;BR /&gt;your question is too wide to give a good answer.&lt;BR /&gt;If you have a production server, I guess you have also a development server. I think your company can buy two mirrored disk for OS. In my mind, the solution is:&lt;BR /&gt;a) Two mirrored disk for OS&lt;BR /&gt;b) Raid disk for your data&lt;BR /&gt;If your company budget help you, you can use a raid for both server and clustered solution (two production servers).&lt;BR /&gt;For limited budget you can use mirrored disks for data.&lt;BR /&gt; &lt;BR /&gt;Backup every day, full backup one time for week at least, incremental backup every day.&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
    <pubDate>Sun, 10 Jul 2005 01:53:37 GMT</pubDate>
    <dc:creator>Antoniov.</dc:creator>
    <dc:date>2005-07-10T01:53:37Z</dc:date>
    <item>
      <title>Windows 2003 server - Production</title>
      <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576114#M2007</link>
      <description>We have a production server on which i have installed some application. Operating systems is windows 2003 server standard edition. What would be best option to have a DR plan to restore the data &amp;amp; get the server back to operation, apart from the normal backup.&lt;BR /&gt;&lt;BR /&gt;Please suggest.&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;Srinivasan&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Jul 2005 04:20:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576114#M2007</guid>
      <dc:creator>Srinivasan Krishnamurth</dc:creator>
      <dc:date>2005-07-05T04:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 2003 server - Production</title>
      <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576115#M2008</link>
      <description>You must create an ASR backup with ntbackup at least. The ASR backup restore a windows installation, but eliminates all data in the system partition.&lt;BR /&gt;&lt;BR /&gt;You sould use a disk image software to create a backup of your server installation and to reduce downtime during a disaster.&lt;BR /&gt;&lt;BR /&gt;HP provides Open View Data Protector One button disaster recovery.</description>
      <pubDate>Tue, 05 Jul 2005 09:50:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576115#M2008</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-07-05T09:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 2003 server - Production</title>
      <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576116#M2009</link>
      <description>Depending on how important the server is to business and if you have hardware raid possibility with hotswap disks:&lt;BR /&gt;&lt;BR /&gt;Some customers buy an extra disk, mirror the OS-disk, takes the extra disk out and stores it a safe place. This is only a good solution if the OS-dis contains mostly static data.&lt;BR /&gt;&lt;BR /&gt;For database servers there are better methods of log-shipping  etc to keep a (remote) standby server synchronized for quick switch over.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune</description>
      <pubDate>Wed, 06 Jul 2005 03:07:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576116#M2009</guid>
      <dc:creator>Rune J. Winje</dc:creator>
      <dc:date>2005-07-06T03:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 2003 server - Production</title>
      <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576117#M2010</link>
      <description>When you start discussing DR there are several considerations that have to be considered.  First, what is the cost to the business whenever the machine application is not available?  And next, what is the cost associated with any lost data?  These are both questions that the end user (real owner) of the application has to determine before you can adequately respond with recommendations to improve the long term availability of the application. &lt;BR /&gt;&lt;BR /&gt;I noticed in particular that you mentioned the term 'restore the data' in your question.  My guess is that you may be talking about the stored data that the application is producing.  More often than not this data is being stored within some sort of database.  These days most databases have some sort of transaction logging facility available.  Replicating this data is often the first defense in a DR scenario when this data is critical.  &lt;BR /&gt;&lt;BR /&gt;There are many hardware and networking solutions.  Some DR solutions can have the application back in seconds and others can involve many hours.  The range of costs associated with the various methods vary greatly.  So it is a matter of the application owner determining the risks and costs associated with the loss of this application and the willingness of the organization to expend resources to limit the risk.</description>
      <pubDate>Sat, 09 Jul 2005 21:28:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576117#M2010</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2005-07-09T21:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 2003 server - Production</title>
      <link>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576118#M2011</link>
      <description>Hi Srinivasan,&lt;BR /&gt;your question is too wide to give a good answer.&lt;BR /&gt;If you have a production server, I guess you have also a development server. I think your company can buy two mirrored disk for OS. In my mind, the solution is:&lt;BR /&gt;a) Two mirrored disk for OS&lt;BR /&gt;b) Raid disk for your data&lt;BR /&gt;If your company budget help you, you can use a raid for both server and clustered solution (two production servers).&lt;BR /&gt;For limited budget you can use mirrored disks for data.&lt;BR /&gt; &lt;BR /&gt;Backup every day, full backup one time for week at least, incremental backup every day.&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Sun, 10 Jul 2005 01:53:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/windows-2003-server-production/m-p/3576118#M2011</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-07-10T01:53:37Z</dc:date>
    </item>
  </channel>
</rss>

