Yadnevik Posted July 23, 2004 Report Share Posted July 23, 2004 Hi, About a month or so ago I took a punt and purchased a Certance CP3101D-160-S backup unit. This is basically a DAT72 Certance Drive attached to a 160Gb drive running an emulated robotic tape library (using linux). Link to info I've tried but not suceeded in getting this unit to work with Retrospect 6.5 SBS edition (with the latest RDU 5.1). The unit works fine with other backup software, the limited Tapeware software that comes with it, Vertias, and CA demo versions that I've tried. (Currently using the Veritas version that I had before I purchase Retrospect) The basic probem is that Retrospect hangs (or worst case BSOD) when you try to do a backup. (or retrospect does a device scan). The best i've acheived by playing around with settings is getting it to find a robotic tape library, but not being able to use it. (this only happen once and I could never repeat it). I've tried updating the tape drivers to the latest Certance drivers, and I've also disabled them in device manager as suggest in other forum post's I've read. This made no difference. Anybody got any suggestions? Hardware: Dell 600SC P4 2.4Ghz Server 2Gb Ram IDE Raid array Win2k SBS SP4 (latest Patch's install) Link to comment Share on other sites More sharing options...
natew Posted July 26, 2004 Report Share Posted July 26, 2004 Hi Make sure that any other drivers installed by other Backup software vendors are not active. How does the device display in configure->devices->environment in Retrospect? Does that screen show that a driver has loaded? How is the device attached to the machine? Thanks Nate Link to comment Share on other sites More sharing options...
Yadnevik Posted July 27, 2004 Author Report Share Posted July 27, 2004 I actually began testing the unit mainly on my own PC, not the server once I started getting BSOD. (I only have one server and can't afford to stuff it up) On my own machine, I installed the copy of Retrospect I have. I'm pretty sure that other drivers from other bakup software are not interferring on this machine as I only have Retrospect installed on that machine (WinXP Pro with an ASUS SCSI basic card.) If Retrospect doesn't lock up or BSOD, then the Unit appears as only a stand alone tape drive by memory. Except you can't load or unload tapes to it. (I think it see's the virtual drive, not the real drive attached to the unit.) The device is attached via an external SCSI cable to the back of the PC. On the Server I have turned on Multi-LUN for the SCSI ID it is attached to (Adpatec 39160 card I think). The only devices attached to this card are the external Certance Unit, and the older Seagate DAT4 internal unit. On my own PC, It's the only device attached (I don't think Multi-LUN was an option on this card. Regards, Kevin Link to comment Share on other sites More sharing options...
Yadnevik Posted July 27, 2004 Author Report Share Posted July 27, 2004 The unit shows as a Seagate DAT DSS-DC Drive Under Environment, the drive is always "Busy", and the driver it is using is "Seagate DAT DDS-DC (1.12)" The PC also periodically pause's (for about 1 second in every 10-20 seconds). When I exited the program (retrospect), it crash's with the following error message. "Retrospect has encountered a serious error: Assertion failure at "thread.cpp-332" A log of this error has been written to the file "assert_log.utx". etc." I have "reported" this to dantz via the error message screen. Below is the first part of the error file. I can post/email the whole file if you are interested. I couldn't find a reference to "thread.cpp-332" on the dantz support site. Kevin XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX OS: Windows 2000 version 5.0 (build 2195), Service Pack 4 Application: C:\Program Files\Dantz\Retrospect\Retrospect.exe, version 6.5.350 Exception occurred on 28/05/2004 at 11:06:43 PM Exception code: C0000005 ACCESS_VIOLATION Fault address: 601E86AB 0001:000E76AB DEVICES.DLL Thread ID: 00001524, Name: Controller thread EAX:115504A8 CS:001B EIP:601E86AB EFlags:00010206 EBX:002F6890 SS:0023 ESP:10C0AF84 EBP: 10C0AFCC ECX:00023FB8 DS:0023 ESI:10C0B07C FS: 003B EDX:10C0B7FC ES:0023 EDI:10C0B000 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= DEVICES.DLL slotResolveChildRef +12B 00160D94 00006D5C 00006C9A 00006C9A 10C0B7FC 10C0B160 0000002F 00000028 meson.dll ModuleDatasend +65B 00160D94 'SCRC' 00006D5C 00006C9A 00006C9A 10C0B7FC 10C0B160 0000002F DEVICES.DLL magResolveChildRef +2ED 10A2870C 00004C72 00004C6A 00004C6A 10C0B7FC 10C0B160 0 -1 meson.dll ModuleDatasend +65B 10A2870C 'MCRC' 00004C72 00004C6A 00004C6A 10C0B7FC 10C0B160 0 DEVICES.DLL loadconLocateRef +84D 00171FFC 10C0B7FC 1099DCB4 10F10000 10F10374 -2 10C0B3DC 6142C60D meson.dll ModuleDatasend +65B 00171FFC 'DCLR' 10C0B7FC 1099DCB4 10F10000 10F10374 -2 10C0B3DC rdu.rpx devsconUShowContents +621 001634E4 0 1127A774 1127A774 1127A774 1127A734 7C577701 1127ABC4 meson.dll ModuleDatasend +65B 001634E4 'DCSC' 0 1127A774 1127A774 1127A774 1127A734 7C577701 meson.dll TMesonMsgDo +89 0 0 109879D4 0 0 0 0 0 meson.dll TThreadmesonDoOne +13A 109879D4 10C0E890 6060FEC8 0 10C0EB3C 0 0 0 meson.dll TThreadmesonQFlush +3E 0 10C0EB3C 0 0 0 1 0000001F 0 meson.dll msgHelper +2D 109879D4 1 10C0EDFC 10C0F2E8 002F6890 0 0 109879D4 meson.dll doTask +21E 'Msg ' 6060FE9B 0 0 10C0ED84 10C0ED84 1 10C0EDC0 meson.dll TThreadTaskCall +21 109879D4 'Msg ' 6060FE9B 109879D4 1 10C0EDFC 10C0F2E8 002F6890 meson.dll TThreadMsgBlock +96 'Msg ' 10C0F288 6062F366 10C0F77C 6062F366 'LopT' 109879D4 6002B057 meson.dll msgInTask +1F 10C0F77C 6062F366 'LopT' 109879D4 6002B057 0 0012BE1C 10C0FA10 meson.dll doTask +21E 'MsgT' 60610E16 0 0 10C0F2C0 10C0F2C0 109879D4 10C0F2C0 meson.dll TThreadTaskCall +21 109879D4 'MsgT' 60610E16 10C0F77C 6062F366 'LopT' 109879D4 6002B057 meson.dll loopInTask +27 'LopT' 109879D4 6002B057 0 0012BE1C 10C0FA10 '`ct/' 0 meson.dll doTask +21E 'LopT' 60610DEA 0 0 10C0F7B4 10C0F7B4 10C0F7C0 10C0F7D4 meson.dll TThreadTaskCall +21 109879D4 'LopT' 60610DEA 'LopT' 109879D4 6002B057 0 0012BE1C meson.dll TThreadMsgLoop +45 'LopT' 0000000C FFFF0000 0 0 000004E4 0 10C0F7FC Retrospect.exe controllerThread +2DB 00172A74 0012EAAC 0012BEFC 0012BEFC 00000011 77F80000 0 0 meson.dll doTask +21E 'Task' 61108D5D 0 0 10C0FF10 10C0FF10 '`dzd' 10C0FF7C meson.dll TThreadTaskCall +21 109879D4 'Task' 61108D5D 00172A74 0012EAAC 0012BEFC 0012BEFC 00000011 meson.dll modThreadRoot +15B 0012BE48 -1 00000158 002F6890 C0000005 87C4ED60 10C0FF88 10C0ABD0 MSVCRT.dll 0001:000075BC 002F6890 -1 00000158 002F6890 7FFD5000 0 10C0FFC0 0 KERNEL32.dll 0001:0000338B Link to comment Share on other sites More sharing options...
natew Posted July 28, 2004 Report Share Posted July 28, 2004 Hi To confirm - the windows drivers for the device are disabled right? Are both the ASUS card and Tape drive 68 pin LVD? Thanks Nate Link to comment Share on other sites More sharing options...
Yadnevik Posted August 3, 2004 Author Report Share Posted August 3, 2004 The test above was performed on the Dell server with the adaptec 39160 SCSI card. The cable used is a VHDCI 68 Male to Micro D 68 Male Cable (which I believe is LVD) The drivers were not disable for the test above, but I tried it again with the drivers disabled. The same happens in that the drive is "seen" as a "Seagate DAT DDS-DC (1.12)" and is always busy. When I try to exit retrospect, to program just keeps trying to exit but never does. After waiting for about 5 minutes I just killed it via task manager. Regards, Kevin Link to comment Share on other sites More sharing options...
natew Posted August 4, 2004 Report Share Posted August 4, 2004 Hi Try manually stopping the removable storage manager service and then running Retrospect. Also go into configure->devices->environment and tell Retrospect to ignore every ID other than the tape drive. Thanks Nate Link to comment Share on other sites More sharing options...
grz Posted September 16, 2005 Report Share Posted September 16, 2005 Hi, I'm just bought EMC|Dantz Retrospect MultiServer 7.x from EMC|Legato running under Windows 2003 server. As a backup device I'm using Certance CP3100 B2D2T, but I can't get it work right. Every time, I run device scaning in Retrospect, it freeze my server and also the Certance device. I looked on web, and found that this device is not in support list :-(. Is there any way how to get it work right? Or must I switch to another backup vendor? PLEASE HELP!!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.