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

■ exadata Storage Servers also have a diagnostics.iso file in the same location, but you cannot use this ISo to
perform LvM-based snapshot recovery of compute nodes.

Note

To perform this type of recovery on your compute nodes, you must perform the following tasks:

diagnostics.iso file to a location on your local workstation or NFS share. • Transfer the

diagnostics.iso file via the ILOM. • Set the CDROM image to this

• Change your server's boot order to boot from CDROM. This will cause the server to boot from

a virtual CDROM drive containing the diagnostics ISO image.

• Respond to the recovery process prompts as outlined in the Solution of this recipe.

• Disconnect your CDROM image and restore the boot settings of your node to the defaults.

• Reboot your compute node and validate the recovery.

While conducting recovery, the diagnostics process will extract the contents of your backup image, restore to the
proper locations on your server, and configure the server to look as it did at the time the LVM-snapshot-based backups
were taken.

8-12. Reimaging a Compute Node
Problem
Your compute node server has become corrupt and you wish to reimage it from the default configuration and patch or
upgrade to the latest software image applied prior to the corruption.

Solution
In this recipe, we will outline the steps required to reimage a compute node that has been become corrupt.

■ reimaging an exadata Compute Server is a complex process and should not be undertaken without the
guidance of oracle Support. It is usually preferable to restore your compute nodes from backups as your first option,
assuming you have valid backups. please refer to recipes 8-5, 8-6, 8-12, or consult your enterprise software recovery
manuals to restore your compute nodes using other means if you have valid backups.

Note

1. The first step you must perform is to remove your node from the RAC cluster. Refer to the

Exadata Owner's Manual or Oracle documentation for details.

Next, log a Service Request with Oracle Support to obtain a computeImageMaker file. The
computeImageMaker file is release-specific and should look like this:

2.

[root@cm01dbm01 stg]# ls -l computeImageMaker_11.2.3.1.0_LINUX.X64_120304-1.x86_64.tar.zip
-rwxrwxrwx 1 root root 310607872 May 31 21:51 computeImageMaker_11.2.3.1.0_LINUX.
X64_120304-1.x86_64.tar.zip
[root@cm01dbm01 stg]#