You are concerned about how recovery from a failed Exadata Storage Server would work. Which
statement is true about the Exadata CELLBOOT USB?
A.
Exadata automatically copies OS binaries and configuration files from another cell during
patching to sync the internal USB.
B.
Regular Exadata Storage Server patches make sure that the internal USB is updated so that it
can be used for recovery.
C.
Changes to network configuration files are possible without usingipconf.plas long as all relevant
files are updated.
D.
Some space from the CELLBOOT USB is used for cache metadata when write back flash
cache is enabled.
E.
Each patch that is performed on Exadata storage servers requires manual resync of the
CELLBOOT USB.
Explanation:
A (not B, not E): Oracle automatically performs backups of the operating system and
cell software on each Exadata Storage Server. The contents of the system volumes are
automatically backed up and require no Oracle DMA intervention or operational processes. Oracle
assumes responsibility for backing up the critical files of the storage cells to an internal USB drive
called the CELLBOOT USB Flash Drive.
C:
Note: The ipconf utility is installed in /opt/oracle.cellos on both the Exadata Storage Servers and
Compute Nodes and is symbolically linked to /usr/local/bin/ipconf. ipconf is called at system
startup time to set and validate your Exadata server network information.
B
There is only one answer and that’s B
As a DMA, you’d like to backup Stroge Cells as well as a part of your backup process. Though, when it comes to Cell backup necessary things to be backed up are pretty much limited. Because Exadata does most of the work automatically for you using an embedded USB called CELLBOOT USB flash drive. Latest successfully working system image is stored in CELLBOOT USB. You can find versions of both active system and CELLBOOT USB by running the command as seen below:
$ imageinfo
Kernel version: 2.6.18-194.3.1.0.4.el5 #1 SMP Sat Feb 19 03:38:37 EST 2011 x86_64
Cell version: OSS_11.2.0.3.0_LINUX.X64_110520
Cell rpm version: cell-11.2.2.3.2_LINUX.X64_110520-1
Active image version: 11.2.2.3.2.110520
Active image activated: 2011-06-24 00:04:28 -0700
Active image status: success
Active system partition on device: /dev/md5
Active software partition on device: /dev/md7
In partition rollback: Impossible
Cell boot usb partition: /dev/sdm1
Cell boot usb version: 11.2.2.3.2.110520
Inactive image version: undefined
Rollback to the inactive partitions: Impossible
What is left for you to back up is just a couple files listed below:
1. /etc/hosts
2. /etc/modprobe.conf
3. /etc/sysconfig/network
4. /etc/sysconfig/network-scripts/*
Exadata also provides a way for you to create your own CELLBOOT USB. All you have to is plug-in a USB disk which should be at least 1 GB and run the tool:
$ /opt/oracle.SupportTools/make_cellboot_usb
Exadata turns your USB disk into a bootable disk of active image of your system.
Yashika what is right answer, I read your explaination???
Your Exadata Storage Servers do not need to be backed up; Exadata automatically backs these
up using a self-maintained internal USB drive
@Ranjeet, we got that from Yashika’s explanation. So what’s the correct answer?
B