Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Integrating with InfoScale Operations Manager
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
About risks
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. A periodic or schedule scan will generate the risk on the Resiliency Platform components. A periodic scan of every 30 minutes is run by the scheduler.
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 types
Risk category | 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 types
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. |
From 3.2 onwards, you can probe and suppress a risk based on which component of Resiliency Platform the risk has occurred.
Probing a risk is way of evaluating a risk to check whether the risk is eliminated or still exists at the Resiliency Platform component. You cannot probe all the risks in the risk view. The risks which cannot be probed have details about the risk resolution. You can perform the given steps and probe the risk again. You have to wait for some time the to see the apply the changes.
For example, an IMS is disconnected due to network issues. The risk is then raised by the Resiliency Platform. When you probe this risk, details of this risk display what steps can be done to resolve this risk. There are some risks which cannot be probed. For those risks, you have to fix the risk and the probe it accordingly.
When you probe a risk, the details panel also displays a link to the proposed resolution for the risk. On clicking the link, the risk pop up is closed and you are redirected to the respective resolution page.
You can avoid a risk using suppress option on the risk view. You can suppress a risk for specific time; for few minutes or hours but cannot suppress a risk for indefinite period. If a risk is active after the suppress period is over, then it will appear under the Active Risks view. You can probe that risk or you can again suppress it for some time. Suppress option is available for all the risk in the Resiliency Platform. Suppressed risks will be seen in Risk view > Suppressed Risks.
Note:
Risks are not generated for resiliency groups that are in maintenance mode. If a risk was raised before the resiliency group was placed in maintenance mode and that risk persists after exiting the mode, then the risk is shown.
See Managing risks.