<?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: VMS Patching on 5 Node CLuster in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173768#M89236</link>
    <description>"It depends."&lt;BR /&gt;&lt;BR /&gt;For many cases, after reading the ECO kit release notes and here assuming that the cluster can continue to operate with one node down (at a time), the patch process is typically this: &lt;BR /&gt;&lt;BR /&gt;perform a BACKUP /IMAGE of the system disk or otherwise ensure a path back out should the installation or the testing of the patch fail.  &lt;BR /&gt;&lt;BR /&gt;Ensure the prerequisites are installed.  &lt;BR /&gt;&lt;BR /&gt;Install the ECO.&lt;BR /&gt;&lt;BR /&gt;Reboot.&lt;BR /&gt;&lt;BR /&gt;Verify correct operations, isolating the node as required.&lt;BR /&gt;&lt;BR /&gt;Repeat on the next node.&lt;BR /&gt;&lt;BR /&gt;==&lt;BR /&gt;&lt;BR /&gt;The BACKUP /IMAGE of the system disk is the path out if there are "any problems faced" that might be specific to your site.&lt;BR /&gt;&lt;BR /&gt;==&lt;BR /&gt;&lt;BR /&gt;In some environments, the above procedure and the above sequence is considered completely wrong and not best practices, and you cannot and should not test in the production cluster; you can and should test off-line, then roll the production cluster forward.&lt;BR /&gt;</description>
    <pubDate>Fri, 04 Apr 2008 04:33:01 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2008-04-04T04:33:01Z</dc:date>
    <item>
      <title>VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173767#M89235</link>
      <description>Hi Friends,&lt;BR /&gt;&lt;BR /&gt;I am installing patches on a 5-node VMS 7.3-2 cluster, each node boots from its own disk. Just want to check on the best practises for installing patches for LAVC cluster members. I am planning to take one node offline from cluster and install the patches, test the node and put it back in the cluster. I will be installing the VMS_UPDATE_V15.00, PCSI v4.0 and other new ECO kits released in Mar'08, has anybody installed these kits, any problems faced ?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Regds,&lt;BR /&gt;Sanjay&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Apr 2008 03:01:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173767#M89235</guid>
      <dc:creator>SANJAY MUNDHRA</dc:creator>
      <dc:date>2008-04-04T03:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173768#M89236</link>
      <description>"It depends."&lt;BR /&gt;&lt;BR /&gt;For many cases, after reading the ECO kit release notes and here assuming that the cluster can continue to operate with one node down (at a time), the patch process is typically this: &lt;BR /&gt;&lt;BR /&gt;perform a BACKUP /IMAGE of the system disk or otherwise ensure a path back out should the installation or the testing of the patch fail.  &lt;BR /&gt;&lt;BR /&gt;Ensure the prerequisites are installed.  &lt;BR /&gt;&lt;BR /&gt;Install the ECO.&lt;BR /&gt;&lt;BR /&gt;Reboot.&lt;BR /&gt;&lt;BR /&gt;Verify correct operations, isolating the node as required.&lt;BR /&gt;&lt;BR /&gt;Repeat on the next node.&lt;BR /&gt;&lt;BR /&gt;==&lt;BR /&gt;&lt;BR /&gt;The BACKUP /IMAGE of the system disk is the path out if there are "any problems faced" that might be specific to your site.&lt;BR /&gt;&lt;BR /&gt;==&lt;BR /&gt;&lt;BR /&gt;In some environments, the above procedure and the above sequence is considered completely wrong and not best practices, and you cannot and should not test in the production cluster; you can and should test off-line, then roll the production cluster forward.&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Apr 2008 04:33:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173768#M89236</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-04-04T04:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173769#M89237</link>
      <description>Sanjay,&lt;BR /&gt;&lt;BR /&gt;Hoff pretty much said it all.&lt;BR /&gt;&lt;BR /&gt;Make REAL sure you have a GOOD system disk backup!&lt;BR /&gt;Since you are shutting down anyway: just make that a verified standalone backup.&lt;BR /&gt;&lt;BR /&gt;... and you should really apply the patches to an independent test system, and test thoroughly, before doing the production environment.&lt;BR /&gt;&lt;BR /&gt;And: _NO_ hurry. Do it at ease, in a quiet period. Take your time. Check and double-check. Preferable do it with TWO persons, and for EACH command, let the typed commands be checked by the other person before hitting &lt;RETURN&gt;. Prudence takes a cost, but it DOES pay off to avoid the trivial errors!&lt;BR /&gt;&lt;BR /&gt;Success.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;&lt;BR /&gt;&lt;/RETURN&gt;</description>
      <pubDate>Fri, 04 Apr 2008 06:00:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173769#M89237</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2008-04-04T06:00:03Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173770#M89238</link>
      <description>Sanjay,&lt;BR /&gt;&lt;BR /&gt;be aware that there might be an issue with VMS732_SYS_v15 - first reported against 8.2/8.3 kits, but now Rick Dyson suggests that the same issue occurs in 7.3-2&lt;BR /&gt;&lt;BR /&gt;see:&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1218070" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1218070&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Duncan&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Apr 2008 07:32:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173770#M89238</guid>
      <dc:creator>Duncan Morris</dc:creator>
      <dc:date>2008-04-04T07:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173771#M89239</link>
      <description>Sanjay,&lt;BR /&gt;&lt;BR /&gt;In addition to the other comments, it is wise to remember that problems can occur differently on different nodes.&lt;BR /&gt;&lt;BR /&gt;The mere fact that an upgrade has been successful on one node is no guarantee that the update will be without side effect on a different node.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Fri, 04 Apr 2008 08:34:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173771#M89239</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2008-04-04T08:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Patching on 5 Node CLuster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173772#M89240</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks very much for the responses. Customer has confirmed that the patches have been tested in their UAT (single node). I will be taking image backup on tape and adding 3rd volume shadow member and then breaking it for having a safe copy of current OS.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Sanjay</description>
      <pubDate>Sun, 06 Apr 2008 06:36:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-patching-on-5-node-cluster/m-p/4173772#M89240</guid>
      <dc:creator>SANJAY MUNDHRA</dc:creator>
      <dc:date>2008-04-06T06:36:26Z</dc:date>
    </item>
  </channel>
</rss>

