Instead of bpstart_notify, perhaps you should define a User-initiated
schedule and have your script do a manual bpbackup of each filesystem
after it locks the VOB.  bpbackup -w will wait and return a status on
completion.

Using the bpstart/bpend setup, you would need to create a separate
policy for each filesystem.  That could be difficult to maintain.

Hope this helps


On Thu, 25 Dec 2003, David Thome wrote:

>
> I'm trying to finish a script that  needs to lock one VOB,  backup it's
> associated filesystem,  unlock it and then go on to the next VOB.  I
> don't want  to lock all VOBS at once during the backup,  just one at a
> time.
>
> I may need to use "bpstart_notify" and "bpend_notify" to accomplish
> this.  Not sure how best to use these to do this task.
>
> The output of
>
> # /usr/atria/bin/cleartool lsvob  -host hostname<?xml:namespace prefix =
> o ns = "urn:schemas-microsoft-com:office:office" />
>
> is below.
>
> column one is *
>
> column two is name of the vob (need to lock and unlock this)
>
>
>
> column three is name of filesystem to backup
>
>
>
> I used awk to pull these out and place in appropriate spot
>
>
>
> lock and unlock the name of the vob
>
> backup the filesystem name
>
>
>
> I think I'm close I just need some advise on how to finish off the job.
>
>
>
> Again I only want to lock one VOB,  back it up,  then unlock it and move
> on to the next VOB.  Only locking one VOB at a time.
>
>
>
> Thank you very much in advance for any help you can offer.
>
>
>
> # /usr/atria/bin/cleartool lsvob  -host hostname
>
>
>
> * /vobs/air            /vobstore/air.vbs public
>
> * /vobs/ground         /vobstore/ground.vbs public
>
> * /vobs/satcomdev      /vobstore/satcomdev.vbs public
>
> * /vobs/passdev        /vobstore/passdev.vbs public
>
> * /vobs/release        /vobstore/release.vbs public
>
> * /vobs/alandev        /vobstore/alandev.vbs public
>
> * /vobs/redhat         /vobstore/redhat.vbs public
>
> * /vobs/tools          /vobstore/tools.vbs public
>
> * /vobs/brokerdev      /vobstore/brokerdev.vbs public
>
> * /vobs/enduserdev     /vobstore/enduserdev.vbs public
>
> * /vobs/cm_testing     /vobstore/cm_testing.vbs public
>
> * /vobs/cccq_test_unix /vobstore/cccq_test_unix.vbs public
>
>
>
>
>
>
>
> Bpstart_notify ??
>
> POLICY=
>
> >SCHED=
>
> >FILE=/opt/openv/netbackup/logs/start.stop
>
> >
>
> >for vob in `/usr/atria/bin/cleartool lsvob  -host  hostname`
>
> >do
>
>
>
> > echo ?$vob? | awk ?{print $2}? > /tmp/vobname
>
> > echo ?Locking vob:$/tmp/vobname? >> $FILE
>
> > /usr/atria/bin/cleartool lock vob:$/tmp/vobname   # place the vob name
> here
>
> >
>
> > echo ?$vob? | awk ?{print $3}? > /tmp/vobfs
>
> > echo ?Calling backup for vob:$/tmp/vobname? >> $FILE
>
> > /usr/openv/netbackup/bin/bpbackup  -iw  $/tmp/vobfs    # (vob
> filesystem name here)
>
>
>
> Bpend_notify ??
>
> > echo "unLocking Vob $vob" >>$FILE
>
> > /usr/atria/bin/cleartool unlock vob:$/tmp/vobname   #place the vob name
> here
>
> >
>
> > echo "finished" >> $FILE
>
> >done
>
> >exit
>

-- 
D. Joe Royer II       Collective Technologies
CCNA, CISSP, VCP      http://www.colltech.com
jroyer AT colltech DOT com