<?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: Imporatant files to protect in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564798#M227142</link>
    <description>if the purpose is a diseaster recovery, I would suggest making two copies of a recovery media with make_tape_recovery.&lt;BR /&gt;&lt;BR /&gt;Also, as a written documentation reference, I woudl print out the txt output from cfg2html script and keep it in a safe place.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 15 Jun 2005 13:09:05 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2005-06-15T13:09:05Z</dc:date>
    <item>
      <title>Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564795#M227139</link>
      <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;wonder if any one could add to my knowledge of important config files to be protected under hpux 11i and later version.Imporatant binaries as well &lt;BR /&gt;&lt;BR /&gt;tia&lt;BR /&gt;Wip&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Jun 2005 12:58:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564795#M227139</guid>
      <dc:creator>wip</dc:creator>
      <dc:date>2005-06-15T12:58:14Z</dc:date>
    </item>
    <item>
      <title>Re: Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564796#M227140</link>
      <description>Everything a make_tape_recovery backs up.&lt;BR /&gt;&lt;BR /&gt;man make_tape_recovery&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
      <pubDate>Wed, 15 Jun 2005 13:05:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564796#M227140</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2005-06-15T13:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564797#M227141</link>
      <description>tripwire is a third party tool that will protect binaries or at least notify you when they change.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 15 Jun 2005 13:07:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564797#M227141</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-06-15T13:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564798#M227142</link>
      <description>if the purpose is a diseaster recovery, I would suggest making two copies of a recovery media with make_tape_recovery.&lt;BR /&gt;&lt;BR /&gt;Also, as a written documentation reference, I woudl print out the txt output from cfg2html script and keep it in a safe place.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Jun 2005 13:09:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564798#M227142</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-06-15T13:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564799#M227143</link>
      <description>Hi,&lt;BR /&gt;I couldn't make out what do you mean by "to be protected". If your object is regarding backup, as others said ignite backup is the best way. Or did you mean the security?&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;&lt;BR /&gt;Jino</description>
      <pubDate>Wed, 15 Jun 2005 21:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564799#M227143</guid>
      <dc:creator>Jino.P.V</dc:creator>
      <dc:date>2005-06-15T21:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Imporatant files to protect</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564800#M227144</link>
      <description>All the configuration files and executables for HP-UX are protected by the permissions of the directories. The only method for these files to be changed is by logging in as root. That means, no one gets the root password except a specific system administrator or two.&lt;BR /&gt; &lt;BR /&gt;As far as backups, there are about 5000 files and directories that need to be saved and have restricted access. As mentioned, Ignite/UX and fbackup can copy these files to tape.</description>
      <pubDate>Wed, 15 Jun 2005 21:51:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/imporatant-files-to-protect/m-p/3564800#M227144</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-06-15T21:51:48Z</dc:date>
    </item>
  </channel>
</rss>

