Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by twickland

  1. Prior to version 18.1, we would get -519 (network communication failed) or -530 (backup client not found) errors only during regular scripted backups and not with proactive backups. This of course makes sense, since the whole purpose of proactive backups is to catch and back up clients when they appear on the network.

    Since upgrading to 18.1, Retrospect is consistently reporting a -530 error for one backup client and a -519 error for another. (These are not the same two clients described in my recent post about storage groups.) Because a proactive backup script constantly pings clients to see if they're online, the Operations Log is filling up with hundreds of these spurious and useless error messages. Thank goodness, this is an issue for only two of our 24 backup clients. While not a fatal problem, it sure is annoying.

    Update: While typing this entry, I just started getting -519 errors for two more clients. I'll need to see if these become consistent, like the other two have been.

    Has anyone else seen this?

  2. Since the storage group disk media set was failing only with new backups, I decided simply to use it only for restores going forward and to create a new regular disk media set for new backups.

    As for the media set password,  I use the same password for all our media sets. That would indicate either that I mistyped the password when creating the media set or that something became corrupted after the creation.

  3. Numerous people, notably David Hertzberg, have questioned whether using Storage Groups is a good idea. We have been using a Disk Storage Group media set for over a year with no particular issues until last week, when we started getting strange errors for two clients: 

    Can't access Backup Set [Username], error -2262 (Catalog File in use by another machine)

    Neither quitting and relaunching Retrospect Engine nor rebooting the backup computer made any difference, and when I attempted to rebuild the catalog, I was unable to do so because Retrospect failed to accept the media set's password. (And that even though the media set was configured to remember the password for any access.)

    This issue cropped up shortly after upgrading to v18.0.0, which may or may not be relevant.

  4. 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.


    • Thanks 1
  5. 16 hours ago, DavidHertzberg said:


    I ask again: When you say "They are all connected via direct IP", do you mean "clients" are all defined with Direct Access Method?

    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.

  6. 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.





  7. 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

  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. 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. 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.

  11. 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.

  12. 8 hours ago, Chunky Gilmore said:

    I can see the individual tapes listed but what i had previously was all the contents of all of those tapes on one file.

    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.


  13. 3 hours ago, Chunky Gilmore said:

    Now it starts up OK but when I go onto 'Restore' and Search for Files and Folders' it only shows one tape title and yet there should be about 350.

    Retrospect stores its data in backup sets. A tape backup set can have many members. The information about what data is in the backup set and how many members it has are located in the backup set's catalog. The Retro.config file does not contain this information, though it does track where the catalogs are stored.

    If the catalog(s) is/are missing or corrupt, you'll need to rebuild it/them. However, if they are still on an accessible disk volume, you should be able to get Retrospect to see them simply by double-clicking on the catalog file in Finder.

  14. ...grooming doesn't seem to do what it is meant to do. 

    Grooming will occur according to the parameters you have set. It will only remove backups that are outside the range set to be retained. It sounds like you may be retaining more backups than you thought. Remember that there is a separate backup for each volume or favorite folder you have included as a source, so the total number of individual backups will be the number of sources times the number of backups to be retained.


    In general, grooming is most effective when you have only a single drive volume in your disk media set. That's because grooming will remove unwanted backups from all the media set's members, but the only free space available for writing to will be on the last member.



    We have another 12TB disk we could add to the media set, would this help? How do you add to a media set?

    Go to Media Sets> Members and click on the plus sign at the bottom of the window. Remember, though, that if adding this member does permit grooming according to your current settings, it's likely that what gets groomed out will be from an earlier member and if so, the freed-up space will be unavailable.

  15. If, as it sounds, your backups are completing successfully, I'd be inclined to ignore the [*] soccClose: shutdown() failed with error X messages. We see those from time to time at the completion of a backup activity when there is no apparent problem. You should, of course, confirm that you can restore everything from your backups before deciding that they really ran successfully.


    My response in the post that David Hertzberg cites above was related to the fact that the scheduled backups did not run. 

    • Like 1
  16. Once Retrospect has gone on to a new member, there is no way to add data to a previous member. The only way to reuse the tapes without losing the data would be to copy the existing data to a new or different media set.


    If you are going to copy directly from one tape media set to another, you need to have two tape drives. Of you have only one drive, you would need to copy to a disk (or other non-tape) media set, and then copy from that set to the tape set.


    You didn't say how many full tape members you have in this media set. To save time, you could get by with only consolidating the data from the short members, if you know when you began to write to the first short member, and copy only the data from that time forward to a new disk media set. You would then mark all of the short members as "missing" and copy the data from the disk media set to an erased tape, which would become the next member of your tape media set.

  • Create New...