This guide provides an overview of the Disaster Recovery System, describes how to use the Disaster Recovery System, and provides procedures for completing various backup and restore related tasks. Cisco Disaster Recovery System (Cisco DRS), which can be invoked from Cisco Unified Contact Center Express Administration, provides full data backup and restore capabilities for all servers in a Cisco Unified Contact Center Express (Unified CCX) cluster.
In case of high availability (HA), Cisco DRS performs a cluster-level backup, which means that it collects backups for all servers in a Unified CCX cluster to a central location and archives the backup data to physical storage device.
The system automatically activates both the Master Agent and the Local Agent immediately after installation on the server and in case of HA setup it is activated on all nodes in the cluster. In Release 9.0(1), Cisco DRS uses an SSL-based communication between the Master Agent and the Local Agent for authentication and encryption of data between the Unified CCX publisher and subscriber nodes. Table 1 provides a quick, high-level reference to the major steps, in chronological order, that you must perform to do a backup procedure by using Cisco DRS. Table 2 provides a quick, high-level reference to the major steps, in chronological order, that you must perform to do a restore procedure by using Cisco DRS. While a backup or restore is running, you cannot perform any Operating System (OS) Administration tasks because Cisco DRS blocks all OS Administration requests by locking the platform API. To access Cisco DRS, choose Disaster Recovery System from the Navigation drop-down list box in the upper-right corner of the Cisco Unified CCX Administration window.
The system automatically activates the Master Agent service on each node of the cluster, but the Master Agent is functional only on the first node. You can access the MA through Cisco DRS user interface to perform activities such as configuring backup devices, scheduling backups by adding new backup schedules, viewing or updating an existing schedule, displaying status of executed schedules, and performing system restoration.
Each server in a Cisco Unified Contact Center Express cluster, including the server that contains the Master Agent, must have its own Local Agent to perform the backup and restore functions for its server. Before using Cisco DRS, you must configure the locations where you want the backup files to be stored. Navigate to Cisco Unified CCX Administration, select Disaster Recovery System from the Navigation drop-down list box in the upper-right corner of the Cisco Unified CCX Administration window, and click Go.
Log in to the Disaster Recovery System with the same Platform Administrator username and password that you use to log in to Cisco Unified Operating System Administration.
After you click the Save button, the Cisco DRS Master Agent validates the selected backup device. Navigate to Cisco Unified CCX Administration, select Disaster Recovery System from the Navigation menu in the upper-right corner of the Cisco Unified CCX Administration window, and click Go.
Sign in to the Disaster Recovery System by using the same administrator username and password that you use for Cisco Unified Communications Operating System Administration. Log in to the Cisco DRS by using the same Platform Administrator username and password that you use to log in to Cisco Unified Operating System Administration.
When performing a system data restoration, you can choose which node in the cluster you want to restore considering both stand alone (SA) and high availability (HA). This paper discusses an approach for creating a good disaster recovery plan for a business enterprise. The process of preparing a disaster recovery plan begins by identifying these causes and effects, analyzing their likelihood and severity, and ranking them in terms of their business priority.
When a disaster strikes, the normal operations of the enterprise are suspended and replaced with operations spelled out in the disaster recovery plan.
The disaster recovery plan does not stop at defining the resources or processes that need to be in place to recover from a disaster.
The second section of this paper explains the methods and procedures involved in the disaster recovery planning process. The first step in planning recovery from unexpected disasters is to identify the threats or risks that can bring about disasters by doing risk analysis covering threats to business continuity. Human caused: These disasters include acts of terrorism, sabotage, virus attacks, operations mistakes, crimes, and so on.
Supplier: These risks are tied to the capacity of suppliers to maintain their level of services in a disaster.
Water: There are certain disaster scenarios where water outages must be considered very seriously, for instance the impact of a water cutoff on computer cooling systems. Climate Control: Losing the air conditioning or heating system may produce different risks that change with the seasons.
Data systems risks are those related to the use of shared infrastructure, such as networks, file servers, and software applications that could impact multiple departments.
Once the disaster risks have been assessed and the decision has been made to cover the most critical risks, the next step is to determine and list the likely effects of each of the disasters. Simple "one cause multiple effects" diagrams (Figure 3) can be used as tools for specifying the effects of each of the disasters.
The intention of this exercise is to produce a list of entities affected by failure due to disasters, which need to be addressed by the disaster recovery plan.
It may be noticed that two or more disasters may affect the same entities, and it can be determined which entities are affected most often. Once the list of entities that possibly fail due to various types of disasters is prepared, the next step is to determine what is the downtime tolerance limit for each of the entities. The cost of downtime is the main key to calculate the investment needed in a disaster recovery plan.

How the disaster affected entities depend upon each other is crucial information for preparing the recovery sequence in the disaster recovery plan. Once the list of affected entities is prepared and each entity's business criticality and failure tendency is assessed, it is time to analyze various recovery methods available for each entity and determine the best suitable recovery method for each.
In the case of data systems, for example, the recovery mechanism usually involves having the critical data systems replicated somewhere else in the network and putting them online with the latest backed up data available. Considering multiple options and variations of disaster recovery mechanisms available, it is necessary to carefully evaluate the best suitable recovery mechanism for an affected entity in a particular organization.
The roles, responsibilities, and reporting hierarchy of different committee members should be clearly defined both during normal operations and in the case of a disaster emergency. Note that not all the members of the Disaster Recovery Committee may actively participate in the actual disaster recovery. Quick and precise detection of a disaster event and having an appropriate communication plan are the key for reducing the effects of the incoming emergency; in some cases it may give enough time to allow system personnel to implement actions gracefully, thus reducing the impact of the disaster. The Cisco Disaster Recovery as a Service Solution (DRaaS) and In-Cloud Disaster Recovery architectures described in this document are designed to provide a new set of related capabilities allowing Virtualized Multiservice Data Center (VMDC)-based Cloud Service Provider (CSPs) to enhance their addressable market, financial performance, and differentiation vs.
The key end-user consumable services being enabled by this system architecture will enable a CSP to offer disaster recovery for both physical and virtual servers from a customer data center to a CSP virtual private cloud (VPC). The traditional disaster recovery (DR) system constitutes a substantial portion of expenses annually. Figure 1-4 is a financial model that presents the monetization opportunity for SPs associated with the deployment of the Cisco DRaaS system architecture. Looking at the Forrester results, the majority of the respondents are either not interested or have no plans for implementing a disaster recovery solution. Zerto conducted a survey to gain a better understanding of why organizations are hesitant to implement a disaster recovery solution.
To gauge the level of satisfaction with those that have implemented a disaster recovery solution, Zerto asked questions that would provide insight to the actual effectiveness of the disaster recovery solution in place (Figure 1-7). Both the Forrester and the Zerto studies indicate that there are barriers that need to be addressed to achieve wide-scale adoption of disaster recovery at the enterprise level and also from a service provider level. Even if the hardware cost barrier can be overcome, traditional disaster recovery solutions requires a great deal of administrative effort to implement. Together, Cisco VMDC and UCS reduce infrastructure expenditures (CAPEX) and operational expenses (OPEX) to increase profitability by reducing the number of devices that must be purchased, cabled, configured, powered, cooled, and secured.
Together, Cisco VMDC and UCS enable business agility through faster provisioning of IT infrastructure and delivery of IT-as-a-service (ITaaS).
Cisco DRS allows you to perform regularly scheduled automatic or user-invoked data backups and to restore data after a failure. Cisco allows you to use any SFTP server product, but recommends SFTP products that have been certified with Cisco through the Interoperability Verification Testing (IVT) process.
Log in to the Disaster Recovery System by using the same Platform Administrator username and password that you use for Cisco Unified Operating System Administration.
The best strategy is to have some kind of disaster recovery plan in place, to return to normal after the disaster has struck. Though both concepts are related to business continuity, high availability is about providing undisrupted continuity of operations whereas disaster recovery involves some amount of downtime, typically measured in days. The ultimate results are a formal assessment of risk, a disaster recovery plan that includes all available recovery mechanisms, and a formalized Disaster Recovery Committee that has responsibility for rehearsing, carrying out, and improving the disaster recovery plan.
Figure 1 depicts the cycle of stages that lead through a disaster back to a state of normalcy.
Only when these are assessed and the affected systems are identified can a recovery process begin. The plan should also define how to restore operations to a normal state once the disaster's effects are mitigated. An effective disaster recovery plan plays its role in all stages of the operations as depicted above, and it is continuously improved by disaster recovery mock drills and feedback capture processes. Risk analysis (sometimes called business impact analysis) involves evaluating existing physical and environmental security and control systems, and assessing their adequacy with respect to the potential threats. The effects of a disaster that strikes the entire enterprise are different from the effects of a disaster affecting a specific area, office, or utility within the company.
It is also useful to determine how many powers feeds operate within the facility and if necessary make the power system redundant. A key factor in evaluating risks associated with telephone systems is to study the telephone architecture and determine if any additional infrastructure is required to mitigate the risk of losing the entire telecommunication service during a disaster. A key objective in analyzing these risks is to identify all single points of failure within the data systems architecture.
A higher value would mean longer restoration time hence the priority of having a Disaster Recovery mechanism for this risk is higher.
In Figure 3, the entities that fail due to the earthquake disaster are office facility, power system, operations staff, data systems, and telephone system. This information becomes crucial for preparing the recovery sequence in the disaster recovery plan.
For example, having the data systems restored has a dependency on the restoration of power.

For less critical data systems, there may be an option to have spare server hardware, and if required these servers could be configured with the required application. This committee should have representation from all the different company agencies with a role in the disaster recovery process, typically management, finance, IT (multiple technology leads), electrical department, security department, human resources, vendor management, and so on. During a disaster, this committee ensures that there is proper coordination between different agencies and that the recovery processes are executed successfully and in proper sequence. Execution Phase: In this phase, the actual procedures to recover each of the disaster affected entities are executed. Reconstitution Phase: In this phase the original system is restored and execution phase procedures are stopped. A hurricane affecting a specific geographic area, or a virus spread expected on a certain date are examples of disasters with advance notice.
At the end of this phase, recovery staff will be ready to execute contingency actions to restore system functions on a temporary basis. The use of DRaaS allows enterprises to focus on application validation without being distracted by rack, stack, and recover activities with their infrastructure and IT services. To allow for more insightful results, Zerto allowed the respondents to check more than one box and found that cost and complexity overwhelmingly are the biggest obstacles to adopting disaster recovery. For survey respondents, this created a capital cost barrier for the equipment purchased and significantly increased the administrative overhead to the point that the Forrester survey shows the majority of the respondents had no plan of implementing disaster recovery. They may choose to repurpose older hardware and create their own recovery site, but now they can also look at a hybrid cloud solution and choose an SP provider that is running ZVR. VMDC is a reference architecture for building a fabric-based infrastructure that provides design guidelines demonstrating how customers can integrate key Cisco and partner technologies, such as networking, computing, integrated compute stacks, security, load balancing, and system management. When the server is restored with these files, you do not need to reconfigure Cisco DRS backup device and schedule.
Be aware that if you delete the IPSEC truststore(hostname.pem) file from the Certificate Management pages, then Cisco DRS will not work as expected.
After the server is restored with these files, you do not need to reconfigure Cisco DRS backup device and schedule. Cisco Developer Network (CDN) partners, such as GlobalSCAPE, certify their products with specified version of Unified CCX.
For an enterprise, a disaster means abrupt disruption of all or part of its business operations, which may directly result in revenue loss. Effects of disasters range from small interruptions to total business shutdown for days or months, even fatal damage to the business. The disaster recovery system cannot replace the normal working system forever, but only supports it for a short period of time.
Finally, ongoing procedures for testing and improving the effectiveness of the disaster recovery system are part of a good disaster recovery plan. And the fourth section explains what information the disaster recovery plan should contain and how to maintain the disaster recovery plan. To mitigate the risk of disruption of business operations, a recovery solution should involve disaster recovery facilities in a location away from the affected area.
Recovery from this type of failure may be lengthy and expensive due to the need to replace or update software and equipment and retrain personnel. The entities with less downtime tolerance limit should be assigned higher priorities for recovery.
Depending on the data system, there may be options of autorecovery or manual recovery, and the cost and recovery time factors of each mechanism vary. Procedures should contain the process to alert recovery personnel during business and nonbusiness hours. Many of Cisco's VMDC-based CSPs seek better monetization of their existing VMDC investments through layered services that are synergistic with the advanced networking capabilities delivered by VMDC. Cisco UCS is a next-generation data center platform that unites compute, network, storage access, and virtualization into a cohesive system designed to reduce total cost of ownership (TCO) and increase business agility. To minimize disaster losses, it is very important to have a good disaster recovery plan for every business subsystem and operation within an enterprise. At the earliest possible time, the disaster recovery process must be decommissioned and the business should return to normalcy.
Nowadays most of the meteorological threats can be forecasted, hence the chances to mitigate effects of some natural disasters are considerable. After the disaster detection, a notification should be sent to the damage assessment team, so that they can assess the real damage occurred and implement subsequent actions. The journal history can be as little as one hour, or up to five days' worth of data, with recovery points available every few seconds.
By standardizing an infrastructure around these systems, a CSP can realize a number of benefits to reduce costs and complexity, while improving agility.

Tabletop exercise definition
How to care for your pet bunny
Usa freedom corps volunteer network


  1. 03.02.2014 at 10:52:18

    Regain some of her linked Press evaluation.

    Author: eminem4ik
  2. 03.02.2014 at 17:15:24

    Out Teflon coating and non-lethally, at least not in the.

    Author: ISABELLA