Did you create new storage units for your media server? Reboot? Assign your policy to the new storage unit?
Make sure that your both servers have the other in their bp.conf file. Best guarantee is to have each labeled as a "SERVER" rather than a "MEDIASERVER". Master server is listed first, of course, in both servers. -M -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathryn Hemness Sent: Friday, January 27, 2006 4:42 PM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files 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 [EMAIL PROTECTED] wrote: > Date: Fri, 27 Jan 2006 15:51:24 -0700 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.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: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Kathryn > Hemness > Sent: Friday, January 27, 2006 2:26 PM > To: veritas-bu@mailman.eng.auburn.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@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > --kathy ============================================================================ === Kathryn Hemness [EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center & Client Services fax: 530.752.9154 _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu