Changeset 3147 in MondoRescue for branches/3.1/mindi/README.ProLiant

Timestamp:

Jun 19, 2013, 8:34:46 AM (11 years ago)

Author:

Bruno Cornec

Message:

• First pass on svn merge -r 2935:3146 ../3.0

File:

• branches/3.1/mindi/README.ProLiant (modified) (2 diffs)

branches/3.1/mindi/README.ProLiant

@@ -1 +1 @@
 $Id$
+
+MondoRescue provides enhanced HP ProLiant support.
+
+HP ProLiant provides the possibility to be configured from a HW perspective at BIOS, Smart Arry (Raid) and iLO (management board) level from a Linux system.
+
+The information is stored in the EEPROM of each HW component (BIOS, SA and iLO), retrieved through the below mentioned HP tools, and stored on the disk with XML files. These files are available at restore time, to be used by the same tools, also available, to reconfigure the HW in a similar way to what it was at backup time.                                                                                                                                        
+                                                                                                                                                           
+Only if you add FirmWare components under /usr/local/bin (CPxxx.scexe files) then these files will also be launched at restore time to force a specific FW version to be installed. As long as FirmWare files are not stored under /usr/local/bin, they won't be applied.                                                                                                                                                   
+At restore time, MondoRescue will ask a question (if not in unattended mode) in order to know if you want to restore the HW *configuration* (not HW FirmWare) content. It will then re-apply what was stored in the XML files to configure the platform exactly as it was at backup time, from a HW confiuration perspective.
 
 -------------------------------------------------------------------------------------
 
+If you have a ProLiant system you first need to get the hp-scripting-tools, hponcfg and hpacucli packages. Due to licenses issues, mindi cannot provide those tools itself. You need to get them from http://downloads.linux.hp.com/SDR
+
+Example for a RHEL6 OS:
+
+wget http://downloads.linux.hp.com/SDR/downloads/bootstrap.sh
+sh ./bootstrap.sh SPP
+sh ./bootstrap.sh Extras
+yum install -y hpacucli hponcfg hp-scripting-tools
+
+You're now ready to check your configuration by running:
+mindi-bkphw /var/cache/mindi /etc/mindi
+[First parameter is the directory where files will be generated,
+ Second parameter is the configuration directory of the file deplist.d/ProLiant.conf is located]
+
+-------------------------------------------------------------------------------------
+Older method:
+
 If you have a ProLiant system you first need to get the hp-scripting-tools, hponcfg and hpacucli packages. Due to licenses issues, mindi cannot provide those tools itself. You need to get them from http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/
+
+Example for a RHEL6 OS:
 
 wget http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/RedHat/6Server/x86_64/8.72/hpacucli-8.70-8.0.noarch.rpm
@@ -13 +41 @@
 wget http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/RedHat/6Server/i386/8.72/hp-scripting-tools-8.70-52.rhel6.i386.rpm
 yum install -y (or worst case rpm -Uvh) hp-scripting-tools-8.70-52.rhel6.i386.rpm
-(will install hp-conrep under /sbin)
+(will install hp-conrep or hp-rcu under /sbin)
 
 You're now ready to check your configuration by running: