I think it is due server version mix.

Until now, every night this command:

COPY FILE "01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp" IN STORE "Local_Backup" TO "01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp" IN
STORE "Clients_On_Rapador"

ran with no errors. Since I updated target server to 2.03 b4, I get this error:

"1306. Error with the store Clients_On_Rapador (Error writing to the file 01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp)"

with backups larger than 1 Mb. Smaller backups work fine almost every time. Source server is 2.02 b15. Next night I'll update source server and try again.
Just for information to EDB developers

Tiago,

<< I think it is due server version mix.

Until now, every night this command:

COPY FILE "01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp" IN STORE "Local_Backup"
TO "01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp" IN STORE "Clients_On_Rapador"

ran with no errors. Since I updated target server to 2.03 b4, I get this
error:

"1306. Error with the store Clients_On_Rapador (Error writing to the file
01002_2009-10-22-MAGEST2_ACTUAL.EDBBkp)"

with backups larger than 1 Mb. Smaller backups work fine almost every time.
Source server is 2.02 b15. Next night I'll update source server and try
again. >>

Is this reproducable when using the EDB Manager to execute the COPY FILE
statement ?  Are you copying from a local store to a local store, or a local
store to a remote store ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,
<<Is this reproducable when using the EDB Manager to execute the COPY FILE
statement ? >>
Yes. Fails also inside an script. With < 1Mb files fails 50% times. 70Mb files fails 100% times.

<< Are you copying from a local store to a local store, or a local
store to a remote store ?>>

From local (2.02b15) to remote (2.03b4). Source line is a 8/20Mbit ADSL. Target is a 1/4 Mbit ADSL.

Tiago,

<< Yes. Fails also inside an script. With < 1Mb files fails 50% times. 70Mb
files fails 100% times. >>

I just tried it here with this statement:

COPY FILE "Test Backup On 2008-01-12.EDBBkp" IN STORE "Local" TO "Test
Backup On 2008-01-12.EDBBkp" IN STORE "Remote"

the backup file was ~67MB in size, and it works fine every time with the
local loopback address.

<< From local (2.02b15) to remote (2.03b4). Source line is a 8/20Mbit ADSL.
Target is a 1/4 Mbit ADSL. >>

Are you sure that there isn't an issue with the line reliability ?  What
happens if you try it with the local loopback address, but with the same
client, etc. ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<Are you sure that there isn't an issue with the line reliability ?  What
happens if you try it with the local loopback address, but with the same
client, etc. ?>>

I just know two facts:
1. It fails since I updated target server to 2.03b4
2. In other installations, where both servers are 2.03b4, all is working fine.

This night I'll update this 2.02 server and try again.

Tim,

After updating to 2.03 problem still remains. I think you are right and I wrong. I'll check the antivirus appliance and the fellow who maintains it. I guess
there is a sort of limit for outcoming files.
Curious thing is if fails since the same day I updated target edbserver

Tiago,

<< I just know two facts:
1. It fails since I updated target server to 2.03b4
2. In other installations, where both servers are 2.03b4, all is working
fine. >>

I just tried the copy from 2.03 B4 to a 2.02 B15 EDB Server, and it works
fine also (67MB).  Just to be sure, I tried it again with a backup file that
was 399MB in size.  It worked also.  This is all using the local loopback
address, but it shouldn't make any difference in terms of whether EDB is
working correctly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tiago,

<< After updating to 2.03 problem still remains. I think you are right and I
wrong. I'll check the antivirus appliance and the fellow who maintains it. I
guess there is a sort of limit for outcoming files. Curious thing is if
fails since the same day I updated target edbserver >>

One more question - are you executing this remotely ?  That is, are you
doing the following:

- Connecting to the EDB Server using a remote session
- Starting a copy from a local store to a remote store using the same remote
session

?

If so, then there might be a scenario with a very slow connection whereby
the progress updating may cause the transfer to fail.  This is just a hunch
on my part right now, but it may bear fruit in terms of explaining your
situation.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tiago,

Okay, I just tried the same copy (399MB backup file) using a network
simulator that was simulating 800KB/S bandwidth, and it worked fine then
also, albeit a bit slower.

2.03 B4 on both ends.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,
<<One more question - are you executing this remotely ?  That is, are you
doing the following:

- Connecting to the EDB Server using a remote session
- Starting a copy from a local store to a remote store using the same remote
session>>

Thanks Tim. This is not the case. It's a job running every night at 4:00AM. It's makes a backup in a local store and then copy it to a remote store.

Definitely, the problem is due a perimetral antivirus appliance. I'll ask them to program an exception on edbbkp files.