<?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: [Migration] Bad Sectors from Source Server in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187729#M120675</link>
    <description>I am part of the team that is doing the migration and yes, the old ML350 G1 has adaptec 2010s configured as raid-5.&lt;BR /&gt;&lt;BR /&gt;As to why it has bad sectors is a question only the raid/hdd firmware developers can answer as we have searched for similar occurences over the web and cannot find a solution.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 20 Jul 2009 07:49:19 GMT</pubDate>
    <dc:creator>artsky</dc:creator>
    <dc:date>2009-07-20T07:49:19Z</dc:date>
    <item>
      <title>[Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187720#M120666</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;We're having a hard time transfering our data from an old server to a new one (HP ProLiant ML530 G6). The old server is configured as Altiris Notification Server (with SQL server settings, etc.) and we would like to migrate everything from it. But the problem is, it has bad sectors. We do not want to manually configure everything from scratch.&lt;BR /&gt;&lt;BR /&gt;We've used HP Norton Ghost, Acronis TrueImage Echo and HP Insight Server but to no avail.&lt;BR /&gt;&lt;BR /&gt;What would you suggest?</description>
      <pubDate>Thu, 16 Jul 2009 10:00:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187720#M120666</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-16T10:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187721#M120667</link>
      <description>All these disk image copying products do just that, copy the entire image of a disk whether is contains data or not. Based on what you say the bad sectors are in areas where there is no file data is that correct? Otherwise you would have a problem whether you copy the disk image or copy all the files. Have you looked at "robocopy"? You still need to start with a new OS and at the end there will be some file copying needed as well. If the bad sectors have files on them then you really need to look at your backup tapes or rebuild the server environment from scratch.</description>
      <pubDate>Thu, 16 Jul 2009 10:41:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187721#M120667</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2009-07-16T10:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187722#M120668</link>
      <description>We're thinking of correcting the bad sectors first but we're running out of time.&lt;BR /&gt;&lt;BR /&gt;The three applications would not let us finish the image process because of the bad sectors.</description>
      <pubDate>Thu, 16 Jul 2009 23:30:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187722#M120668</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-16T23:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187723#M120669</link>
      <description>Now running HDD Regenerator on the old server and&lt;BR /&gt;&lt;BR /&gt;...wating to see good results</description>
      <pubDate>Fri, 17 Jul 2009 00:33:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187723#M120669</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-17T00:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187724#M120670</link>
      <description>Did you use ghost with switch's? You can ignore bad sectors.</description>
      <pubDate>Fri, 17 Jul 2009 03:49:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187724#M120670</guid>
      <dc:creator>MStoumba</dc:creator>
      <dc:date>2009-07-17T03:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187725#M120671</link>
      <description>We're able to identify the defetive drive and had replaced it.&lt;BR /&gt;&lt;BR /&gt;We will try Ghost with the switches as suggested.&lt;BR /&gt;&lt;BR /&gt;Any more?</description>
      <pubDate>Fri, 17 Jul 2009 06:24:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187725#M120671</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-17T06:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187726#M120672</link>
      <description>restore from last good backup and buy a server with hardware RAID next time!!!</description>
      <pubDate>Fri, 17 Jul 2009 07:23:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187726#M120672</guid>
      <dc:creator>u84823</dc:creator>
      <dc:date>2009-07-17T07:23:47Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187727#M120673</link>
      <description>Sorry but we have the HW RAID already</description>
      <pubDate>Mon, 20 Jul 2009 01:28:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187727#M120673</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-20T01:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187728#M120674</link>
      <description>If there is hardware RAID, why are you seeing bad sectors?</description>
      <pubDate>Mon, 20 Jul 2009 06:34:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187728#M120674</guid>
      <dc:creator>u84823</dc:creator>
      <dc:date>2009-07-20T06:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187729#M120675</link>
      <description>I am part of the team that is doing the migration and yes, the old ML350 G1 has adaptec 2010s configured as raid-5.&lt;BR /&gt;&lt;BR /&gt;As to why it has bad sectors is a question only the raid/hdd firmware developers can answer as we have searched for similar occurences over the web and cannot find a solution.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Jul 2009 07:49:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187729#M120675</guid>
      <dc:creator>artsky</dc:creator>
      <dc:date>2009-07-20T07:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187730#M120676</link>
      <description>See here: &lt;A href="http://h50146.www5.hp.com/lib/doc/manual/workstation/hp_workstation/c00218082.pdf" target="_blank"&gt;http://h50146.www5.hp.com/lib/doc/manual/workstation/hp_workstation/c00218082.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Might be worth enabling the background check and leaving the server at a startup prompt (i.e. the Windows boot menu) to ensure it's completely idle to enable the check to run.</description>
      <pubDate>Mon, 20 Jul 2009 08:21:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187730#M120676</guid>
      <dc:creator>u84823</dc:creator>
      <dc:date>2009-07-20T08:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187731#M120677</link>
      <description>Still working on it.&lt;BR /&gt;&lt;BR /&gt;just an update</description>
      <pubDate>Wed, 22 Jul 2009 00:07:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187731#M120677</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-22T00:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187732#M120678</link>
      <description>[Update]&lt;BR /&gt;&lt;BR /&gt;Working on with Norton Ghost again, now with switches for bypassing bad sectors.</description>
      <pubDate>Sun, 26 Jul 2009 23:22:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187732#M120678</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-26T23:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187733#M120679</link>
      <description>Worst comes to worst, we will be manually configuring Altiris Notification Server on the new machine.&lt;BR /&gt;&lt;BR /&gt;Is there a way to know or to have a "map" or a list of all configuration modules of the ANS since what we're going to do is to set up everything from scratch, parallel to the old server.&lt;BR /&gt;&lt;BR /&gt;Any advise?</description>
      <pubDate>Tue, 28 Jul 2009 08:01:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187733#M120679</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-07-28T08:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187734#M120680</link>
      <description>*bump*</description>
      <pubDate>Mon, 03 Aug 2009 04:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187734#M120680</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-08-03T04:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187735#M120681</link>
      <description>* bump *</description>
      <pubDate>Thu, 06 Aug 2009 01:48:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187735#M120681</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-08-06T01:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: [Migration] Bad Sectors from Source Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187736#M120682</link>
      <description>No solution found.</description>
      <pubDate>Fri, 07 Aug 2009 04:29:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/migration-bad-sectors-from-source-server/m-p/5187736#M120682</guid>
      <dc:creator>zeroseven0183</dc:creator>
      <dc:date>2009-08-07T04:29:37Z</dc:date>
    </item>
  </channel>
</rss>

