Or use the old good method to edit the bihavior file .
change the TRIES_PER_PERIOD to 0

smpt


>  -------Original Message-------
>  From: Bobby Williams <bobbyrjw at bellsouth.net>
>  Subject: Re: [Veritas-bu] Pausing scheduling under NetBackup 6
>  Sent: 04 Aug '06 11:29
>  
>  Just disable the service before you reboot.??Then NB won't start until after
>  you do the maintenance.
>  
>  
>  
>  
>  Bobby Williams
>  2205 Peterson Drive
>  Chattanooga, Tennessee??37421
>  423-296-8200
>  
>  -----Original Message-----
>  From: veritas-bu-bounces at mailman.eng.auburn.edu
>  [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Nardello,
>  John
>  Sent: Thursday, August 03, 2006 5:27 PM
>  To: veritas-bu at mailman.eng.auburn.edu
>  Subject: [Veritas-bu] Pausing scheduling under NetBackup 6
>  
>  Under NetBackup 6 MP3, we've noticed that the "nbemmreq -suspend_scheduling"
>  command seems to only be in effect until daemons get cycled, and after that
>  normal scheduling seems to resume.
>  
>  Short of disabling a service, does anyone have a better way of making sure
>  backups don't start automatically after a server reboot while we're doing
>  maintenance ? Setting tries = 0 worked under NB 5 but you can't do that
>  through the CLI anymore under NB 6.
>  
>  Any ideas ?
>  - John Nardello
>  
>  
>  _______________________________________________
>  Veritas-bu maillist??-??Veritas-bu at mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>  _______________________________________________
>  Veritas-bu maillist??-??Veritas-bu at mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>