Dave,
It sounds like a binding problem. Are those tape drives connected via a SAN
switch? I suggest you check the connectivity of those drives and make sure the
connectivity is configured correctly at the OS level. What does "inquire" say
when you run it on the dedicated storage node?
On Feb 6, 2013, at 4:16 PM, <dave2 AT CAMBRIDGECOMPUTER DOT COM>
wrote:
> Hi,
>
> We are seeing a case where NetWorker is failing to mount a tape on a new
> dedicated storage node due to it believing there is a serial number
> mismatch.
>
> The first time we saw this, I had configured the drives manually (via
> jbedit), so there was no serial number in the tape drive resource.
>
> The second time, I used dvdetect and the gui based autochanger
> configuration method.
>
> The server's daemon.log shows the following:
>
> …
>
> 38752 02/06/13 11:07:29 nsrd rd=crm:/dev/rmt/2cbn Eject operation in
> progress
>
> 42506 02/06/13 11:07:29 nsrd media alert: device "/dev/rmt/2cbn": serial
> number mismatch, check system device ordering.
> Expected "Serial Numbers:ATNN=IBM U
> LTRIUM-TD2 351A600203:351A600203", found ":ATNN=IBM ULTRIUM-TD3
> 7410 810032:7410810032"
>
> 72504 02/06/13 11:07:29 nsrd rd=crm:/dev/rmt/2cbn eject operation failed:
> read open error: drive status is 65329 35 The
> drive serial number has changed
>
> 7224 02/06/13 11:07:30 nsrd [Jukebox `cdl', operation # 910]. read open
> error: drive status is 65329 35 The drive serial
> number has changed
>
> …
>
> I'm noticing the following:
>
> 1. the serial number mismatch says "/dev/rmt/2cbn," not
> "rd=crm:/dev/rmt/2cbn"
>
> 2. The serial number of rd=crm:/dev/rmt/2cbn is 7410810032. This is
> in changer "DD1"
>
> 3. The serial number of /dev/rmt/2cbn (on the backup server) is
> 351A600203. This is in changer "CDL-old"
>
>
>
> Environment Info:
>
> NSR Server is Solaris, NetWorker 7.6.4.5
>
> NSR Dedicated Storage Node is Solaris, NetWorker 7.6.4.5
>
> Anyone see this, or have any thoughts about it?
|
