Jump to content

lgrantham

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lgrantham

  • Rank
    Occasional forum poster
  1. it went something like: 1. corrupt config75.dat - lost client and backup sets. 2. recovered previous config75.dat from backup. 3. all local HD backups then reported " -645 chunk file damaged during save" error. 4. removed config75.dat and .bak then rebooted. relicenced and started from scratch (one empty backup set, one new script). same errors only - no complete execution of backup of local HDs. lots of KB reading and forum browsing later, still no solution. couple of gems in the KBs, which I might post for fun on another post, but not worth the effort re fixing this problem. let filemon and regedit loose on the problem (www.sysinternals.com - now MS owned). showed a bunch of .dat files in the folder: all users\application\retrospect\rtrsec.dir\ and "my computer.dat" being accessed extensively during each failed execution. we had nothing to lose, as next step was full uninstall, wipe and reinstall, so we shut down retrospect, and dumped the rtrsec.dir folder, and the rtrexec.dir folder for good measure. restarted and the script finally executed to completion. seems the corruption was in the 'my computer.dat' file (310MB), and not the config75.dat as most of the KB and forum threads indicated. I think I would be inclined to move this folder first in similar circumstances, rather than dump your client and backup set configurations (config75.dat). you can always put it back again if there is no joy. hope this saves someone more time than the KB did me. cheers lewis
  2. Ok, this ones a comlete mystery. we have a multiserver licence, currently installed as version 7.5.387, hot fix 7.5.12.103. OS in question is windows 2003 server (standard ed) SP2. we have just finished a summer refit, including 120 new backup sets, and around 120 refreshed clients (old ones removed and reinstalled, client units inspected etc). in short - quiet a lot of leg and finger work. 25th september, retrospect decided to account itself unlicenced, and ask for a licence code. We put the numbers back in. started ok, but doesnt look right. reason being all our new entries are missing. client records are pre-summer, all the old stuff is resurrected. all the new data is gone. same for the backup sets. about the only part that looks to remain intact are the scripts. sadly those now reference a couple of hundred clients and backup sets that are not in existence according to retrospect. Would appreciate any info on whats going on here. I cant hold out any acceptable level of service on such shifting sands. Not counting the amount of human resource this thing has just tipped down the drain, we are currently in such an inconsistent state that I may have little choice but to throw this product out if I cannot identify whats occured and be able to assure others that any issues have been fixed. Ive looked long and hard at the system to no avail. I cant explain it. Maybe others here have some ideas in this regard? many thanks lewis
×