cgtyoder

David, your condescending comments aren't needed here. Martin (and others, myself included) are frustrated at this slowness, and a little venting is not out of order. I don't understand why you feel the need to carry water for Dantz - if you don't have anything positive to contribute, you aren't required to post.

No, you're not the only one. Came here, searching for info on this problem. It is very frustrating! The first scan on my MBP (10.13.6), accessed from Retrospect Desktop 15.6.1.104 (W10), took 14 hours. I will have to try turning ISA off. Looking forward to a real solution...

[R Single Server 7.7.620 on Windows Server 2003 Std SP2] I am having trouble specifying excluding a Mac OS X (10.9) directory in my Proactive Backup script. I want to exclude /System/Library/Caches/ (and everything beneath it), but I haven't figured out the correct Condition which works. I've tried a (Mac OS) path as above and also as "My Volume:System:Library:Caches:" (without the quotes), but to no avail. Any suggestions as to how to specify the correct path? (Yes, I realize this is setup is ancient, but what can I say - it works.)

Thanks for the suggestion, but that hasn't worked either.

Scillonian, thanks for the comment. Unfortunately, on the Mac client (6.3.029), the only way to specify "Private Folder/File" is by pre- or appending the bullet character ("•") to the file/dir name. And since this is in /System/, it's off-limits to rename - that is sure to break things. I guess I'll have to experiment more.

Too late to do a repair - I've already blown away the orig catalog file. I will keep trying and cross my fingers that I don't need it...

Running Retrospect Single Server 7.7.620 on Win Server 2003 Standard SP2 x32. I got an error during a scheduled backup set grooming about the catalog file being damaged, so I went to recreate it. Now, 24 hours later, I get the error, "Backup Set format inconsistency (6 at 695069483)". I have done this 2 times now, but I can't complete the catalog file rebuild. Is there any hope for recoving this backup set? Attached is a screen shot of the log. Thanks for any pointers!

I am having the same problem here. I really hope I don't lose my whole backup set because of this! The rebuild takes 25 hours before it fails, so it's costly to test. Any one have any success with this? My env: Retrospect Single Server 7.7.620 Windows Server 2003 x32 SP2, 4GB RAM -Conrad

I am running Retrospect Single Server 7.7.341 x64 on Windows Server 2008 Std x64 SP2. I am planning to upgrade the OS to Server 2008 R2. Are there any concerns/issues I should know about when upgrading wrt Retrospect? Thanks for any input.

Running Retrospect 7.7.325, DU 7.7.3.102 (64-bit) on Windows Server 2003 Std R2 x64 SP2. I have a backup set that I cannot groom ("error -2241 ( Catalog File invalid/damaged)"). So I recreated the CF from disks, which succeeded without errors. I try to groom the backup set again, and get the same error as before. What are my options here to get this working again? Thanks for any assistance.

I was shown that KB article by tech support. Already following all recommendations and requirements.

Your link is not valid.

It was not. The chance of a file being fragmented on a disk can be rather high. Frankly, if you write software that requires a particular file be contiguous on disk, you are begging for trouble (Doesn't matter if it's "documented" or not.) Performance at the cost of basic stability is never the correct choice.

Well, tech support says, "Too Bad." Gots to scrap the existing backup set and start again. Bleah. Moving on...

Running Retrospect Single Server 7.7.325.0 on Server 2008 Std x64 SP2. Retrospect has gotten in a state where I start it, but the GUI does not appear, but Retrospect.exe is listed in the processes list. If I attempt to end the process, it does not end. If I stop/start/restart the Retrospect Launcher service, that does not affect me being able to kill the process and restart Retrospect. Is there any way to get this working again without rebooting the server? Thanks for any assistance.

I am trying to kill it via the processes tab. Where is the kill -9 when you need it? :content:

I reported it to support. I will report back when there is some resolution.

Daniels - thanks much for the link. Lennart - I do realize this is a user-to-user forum (I've been here longer than you - give me a little credit here... :glasses:) And $75 for a support incident (I can't verify that - they don't list their prices on the website) is in some cases reasonable and in some cases steep. Depends on your situation.

Well this is not good. I really don't want to pay for a support incident and then take the chance that they will declare it a bug. I mean, it's not exactly in their financial interest to do so. My backup set is rather large - about 550GB. (I don't know if that's really big compared to what other people are doing.) What are the chances of things working if I transferred the backup set to a new one? I suppose I have nothing to lose at this point...

Running Retro Client 7.7.06 on Win 7 x64. I get the message as in the Subject line, when the Client wants to display the countdown to backup, or it is finished, etc. Is there any way to bypass this so the countdown/completed/etc dialog just displays? Thanks for any assistance.

But I don't want to turn off notifications - they are important. Are you saying turning off UAC will "fix" the problem?

Just found out that Iomega has discontinued their REV drive line, and I was planning on getting a REV 120 drive for my new server, but I can't find any (new ones) available. Any suggestions for a suitable replacement, especially cost wise, that is Retrospect-friendly?

Running Retrospect 7.7.208.0 Single Server on Windows Server 2008 Std x64 SP2. Been having some problems lately - one of them is that when I attempt to quit Retrospect, it hangs and will not quit. End Task from Task Manager does the trick. However, when I attempt to restart Retrospect, I get a Retrospect Monitor window saying, "Cannot connect to Retrospect." I have to use Task Manager as well to kill this. I end up having to restart the server to get things working again. What is happening here?

Rich, you are The Man. That did it. (I did have to reboot, then stop the Retrospect Helper Service first before I could change the Config77.dat file.) Thanks for the assistance.

It gets worse now - after restarting this time, I am still getting the Retrospect Monitor window saying, "Cannot connect to Retrospect." Any suggestions? Do I need to reinstall R?