Backup and Recovery - Oracle Exadata Recipes: A Problem-Solution Approach - page 223

Figure 8-19. Changing boot device back to the default

When complete, issue the reboot command from the ILOM console. After your compute
node starts, log in as root and validate your image by running the imagehistory
command. Note the restore from nfs backup text in the last stanza.

11.

[root@cm01dbm02 ~]# imagehistory
Version : 11.2.2.2.0.101206.2
Image activation date : 2011-02-21 11:16:12 -0800
Imaging mode : fresh
Imaging status : success

... output omitted for brevitty

Version : 11.2.2.4.2.111221
Image activation date : 2012-02-11 23:26:55 -0500
Imaging mode : patch
Imaging status : success

Version : 11.2.2.4.2.111221
Image activation date : 2012-09-06 14:19:55 -0500
Imaging mode : restore from nfs backup
Imaging status : success

[root@cm01dbm02 ~]#

12. Finally, validate and/or start your cluster resources and databases.

How It Works
Recovering your compute nodes from LVM-based snapshots is a good way to restore your system to a working state,
assuming that you have employed LVM snapshot backups using steps outlined in Recipe 8-6. This type of compute
node recovery is enabled via a special recovery process built into the bootable diagnostics.iso image, installed on
each compute node in the / opt/oracle.SupportTools directory. /opt/oracle.SupportTools/diagnostics.iso is
symbolically linked to /opt/oracle.cellos/iso/cellbits/diagnostics.iso .