I can't recover my backup

Kanishk, welcome to these public User Forums.

Sorry but your screen images embedded in your post above do not show in the forum so cannot see the information they were intended to show us?

Please can you confirm what version & build of Acronis True Image you are using here?
If this is ATI 2019, do you have the latest build # 17750 - check on the Account page in the GUI.

The first test here needs to be whether you can validate the backup .tib image file in the location where Acronis has created it, without any actions to delete that file after moving it to a different drive?

If the original backup file validates correctly, then this raises the possibility that the file is being corrupted when it is being copied / moved to your second drive.

And did you move the entire backup chain? You need the full and all incrementals in that chain to be able to successfully recover (at least the full).

Also, I'd go back to the root of the new USB drive and make sure to give all authenticated users full access to the entire USB drive, or at least the folder where the backups are. It doesn't happen often, but when a USB drive is connected to a different machine, it sometimes only has full access granted to the original computer and not to subsequent ones. 

If all files are there and permissions are ruled out, you should be able to validate and recover if there is no corruption.

Keep in mind, I would not import a backup that already exists in your tasks since it is the same data! Instead, use the offline rescue media. Recover to a temp location and then copy and paste from there to the final location.

Right, well I actually deleted the incremental backups. I guess I can't recover my original  backup then, eh?

So I am going to start with the backusp all over again. I've posted images of everything relevant on this folder: https://1drv.ms/f/s!AmqDwfJBzji6gv8m6W4W3ThmDXKDBg

I've listed the drives on my PC, my backup settings, location of backup.

Now to be extra secure, I want to backup my backup to my OneDrive. To do that, I copy the .tib file (before any of its increments were created) to my 1TB EHD in E:\Backup\System Image. The location shouldn't matter, right?

If I wanted to recover this backup after a month or two, the backup shouldn't be corrupted, right? There were no increments to copy since they were not created then so Acronis cannot detect the backup being partially incomplete, right?

Thank you for the further information and screen images (via OneDrive).

Please check that the new backup has run successfully, and that the included Validation action has also run without issue.

I would recommend using the MVP Log Viewer tool to access the messages that Acronis writes to the log files for all the above backup & validation actions - see link in my signature.

The backup has been validated (check OneDrive link to see the picture.) Deleting the increments is the reason that I couldn't restore the backup, isn't it? How does Acronis differentiate between a backup that had no increments and one which does? Isn't the original file untouched either way?

That is good that the new backup has been validated without issue.  There is information about all backup files which Acronis stores in an internal SQLite database, and some other information stored within the backup .tib files themselves that links between the files in a version chain,

The database information should not be modified other than by ATI and if you want to remove the information about backups, then the way to do so is to use the Delete option for the task, then elect to just remove the settings and leave the files the task created in place.  Doing this removes the task information from the database, thus would allow for the files to be added back (as an existing backup) at a later time and from a different location (without conflicting with an existing task).

Providing all the files for a version chain are present, it should be possible to restore from any particular file in the chain without seeing any errors that are caused by missing files.

You can restore a full (as long as it's healthy), at any time.  The key is to use recipe media which has no interaction with the Acronis backup database keeps ng track of everything being done in Windows. So yes, you can copy to OneDrive and copy it back and restore later with rescue media.

You do NOT want to be copying back files that the database already expects to be there and import them if the originals still exist. Using recovery media will be the easiest if you need to do this.

For incremental chains, regardless if using rescue media or True Image in Windows... You need all parts of the incremental up to the one selected. If one is missing (let's say #10 of 20), everything after it is useless. This is how incrementals in all backup programs work based on the design of the incremental scheme.

If you setup the backup scheme in the Windows app as a Custom Scheme using the Full option not incremental or differential then you will not get the errors you talk about when using the Windows app to recover.

I am trying to understand what y'all have written.

The first test here needs to be whether you can validate the backup .tib image file in the location where Acronis has created it, without any actions to delete that file after moving it to a different drive?

What do you mean?

Also, I'd go back to the root of the new USB drive and make sure to give all authenticated users full access to the entire USB drive, or at least the folder where the backups are. It doesn't happen often, but when a USB drive is connected to a different machine, it sometimes only has full access granted to the original computer and not to subsequent ones. 

What do "authenticated users" even mean? If I wanted to give myself permissions, I'd add my account in the list. What's authenticated users then?

Keep in mind, I would not import a backup that already exists in your tasks since it is the same data! Instead, use the offline rescue media. Recover to a temp location and then copy and paste from there to the final location.

I don't understand. If the backup exists in my list already then how would I add it again to the list? Even if I did, why would I want to use offline rescue media when recovering data via the application is much easier?

I would recommend using the MVP Log Viewer tool to access the messages that Acronis writes to the log files for all the above backup & validation actions - see link in my signature.

What purpose would installing this Log Viewer tool serve?

That is good that the new backup has been validated without issue.  There is information about all backup files which Acronis stores in an internal SQLite database, and some other information stored within the backup .tib files themselves that links between the files in a version chain,

I don't understand. Are you saying that when the increments are created that the original backup file's information is modified... internally? Wouldn't this database file be located somewhere? ATI doesn't modify the original TIB file, right?

The database information should not be modified other than by ATI and if you want to remove the information about backups, then the way to do so is to use the Delete option for the task, then elect to just remove the settings and leave the files the task created in place.  Doing this removes the task information from the database, thus would allow for the files to be added back (as an existing backup) at a later time and from a different location (without conflicting with an existing task).

'task information' means?

Are you saying that if I want to backup my file to OneDrive, I should back it up, remove it from the task queue and then copy it to my other external hard disk? So if I just copy my original file directly I won't be able to restore it at a later date?

Providing all the files for a version chain are present, it should be possible to restore from any particular file in the chain without seeing any errors that are caused by missing files.

Wait, missing files means that all files aren't there, right? Also didn't y'all just say that I can't restore backups if the incremental backups aren't also copied?

You can restore a full (as long as it's healthy), at any time.  The key is to use recipe media which has no interaction with the Acronis backup database keeps ng track of everything being done in Windows. So yes, you can copy to OneDrive and copy it back and restore later with rescue media.

But Windows is keeping track of my external hard disks. I don't want to necessarily restore files from an earlier backup using rescue media, why not just use the Acronis media?

You do NOT want to be copying back files that the database already expects to be there and import them if the originals still exist. Using recovery media will be the easiest if you need to do this.

I don't understand. Can you use an example?

For incremental chains, regardless if using rescue media or True Image in Windows... You need all parts of the incremental up to the one selected. If one is missing (let's say #10 of 20), everything after it is useless. This is how incrementals in all backup programs work based on the design of the incremental scheme.

 Wait are you saying that if I have files #1-15 and #17, 19 missing then I can restore files from any backup upto #15?

If you setup the backup scheme in the Windows app as a Custom Scheme using the Full option not incremental or differential then you will not get the errors you talk about when using the Windows app to recover.

Are you talking about just using full backup schemes? Incremental require more care?

The Windows installed True Image application uses an internal database to track all backups created by the app.  The default backup scheme in the app is an incremental scheme as this is what most users desire.  The default Incremental scheme must create a Full backup of the selected data first before it creates any incremental backups as this Full backup is what the remaining incremental backups are based on.

If you use the default scheme and specify that you want 5 incremental backups after the original Full backup then the app will create a Full backup of the data first followed by 5 incremental backups which will only contain any changed data of the original Full backup.  The next backup in sequence after that will be another Full backup.  If you have automatic cleanup enabled then once this Full backup completes the original full and it's associated incremental backups will be deleted.

With the above in mind your backup task chain in this example is a Full + 5 incremental files.   Let's say that you run this backup task chain to drive D on your PC.  You then decide to copy the Full backup file to drive E on your PC.  Then you decide to recover the Full backup using the True Image app in Windows.  The app will give you an error saying that it cannot locate the incremental files for this Full file because they do not exist on the E drive.  The app knows this because of the internal database tracking the app does.

So If you want to copy backups to another drive on your PC and then recover those backups from that drive you must have all backups associated with the backup chain as recorded by the database to make a successful recovery.

To get around this limitation you can use bootable Acronis Recovery Media to recover backups as it knows nothing of the database therefore it will restore up to the and including the last available backup in the chain without the error.

Enchantech wrote:

The Windows installed True Image application uses an internal database to track all backups created by the app.  The default backup scheme in the app is an incremental scheme as this is what most users desire.  The default Incremental scheme must create a Full backup of the selected data first before it creates any incremental backups as this Full backup is what the remaining incremental backups are based on.

If you use the default scheme and specify that you want 5 incremental backups after the original Full backup then the app will create a Full backup of the data first followed by 5 incremental backups which will only contain any changed data of the original Full backup.  The next backup in sequence after that will be another Full backup.  If you have automatic cleanup enabled then once this Full backup completes the original full and it's associated incremental backups will be deleted.

With the above in mind your backup task chain in this example is a Full + 5 incremental files.   Let's say that you run this backup task chain to drive D on your PC.  You then decide to copy the Full backup file to drive E on your PC.  Then you decide to recover the Full backup using the True Image app in Windows.  The app will give you an error saying that it cannot locate the incremental files for this Full file because they do not exist on the E drive.  The app knows this because of the internal database tracking the app does.

So If you want to copy backups to another drive on your PC and then recover those backups from that drive you must have all backups associated with the backup chain as recorded by the database to make a successful recovery.

To get around this limitation you can use bootable Acronis Recovery Media to recover backups as it knows nothing of the database therefore it will restore up to the and including the last available backup in the chain without the error.

But what if I backup my first full backup before the increments were even created? How can the app then say that that backup is invalid? There was only one backup when I copied it to my external hard disk.

But what if I backup my first full backup before the increments were even created? How can the app then say that that backup is invalid? There was only one backup when I copied it to my external hard disk.

There should not be a problem with the backup file if it was copied without error, i.e. create a checksum for the source file then compare that checksum with the value obtained for the copied file on your second disk.  I use an Explorer add-on called HashTab to create / check checksums.

Note: as mentioned previously in this topic, you should not be attempting to add the copied file as an existing backup when the original backup task that created it is still shown in the ATI GUI (unless you rename the stem part of the file name, i.e. change My_partitions_full_b1_s1_v1.tib to Copy_My_partitions_full_b1_s1_v1.tib before adding the file. 
The alternative is to do any recovery using the Acronis bootable Rescue Media instead of from the Windows ATI application.

If your backup task Scheme setting is that of Incremental then the installed application expects to find all incremental versions in the backup chain in the same location as the full backup file.  So if you create an Incremental Scheme backup task, run it to make the initial full backup, copy that backup to another disk and continue to let the task run.  Then later you attempt to restore the copied full version file from the other disk you will get the error.

Reason is that the app database has record of incremental versions associated to that full backup.  If they are not in the same location as the full backup file you get the error.  This is program logic.

Steve Smith wrote:

But what if I backup my first full backup before the increments were even created? How can the app then say that that backup is invalid? There was only one backup when I copied it to my external hard disk.

There should not be a problem with the backup file if it was copied without error, i.e. create a checksum for the source file then compare that checksum with the value obtained for the copied file on your second disk.  I use an Explorer add-on called HashTab to create / check checksums.

Note: as mentioned previously in this topic, you should not be attempting to add the copied file as an existing backup when the original backup task that created it is still shown in the ATI GUI (unless you rename the stem part of the file name, i.e. change My_partitions_full_b1_s1_v1.tib to Copy_My_partitions_full_b1_s1_v1.tib before adding the file. 
The alternative is to do any recovery using the Acronis bootable Rescue Media instead of from the Windows ATI application.

But TeraCopy can do what you said as well if you tick the 'verify' button, right?

Also I should not try to add the same backup because... the program will have a conflict? Two backups having the exact same schemes but created on separate dates will also cause a problem? (They would have the exact same name.)

Also would changing the name corrupt the file? I think the more important question is: How does ATI identify backups? Is there some internal code written onto each backup?

Enchantech wrote:

If your backup task Scheme setting is that of Incremental then the installed application expects to find all incremental versions in the backup chain in the same location as the full backup file.  So if you create an Incremental Scheme backup task, run it to make the initial full backup, copy that backup to another disk and continue to let the task run.  Then later you attempt to restore the copied full version file from the other disk you will get the error.

Reason is that the app database has record of incremental versions associated to that full backup.  If they are not in the same location as the full backup file you get the error.  This is program logic.

Are you saying that if my backup scheme is of an incremental backup, the software expects to find all increments even when the increments haven't been created? So copying an incomplete backup cycle is pointless?

Or are you saying that trying to recover backups from a different hard disk causes error because the software expects to find the backup in G:/ and not E:/? Just to clarify: The software does not care where the backup is from, right? The drive or the name of the folder? Even the file names? (i.e. if all the files are changed together using Bulk Rename Utility?)

  _____

Finally, how do I test if my backup works? I don't have a spare laptop to try the backup on.

But TeraCopy can do what you said as well if you tick the 'verify' button, right?

Also I should not try to add the same backup because... the program will have a conflict? Two backups having the exact same schemes but created on separate dates will also cause a problem? (They would have the exact same name.)

Also would changing the name corrupt the file? I think the more important question is: How does ATI identify backups? Is there some internal code written onto each backup?

I have never used TeraCopy but if verify does the same checksum, it should be fine.

If you add back a backup which has the same name as an existing task in the GUI, then you will see no change in the GUI unless you look at the Recovery point drop-down list of dates/times.  The issue will arise because you will be mixing backups for that existing task with files from a different backup location to the one used by the task.  This is why you should rename the backups held on a different disk to avoid this confusion.

Renaming the file will not corrupt the file.  ATI identifies backups depending on how you are looking at them. 
If you are using the ATI GUI in Windows, then the internal database if used in conjunction with the information stored in the GUI for the task.
If you use the standalone ATI Rescue Media (offline from Windows), then ATI identifies backups based only on the file names and doesn't use the internal database etc.

Are you saying that if my backup scheme is of an incremental backup, the software expects to find all increments even when the increments haven't been created? So copying an incomplete backup cycle is pointless?

If you are using the ATI GUI and using the same name as a task known in the GUI, then ATI will throw up errors if it deems that Incremental files which have been created using the GUI are not found.  This is because the internal database 'knows' about the missing files.

If you are using the standalone ATI Rescue Media, then there should be no issue provided the Incremental version chain is complete up to the last file in the chain, i.e. you have all the files in the chain with nothing missing, so files 1, 2 ,3, 4, 5 etc or 1,2,3

Or are you saying that trying to recover backups from a different hard disk causes error because the software expects to find the backup in G:/ and not E:/? Just to clarify: The software does not care where the backup is from, right? The drive or the name of the folder? Even the file names? (i.e. if all the files are changed together using Bulk Rename Utility?)

Only if using the ATI GUI and where the GUI already has a task using the same name for the files and those files are stored in a different location.

If using the standalone ATI Rescue Media, then it doesn't care where the files are stored or how they are named so long as the required files are present and correct.

If you do choose to rename files using a Bulk Rename Utility, then please only rename the stem part of the file name, leaving the _full_ / _inc_ part as it is, as this shows exactly what files belong to what version chain.

Finally, how do I test if my backup works? I don't have a spare laptop to try the backup on.  

You don't need a spare laptop - just a spare disk drive if you want to prove that your backup is good and could be used in the event of a major recovery being needed.

Otherwise, the best you can do is do a validation of the backup chain, and test doing some recovery tests by restoring random files or folders to an temporary alternative location.

Investing in a spare laptop disk drive would be the ideal method, as this would allow you to perform a full disk recovery, then to swap out your working drive and replace by the spare and test that the laptop boots fine.  All without putting your working drive at risk, plus with the benefit of having a ready working spare drive.

If you add back a backup which has the same name as an existing task in the GUI, then you will see no change in the GUI unless you look at the Recovery point drop-down list of dates/times.  The issue will arise because you will be mixing backups for that existing task with files from a different backup location to the one used by the task.  This is why you should rename the backups held on a different disk to avoid this confusion.

What do you mean by 'no change'? 'no change' as in there won't be any problems or 'no change' as in there won't be a new entry in the backups' list?

Issue meaning seeing history of both backups? That's fine. Would I be able to recover despite the two having the same name?

Renaming the file will not corrupt the file.  ATI identifies backups depending on how you are looking at them. 
If you are using the ATI GUI in Windows, then the internal database if used in conjunction with the information stored in the GUI for the task.
If you use the standalone ATI Rescue Media (offline from Windows), then ATI identifies backups based only on the file names and doesn't use the internal database etc.

How can there be an internal database or information stored on the application if I am recovering a file? ATI retains information of all backups it has ever done even if they are deleted in the application? What happens if you are restoring the data on a different PC? Then there can't be an internal database or any information, right?

If you are using the ATI GUI and using the same name as a task known in the GUI, then ATI will throw up errors if it deems that Incremental files which have been created using the GUI are not found.  This is because the internal database 'knows' about the missing files.

When you say "a task known" do you mean known in the history of all backups that the application has ever done or known from the list of current backups?

If I wanted to test recovering files from a duplicated backup cycle then I would have to first change the name of the backup? If that were the case, would the application simply lose its history of the backup? Hence I would be able to backup data from the renamed backup despite it not having any of the increments that my main backup does?

If you are using the standalone ATI Rescue Media, then there should be no issue provided the Incremental version chain is complete up to the last file in the chain, i.e. you have all the files in the chain with nothing missing, so files 1, 2 ,3, 4, 5 etc or 1,2,3

If I can recover partial incremental backups (missing files 5-10) from the rescue media then why can't the main application do that as well? Why the handicap?

Are you saying that if my backup scheme is of an incremental backup, the software expects to find all increments even when the increments haven't been created? So copying an incomplete backup cycle is pointless?

If incrementals haven't occured yet, that's fine.  The problem is you have a full and have taken 10 incrementals, but decided to delete the first 3 and want to keep just 4-10.  Your chain is broken as you are missing the 3 that came before any of the others.

Another example  - same setup, but you deleted # 7 manually.  Well, you can still recover 1-6, but 8-10 are junk

And... to clarify Steve's comment above... an incremental chain is more than just names - it also keeps a record of each incremental, so you can't just try to sneak in some other incremental that you've named to match if you deleted one.  It still has to be from the right version chain, regardless of using the GUI in Windows or rescue media in this case.

Generally speaking though, as long as the chain is good (up to the incremental you plan to restore from), then the rescue media doesn't care much about the backup other than that the name is good, all the files are in the same folder for the backup you want to recover from and that all of the files are actually from that backup chain.

The GUI in Windows does a lot more that it keeps track of so that it knows when to run schedules, delete chains with the cleanup schedule, etc.  So it is a bit more sensitive when it comes to manual manipulation outside of the application.  

Also I have set my backup scheme to create a new full backup after every six increments but that does not seem to be happening.

Kanishk,

I've only seen that in older versions of ATI when the user went and changed the backup scheme or the backup retention timeline after the backup has been running. But, if you've been making duplicates of these files (teracopy or whatever) and they exist in multiple places with similar names when Acronis was active, I could see that causing an issue too.  Acronis is contstantly looking for existing backups... if it found some with the same name as what's already in the database, but in a different location, I can see that causing issues too.  

I would manually kick off the backup (back to back) until the next full starts and then monitor to see if it behaves as expected after that. Don't mess with the schedule, type or cleanup anymore.  

What do you mean by 'no change'? 'no change' as in there won't be any problems or 'no change' as in there won't be a new entry in the backups' list?

No change in the entry list.  One backup per name.  Names need to be unique.  This is why it's not a good idea to have multiple copies of the same backup accessible to Acronis at the same time.  It expects them to be where they were originally created and will treat them like that unless you move them and validate the backup in the GUI.  It knows nothing about any manual changes, or duplicates of the same file that exist elsewhere it didn't have a part in creating.  

Issue meaning seeing history of both backups? That's fine. Would I be able to recover despite the two having the same name?

As long as the files are part of that version chain, all parts of the chain are in the same folder and nothing is corrupted, you will be able to recover.  And rescue media can be simpler in this case, just because it doesn't care anything about the Windows database.  I only use rescue media to recover full disk or full partition backups and only use Acronis is Windows to recover files/folders of pure data (pictures, documents, etc)

How can there be an internal database or information stored on the application if I am recovering a file? ATI retains information of all backups it has ever done even if they are deleted in the application? What happens if you are restoring the data on a different PC? Then there can't be an internal database or any information, right?

He's talking about renaming the backup files (.tibs) made by Acronis.  Acronis records all of the names and locations of .tibs created in Windows.  If you manually start renaming them, it won't corrupt the backups, but will screw up Acronis ability to locate those files and recover from them in Windows.  All backups for a single chain need to have a common name and be in the same folder.  Just avoid changing the names manually and try to use good names to start with as your routine.

When you say "a task known" do you mean known in the history of all backups that the application has ever done or known from the list of current backups?

Just what's active in the GUI task pane - that is what is currently in the Acronis database.

If I can recover partial incremental backups (missing files 5-10) from the rescue media then why can't the main application do that as well? Why the handicap?

You can in the GUI if you validate the backup again as it will still be able to recover up to the point where it isn't broken, but you have to select the right date.  Regardless of the GUI or rescue media, you can have missing files at the end and be able to recover up to the most current incremental before, but if there is any type of gap, then nothing can be recovered after that. The database just expect everything it created to be there as it was created so you have more to contend with than in rescue media which doesn't have any database to check against - just the files it has available to use.

The key in the GUI is to validate what you have - but really, not to mess with the original files at all if you want it to be seamless.

i.e.

Full and inc 1,2,3,4,5, 6, 7, 8, and 10 - can recover any of these up to 8 since all incrementals before it are in tact.  But since 9 is missing, 10 is useless since there is a gap.

Full and inc 2, 3, 4, 5, 6, 7, 8, 9, 10 - you can only recover your full because the entire incremental chain is broken without 1 since there is a gap between the full and all incremental after it

Full and inc 1, 2, 3, 4, 5, 7, 8, 9, 10 - you can recover up to incremental 5, but since 6 is missing, 6-10 are useless

No change in the entry list.  One backup per name.  Names need to be unique.  This is why it's not a good idea to have multiple copies of the same backup accessible to Acronis at the same time.  It expects them to be where they were originally created and will treat them like that unless you move them and validate the backup in the GUI.  It knows nothing about any manual changes, or duplicates of the same file that exist elsewhere it didn't have a part in creating.  

Just to verify: You are saying that if I create a backup, copy it to an external hard disk, add that backup to the GUI, Acronis won't update the list of backups at all?

I should add here that the names are the same but the dates in my backups were different. That would be the case even now if I were to delete my existing backup scheme (after having copied to a cloud storage) and create a new backup scheme. In my case, the first (full) backup would be called "Samsung SSD 850 EVO M.2 250GB_full_b1_s1_v1"

That's why I created this thread basically. My current backup scheme is 3 backup cycles - 1 full + 6 increments per day for three weeks. I could keep three of the older backups on the cloud and then the newer three on my external hard disk. If I wanted to recover files from 3 weeks ago, how would I do it? I would download the backup made in the cloud (the old backup) and then add it to the GUI, right? But you are saying that the app won't register the newly added backup at all because there's a name conflict? To avoid that name conflict, I should rename the backup's names before uploading them to the cloud, right? So if I were to change the name to "Samsung 850 EVO M.2 SSD 250GB_full_b1_s1_v1" and so forth, I should be able to recover files from my earlier backup?

As long as the files are part of that version chain, all parts of the chain are in the same folder and nothing is corrupted, you will be able to recover. 

Doesn't this contradict what you just said? The application won't add my older same-name backups, right?

He's talking about renaming the backup files (.tibs) made by Acronis.  Acronis records all of the names and locations of .tibs created in Windows.  If you manually start renaming them, it won't corrupt the backups, but will screw up Acronis ability to locate those files and recover from them in Windows.  All backups for a single chain need to have a common name and be in the same folder.  Just avoid changing the names manually and try to use good names to start with as your routine.

The backups are good as long as they share the same name, right? So it can't screw up Acronis' ability to recover the backups, right? I assume you mean that Acronis can't create increments if I rename the backups? (which makes sense.)

Also could you please tell me why do I have 8 increments despite my setting specifying six?

Kanishk,

I've only seen that in older versions of ATI when the user went and changed the backup scheme or the backup retention timeline after the backup has been running. But, if you've been making duplicates of these files (teracopy or whatever) and they exist in multiple places with similar names when Acronis was active, I could see that causing an issue too.  Acronis is contstantly looking for existing backups... if it found some with the same name as what's already in the database, but in a different location, I can see that causing issues too.  

I would manually kick off the backup (back to back) until the next full starts and then monitor to see if it behaves as expected after that. Don't mess with the schedule, type or cleanup anymore.  

 Are you saying that even the mere existence of duplicate backups on different hard disks causes problem to the GUI?

Also the two secnarios that you described as being problematic - aren't they the same? Having backups in two locations at the same time.

Also why not touch the clean up option? Since I want only six increments, I want to delete the last two and have the next be full (once I get help on the matter.)

Your screenshots show the Scheme is working as intended.   The problem is that you are not understanding the naming convention. 

Looking at the last backup inc_b1_s8_v1.tib.  This backup is your 7th increment of the scheme.  The size of the backup is 73,79,083KB indicating that it is a full backup of all selected data. 

Your scheme as an incremental scheme will produce this same scenario 3 times according to your settings before you will see a new backup file that has full in the name.  If you wish to have only 6 increments then you need to set chains to 1.  This will produce a full followed by 6 inc, then a new full.

Enchantech wrote:

Your screenshots show the Scheme is working as intended.   The problem is that you are not understanding the naming convention. 

Looking at the last backup inc_b1_s8_v1.tib.  This backup is your 7th increment of the scheme.  The size of the backup is 73,79,083KB indicating that it is a full backup of all selected data. 

Your scheme as an incremental scheme will produce this same scenario 3 times according to your settings before you will see a new backup file that has full in the name.  If you wish to have only 6 increments then you need to set chains to 1.  This will produce a full followed by 6 inc, then a new full.

Wait, the option that I ticked is to have a full version after every six increments. The seventh file is not a full backup. The full backup measures 37.4GB. What happens three times? Creating three full backups having six increments, right?

The name of the file itself is 'inc' and not 'full'.

Wait, the option that I ticked is to have a full version after every six increments. The seventh file is not a full backup. The full backup measures 37.4GB. What happens three times? Creating three full backups having six increments, right?

 

The name of the file itself is 'inc' and not 'full'.

I agree, it should be a full instead of inc #8 if the settings have always been to create 6 inrementals

full_b1_s1_v1    (1) 

inc_b1_s2_v1    (2) but inc 1

inc_b1_s3_v1    (3) but inc 2

inc_b1_s4_v1    (4) but inc 3

inc_b1_s5_v1    (5) but inc 4

inc_b1_s6_v1    (6) but inc 5

inc_b1_s7_v1    (7) but inc 6

next  file after that should be backup should be

full_b2_s1_v1    (1) 

The reason this might not be is if you've been changing the settings around, or your "copy" is causing trouble as you've been trying to also import it into the console... please see comments to your next question for clarification.

------------------

Just to verify: You are saying that if I create a backup, copy it to an external hard disk, add that backup to the GUI, Acronis won't update the list of backups at all?

No, that's not what I'm saying. 

I'm saying if that backup already exists elsewhere (the original location you are telling Acronis is the destination for your backup script exists first and foremost) and then you make a copy of that same exact .tib file chain...  and put it somewhere else (while the original also exists)... and then try to import the DUPLICATE (copy) at the same time, then you won't see the copy added as a new (2nd) entry.    

This is because they are essentially the exact same backup chain, with the exact same name, but you've made a copy of it and are trying to add it as a second entry.  Acronis is going to keep using the information from the backup script that you told it to when the backup was originally created because it will see the files and name as being the same.  ignoring the request to add it a second time, but from a different location it did not originally create.

You can only have one "entry" for the same backup chain name (whether that be the original or a backup you made separately) in the console at a time.  The work-a-round would be to rename the entire copy to something else (keeping the version the same.

example:

Original

My-PC_full_b1_s1_v1  

MY-PC_inc_b1_s2_v1

Copy (rename to something else like)

My-PC-COPY_full_b1_s1_v1  

MY-PC-COPY_inc_b1_s2_v1

and then import it by using "add existing backup" and selecting the latest backup in the chain.  That way it will be "unique" based upon name.

The problem is it will not keep updating automatically as you make more copies of newer incrementals and newer full chains. This is a manual process you have to deal with if you want to use the GUI this way.  I would just rename them to begin with when you copy them and then rely on rescue media to restore from if need be. At least as long as you have an active backup still going that has the same data in it.

As long as the files are part of that version chain, all parts of the chain are in the same folder and nothing is corrupted, you will be able to recover. 

Doesn't this contradict what you just said? The application won't add my older same-name backups, right?

Nope, because that was talking about the rescue media.  The rescue media cares nothing about the Windows database.  It does, however, require that the backup chain be in tact when you try to use it.  This means that all parts of the backup need to be in a single location (that you point to when asked what the source .tib file is during a recovery).

Or, if this backup was deleted from the Windows version of the Acronis Console and is not currently listed, you can "add existing" backup and import it in Windows and use it there.  Pretty much anytime you need to do a full DISK or OS recovery though, you should be using recovery media and not Windows to start the process. 

Are you saying that even the mere existence of duplicate backups on different hard disks causes problem to the GUI?

Yes, I believe this can be an issue at times.  Especially if you're specifically trying to add copies of backups that already exist in the console, and more-so if the copies differ from the original (such that maybe one has more incrementals than the other because they weren't copied yet). 
 

I also believe that the behavior that ATI uses to automatically scan attached disks and add .tib files to the console that it finds can cause problems.  I have been asking and submitting feedback to Acronis to change this behavior so that it only adds backups that the user specifically tells it to because there are many reasons that a user would manually create copies of their backups to have them in multiple locations.  We don't want them all to be added into the console by default just because a drive is attached to the computer and if there is a chance it can "confuse" the Acronis script due to being the same backup already there, but in a different location, that is no good.

I would say this isn't always likely, but can be a problem. 

The reason this might not be is if you've been changing the settings around, or your "copy" is causing trouble as you've been trying to also import it into the console... please see comments to your next question for clarification.

I think there is some confusion here:

1) When I started this thread I was talking about trying to an older backup that was no longer the one that was created by the GUI.

For example: the current backup scheme started on 25th May and run tills 30th May. i.e 1 full + 4 increments

I was trying to meanwhile add an older backup that was created on the 15th May and ran till 21st May, i.e. 1 full + 5 increments.

Because they were both first backups, both of their names were "Samsung SSD 850 EVO M.2 250GB_full_b1_s1_v1"  but they were in fact different backups. I think this caused Acronis problems? Of course in my case the increments were missing. 

2) I didn't change settings with my new current backup scheme (started on 09-04-19).

3) I haven't copied this backup scheme to my E: drive. I have only created a hard link to the folder in my OneDrive folder (D:\OneDrive).

I'm saying if that backup already exists elsewhere (the original location you are telling Acronis is the destination for your backup script exists first and foremost) and then you make a copy of that same exact .tib file chain...  and put it somewhere else (while the original also exists)... and then try to import the DUPLICATE (copy) at the same time, then you won't see the copy added as a new (2nd) entry.    

My earlier clarification should provide more context to you. The backup scheme and name might be the same but the cycles are actually from different dates.

___

Finally, what should I do about my backup cycle not following my backup scheme? Make a new one?

I deleted the increments, kept only the original file, validated it once (successfully), deleted the task from the list, renamed the file to "Samsung SSD 850 EVO M.2 250GB (09-04-19)_full_b1_s1_v1", added it back to the task list and the screen that I got is what I've attached. Is this screen normal? If so, why does ATI not know what the contents of the file are? It should, right? I can recover the files apparently (also attached.)

I am going to create a new backup plan and see if I can have the application create only six increments without changing the settings after creating the plan. The folder is still hard-linked to OneDrive and the location of the new and the old backup is the same. Will these things be a problem?

I deleted the increments, kept only the original file, validated it once (successfully), deleted the task from the list, renamed the file to "Samsung SSD 850 EVO M.2 250GB (09-04-19)_full_b1_s1_v1", added it back to the task list and the screen that I got is what I've attached. Is this screen normal? If so, why does ATI not know what the contents of the file are? It should, right? I can recover the files apparently (also attached.)

Yes, that's normal.  You've successfully added an existing backup to the console. The key being that it does not match anything else in the taskpanel that is already there. 

Acronis does know the contents of the files within the backup.  This is confirmed by your second screenshot.  Keep in mind, the console shows only the file/folders that would be viewable in Windows File Explorer (you may need to turn on show hidden files or system files in file explorer to see more).  Alternatively, now that it's in the console again, you can also go back to the .tib file and double click it and then it will open up in file explorer where you can navigate from there and copy/paste directly out of it.

I am going to create a new backup plan and see if I can have the application create only six increments without changing the settings after creating the plan. The folder is still hard-linked to OneDrive and the location of the new and the old backup is the same. Will these things be a problem?

It should work. I would recommend testing as well to confirm.  You may also want to look at the specific OneDrive backup feature of ATI2019.  Start with a regular backup and test it.  You can manually run the backup to get the incrementals to complete and verify the next backup will then be a full

https://www.acronis.com/en-us/articles/onedrive-backup/ 

There's no feature to upload ATI images to OneDrive.

Also I cannot seem to enable Acronis Active Protection. I remember there being some sort of an error when I tried enabling Windscribe (VPN) that said something about too much CPU usage. Windscribe isn't open right now but I still can't seem to enable AAP. It's stuck at enabling service:

There's no feature to upload ATI images to OneDrive.

Correct, Acronis only support uploading backup images to their own Cloud servers directly.

I still can't seem to enable AAP. It's stuck at enabling service:

Check that the AAP Service is running in the Windows Task Manager > Services page.

See KB 59356: Acronis True Image 2017 New Generation: troubleshooting Acronis Active Protection - which has checks to make too.

Steve Smith wrote:

There's no feature to upload ATI images to OneDrive.

Correct, Acronis only support uploading backup images to their own Cloud servers directly.

I still can't seem to enable AAP. It's stuck at enabling service:

Check that the AAP Service is running in the Windows Task Manager > Services page.

See KB 59356: Acronis True Image 2017 New Generation: troubleshooting Acronis Active Protection - which has checks to make too.

 

This page was made to upload your images to OneDrive, yes?

https://www.acronis.com/en-us/articles/onedrive-backup/ 

The option shown on the image on the site does not appear to me.

Sorry but the answer is still no.  The article you linked to is not for backing up to OneDrive, but for backing up your OneDrive files & folders to the Acronis Cloud servers.  This assumes that you have a Microsoft Office 365 account which includes OneDrive.

How to Backup OneDrive to Acronis True Image

Acronis True Image 2019 Cyber Protection is the #1 personal backup software, providing an intuitive user interface that lets you create a full-disk image backup including operating systems, applications, data, preferences, and history. It also allows you to create a cloud-to-cloud backup of your Office 365 account, including the contents of your OneDrive.

1. Open Online Dashboard by doing one of the following:

• Follow the link: https://cloud.acronis.com.
• On the sidebar of Acronis True Image 2019, click Backup, click Add backup, click the Backup source area, and then select Cloud service.

2. Sign in to your Acronis account.

3. On the sidebar, click Resources, click Add, and then choose Microsoft Office 365 for Home.

4. Log in to your Microsoft account, if prompted.

5. At the Backup source area, select items to backup:

• Entire account
• Outlook
• OneDrive

My mistake. Apologies.

I created a new system link of my system image folder to OneDrive. The backup that was created by ATI after that failed. I deleted the system link folder from OneDrive and the backup failed yet again.Curiously, the log shows that the new backup was validated successfully.

I created a new system link of my system image folder to OneDrive. The backup that was created by ATI after that failed. I deleted the system link folder from OneDrive and the backup failed yet again.Curiously, the log shows that the new backup was validated successfully.

Are you using Files on Demand for OneDrive here?  If so, then this gives problems for Acronis due to the way links to files are now handled by Microsoft.

Your backup destination should not be directly to a OneDrive folder using Files on Demand.

Steve Smith wrote:

I created a new system link of my system image folder to OneDrive. The backup that was created by ATI after that failed. I deleted the system link folder from OneDrive and the backup failed yet again.Curiously, the log shows that the new backup was validated successfully.

Are you using Files on Demand for OneDrive here?  If so, then this gives problems for Acronis due to the way links to files are now handled by Microsoft.

Your backup destination should not be directly to a OneDrive folder using Files on Demand.

I deleted the system link from OneDrive. So there's no folder in OneDrive now.

I deleted the system link from OneDrive. So there's no folder in OneDrive now.

Where exactly is your backup destination set to be?  This should not be any folder within the OneDrive folder structure but be somewhere outside of those folders.

OneDrive: D:\OneDrive

ATI: G:\Computer\System Image

Kanishk, sorry but I am getting confused here, so please can you restate / clarify exactly what the issue is that we are trying to help you solve?

Despite the backup being validated successfully, ATI shows an error after the backup is done as evidenced by the X seen in the pictures attached.

The backup is being reported as corrupted but the validation was successful.

Have you moved the backup to another location after successfully doing the backup?

We need to see the log files for this backup task - if possible create an Acronis System Report and attach it as SystemReport.zip using the File > Upload option below.  The pictures with a cross mark do not tell us what the underlying issues may be here.

See report: https://ufile.io/del45x05

Kanishk, thank you for the System Report zip file, this shows the following activity on your system for this backup task / validation.

25/04/2019 14:32:55 :661  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_full_b1_s1_v1.tib
25/04/2019 14:32:55 :780  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_full_b1_s1_v1.tib
25/04/2019 14:32:55 :797  Pending operation 4 started: 'Validate Backup Archive'.
25/04/2019 14:44:56 :232  Operation has succeeded

26/04/2019 12:01:29 :954  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s2_v1.tib
26/04/2019 12:01:30 :092  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s2_v1.tib
26/04/2019 12:01:30 :098  Pending operation 4 started: 'Validate Backup Archive'.
26/04/2019 12:13:56 :188  Operation has succeeded.

27/04/2019 12:01:54 :152  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s3_v1.tib
27/04/2019 12:01:54 :288  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s3_v1.tib
27/04/2019 12:01:54 :296  Pending operation 4 started: 'Validate Backup Archive'.
27/04/2019 12:14:42 :225  Operation has succeeded.

28/04/2019 12:00:00 :438  Acronis True Image works in recovery-only mode. Please activate the product.

28/04/2019 12:14:38 :899  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
28/04/2019 12:14:39 :054  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
28/04/2019 12:14:39 :080  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 12:01:58 :019  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 12:01:58 :274  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 12:01:58 :306  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 13:24:30 :739  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s6_v1.tib
29/04/2019 13:24:30 :880  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s6_v1.tib
29/04/2019 13:24:30 :924  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 13:53:45 :819  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 13:53:46 :025  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 13:53:46 :039  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 14:28:29 :665  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 14:28:29 :803  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 14:28:29 :814  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 15:00:37 :732  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 15:00:37 :737  Pending operation 4 started: 'Validate Backup Archive'.

29/04/2019 22:57:16 :797  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 22:57:16 :881  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 22:57:16 :893  Pending operation 4 started: 'Validate Backup Archive'.

30/04/2019 00:57:14 :483  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
30/04/2019 00:57:14 :662  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
30/04/2019 00:57:14 :666  Pending operation 4 started: 'Validate Backup Archive'.

30/04/2019 12:00:52 :279  The following backups have been successfully created: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
30/04/2019 12:00:52 :330  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
30/04/2019 12:00:52 :344  Pending operation 4 started: 'Validate Backup Archive'.

30/04/2019 14:00:00 :106  Acronis True Image works in recovery-only mode. Please activate the product.
30/04/2019 14:00:02 :093  Validate Backup Archive Location: G:\Computer\System Image\Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
30/04/2019 14:00:02 :096  Pending operation 4 started: 'Validate Backup Archive'.

Your backups were being created and validated successfully up to 27/04/2019 12:14 after which your ATI 2019 application is being reported as not being activated.

28/04/2019 12:00:00 :438  Acronis True Image works in recovery-only mode. Please activate the product.

After this date / time, the backup have continued to work and look to be successful in creating new backup files, but here I am seeing duplication of file names, and validation never shows as completing.

28/04/2019 12:14:38 :899  Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
29/04/2019 12:01:58 :019  Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 13:24:30 :739  Samsung SSD 850 EVO M.2 250GB_inc_b1_s6_v1.tib
29/04/2019 13:53:45 :819  Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 14:28:29 :665  Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
29/04/2019 22:57:16 :797  Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib
30/04/2019 00:57:14 :483  Samsung SSD 850 EVO M.2 250GB_inc_b1_s4_v1.tib
30/04/2019 12:00:52 :279  Samsung SSD 850 EVO M.2 250GB_inc_b1_s5_v1.tib

From the above, you look to have been deleting backup files and trying to recreate these, hence you have created 5 x the b1_s5_v1 files, plus 2 x s4 as shown above.

The first action needed here is to activate ATI 2019 to get full function made available again.

I seem to have activated and successfully validated the backups.

That is good..