Hi Karen !
Thanks for your reply ...
This is the output of
# ./bpstulist -L
Label: BK1000-dlt
Media Type: Media Manager (2)
Host Connection: BK1000
Number of Drives: 6
On Demand Only: no
Density: dlt (13)
Robot Type/Number: ACS (1) / 0
Max Fragment Size: 0
Max MPX/drive: 4
Label: BK1000-ndmp
Media Type: NDMP (3)
Host Connection: BK1000
Number of Drives: 2
On Demand Only: yes
Density: dlt (13)
Robot Type/Number: ACS (1) / 1
Max Fragment Size: 0
Max MPX/drive: 1
NDMP attach host: fs32
I created the 2nd one, because I realized that a class with NDMP requests
a robot of the type NDMP ...
Again my desired setup:
fs32-filer--- connected to 2 DLT's in the STK Lib
BK1000--- connected to 6 DLT's in the same STK
BK1000 --- owns the robotic control
With the 2 robot setup I'm hung now at error 96 - no media available,
which is quite clear to me, because alle media are in a volume group
owned by robot 0 ...
Regards
Axel
*********** REPLY SEPARATOR ***********
On 15.06.2001 at 07:24 Karen Schoenbauer wrote:
>You need to look at how you configuref your storage unit.
>
>Bpsched will fork a process which checks the drive status. This fork
>process uses what you have configured for the storage unit.
>
>> -----Original Message-----
>> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
>> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Axel
>> Kunze
>> Sent: Friday, June 15, 2001 5:25 AM
>> To: veritas-bu AT mailman.eng.auburn DOT edu
>> Subject: [Veritas-bu] Help on NDMP
>>
>>
>> Hello everybody !
>>
>> I'm now getting crazy with this NDMP ....
>>
>> I configured our NetApp Filer with 2 DLT7000 out of the STK 9740
>> Library. In the
>> Device Manager the drives are available via /ndmp/... and UP. Fine ...
>> I want my Solaris Box to control the STK and the other 6 drives,
>> so I left the
>> robotic control, where it was ...
>> This is what tpconfig shows now:
>>
>> 0 QUANTUMDLT70000 /dev/rmt/0cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=0
>> 1 QUANTUMDLT70001 /dev/rmt/1cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=1
>> 2 QUANTUMDLT70002 /dev/rmt/2cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=2
>> 3 QUANTUMDLT70003 /dev/rmt/3cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=3
>> 4 QUANTUMDLT70004 /dev/rmt/4cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=4
>> 5 QUANTUMDLT70005 /dev/rmt/5cbn dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=5
>> 6 DAB-FS30_STK9740_Drive /ndmp/nrst0a dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=6
>> 7 DAB-FS30_STK9740_Drive /ndmp/nrst1a dlt No
>> UP
>> ACS(0) Definition ACS=0, LSM=0, PANEL=1, DRIVE=7
>>
>> The set_ndmp_attr -verify are running as well ...
>>
>> Now I set up a NDMP Class with a NDMP Client, start a manual
>> backup and Netbackup queues
>> the job and ends up with code 213 - no storage units available for use
>...
>>
>> Where did I misconfigure this device configuration ?!?
>>
>> Regards
>>
>> Axel Kunze
>>
>> _______________________________________________
>> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
|
