Discussion forum for FBackup users.
We are organizing a giveaway, where 50 licenses for Backup4all Professional (total value of $2500) will be given to 50 users. All you have to do is create a video tutorial about FBackup and upload it to Youtube - there is no drawing so as long as there are licenses left from those 50, you will receive one too. Here are the details: Backup4all Giveaway.
A full backup takes 3 hours. The test of that backup takes 8 hrs. Something is amiss. I read the forums and have done all the recommended fixes: all Fbackup .exe's and the network destination drive are excluded in the virus scanner (MS Security Essentials), the minimum set of source files to back-up are selected (no windows or system files), etc.
We're running Win 7 64 bit, FBackup 4.6.253, network backup to a Seagate Central Axis via wired network.
Any more suggestions?
Hi,
What is the read speed from the destination device?
If you manually copy a large file to destination and then you copy it back, is the copy time the same for both cases?
The write spped of a 751Mb file was averaging about 10.5 Mb/s, 1m 15 s total time. The read for same file copyed back to PC was averaging 11.5 Mb/s, 1m 05s total time.
Hi,
Is the time difference the same for the next backup updates?
The timing was the same on the next backup too. Would like a log file?
P.S. We also have esentially an identical backup set-up on a Vista machine on the same network and back-up server. The backup takes about 3 hours and the test less than one.
Hi,
As the backup jobs are configured the same way (as you told us), is there any difference how these two computers access the destination drive?
Is one computer behind a router?
There is one switch that the two computers and the backup server are connected to. Both computers have the destination called out the same way, e.g \\Mca-05abb7\jiloa\My Backup\Charmed2010\Weekly Backup\. Each has it's own file directory. The weekly full backup ran again yesterday with the same results. About three hours for the backup and about 8 for testing. The daily mirror backup takes about 30 minutes and testing takes about 30 minutes. Could there be something to do with the compression of the weekly?
Hi,
You cannot compare a Full backup (which is zip compressed and include all files) and a Mirror (which is not zipped and include only new and modified files).
O.K. But why does the full backup on the Vista 32 machine test so quickly while the full backup on the Win 7 64 machine test so slowly? What else can we try to solve this long test issue?
Hi,
Please try to backup using low compression (fastest).
Didn't find a setting for low compression. In Full Backup/Properties/Compression encryption is set to "No Encryption" and split by file is set to "None". Why dies it take so long on this computer (win 7 64b) but not on the Vista machine?
Oh, you are correct, that option is available only in Backup4all, our commercial edition.
From the information received, I cannot figure what the problem is.
Please note you can disable the test after backup from Backup Properties->Advanced page.
Disbling test is an option. It is not recommended in anything I've already read on this site. Does the testing work the same way with Backup4all? Would it likely be the same length?
Hi,
The test works the same way in Backup4all. As your situation is not a general one (not every client has such problems) there are some more options in Backup4all to configure trying to speed up the backup.
I just tuned off test as it looks like many others have done. I little risk. But much time saved.
You must log in to post.