As a workaround, configure the network settings manually in command line when booted in WinPE
Configuration
This is a limitation. Configure the network settings manually in command line when booted in WinPE
Configure certain Windows events to be considered as critical
Configuring Acronis Access on the first run
This article applies to:
- Acronis Access
Click Configure -> ESX Hosts
Agent for vCloud obtains events from vCloud Director via a RabbitMQ AMQP broker
Configuring Acronis Agent for vCloud
The issue is caused by the corruption in the registry key that contains information on VMware vCenter Integration
Recommendations in this article target deployment of Acronis Backup in environments of 200 to 1000 machines.
(!) If your environment is 1000+ machines, please contact Acronis Customer Central with a reference to this article. Acronis Professionals will analyze your environment and provide you with ad hoc recommendations.
If there is not enough storage space to create the temporary snapshot file, the backup operation will fail with an error message similar to the following one:
Not enough storage is available to process this command
This article describes what this temporary file is and how to modify its size. For detailed description of the snapshot process, see SnapAPI.
Acronis Files Advanced (formerly Access Advanced) 6.1 and later has a command line tool which collects information about your configuration. This tool provides an easy way to give our support team all the necessary information about your setup in case you are experiencing issues. When running the tool on a machine with a single Gateway Server or a single Files Advanced Server installed, only the information about the installed component will be collected.
Symptoms
When backing up a Hyper-V Virtual Machine running on Windows Hyper-V Server 2016 (Windows 10) or higher AND this Virtual Machine is running on outdated VM configuration version 5.0, then Changed Block Tracking information for this virtual machine cannot be retrieved and entire virtual disks are processed during backup.
Example of backup log where the problem is observed – both virtual disks are read from start to end instead of reading only changed sectors reported by CBT: