Retro 6.1.230 and OS X 10.6.3

[gibsonm]

Hi,

 

I recently upgraded our backup machine from 10.6.2 to 10.6.3.

 

Under 10.6.2 everything ran fine.

 

Now we have an issue.

 

Backups to disk (via FireWire 800) work fine.

 

Backup to the LTO3 tape drive appear to lockup the machine. When I’ve tried running the scripts manually they execute fine (matching files and sessions and writing data to the tape). However once I stop it the machine locks up (clock doesn’t change, can’t quite out of Retrospect, need to resort to hitting the power button).

 

I doubt its the LTO3 SCSI driver as it quite happily recognises the Tandberg drive and writes to it (have even been able to manually restore a folder from the tape drive).

 

This has happened to 4 different scripts to date so I suspect its not catalog corruption, etc.

 

Any ideas?

Edited April 7, 2010 by Guest

[Lennart_T]

Retrospect 6 (any version) does not support backing up Mac OS X 10.6 (any version). You need Retrospect 8.1 or later.

 

The fact that Retrospect previously hasn't reported any errors with 10.6 doesn't mean the backups were successful. It just means Retrospect are not even aware of what to check for in 10.6.x.

[gibsonm]

True but I never said it was backing up 10.6.

 

The machine running Retrospect (i.e. has the Retrospect application software installed on it) is the machine that was upgraded from 10.6.2 to 10.6.3.

 

The Xserve that this machine backs up (i.e. the Xserve is the client) runs 10.5.8.

 

To confirm again, the problem is not with the Xserve but the MacPro that has Retrospect installed.

Edited April 7, 2010 by Guest

[Lennart_T]

True but I never said it was backing up 10.6.

That is correct. You didn't say much about anything, actually.  ;-)

The machine running Retrospect (i.e. has the Retrospect application software installed on it) is the machine that was upgraded from 10.6.2 to 10.6.3.

That doesn't really matter as Retrospect 6.x isn't supported with Mac OS 10.6.x in any way.

 

http://kb.dantz.com/article.asp?article=9723&p=2

[gibsonm]

Sure but as 8.1 for the Mac has been a complete waste of time until very recently due to almost no documentation on how to use it (I purchased it and installed it on this machine but its never been used and indeed I suspect the service agreement that was bundled with it is about to expire) I’ve been forced (no doubt like many others) to stay with 6.1 (which the client is happy with and knows how to use).

 

To date it has been faultless (right up to the 10.6.3 update in fact) but I guess I’m now forced to try and get 8.1 to work (was hoping to hold out for the alleged soon to be released next patch before going down that road).

 

Anyway that link provides EMC with a ready made response so I guess there’s no point pursuing the matter.

 

Thanks anyway.

Edited April 7, 2010 by Guest

[Lennart_T]

I heard that version 8 even has a manual now.

...And that it's (finally) useable!

[gibsonm]

Yes indeed if your definition of “useable†is to throw out everything that worked to date and start over.

 

The mythical “conversion script†mentioned in the couple of page original readme file has been officially abandoned in the new manual (see p17). There it refers you to the multiple chapters you need to read to be able to replicate what you already had working in 6.1 (and earlier).

 

Its up there with Microsoft’s pushing of VBA in Office 2001, X and 2004 and then abandoning it in Office 2008 in terms of “seamless transitionâ€.

 

The client knows 6.1 and is comfortable doing things with it unsupervised. There is a whole bunch of data dump / re learning required before they’ll reach the same comfort level with 8.x.

 

But that’s wandering off topic.

Edited April 7, 2010 by Guest