Skip to main content

The last backup failed

Thread needs solution

I just noticed that ATI2016 has been failing on my laptop running Win10 x64. The last successful BU was run on 10/11/2016. It appears that it has been failing to run since then. The source is my boot drive which is a Corsair Force 3 SSD (about 250 GB with 48GB free). The target for the BU is a USB attached WD 3TB Red drive with 1700 GB free. In TI if I click on the "Check for a solution" it goes to the Acroins site and brings up a page stating "58859: Acronis True Image: Backup Fails with "Cannot open a backup on an encrypted volume" or "The backup location was not found on the destination drive".

To my knowledge the volume is not encrypted I have not encrypted the volume) and the location is on the destinaton drive. I can open the destination in the Windows Explorer and TI is able to drill down to the location if I try to change the destination.

The BU location is J:\BU\Acronis, I just changed the BU location to J:\BU\Acronis\W700 and it is now working. I've created three incremental BUs with the new location, however I'm surprised that TI did not create a full backup as the first BU. Any ideas why it did not? Following are the three BU names that were created.

J:\BU\Acronis\W700\W700-Incremental_inc_b1_s3_v1.tib
J:\BU\Acronis\W700\W700-Incremental_inc_b1_s4_v1.tib
J:\BU\Acronis\W700\W700-Incremental_W700_BU5_D2016-10-24_T0951_inc_b1_s5_v1.tib

As you can see the third BU I modified the TIS file to customize the BU file name.

Per the options, TI backups daily at 0013 hours, the scheme is Incrementas and should create a full version after every 5 incremental versions, automatic cleanup is to store no more than 10 recent version chains.

I just looked at the TIS file and noticed that TI is pointing to the original location for the first two BUs, see the following. In that TI is NOT able to use the files in the original location I don't think I could restore using the FULL BU.

<volume_location device_instance_id="" uri="J:\BU\Acronis\W700-Incremental_W700_D2016-10-10_T0014_W700_D2016-10-10_T0014_full_b1_s1_v1.tib" volume_id="2258989531" />
                        <volume_location device_instance_id="" uri="J:\BU\Acronis\W700-Incremental_W700_D2016-10-11_T0013_W700_D2016-10-11_T0013_inc_b1_s2_v1.tib" volume_id="627624180" />
                        <volume_location device_instance_id="" uri="J:\BU\Acronis\W700\W700-Incremental_inc_b1_s3_v1.tib" volume_id="2619801998" />
                        <volume_location device_instance_id="" uri="J:\BU\Acronis\W700\W700-Incremental_inc_b1_s4_v1.tib" volume_id="580000094" />
                        <volume_location device_instance_id="" uri="J:\BU\Acronis\W700\W700-Incremental_W700_BU5_D2016-10-24_T0951_inc_b1_s5_v1.tib" volume_id="2712235839" />
                        <volume_location device_instance_id="STORAGE\VOLUME\{9191AE93-EFB5-11E5-BDC5-806E6F6E6963}#0000000008100000" uri="J:\BU\Acronis\W700\W700-Incremental_W700_BU6_D2016-10-24_T1112_inc_b1_s6_v1.tib" volume_id="3891978520" />
                        <volume_location device_instance_id="STORAGE\VOLUME\{9191AE93-EFB5-11E5-BDC5-806E6F6E6963}#0000000008100000" uri="J:\BU\Acronis\W700\W700-Incremental_W700_BU6_D2016-10-24_T1112_inc_b1_s6_v1.tib" volume_id="3891978520" />
                        <volume_location device_instance_id="STORAGE\VOLUME\{9191AE93-EFB5-11E5-BDC5-806E6F6E6963}#0000000008100000" uri="J:\BU\Acronis\W700\@task@_@MACHINE@_BU@EXEC@_D@DATE@_T@TIME@.tib" volume_id="0" />

Thus one question I have is why is TI having a problem with the original folder?

I just completed my test using the new location, although BU setup in TI specifies that an incremental set consist of 5 files this set comprised 7 incremental BUs and one full. Two of the incremetal BUs are in the old folder and 4 incremental and one full are in the new folder. I'm looking at the TIS file and I don't see where the value for a set (e.g. how many BUs are in a set) is established.

 

0 Users found this helpful

Hard to say.  Acronis bases the backkup disks by UUID which is a hardware identifier of the disk.  Any change to the disk parition scheme will give it a new UUID (for instance, on a source disk running Windows 10, any Windows 10 "upgrades" will create a new recovery partition, hence, changing the UUID of the drive and requiring us to go in and re-pick the source again.

If/when Acronis fails becuase the drive is not found or unknown, I can usually go into the backup script and re-select the source and destination again (even if they appear to us to be the same, they may not be based on UUID) and then backups will typically pick up again.

As for Acronis spreading your backup in 2 locations, it "should" still be usable if you were to use your offline recovery media and move all of the files into the same folder ahead of time so that Acronis can see all of the files chain in one loation.

Alternatively, in Windows, if you wanted to move the files manually via Windows file explorer so they were in one spot again, you could then attempt to "validate" the backup after moving the files.  That should trigger ACronis to  throw up an error that the files are missing and ask you to ignore them (hence dropping them from the database as a reference) or locate them (hence updating the location of the files in the database).  You could then point the files to where they were moved and that should get things back on track again.