Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V
- Section I. Overview of Resiliency Platform
- Section II. Preparing your environment
- Using array-based replication
- Protecting Hyper-V virtual machines using array-based replication - an overview
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
- Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
- Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
- Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
- Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
- Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
- Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Understanding the role of resiliency groups in disaster recovery operations
- How Resiliency Platform configures disaster recovery protection for virtual machines
- Prerequisites for configuring Hyper-V virtual machines for disaster recovery
- Limitations for virtual machine disaster recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Managing virtual machines for remote recovery (DR) in vCloud
- Section IV. Managing disaster recovery
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- Monitoring risks, reports, and activites
- About the Resiliency Platform Dashboard
- Understanding asset types
- Displaying an overview of your assets
- About risk insight
- Displaying risk information
- Predefined risks in Resiliency Platform
- Viewing the current risk report
- Viewing the historical risk report
- Viewing reports
- Managing activities
- Viewing activities
- Aborting a running activity
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
- Glossary
About risk insight
The objective of the Risk Insight feature is to notify you about the vulnerabilities that might impact the recoverability or continuity of your protected assets.
Risk Insight detects the changes to the state and configuration of your protected assets. It identifies if there is a risk to the recoverability or continuity of your protected assets.
Veritas Resiliency Platform also enables you to set up the replication lag threshold or service level threshold. Risk insight alerts you when the replication lags beyond the threshold that you specified.
Risk insight generates two types of reports:
Current risk reports: Provides the summary and detail information about all the current risks in your data center.
Historical risk reports: Provides a summary and a detailed analysis of information about the risks in your environment during the specified period.
These reports help you take actions to prevent such risks. The historical risk data is purged after a period of two years.
The risks covered by risk insight can be classified into three main categories:
Table:
Risk Type | Description |
|---|---|
Recoverability | Risks that may impact the ability to recover and run the application on the recovery site. |
Continuity | Risks that may impact the ability to run your applications without disruption either on your production site or on your recovery site. |
SLA | Risks that may impact the ability to fulfill the service level agreements (SLA) for your applications. |
On the basis of criticality, the risks can be classified into two types:
Table:
| Risk type | Description |
|---|---|
Error | A risk that disrupts any stated goals of the product. An error must be fixed to make the product work as expected. |
Warning | A risk that jeopardizes any stated goals of the product. A warning alerts you about a potential problem in your environment. |