Backup4all Forum

Trying Backup4All on an XP machine with a very large # of files. I watched it for a couple of hours, and it was still "Estimating" and calculating the # of files to backup.

When I woke up this AM it was 10.5 hours into it and still "Estimating", though it said it was "updating the catalog". No files had been backed up.

Seems crazy - is this normal for a large # of files? Any way to speed this up and make it useable for me?

Hi,

Please send us the last backup log from View->Job Logs->Last backup log to support[at]backup4all[dot]com

Hi,

I have the same problem, my backup is 87 hours estimating. My backup is in local and is been restoring to local.

The backup has 572017 files in 177,69GB.

is there a way to increase speed?

Thanks,

Hi,

How much free disk space you have on C: drive?

Hello,

There are 65 GBytes. In partition i am restoring the backup there are 253GBytes free.

The backup was made in 4GBytes files.

Thanks

Hi,

Please send us the last restore log from View->Job Logs->Last restore log to support[at]backup4all[dot]com

I downloaded the 4.6 backup for all trial version. I have am trying to backup 300 gigs on a mapped share to a 1TB NAS so far this backup has been running 3 days retrospect is able to do this in 4hrs. Is your software always this slow this is unacceptable to use in a fast paced production enviroment

Hi,

Backup4all is not slow, the performance depends on your network, on the backup configuration, computer performance and so on.
If the same computer gets better results with another application, that means the backup configuration needs to be adjusted.
Please send us the last backup log (from View->Job Logs->Last backup log) and the backup catalog (.bkc file from View->Open Folder->Destination) to support[at]backup4all[dot]com.
Put the files into a zip archive.

The initial backup is still in progress Log FILE SENT there is no BKC file in the destination folder

Hi,

After the backup is finished, please send us both files: the log and the catalog.
The catalog is created at the end of the backup.