formzone Posted June 8, 2011 Report Share Posted June 8, 2011 Hi folks I am running Retrospect 8.2.0 on a MacPro 1.1 with OSX Server 10.6.7 Modellname: Mac Pro Modell-Identifizierung: MacPro1,1 Prozessortyp: Dual-Core Intel Xeon Prozessorgeschwindigkeit: 2.66 GHz Anzahl der Prozessoren: 2 Gesamtzahl der Kerne: 4 L2-Cache (pro Prozessor): 4 MB Speicher: 24 GB Busgeschwindigkeit: 1.33 GHz Boot-ROM-Version: MP11.005C.B08 SMC-Version (System): 1.7f10 Every day, Retrospect Engine stops with the following terminal topic: 08.06.11 08:31:14 Retrospect[12613] [ENGINE] 8.2.0.399 connected to 'Server_Retrospect' (127.0.0.1:22024, 8.2.0.399) 08.06.11 08:31:14 Retrospect[12613] Warning - unable to find template matching predicate activityType CONTAINS[cd] "Proaktiv" 08.06.11 09:59:40 com.roxio.RetroEngine[86807] Assertion failure at "module.cpp-997", on threadID 0x4C87000 08.06.11 09:59:40 com.apple.launchd[1] (com.roxio.RetroEngine[86807]) Exited with exit code: 255 When I start the engine, the terminal give the following message: 08.06.11 09:59:40 com.roxio.RetroEngine[86807] Assertion failure at "module.cpp-997", on threadID 0x4C87000 08.06.11 09:59:40 com.apple.launchd[1] (com.roxio.RetroEngine[86807]) Exited with exit code: 255 08.06.11 14:50:57 [0x0-0x1fe1fe].com.apple.systempreferences[20424] 2011-06-08 14:50:57.497 Retrospect[20435:e0b] Retro Prefs Pane Helper: stop_server 08.06.11 14:50:57 sudo[20438] root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/launchctl unload /Library/LaunchDaemons/com.roxio.launchd.retroengine.plist 08.06.11 14:50:58 [0x0-0x1fe1fe].com.apple.systempreferences[20424] 2011-06-08 14:50:58.508 Retrospect[20442:e0b] Retro Prefs Pane Helper: start_server 08.06.11 14:50:58 sudo[20444] root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/launchctl load /Library/LaunchDaemons/com.roxio.launchd.retroengine.plist 08.06.11 14:50:58 com.roxio.RetroEngine[20446] #2> Command line is /Library/Application Support/Retrospect/RetrospectEngine.bundle/Contents/MacOS/RetroEngine 08.06.11 14:51:08 com.roxio.RetroEngine[20446] DAGServer:RegisterProtocal Protocal(GUID=200)! When I start the Server the proactive Script Is working normal. Does anyone know what I can do to fix the problem? Thanks JoEddy Quote Link to comment Share on other sites More sharing options...
formzone Posted June 14, 2011 Author Report Share Posted June 14, 2011 Nobody gives a answer! But what is the failure: com.roxio.RetroEngine[102] Assertion failure at "module.cpp-997", on threadID 0x4C04000 com.apple.launchd[1] (com.roxio.RetroEngine[102]) Exited with exit code: 255 it was on saturday, nobody working. please give me a answer! JoEddy Quote Link to comment Share on other sites More sharing options...
Guest Steve Maser Posted June 14, 2011 Report Share Posted June 14, 2011 This could be a localization issue -- I don't know how many forum posters run the non-English version of Retrospect 8.2, but in general an "assertion failure" is a crash. The question is *why* does it crash? There could be a number of things to look at: 1) You don't list what you use for your backup media. Are you using Tape? SCSI? External HD? DROBO? Something else? Assuming for the moment that it's not a hardware problem... 2) What might be occurring is a client backup issue of some sort that *may* be a localization issue. If it's stopping "every day", I'd venture to guess that it's hitting some bad file on some specific client each day in one of your Proactive scripts that causes the crash. What I'd suggest in this case is that you temporarily disable your proactive backups and just do a manual backup of each client to see if one of them causes the engine to crash during the backup (or scanning) phase and then debug from that point on. Quote Link to comment Share on other sites More sharing options...
formzone Posted June 15, 2011 Author Report Share Posted June 15, 2011 (edited) Hi Rookie I figured out, that it is more or less 2 houres after starting the retrospect server. I'm backing up to a WD My Book Studio II with esata. All the proaktive scripts are running without a problem as you can see, but suddenly, after 2 hours the server stops. On the same server time machine is also active. The last backup was at 9.15/11.15, is there a problem with time machine? Console: 15.06.11 11:15:40 com.roxio.RetroEngine[107] Assertion failure at "module.cpp-1063", on threadID 0x4C04000 15.06.11 11:15:40 com.apple.launchd[1] (com.roxio.RetroEngine[107]) Exited with exit code: 255 Roxio: 14.06.11 20:31:12: Ausführung wurde erfolgreich beendet Gesamtdurchsatz: 719.7 MB/Min Gesamtdauer: 00:01:11(00:01:00 Leerlauf/Warten/Vorbereiten) + Normales Backup mit Retrospect Backup am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 06:00:00: Kopieren von Retrospect 15.06.11 06:00:07: Snapshot gespeichert, 147 KB 15.06.11 06:00:09: Vergleichen von Retrospect 15.06.11 06:00:11: Ausführung wurde erfolgreich beendet Erledigt: 4 Dateien, 16.8 MB Durchsatz: 670.1 MB/Min (Kopieren: 502.5, Vergleich: 1'005.1) Dauer: 00:00:10(00:00:07 Leerlauf/Warten/Vorbereiten) - 15.06.11 06:00:11: Kopieren von Users 15.06.11 06:00:16: Snapshot gespeichert, 511 KB 15.06.11 06:00:17: Vergleichen von Users 15.06.11 06:00:21: Ausführung wurde erfolgreich beendet Erledigt: 192 Dateien, 18.3 MB Durchsatz: 1'100.7 MB/Min (Kopieren: 1'100.7, Vergleich: 1'100.7) Dauer: 00:00:09(00:00:07 Leerlauf/Warten/Vorbereiten) 15.06.11 06:00:22: Ausführung wurde erfolgreich beendet Gesamtdurchsatz: 701.9 MB/Min Gesamtdauer: 00:00:20(00:00:14 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:21:52: Kopieren von Users auf Formzone_HD_AB2 15.06.11 08:22:35: Snapshot gespeichert, 6.1 MB 15.06.11 08:22:38: Vergleichen von Users auf Formzone_HD_AB2 15.06.11 08:22:41: Ausführung wurde erfolgreich beendet Erledigt: 13 Dateien, 296 KB Durchsatz: 11.5 MB/Min (Kopieren: 8.6, Vergleich: 17.3) Dauer: 00:00:48(00:00:44 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:29:45: Kopieren von Users auf Macintosh_HD_P1 15.06.11 08:34:03: Snapshot gespeichert, 27.5 MB 15.06.11 08:34:06: Vergleichen von Users auf Macintosh_HD_P1 *Datei "Macintosh_HD_P1/Users/monika/Library/Application Support/SyncServices/Local/admin.syncdb": ungleich *Datei "Macintosh_HD_P1/Users/monika/Library/Calendars/Calendar Cache": ungleich *Datei "Macintosh_HD_P1/Users/monika/Library/Calendars/B714A959-9651-4CC0-9FDD-D8748C19F6A0.calendar/Info.plist": ungleich *Datei "Macintosh_HD_P1/Users/monika/Library/Calendars/E3B6769C-EE45-415E-8A2A-C22A8A39CF93.calendar/Info.plist": ungleich *Datei "Macintosh_HD_P1/Users/monika/Library/Logs/Sync/syncservices.log": unterschiedliche Dateigröße (Set: 12027702, Vol: 12028877) *Datei "Macintosh_HD_P1/Users/monika/Library/Preferences/iCalExternalSync.plist": ungleich 15.06.11 08:34:22: Ausführung wurde erfolgreich beendet Erledigt: 706 Dateien, 318.1 MB Durchsatz: 1'413.5 MB/Min (Kopieren: 1'590, Vergleich: 1'363.2) Dauer: 00:04:36(00:04:09 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:35:18: Kopieren von monika auf Macintosh_HD_P2 15.06.11 08:37:49: Snapshot gespeichert, 8.7 MB 15.06.11 08:37:51: Vergleichen von monika auf Macintosh_HD_P2 15.06.11 08:38:05: Ausführung wurde erfolgreich beendet Erledigt: 504 Dateien, 200 MB Durchsatz: 1'091.1 MB/Min (Kopieren: 1'200.2, Vergleich: 1'091.1) Dauer: 00:02:46(00:02:24 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:39:57: Kopieren von mitarbeiter auf Macintosh_HD_P2 15.06.11 08:41:50: Snapshot gespeichert, 3.6 MB 15.06.11 08:41:52: Vergleichen von mitarbeiter auf Macintosh_HD_P2 15.06.11 08:41:59: Ausführung wurde erfolgreich beendet Erledigt: 332 Dateien, 90.6 MB Durchsatz: 836.2 MB/Min (Kopieren: 905.9, Vergleich: 905.9) Dauer: 00:02:01(00:01:48 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:42:34: Kopieren von Users auf Macintosh_SSD_AF1 15.06.11 08:43:51: Snapshot gespeichert, 19.6 MB 15.06.11 08:43:54: Vergleichen von Users auf Macintosh_SSD_AF1 15.06.11 08:44:09: Ausführung wurde erfolgreich beendet Erledigt: 845 Dateien, 407.2 MB Durchsatz: 1'879.1 MB/Min (Kopieren: 2'035.7, Vergleich: 1'744.9) Dauer: 00:01:34(00:01:07 Leerlauf/Warten/Vorbereiten) + Normales Backup mit BackUp Users am 15.06.11 (Ausführungseinheit 1) nach Backup-Set Medienset B... - 15.06.11 08:45:13: Kopieren von Formzone_lokal auf Macintosh_SSD_AF1 15.06.11 08:45:13: Es müssen keine Dateien kopiert werden. 15.06.11 08:45:46: Snapshot gespeichert, 9.7 MB 15.06.11 08:45:49: Vergleichen von Formzone_lokal auf Macintosh_SSD_AF1 15.06.11 08:45:50: Ausführung wurde erfolgreich beendet Dauer: 00:00:36(00:00:32 Leerlauf/Warten/Vorbereiten) JoEddy Edited June 15, 2011 by JoEddy Quote Link to comment Share on other sites More sharing options...
Guest Steve Maser Posted June 15, 2011 Report Share Posted June 15, 2011 Yes -- there have been other people reporting problems running Time Machine concurrently with the Retrospect Engine. Try turning off Time Machine and see if that allows Retrospect to run without issue. Quote Link to comment Share on other sites More sharing options...
1374921330A18DE1E040000A2A666149 Posted June 28, 2011 Report Share Posted June 28, 2011 I got the same problem on an XServe running Mac OS X 10.6.8 Server without using Time Machine. Quote Link to comment Share on other sites More sharing options...
f30e6e60-a263-4d69-8f60-c92703669308 Posted June 28, 2011 Report Share Posted June 28, 2011 On the same server time machine is also active Is the same WD My Book Studio II being used as the Time Machine destination? Quote Link to comment Share on other sites More sharing options...
formzone Posted June 29, 2011 Author Report Share Posted June 29, 2011 hello no, it is a separate internal disk. With disabled time machine retrospect is working fine. So, this is for the moment ok, but I would work simultan with time machine. Quote Link to comment Share on other sites More sharing options...
c3768c36-bf22-4c6d-bc39-cdddd3062225 Posted September 27, 2011 Report Share Posted September 27, 2011 Any new status on this issue? I too was running 8 on a MacPro, backing up to a VXA 320 via ATTO SCSI, the Engine was always quitting by itself. Time Machine is not enabled on this machine, accessing only 1 client via a test script backing up only one folder with about 50GB of data. Though the data could be the problem, it never appeared to happen at the same time or on a certain file. I'd check the console and it would show that it has lost connection to the backup server. I'd check the engine and it would be off. Quote Link to comment Share on other sites More sharing options...
twickland Posted September 27, 2011 Report Share Posted September 27, 2011 Any new status on this issue? I too was running 8 on a MacPro, backing up to a VXA 320 via ATTO SCSI, the Engine was always quitting by itself. Are you getting the same asserts as the original questioner? Are you also running a version of OS 10.6.x server? The symptoms may match but the cause may differ, so more specifics would help. Any information in your crash logs? What hardware/OS/other software are the backup and client computers running at the time of the backups? Have you tried running other backups with this client as a source? Any engine crashes with local backups? Is this a recent problem? Have you tried reinstalling the engine? Quote Link to comment Share on other sites More sharing options...
f30e6e60-a263-4d69-8f60-c92703669308 Posted September 27, 2011 Report Share Posted September 27, 2011 I too was running 8 on a MacPro, backing up to a VXA 320 via ATTO SCSI, the Engine was always quitting by itself. Time Machine is not enabled on this machine, accessing only 1 client via a test script backing up only one folder with about 50GB of data. Since you are testing with such a small dataset, perhaps try without the SCSI tape drive in the mix. Use a Disk Media Set with the same Source, and see if it's more reliable or not. Of course your ultimate goal is to have it work with the tape drive, but it would be helpful to try and identify/isolate any potential cause of the Engine crashes. Dave Quote Link to comment Share on other sites More sharing options...
c3768c36-bf22-4c6d-bc39-cdddd3062225 Posted September 27, 2011 Report Share Posted September 27, 2011 Since you are testing with such a small dataset, perhaps try without the SCSI tape drive in the mix. Use a Disk Media Set with the same Source, and see if it's more reliable or not. Of course your ultimate goal is to have it work with the tape drive, but it would be helpful to try and identify/isolate any potential cause of the Engine crashes. Dave I'll try that the next time I set up V. 8 on the MacPro - I've gone back to just trying to get V. 6 running on a G5. Quote Link to comment Share on other sites More sharing options...
6bb4e311-4536-4d71-81d2-1910303931c9 Posted October 4, 2011 Report Share Posted October 4, 2011 Just to make sure you're not alone: the proactive backups never really worked the way we would have expected it, based on the v6 experience. And by that, I mean that I'd expect RS 8 to sequentially scan through all sources of a proaqctive backup and just start over when it reaches the bottom of the list. But instead the CPUs are sitting idle for many minutes, the script does not start at the top again, trying to get those sources that he missed previously. It is pretty much unpredictable how long it takes for the script to get its job done. At some points, under load, RS crashes and takes with it the whole settings file. At some other points, whose exact conditions I still have not understood, the config80.dat file has quickly increased to 484.2 MB ... from a previous 500 kB... with just a few sources added. RS 8 is one heck of a PITA and the only reason we still use it is that evaluation of other products takes some time. If the anticipated 8.3 update makes it in time, RS will have one more chance and then we're gone. It's not just you and your installation... others feel the pain too. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.