Cyrus
I think you are getting yourself confused and mislead.
Disregard all that stuff, some of which is to be expected anyway, and start again, this time with a bit off patience.
I don't know what settings you made but try a nice small backup and it should run immediately and take only 2 minutes to complete eg /opt or /root only. Set it to manual only. Have a look at your server and workstation hard disk lights, they should be flashing. Remember to use a workstation folder that is actually shared, and to put a user name and password in to allow access to your workstation if required eg w2K/XP. Also have a look at your workstation share, after a minute or so you should see an empty file in a folder with the same number as your backup set, this file will gradually get bigger if you click on Refresh in Windows Explorer. If you see this then backup2ws is configured correctly and definitely working. Just be patient for it to finish.
Using a sme v5.6 with Pent 133 and 96Mb RAM and backing up to a WinXP w/s Pent 233 with 256Mb RAM I tested the following:
1) A small backup which creates a backup file of only 8Mb took approx 5 minutes to complete.
2) A backup which creates a backup file of 353Mb took approx 1hr 20min to complete.
3) A full backup (3.1Gb used on server) which creates a backup file split into 1Gb chunks, actually created one 1Gb file (part1), and one 866Mb file (part 2), took 7 hrs 20 minutes to complete.
4) A full backup (3.1Gb used on server) set to NOT create a backup file split into chunks, actually created one 2Gb file (2,097,152) (ie the magic 2Gb server backup file size creation limit was reached). When reading the file with WinRAR the backup was corrupt, indicating that the file was not saved beyond the 2Gb limit.
So the 2Gb issue is not resolved at all by this program, which is understandable as other factors cause it.
5) The next test I am trying is to split the backup into < 2Gb (=2,000,000) chunks and I assume this will probably run OK, although the answer will be many hours away at the speeds mentioned above.
I think the slow processor is contributing to the long backup file creation times, as previously noted with other forms of backup programs.
I will advise outcome of test 5 tomorrow when complete.
Regards
Ray Mitchell