Lennart_T

From the error it looks like it is your C: drive that causes the problem ("can't read error"). If it was the destination, the error should say "can't write error" or something like that. I would check the C: drive, both the S.M.A.R.T. status as well as doing a surface scan. (Windows CHKDSK does not do a surface scan.)

I finally got around to trying this. Sorry about the delay. First try: Stopped the engine, renamed my 337 MB config80.dat file, rebooted the computer. The client was still there, no dashboard. Second try: Stopped the engine, Moved my renamed file, the .bak and the newly created .dat (955kB) to the desktop, rebooted the computer. The client was still there, no dashboard.

Which one was it? (Just curious.)

If you have installed software that enables you to write to NTFS disks, Fuse is often part of the package.

I do not think so. Only if you are using third party file systems, such as NTFS.

Does it have to be manually? Can it be a script? If "yes", create a script and schedule it to run once at a time in a few minutes from "now".

SATA is a type of connection. It is used on both SSD as well as HDD. I would use an SSD for the catalog file and HDDs as members of the Media Set. Is this to be used as a 24/7 server? Then WD RED would probably be a better choice than WD Black.

Yes, I see only the list.

You lost your bet, at least in my case.

David, I'm using the Desktop Edition 15.6.1 (105), too. Step 1 on your linked page says you should sign up.

I'm also on 15.6.1 (105). I see(in the KB article) that I have to sign up for the Management Console. I never did that (didn't know there was a Management Console), so that's why my console is empty. I do not see any real need for me to use the Management Console so I don't bother with it. Thank you David, for the links.

Hello David, In my case it is on the backup server itself. I will have to read up on your links tomorrow.

Then I have the same "problem", because my dashboard is empty, too.

Yes, it is supposed to be blank until you select something, such as "Activities", "Scripts" or "Past Backups".

Not really. Is this a backup? Or is it an original/archive? If it is a backup, you could set the tape as "lost" in Retrospect and run a backup from the original. Retrospect will backup the files that was on the bad/lost tape. Yes, see above in this post.

No, there isn't. No, you can't. Both the source as well as the destination must be different for scripts to run concurrently. You could run a normal backup script from the source computer(s) to media set A. Then you could run a "Copy Backup" script from Media Set A to Media Set B. That way the source computer(s) is/are not involved and free for other uses.

I see. I don't use the console, so wasn't really aware of the issue. As I understand it, this is a cosmetic bug in the console. You also write "appear" deferred. Does that mean your scripts are actually running? The kb points out that the console is (too) different in versions prior to 12.5, so if you are really affected by this problem, you will have to upgrade.

What exactly is the "defer issue"?

It isn't the first time that some versions of Windows 10 screws up Retrospect. It looks like Microsoft has fixed that problem in this Windows update.

It's not just a question of modified dates. It can be any date. I have seen files where the creation date is later than the modified date. I know it should not happen, but it did. The following was written years ago. I expect more file meta-data is being checked nowadays, especially changes in ACL/ACE. https://docs.microsoft.com/en-us/windows/desktop/secauthz/access-control-lists

Check the dates of the files. If one of the dates are inte future, they will always be seen as modified since the last backup. Also check the dates of the containing folder(s). Come to think of it, if the links are (re)created every day or at every boot, that is probably the answer.

What happens if you copy the .rdb files in the Finder instead of using Retrospect? (Just as a test to see if the raid drive unmounts.)

You almost got it right. I did have a long-time job that included administrating a Retrospect Windows installation (with Windows and Mac clients, about 60 in total). I did get laid off and got a new job that includes administrating a small workgroup's Windows backups. I have had a Mac installation at home, starting with version 6 and CD-Rs. Now I'm at version 15.6 with hard drives.

I have been using Retrospect Mac since version 3 and Retrospect Windows since version 6.5. Nowadays, I only use Retro Mac at home for two computers (one client) and a NAS. I use Retro Windows at work with four computers (three clients). Both with Disk Media/Backup Sets. Gone are the days with dozens of computers, servers and tape libraries.

Doh. Once again I have failed to notice that this is the Windows discussion. Sorry about that.