HP Integrity BL870c Server-Blade User Manual
Page 34
Table 6 Backup and restore procedures (continued)
Alternatives/comments
Procedure
Focus
Phase
Should be on label and in FRU.
Ensure serial# and UUID are recorded for
later reference.
BL system settings
Areas to consider:
nl
Note: can’t migrate at nPar level, other
than with Service Guard.
nl
Moving Environment
off
Migration
• Virtualized environments
nl
* note HPVM 6.x documents Online/offline
o Online/offline
- Shutdown servers in BL Domain.
nl
Blade Link Domain
Physical Change
- Replace Blade(s)
nl
- Replace Blade Link
Ensure, via SR and dumpfru
nl
Initial conditions
• Processors, Memory, IO loaded correctly.
nl
• Memory Required to be loaded on each
blade
nl
• FW recipe is consistent across blades.
nl
• SAS and LOM FW must be consistent
across all blades in the Blade Link Domain.
Restore of iLO and SFW
variables are same for three
cases
Use Cases:
nl
i. Restoration of a prior existing Partition.
nl
ii. Blade repair/replace condition
nl
Place Partition into
desired state
Restore
iii. Blade Link Domain upgrade case
A. Blade Link attach– run sysset
command to synchronized primary and
secondary FRU, if required.
nl
B. iLO
nl
1. Optional - Set iLO to default state for a
partition newly created (iLO cm menu, dc
command)
nl
2. Optional: Manually configure iLO
nl
C. SFW
nl
1. Restore system variables from disk using
dmpstore
command; i.e., Shell>
dmpstore –l filename
Example:
Shell> dmpstore –l
fs0:\tmp\sysvar
nl
2. Manually configured SFW system
variables; e.g., interleaving.
For further details please refer to the HP Integrity BL860c i4, BL870c i4 & BL890c i4 Server Blade
HP User Service Guide at
http://www.hp.com/go/Blades-docs.
34
System server configuration and booting within an nPartition