Aller au contenu principal

ATI 2013 Build 6415 Large File Back Up

Thread needs solution

The drive that I backup is my 'C' drive. At present 240GB has been used. Until recently the backup only took approximately 1 hour, and the backup file size was approximately 80GB. However over the past few weeks the backup has taken over 3 hours and the file size of the latest backup file size is 209GB. I have not changed any settings.

0 Users found this helpful

Post a screen capture of your storage folder sorted in date/time,
and a screen capture of your backup scheme.

If you are doing any defragging in between backups, the defrag should be turned OFF
as TI tracks disk usage for what to include within a backup.

If using full plus incrementals, you might want to consider this example for starting a new task.'

GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is an example only with user choice for whatever number of chains to be retained best fits the individual needs.

Latest Update 07/12
Full single BU
225GB to backup
Disc Mode
Compression - High
Operation Priority - High
Estimated BU size - 118.2GB
Actual BU size - 191GB
Time to BU - 2hrs 45 min
Very few pictures.
Something definitely is wrong. I may have to look elsewhere to get something that does the job quicker and has a lot smaller BU file.

Any assistance is appreciated.

High compression will add considerable backup time. Normal compress is ok. Pictures, audio, music, etc are already compressed and no space savings will occur on those file types.

Disk mode backup will include all partitions used space--usually 65-70% of all used space.

Have you examined the backup task to confirm that you nothing other than your stem disk is included within the path of what is being backed up?

Which version of Windows?

Am using W7 Ultimate

I have always backed up my complete C: drive all the time.

Performing a defrag operation will move a lot of data from one disk sector to another disk sector and as TrueImage includes any disk sector changes in its backup so a defrag operation can make your backup to be much larger without you actually changing any files.

Also, if your disk has bad disk sectors, the extra reads and relocates can increase the backup size. You may want to check your entire disk for bad sectors.

At this point, your best fix is to stop using your existing backup task and start a completely new task and point to the new task to a new storage folder and use a different name or custom name for this new task. Don't reuse the same name for the task or for the tib file.

Review my signature link 2-A for assistance.