Jump to content

kleeberg

Members
  • Posts

    39
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by kleeberg

  1. I am using Mac Retrospect 12.5 on OSX 10.11.2 with server 5.0.15. I am unable to get retrospect to recognize this as a mailserver (or any other mailserver) to send me warnings in the event of back up failures. This has been true for a long time (I tested it on another Mac with an older version of OSX and Server andi got it to work just fine) I tried by the machine name, its public IP, its loopback IP and depending on what setting I use I either get "E-mail notification failed: error 530 (unknown)" or "No server found at that address (597). Could not find anything more in the mail log using Console: 1/21/16 11:32:36.930 AM Retrospect[3456]: PreferencesEmailController::sendTestEmail exception: E-mail notification failed: error 530 (unknown) 1/21/16 11:32:41.128 AM Retrospect[3456]: PreferencesEmailController::sendTestEmail exception: E-mail notification failed: error -597 (mail server not found) Any suggestions?
  2. I am having the same problem and have found that toggling the SSL on and off only changes the failure message to an error -530 unlike what EWTHackman saw. I have tried several different mail servers, the one on the server (using the name and 127.0.0.1) and on other boxes by name and IP with the same results. Solutions? Paul
  3. For some reason one of my client computers is showing "Loading Dashboard" when I start the Retro app. Backups seem to be occurring correctly. The fix described in http://forums.retrospect.com/index.php?/topic/151168-dashboard/ appears to apply to the windows version. I also see it happening on another stand-alone with the server app. When I run the retrospect app I get the same message. Backups are occurring correctly and all other screens are correct. Any suggestions? Paul
  4. Thank you. I will exclude those files from the Time Machine backup. I had not planned on backing up my time machine volume to retrospect, but I was wondering if Time Machine saved some files on the source drive that retrospect did not need to back up. I suspect not, but thought I would ask. Paul
  5. I am curious to know which folders I should exclude from retrospect backups and which from time machine. When I look inside Time Machine, I see that it is backing up RetroISAScan files that can be relatively large. Are these safe to exclude from Time Machine? Are there other files that can safely be excluded? Same for Retrospect. Are there Time Machine files that can be excluded? Finally, I think I can safely exclude my local iDevices backups from the computer backups which would save some space. I ask because time machine is in the midst of a 110GB backup and oddly that has happened more than once recently. On average, my Retrospect backups (backing up this and 3 other machines) average about 4G per night. I plan on using TImeTracker to drill into my Time Machine backup (once it completes in a day or so...) to see what took up so much space.
  6. Found the location of these .cdt files by searching google for receipt.0.cdt but still unclear as to their purpose. Used terminal to manually delete the ones I could find (interestingly wildcards did not work in these directories) but retrospect still chocked on some other oddly named .cdt files i could not find. Partitioned the drive, used Carbon Copy Cloner to clone the drive onto the new partition and the backup went smoothly. Still I think 1) a fault client should not freeze the backups, 2) if activity stalls, an alert should be triggered, 3) the path of the offending file should be able to be retrieved in a log someplace. Paul
  7. I am baffled. So far, the Retrospect console diplays three different files (one twice so far) when it freezes: receipt.0.cdt C079F490-7164-45F4-ACC4-88F9E6C4D02A.1.cdt receipt.0.cdt 57CA01DD-E52A-4D09-9AAB-7BC3D7CEDB23.1.cdt Search of the client using Spotlight and including the system files did not reveal any files with the .cdt extension. Running "locate" in terminal both before and after running "locate.updatedb" did not reveal any files with the .cdt extension. Searching the web indicates that this file belongs to CorelDraw but that app has ever been on this client. Console also does not reveal anything with the .cdt extension. The retrospect log does not reveal any information since, when I stop the activity, the log only shows "Script 'XXXX' stopped by operator" Thoughts? Paul
  8. Interestingly, I am having the same problem but I am using Retrospect on a Mac OS X 10.10.1 Server. I am running Retrospect 10.5.3 and client 11.5.0 and the backup hangs on one Mac running 10.10.1 on the network. As with the first poster, Retrospect hangs and the process needs to be stopped on the server but the client causing the hang must be rebooted else I get the -505 error. Assessing the disk with disk utilities does not show a problem. Time machine works just fine. This is the first time I have noted the file which caused the hang and I will see if it is consistent. I also believe this first appeared after upgrading Retrospect to 10.5.x It troubles me that Retrospect would hang as a result of a faulty client and that the only way I discovered the problem was when I received notification on my laptop that it had not been backed up in 7 days. Retrospect has worked so flawlessly for me for years that it had become a "set-it-and-forget-it" app. I will address my problem with the local client, but I believe Retrospect needs to address this issue with, at a minimum, notification if it appears that a client has hung. Paul
  9. I uninstalled Retrospect following the read me directions and used the uninstaller, used spotlight to search for every file (including system files) which had "retro" in the name and deleted them, rebooted, emptied trash, downloaded a fresh client from the website, installed and this computer still has the other computer's name. Did finally change the name by deleting the other sources in the backup server and added this one. So now it is named correctly but Retrospect still sees it as a server so I am unable to back it up so that it does not think I am in violation of my license. What can I do?
  10. I have now purchased a new MacBook Pro and used migration manager to move files from the MacBook Air above. Again, on this new device, I get the same message that the license prohibits adding the client and it has assumed the name of the Macbook Air in the Retrospect preferences client though it shows the new IP for the machine and I have changed the device's name in sharing preferences, the local DNS and with hostname. What can I do? Do I de-install all traces of retrospect on this MBP?
  11. Background: I am migrating to a new server and have updated all of my personal machines to MacOS 10.9. I have updated to the current retrospect drivers but for some reason when I attempt to add my laptop as a client to the new Retrospect engine, I get the -684 error. I look at my licenses and I am well within my 20 license limit with one server. All the same devices are still happily being backed-up by the 10.5 version of Retrospect on the old server. About a year ago, I had updated the a MacOS server to 10.8 (not the one running Retrospect nor was Retrospect backing it up) and in the process of attempting to install the server monitor on my desktop and laptop, accidentally made them both Mac 10.8 servers, but retrospect was still OK. Now that I have upgraded to 10.9, server has been disabled on the laptop and the desktop. Oddly I was able to add the desktop but not the laptop. For some reason the new copy of Retrospect seems to think it is a server. Question: How do I prevent Retrospect from thinking my Mac laptop is a server? Paul
  12. One of my computers, a MacBook Air (Accidentally updated to server a while ago) was updated from the old client to the new client and all worked well. Backups from a headless MacOS 10.8.2 server 10.0.1 are working fine. In order to be able to control the headless server from my MacBook air, I attempted to install the Retrospect app on it. (Did have the EMC retrospect 8 app on it previously which I had manually removed from the applications folder.) The first attempt, 10.0.1 installed and placed the other files in the Applications/Retrospect folder (client installers, client update, etc.) but the Application itself was an open window and was blank with a spinning beach ball. After about 15 minutes did a force quit. Went to reboot the MacBook air and it would not completely shut down so after 10 minutes forced a restart. After restarting, attempted to remove Retrospect using the Uninstall script and it failed. Took the Applications/retrospect folder and put it in the trash. I could not empty the trash so rebooted the machine again. Then the trash emptied. Another attempt to install the application after dragging it into the applications folder and clicking the icon, the app started and again the spinning beach ball. But this time none of the other files in the retrospect directory appeared. Backups of this as a client appear to be working but I would like to be able to use this to control retrospect without having to revert to VNC. Am comfortable with terminal. Are there specific files which I should delete manually? BTW, permissions check and disk verification passed without errors. I also installed the app on an iMac 10.8.2 server which is a client to the same 10.0.1 retrospect engine residing on the headless server without a problem. Thanks in advance for any help.
  13. That is odd. It is showing up in the Retrospect 8.0 forum. I am confused.
  14. I just installed the driver update 8.1.1.103 as instructed in the release notes and Retrospect apps on the client machines are unable to connect to the server. Looking at the log on the server after doing a warm reboot, I see: 4/17/10 7:38:59 AM com.retrospect.RetroEngine[407] DLLoadLib: no id resource in "/Library/Application Support/Retrospect/RetrospectEngine.bundle/Contents/MacOS/libretrores.dylib", skipDyloCheck 0x1 4/17/10 7:38:59 AM com.retrospect.RetroEngine[407] #2> Command line is /Library/Application Support/Retrospect/RetrospectEngine.bundle/Contents/MacOS/RetroEngine 4/17/10 7:38:59 AM com.retrospect.RetroEngine[407] #2> Command line is /Library/Application Support/Retrospect/RetrospectEngine.bundle/Contents/MacOS/RetroEngine 4/17/10 7:39:04 AM com.retrospect.RetroEngine[407] dag service: client connected. 4/17/10 7:39:04 AM com.retrospect.RetroEngine[407] dag service: client disconnected. 4/17/10 7:39:04 AM com.retrospect.RetroEngine[407] dag service: client connected. 4/17/10 7:39:04 AM com.retrospect.RetroEngine[407] dag service: client disconnected. .... I am running MacOSX Server 10.5.8 and the client Macs have 10.6.3. Suggestions? Paul
  15. I answered my second question. I set all the clients so that Retrospect has only read access to the clients and then set their clocks correctly.
  16. By the way, I should mention that the server running retrospect had the correct time.
  17. This AM I noticed that my clocks are 5 hour behind. Retrospect workgroup 6.1.230. They are all set to coordinate themselves with the Apple USA time servers. I reset one of the Mac clients to the correct time. Then when I looked in the client configuration, it shows the clock which I had set to the correct time to be 5 hours off while the clock on the computer that is 5 hours off was reported as being within a few seconds of being correct. This is a new issue and I have not changed any retrospect settings in months. Location time zone settings on all machines are set correctly. Clients are MacOSX 10.6.2. Retrospect running on MacOS 10.5.8 Server. Has anyone else seen this? Is there a way I can prevent Retrospect from automatically setting the clocks on the clients? Paul
  18. I too am having exactly the same issue that Maser describes and have found that quitting and starting the program appears to fix it. Have used the server for at least two years and recently carbon-copied the drive to a new device so it is running on different hardware. Problem has seemed to occur since then. Am using the latest Server and clients. Was the issue reported to Apple? Is there a work-around? My back-ups occur within 2 hours over night. Is there a way to have the program quit and restart each day automatically? Thanks!
  19. I have had trouble with "stuck processes" on my mini 10.5.3 server since it crashed after a Retrospect back up a month ago and found an interesting piece of data this am: Using a recycled usb connected hard drive connected to the mini server, Retrospect running on the mini was able to back up its own hard drive at only 18 mb/min (40GB took almost 2 days to complete), while it was able to back-up a remote wired ethernet connected intel iMac hard drive with 160GB at 350mb/min to the same usb device on the mini. Odd! The disk on the mini passed all the tests I was able to run on it with Disk Utility. The unix command "top" shows stuck processes sometimes climbing to 30 or more before dropping back down again. When the # of stuck processes climbs, the back-up of the mini's own hard drive would freeze, but it had no effect on the backup of the ethernet connected device. Seems to suggest that there is a problem with the mini's internal hard drive. I am not eager to take the server down unless I have to. Log files have not been helpful. No unusual data has been written to the files during freezes. Thoughts?
  20. There was an item in there so I removed it this morning. Since I had concluded that retrospect was not the problem, I had turned autolaunch on again last night. I awoke this AM to find two copies of Retrospect running and both attempting the automatic back up. I took screen shots if it would be of value. We will see if things improve now that RetroRun is no longer in the Startupitems. Thanks again for your help.
  21. Pardon my ignorance, but I did not know what you meant by sources. Each device has Retrospect Client 6.1.130. As of this point, I do not believe it is retrospect, so thanks for attempting to help. I apologize for being ignorant of what you were asking and what you needed to know. I still do not understand why RetruRun is still showing as using processor cycies after turning off autolaunch and rebooting the machine. Could it be that this Server was upbraded and migrated over the years from 10.3.x to 10.5.x so some old processes may still be resident? At this point, I doubt it matters.
  22. Well, looks like there were more herrings out there than I thought. Decided to go into my day job late and spend more energy tackling this. Disconnected the USB drives and checked them with a separate Mac, but problem still occurred. Disconnected the server from the network, issue still occurred. Turned off all services and poked around. Though mailq showed nothing, ServerAdmin showed something of 0 size in the queue. Deleted it. Now, as I add services back, things seem to be running fine. Not sure if that was it but so far all is well. Thanks for your help.
  23. I will do my best to describe the network. LAN with 5 Macs total. Mixture of ethernet and wireless. All macs and the airport base station have a fixed 192.168.1.x IP. Airport base is in bridge mode. Server is also local DNS, a web server, mailserver and an OpenDirectory master. AFP and Firewall are enabled. No changes had occurred in the configuration of the network for weeks. Server logs in automatically to a user account on reboot to allow Retrospect to run. Retrospect was set to autolaunch to back up the hard disks on each of the machine for a certain interval over night. Now the autolaunch is disabled. Server connects to the Internet via DSL with a fixed IP. Server is in the DMZ. No unusual network activity. No entries in the system log that I can find of relevance when the machine experiences stuck processes. I believe the VM growth was a red herring. That apparently is a known issue on the Apple forum and was not the cause. LaunchCFMA is no longer visible in the list of processes (at least of the ones I can see sorted by CPU utilization) so I do not think it is the issue either. I would change the title of this post if I could. I began to suspect RetroRun and RetroRunSL may be the cause because of other posts I read on this forum. Just guessing. Both these processes show in "top" after rebooting the machine without ever launching Retrospect. I see that RetroRunSL is in the SystemLoginItems.plist. I would like to try eliminating that to see if it improves things. Can I just delete that file? It is frustrating to work on a machine where it will not respond to me for minutes at a time and I have to wait. Aargh!
  24. Well, the stuck processes still appear in top, now climbing up to 36 stuck processes before falling back down again and RetroRun and RetroRunSL are still among the processes I see. Still not sure what to do.
×
×
  • Create New...