Many problems with release version

[rausch]

I've run into several issues with the released product. I really appreciate the trial key opportunity.

 

Problem #1 Preference Pane won't stop engine:

3/29/09 12:47:24 PM [0x0-0x12d12d].com.apple.systempreferences[39833] 2009-03-29 12:47:24.756 Retrospect[39872:913] Retro Prefs Pane Helper: stop_server 
3/29/09 12:47:24 PM [0x0-0x12d12d].com.apple.systempreferences[39833] launchctl: Error unloading: com.retrospect.RetroEngine 

Force Quit RetroEngine and start from the prefpane revives it.

 

Problem #2 Engine shows up multiple times

Retrospect Engine server name shows multiple times in GUI main window, and in preferences window. Removing one just has it pop back again. This symptom went away after a force-quit/restart of the engine.

 

Problem #3 Client scanning problems

Client backup stopped arbitrarily with no explanatory error in the log without giving "Remaining" message.

Started back up again on proactive script schedule, taking more than 8 hours to not completely scan files on the remote client until stopped.

 

		+	Normal backup using ProActive Clients at 3/28/2009 4:03 PM (Execution unit 1)
	To Media Set Palindrome 1...
	3/28/2009 4:03:43 PM: Copying Macintosh HD on Pants
/* lots of can't read errors from cache files */
	3/28/2009 10:34:18 PM: Snapshot stored, 615.4 MB
	3/28/2009 10:35:23 PM: Comparing Macintosh HD on Pants
/* lots of compare errors because it copied cache and syncservices files */
	3/29/2009 1:47:39 AM: 158 execution errors
	Completed: 364973 files, 106.2 GB
	Performance: 438.2 MB/minute (356.5 copy, 568.6 compare)
	Duration: 09:43:54 (01:28:00 idle/loading/preparing)

			Can't access volume EMC Retrospect 8 on Pants, error -1101 ( file/directory not found)EMC Retrospect 8 on Pants, error -1101 (%s)]
	3/29/2009 1:48:02 AM: Execution incomplete
	Total performance: 438.2 MB/minute
	Total duration: 09:43:54 (01:28:01 idle/loading/preparing)
	+	Normal backup using ProActive Clients at 3/29/2009 2:18 AM (Execution unit 1)
	To Media Set Palindrome 1...
	3/29/2009 2:18:14 AM: Copying Macintosh HD on Pants
	3/29/2009 12:47:06 PM: Execution stopped by operator
	Duration: 00:00:22 (00:00:22 idle/loading/preparing)

 

Problem #4 Error messages in log are not explained.

What is the difference between read errors -1101, -1012? What is the difference between compare errors "didn't compare" and "different data size".

 

Problem #5 Rule "All Files Except Cache Files" copies /Users/*/Library/Caches.

 

Problem #6 Client performance is unusable. Local performance is poor.

Client performance is reported as 200-600MB/min. Under Retrospect version 6.1.230, speeds between the same server and client computers are 1600-1800MB/min for first backup. This is consistent with beta 5 performance, and not useful for larger numbers of clients. Local drive to local media set is also under 1000MB/min, and drops to under 10MB/min at times during simultaneous backup.

 

Problem #7 Send Test E-Mail button in preferences produces no email, and no log entry, even with SetNetworkLogging=7 in the bundle retro.ini.

 

Problem #8 Options for Disk Media Set (catalog compression, grooming) grayed-out. See screen shot attached. I made a second Media Set, and that one had the options enabled.

 

Problem #9 CPU Usage > 90% when scanning files.

How about a little "niceness" when scanning files? The computer is almost unusable for significant stretches of time. I suspect this has something to do with the client performance/scan failure described in problem #3.

 

Configuration Info:

Fresh install of version 8.0.594.1, used uninstall script to remove Beta. Uninstalled, restarted, installed client, restarted. Server is Mac OS X Server 10.5.6, Client is Mac OS X 10.5.6. Both computers are MacBook Pro (Early 2008) 2.6GHz, 4GB RAM.

[Mayoff]

Problem #5 Rule "All Files Except Cache Files" copies /Users/*/Library/Caches.

 

Can you post more of the log then "/* lots of can't read errors from cache files */" I really would like to see exactly what Retrospect is reporting in the log for this. I have been unable to reproduce a problem with the cache files selector.

[rausch]

Some updates on these issues:

 

Problem #1

I've had some repeats of this issue. Notably today I wanted to change the retro.ini back to log level 3 (see problem #5 and request).

 

Problem #2 Engine shows multiple times.

Since force quitting the engine and restarting it, I don't see this any longer.

 

Problem #5

The log for my ProActive backup only contains messages like these:

 

		necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 7f: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 80: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 81: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 82: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 83: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 84: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 85: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 86: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 87: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 88: %*$]
	necoIncoming:    cmd 300 [ 680 bytes]: 6e 63 53 4e ff ff b1 4e 03 e0 15 0b 00 07 03 89: %*$]

 

I have changed the log level back to 3, and I'll post the results after a backup finishes.

 

Problem #6

Client performance continues to be under 300MB/min, and scanning takes way too long. With 5 clients it seems like it couldn't complete backing them all up in one day.

 

Problem #8

I have been able to change the Grooming options on the catalog I wasn't able to before. It seems it may have been in use (or Retrospect thought it was), despite it not appearing to be.