Another list member replied off-line telling me to make sure the Removable
Storage Manager in windows is disabled.
Sure enough, RSM was enabled and after disabling it, the windows box
appears to be leaving the other drives alone.
I'll be monitoring the system closely to make sure the windows server
really is leaving the drives alone.
Thanks.
On Thu, 1 Apr 2004, Steve Mickeler wrote:
>
> The shared drives hadnt been added to netbackup yet. They were seen by
> the OS and the static lun mappings were done but nothing was trying to
> use the drives, yet windows was still trying to communicate/reset the
> drives.
>
>
> On Thu, 1 Apr 2004, Paul Gimpelev wrote:
>
> > Just out of curiosity - did you configure the drive as an SSO drive in NBU?
> > If
> > you did, make sure that that the unix path to tape "/dev/rmt/X"
> > corresponds to
> > a proper "tapeX" device on Windows server.
> >
> > paulg
> >
> > On Mar 31, 4:36pm, Steve Mickeler wrote:
> > > Subject: [Veritas-bu] sharing tape devices between windows and unix
> > >
> > > Based on the problem I just experienced, and taking into consideration I'm
> > > a unix guy, not a windows guy, is there a "proper" way to get the windows
> > > server, running windows 2003 server, to be able to use 3 of my drives from
> > > the unix side without it causing havoc on my side ?
> > >
> > > The windows server is a Dell Poweredge 1650 with a JNI 6410 PCI HBA
> > > attached to the SAN. It's running NBU 4.5 FP6 and has an SSO license
> > > installed.
> > >
> > > We've zoned a single drive that only the windows server can see and use.
> > > It was when I expanded the drives on the zone for the windows server when
> > > problems on the unix nbu environment occured. It appeared like the windows
> > > server was trying to communicate/use the shared tape drives even though
> > > they has not been allocated to any storage unit on the windows nbu config.
> > >
> > > I'd like to make this SSO setup work because the single tape device on the
> > > windows box will cause some problems in the event that both a restore and
> > > a backup are required at the same time.
> > >
> > > Thanks.
> > >
> > >
> > >
> > >
> > > On Wed, 31 Mar 2004, Steve Mickeler wrote:
> > >
> > > >
> > > > The introduction of a new windows master server appears to be causing
> > > > the
> > > > I/O interruptions.
> > > >
> > > > The windows master server was zoned to allow it to see 3 of the 4 drives
> > > > that have been allocated to the unix master server & unix sso servers.
> > > >
> > > > So now I have to figure out why the windows server is trying to
> > > > communicate with those 3 tape drives.
> > > >
> > > >
> > > >
> > > > On Wed, 31 Mar 2004, Steve Mickeler wrote:
> > > >
> > > > >
> > > > > The I/O errors are also cuasing netbackup to freeze the tape that was
> > > > > in
> > > > > the drive when the error occured.
> > > > >
> > > > > ie:
> > > > >
> > > > > 03/31/2004 13:41:46 harbor titan1 FROZE media id 000036, could not
> > > > > write tape mark to begin new image
> > > > _______________________________________________
> > > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > > >
> > > _______________________________________________
> > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > >-- End of excerpt from Steve Mickeler
> >
> >
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
