I tried the ntp update by itself and no issues ???

So I have tried to "apt-get remove tklbam" then "apt-get install tklbam", no workies.

Then I tried "apt-get --purge remove tklbam" then "apt-get install tklbam", no workies.

Then tried to init tklbam but it says already initialised.

Slightly new error message now...

--------------------------------------------------------------------------

I suspect someone did something in the back :)

Thanks, working great... 30Hours for 80Gb hmmmmm

Is it possible to set a cron job for full backups to start at a specific time?

Eg starting at 9pm on a Friday once a month?

Spoke to soon something just bummed out and started up again...

------------------------------

It is working but has allot of errors all the time. It appears to recover from that easily enough but considering I am trying to transfer 80Gb any time spent resending or zipping is a slow down.

The router is a brand new draytek 2830Vn and these are my first choice from installations with flawless performance. The internet connection is in a large metro area with good upload speeds 722Kb/s average.

The system has issues "creating buckets" which I assume are zipped portions eg

-------------------------

Firstly thanks for all the suggestions and help, its appreciated.

I am from a technical background so most of the time I hate hearing the fault is with the internet or a cable or something physical like that, even when I know it can be the truth.

So I decided to investigate further.

I am monitoring the server that is currently backing up about 80 Gb through several means and it became apparent that my usage graphs bandwidth fall offs correlated with the times the errors occured in tklbam - super it looks like my pride is about to take a hit.

The answer was a little more technical and I hope someone might benefit from this.

The story goes - I setup the server (proxmox with a few MySQL, Postgres and a single Fileserver instance), a UPS, a router, voip, 3 switches (on vlans) and redundant internet access via Drayteks 4 gigabit ports and fantastic tripple WAN. I routed a WAN connection through my office so I did not have to setup DSL (obviously would not work from my office as it was someone elses DSL) and ran a wireless card for a bit more speed.

When I relocated the server everything worked great and I did not question its operation, until performing a backup.

Would you believe having the 2 WAN ports open but not connected while ADSL was chugging along cause the entire problem? The second I disabled them I noticed the difference.

On top of that there might be QOS issues  (playing around with VOIP traffic profiles etc) but I am leaving it for now as my backup has just uploaded about 40 volumes flawlessly (in about 3 hours it appears). Prior to this 140 took 20 hours.

I have no idea how this would cause a problem because I would imagine a disconnected WAN port would simply not allow any traffic (obviously). Mabey it was some internal routing conflict or out of order packets - who knows!

So thanks Jeremy for the kick start, without it I usually dont question cables and internet connections because I always use high quality new equipment.

errors are still common :(

New image, network is perfect, cables are short and shielded cat 6, adsl is fine with several services running perfectly. Now tklbam is telling me that it cannot resolve hub.turnkeylinux.org!

I simply have to conceed that I cannot use large file systems with TKLBAM.

If any devs are reading this the queue is stuck again with all my backups stating that they are 3 days old. I have placed feedback twice now but not heard anything.

Well I deleted the old file server running under proxmox again, downloaded a fresh copy of TKL Fileserver copied all my files over from the old windows file server using xxcopy and made sure all computers on the network can access the files. So far so good.

I made sure I could resolve addresses by performing an apt-get update - all good.

Now I am performing a backup. 

Running for 5 minutes and not a single error!

Mabey the issue all along was a dodgy download?

This time I downloaded the fresh image to my clients old server via tightvnc from my office and uploaded it to Proxmox over the giga network in the clients office (love the speed).

This thing is now exceeding my expectations with 1016kbps upload average!

I also turned QOS off for a bit of extra speed.

I estimate about 30ish hours if the averages stay this way.

So after all that fuss it looks like the image was indeed dodgy.

TKLBAM is now flawlessly uploading a heap of files and has done for 36 hours.

The only problem is that 1mbs (mega bits per second) is equivalent to about 125KBs (Kilo Bytes per second).

Lets do the maths... I want to upload approx 90GB (Giga Bytes) at 125KBs (Kilo Bytes).

Thats 90,000,000 KB (Kilo Bytes) at 125KBs = 720,000 seconds = 200 Hours = impractical!

Where is my fiber to the node Julia Gillard! (She is our Prime Minister if your wondering)