Contents

Introduction

Background Information

Download Recovery Software ISO Image

Upload ISO Image to the ESXi Datastore

Required VM Settings Prior to Recovery

Post-Recovery Requirements

Introduction

This document describes how to obtain and run the Recovery Software for the Cisco Unified Communications Manager (CUCM).

Background Information

This document describes how to obtain and run the Recovery Software for the Cisco Unified Communications Manager (CUCM), as well as the changes that are required to the Virtual Machine (VM) settings before and after the recovery.

The Recovery Software ISO images are saved in the ESXi datastore.

Datastores are logical containers, analogous to file systems, which hide the specifics of each storage device and provide a uniform model for the storage of VM files. Datastores can also be used in order to store ISO images, VM templates, and floppy images.

The vSphere Client is used in order to access the different types of storage devices that your ESXi host discovers, and in order to deploy datastores on them.

Download Recovery Software ISO Image

To obtain the Recovery Software ISO image:

1. From the Cisco home page, navigate to Downloads Home > Products > Unified Communications > Call Control > Unified Communications Manager (CallManager).

2. Click the appropriate CUCM version and download the Recovery Software:

3. Download the Recovery Software ISO image and save it in the ESXi Datastore.

Upload ISO Image to the ESXi Datastore

Complete these steps in order to upload the Recovery Software ISO image to the datastore via the vSphere Client Version 5.0:

1. Log into the vSphere Client:

2. Click Datastore and Datastore Clusters:

3. Right-click the datastore to which you would like to upload the file and click Browse Datastore:

4. Choose the folder to which you would like to upload the ISO image:

5. Click the Upload files tab:

6. Browse to the folder location where the image is saved on your machine:

7. Once you select the file, a pop-up message appears. Choose Yes:

The ISO image then begins to upload to the datastore:

Required VM Settings Prior to Recovery

Complete these steps in order to ensure that the VM settings are correct before you run the Recovery Software:

1. From the vSphere Client, navigate to the CUCM VM machine.

2. Right-click the VM for which you would like to run the Recovery Software and power off the VM:

3. Right-click and navigate to Edit Settings:

4. From the Hardware tab, select CD/DVD drive, check the Connect at power on check box, and browse to the recovery.iso image that you saved in the datastore:

5. From the Options tab, select Boot Options, check the Force BIOS Setup check box, select OK, and power on the VM:

6. The VM boots into BIOS mode. Navigate to the boot menu:

7. Use the plus (+) symbol in order to move the CD-ROM Drive option to the top of the list:

8. Press the F10 key, and you are prompted to save this setting:

The system now loads with the CD-ROM drive where the Recovery Software is located. When the system boots up, you see the options that are shown in the next image.

9. Choose option F (press the F key):

The File System check begins:

Once the File System check is complete, you are taken back to the main menu:

10. Choose option Q (press the Q key) in order to quit the Recovery Software program. You are then prompted to reboot the system, as shown here:

Post-Recovery Requirements

Note: Before you proceed with the reboot, ensure that you uncheck the Force entry into BIOS check box.

Complete these steps after you have run the Recovery Software:

1. Right-click the VM, navigate to Edit Settings > Options > Advanced > Boot Options, and ensure that the The next time the virtual machine boots, force entry into the BIOS setup screen check box is unchecked:

2. From the Hardware tab, uncheck the Connected and Connect at Power ON check boxes:

3. Proceed to reboot the system:

1. Right-click the CUCM VM.

2. Power off the machine.

3. Power on the machine.

Note: Although the Recovery Software helps to fix the file system errors and move the system out of the Read-Only mode, Cisco recommends as a best practice that either the server is upgraded to the next patch level or is rebuilt.