[Veritas-bu] sharing tape devices between windows and unix
JSimon at reliant.com
Thu Apr 1 11:21:22 CST 2004
I would really recommend against sharing fibre devices between Windows and Unix.
1. Everytime you reboot you are going to cause PLOGI's on the fabris, and you know Windows reboots a lot, since you are running JNI cards you will have problems because their implmentation of FCP2 error correction isn't quite complete. So rebooting a Windows machine could cause backups on the Unix box to fail (this assumes you are running JNI in the Unix boxes if not ignore this).
2. There are (or were as of last Sept) issues with SSO on Windows, it doesn't play nice with Unix, Windows will try to reserve the drives even when not in use. So be aware, the Unix box might not get to use the tape drives when it needs to.
3. I noticed other people mention tape number changing on Windows, seen this too, there are issues with JNI and persistant binding on Windows, and if stuff moves around it will completely hose your SSO config.
If you really want to mix them, I would at least switch to Emulex, where FCP2 works completely and there is a special Windows persistant binding driver so stuff doesn't move around.
From: veritas-bu-admin at mailman.eng.auburn.edu
[mailto:veritas-bu-admin at mailman.eng.auburn.edu]On Behalf Of Steve
Sent: Wednesday, March 31, 2004 3:36 PM
To: veritas-bu at mailman.eng.auburn.edu
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
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.
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.edu
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
More information about the Veritas-bu