The problem with the attached statement: "The problem is that this script
mismatches your drive numbers to drive path" is incorrect. Vmconf does not
match up drives and paths, it gives the user a list of drives and paths, and
the user is responsible for inputting them in the correct order. After using
vmconf or tpconfig it is always good to manually check the assignments. I
suggest using robtest to insert a tape into a drive then using the "mt -f
/dev/rmt/xxx status" command to see which drive has the tape. This is the
best way to insure that the tape drives match the paths. While this is time
consuming it should only have to be done once, unless more drives are added.

Patrick Whelan 
Consulting 
[NBU (with extensions) and Storage Migrator for UNIX] 
[VxFS and Volume Manager]
pwhelan AT veritas DOT com

Of course this is just my opinion, I could be wrong. - Dennis Miller
Friends help friends move, good friends help move bodies - Unknown.


                -----Original Message-----
                From:   David A. Chapa [mailto:david AT datastaff DOT com]
                Sent:   Friday, July 14, 2000 6:03 AM
                To:     Everett, Craig
                Cc:     'veritas-bu AT mailman.eng.auburn DOT edu'
                Subject:        Re: [Veritas-bu] FYI: Netbackup 3.2
Installation problem

                I've always been a fan of tpconfig...rarely teach 
                vmconf.  You know what you are getting with tpconfig 
                because the control is in your hands.

                David

                Quoting "Everett, Craig" <Craig_Everett AT intuit DOT com>:

                > FYI:
                > I just found out that using the vmconf script to 
                automatically install a
                > robot during an initial Netbackup installation is at 
                best 50% successful on
                > average. The script identifies robotic controllers 
                and drives and then adds
                > them to your database for use with Netbackup. The 
                problem is that this
                > script mismatches your drive numbers to drive paths 
                so that when you go to
                > mount a tape for backup the drive automatically downs 
                itself. The robot
                > will
                > mount a tape in drive3 and it will actually be in 
                drive4.
                >
                > Solution: Don't use vmconf to automatically 
                install/configure a robot. It
                > doesn't work properly. Support says it's supposed to 
                be fixed in 3.4 but
                > I'm
                > not holding my breath.
                >
                > Thanks,
                >
                > Craig Everett
                > Intuit Inc,
                > San Diego
                > _______________________________________________
                > Veritas-bu maillist  -  Veritas-
                bu AT mailman.eng.auburn DOT edu
                > 
                http://mailman.eng.auburn.edu/mailman/listinfo/veritas-
                bu
                > 



                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                David A. Chapa                847 413 1144 p
                Director of Technology        847 413 1168 f
                DataStaff, Inc.               http://www.datastaff.com
                nbu-lserv AT datastaff DOT com       majordomo AT datastaff DOT 
com
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                _______________________________________________
                Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
                http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu