<?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: Moving SANS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6907495#M28999</link>
    <description>&lt;P&gt;There is also a feature that let's you copy EVA to 3PAR at the storage level. &amp;nbsp;You get a temporary license with the 3Par when new to do this.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Oct 2016 20:44:00 GMT</pubDate>
    <dc:creator>Shael Richmond</dc:creator>
    <dc:date>2016-10-13T20:44:00Z</dc:date>
    <item>
      <title>Moving SANS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906866#M28995</link>
      <description>&lt;P&gt;-openvms 8.3 FOE (therefore no shadow licence) on rx2660&lt;/P&gt;&lt;P&gt;- boots from SAN (EVA)&lt;/P&gt;&lt;P&gt;Need to move this to a 3PAR SAN.&lt;/P&gt;&lt;P&gt;Just looking for advice on how to actually do this. My initial thought is this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;install a minium vms environment on a 3PAR LUN using &lt;A href="http://h41379.www4.hpe.com/doc/83final/ba322_90045/apes06.html" target="_blank"&gt;http://h41379.www4.hpe.com/doc/83final/ba322_90045/apes06.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;boot from this temporarily&lt;/P&gt;&lt;P&gt;copy ORIGINAL system disk to a brand new 3PAR lun&lt;/P&gt;&lt;P&gt;change to boot from the copied LUN&lt;/P&gt;&lt;P&gt;Thoughts appreciated....?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2016 09:16:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906866#M28995</guid>
      <dc:creator>Bazza77</dc:creator>
      <dc:date>2016-10-12T09:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SANS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906869#M28996</link>
      <description>&lt;P&gt;Find and read the&amp;nbsp; HP 3PAR OpenVMS Implementation Guide&lt;/P&gt;&lt;P&gt;&lt;A href="http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04739526-1.pdf" target="_blank"&gt;http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04739526-1.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;From experience:&lt;/P&gt;&lt;P&gt;- you need OpenVMS I84 V8.3-1H1 to access 3PAR LUNs&lt;/P&gt;&lt;P&gt;- OpenVMS I64 V8.3-1H1 (un-patched DVD) can access/read/write 3PAR LUNs&lt;/P&gt;&lt;P&gt;- OpenVMS I64 V8.3-1H1 (un-patched) can NOT boot from 3PAR LUN (incurs INCONSTATE bugcheck)&lt;/P&gt;&lt;P&gt;- you&amp;nbsp;should/must install all available patches for V8.3-1H1&lt;/P&gt;&lt;P&gt;Volker.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2016 09:32:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906869#M28996</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2016-10-12T09:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SANS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906907#M28997</link>
      <description>&lt;P&gt;Follow the advise of Volker first. &amp;nbsp;Once the minimum system is booted from the 3PAR, copy all of the drives (OS and data) using backup in image mode to the 3PAR. &amp;nbsp;In this fashion, you have both the new setup and a "backout" set should something go wrong.&lt;/P&gt;&lt;P&gt;I have worked with many clients that have done this with much success. &amp;nbsp;The reason for the backout set is that quite often, there are disk references that show up on the new SAN that were not known at the time. &amp;nbsp;The backout option allows for the production system to continue while the problems are found and fixed. &amp;nbsp;Besides, its always a good practice to have the old setup available in case of major problems.&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2016 12:09:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906907#M28997</guid>
      <dc:creator>abrsvc</dc:creator>
      <dc:date>2016-10-12T12:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SANS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906947#M28998</link>
      <description>&lt;P&gt;Thank you the replies, seems section 7 has a fully worked example.&lt;/P&gt;&lt;P&gt;I will read up on vms patching, I do not think the system has been touched for a long while.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2016 14:02:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6906947#M28998</guid>
      <dc:creator>Bazza77</dc:creator>
      <dc:date>2016-10-12T14:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SANS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6907495#M28999</link>
      <description>&lt;P&gt;There is also a feature that let's you copy EVA to 3PAR at the storage level. &amp;nbsp;You get a temporary license with the 3Par when new to do this.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2016 20:44:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/moving-sans/m-p/6907495#M28999</guid>
      <dc:creator>Shael Richmond</dc:creator>
      <dc:date>2016-10-13T20:44:00Z</dc:date>
    </item>
  </channel>
</rss>

