# VMware Data Recovery 管理员指南 ZH CN-000193-00 vmware $ ^{®} $ 您可以在 VMware 的网站上找到最新的技术文档，网址为 http://www.vmware.com/cn/support/ VMware 网站还提供了最新的产品更新。 如果您对本文档有任何意见和建议，请将您的反馈提交到： docfeedback@vmware VMware Data Recovery 7 备份虚拟机 7 卷影复制服务 8 删除重复存储的优点 8 2 安装 VMware Data Recovery 9 VMware Data Recovery 系统要求 9 安装客户端插件 9 安装备份设备 10 向备份设备中添加硬盘 10 3 配置 VMware Data Recovery 13 启动备份设备 创建备份作业 15 还原虚拟机 16 VMware Data Recovery 故障排除 18 索引 21 ## 关于本文档 《VMware Data Recovery 管理员指南》包含为中小型企业建立备份解决方案的信息。 ## 目标读者 本文档适用于需要使用 VMware Data Recovery 提供备份解决方案的用户。本书的目标读者为熟悉虚拟机技术和数据中心操作且具有丰富经验的

system crashes before the messaging server receives an acknowledgement from the consumer, then on recovery, the message will be available to be delivered to a consumer again. With point-to-point messaging effective to disconnect the brokers, while the mirror events are always captured. ## Disaster & Recovery Considerations As you use the mirror option to replicate data across datacenters, you have to take might have been delivered but that will not have been reflected in the delivery count. During the recovery phase, the server will not have knowledge of that and will deliver the message with redelivered

Challenges of reconfiguration • Ensure result correctness • reconfiguration mechanism often relies on fault-tolerance mechanism • State re-partitioning and migration • minimize communication • keep duration

availability, recovery semantics, and guarantees Vasiliki (Vasia) Kalavri vkalavri@bu.edu ## Today's topics • High-availability and fault-tolerance in distributed stream processing • Recovery semantics against failures and guarantee correct results after recovery? • how can we ensure minimal downtime and fast recovery? • how can we hide recovery side-effects from downstream applications? ## What is failures. ## Recovery types ## Recovery types • Precise recovery (exactly-once) • It hides the effects of a failure perfectly • Post-failure output is identical to no-failure ## Recovery types • Precise

Exactly-once fault-tolerance in Apache Flink Vasiliki (Vasia) Kalavri vkalavri@bu.edu Go read his PhD thesis: http://kth.diva-portal.org/smash/get/diva2:1240814/FULLTEXT01.pdf ## Fault-tolerance approaches sums of even and odd numbers • The snapshot contains the source offset 5 and the sums 6 and 9 ## Recovery process 1. Stop and restart the application. All operators have empty state.  ## Recovery process 1. Stop and restart the application. All operators have empty state. 2. Initialize stateful operators from the latest checkpoint. 3. Resume processing. Recovery 2: Reset application

point-in-time recovery (PITR) .....324 22.3.1. Setting up WAL archiving .....325 22.3.2. Making a Base Backup .....327 22.3.3. Recovering with an On-line Backup .....328 22.3.3.1. Recovery Settings not speculate what you think went wrong, what “it seemed to do”, or which part of the program has a fault. If you are not familiar with the implementation you would probably guess wrong and not help us a following options are intended for work on the PostgreSQL source, and in some cases to assist with recovery of severely damaged databases. There should be no reason to use them in a production database setup

6.25 139 Release 6.25.3 139 Cluster Management 139 Query Processing 139 Server 140 Disaster Recovery 140 Release 6.25.2 140 New and Changed Features 140 Server 140 Cluster Management 141 Resolved Master Redundancy 291 About the Greenplum Segments 291 Segment Redundancy 292 Segment Failover and Recovery 292 Example Segment Host Hardware Stack 293 Example Segment Disk Layout 294 About the Greenplum Redundancy and Failover in Greenplum Database 313 About Segment Mirroring 313 Segment Failover and Recovery 314 About Master Mirroring 314 About Interconnect Redundancy 315 About Database Statistics in

jpg) O'REILLY Introducing Istio Service Mesh for Microservices Build and Deploy Resilient, Fault-Tolerant Cloud Native Applications ![Image](/uploads/documents/9/c/7/e/9c7ef33035188e2a303c307c3a3e22a2/p2_7

ACTION} added – {EVENT.SEVERITY} added – {EVENT.NSEVERITY} added • Default messages for operations, recovery operations and update operations have been changed to reflect the updated macros New graph widget directly in the ’events’ and ’problem’ tables at the moment when an event is generated for a problem or recovery. Zabbix frontend can search and query the respective tables directly. This change leads to a better that for internal events the name contains an error message why an object changed its state; upon recovery no name is used. For discovery and auto-registration events no name is used. A new {EVENT.NAME}

duration of an event. • {EVENT.TAGSJSON} and {EVENT.RECOVERY.TAGSJSON} macros will resolve to a JSON array containing event tag objects or recovery event tag objects. For more details, see Macros supported Global correlation conditions • Problem update screen • Action operation details – in the Operations, Recovery operations and Update operations tabs • Maintenance period details – in the Periods tab • Discovery operation, UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance and resilience. Zabbix operates on market leading versions. Zabbix server is tested on the