Two types of user access, or access roles, are available for clients.
User: Can monitor data backups, exceptional activities, and exceptional usage/performance factors, make limited configuration changes (some are best left to Acronis engineers), activate servers, and initiate recovery.
Admin: This type can perform the same actions as the User as well as additional actions: add account users, change account user’s access role, certify a continuity server.
User access is set on the Add User page, and can be changed on the User page.
Alerts are visible to account users. There are four types of alerts:
Client: Some are initiated in response to client-defined criteria. These are consumption threshold violations specific to named servers and are defined on the Server Details Alerts Tab. There are others like: “CAFS: error occurred during Backup process” and “Protected Disk Resize.” They are visible to all access roles.
Internal Only: These are initiated for certain conditions monitored by Recovery Console. These are visible only to users with the access role “super” (i.e., Acronis engineers).
Partner Wide: Similarly to Client alerts, these are specific to named servers and are defined on the Server Details Alerts Tab. They are visible to the partner’s users and the users of their accounts.
System Wide: These are visible only to users with the access role “super.”
Acronis’s business continuity servers can be tested to prove each server can run your applications seamlessly—before you need to use them in a DR situation. Testing can prove the DR environment is configured properly and your written procedures (runbook) are complete and correct.
Acronis delivers peace of mind founded on the evidence of successful testing. Should you need to execute an actual failover, you can be confident in an uneventful success.
Testing is convenient. Testing has no impact on your production environment. It can be scheduled to easily accommodate the availability of people and resources, it permits the efficient and optimal utilization of subject matter experts.
Testing is a tool you can apply to different scopes. For example, you can test failover for an individual server, an application stack, or your entire data center.
Testing easily helps you identify elements that typically add complexity to failover, such as DNS changes, login scripts, and static IP addresses, and create and validate solutions. Testing enables you to develop a complete runbook that you can be confident in. There is a runbook template in the Support > Resources area of Recovery Console to get you started.
Support tickets can have one of four priorities.
Critical. Use when service is not accessible and end users are not able to access Primary Services.
High. Use when service is not accessible, but no end user outage to Primary Services is experienced.
Medium. Use when service is not accessible but a work around is available that allows access.
Low. Use for technical questions that do not involve an inaccessible system.