We're using a backup program to backup our local data and I have set the data to split into 512MB chunks. On our remote server, I have a session within BC which has a comparision between the remote server (set as local) and the local server (set as FTP) where the data is backed-up.
On the remote server, I have set-up a nightly schedule which runs a BC script to load the session and mirror it. It begins at 00:00 and is set to end after 8 hours if the comparision hasn't finished (to conserve our bandwidth for when we need it).
The problem we're having is that the first 512MB block will transfer, and then the connection just times out. BC is set to reconnect on disconnect, so it does this then starts transferring the same file again! Of course, Windows then ends the schedule and the incomplete file is left in the Windows "temp" folder. This is despite the fact that the file has already downloaded successfully. As a result, we are ending up with no files being backed-up.
I have set-up a verbose log file, and here are some snippets:
...
09/06/2006 00:00:34 Sent> RETR [file1].zip
09/06/2006 00:00:34 Recv> 150 Opening BINARY mode data connection for [file1].zip (537651427 Bytes).
09/06/2006 04:51:35 Stat> 537651427 bytes transferred. (30.0 KB/s) (04:51:01)
09/06/2006 04:53:35 Stat> Timeout (120s).
09/06/2006 04:53:35 LocalHelp: 3
09/06/2006 04:53:35 Stat> Client closed the connection.
09/06/2006 04:53:35 Stat> Resolving host name "[host]"
09/06/2006 04:53:35 Stat> Connecting to [IP] Port: 21
...
09/06/2006 04:53:35 Sent> RETR [file1].zip
09/06/2006 04:53:35 Recv> 150 Opening BINARY mode data connection for [file1].zip (537651427 Bytes).
[END OF LOG]
Thanks in advance...
On the remote server, I have set-up a nightly schedule which runs a BC script to load the session and mirror it. It begins at 00:00 and is set to end after 8 hours if the comparision hasn't finished (to conserve our bandwidth for when we need it).
The problem we're having is that the first 512MB block will transfer, and then the connection just times out. BC is set to reconnect on disconnect, so it does this then starts transferring the same file again! Of course, Windows then ends the schedule and the incomplete file is left in the Windows "temp" folder. This is despite the fact that the file has already downloaded successfully. As a result, we are ending up with no files being backed-up.
I have set-up a verbose log file, and here are some snippets:
...
09/06/2006 00:00:34 Sent> RETR [file1].zip
09/06/2006 00:00:34 Recv> 150 Opening BINARY mode data connection for [file1].zip (537651427 Bytes).
09/06/2006 04:51:35 Stat> 537651427 bytes transferred. (30.0 KB/s) (04:51:01)
09/06/2006 04:53:35 Stat> Timeout (120s).
09/06/2006 04:53:35 LocalHelp: 3
09/06/2006 04:53:35 Stat> Client closed the connection.
09/06/2006 04:53:35 Stat> Resolving host name "[host]"
09/06/2006 04:53:35 Stat> Connecting to [IP] Port: 21
...
09/06/2006 04:53:35 Sent> RETR [file1].zip
09/06/2006 04:53:35 Recv> 150 Opening BINARY mode data connection for [file1].zip (537651427 Bytes).
[END OF LOG]
Thanks in advance...
Comment