Jump to content

Error -519 after backing up 2.1 GB of 5 GB client volume


jhg

Recommended Posts

Server Retrospect Professional 7.0.265 with latest update, running on XP SP2 with all current updates.

 

Client is XP SP2 with latest client

 

Backup to file starts OK, proceeds for about 2 GB and then quits with -519 error.

Second volume on client skipped due to -519.

 

Restaring the backup script manually in the same Retrospect session also fails with -519

 

Closing and restarting Retrospect (without touching the client machine) seems to fix the

problem -- at least it now says it's scanning. I'm going to bed and will post more info

tomorrow.

Link to comment
Share on other sites

I tried the backup several times and noticed that each time

it hung on a specific file, called "backdoor.rlk", which is

an IDS signature file for Kerio Personal Firewall. There

appear to be three variables here for further experimentation:

 

The file's name

its contents

its location

 

or any combination of these three. Applying the scientific method,

I tried the following experiments:

 

 

Test 1

Disable the firewall (but leave the service running)

Result: Same - hangs at backdoor.rlk and eventually fails with

-519 error.

 

 

Test 2:

Disable the firewall service completely

Result: Same

 

 

Test 3:

Put the entire IDS signature directory into a ZIP file

and delete the signature directory.

Result: Backup completes successfully

 

 

Test 4:

Restore the IDS signature directory from the ZIP but

delete backdoor.rlk

Result: Backup completes successfully

 

 

Test 5:

Create a dummy "backdoor.rlk" file in C:\, containing

the single word "test"

Result: Backup completes successfully

 

 

Test 6:

Create a dummy "backdoor.rlk" file in the Kerio IDS

signature directory.

Result: Backup completes successfully

 

 

Test 7:

Restore the original "backdoor.rlk" file from the ZIP

into the Kerio IDS signature directory

Result: Hangs at backdoor.rlk and fails with -519 error

 

Test 8:

Move backdoor.rlk to C:\

Result: Hangs and fails with -519 error

 

This pretty clearly indicates that the contents of the file,

not its name or location, are to blame. Note that all the

above tests were executed without rebooting, so the firewall

service remains completely disabled. Next I tried:

 

Test 9:

Delete last line of backdoor.rlk and save (still in C:\)

Result: Hangs and fails with -519

 

Test 10:

Delete all but the first line of backdoor.rlk

Result: Backup completes successfully

 

Test 11:

Restore backdoor.rlk from ZIP and delete last half of

the file (lines 57-112)

Result: Backup completes successfully

 

Test 12:

Restore backdoor.rlk from ZIP and delete first half of

the file (lines 1-56)

Result: Hangs and fails with -519

 

AHA! We're on to something. Since the whole file is 112 lines,

a binary search should take only 6 more tests.

 

Test 13:

Keep lines 1-28 of the file

Result: Successful backup

 

Test 14:

Restore backdoor.rlk from ZIP and delete all but lines

29-56 (OK, it's not quite a binary search since I have

to verify failure on the other half of the range after a

success)

Result: Successful backup (!?)

 

Hmmm... lines 1-56 will cause Retrospect to fail, but 1-28 and

29-56 individually will not. I should reverify that the file

still causes the backup to fail.

 

Test 15:

Restore backdoor.rlk from ZIP

Result: Hangs and fails with -519

 

Would anyone at Dantz care to take this up?

Link to comment
Share on other sites

Hi

 

Retrospect doesn't look inside files when it backs them up. It just pulls the file over as raw data and stores it in the backup set.

 

Here is a guess:

I suspect that reading the file for backup is locking that file temporarly. As a result the firewall program can no longer use the file and then fails most ungracefully.

 

If you create a selector that excludes that file from backup do you still have the same problem?

 

Thanks

Nate

Link to comment
Share on other sites

The firewall is totally disabled. Neither the windows service nor the GUI are running.

 

I thought I was pretty clear in my last post that I can alternate between success and

failure at will just by changing the contents of the file.

 

It's obvious to me that -519 just means "Server lost contact with client". Whether this

is due to a true network problem or just a client failure is probably not communicated.

You say Retrospect doesn't look inside the files, but at some point it must read the

data and store it in buffers. My guess is something in the file is causing the client

to fail completely and stop sending data, which is interpreted by the server as a

communications failure. Since Retrospect has the option of doing a byte-by-byte

comparison (I don't have that turned on), then the client must be capable of examining

the contents. I think that is where the error will be found.

Link to comment
Share on other sites

Hi

 

 

 

Quote:

I thought I was pretty clear in my last post that I can alternate between success and

 

failure at will just by changing the contents of the file.

 


 

 

 

You demonstrated that point yes.

 

 

 

What I'm saying is, Retrospect backs up the file as a stream of bytes. It doesn't recognize the type or content of the file. It just sees raw data as it is represented by the file system.

 

 

 

Did you also try a test where you copied the file to another disk and backing it up from there? If the contents of the file were causing the error it would occur no matter where the file is located.

 

 

 

Thanks

 

Nate

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...