Jump to content

CherylB

Members
  • Content count

    26
  • Joined

  • Last visited

Everything posted by CherylB

  1. Retrospect documentation says you should be able to configure the system to clean tape drives after every 400 hours of use. The documentation says you control click on the drive and set it there but there is no option to select for auto cleaning. Where can I find more information on configuring this automatic feature? Thanks for any suggestions.
  2. That is good news. We are in the process of upgrading to v.16.
  3. DavidHertzberg, thank you for the detailed information. I have filed a support case and hope the March 6 upgrade to v. 16 (or v.16.1) will be helpful in speeding up Instant Scan and other backups.
  4. Martin is definitely not the only one experiencing over-lengthy backups. We use incremental backups and the instant scanning often takes multiple hours and sometimes overnight. I will discuss this with our team and try turning off ISA but am hoping the release of v.16 repairs this.
  5. Am getting the error above and the computer is not backing up. I found the Retrospect error code page but that merely lists the same info I see on the failed backup. I don't know what this means nor what to do to resolve this problem. The computer is using OS 10.11 and Retrospect v is 15.1 but I can't check because the hard drive on the computer has failed. What does -808 mean?
  6. Lennart_T and DavidHertzberg-- thanks to both of you. Both of you have been very helpful when I have posted questions on this forum.
  7. We could not bring the hard drive back to life. Lennart_T suggested to "Repair" the media set in Retrospect which I ran yesterday. Today I am happy to report the repair was the correct fix and I have a backup for the entire lab. Thank you Lennart_T Once we have the hard drive for the failed computer replaced it will be added to the backup schedule.
  8. The hard drive is toast. I'll start with the Repair in Retrospect. Thank you!
  9. (Date) Connected to Computer Name * Resolved container Akumar's imac to 1 volumes: akumar iMac on Akumar's iMac - Date Time Copying akumar iMac on Akumar's iMac Date Time Found 1186107 files, 2511 folders, 295.6 GB !Trouble matching akumar iMac on Akumar's iMac to Lab Name june 2017 [001], error -808 (key/refnum search failed) Does the above info help? Thank you for your time!
  10. I sent in an email to Retrospect Support yesterday: Agent Response: Can you send us a copy of the operations_log.utx file from library/application support/Retrospect? We can review the log to better understand what may be happening. Please let us know if you have any additional questions.The Retrospect Support Team I sent a zip file of the operations_log.utx file this morning.
  11. Here's what was in files I tried to send: Computers are Mac’s running OS 10.13.4 or 10.13.5 From the logs: DATE TIME Connected to COMPUTER NAME (CN) *Resolved container CN to 2 volumes: cn on cn CN on cn +Can’t access volume cn on cn, error -1,101 (file directory not found) Retrospect then continues to the 2ndvolume (CN on cn) and ends with “Execution completed successfully.” In another instance there is one volume but the error message says: “Folder CN/private/var/db/ConfigurationProfiles/Store/, +Scanning incomplete, error -1,101” Retrospect continues to build and store a snapshot. Completes with 1 execution error.
  12. I am using Retrospect v. 15.1.0.131 and am still having this error -1,101 problem. The problem is I don't see a clear pattern either. Here are 2 samples in the files attached below.
  13. Understood. Thanks for letting me know.
  14. Yesterday I updated our server v. of Retrospect to version 15.0.0.312 as recommended by the Agent. This has had no affect on fixing the error -1,101 bug and the backups are still generating this error code. I updated the Support Case History today.
  15. Thanks David. I did submit an email Support Request earlier this morning. Here is the response. I am just now starting to test this solution. Agent Response: For -1101 errors, please try this pre-release test version of Retrospect:Please let us know if you have any additional questions.The Retrospect Support Team
  16. Mayoff, I am requesting the bug fix version for v.15.0.0.190 users asap. We recently upgraded the server to v.15 and I am progressively upgrading each of the clients. I was seeing a lot of the error code listed below while we were at v.14.5 but the error codes are continuing after upgrading to v.15. Very frustrating! "Can't access volume..., error -1,101 (file/directory not found)... Compressing catalog file...Execution incomplete"
  17. Thank you David. I will contact Retrospect Tech Support.
  18. I’m beginning to see a pattern of errors in Retrospect v.14.5. It seems to be happening with only on computers that have upgraded to OS 10.13.3. (OS 10.12 & prior are fine.) Retrospect finds the volume, and reads like this: 3/13/18 2:28:53 AM: Copying [computer name] on [computer name] While scanning volume [computer name], Folder [computername]/private/var/db/ConfigurationProfiles/Store/ Scanning incomplete, error -1,101 (file/directory not found) Then Retrospect continues to match and backup files on that computer but marks the entire script as unsuccessful (as indicated by the red dot with an X). How can I resolve this?
  19. UPDATE: Upgrading clients to v.15 (15.0.0.190) works on many but not all. Some clients running OS 10.13.4 are getting tagged with error -1,101. [date] [time] Copying [computer name] on [computer name] Whie scanning volume [computer name], Folder computer name/private/var/db/ConfigurationProfiles/Store/, Scanning incomplete, error -1,101 (file/directory not found) [date] [time] Found: 982320 files, 218259 folders, 98.8 GB The Log tells me it finished matching these files, builds a Snapshot, Stores it, but Execution is incomplete. I go back to Sources and check Summary and Status for this particular computer is listed as "Backed up". Again, in Sources I refresh this machine and do not get an error messages. So I am ran a back up now but continue to get this same error. Suggestions welcome.
  20. Running 14.6.1 (client 14.6.0.127) did not resolve the error issue for me either so I began updating to v.15 last week. So far, the computers that have been upgraded to v.15 do not give the error -1,101 (file/directory not found). If that changes I will update this ticket.
  21. Thank you DavidHertzberg--I filed a Support Case and Retrospect is on the case. They suggested upgrading to v.14.6 at the very least. Am waiting to hear from my supervisor if he wants us on v.14.6 or go straight to v.15.
  22. Thanks for the reply David. No, I'm not "Moisie". Guess I'm a "fuddy-duddy" too since I'm sticking with OS 10.12 for now but many of the users I support ran the upgrade. We are in the process of soon upgrading to Retrospect V.15 but I will try your suggestions and reply back here.
  23. Retrospect Agent reply VERY helpful: (script is currently rebuilding catalog file). "I would start by making sure the script is not currently running. If the script is stopped and you are unable to remove the client from sources, try going to System Preferences. Stop the Retrospect Engine and restart the Retrospect Engine again. Then return to sources, select the client and click Remove to remove it from the window. Click Add to re-add the client. Please let us know if you have any additional questions, The Retrospect Support Team"
  24. The backup server was updated to v. 13 as verified in retrospect preferences. I went to the individual client computer (Mac 10.10.5) and updated it to Retrospect v. 13. (I uninstalled the prior version before installing v.13.) I removed the client computer from the backup server Sources. It is still listed with the "busy" icon on the left side and v.12.5 is posted as the version. I checked back and the client computer does show it is using v.13. I am trying to delete the client computer with the older v. of Retrospect (12.5) from Sources and then Add it back so the backup will resume. Retrospect is not removing the client computer from Sources and isn't backing up because it says it is busy. Advice welcome!
  25. I am continuing to get the -559 (network connection timeout) error which is followed by: "necoSoccTimer: connection failed. Can't access backup client, error -559" I've contacted phone tech support and am told this is a known problem and they are working on a solution. I have the Retrospect error code list. That briefly describes the problem but not how to fix it. I have deleted Retrospect from the client computers and re-added. I deleted the computers in Sources and Script and added via multicast. The next backup cycle comes around and I see one these error codes: -530, -519, -505. We have multiple clients on the same network/switch and firewall that do not get these errors. I was also instructed to open Activities in Retrospect and stop it. I then opened System Preferences on the probelm computers and stopped Retrospect. Turned it back on and resumed Activities in Retrospect. That did not resolve the issue. I want to know why these backup's are failing and avoid these problems from reoccurring.
×