Thanks, Jim -
The steps worked and now all 4 of my drives are shared and
duplications are running. But 2 duplications are coming directly
from the media server and the I/O is still going through the
master according to iostat on the master.
On Sat, 28 Jan 2006, Jim Peppas wrote:
> Date: Sat, 28 Jan 2006 21:58:30 +0200
> From: Jim Peppas <perf AT peppas DOT gr>
> To: 'Kathryn Hemness' <kfhemness AT ucdavis DOT edu>
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
>
> Hi.
>
> I think there is a mixup here. Do you want to share all drives or just split
> half of the drives to each media server?
>
>
> SSO drives have to have the same name....
>
> If you want to share all drives , you have to do the following:
>
> 1. Delete all Netbackup entries of all drives on all Master/media Servers.
> 2. Configure the drives on the first Media server (it might be the master,
> no problem) using names that refer to the Library , not the server. The
> simplest way is to run :
>
> /usr/openv/volmgr/bin/tpautoconf -set_gdbhost <Master_server>
> /usr/openv/volmgr/bin/tpautoconf -a
>
> 3. After you finish the configuration of the drives, by running a vmoprcmd
> command on that server see entries like:
>
> PENDING REQUESTS
>
> <NONE
>
> DRIVE STATUS
>
> Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl.
> ReqId
> 0 hcart2 TLD - No - -
> 1 hcart2 TLD - No - -
> 2 hcart2 TLD - No - -
> 3 hcart2 TLD - No - -
>
> ADDITIONAL DRIVE STATUS
>
> Drv DriveName Shared Assigned Comment
> 0 LIBA_LTO-1 No -
> 1 LIBA_LTO-2 No -
> 2 LIBA_LTO-3 No -
> 3 LIBA_LTO-4 No -
>
>
> 4. From the Java Admin.Console do the following (Note: If you have a Window
> Admin Console, all this stuff is much easier, since the Windows Console
> allows browsing for devices, while Java does not. In Java you have to know
> the expact paths for the drives)
>
> Run the Device Configuration Wizard (Recommended by Veritas). In the list
> with the hosts there should be the first server. Add the rest of them. By
> clicking throuout the rest of the wizard you should, at the end, have
> automatically have all drives as shared on all servers. If you run vmoprcmd
> again the "Shared" status should have changed from "No" to "Yes". Be sure to
> have installed an SSO key on each of your servers involved before running
> the wizard.
>
> >From this point on you have to define storage units for each media server.
> If you don't want servers to use all available drive, set the "Max
> concurrent drives" option to the desired amount (If you have 4 drives and
> want each server to use 2, put 2). This means that the servers will use 2
> drives max (Note: not 2 specific drives, any 2 drives available).
>
>
> It is also possible to run steps 1 and 4 only. You can try this first.
> Usually, the only setback you have is that Netbackup gives the Drive names.
> You have to change the names later on to your desired names. That why I run
> usually configure the drives first on the robot controller and then run the
> wizard
>
> Sorry for being too detailed.
>
> Regards,
> Jim
>
>
> -----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 Kathryn
> Hemness
> Sent: Saturday, January 28, 2006 6:04 AM
> To: Scott Jacobson
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
>
> Scott -
>
> Thanks for the vote of confidence, but I'm not there yet.
> Both the master and media servers are in each other's bp.conf file.
>
> I have a single robot with 4 drives in it. The drives are all visible on
> both of the servers. I've renamed the drives accessed from the media server
> differently from their corresponding device names on the master server. I
> used tpconfig on each server to assign the drives to Robot 0.
>
> In the Device Monitor in NetBackup java gui, I see 8 shared drives. All 4
> drives are in use; 2 on drives defined on the Master and the other 2 on the
> drives defined on the media server.
>
> Here's sort of what it looks like
> MasterDrive1= TLD ; MediaDrive1 = PEND-TLD
> MasterDrive2= DOWN-TLD ; MediaDrive2 = TLD MasterDrive3= DOWN-TLD ;
> MediaDrive3 = TLD
> MasterDrive4= TLD ; MediaDrive4 = PEND-TLD
>
> Error messages on my media server indicates RESERVATION CONFLICT for 2 scsi
> devices (probably the MasterDrive[23] indicated above).
>
> My duplications are running at fair speeds, but there's not been a need for
> a tape dismount/remount for tapes in use by my media server.
>
> The reason I had thought there might be a need for individual vm.conf files
> is because the NB51 Media Manager Guide indicates about 4 SSO settings for
> the vm.conf and I was wondering about whether or not the Master and Media
> servers should contain the same entries, and I don't even have a vm.conf
> file on my Media server.
>
> Anyway, I can't do any more work on the tpconfig stuff because my peak
> backup windows just opened. I'll do some more tweaking tomorrow if the
> media server RESERVATION CONFLICTS don't down all of the drives.
>
> I'm cc'ing this back to the list in case there are others who can shed light
> on this subject.
>
>
> On Fri, 27 Jan 2006, Scott Jacobson wrote:
>
> > Date: Fri, 27 Jan 2006 19:32:44 -0700
> > From: Scott Jacobson <SJACOBSO AT novell DOT com>
> > To: Kathryn Hemness <kfhemness AT ucdavis DOT edu>
> > Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
> >
> > Kathryn,
> >
> > >From a SSO standpoint you should be able to use "robtest"
> > to verify you can move tapes to drives onto the media server tape
> > drives FROM the Master Server
> >
> > If not, as Mark mentioned, make sure the conf files on both Master
> > and Media Servers know of one another - very important.
> >
> > Storage Unit definition needs both Master and Media server host names
> > and then applied to your Dup policy.
> >
> > I think your there... need to depart soon.
> >
> > -sj
> >
> > >>> Kathryn Hemness <kfhemness AT ucdavis DOT edu> 1/27/2006 6:29 pm >>>
> > Hi Scott -
> >
> > I've made some changes for unique drive names. The drives
> > on my Master server are Hagrid-* and the corresponding names on my
> > media server are Olympe-*. I've not defined 2 robotics; I still only
> > have 1 robot defined. This shared storage unit is for duplicating
> > disk-staged backups only; no backup policies use it.
> >
> > That said, here are the results of the vmoprcmd on both my master and
> > media servers:
> >
> > /usr/openv/volmgr/bin/vmoprcmd on the Master:
> >
> > PENDING REQUESTS
> >
> > <NONE>
> >
> > DRIVE STATUS
> >
> > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl.
> > ReqId
> > 0 hcart2 TLD - No -
> > -
> > 1 hcart2 TLD - No -
> > -
> > 2 hcart2 TLD - No -
> > -
> > 3 hcart2 TLD - No -
> > -
> >
> > ADDITIONAL DRIVE STATUS
> >
> > Drv DriveName Shared Assigned Comment
> > 0 Hagrid-1 Yes -
> > 1 Hagrid-2 Yes -
> > 2 Hagrid-3 Yes -
> > 3 Hagrid-4 Yes -
> > [/]
> >
> > /usr/openv/volmgr/bin/vmoprcmd on the Media Server: # ./vmoprcmd
> >
> > PENDING REQUESTS
> >
> > <NONE>
> >
> > DRIVE STATUS
> >
> > Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl.
> > ReqId
> > 0 hcart2 TLD - No -
> > -
> > 1 hcart2 TLD - No -
> > -
> > 2 hcart2 TLD - No -
> > -
> > 3 hcart2 TLD - No -
> > -
> >
> > ADDITIONAL DRIVE STATUS
> >
> > Drv DriveName Shared Assigned Comment
> > 0 Olympe-1 Yes -
> > 1 Olympe-2 Yes -
> > 2 Olympe-3 Yes -
> > 3 Olympe-4 Yes -
> >
> > Here's my new tpconfig on the Media server: # ./tpconfig -d
> >
> > Index DriveName DrivePath Type Shared
> > Status
> > ***** ********* ********** **** ******
> > ******
> > 0 Olympe-1 /dev/st/nh1c0t0l2 hcart2 Yes
> > UP
> > TLD(0) Definition DRIVE=1
> > 1 Olympe-2 /dev/st/nh1c0t0l3 hcart2 Yes
> > UP
> > TLD(0) Definition DRIVE=2
> > 2 Olympe-3 /dev/st/nh1c0t0l4 hcart2 Yes
> > UP
> > TLD(0) Definition DRIVE=3
> > 3 Olympe-4 /dev/st/nh1c0t0l5 hcart2 Yes
> > UP
> > TLD(0) Definition DRIVE=4
> >
> > Currently defined robotics are:
> > TLD(0) robot control host = albus.ucdavis.edu
> > volume database host = albus.ucdavis.edu
> >
> >
> > On Fri, 27 Jan 2006, Scott Jacobson wrote:
> >
> > > Date: Fri, 27 Jan 2006 18:00:45 -0700
> > > From: Scott Jacobson <SJACOBSO AT novell DOT com>
> > > To: Kathryn Hemness <kfhemness AT ucdavis DOT edu>
> > > Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
> > >
> > > Send me your "vmoprcmd" output and I'll give you a head start. Also
> > > Mark is correct, you need to those things as well.
> > >
> > > -sj
> > >
> > > >>> Kathryn Hemness <kfhemness AT ucdavis DOT edu> 1/27/2006 5:40:20 pm
> > > >>> >>>
> > > Scott -
> > >
> > > Did I miss something here? Did you intend to show me the results of
> > > your vmoprcmd or a tpconfig -d?
> > >
> > > On Fri, 27 Jan 2006, Scott Jacobson wrote:
> > >
> > > > Date: Fri, 27 Jan 2006 17:32:00 -0700
> > > > From: Scott Jacobson <SJACOBSO AT novell DOT com>
> > > > To: Mark.Donaldson AT cexp DOT com, Kathryn Hemness
> > <kfhemness AT ucdavis DOT edu>
> > > > Cc: veritas-bu AT mailman.eng.auburn DOT edu
> > > > Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
> > > >
> > > > Kathryn,
> > > >
> > > > In a SSO environment your Drive Names must be unique.
> > > >
> > > > In my environment for example, from the Master, run "vmoprcmd".
> > > These
> > > > are the names I use
> > > > to keep things straight.
> > > >
> > > > -sj
> > > >
> > > > >>> Kathryn Hemness <kfhemness AT ucdavis DOT edu> 1/27/2006 4:41 pm >>>
> > > > Hi Mark --
> > > >
> > > > Here are my tpconfigs on both the Master and Media servers:
> > > >
> > > > Master server: /usr/openv/volmgr/bin/tpconfig -d
> > > >
> > > > Index DriveName DrivePath Type
> > Shared
> > > > Status
> > > > ***** ********* ********** ****
> > ******
> > > > ******
> > > > 0 Hagrid-1 /dev/rmt/3cbn hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=1
> > > > 1 Hagrid-2 /dev/rmt/2cbn hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=2
> > > > 2 Hagrid-3 /dev/rmt/1cbn hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=3
> > > > 3 Hagrid-4 /dev/rmt/0cbn hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=4
> > > >
> > > > Currently defined robotics are:
> > > > TLD(0) robotic path = /dev/sg/c0tw2001005013e00369l1,
> > > > volume database host = albus.ucdavis.edu
> > > >
> > > >
> > >
> > **********************************************************************
> > *********
> > > >
> > > > Media Server:# /usr/openv/volmgr/bin/tpconfig -d
> > > > Index DriveName DrivePath Type
> > Shared
> > > > Status
> > > > ***** ********* ********** ****
> > ******
> > > > ******
> > > > 0 Hagrid-1 /dev/st/nh1c0t0l2 hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=1
> > > > 1 Hagrid-2 /dev/st/nh1c0t0l3 hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=2
> > > > 2 Hagrid-3 /dev/st/nh1c0t0l4 hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=3
> > > > 3 Hagrid-4 /dev/st/nh1c0t0l5 hcart2 Yes
> > > > UP
> > > > TLD(0) Definition DRIVE=4
> > > >
> > > > Currently defined robotics are:
> > > > TLD(0) robot control host = albus.ucdavis.edu
> > > > volume database host = albus.ucdavis.edu
> > > >
> > > > All I/O is still going through the device paths of the Master
> > > Server.
> > > >
> > > >
> > > >
> > > > On Fri, 27 Jan 2006 Mark.Donaldson AT cexp DOT com wrote:
> > > >
> > > > > Date: Fri, 27 Jan 2006 15:51:24 -0700
> > > > > From: Mark.Donaldson AT cexp DOT com
> > > > > To: kfhemness AT ucdavis DOT edu, veritas-bu AT mailman.eng.auburn
> > > > > DOT edu
> > > > > Subject: RE: [Veritas-bu] Examples of SSO vm.conf files
> > > > >
> > > > > It's not vm.conf, it's tpconfig.
> > > > >
> > > > > Be sure which drives are the shared ones, ie /dev/rmt/x on
> > server1
> > > > is
> > > > > /dev/rmtY on server2. Then carefully setup the drives as shared
> > > > drives via
> > > > > tpconfig.
> > > > >
> > > > > vm.conf is plain.
> > > > >
> > > > > Really, the manual is your friend on an SSO setup.
> > > > >
> > > > > -M
> > > > >
> > > > > -----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
> > > Kathryn
> > > > > Hemness
> > > > > Sent: Friday, January 27, 2006 2:26 PM
> > > > > To: veritas-bu AT mailman.eng.auburn DOT edu
> > > > > Subject: [Veritas-bu] Examples of SSO vm.conf files
> > > > >
> > > > >
> > > > > Greetings -
> > > > >
> > > > > I'm trying to setup SSO for an LTO2 library shared between a
> > > Solaris
> > > > 9
> > > > > Master and a RHEL3 Linux Media server. Can someone give me
> > > examples
> > > > of
> > > > > the vm.conf files on each server?
> > > > >
> > > > > Right now, I'm using an evaluation license and I can see drives
> > > > > on both Master and Media servers and the robotic is controlled
> > > > > by the Master. However, all of the traffic is still going
> > through
> > > > > the Master server. The Master server has a vm.conf but my Linux
> > > > > media server doesn't.
> > > > >
> > > > >
> > > > > --kathy
> > > > > _______________________________________________
> > > > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > > > >
> > > >
> > > > --kathy
> > > >
> > > >
> > >
> > ======================================================================
> > =========
> > > > Kathryn Hemness kfhemness AT ucdavis DOT edu
> > > > System Administrator phone: 530.752.6547
> > > > Campus Data Center & Client Services fax: 530.752.9154
> > > > _______________________________________________
> > > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > > >
> > >
> > > --kathy
> > >
> > >
> > ======================================================================
> > =========
> > > Kathryn Hemness kfhemness AT ucdavis DOT edu
> > > System Administrator phone: 530.752.6547
> > > Campus Data Center & Client Services fax: 530.752.9154
> > >
> >
> > --kathy
> >
> >
> ============================================================================
> ===
> > Kathryn Hemness kfhemness AT ucdavis DOT edu
> > System Administrator phone: 530.752.6547
> > Campus Data Center & Client Services fax: 530.752.9154
> >
>
> --kathy
>
> ============================================================================
> ===
> Kathryn Hemness kfhemness AT ucdavis DOT edu
> System Administrator phone: 530.752.6547
> Campus Data Center & Client Services fax: 530.752.9154
> _______________________________________________
> 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
>
--kathy
===============================================================================
Kathryn Hemness kfhemness AT ucdavis DOT edu
System Administrator phone: 530.752.6547
Campus Data Center & Client Services fax: 530.752.9154
|
