User`s guide

Network share with a backup not found by standalone Acronis True Image OEM Quick Backup

There can be several reasons why you are not able to locate the desired network share when using a

standalone version of Acronis True Image. See the Acronis Support KB article "Standalone Version of

Acronis True Image Cannot Find Network Share with an Image Archive

(http://kb.acronis.com/content/1550)".

You cannot log on to a network share after booting to rescue media

How to solve the problem when a standalone version of Acronis True Image OEM Quick Backup

cannot log you on to the network where the image archive is, and keeps asking for the user name

and password again and again. See the Acronis Support KB article "Standalone Version of Acronis

True Image Recovery Wizard Keeps Asking for User Name and Password When Trying to Restore an

Image from a Network Share (http://kb.acronis.com/content/1551)".

New user profile created after recovering My mail backup of Microsoft Outlook

You can find the solution in the Acronis Support KB article "Restoring E-Mail Backup of Microsoft

Outlook Creates a New Profile (http://kb.acronis.com/content/1804)".

You cannot get access to recovered files or folders

After recovering files/folders with Acronis True Image you get "Access denied" message when trying

to access them. To solve the issue, see the Acronis Support KB article "Access Denied to Files or

Folders Restored with Acronis True Image (http://kb.acronis.com/content/1520)".

15.5 Bootability after recovery issues

If a system was bootable at the time of backup, you expect that it will boot after recovery. However,

the information the operating system stores and uses for booting up may have become outdated at

the time of recovery, especially if you change partition sizes, locations or destination drives. Acronis

True Image OEM Quick Backup automatically updates Windows loaders after recovery. Other loaders

might also be fixed, but there are cases when you have to re-activate the loaders. Specifically when

you recover Linux volume in a dual boot configuration, it is sometimes necessary to apply fixes or

make booting changes so that Linux can boot and load correctly. Below is a summary of typical

situations that require additional user actions when the recovered operating system becomes

unbootable.

The machine BIOS is configured to boot from another hard disk drive (HDD).

Solution: Configure the BIOS to boot from the HDD where the operating system resides.

In some cases BIOS has two menus for setting the boot sequence: one for setting the boot devices priority and

the other - for setting the HDD boot order.

Windows was recovered to a dynamic volume that cannot be set bootable

Solution: Recover Windows to a basic or simple dynamic volume.

A system partition was recovered to a disk that does not have an MBR

When you configure recovery of a system partition to a disk that does not have an MBR, the program

prompts whether you want to recover the MBR along with the system partition. Opt for not

recovering only if you do not want the system to be bootable.

Solution: Recover the partition once again along with the MBR of the corresponding disk.