Skip to main content

How to avoid slow consolidation and still not overload destination?

Thread needs solution

We are backing up several computers to a NAS using ATI Home 2009 on XP. Most of the backups are file-based and incremental. The backups them selvs are very fast and function is stable. However, it does not take long until the NAS is full of old backups. Using consolidation is impossible, we end up having computers not doing anything else than running consolidation jobs. Today we manually remove old backups on a regular basis. The backups are rather large, a full backup (of files) is about 500 Gb.

We are about to upgrade to Win7 now and are also thinking of upgrading ATI Home to 2010 but after running some tests with the trial version the problem seam to remain.

How does the rest of you handle this? We cannot be alone with this problem. Norton Ghost v15 seam to have this functionality built in its destination manager, and it is much faster. But Ghost is sooo ugly...

0 Users found this helpful

I believe that consolidation is totally worthless.

I have three document backups and two full backups. When my backup drive gets filled up I wipe out one of the backups entirely.
1. I do a “select all” on the folder, hold down the shift key and push the delete button. This wipes out all the files immediately, bypassing the recycle bin.
2. Then I run that backup – the one going to an empty folder now, and verify it.
3. If that gives me enough room I either stop or go on and wipe out another entire folder of backups, run that backup again, then verify.

Basically I make sure that I always have at least one good set of backups, one full and one docs, at all times.

I believe that consolidation is totally worthless.

Consolidation seems to eliminate the advantages of incremental backups. So far I’ve consolidated based on the number of backups, not size or date. I tell Acronis to consolidate after 10 incremental backups. It might take ten minutes to run the last incremental backup and then it would take three hours to consolidate. It’s probably slower than just running a whole new backup every time. AND, after you’ve hit the 10 file limit, it will consolidate every time thereafter, destroying any reason for making incremental backups.

Can someone confirm if this is really what the Acronis code does? If so, then it’s moronic.

This makes sense:
A. Reached 10th backup? Yes.
B. Make a new full backup.
C. Erase 10 old backups.
D. Start over again with incremental backups.

If consolidation is worthless why have the function? If there is some function to it, or some way to run it so that it makes sense, can someone please tell me what that is.