| peacefulterran 2006-10-31, 1:13 pm |
| I'm posting this as it might help someone stuck in the same situation I
was in yesterday.
Backup computer (just IBM - Windows XP box) was stuck somewhere in a
parallel universe, with Retrospect running and other software running.
Nothing seemed to bring it back, so I did the ultimate human vs
computer revenge : shut down the beast.
However, after that, I've tried to run backup again to make sure
everything was ok, and of course, it wasn't. I was getting error -106
(data overwrite attempt). After this error, I was asked to specify a
new backup set (or a new disk? Whatever) whenever I've tried to run my
backup script.
Verifying the backup set didn't show any problem.
Recreating the catalog changed nothing.
So, I've taken a look at the backup set directory. There, I could see
what files that I could only guess where the result of previous backup
sessions (although there were more than one file per session, probably
two file per source, plus one file for each time one file would be
larger than 614408 kB). Well, the last in date was 0 kB in size, while
the smallest after that was always 12 kB or higher.
So, what I did:
- closed Retrospect
- moved the last, 0-kB, backup-session file to another location
- reopened Retrospect
- recataloged from scratch the backup set
- specified my backup set as the destination in my backup script (it
was forgotten after recataloging)
..=2E.and voil=E0! Running backup script worked like a charm!
Hope this helps someone someday...
Fred
|