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
- Managing disaster recovery network mapping
- Using array-based replication
- Section III. Working with resiliency groups
- Managing resiliency groups
- Configuring resiliency groups for remote recovery
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Section IV. Managing disaster recovery
- Managing resiliency plans
- Creating a new resiliency plan template
- Monitoring risks, reports, and activites
- Managing evacuation plans
- Appendix A. General troubleshooting
- Appendix B. Sample policy and trust relationships for AWS
About permissions for operations in the console
Users that are configured for Resiliency Platform have permission by default to view the web console but not to perform any operations. Permissions for operations must be assigned separately by a Resiliency Platform administrator, who assigns the appropriate personas to users or groups. A persona is a role with access to a set of operations. The administrator can further limit the scope of some operations by selecting the objects, such as resiliency groups, to which the user has access.
For example, an administrator can assign one user the permission to perform operations on resiliency group RG1 and assign another user the permission to perform operations on RG2. If more resiliency groups are added later, the administrator needs to update permissions to assign access to the new resiliency groups.
Some objects, such as resiliency plans or virtual business services, can include multiple resiliency groups. To perform an operation on such an object, a user must have access to all its resiliency groups. Otherwise, the operation fails.
For more information on setting up user access to operations, refer to the Deployment Guide.