<?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 Cluster in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098020#M46607</link>
    <description>****&lt;BR /&gt;Next is purely based on deduction, based on what I know of setting upo a cluster. I've never tried this.&lt;BR /&gt;I may be wrong in SRM names but you'll grep the meaning if you take a look.&lt;BR /&gt;****&lt;BR /&gt;Having said this:&lt;BR /&gt;&lt;BR /&gt;Suppose DSA100 is your (cluster) disk, and your client boots from [SYS1], you will normally boot:&lt;BR /&gt;&lt;BR /&gt;os_flags = (1,0) --&amp;gt; will boot from SYS1&lt;BR /&gt;boot_dev = DSA100 --&amp;gt; will boot from DSA100&lt;BR /&gt;&lt;BR /&gt;so&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot&lt;BR /&gt;will actually be:&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot flags=(1,0) DSA100&lt;BR /&gt; &lt;BR /&gt;Now, make a image backup of this disk, assume DSA200.&lt;BR /&gt;&lt;BR /&gt;After creating DSA200 - the new systemdisk -&lt;BR /&gt;shutdown this client, and to test it:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot DSA200&lt;BR /&gt;&lt;BR /&gt;of change boot_dev to DSA200.&lt;BR /&gt;&lt;BR /&gt;You _may_ remove all [SYS?] directories but the one you want to boot from, and change the save one to [sys0] but you'll need to change OS-FLAGS accordingly.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 21 Oct 2003 07:17:54 GMT</pubDate>
    <dc:creator>Willem Grooters</dc:creator>
    <dc:date>2003-10-21T07:17:54Z</dc:date>
    <item>
      <title>VMS Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098018#M46605</link>
      <description>how can i give Client in a VMS Cluster a own systemdisk, without leaving the cluster?</description>
      <pubDate>Tue, 21 Oct 2003 02:24:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098018#M46605</guid>
      <dc:creator>Winfried Wetzel</dc:creator>
      <dc:date>2003-10-21T02:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098019#M46606</link>
      <description>If you with Client mean a Satellite node booting over the network this might help:&lt;BR /&gt; &lt;BR /&gt;A reboot is necessary to switch to local system disk, if you call that leaving the cluster.&lt;BR /&gt; &lt;BR /&gt;Just set Cluster parameters and copy sys$system:cluster_authorize.dat from the cluster. This file contains cluster group number and password that will make the node member of the cluster if cluster parameters are set.&lt;BR /&gt;Parameters could be set by using sys$manager:cluster_config.com or manually put them into sys$system:modparams.dat and run AUTOGEN.</description>
      <pubDate>Tue, 21 Oct 2003 04:12:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098019#M46606</guid>
      <dc:creator>Åge Rønning</dc:creator>
      <dc:date>2003-10-21T04:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098020#M46607</link>
      <description>****&lt;BR /&gt;Next is purely based on deduction, based on what I know of setting upo a cluster. I've never tried this.&lt;BR /&gt;I may be wrong in SRM names but you'll grep the meaning if you take a look.&lt;BR /&gt;****&lt;BR /&gt;Having said this:&lt;BR /&gt;&lt;BR /&gt;Suppose DSA100 is your (cluster) disk, and your client boots from [SYS1], you will normally boot:&lt;BR /&gt;&lt;BR /&gt;os_flags = (1,0) --&amp;gt; will boot from SYS1&lt;BR /&gt;boot_dev = DSA100 --&amp;gt; will boot from DSA100&lt;BR /&gt;&lt;BR /&gt;so&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot&lt;BR /&gt;will actually be:&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot flags=(1,0) DSA100&lt;BR /&gt; &lt;BR /&gt;Now, make a image backup of this disk, assume DSA200.&lt;BR /&gt;&lt;BR /&gt;After creating DSA200 - the new systemdisk -&lt;BR /&gt;shutdown this client, and to test it:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;boot DSA200&lt;BR /&gt;&lt;BR /&gt;of change boot_dev to DSA200.&lt;BR /&gt;&lt;BR /&gt;You _may_ remove all [SYS?] directories but the one you want to boot from, and change the save one to [sys0] but you'll need to change OS-FLAGS accordingly.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Oct 2003 07:17:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098020#M46607</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2003-10-21T07:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098021#M46608</link>
      <description>recent SYS$MANAGER:CLUSTER_CONFIG.COM have option to create duplicate system disk. &lt;BR /&gt;Or you do VMS installation on local disk in client, copy CLUSTER_AUTHORIZE.DAT to client system disk, set system params on new client disk (copy from previos system specific area).</description>
      <pubDate>Tue, 21 Oct 2003 11:02:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-cluster/m-p/3098021#M46608</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2003-10-21T11:02:52Z</dc:date>
    </item>
  </channel>
</rss>

