Kathryn

You do need a storage unit for every media server that will be backing
up data.  The policy should point to the storage unit of the media
server you want to back up to.  The tpconfig entry on the media server
will point to the master as having the library control however - See the
tpconfig output below - the media server "robotic control host points to
the master"

Monte

-----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 4:40 PM
To: Scott Jacobson
Cc: Mark.Donaldson AT cexp DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Examples of SSO vm.conf files

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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu