Table Of Contents
Video Surveillance Recovery Guide for UCS B- and C-Series Platforms
Video Surveillance Recovery Guide for UCS B- and C-Series Platforms
November 2012This guide describes the procedure to recover a virtualized Cisco® Video Surveillance Manager (VSM) on the Cisco Unified Computing System™ (UCS) B- and C-Series platforms.
Contents
This document includes the following sections:
Introduction
This guide describes the procedure to recover a virtualized VSM on the UCS B- and C-Series platforms.
Audience
This document is intended for use by Cisco System Engineers, Physical Security Advanced Technology Provider (ATP) partners, and technical field staff that are developing and implementing Cisco Video Surveillance and UCS Servers for branch office and data center solutions.
A successful implementation also requires additional knowledge in the following areas:
•Cisco UCS Servers configuration
•Cisco VSM (Release 6.3.2) installation and configuration
Assumptions
This guide contains detailed instructions on the recovery of VSM on UCS blade and rack-mount servers, and assumes that data has been backed up and is available for restoring on the new recovered image. For backup instructions, see http://www.cisco.com/en/US/docs/security/physical_security/video_surveillance/network/vsm/6_3/install_upgrade/vsm_install_upgrade.html.
Recovering the VSM on the UCS
To recover the VSM on the UCS:
Step 1 Download the VSM, Release 6.3.2 VMware recovery template from the Cisco web site.
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 2 Launch the vSphere Client software (see Figure 1).
Figure 1 vSphere Client Software—Powering Off the VSM VM
Step 3 In the left pane (Inventory tree), right-click a virtual machine (VM) and select Power > Power Off to power off the current VSM VM.
Step 4 On the vSphere Client toolbar, click File > Deploy from OVF Template (see Figure 2).
Figure 2 Deploying the OVF Template
Step 5 In the left pane (Inventory tree), select the newly recovered VM (see Figure 3).
Figure 3 Current Summary of Selected VM
Step 6 Right-click the VM and select Edit Settings (see Figure 4).
Figure 4 Edit Settings
Step 7 On the Virtual Machine Properties screen (see Figure 5), click Add and connect to the existing media virtual disk from the old VM.
Figure 5 Adding a Hard Disk
Step 8 Click OK to display the device types (see Figure 6).
Figure 6 Selecting Device Type (Hard Disk)
Step 9 From the list of device types, select Hard Disk and click Next to display the disk types (see Figure 7).
Figure 7 Selecting the Disk Type to Use
Step 10 Click the Use an existing virtual disk radio button and click Next to display the existing disks (see Figure 8).
Figure 8 Select an Existing Disk
Step 11 Click Browse to navigate to the datastore in the old VM directory (see Figure 9).
Figure 9 Browsing Datastores
Step 12 Select the virtual disk file with 13 TB file size. (Select the appropriate media disk from the existing VM.)
Step 13 Click OK and complete the remaining steps by selecting the default values (see Figure 10).
Figure 10 Ready to Complete
Step 14 Click Finish to display the devices (see Figure 11).
Figure 11 Newly Added Hard Disk
Step 15 Select New Hard Disk (adding) and click OK to display the list of VMs (see Figure 12).
Figure 12 Powering on the New VM
Step 16 In the left pane (Inventory tree), right-click a VM and select Power > Power On to display the VMs (see Figure 13).
Figure 13 Opening the VM Console
Step 17 In the left pane (Inventory tree), right-click a VM and select Open Console.
Step 18 Log on to the VSM with the standard default root username and the secur4u password.
Step 19 Launch the Yet Another Setup Tool (YaST) Control Center (see Figure 14) to configure the network and Network Time Protocol (NTP) settings to match the original VM.
Figure 14 YaST Control Center
Step 20 Restore the VSOM to VSM data:
a. Copy the VSOM backup file from its current location to the installed VSM server.Enter the following shell commands to stop the server:
shell> service cisco stop
b. From the Secure Shell (SSH) command line, enter the following command, where filename is the name of the backup file, and must include the .tar.gz extension:
shell> /usr/BWhttpd/bin/vsom_backup_restore -f filename
For example:
shell> /usr/BWhttpd/bin/vsom_backup_restore -f VSOM_psbu-dev03_backup_20100128164352.tar.gz
c. Restart the server.
shell> service cisco start
Step 21 Restore the VSM data:
a. Enter the following command to stop the server:
shell> service cisco stop
b. Copy the Video Surveillance Media Server (VSMS) backup file from its current location to the VSMS server.
c. Use the following command to extract the backup file, where the filename is the name of the backup file, and must include the .tar.gz extension:
shell> gunzip filename.tar.gz e.
d. From the SSH command line, enter:
shell> tar -Pxvf filename.tar
For example:
shell> tar -Pxvf VSMS_PST_backup_20070327153851.tar
e. Restart the server:
shell> service cisco restart
Step 22 Verify that the data is restored by logging on to the VSOM and viewing feeds from cameras and playing back archives.
Step 23 In the left pane (Inventory tree), right-click the non-functional VSM VM and select Delete from Disk (see Figure 15).
Caution Do not delete the original machine until all the previous steps in the recovery procedure have been completed.
Figure 15 Deleting the VSM VM from the Disk
More Information
For more information about Cisco-related products, see the following resources:
For more Cisco Physical Security product information:
http://www.cisco.com/go/physec/Cisco Unified Computing and Servers:
http://www.cisco.com/en/US/products/ps10265/index.htmlCisco Video Surveillance Media Server Software Install and Upgrade Guides:
http://www.cisco.com/en/US/products/ps9152/prod_installation_guides_list.html