<?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: Patch Installation in production Env in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468180#M360805</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;If you are running 11.23 or 11.31 and are lucky enough to have a spare disk, you could leverage DRD to shorten your maintenance window and provide a fail safe net.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-4030/5992-4030.pdf" target="_blank"&gt;http://docs.hp.com/en/5992-4030/5992-4030.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Tue, 28 Jul 2009 12:56:07 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2009-07-28T12:56:07Z</dc:date>
    <item>
      <title>Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468176#M360801</link>
      <description>What are the procedure for installing the patch in a production env??? Is there any other options rather than lvsplit and do patching?????</description>
      <pubDate>Tue, 28 Jul 2009 12:27:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468176#M360801</guid>
      <dc:creator>Anoop R Nath</dc:creator>
      <dc:date>2009-07-28T12:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468177#M360802</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;1) I do the install exactly as I would in production on a lab system.&lt;BR /&gt;&lt;BR /&gt;2) Ignite make_tape_recovery or make_net_recovery to avoid lvsplit, which I don't like to do.&lt;BR /&gt;&lt;BR /&gt;Item two creates a bootable, restorable installation. I would prior to relying on it do a test restore.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 28 Jul 2009 12:30:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468177#M360802</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-07-28T12:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468178#M360803</link>
      <description>My procedure is to first install on a sand box system, then the development system and finally on the production system.  In each case, I make an Ignite backup so that I can rebuild the system if necessary.  Splitting the mirrors would work, too, but I prefer to keep the mirrors and the protection they provide intact.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Tue, 28 Jul 2009 12:33:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468178#M360803</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2009-07-28T12:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468179#M360804</link>
      <description>Hi Anoop,&lt;BR /&gt;&lt;BR /&gt;Splitting all the mirror and merging is little complicated job. Best way would be take a ignite backup and install it.&lt;BR /&gt;&lt;BR /&gt;If you have physical access to the server, you can physically detach the mirror and install the patches.&lt;BR /&gt;&lt;BR /&gt;As Pete suggested, it is always recommanded to install it on development before deploy it on production.</description>
      <pubDate>Tue, 28 Jul 2009 12:43:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468179#M360804</guid>
      <dc:creator>Ganesan R</dc:creator>
      <dc:date>2009-07-28T12:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468180#M360805</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;If you are running 11.23 or 11.31 and are lucky enough to have a spare disk, you could leverage DRD to shorten your maintenance window and provide a fail safe net.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-4030/5992-4030.pdf" target="_blank"&gt;http://docs.hp.com/en/5992-4030/5992-4030.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 28 Jul 2009 12:56:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468180#M360805</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-07-28T12:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468181#M360806</link>
      <description>Dear all,&lt;BR /&gt;&lt;BR /&gt;Thanks for the comments. It is the server that have not updated the pathces since 2007. If the ignite is not restoring it will become a great problem.</description>
      <pubDate>Tue, 28 Jul 2009 13:56:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468181#M360806</guid>
      <dc:creator>Anoop R Nath</dc:creator>
      <dc:date>2009-07-28T13:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468182#M360807</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Before any major patch update, I do some kind of Ignite backup.&lt;BR /&gt;&lt;BR /&gt;That is a time tested, reliable way to back out should you have trouble. Its not the fastest, but it is a good way.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 28 Jul 2009 14:16:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468182#M360807</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-07-28T14:16:44Z</dc:date>
    </item>
    <item>
      <title>Re: Patch Installation in production Env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468183#M360808</link>
      <description>As everyone has mentioned, the first start in patching is to use DRD and/or IUX to make sure you can return to where you started.  If you split a mirror I would do so to enable DRD.  If you cannot run in production without a mirror I would use IUX.  If possible I would use both.&lt;BR /&gt;&lt;BR /&gt;You have not mentioned how you were going to select your patches.  If you do not have a support contract that provides for patch assessment I would recommend trying the Software Assistant (SWA) tool.  It is available from &lt;A href="https://www.hp.com/go/swa." target="_blank"&gt;https://www.hp.com/go/swa.&lt;/A&gt;</description>
      <pubDate>Tue, 28 Jul 2009 22:26:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/patch-installation-in-production-env/m-p/4468183#M360808</guid>
      <dc:creator>Bob E Campbell</dc:creator>
      <dc:date>2009-07-28T22:26:46Z</dc:date>
    </item>
  </channel>
</rss>

