Jump to content

Recommended Posts

Complete error: "scanning incomplete, error -645 (chunk file damaged during save)"

 

Retrospect multi server 7.7.620 - backs up 4 vmservers using 2 backup sets, 2 separate catalogs, to 2 different external usb drives (one backup set on alternating nights). Was working fine and I paused a backup execution on 1st server c drive while scanning at start. While doing something on the computer the program is on, I had to reboot and did so before I thought about the paused backup set. After reboot I started the backup again and everything seemed to be ok, but I got the above error after completion. Everything else backs up fine except the c drive backup on the 1st server which shows as "incomplete on overall backup with error above. Does the same on both backup sets. All hard drives are ok and everything checks out after multiple reboots, Retrospect restarts, etc. I've run 3 complete backups with everything normaI except the "incomplete" with the above error, I think I must have goobered something in the program when I rebooted during the scanning pause.

 

I would really appreciate any help anyone might give on the problem, I can't find much of anything on that particular error... but it's definitely persistent.

 

Thank you for any direction on it... Randell

Share this post


Link to post
Share on other sites

Can't believe it! First time on forum, couldn't find a search function, saw total 173 pages and figured my only hope was to post the problem. THEN (of course), I was sort of looking around and ran across the thread on the 2nd page from "lewis" on the same problem. Sure looks like that may be the answer, if so I will be eternally grateful to lewis and the others who posted on the thread. I won't know until maybe tomorrow, but I will definitely post back as to the results. If that works it's a great solution to an otherwise time consuming problem. Thanks!... Randell

Share this post


Link to post
Share on other sites

It would be interesting to read what "lewis" posted. Please post link to that thread.

 

My advice is to run CHKDSK on the client in question.

Share this post


Link to post
Share on other sites

http://forums.retrospect.com/index.php?/topic/20551-chronic-645-chunk-file-damaged-during-save-retro-75-with-fix/

 

Running backup now after deleting "my server.dat" as discussed in that thread. So far it seems to be going well, but taking a lot longer with the re-building and comparing (it's a terminal server and the dat file I moved is over 2GB). The other 3 servers will still have to back up after the 1st one finishes (hopefully), so it will be tomorrow (later today) before I know how it went. So far so good... Randell

Share this post


Link to post
Share on other sites

Worked perfectly! It took over twice as long for the backup on that server the first time, had to rebuild the dat file and ran a compare cycle on all the files, but back up on all 4 servers finally completed (total 6 hr 45 min rather than about 3 hrs) without any errors. Lewis came up with a great solution to a difficult problem, saved a lot of time.

 

Randell

Share this post


Link to post
Share on other sites

I don't know what was going on in the corrupted server dat file, but it was over 2 GB in size and the others were all less than 100 MB (11 to 89). The rebuilt file for the problem server is 38 MB... interesting.

 

Randell

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×