<?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: System Recovery in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919616#M26491</link>
    <description>Thanks Guys,&lt;BR /&gt;&lt;BR /&gt;We actually use RDP (altiris)to do the the initial system builds, which uses our standard ks.cfg file to create the filesystems and add all RPM's. So I'm fairly confident we can get the server to the same generic point. &lt;BR /&gt;&lt;BR /&gt;However I was more concerned about what may or not have been added from the point the server is handed to the application teams. Some of these servers become Oracle others Websphere and so on.. and there is always the chance that extra RPM's have been added without proper change management, which was the reason for the restoration of / excluding /proc &amp;amp; /tmp.</description>
    <pubDate>Tue, 02 Jan 2007 10:05:07 GMT</pubDate>
    <dc:creator>Matthew Pegge_1</dc:creator>
    <dc:date>2007-01-02T10:05:07Z</dc:date>
    <item>
      <title>System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919613#M26488</link>
      <description>What files if any should be excluded when restoring a system from bare metal (RHAS3 and 4) i.e. Rebuilt O/S from kickstart file to replicate partitions etc.. is there any files that should be excluded from the full restore? Are there any other gotchas when recovering servers with SAN attached storage?</description>
      <pubDate>Tue, 02 Jan 2007 05:36:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919613#M26488</guid>
      <dc:creator>Matthew Pegge_1</dc:creator>
      <dc:date>2007-01-02T05:36:20Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919614#M26489</link>
      <description>I think you could exclude /proc /tmp&lt;BR /&gt;but best test this! for I have not &lt;BR /&gt;&lt;BR /&gt;Jean-Pierre Huc&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Jan 2007 06:49:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919614#M26489</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2007-01-02T06:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919615#M26490</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;I would recommend that you build the OS as well and then exclude /dev /proc /tmp.&lt;BR /&gt;&lt;BR /&gt;Just remember that you shouldn't mix RHAS3 and RHAS4 OS restores as they use different versions of LVM. In other words, don't do an OS restore of RHAS3 onto a kickstarted RHAS4 filesystem or vice versa. &lt;BR /&gt;&lt;BR /&gt;In fact the best backup restore method would be to create a kickstart file from the original server, and keep all the latest RPM's. Then after the kickstart,all you would need to restore are /var, /home and  /etc (and maybe /usr/local) and any other customised directories off the root. I would also restore /etc/sysconfig to another location and then mv the files as needed.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Andrew Y&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Jan 2007 07:44:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919615#M26490</guid>
      <dc:creator>Andrew Young_2</dc:creator>
      <dc:date>2007-01-02T07:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919616#M26491</link>
      <description>Thanks Guys,&lt;BR /&gt;&lt;BR /&gt;We actually use RDP (altiris)to do the the initial system builds, which uses our standard ks.cfg file to create the filesystems and add all RPM's. So I'm fairly confident we can get the server to the same generic point. &lt;BR /&gt;&lt;BR /&gt;However I was more concerned about what may or not have been added from the point the server is handed to the application teams. Some of these servers become Oracle others Websphere and so on.. and there is always the chance that extra RPM's have been added without proper change management, which was the reason for the restoration of / excluding /proc &amp;amp; /tmp.</description>
      <pubDate>Tue, 02 Jan 2007 10:05:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919616#M26491</guid>
      <dc:creator>Matthew Pegge_1</dc:creator>
      <dc:date>2007-01-02T10:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919617#M26492</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;Well then you should just need to add /dev to the exclude list. &lt;BR /&gt;&lt;BR /&gt;Although Oracle is usually pretty good about keeping things in its own tree and I don't have any live Websphere sites any longer to check on those. However both use Java.&lt;BR /&gt;&lt;BR /&gt;I would also not change /boot unless its really needed. If you have a spare blade or two I would suggest a few tests. The other thing to remember is that the WWN will change if you change blades so you may have to update your switches and possibly your configuration on your restored blade. I will try to update this in Feb when we do our testing on our blades.</description>
      <pubDate>Wed, 03 Jan 2007 01:07:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919617#M26492</guid>
      <dc:creator>Andrew Young_2</dc:creator>
      <dc:date>2007-01-03T01:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919618#M26493</link>
      <description>Thanks for your help! I'm about to start some tests today so will also update the post to let you know how I go! I'm starting with a non SAN attached blade then will move to SAN attached blades and DL's.&lt;BR /&gt;&lt;BR /&gt;Thanks again!</description>
      <pubDate>Wed, 03 Jan 2007 03:22:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919618#M26493</guid>
      <dc:creator>Matthew Pegge_1</dc:creator>
      <dc:date>2007-01-03T03:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: System Recovery</title>
      <link>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919619#M26494</link>
      <description>If using RHAS 4 you should also exclude /selinux and /sys.</description>
      <pubDate>Fri, 05 Jan 2007 08:30:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/system-recovery/m-p/3919619#M26494</guid>
      <dc:creator>pjs_1</dc:creator>
      <dc:date>2007-01-05T08:30:52Z</dc:date>
    </item>
  </channel>
</rss>

