| 1 | $Id$
|
|---|
| 2 |
|
|---|
| 3 | MondoRescue provides enhanced HP ProLiant support.
|
|---|
| 4 |
|
|---|
| 5 | 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.
|
|---|
| 6 |
|
|---|
| 7 | 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.
|
|---|
| 8 |
|
|---|
| 9 | 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.
|
|---|
| 10 | 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.
|
|---|
| 11 |
|
|---|
| 12 | -------------------------------------------------------------------------------------
|
|---|
| 13 |
|
|---|
| 14 | 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.hpe.com/SDR
|
|---|
| 15 |
|
|---|
| 16 | Example for a RHEL6 OS:
|
|---|
| 17 |
|
|---|
| 18 | wget http://downloads.linux.hpe.com/SDR/downloads/bootstrap.sh
|
|---|
| 19 | sh ./bootstrap.sh spp
|
|---|
| 20 | sh ./bootstrap.sh stk
|
|---|
| 21 | yum install -y hpssacli hponcfg hp-scripting-tools
|
|---|
| 22 |
|
|---|
| 23 | You're now ready to check your configuration by running:
|
|---|
| 24 | mindi-bkphw /var/cache/mindi /etc/mindi
|
|---|
| 25 | [First parameter is the directory where files will be generated,
|
|---|
| 26 | Second parameter is the configuration directory of the file deplist.d/ProLiant.conf is located]
|
|---|
| 27 |
|
|---|
| 28 | ---------------------------------------------------------------------------------------
|
|---|
| 29 | OLD - ODL - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD - OLD
|
|---|
| 30 | ---------------------------------------------------------------------------------------
|
|---|
| 31 | Older method:
|
|---|
| 32 |
|
|---|
| 33 | 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.hpe.com/SDR/repo/spp
|
|---|
| 34 |
|
|---|
| 35 | Example for a RHEL6 OS:
|
|---|
| 36 |
|
|---|
| 37 | wget http://downloads.linux.hpe.com/SDR/repo/spp/RedHat/6Server/x86_64/current/hpssacli-2.30-6.0.x86_64.rpm
|
|---|
| 38 | yum install -y (or worst case rpm -Uvh) hpacucli-2.30-6.0.x86_64.rpm
|
|---|
| 39 | (will install hpacuscripting under /usr/sbin)
|
|---|
| 40 | wget http://downloads.linux.hpe.com/SDR/repo/spp/RedHat/6Server/x86_64/current/hponcfg-4.6.0-0.x86_64.rpm
|
|---|
| 41 | yum install -y (or worst case rpm -Uvh) hponcfg-4.6.0-0.x86_64.rpm
|
|---|
| 42 | (will install hponcfg under /usr/sbin)
|
|---|
| 43 | wget http://downloads.linux.hpe.com/SDR/repo/stk/RedHat/6Server/x86_64/current/hp-scripting-tools-10.30-39.rhel6.x86_64.rpm
|
|---|
| 44 | yum install -y (or worst case rpm -Uvh) hp-scripting-tools-10.30-39.rhel6.x86_64.rpm
|
|---|
| 45 | (will install hp-conrep or hp-rcu under /sbin)
|
|---|
| 46 |
|
|---|
| 47 | You're now ready to check your configuration by running:
|
|---|
| 48 | mindi-bkphw /var/cache/mindi /etc/mindi
|
|---|
| 49 | [First parameter is the directory where files will be generated,
|
|---|
| 50 | Second parameter is the configuration directory of the file deplist.d/ProLiant.conf is located]
|
|---|
| 51 |
|
|---|
| 52 | -------------------------------------------------------------------------------------
|
|---|
| 53 | Some of these tools are also provided as part of the Smart Start Scripting Toolkit. You can get it from http://www.hp.com/servers/sstoolkit and use the following:
|
|---|
| 54 | cd /tmp
|
|---|
| 55 | wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1221080004/v63551/ss-scripting-toolkit-linux-8.70.tar.gz
|
|---|
| 56 | mkdir ssstk
|
|---|
| 57 | cd ssstk
|
|---|
| 58 | tar xvfz ../ss-scripting-toolkit-linux-8.70.tar.gz
|
|---|
| 59 | cp -a utilities/conrep /usr/sbin
|
|---|
| 60 | cp -a utilities/conrep.xml /usr/share/conrep/conrep.xml
|
|---|
| 61 | cp -a utilities/hponcfg /usr/sbin
|
|---|
| 62 | cp -a utilities/hpacucli/hpacuscripting /usr/sbin
|
|---|
| 63 | cp -a utilities/hpacucli/.hpacuscripting /usr/sbin
|
|---|
| 64 |
|
|---|
| 65 | # For versions <= 1.90
|
|---|
| 66 | cp -a utilities/cpqacuxe/cpqacuxe /usr/local/bin
|
|---|
| 67 | cp -a utilities/cpqacuxe/bld /usr/local/bin
|
|---|
| 68 | mv /usr/local/bin/bld/*.so /usr/local/lib
|
|---|
| 69 | echo /usr/local/lib >> /etc/ld.so.conf
|
|---|
| 70 | ldconfig
|
|---|
| 71 |
|
|---|
| 72 | -------------------------------------------------------------------------------------
|
|---|
| 73 | Older URL:
|
|---|
| 74 | wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v40154/ss-scripting-toolkit-linux-1.70.tar.gz
|
|---|
| 75 | wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v43548/ss-scripting-toolkit-linux-1.81.tar.gz
|
|---|
| 76 | wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v44247/ss-scripting-toolkit-linux-1.90.tar.gz
|
|---|
| 77 | -------------------------------------------------------------------------------------
|
|---|
| 78 | If you're making a backup with mondoarchive on a ProLiant system that you want to be able to restore using the Virtual Media function of ProLiants, then you have to ensure that the required drivers will be available at restore time.
|
|---|
| 79 | In order to ensure that, you may want to do on 2.2.x (x < 5) versions:
|
|---|
| 80 | - Edit your /usr/sbin/mindi script
|
|---|
| 81 | - Look for declaration of the variable FORCE_MODS.
|
|---|
| 82 | - Change it to FORCE_MODS="usb-storage sr_mod"
|
|---|
| 83 |
|
|---|
| 84 | Those drivers will then be available at restore time, and your virtual media thus detected and supported.
|
|---|
| 85 | As the CD-ROM emulated is a USB one, it will be a slower restore than using a real CD, or the network, but can be an easy way to load the mindi boot image e.g. and launch the rest of the restore through the network.
|
|---|
| 86 |
|
|---|
| 87 | With latest versions of mindi, those modules are already included and you don't have to do anything to have it work.
|
|---|
