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

availability, recovery semantics, and guarantees Vasiliki Kalavri | Boston University 2020 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? Vasiliki failures. 7 Vasiliki Kalavri | Boston University 2020 Recovery types 8 Vasiliki Kalavri | Boston University 2020 Recovery types • Precise recovery (exactly-once) • It hides the effects of a failure

way of defining trigger hysteresis by introducing an optional second trigger expression called ’recovery expression’ where you can separately define the conditions that have to be met for the trigger to generated. You can use the problem expression as basis (then it works the same way as before), the recovery expression as basis, or even select ’None’ in which case the trigger will always remain in problem Trigger hysteresis 5.9 Recovery operations Being notified on problem recovery has become easier in Zabbix. If previously there was the slightly confusing concept of a special ”Recovery message” or the possibility

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 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}

indicated using the {HOST.NAME} macro • Problem notifications have been made more distinct from recovery notifications in the message subject 7 Item value preprocessing When it comes to preprocessing is not associated with a problem in any way. This means that if an event is either a problem or recovery event, it will not be deleted until the related problem record is removed. Additionally, the housekeeper Template Module Interfaces SNMPv2) leads to a problem resolving prematurely. Fixed by adding a recovery expression disallowing this in 3.4.9. For details, see: ZBX-13278. Known issues for 3.4.0 - 3

been added, similar to other actions in Zabbix. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending service actions support problem escalation scenarios. New message templates Service, Service recovery, and Service update have been added to media types and should be defined to enable correct sending {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} - resolve to a partially evaluated trigger or recovery expression, where only item-based functions are applied; • {FUNCTION.VALUE<1-9>}, {FUNCTION.RECOVERY.VALUE<1-9>} -

first rendering time of the notification. • The Display OK triggers for setting is now applied to recovery type notifications. That becomes relevant if it is shorter than the regular problem notification containing the message body and title in response, if the client receives the same notification ID. • Recovery of a crashed tab is implemented. Any tab that is still able to execute JavaStript will detect a Templates you can import it manually into Zabbix. Macros A new {EVENT.RECOVERY.NAME} macro is supported, returning the recovery event name. {TRIGGER.ID} macro is now supported in trigger tag values.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.3. Automatic Two-phase Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 13. Database Validation and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 13.2. Database Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

per second. For each recovered event, an event_recovery record is created. Normally most of the events will be recovered so we can assume one event_recovery record per event. That means additional 80 bytes service - Oracle service name. oracle.fra.stats[connString,,,] Fast Recovery Area (FRA) statistics. JSON object connString - URI or session name. user, password - Oracle pgsql.dbstat.conflicts.rate[”{#DBNAME}”] - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers). pgsql.dbstat.temp_files.rate[”{#DBNAME}”]

Control Functions .......................................................................285 9.26.4. Recovery Control Functions ....................................................................287 9.26.5 ...............................................553 24.3. Continuous Archiving and Point-in-Time Recovery (PITR)................................554 24.3.1. Setting Up WAL Archiving.................... ................584 26. Recovery Configuration ....................................................................................................586 26.1. Archive Recovery Settings ...............