This has been fixed in the latest version of Acronis Backup & Recovery 10
Linux-based bootable media
When restoring ESXi configuration onto a new or existing physical machine, the local datastores are not attached after ESXi boots up. This is a known issue of 8184 build of Acronis vmProtect 8
You need to collect restore operation log and save it to an external/flash drive, a network share or a floppy disk
Deployment on Dell Precision workstations results in drive letters in reverse order
You will need Acronis Bootable Media with the Acronis Snap Deploy 4 Master Image Creator component
This article describes the troubleshooting steps in case a network share cannot be selected as a backup destination. "The drive is not ready" error is typically related to the share specifics which should be revealed. One of the common solutions is to access the share using its IP address instead of the hostname
This has been fixed
You may need to do a sector-by-sector restore of a disk backup if it has a file system that was corrupted before the backup was made
What is Acronis Startup Recovery Manager and what features it offers
Acronis Disk Director only supports disks with 512 bytes logical sector size
This article applies to:
The typical reason for a VM to be missing in the backup or replication wizard (unavailable for selection) is that this VM was created by Acronis vmProtect and is in fact a replica VM. It is not possible to back up replica VMs by default, however this may be possible after additional adjustments
During backup or recovery operation the hard drive is grayed out when using Intel Smart Response technology
While Restoring LVM volume created with Acronis Backup & Recovery 10 in Sector-by-Sector mode ask for reboot before restore is finished
Switch to Windows-like disk representation
Change to a different drive letter that has not been already assigned
Symptoms
An attempt to save log from Acronis Bootable Media with Linux-like representation fails with the following error message:
Failed to save the log entries to the file
Cause
This is a known issue.
Solution
It is recommended to create Acronis Bootable Media with Windows-like to avoid this issue.
When you boot a Hyper-V virtual machine from Acronis Bootable Media, do not move the mouse in the boot menu and use keyboard to select the necessary component to load
The issue is only with Acronis Bootable Media. As a workaround, convert the disk from Windows
This has been fixed
This has been fixed
This is a known issue with Acronis Bootable Media
As a workaround, use mouse to boot into the full environment
This article applies to:
- Acronis Backup & Recovery 11
- Acronis Backup & Recovery 10
- Acronis Snap Deploy 3
Symptoms
- You install Acronis PXE Server and configure machines to boot from it;
- Machines fail to boot from Acronis PXE Server with the following error:
Acronis Loader fatal error: At least 512 Kb of conventional memory required to start Acronis Loader
Cause
Incorrect work of Intel RAID in BIOS.
You must always use 32-bit drivers for WinPE-based media creation for the purpose of proper hardware recognition (WinPE media created this way will work correctly on 64-bit systems as well). However, for Acronis Universal Restore purposes you'll also need to specify 64-bit system drivers for the system to load correctly after the recovery.
Only older versions of Acronis products support VIA C3 processors
Hit ALT-left SHIFT-NUM LOCK to enable keyboard navigation in Acronis Bootable Media
What a bootable media of an Acronis backup software is and what features it offers
Acronis products allow you to create Linux-based bootable rescue media as well as WinPE-based bootable rescue media
Symptoms
When trying to create a bootable media on a stick with more than 32 GB capacity you get an error message "Media cannot be formatted" or bootable media is created, but the system does not boot from it.