(CEP-17017) Multi service level objective using Veritas Resiliency Platform (VRP) and NetBackup
Interaction Date: Feb 2 – Feb 26, 2021 Interaction Type: Product Overview / Demo (1:1 Demo) The NetBackup product management team is looking for customers to provide feedback on VMware based workloads with dual protection feature using both NetBackup and Veritas Resiliency Platform (VRP). If you are interested in participating in this or other exciting interactions, make sure you are registered in the program (https://cpep.veritas.com) then contact us at customer.engagement@veritas.com to be included in this session.
(CEP-9788) VRP - Disaster Recovery in the Public Cloud
Interaction Date: March 4 – 18, 2019 Interaction Type: Online Survey The Veritas Product Management team would like to understand your usages of cloud as a disaster recovery target and also the problems and challenges you face with on premise or cloud DR. If you are interested in participating in this or other exciting interactions, make sure you are registered in the program (https://cpep.veritas.com) then contact us at customer.engagement@veritas.com to be included in this session.(CEP-7584) VRP Tech Day
Interaction Date: October 15, 2018 Interaction Type:On-Site Visit Veritas Resiliency Platform Engineers met on-site with a customer to review requirements and helped prepare a disaster recovery solution to work in their environment. If you are interested in participating in this or other exciting interactions, make sure you are registered in the program (https://cpep.veritas.com) then contact us at customer.engagement@veritas.com to be included in this session.(CEP-4483) NetBackup, CloudPoint, VRP, and Access Personas Survey
Interaction Dates: 6/13/2018 - 6/21/2018 Interaction Type: Online Survey The Veritas Customer Experience team is constantly updating its customer & user profiles or personas to ensure products are always built with them front and center. To that end, we are looking for your input to update our user profiles. If you are interested in participating in this or other exciting interactions, make sure you are registered in the program (https://cpep.veritas.com) then contact us at customer.engagement@veritas.com to be included in this session.
Video - Migrating your assets to different availability zones of AWS
Using Veritas Resiliency Platform you can migrate your assets to Amazon Web Services (AWS) cloud. The following video covers how to migrate your assets to the different availability zones of AWS. Some of the reasons for migrating to different availability zones are: high availability and load balancing, or to retain your VMware cluster configuration of the source data center on the target data center. The video shows how to club your assets to form a resiliency group and configure this resiliency group for disaster recovery. While configuring, you need to choose the replication technology, select the Replication Gateways that are mapped to different availability zones, map the networks to successfully protect the assets or virtual machines.Evacuating your assets using Veritas Resiliency Platform
The Evacuation Plan feature of Veritas Resiliency Platform lets you evacuate all the assets from your production data center to your recovery data center. Instead of individually moving your assets to the recovery center, you can save your time by adding these assets to the evacuation plan and then execute the plan with a single click operation. Resiliency Platform supports evacuation to various recovery data centers namely Azure, Amazon Web Services, vCloud Director, and even to your on-premises data center. Use the evacuation plan template to define the sequence in which the virtual business services (VBS) should be migrated from the production data center to the recovery data center. Resiliency groups that do not belong to any VBSs, are appended at the end of the evacuation plan workflow after the VBS. If you have not configured any VBSs, then the evacuation plan is created using only the resiliency groups. Having a VBS is not compulsory. An evacuation plan has Priorities. You can add the VBSs to different priority levels but the ordering of resiliency groups is done by the Resiliency Platform. You can also define the VBS priority within the priority group. When you have a large number of VBSs, then up to 5 VBSs within a priority group are migrated in parallel to the recovery data center. Similarly, if you have a large number of resiliency groups, up to 10 resiliency groups are migrated in parallel. Continue on failures is another functionality of an evacuation plan. If an asset within a VBS or a resiliency group fails to recover, the evacuation plan skips the asset and continues the process for the remaining assets. You have the option to select this checkbox while creating the evacuation plan. If you choose not to select the checkbox, then the evacuation process stops till you have fixed the problem. For a VBS or a resiliency group to successfully evacuate to the target data center, it should meet the following criteria: ■ VBS or resiliency group that belong to the evacuation plan must be configured for disaster recovery ■ VBS can contain resiliency groups some of which are configured for disaster recovery and some using the service objective with data availability as Copy. ■ Resiliency group must belong to only one VBS. After successfully creating an evacuation plan, you can perform operations such as Rehearse evacuation, Cleanup rehearse evacuation, Evacuate or Regenerate the plan. It is recommended that you perform a rehearsal to ensure that the assets are evacuated properly. After rehearsal you can run the cleanup rehearse operation to delete all the temporary objects that were created during rehearsal. At a later point in time if you make some changes to the VBSs or the resiliency groups, an alert is raised asking you to regenerate the plan. Refer to About evacuation plan for more information on the situations when an alert is raised. To create and run an evacuation plan, you need Manage Evacuation Plans permission. You can also watch the videoshere.
