I am running an HP Proliant Server w/ Win Server 2003 on it. I have my Certance Ultrium 2 backup device hooked into my server via SCSI. I had been using Veritas Backup Exec, but am now switching back to ARCserve because my company has more licenses for them. After installing ARCserve 11.1, I went into the device configuration to make my Ultrium Tape drive the backup device. ARCserve see's the drive as an available device under the tape/optical feature, but does not allow me to assign it as the library device. Even trying other methods, such as configuring a group, does not let me select the device even though it is shown under the device tab. I have been wrestling with this problem for weeks so I have done plenty of service start/stop and enabling/disabling, as well as reinstalling ARCserve. If anyone could help me with this, I would appreciate it. If you need additional info, please let me know. Thx.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Unable to assign Certance Ultrium 2 as backup device 1
- Thread starter Koach
- Start date
If it's just a standalone drive you don't need to run device configuration - else check this:
- Thread starter
- #3
If I don't need to run device config, how do I select it as a device to backup my jobs to? I read through CA's guide on the link, and no help. Here are some pics of what my problem looks like incase its tough to get a mental picture.
It's there, but you can't assign it to the library.
No help with the device group config either.
Hope this helps a bit more. Thanks again for all the help.
It's there, but you can't assign it to the library.
No help with the device group config either.
Hope this helps a bit more. Thanks again for all the help.
Koach - is this part of a library? You seem to hint this, but I need confirmation, as you won't be able to assign it to a library if the changer is not detected - which would appear to be what is happening.
If it is in a library, can you see both the medium changer device, and tape drive in Windows Device Manager (even if OS level drivers are not loaded or disabled?).
If it's a standalone drive then as I said previously it doesn't need device config to be run, it should show in the destination tab when you setup a backup job. If it's 'offline' then highlight the drive in ARCserve manager and set it online again.
If you are still getting no further, look for a file called tape.log in the \log directory under where you have installed ARCserve, it will log the boardscan to this file when the ARCserve tape engine is started, cut and paste just the section with the boardscan here please.
If you have time to do a screenshot of Windows device manager showing tape devices and medium changers (if applicable, that'd be cool too.
Just had one other thought - if you used BE on this machine before RSM might have reserved the drive/changer for BE, in which case run ARCserve device configuration and choose the option for enable/disable device for RSM and have ARCserve take ownership of it. An document showing it for older versions here, but the concepts are the same with the version you have and applies post W2K also:
If it is in a library, can you see both the medium changer device, and tape drive in Windows Device Manager (even if OS level drivers are not loaded or disabled?).
If it's a standalone drive then as I said previously it doesn't need device config to be run, it should show in the destination tab when you setup a backup job. If it's 'offline' then highlight the drive in ARCserve manager and set it online again.
If you are still getting no further, look for a file called tape.log in the \log directory under where you have installed ARCserve, it will log the boardscan to this file when the ARCserve tape engine is started, cut and paste just the section with the boardscan here please.
If you have time to do a screenshot of Windows device manager showing tape devices and medium changers (if applicable, that'd be cool too.
Just had one other thought - if you used BE on this machine before RSM might have reserved the drive/changer for BE, in which case run ARCserve device configuration and choose the option for enable/disable device for RSM and have ARCserve take ownership of it. An document showing it for older versions here, but the concepts are the same with the version you have and applies post W2K also:
-
1
- #5
davidmichel
Technical User
There has to be a tape library there in order to assign a drive to it.
Ck the faq section for the faq Which Driver to Use.
Also update
QO63594 119 MB 01/27/05 NT -BAB R11.1 SERVICE PACK 1 - ENGLISH
QO68139 17.9 MB 05/23/05 NT -WINDOWS 2003 SP 1 SUPPORT UPDATE
QO74248 10.6 MB 11/14/05 NT -DEVICE SUPPORT UPDATE 6
So what happens if you try to backup to the drive?
Is the only problem not being able to assign the drive to a non existant library?
Ck the faq section for the faq Which Driver to Use.
Also update
QO63594 119 MB 01/27/05 NT -BAB R11.1 SERVICE PACK 1 - ENGLISH
QO68139 17.9 MB 05/23/05 NT -WINDOWS 2003 SP 1 SUPPORT UPDATE
QO74248 10.6 MB 11/14/05 NT -DEVICE SUPPORT UPDATE 6
So what happens if you try to backup to the drive?
Is the only problem not being able to assign the drive to a non existant library?
- Thread starter
- #6
First off, let me thank you guys for replying and helping me out. Like I said in my initial post, I have been messing with this problem for about a week now, so all the "normal, routine" net admin stuff, I have already done. The device is a standalone tape drive, not in a library. It is in Device Manager (working properly and all). I tried the disabling trick so ARCserve would run it, but that didnt work. Also, when I do the Enable/Disable for RSM, it says no devices detected. Lastly, when I try to just forget about the device config and make a backup job, it gets all the way to the end and gives the error "Cannot submit the job due to unavailable group or device." I did copy/paste that log file. It shows the Ultrium getting detected...yet thats it...still can't use it. 
I am to the point of just switching back to Veritas...my head hurts.
03/03 08:45:30 [0fa4] ============ TAPE ENGINE SUMMARY LOG ====================
03/03 08:45:30 [0fa4] Product Info: [CA Inc.] [BrightStor ARCserve Backup] Ver[11.1]
03/03 08:45:30 [0fa4] Tapeeng Info: Date[Feb 3 2006] Time[15:47:18]
03/03 08:45:30 [0fa4] Debug Info : Level[1] Read/Write/TestUnitReady Logging[OFF]
03/03 08:45:30 [0fa4] =========================================================
03/03 08:45:30 [0fa4] Client Set DebugLevel: 1
03/03 08:45:30 [0fa4] *SAN: LDN:1 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] *SAN: LDN:2 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] *SAN: LDN:3 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] Loading Changer.dll: Date[Feb 2 2006] Time[17:25:46]
03/03 08:45:31 [0fa4] TapeDrive[3] ABSL:3060 <ULTRIUM 2 1783> S/N[]
03/03 08:45:31 [0fa4] ABSL = 0 0 0 0, adapterTransferSize = 131072
03/03 08:45:31 [0fa4] ABSL = 2 0 0 0, adapterTransferSize = 126976
03/03 08:45:31 [0fa4] ABSL = 2 0 4 0, adapterTransferSize = 126976
03/03 08:45:31 [0fa4] ABSL = 3 0 6 0, adapterTransferSize = 1052672
I am to the point of just switching back to Veritas...my head hurts.03/03 08:45:30 [0fa4] ============ TAPE ENGINE SUMMARY LOG ====================
03/03 08:45:30 [0fa4] Product Info: [CA Inc.] [BrightStor ARCserve Backup] Ver[11.1]
03/03 08:45:30 [0fa4] Tapeeng Info: Date[Feb 3 2006] Time[15:47:18]
03/03 08:45:30 [0fa4] Debug Info : Level[1] Read/Write/TestUnitReady Logging[OFF]
03/03 08:45:30 [0fa4] =========================================================
03/03 08:45:30 [0fa4] Client Set DebugLevel: 1
03/03 08:45:30 [0fa4] *SAN: LDN:1 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] *SAN: LDN:2 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] *SAN: LDN:3 Server NOT a PRIMARY/DISTRIBUTED, Marking Shared Device as UNAVAILABLE
03/03 08:45:30 [0fa4] Loading Changer.dll: Date[Feb 2 2006] Time[17:25:46]
03/03 08:45:31 [0fa4] TapeDrive[3] ABSL:3060 <ULTRIUM 2 1783> S/N[]
03/03 08:45:31 [0fa4] ABSL = 0 0 0 0, adapterTransferSize = 131072
03/03 08:45:31 [0fa4] ABSL = 2 0 0 0, adapterTransferSize = 126976
03/03 08:45:31 [0fa4] ABSL = 2 0 4 0, adapterTransferSize = 126976
03/03 08:45:31 [0fa4] ABSL = 3 0 6 0, adapterTransferSize = 1052672
Can you try submitting a job without using the backup wizard? The tape.log boardscan looks fine here. If it still doesn't help, try deleting the tape engine key as specified at the end of the first document link I gave you and restarting the tape engine.
I know it's no real consolation, but one of the major differences between BE and ARCserve is that it interfaces directly with your hardware via the tape engine, without the need for any OS level drivers for the tape drive and medium changer, so it's probably different to what you are used to dealing with in that respect.
I know it's no real consolation, but one of the major differences between BE and ARCserve is that it interfaces directly with your hardware via the tape engine, without the need for any OS level drivers for the tape drive and medium changer, so it's probably different to what you are used to dealing with in that respect.
davidmichel
Technical User
Ok you got the updates installed, thats good.
You have given up on trying to assign the stand alone tape drive to a library thats good.
Leave the tape drive as disabled, for direct attached SCSI the tape drive driver is bound to cause some problems.
Since this is stand along tape drive I doubt that deleting the Tape Engine registry key will help.
In the Manager Device window the drive should show up indented under the SCSI controller with a status of idle. While there check which group the drive is in.
Now the above message about unavailable group or device could just mean that the tape drive is in GROUP1 and the backup job submitted is pointing to GROUP0.
All else fails set the Tape Engine log to Detailed level and lets see what is going on.
You have given up on trying to assign the stand alone tape drive to a library thats good.
Leave the tape drive as disabled, for direct attached SCSI the tape drive driver is bound to cause some problems.
Since this is stand along tape drive I doubt that deleting the Tape Engine registry key will help.
In the Manager Device window the drive should show up indented under the SCSI controller with a status of idle. While there check which group the drive is in.
Now the above message about unavailable group or device could just mean that the tape drive is in GROUP1 and the backup job submitted is pointing to GROUP0.
All else fails set the Tape Engine log to Detailed level and lets see what is going on.
- Status
Similar threads
- Locked
- Question
- Locked
- Question