Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Alfaj0r

  • Rank
  1. Power is fine. The NIC on it has been tested and it doesn't drop any ICMP packets during this time. The NAS has the latest firmware that it will support. Just to be clear: I'm certain that this NAS sucks, and is part of the problem. But I can't replace it, and I'd like to use it, so I'm trying to find out if I can make Retrospect a bit more flexible when using it as a destination backup set.
  2. This one is pretty weird. Our backup to a Lacie NAS works fine... but all of a sudden, it'll say that there's trouble writing media, showing the error -116 (volume doesn't exist) The thing is, the NAS has plenty of space in it. If I dismiss that message, I get this: From there, I click on "Show Members" at the bottom left, and go to the following: The "Skip this member" option is checked. I uncheck it, and hit OK, and the whole backup resumes and keeps going until this scenario repeats itself. I'm guessing the Lacie drive drops the connection, and as soon as that happens the backup job marks the set as invalid... but that's just plain annoying. Is there a good workaround for this? a way to add tolerance for this kind of behavior?
  3. Upgrade, you say? Is that different than an update? Because I checked for updates, and there are none available.
  4. Using version 7.6.123 on a multi-server install. I'm backing up an entire Windows 2008 R2 server, and I'm getting error messages every single time the job runs: -Can't back up registry, error -517 (backup client is busy) -Can't back up WMI Repository, error -517 (backup client is busy) -Can't back up COM+ Class Registration database, error -517 (backup client is busy) -Can't back up Removable Storage Manager, error -517 (backup client is busy) Each one of these is an email sent to 4 people, so it's pretty annoying to have to delete these every single time the backup runs (which is 4 times a week!). Now, according to a post by Mayoff in another thread , the one about the Removable Storage Manager is a "cosmetic error". Can I make it so the backup excludes trying to back it up, so that I don't have to have 4 people deleting an email 4 times a week? On that note, what are the chances that the other issues are also cosmetic? I'd appreciate any help in figuring out how to keep the errors from happening. The rest of the backup seems to run fine, but the errors are annoying and make the IT management feel a bit uneasy.
  5. Someone else had set up the Retrospect client on an Ubuntu server, and it was working, until the server was restarted. The guy who set it up no longer works here, so I'm trying to figure this out, but I'm in need of some help. I have two files: RCL.tar and retroclient_7.6.100-2_i386.deb I can successfully do a "dpkg -i retroclient_7.6.100-2_i386.deb", but I'm not sure where to go from there. What do I do next? How does the RCL.tar come into play?