Direkt zum Inhalt

[RESOLVED] Backup consolidation useless.

Thread needs solution

Now I know, it has not much in common. But please read ahead.

I am testing Acronis and one thing is really bad: Backup consolidation for end users. If you only have one backup disk, consolidation takes days to finish. A full backup needs a couple of hours. Why is that?

I assume because Acronis is creating a second archive and puts all the files from previous jobs in the new file. That way, the hard disk reading head are jumping from one location on the disk, to another. All the time. Hence a consolidation jobs takes ages because the hard disk write performance is interrupted by millions of read operations.

What does that have to do with Windows 8's File History?

Well, Windows is sorting files in folders and using indexes. Hence, if a files is not changed, there is a link to the previous backup. So far TI2013 has the same technique.

Now for the difference:

If you delete old File History backups, Windows must create a new full backup out of the old files. If you delete the first backup of incremental backups, that's always the full backup. If you delete the full backup, you need to synthetically create a full backup from the remaining files. Because File History is working with files and folders, rather than archives, it just changes the indices to the files.

In short:
- Acronis' technique to create a consolidation or synthetic full backup is horribly slow, taking ten times than a regular full backup.
- Windows need a couple of minutes for a consolidation or synthetic full backup.

Issue resolved here.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 7
Kommentare: 166

 Hello Peter,

Thank you for posting this question. I will be happy to clarify the situation.

Basically, the problem you are facing is caused by the difference in the technology used to create backups by Windows 8 File History and True Image 2013 Files and Folders Backup. It is incorrect to compare these to backup technologies' performance, and I will explain why.

In case of True Image Files and Folders Backup (and here also e-mail backup and disk backup) you are storing each version of your backup archive in a separate *.TIB backup file. So every time you want to consolidate a full and incremental or differential backup, you first have to read all the versions to be deleted, then write the new full backup, and then delete the old backups. This is time consuming and will cause your disks to spin more.

Windows 8 File History on the other hand should be compared with True Image 2013 Nonstop Backup where you have only one archive (Nonstop Backup Storage) and write all the versions into it. Similar to Windows 8 File History, only changes in new files are written to the Nonstop Backup storage with each new backup, and the repeating items are linked through the index. Thus all the file versions are regarded as a set of metadata with links to indexed information storage, and the consolidation happens automatically after each backup. This technology gives you significant performance improvement upon consolidation in comparison to traditional backup technology with separate set of backup archives.

However performance is just one parameter that should be considered when choosing the backup strategy, as there are some limitations on the Nonstop Backup. Please refer to this online help topic to check all the parameters for Nonstop Backup.

Let me know if you have additional questions.

Thank you.