recovery point

After upgrading from Acronis vmProtect 7 to Acronis vmProtect 8, recovery points are listed in incorrect order by default in the Recovery wizard. The Acronis vmProtect 7 recovery points are selected by default instead of Acronis vmProtect 8 recovery points even if they are newer. This happens if user continues backing up to archive created with Acronis vmProtect 7. This is a UI issue only. Recovery can be done from any recovery point regardless of which version of Acronis vmProtect was used to create them. Another problem is that first backup with Acronis vmProtect 8 into archive created by Acronis vmProtect 7 will be full one due to the same reasons. The subsequent backups will be incremental ones.

Description

Archive 12 format is a main archive type for Acronis Backup 12.5. It is used to back up any data, including mobile data, applications, application-aware backup, MacOS, Oracle DB etc

It is a single .tibx file for each backup chain: Full or Differential + all Incremental files that depend on it

Metadata is stored inside the archive, checksummed and verified (there is no separate xml file for metadata).

Symptoms

You receive the following error when browsing recovery points for a backup:

Failed to resolve the backup. The specified file does not exist.

If you check the backup location, the first volume of the archive is missing.

E.g. a complete set of archive volumes looks like this

[Machine Name]-[Plan ID]-[Unique ID]A.tibx

[Machine Name]-[Plan ID]-[Unique ID]A-0001.tibx

[Machine Name]-[Plan ID]-[Unique ID]A-0002.tibx

Symptoms

Backup in Version 12 format fails with following error message:
error 0x40011: The specified file does not exist

Symptoms

  • You created a backup plan with Acronis Cloud storage as a destination. You run the backup plan successfully 
  • When trying to restore any recovery point, the process just hangs on Loading
  • When checking the PCS logs on the agent machine, you see the error message like:
2019-05-22T11:46:16:889+01:00 4627423232 E00000000: io: failed to open '/1/mac1-FC34F9B9-CF1A-4013-887E-215E3039A33C-32F65865-2379-4978-B7CE-5ABF6F288D30A.xml' (pcs_err=-13)