Deploy Acronis Agent for ESX/ESXi to each host instead of deploying one to the cluster
Acronis True Image Rescue Media changes SAN signatures of disks, which prevents Microsoft Cluster Service from starting
As a workaround, unplug the USB device and reboot the machine
Acronis productd can back up and restore physical nodes
Acronis Agent for Hyper-V is unable to back up virtual machines (or virtual drives) if the virtual drives storage is allocated on a CSV organized under Windows 2008 R2 environment
Acronis Recovery for Microsoft Exchange is not a cluster-aware application, and does not include support for cluster-related settings or events
Acronis Recovery for SQL Server is not a cluster-aware application, and does not include support for cluster-related settings or events
If you choose to enable the mobilEcho Client Management Server on a cluster, you will need to manually create the mobilEcho Management service on each node. Before you do this, you will need to prepare the cluster by moving the mobilEcho Client Management servers configuration and data files to shared storage that is accessible to all nodes of the cluster.
Backup of virtual machines hosting on failover cluster may fail with non-informative error messages if the user doesn't have enough privileges for the CSV
The PDF in Related Documents describes how to configure print queues within Acronis Files Connect (formerly ExtremeZ-IP) on a Microsoft cluster.
see attached pdf
- PDF/PPT Description: Acronis Files Connect Print Cluster Setup.pdf
Scenarios of server cluster restore using Acronis Backup & Recovery
In some cases cluster logs are required for investigation. To get the required logs, please follow the steps in the Solution section of this article.
These solutions can be applied to Microsoft Windows Server 2003 and 2008 within a cluster. You can use one of the two provided methods to collect the logs:
Acronis Backup Advanced supports the following Exchange cluster configurations.
Exchange 2003 Cluster and Single Copy Cluster (SCC) for Exchange 2007
Both configurations are failover cluster solutions based on a shared storage. Each of them uses a single copy of a storage group on storage that is shared between the cluster nodes. Only one cluster node can access (manage) shared data at a time. The node that is currently managing shared data is called an active node. Other nodes are called passive or standby.
Install Agent for Windows inside the virtual machines
How to change a volume's cluster size