So, I got my TonidoPlug today. I set it up connect and mounted a 2TB drive, configure it to use the external drive for user data and then from Tonido running on my Mac created a group. I'm now trying to use the backup app to backup data on the Mac to the drive attached to the plug.

Tonido on my Mac scans the files and then I get "Contacted remote host. Waiting for remote host to begin transfer", but it doesn't seem to ever start transfer the files. Did I miss some setup step?

When you setup group, did you get the invitation and joined?

Yes, and I have confirmed that the group was setup properly by syncing calendar items from both tonido instances on the group calendar in the workspace app.

So, I tried a smaller source directory to backup and it worked. The directory that worked contained 500KB. The directory I wanted to backup is 200GB. Should the size of the source directory impact how long it takes for the target system to start backing up?

Also, while I can see the backed up files when I explore the file system of the plug, the incoming tab in the backup app doesn't list the successful backup. Is this normal? Point to the issue?

Another test, this time bigger 16GB, and it worked.

When I try the 200GB backup there are errors reported about some files it can't find, but I am assuming that the backup is still supposed to backup the other 300,000+ files it can find.

Well it seemed to work. It started backing up files, but then it stopped. It's been trying to backup a 33KB file for 45 minutes. I'm going to stop the backup delete all the records and start over.

Now the plug's backup app's incoming tab shows the backup. Let's hope things are fixed.

Hi,
Backup will initially take longer because it does checksum calculations to ensure only those files or chunks of files that are not available at target needs to be backed up. Once the initial backup is complete, it will be faster because it will scan and detect only the files that are changed/new to backup.

In case network comm drops, backup will try to reconnect and restart backup or you can manually hit backup and that should take care of it. I typically have it in periodic backup mode as well to handle network drops.

FYI: Backup is being completely redesigned and will be replaced with the new version in future release cycles.

I get it that the initial backup takes longer, but I was thinking that the bottleneck of the process would be in the disk or network I/) not the MD5 (or whatever algorithm is used) hash or encryption.

Is there are an ETA or other details available about the new version?