Skip to main content

Starting Fresh - True Image 2014

Thread needs solution

I've tried before to create my backup files from scratch.  For unimportant reasons there became problems with the backup configuration and I wanted to start fresh.  I'm doing incremental, so the first pass captures the existing data then each week any new/changed data is updated.

Simply deleting the existing backups on my NAS doesn't reset the version counter in Acronis.  If there were 50 versions before deleting the .tib files, the counter will count the next pass at 51 rather than reset to 1.  

Is there a way to get that counter to reset when I want to start a fresh backup?

Thank you.

0 Users found this helpful

Robert, Acronis stores versions information in a Database so if you manually remove existing backups via Windows Explorer or tools on your NAS, then the Database still holds that information but now your files no longer match.

You have two choices of how to proceed from here.

  1. Run a Validation of the backup task that created these backups and take the option to ignore each missing file that gets reported, this will help reconcile the database information with the actual status of remaining files.
  2. Create a whole new backup task and start afresh with a new backup name for the files.

One obvious point to make here is to never delete any earlier incremental files from a chain as this will break the version chain at that point and all later files will be useless!  This is also a reason to not create very large numbers of incremental backup files, as any damage or corruption of files within the chain will break it at that point.

When you speak about version 50 leading on to 51 etc, if this is shown as _full_b50_   then the only way to get back to _full_b1_ is to create a completely new backup task and delete the task settings for the previous task. 

Thanks, Steve.  The step I missed previously was deleting the task in Acronis.  

I don't fully understand your point about not creating large numbers of incremental backup files.  Isn't the whole point of using incremental backups that it is more efficient?  I understand that if a point in the chain becomes unsuable that can cause problems, but the chances of that should be remote.  If incremental isn't the way to go, what is?

Robert, the choice is always with the end user about how large a chain of incrementals you wish to use, but there is a trade off between efficiency in terms of the time taken to create a new incremental (identifying only the changes that have occurred since the last incremental backup) and the time it takes to recover, where Acronis will need to piece together every incremental in the chain along with the full in order to build the recovery data.  This need to build the chain also applies to exploring the backup files in Windows Explorer or Mounting the image, the larger the chain the longer this can potentially take.

My personal choice is to keep chains fairly short and then start a new chain and repeat, but I have seen posts from other users in these forums where they have built chains of 100's of incrementals which is too risky for me.  I have seen too many disk drives go bad over time to want to try that route, so try to spread my eggs around different baskets as well.

Purchased TureImage 2014 when it was new. Had it on old machine. Now I have new machine and tried to reload it. Software says, installation successful. However, when I try to run it, I get the following error dialog boxes.

 

Qt5Core.dll missing

Qt5Widgets.dll missing

Qt5GUI.dll missing

Then a dialog box says, TrueImage not installed.

Any help welcomed!

Bob

Understood, Steve.  I thought you were suggesting that incremental was a less good option.  My mistake.

Agreed on keeping the chain smaller for efficiency reasons.  As noted earlier, I'm less concerned about the backup files becoming corrupt on the remote storage and not overly concerned at all about a drive failure.  One drive failing would be no issue (RAID 5 configuration) and the chances of two drives failing simultaneously are quite remote.  Also, when a full data backup takes nearly 2 days, it becomes more of an issue to start over.  I keep the chain at a, somewhat, reasonable size by only doing weekly backups rather than daily. 

Thanks and I appreciate the insights.

Bob, 

I think you'd be better starting your own topic rather than hoping for answers to a different problem in this one. More people are likely to see it if it's standalone.