Jump to content

twickland

Members
  • Content count

    1,679
  • Joined

  • Last visited

  • Days Won

    39

twickland last won the day on November 24

twickland had the most liked content!

Community Reputation

69 Excellent

About twickland

  • Rank
    Retrospect Guru

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm curious why you have installed the Retrospect server app on the client FS SERVER. I wonder whether this could be part of the problem; say, if the external volumes on that machine have been reserved for a local backup. Should we assume that there's no problem that the local volumes JRP DATA and JRP DATA BU are shown as offline?
  2. We have solved the problem. The cause seems most likely to have been Retrospect's new automatic client update feature. In any case, at some point the client software on the affected machines became corrupted or was actually deleted. In the cases we tested, if the client was removed from the sources list and we attempted to re-add it, the process failed due to an incorrect public/private keypair. We decided to just go ahead and reinstall the client software locally on all our "invisible" Windows clients, which solved the problem; we did not need to delete any client configuration files, so these must have been OK.
  3. Yes, clicking on "Add source directly..." and entering the client's IP address. We need to do this because our IT people block multicast and the clients are found in multiple subnets. Incidentally, for clients added by the direct method, Retrospect typically displays the -519 error message (rather than -530) when the client is simply not visible on the network. It even shows -519 in the add client dropdown if one enters an unassigned IP address. As for the Windows client that briefly went incognito, it's now back and being backed up successfully. We have a total of 20 Windows clients, only four of which are currently able to be backed up. Three of those are on Windows 10 and one is on Windows 7. Knowing the users, I have a suspicion that those three Windows 10 machines may not have had the latest security patches applied. Our networking people say there have been no changes to our wired network (we don't use WiFi for any backups). I haven't yet heard from our desktop support folks to get their take on this issue. Something is definitely amiss, as the client machines that are not visible on the network in Retrospect are also unresponsive when port 497 is pinged.
  4. We have run into a peculiar issue where most of our Windows 10 client machines can no longer be backed up. They are all connected via direct IP (due to our network's security settings), and have a variety of different client versions from 15.6 to 16.5.1. On each machine, the Retrospect Client app appears to be normal, the IP address has not changed, the Windows firewall is set to enable communication, and the computer is awake, but when access is attempted from the backup server, we get a -519 error. Mac client machines are unaffected. Even more oddly, a newly-added Windows 10 client was able to be backed up once before going incognito. I assume this is most likely an issue with our local network, since I would think if the problem were more widespread, there would have been other posts to this forum. Any ideas as to what might be the issue here, so I can intelligently discuss the problem with our network techs, who have no knowledge of any particular requirements that Retrospect might impose? Does Retrospect still use TCP and UDP port 497? We're running Retrospect 16.5.1 server on MacOS 10.14.6. Thanks.
  5. twickland

    Scan tape into set ?

    I think this should work:
  6. We recently ran into a number of issues with backing up certain client favorite folders. These all occurred shortly after upgrading to v 16.0.1, which may or may not be a coincidence. In one case, a client favorite folder began showing up the the Sources list with the tilde "offline" icon. Browsing the drive volume showed the folder as still having the stripe icon. To solve the problem, I needed to forget and re-add the favorite folder. In a second case, the favorite folder was not being backed up, returning a -519 network communication failed error. However, I was able to browse the folder in question from the Sources list, after which it was able to be backed up normally. In several other cases, the folders stopped backing up with a proactive script. After backing them up with a regular script, they were once again backing up with the proactive script. I discovered these issues after the clients appeared in the "No backup in 7 days" list. For now, I will assume the problems have been fixed. The issue was reported to Retrospect Support
  7. The peculiar reported capacity of these tapes may be related to the media set locked-unlocked bug I reported here back in 2015 that still has not been fixed.
  8. The actual data in your media sets and the media set catalogs will be unaffected by creating a new configuration file. You will need to point Retrospect to the locations where the media set catalogs are located, but if the catalogs themselves and the data on the disks and tapes are not corrupt, you should be fine here. The hassle will be to manually recreate all your scripts and schedules, any custom rules you may have had, and your source lists, especially if they contain favorite folders. Many of us have begged for years to have Retrospect split the various aspects of its configuration into separate files, or at least to enable users to export and reimport scripts, lists, etc., so that everything doesn't need to be manually re-entered when corruption occurs. Good luck!
  9. twickland

    Dashboard empty

    As a point of reference, I'm running Retrospect Single Server Version 15.6.1 (105) on MacOS 10.12.6. The top-level dashboard items are visible whether or not the management console is enabled. Lennart, a question for you: Can I assume that when you select "Past Backups," what you see is just the listing of past backups and not the spiffy and colorful pie charts, bar graphs, and other doodads that are supposed to be present on the dashboard when the server itself is selected?
  10. twickland

    Dashboard empty

    Actually, not true. The dashboard should have all of its reporting images available when the top level is selected.
  11. I don't recall Fast Catalog Rebuild as an option for other than tape and optical media sets; i.e., ones that you would typically need to insert the media members sequentially into the drive.
  12. It would appear that the search function on the Sources page (accessed by clicking on the drop-down plus sign at the right of the toolbar) can only access the top level of the sources list; you cannot, for example, search for volume names, favorite folders, etc. that are on client machines. Is the search function really that pathetically limited, or am I missing something? I'm using Retrospect 15.0 and have not used this particular search in earlier versions.
  13. Let's begin with clearing up the terminology. Retrospect stores backup data in Media Sets. The catalog file simply keeps track of the data that is in the Media Set. The greater the number of files, folders, and backups a given Media Set contains, the larger its catalog file will be. It sounds like you are using a Disk Media Set. It's usually best for the catalog for a Disk Media Set to be stored on a different volume than the data. Grooming enables you to recover space on the data volume by deleting older backups. Keeping the Media Set's catalog file compressed enables you to save space on the disk volume where the catalog file is stored, at the price of whatever performance hit is caused by the need to repeatedly compress and expand the catalog. I'm curious how large your Media Set is, both in the number of files and in the data itself. 36 GB seems like a pretty big catalog file We use both disk and tape Media Sets to back up 38 source volumes, and for a tape set that has around 25 million files, the catalog file is around 11 GB; for a disk set containing 6 million files, the catalog file is around 9 GB. (We don't keep any of our catalogs compressed.) As always, the more information you can give us about your setup, including OS and software versions, the better we can help.
  14. You may be confusing a backup set with the tape members of that backup set, as none of the screenshots above show any actual tape members. Your third screenshot above shows that Retrospect is aware of six backup sets. You can highlight any or all of them to search for your files of interest. You can also open more catalog files and search them as well. I can't say what limitations, if any, that Retrospect 5.1 may have regarding how many backup set catalogs that it can be aware of and search through in one go. That may depend on how many tape members are in each backup set, as well as the total count of files in the backups. As David notes above, having a backup set's catalog is not useful if you don't actually have the tape members of that backup set. In your next post, please give us an idea of how many tape members there are in a typical backup set of yours. You can find this by going to Configure>Backup Sets>Configure [specific backup set]>Members.
  15. Each catalog will have the name of its backup set, and not the word "catalogue."
×