<?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: mirror systems in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164834#M456916</link>
    <description>And that is one fine hat there, Ron.  Clothes do make the man, they say!  Enjoy it and keep on working at it - there's more to come.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete&lt;BR /&gt;&lt;BR /&gt;No points please</description>
    <pubDate>Thu, 19 Mar 2009 13:10:43 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2009-03-19T13:10:43Z</dc:date>
    <item>
      <title>mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164828#M456910</link>
      <description>Hello!!&lt;BR /&gt;&lt;BR /&gt;Our current environment consists if a production server, (rp8420 11.23,) and a DR server offsite, (rp8420 11.23.)  As of now, we replicate the database via the application's shadow procedure, but have to keep up on the OS manually, (copy /home, /etc/passwd, etc.)&lt;BR /&gt;&lt;BR /&gt;My question, is there a cost-effective solution to mirror the OS to the DR site?&lt;BR /&gt;&lt;BR /&gt;If you need anymore information, please ask.&lt;BR /&gt;&lt;BR /&gt;Thank you!!!</description>
      <pubDate>Thu, 19 Mar 2009 10:33:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164828#M456910</guid>
      <dc:creator>Ron Irving</dc:creator>
      <dc:date>2009-03-19T10:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164829#M456911</link>
      <description>Ron,&lt;BR /&gt;&lt;BR /&gt;I'll be very interested to see what sort of response you get as we have a nearly identical situation.  At his point I use cron nightly to keep key OS files in sync, much as you do.  I believe this might be a good application for rsync but have never gotten around to trying it.&lt;BR /&gt;&lt;BR /&gt;It would be ideal if we could do remote mirroring!  Hmmm, I wonder if Dynamic Root Disk would offer anything - I'll have to look into that but I doubt it.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 19 Mar 2009 10:39:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164829#M456911</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2009-03-19T10:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164830#M456912</link>
      <description>Thanks Pete.  I tried to get an interest in Sevice Guard, but they weren't interested in paying for it.  Go figure.  We're looking at rsync right now.  Can you share your cron scripts?  That may be a short-term fix.&lt;BR /&gt;&lt;BR /&gt;Thanx!!</description>
      <pubDate>Thu, 19 Mar 2009 10:51:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164830#M456912</guid>
      <dc:creator>Ron Irving</dc:creator>
      <dc:date>2009-03-19T10:51:19Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164831#M456913</link>
      <description>Ron,&lt;BR /&gt;&lt;BR /&gt;Any cron scripts are much less elaborate than you may be thinking (actually, I may have misled you a bit).  Primarily, I use cron to sync the application files so that program source for our home-grown applications remains the same on both systems.  The system files (passwd, hosts, group, PATH, shells, profile, etc.) are always kept in sync manually on all our systems by the administrator making the change - ME.  Any changes occur on the production server and the changed file is immediately propagated to all other servers.  Simplistic, maybe, but that's the way I set it up years ago and it still seems to work for us.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 19 Mar 2009 11:27:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164831#M456913</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2009-03-19T11:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164832#M456914</link>
      <description>Thanks Pete.  That's what we're planning on doing in the short teerm.&lt;BR /&gt;&lt;BR /&gt;Hey...check me out Pete...only took 9 years, but I got a grad-hat!!!</description>
      <pubDate>Thu, 19 Mar 2009 11:32:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164832#M456914</guid>
      <dc:creator>Ron Irving</dc:creator>
      <dc:date>2009-03-19T11:32:16Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164833#M456915</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Use Ignite make_tape_recovery and/or make_net_recovery to create an image and then restore it at the DR site.&lt;BR /&gt;&lt;BR /&gt;Its cost effective (free) and can with practice even be automated.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 19 Mar 2009 12:52:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164833#M456915</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-03-19T12:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164834#M456916</link>
      <description>And that is one fine hat there, Ron.  Clothes do make the man, they say!  Enjoy it and keep on working at it - there's more to come.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete&lt;BR /&gt;&lt;BR /&gt;No points please</description>
      <pubDate>Thu, 19 Mar 2009 13:10:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164834#M456916</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2009-03-19T13:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164835#M456917</link>
      <description>Ron,&lt;BR /&gt;&lt;BR /&gt;I've not seen any facilities inside of Service Guard that assist in maintaining the OS anyway.  &lt;BR /&gt;&lt;BR /&gt;Mainly, I'd be looking at spreadsheets to maintain that patches are applied evenly across systems.  As far as configuration files in the OS, there are a few of them I'd not want to change automatically anyways.  So, yeah, I think this is hand management for the few items that change, but, most of those, except for patches should be scriptable.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Mar 2009 17:28:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164835#M456917</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2009-03-19T17:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: mirror systems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164836#M456918</link>
      <description>Thanks all.  I think I have what I need.&lt;BR /&gt;&lt;BR /&gt;A bientot!!!&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Thu, 19 Mar 2009 17:43:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirror-systems/m-p/5164836#M456918</guid>
      <dc:creator>Ron Irving</dc:creator>
      <dc:date>2009-03-19T17:43:25Z</dc:date>
    </item>
  </channel>
</rss>

