2.1 TB takes a week ...

[danico]

I have a client that has lots of images and lots of data. The total is 2.1 TB which, of course we need to backup. I would like to do a mirror to multiple disks per week. The problem is, it takes a week to get the first copy over to the disk. If I do a straight robocopy it takes two days, still very slow but not a week. Any suggestions how I can speed this up or possible seed the drives and just do updates to them after the seeding?

Thanks everyone.

Mark

[Adrian (Softland)]

Hi,

Please send us the last backup log to support[at]backup4all[dot]com, to see what can be improved.

[danico]

I'll do that. It's gonna take a few days for it to complete.

[bohica2012]

What was the final resolution to this issue?

Were there changes to the B4A job parameters which improved the end-to-end time?

[thirty7]

I would also like an update to this. I am new to this software and I am very unimpressed with the speed. I am backing up from a SSD to an external SSD as a test, about 200gb, and it should only take 2 hours or less.

[Adrian (Softland)]

@thirty7

Please send us the last backup log for that job to support[at]bacup4all[dot]com

[RickkeeC]

Hello, any developments in having the ability to pre-seed a mirror or other job? Have close to one TB of files. Running a new backup will take weeks. Any ability to build a catalog, where one does not exist from existing file set without resyncing?

[Adrian (Softland)]

Hi,

You cannot build the catalog from the files existing in destination.
But you can set a filter in Backup4all to include only files with date modified newer than a specified date (when you manually copied the files to destination).
This way, Backup4all will back up only new and modified files.