Recovering Cisco Video Surveillance VMs on the Cisco UCS Platforms
Recovery is used to replace an existing VM with a OVA deployment of the same release. This entails shutting down the existing VM, deploying the new VM, and transferring the storage and other properties to the new VM.
Refer to the following topics for more information.
Assumptions
The following instructions assume that the system configuration and data was previously backed up and is available for restoring on the new image.
For backup instructions, see the Cisco Video Surveillance Management Console Administration Guide.
Summary Steps
Review the following summary steps before you begin. Use the “Detailed Instructions: Recovering the VSM on the UCS” section to complete the recovery process.
|
|
|
|
|---|---|---|
Backup the server configuration using the Cisco VSM Management Console |
The configuration data from the existing VM will be restored to the new VM. The data will be lost if not backed up and restored. See the Cisco Video Surveillance Management Console Administration Guide. |
|
Download the replacement OVA image from the Cisco website. Note The new VM should be the same version as the old VM being replaced. |
||
The existing VM must be powered off before it is replaced. All video processing and user access to the virtual machine will be lost during the recovery process. |
||
Add the new replacement VM to the vSphere Client configuration. |
||
Connect the new (replacement) VM to the existing media virtual disk (used by the old VM). |
Associates the storage from the old VM to the new replacement VM. |
|
Complete the configuration on the new VM. The configuration should be the same as the old VM. |
You must manually apply the same configurations from the old VM to the new VM. |
|
Restores the existing video repositories to the new VM, which retains the existing video archives. |
||
Complete the Initial Setup using the Cisco VSM Management Console. |
Use the browser-based Management Console to preform the initial server setup. See the “Completing the Initial Server Setup Using the Management Console” section |
|
Restores the configuration data that was backed up from the old VM. See the Cisco Video Surveillance Management Console Administration Guide. |
||
Verify that the data is restored by logging on to the VSOM and viewing live video from cameras and playing back archives. |
See the Cisco Video Surveillance Operations Manager User Guide to check cameras, video streams and recordings to verify that the replacement VM is working properly. |
|
Permanently deletes the old VM from the vSphere Client software. |
Detailed Instructions: Recovering the VSM on the UCS
Step 1
Before you begin, backup the server configuration using the Cisco VSM Management Console (see the Cisco Video Surveillance Management Console Administration Guide). If the server hosts both the Operations Manager and Media Server, back up both configurations.
Step 2 Download the replacement OVA image from the Cisco website.
See the “Obtaining the Software Images” section.
Note Template files are typically large in size. We recommend downloading and copying it to universal serial bus (USB) flash to avoid download delays.
Step 3 Power off the existing Cisco VSM virtual machine (VM):
a. Launch the vSphere Client software (Figure 2-1).
b. Right-click the VM in the left pane (Inventory tree).
d. Click Yes to confirm the action.
Figure 2-1 vSphere Client Software—Powering Off the VSM VM
Step 4 Deploy the new (replacement) VM (Figure 2-2).
a. Select File > Deploy from OVF Template.
Figure 2-2 Deploying the OVF Template
b. Click Browse and select the .ova template file from a local disk, or enter the URL to download the file from the Internet.
c. Enter the remaining settings to deploy the template ( Table 2-2 ):
|
|
|
|---|---|
Select the specific host or cluster where you want to run the template. |
|
Select where the VM files will be stored. It should be deployed a datastore on internal storage, not external storage. See the “Requirements” section for the amount of disk size required to deploy the VM (depending on the UCS platform). This requirement is for the VM only and does not include the video partition(s) disk space. |
|
Click Next to accept the default disk format (Thick Provisioned Lazy Zeroed). |
d. Click Finish to accept the selected deployment settings.
e. Wait for the Cisco VSM template to deploy. Click Close when the success message appears.
f. Verify that the VM displays under the host entry in the Inventory tree (Figure 2-3).
Step 5 Connect the new (replacement) VM to the existing media virtual disk (used by the old VM).
a. Right-click the new VM and select Edit Settings (see Figure 2-3).
b. Click Add (Properties screen in Figure 2-4).
c. Select Hard Disk and click Next (Figure 2-5).
Figure 2-5 Selecting Device Type (Hard Disk)
d. Select Use an existing virtual disk and click Next (Figure 2-6).
Figure 2-6 Selecting the Disk Type to Use
e. Click Browse to navigate to the datastore in the old VM directory (see Figure 2-7).
Figure 2-7 Browsing and Selecting a Datastore
f. Select the appropriate media disk from the existing VM and click OK.
Tip See the “Adding Hard Disks for Media Storage” section for more information about the hard disk configuration for the old VM.
g. Complete the remaining steps by selecting the default values and then click Finish (see Figure 2-8).
h. Click OK to exit the VM Properties page (Figure 2-9).
Step 6 Complete the following steps to complete the configuration on the new VM.
The configuration should be the same as the old VM.
|
|
|
|
|---|---|---|
Complete the initial server setup and configure the network settings. |
Completing the Initial Server Setup Using the Management Console |
Step 7 Restore the video repositories.
Complete one of the following procedures for the OVA version you are restoring.
Note The video repositories include the video files from the original (old) VM. You must restore these repositories to the new VM or the video files will be lost.
a. Switch to the root user permissions
b. Run the storage integration script with the recovery option setup_media_storage.sh -r as described in the “Release 7.5 and Later: Adding Storage Partitions” section
c. Continue to Step 8.
Note The video repositories include the video files from the original (old) VM. You must restore these repositories to the new VM or the video files will be lost.
a. Switch to the root user permissions
b. Find the available media partitions:
– Find the available media partitions listed by labels (Figure 2-10).
linux:~# ls –al /dev/disk/by-label
Figure 2-10 Example Output for the Listed Media# Repositories
c. Note down all the media# listed in the output.
Figure 2-10 shows example output.
d. Create a partition directory:
g. After successfully creating the partition, change ownership of the partition to the nobody account and group using the following command:
linux:~ # chown nobody:nobody /media1
h. Repeat these steps to mount an sd# device with a media# label for each hard-disk added to the VM.
i. Reboot the Cisco VSM virtual machine (log out and select the Reboot option at the bottom of the screen).
j. Continue to Step 8.
Step 8 Complete the Initial Setup using the Cisco VSM Management Console.
See the “Completing the Initial Server Setup Using the Management Console” section.
Step 9 Restore the VSOM and Media Server configurations.
See the Cisco Video Surveillance Management Console Administration Guide.
Step 10 Verify that the data is restored:
a. Log on to the browser-based Operations Manager.
b. Configure the Media Server options for the /media1 and /media0 partitions.
c. View live video from cameras and playing back archives.
See the Cisco Video Surveillance Operations Manager User Guide for more information.
Step 11 Delete the old VM from the left pane (Inventory tree):
a. Right-click the old (non-functional) VSM VM.
b. Select Delete from Disk (see Figure 2-11).
Do not delete the original machine until all the previous steps in the recovery procedure have been completed.
Figure 2-11 Deleting the VSM VM from the Disk
Feedback