<?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: Backup/Restore approach when installing new RAID controller in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/backup-restore-approach-when-installing-new-raid-controller/m-p/4006665#M83873</link>
    <description>ECOs to current.  Initialize the target disk with a cluster size to a multiple of 16 and more than enough headers, and follow the directions for a disk-to-disk BACKUP /IMAGE /NOINIT transfer.  Enable Dynamic Volume Expansion.&lt;BR /&gt;&lt;BR /&gt;Here is what I have been classically recommending for the disk initialization process:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/193" target="_blank"&gt;http://64.223.189.234/node/193&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For the paranoid and given measured disk failure rates, I'd also redistribute the disks in the array, and scatter them across multiple controllers; I'd ensure the disks in the array are from different batches and different sources.  (RAID5 has a nasty habit of encountering a secondary spindle failure during the recovery from a failed spindle, and tipping over hard, for instance.)&lt;BR /&gt;&lt;BR /&gt;If you are unfamiliar or uncomfortable with OpenVMS system operations and/or BACKUP and/or sufficiently paranoid over your data, do consider enlisting formal assistance.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC&lt;BR /&gt;</description>
    <pubDate>Thu, 24 May 2007 11:26:19 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-05-24T11:26:19Z</dc:date>
    <item>
      <title>Backup/Restore approach when installing new RAID controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-restore-approach-when-installing-new-raid-controller/m-p/4006664#M83872</link>
      <description>We're running OpenVMS 8.3 on an Integrity rx3600.&lt;BR /&gt;&lt;BR /&gt;We have (8) 73GB SAS disks connected using the standard 8 port SAS HBA (347786-B21) that shipped with the rx3600. We're upgrading to the SmartArray P400 SAS controller because of hardware support for the RAID levels we want and because it has a battery-backed cache.&lt;BR /&gt;&lt;BR /&gt;Our current system volume is two drives using hardware RAID 1. Our other six drives are software RAID 1+0 using RAIDSERVER with shadowed drives. We use that for our data volumes, and we have multiple volumes created using initialize/size=.&lt;BR /&gt;&lt;BR /&gt;The new controller and disks will be setup using hardware RAID 10. I'm guessing OpenVMS will see this as a single device, and we're going to create multiple logical volumes.&lt;BR /&gt;&lt;BR /&gt;I'm looking at the following as a reference for doing the backup/restore:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/83final/ba322_90045/ape.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/83final/ba322_90045/ape.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;However, I'd appreciate any other guidance you might have for this type of situation.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 24 May 2007 10:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-restore-approach-when-installing-new-raid-controller/m-p/4006664#M83872</guid>
      <dc:creator>BoyeDav</dc:creator>
      <dc:date>2007-05-24T10:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: Backup/Restore approach when installing new RAID controller</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/backup-restore-approach-when-installing-new-raid-controller/m-p/4006665#M83873</link>
      <description>ECOs to current.  Initialize the target disk with a cluster size to a multiple of 16 and more than enough headers, and follow the directions for a disk-to-disk BACKUP /IMAGE /NOINIT transfer.  Enable Dynamic Volume Expansion.&lt;BR /&gt;&lt;BR /&gt;Here is what I have been classically recommending for the disk initialization process:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/193" target="_blank"&gt;http://64.223.189.234/node/193&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For the paranoid and given measured disk failure rates, I'd also redistribute the disks in the array, and scatter them across multiple controllers; I'd ensure the disks in the array are from different batches and different sources.  (RAID5 has a nasty habit of encountering a secondary spindle failure during the recovery from a failed spindle, and tipping over hard, for instance.)&lt;BR /&gt;&lt;BR /&gt;If you are unfamiliar or uncomfortable with OpenVMS system operations and/or BACKUP and/or sufficiently paranoid over your data, do consider enlisting formal assistance.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC&lt;BR /&gt;</description>
      <pubDate>Thu, 24 May 2007 11:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/backup-restore-approach-when-installing-new-raid-controller/m-p/4006665#M83873</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-05-24T11:26:19Z</dc:date>
    </item>
  </channel>
</rss>

