Jump to content

Recommended Posts

I am a MAC novice and have even less experience with Retrospect, but have read the online tutorials and have a bit of a problem. When I open Retrospect and go to the configure tab and go to devices, the Retrospect application freezes. I have an Overland autoloader attached to my MAC server. Can someone tell me why every time I go to devices my Retrospect freezes?

 

Thanks!

 

Chris

Link to comment
Share on other sites

Chris,

 

We need a bit more information in order to help you. For example, some hardware (e.g., an Adaptec SCSI card) doesn't have drivers that work with Mac OS 10.4.x.

 

In order to try to figure out what is happening, we need to know:

(1) version of Retrospect you are running (can get this from the Retrospect log)

(2) version of Retrospect Driver Update ("RDU") you are running (see Retrospect log)

(3) what computer hardware you have (computer, peripherals)

(4) how you are interfacing your autoloader to your computer (SCSI? what card?

(5) if #4 is for an interface card, the firmware version and driver for that card

(6) what version of Mac OS X you are running.

 

#3, 4, and 5 can be found in your Apple System Profiler (under the Apple menu, About This Mac, click the "More Info" button).

 

Give us that information and we will try to help.

 

Russ

Link to comment
Share on other sites

ok, here are my responses:

 

Retrospect version 6.1.126

Doesnt give me a Driver Update Version, but does give me a Device Access version of 1.0.107

Using a Dual 2.3 GHz PowerPC G5 with 3GB RAM and Mac OS X Server version 10.4.8

Connected by SCSI card but not sure what type or firmware/driver versions are. It says SCSI target device @1 is IBM Ultrium TD2 with revision 4770 and then SCSI target device @6 is Overland NEO series with revision 0513 - that is our Autoloader.

 

 

-Chris

Link to comment
Share on other sites

> Doesnt give me a Driver Update Version...

 

Then you're not loading any RDU. That's a problem, as the Device Update file has program updates that address software defects.

 

> ...but does give me a Device Access version of 1.0.107

 

Which is odd, as Retrospect hasn't used a Device Access file since version 4.3 (it was supplanted by the License Manager in 5.0.x)

 

> Connected by SCSI card but not sure what type or firmware/driver versions are

 

That's gonna be a problem, then. If you're using an unsupported SCSI Host Adapter, Retrospect is likely to freeze. Since Retrospect _is_ in fact freezing, my first guess is that you're using an unsupported SCSI Host Adapter. Round and round she goes...

 

Dave

Link to comment
Share on other sites

> Is it possible that retrospect itself needs some sort of updates?

 

Yes. The application itself is at its latest revision, but the modular upate file "Retrospect 6.1 Driver Update" should be in the same folder as the Retrospect application. Current RDU version is 6.1.9.102, but you should download it from the EMCInsignia website and get the latest.

 

> nobody here that can answer any questions about anything hardware related.

 

Then you'll need to answer them yourself.

 

First, you are unclear about what you see in System Profiler ("It says...").

 

Select "PCI Cards" from the left hand Contents column, and see what it shows.

 

Dave

Link to comment
Share on other sites

Quote:

ok, I got the driver update successfully installed.

 

is it possible that is all I needed to do?

 


Perhaps. Does the problem still exist?

 

Quote:

ah-ha....when I look at PCI Cards it lists:

 

ATTO ExpressPCI UL45

ATTO ExpressPCI UL45

bcom5704

bcom5704

LSI,929X

LSI,929X

 


Ok. The two "bcom" "cards" are "virtual PCI cards" for your two network ports.

It appears that you have two ATTO UL4S cards. Correct? If so, those would be fine if they have current firmware and drivers. Do they? Current versions for the firmware and driver are:

driver: v4.00

firmware flash file: v1.52 (Released 7/21/06)

 

As for the two LSI cards, I don't recognize them and you haven't posted a full listing of the Apple System Profiler output for the PCI cards. I will say that the Apple Dual-channel SCSI card (really, a rebranded LSI Logic 22320 SCSI card) that was the BTO SCSI option for our Xserve G5 (and is still the Apple BTO option for the Intel Xserve) never worked right with Retrospect, and we had to replace it with our ATTO UL4D. The Apple System Profiler tag for the LSI Logic 22320 is "LSI,1030" which is not the same as what you have.

 

Why not post the Apple System Profiler output for your PCI Cards. That would help because it would also give firmware levels.

 

And you still haven't told us what card is driving your backup device. Just so we don't keep going round and round, here is the sort of information that would be helpful (an example from Apple System Profiler for our Xserve G5):

 

Quote:

PCI Cards:

 

LSI,523:

 

Name: LSILogic,raid

Type: scsi-2

Bus: PCI

Slot: SLOT-2

Vendor ID: 0x1000

Device ID: 0x1960

Subsystem Vendor ID: 0x1000

Subsystem ID: 0x4523

Revision ID: 0x0001

 

ATTO ExpressPCI UL4D:

 

Name: ATTO,ExpressPCIProUL4D

Type: scsi-2

Bus: PCI

Slot: SLOT-3

Vendor ID: 0x117c

Device ID: 0x0030

Subsystem Vendor ID: 0x117c

Subsystem ID: 0x8013

ROM Revision: 1.5.2

Revision ID: 0x0008

 

ATTO ExpressPCI UL4D:

 

Name: ATTO,ExpressPCIProUL4D

Type: scsi-2

Bus: PCI

Slot: SLOT-3

Vendor ID: 0x117c

Device ID: 0x0030

Subsystem Vendor ID: 0x117c

Subsystem ID: 0x8013

ROM Revision: 1.5.2

Revision ID: 0x0008

 

bcom5704:

 

Type: network

Bus: PCI

Slot: SLOT-4

Vendor ID: 0x14e4

Device ID: 0x1648

Subsystem Vendor ID: 0x106b

Subsystem ID: 0x005a

Revision ID: 0x0003

 

bcom5704:

 

Type: network

Bus: PCI

Slot: SLOT-4

Vendor ID: 0x14e4

Device ID: 0x1648

Subsystem Vendor ID: 0x106b

Subsystem ID: 0x005a

Revision ID: 0x0003

 

Parallel SCSI:

 

SCSI Parallel Domain 0:

 

Initiator Identifier: 7

 

SCSI Target Device @ 16:

 

Manufacturer: MEGARAID

Model: Logical Drive 0

Revision:

SCSI Target Identifier: 16

SCSI Device Features: Wide, Sync

SCSI Initiator/Target Features: Wide, Sync

Peripheral Device Type: 0

 

SCSI Logical Unit @ 0:

 

Capacity: 50 GB

Manufacturer: MEGARAID

Model: Logical Drive 0

Revision:

Removable Media: Yes

Detachable Drive: No

BSD Name: disk0

OS9 Drivers: No

SCSI Logical Unit Identifier: 0

S.M.A.R.T. status: Not Supported

 

SCSI Target Device @ 17:

 

Manufacturer: MEGARAID

Model: Logical Drive 1

Revision:

SCSI Target Identifier: 17

SCSI Device Features: Wide, Sync

SCSI Initiator/Target Features: Wide, Sync

Peripheral Device Type: 0

 

SCSI Logical Unit @ 0:

 

Capacity: 417.42 GB

Manufacturer: MEGARAID

Model: Logical Drive 1

Revision:

Removable Media: Yes

Detachable Drive: No

BSD Name: disk1

OS9 Drivers: No

SCSI Logical Unit Identifier: 0

S.M.A.R.T. status: Not Supported

Volumes:

disk1s3:

Capacity: 417.29 GB

Available: 398.97 GB

Writable: Yes

File System: Journaled HFS+

 

SCSI Target Device @ 63:

 

Manufacturer: MEGARAID

Model: MEGARAIDDUMMYDEV

Revision: 1.00

SCSI Target Identifier: 63

SCSI Device Features: Wide, Sync

SCSI Initiator/Target Features: Wide, Sync

Peripheral Device Type: 31

 

SCSI Logical Unit @ 0:

 

Manufacturer: MEGARAID

Model: MEGARAIDDUMMYDEV

Revision: 1.00

SCSI Logical Unit Identifier: 0

 

SCSI Parallel Domain 1:

 

Initiator Identifier: 7

 

SCSI Target Device @ 3:

 

Manufacturer: SEAGATE

Model: ST373405LW

Revision: 0003

SCSI Target Identifier: 3

SCSI Device Features: Wide, Sync, DT

SCSI Initiator/Target Features: Wide, Sync, DT

Peripheral Device Type: 0

 

SCSI Logical Unit @ 0:

 

Capacity: 68.37 GB

Manufacturer: SEAGATE

Model: ST373405LW

Revision: 0003

Removable Media: Yes

Detachable Drive: No

BSD Name: disk2

OS9 Drivers: No

SCSI Logical Unit Identifier: 0

S.M.A.R.T. status: Not Supported

 

SCSI Parallel Domain 2:

 

Initiator Identifier: 7

 

SCSI Target Device @ 0:

 

Manufacturer: EXABYTE

Model: VXA 1x10 1U

Revision: A10E

SCSI Target Identifier: 0

SCSI Device Features: Wide, Sync

SCSI Initiator/Target Features: Wide, Sync

Peripheral Device Type: 8

 

SCSI Logical Unit @ 0:

 

Manufacturer: EXABYTE

Model: VXA 1x10 1U

Revision: A10E

SCSI Logical Unit Identifier: 0

 

SCSI Target Device @ 1:

 

Manufacturer: EXABYTE

Model: VXA-2

Revision: 2120

SCSI Target Identifier: 1

SCSI Device Features: Wide, Sync

SCSI Initiator/Target Features: Wide, Sync

Peripheral Device Type: 1

 

SCSI Logical Unit @ 0:

 

Manufacturer: EXABYTE

Model: VXA-2

Revision: 2120

SCSI Logical Unit Identifier: 0

 


 

Russ

Link to comment
Share on other sites

Quote:

> ...but does give me a Device Access version of 1.0.107

 

Which is odd, as Retrospect hasn't used a Device Access file since version 4.3 (it was supplanted by the License Manager in 5.0.x)

...

Dave

 


Uh, Dave, to quote a recent post I saw in these forums:

 

Quote:

where I come from that's what we call "
crazy
talk."

 


Dave, I suggest that you look in your Retrospect menu, "About Retrospect...", click the "Status" button.

Our Xserve G5 has a clean install of Retrospect Workgroup 6.0 onto Mac OS 10.4.2 Server, now upgraded to Retrospect Workgroup 6.1 and Mac OS 10.4.8 Server, and never saw Retrospect 4.3 (that was on our old PPC ASIP server) or Retrospect 5.0.x. But it reports:

 

Quote:

Retrospect Backup

Version 6.1.126

...

Device Access Version: 1.0.107

Driver Update Version: 6.1.9.102

 


There may no longer be a "Device Access" plug-in, but Retrospect 6.1.126 still believes that it is using that code. Perhaps you are starting to have "senior moments" like I experience every day.

 

Why don't you report to us what your "About Retrospect..." reports in its Status dialog?

 

Russ

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...