I am running a COPY FILE script to backup a database from a LAN to a cloud computer.

I have run it OK a number of times. Generally my connection from the LAN to the cloud / internet isn't too bad

There was a power-cut during an COPY FILE process just now.

Now when I re-run the SCRIPT I get an error 600: Access Denied to File.

Has this error come about because the copy process was interrupted by the power cut?

How can I restart this copy process effectively?

If I want to automate this process (and guard for the possible error!) how can I do this?

OK: Sorry for the over-hasty posting.

I know a little more now. I had assumed that the problem was a lock on the file on the LAN, i.e. the local file but actually the problem was with the partially created file on the server.

The file had partially been copied across & then the session had dropped. I assumed that this would result in the file being deleted on the server, but it seems some residual file existed and the servers OS was fretting about it.

This makes the problem a little bit more complex. I really don't want the users to log onto the cloud server to stop a process or delete a file so that a new version can be copied up ... what is the best thing to do?

Adam


How did you resolve the problem this time? If its a Windows / DOS command then its more difficult since you can't directly shell out to the OS from a script.

If you could set up a batch file to do the job this is the sort of approach I'd take:

1. build some error handling into the script

BEGIN
backup code
EXCEPTION
sort out problems using the generated error number
END

and write a custom function in Delphi which will cure the problem. This can be CALLed from the script and can shell out to the OS

2. persuade all your users to buy some decent backup software like Acronis so you don't have to bother

I can't try things out here but what about just DROPing the store and recreating it?

Roy Lambert [Team Elevate]

Adam,

<< I know a little more now. I had assumed that the problem was a lock on
the file on the LAN, i.e. the local file but actually the problem was with
the partially created file on the server.

The file had partially been copied across & then the session had dropped. I
assumed that this would result in the file being deleted on the server, but
it seems some residual file existed and the servers OS was fretting about
it. >>

I checked this, and this is the situation with the latest build:

If a write to a remote file is interrupted, then the file handle will be
released when the dead session is cleaned up by the server.  However, it
will leave a partial file in place, which is not correct, and I've corrected
this for the next build.

So, if you're using pinging on the remote side, and you've configured the
ElevateDB Server to have a small dead session expiration time on the server,
then the file will be released fairly quickly.

You can find out more here:

http://www.elevatesoft.com/articles?action=view&category=edb&article=connections_disconnections_reconnections

--
Tim Young
Elevate Software
www.elevatesoft.com