Disaster Recovery Status Report 22 Feb2012reesmorgan
The document provides a status report on a disaster recovery test conducted by Aviat Networks on February 22, 2012. It details the applications tested, environment prepared, timeline, and discoveries from the test. The test validated Aviat's disaster recovery solution using EMC RecoverPoint and VMware SRM to failover virtual machines from Santa Clara to San Antonio. Some applications tested successfully while others had partial or failed results, revealing areas for improvement in the disaster recovery configuration.
This document discusses data replication in distributed systems. It describes two types of replication: synchronous and asynchronous. For asynchronous replication, there is primary site asynchronous and peer-to-peer asynchronous. The document then focuses on the lazy master framework, outlining components like the primary/secondary copies, ownership, propagation, refreshment, and configuration. It provides details on the system architecture involving log monitors, propagators, receivers, and refreshers. Finally, it covers topics like failure and recovery handling.
HBase Read High Availabilty using Timeline Consistent Region ReplicasDataWorks Summit
The document describes HBase's new timeline consistency feature for high availability reads using region replicas. It discusses how region replicas work, including that the primary region accepts writes while secondary replicas only allow reads. It introduces the new timeline consistency option for reads that returns results from secondary replicas, allowing for highly available reads. The implementation details and future work are also outlined.
Disaster recovery plans aim to restore critical network functionality after a disaster. Key aspects include planning for worst case scenarios, documenting recovery procedures, and considering data, systems, and personnel. Redundancy of data, servers, and hardware at multiple locations guards against single points of failure. While backups are important, more sophisticated techniques like disk mirroring ensure near real-time data availability. Testing and updating plans is also essential as networks change.
The document discusses disaster recovery (DR) planning and testing using virtual DR solutions. It notes that downtime has significant economic costs, and that most enterprises prioritize improving DR capabilities. Traditional DR testing is static, focuses on backups, and has slow recovery times. Virtual DR solutions allow replicating workloads into virtual machines, enabling one-click failover and flexible testing. This reduces recovery times and costs while improving protection of workloads. The document promotes PlateSpin Protect and Forge solutions for virtual DR and workload protection across environments.
This document discusses key aspects of disaster recovery planning (DRP) fundamentals. It covers why DRP is needed, defining disaster scenarios, DRP perspectives and requirements, getting management buy-in, assessing organizational geography, and deciding on cold, warm or hot site approaches. It also outlines the roles of the DRP control group, committee and teams in disaster recovery management. The overall message is that with organizations' growing IT dependence, DRP must be taken seriously to ensure business survival.
Disaster Recovery Plan / Enterprise Continuity PlanMarcelo Silva
This document outlines a presentation on developing a Disaster Recovery Plan (DRP) and Enterprise Continuity Plan (ECP). It discusses defining roles and teams for responding to incidents, assessing risks across six resilience layers of strategy, organization, processes, data, technology, and facilities. It also covers training the response team, engaging outside experts, and creating awareness campaigns to implement the DRP/ECP.
This disaster recovery plan outlines procedures for restoring the company's core information systems in the event of a disaster. It details practices for regular data backups, server administration, and system shutdown/startup. Full backups are taken weekly with incremental backups daily and are stored both onsite and offsite. In the event of a disaster, the plan provides guidelines for damage assessment, prioritizing critical services, and reconstituting IT systems through salvaging equipment and restoring from backups to return to normal operations.
The document discusses disaster recovery and business continuity plans. It explains that disaster recovery plans, also known as business continuity plans, describe how an organization will deal with potential disasters and minimize disruption. The document then provides details on the increasing importance and complexity of disaster recovery planning for modern enterprises. It also outlines some of the key aspects of developing a disaster recovery plan, including risk analysis, business impact analysis, and testing procedures.
Disaster Recovery: the process related to preparing for recovery or planning critical technology infrastructure before a natural or human disaster occurs.
Disaster Recovery Planning: Best Practices, Templates, and ToolsZetta Inc
The document discusses best practices for building an effective disaster recovery (DR) plan. It recommends conducting a business impact analysis to identify critical applications and recovery objectives. A risk assessment should identify infrastructure dependencies and single points of failure to manage risks. DR plans must be tested to ensure they can meet recovery time and point objectives. The presentation then describes how the Zetta cloud backup and DR solution helps customers limit exposure to outages through geographic replication, high availability configurations, and browser-based recovery capabilities.
This document provides an overview of disaster recovery strategies using IBM Tivoli Storage Management (TSM). It discusses developing a comprehensive disaster recovery plan with TSM, which includes classifying data, understanding recovery time objectives, developing notification and recovery procedures, and regularly testing the disaster recovery plan. The document also covers infrastructure considerations like data center design and distributed system architectures to improve availability. Effective disaster recovery planning with TSM can help businesses continue operating after a disaster by recovering critical data and systems.
Disaster Recovery Status Report 22 Feb2012reesmorgan
The document provides a status report on a disaster recovery test conducted by Aviat Networks on February 22, 2012. It details the applications tested, environment prepared, timeline, and discoveries from the test. The test validated Aviat's disaster recovery solution using EMC RecoverPoint and VMware SRM to failover virtual machines from Santa Clara to San Antonio. Some applications tested successfully while others had partial or failed results, revealing areas for improvement in the disaster recovery configuration.
This document discusses data replication in distributed systems. It describes two types of replication: synchronous and asynchronous. For asynchronous replication, there is primary site asynchronous and peer-to-peer asynchronous. The document then focuses on the lazy master framework, outlining components like the primary/secondary copies, ownership, propagation, refreshment, and configuration. It provides details on the system architecture involving log monitors, propagators, receivers, and refreshers. Finally, it covers topics like failure and recovery handling.
HBase Read High Availabilty using Timeline Consistent Region ReplicasDataWorks Summit
The document describes HBase's new timeline consistency feature for high availability reads using region replicas. It discusses how region replicas work, including that the primary region accepts writes while secondary replicas only allow reads. It introduces the new timeline consistency option for reads that returns results from secondary replicas, allowing for highly available reads. The implementation details and future work are also outlined.
Disaster recovery plans aim to restore critical network functionality after a disaster. Key aspects include planning for worst case scenarios, documenting recovery procedures, and considering data, systems, and personnel. Redundancy of data, servers, and hardware at multiple locations guards against single points of failure. While backups are important, more sophisticated techniques like disk mirroring ensure near real-time data availability. Testing and updating plans is also essential as networks change.
The document discusses disaster recovery (DR) planning and testing using virtual DR solutions. It notes that downtime has significant economic costs, and that most enterprises prioritize improving DR capabilities. Traditional DR testing is static, focuses on backups, and has slow recovery times. Virtual DR solutions allow replicating workloads into virtual machines, enabling one-click failover and flexible testing. This reduces recovery times and costs while improving protection of workloads. The document promotes PlateSpin Protect and Forge solutions for virtual DR and workload protection across environments.
This document discusses key aspects of disaster recovery planning (DRP) fundamentals. It covers why DRP is needed, defining disaster scenarios, DRP perspectives and requirements, getting management buy-in, assessing organizational geography, and deciding on cold, warm or hot site approaches. It also outlines the roles of the DRP control group, committee and teams in disaster recovery management. The overall message is that with organizations' growing IT dependence, DRP must be taken seriously to ensure business survival.
Disaster Recovery Plan / Enterprise Continuity PlanMarcelo Silva
This document outlines a presentation on developing a Disaster Recovery Plan (DRP) and Enterprise Continuity Plan (ECP). It discusses defining roles and teams for responding to incidents, assessing risks across six resilience layers of strategy, organization, processes, data, technology, and facilities. It also covers training the response team, engaging outside experts, and creating awareness campaigns to implement the DRP/ECP.
This disaster recovery plan outlines procedures for restoring the company's core information systems in the event of a disaster. It details practices for regular data backups, server administration, and system shutdown/startup. Full backups are taken weekly with incremental backups daily and are stored both onsite and offsite. In the event of a disaster, the plan provides guidelines for damage assessment, prioritizing critical services, and reconstituting IT systems through salvaging equipment and restoring from backups to return to normal operations.
The document discusses disaster recovery and business continuity plans. It explains that disaster recovery plans, also known as business continuity plans, describe how an organization will deal with potential disasters and minimize disruption. The document then provides details on the increasing importance and complexity of disaster recovery planning for modern enterprises. It also outlines some of the key aspects of developing a disaster recovery plan, including risk analysis, business impact analysis, and testing procedures.
Disaster Recovery: the process related to preparing for recovery or planning critical technology infrastructure before a natural or human disaster occurs.
Disaster Recovery Planning: Best Practices, Templates, and ToolsZetta Inc
The document discusses best practices for building an effective disaster recovery (DR) plan. It recommends conducting a business impact analysis to identify critical applications and recovery objectives. A risk assessment should identify infrastructure dependencies and single points of failure to manage risks. DR plans must be tested to ensure they can meet recovery time and point objectives. The presentation then describes how the Zetta cloud backup and DR solution helps customers limit exposure to outages through geographic replication, high availability configurations, and browser-based recovery capabilities.
This document provides an overview of disaster recovery strategies using IBM Tivoli Storage Management (TSM). It discusses developing a comprehensive disaster recovery plan with TSM, which includes classifying data, understanding recovery time objectives, developing notification and recovery procedures, and regularly testing the disaster recovery plan. The document also covers infrastructure considerations like data center design and distributed system architectures to improve availability. Effective disaster recovery planning with TSM can help businesses continue operating after a disaster by recovering critical data and systems.
9. 备用网络系统 a) 灾难发生时能在预定时间内调配所需的通信线路和
网络设备到位
备用基础设施 a) 有符合介质存放条件的场地;
b) 有满足信息系统和关键业务功能恢复运作要求的备
用场地。
技术支持 —
运行维护支持 a) 有介质存取、验证和转储管理制度;
b) 按介质特性对备份数据进行定期的有效性验证;
c) 有备用场地管理制度;
d) 与相关厂商有符合灾难恢复时间要求的紧急供货协
议;
e) 与相关运营商有符合灾难恢复时间要求的备用通信
线路协议。
灾难恢复预案 有相应的经过完整测试和演练的灾难恢复预案
1.1.2.3 第 3 级 电子传输和部分设备支持
第 3 级灾难恢复应具有技术和管理支持:
要素 要求
数据备份系统 a) 完全数据备份至少每天一次;
b) 备份介质场外存放;
c) 每天多次利用通信网络将关键数据定时批量传送至
备用场地。
备用数据处理系统 a) 配备灾难恢复所需的部分数据处理设备。
备用网络系统 a) 配备部分通信线路和相应的网络设备。
备用基础设施 a) 有符合介质存放条件的场地;
b) 有满足信息系统和关键业务功能恢复运作要求的场
地。
技术支持 a) 在备用场地有专职的计算机机房运行管理人员。
运行维护支持 a) 按介质特性对备份数据进行定期的有效性验证;
b) 有介质存取、验证和转储管理制度;
c) 有备用计算机机房管理制度;
d) 有备用数据处理设备硬件维护管理制度;
e) 有电子传输数据备份系统运行管理制度。
灾难恢复预案 有相应的经过完整测试和演练的灾难恢复预案
第 3 级是在第 2 级的基础上用电子链路取代了车辆进行数据传送的数据备份。接
10. 收方的硬件平台必须与生产中心物理地相分离,在故障发生后,存储的数据用于数据
恢复。由于热备份中心要保持持续运行并配备了灾难恢复所需的数据处理的软硬件部
分,因此增加了成本。但确实是消除了运送工具的需要,提高了数据恢复的速度。
1.1.2.4 第 4 级 电子传输及完整设备支持
第 4 级灾难恢复应具有技术和管理支持:
要素 要求
数据备份系统 a) 完全数据备份至少每天一次;
b) 备份介质场外存放;
c) 每天多次利用通信网络将关键数据定时批量传送至
备用场地。
备用数据处理系统 a) 配备灾难恢复所需的全部数据处理设备,并处于就绪
状态或运行状态。
备用网络系统 a) 配备灾难恢复所需的通信线路;
b) 配备灾难恢复所需的网络设备,并处于就绪状态。
备用基础设施 a) 有符合介质存放条件的备用场地;
b) 有符合备用数据处理系统和备用网络设备运行要求
的场地;
c) 有满足关键业务功能恢复运作要求的场地;
d) 以上场地应保持 7 x 24 运作。
技术支持 在备用场地有:
a) 7 x 24 专职计算机机房管理人员;
b) 专职数据备份技术支持人员;
c) 专职硬件、网络技术支持人员。
运行维护支持 a) 有介质存取、验证和转储管理制度;
b) 按介质特性对备份数据进行定期的有效性验证;
c) 有备用计算机机房运行管理制度;
d) 有硬件和网络运行管理制度;
e) 有电子传输数据备份系统运行管理制度。
灾难恢复预案 有相应的经过完整测试和演练的灾难恢复预案
第 4 级 这种数据备份要求两个中心相关的主机同时处于活动状态并管理彼此的
备份数据,实现数据的在线备份。备份中心硬件平台必须保证与生产中心方平台物理
地相分离,在两个中心之间,在线关键数据的拷贝多次向备份中心传送着。在故障发
生时,备份中心具备关键业务灾难恢复所需的全部数据处理设备,并处于就绪状态或
11. 运行状态,以及灾难恢复所需的网络设备并处于就绪状态,保证需要恢复的关键数据
通过可迅速恢复。
1.1.2.5 第 5 级 实时数据传输及完整设备支持
第五级灾难恢复应具有技术和管理支持:
要素 要求
数据备份系统 a) 完全数据备份至少每天一次;
b) 备份介质场外存放;
c) 采用远程数据复制技术,并利用通信网络将关键数据
实时复制到备份场地。
备用数据处理系统 a) 配备灾难恢复所需的部分数据处理设备。
a) 配备灾难恢复所需的全部数据处理设备,并处于就绪
状态或运行状态。
备用网络系统 a) 配备灾难恢复所需的通信线路;
b) 配备灾难恢复所需的网络设备,并处于就绪状态。
c) 具备通信网络自动或集中切换能力。
备用基础设施 a) 有符合介质存放条件的备用场地;
b) 有符合备用数据处理系统和备用网络设备运行要求
的场地;
c) 有满足关键业务功能恢复运作要求的场地;
d) 以上场地应保持 7 x 24 运作。
技术支持 在备用场地有:
a) 7 x 24 专职计算机机房管理人员;
b) 7 x 24 专职数据备份技术支持人员;
c) 7 x 24 专职硬件、网络技术支持人员
运行维护支持 a) 有介质存取、验证和转储管理制度;
b) 按介质特性对备份数据进行定期的有效性验证;
c) 有备用计算机机房运行管理制度;
d) 有硬件和网络运行管理制度;
e) 有实时数据备份系统运行管理制度。
灾难恢复预案 有相应的经过完整测试和演练的灾难恢复预案
第 5 级是考虑生产中心和备份中心相距离隔较远, (根据单一提交更新范围,在
本地和远程数据库中同时更新着数据),也就是说,在更新请求被认为是满意之前,
第 5 级需要生产中心与备份中心的数据都被更新。我们可以想象这样一种情景,数
据在两个中心之间相互映像,由远程两个阶段提交过程来同步,因为关键应用使用了
12. 双重在线存储,所以在故障发生时,仅仅传送中的数据被丢失,恢复的时间被降低到
了小时级。
1.1.2.6 第 6 级 数据零丢失和远程集群支持
第六级灾难恢复应具有技术和管理支持:
要素 要求
数据备份系统 a) 完全数据备份至少每天一次;
b) 备份介质场外存放;
c) 远程实时备份,实现数据零丢失。
备用数据处理系统 a) 备用数据处理系统具备与生产数据处理系统一致的
处理能力并完全兼容;
b) 应用软件是“集群的”,可实时无缝切换;
c) 具备远程集群系统的实时监控和自动切换能力。
备用网络系统 a) 配备与生产系统相同等级的通信线路和网络设备;
b) 备用网络处于运行状态;
c) 最终用户可通过网络同时接入主、备中心。
备用基础设施 a) 有符合介质存放条件的备用场地;
b) 有符合备用数据处理系统和备用网络设备运行要求
的场地;
c) 有满足关键业务功能恢复运作要求的场地;
d) 以上场地应保持 7 x 24 运作。
技术支持 在备用场地有:
a) 7 x 24 专职计算机机房管理人员;
b) 7 x 24 专职数据备份技术支持人员;
c) 7 x 24 专职硬件、网络技术支持人员;
d) 7 x 24 专职操作系统、数据库和应用软件技术支持
人员。
运行维护支持 a) 有介质存取、验证和转储管理制度;
b) 按介质特性对备份数据进行定期的有效性验证;
c) 有备用计算机机房运行管理制度;
d) 有硬件和网络运行管理制度;
e) 有电子传输数据备份系统运行管理制度。
e) 有实时数据备份系统运行管理制度。
f) 有操作系统、数据库和应用软件运行管理制度。
灾难恢复预案 有相应的经过完整测试和演练的灾难恢复预案
第 6 级在第 5 级的基础上,除了可以实现零数据丢失率,同时保证数据立即自动
38. 3.8.2 Symantec 远程镜像数据容灾原理
Symantec 建议利用 VERITAS Storage Foundation 系列软件的镜像技术,来构
建容灾方案。利用 VERITAS Storage Foundation 的镜像技术构建容灾系统是非常简
单的,它只有一个条件,就是将生产中心和灾备中心之间的 SAN 存储区域网络通过光
纤连接起来,建立城域 SAN 存储网络。然后,我们就可以通过 Storage Foundation
提供的非常成熟的跨阵列磁盘镜像技术来实现同城容灾了,容灾方案的结构如下图所
示:
39. 从镜像原理上讲,在城域 SAN 存储网络上的两套磁盘系统之间的镜像,和在一
个机房内的 SAN 上的两个磁盘系统之间的镜像并没有任何区别。
利用裸光纤将生产中心和灾备中心的 SAN 网络连接起来,构成城域 SAN 网络以
后,利用 VERITAS Storage Foundation 的先进的逻辑卷管理功能,我们就可以非常
方便的实现生产中心磁盘系统和灾备中心磁盘系统之间的镜像了。如下图所示。