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.
Backup for OpenStack cloud
Hi All, Now a days there is lot of buzz about OpenStack cloud. I would like to check how can we deploy Backup infrastrucute in an OpenStack cloud enviornment. One way is like building backup domain (with Master, media, storage and client) in each tenant. 2nd way, putting Master server outisde of each tenant and just - Media, Storage inside tenant to backup tenant VMs as shown in diagram. in this case Tenant VMs have to connect to master server via Media agent and vice versa. Have anyone deployed OpenStack cloud in thier enviornment and which backup software has been deployed. Does Netbackup or any other backup software supports KVM hypervisor to take image level snapshot of VMs?