My recent discovery of the non-restart problem was in a cron-called
script.  

Maestro is managing the Documentem backup since it has so many
cross-server dependencies.

We don't have an all-or-nothing rule for scheduling so I tend to use
cron for all my all-on-one-server netbackup reports and stuff.  I'm have
full control this way rather than putting in a ticket to the scheduling
guy.

I do have a couple NB activities crossing server boundaries, mostly
related to Netapp snapshot processing, and I'm resisting getting these
into the enterprise scheduler and instead I'm relying ssh and shared
keys.  I know this is less reliable.  My old-school habit is showing on
this one... I'm cringing on giving up my control on these couple
backups.

What I really want is the parent_start_notify script to work as I want
it ("correctly", IMO) and have the NB scheduler drive all and get rid of
my few cron driven scripted backups.

-----Original Message-----
From: Jeff Lightner [mailto:jlightner AT water DOT com] 
Sent: Thursday, January 17, 2008 10:57 AM
To: Donaldson, Mark - Broomfield, CO; Bob.A.Stump AT fnis DOT com;
VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] 3rd party scheduling

I'm confused by this.  If you have Maestro why do you use cron to do the
scheduling that you had a problem with?

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
Mark.Donaldson AT cexp DOT com
Sent: Thursday, January 17, 2008 12:13 PM
To: Bob.A.Stump AT fnis DOT com; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] 3rd party scheduling

I came across one recent disadvantage of external scheduling, in my case
it's simply cron calling scripts.

The automatic-retry-in-event-of-failure feature of NB doesn't work
anymore.  Really, it's "retry withing window" and if there's no
scheduled windows, then there's no retry.

I guess I'm not in on on this trend you're describing.  Except for a few
applications that require massive multi-server coordinated preparation
(Documentum, for example) there's no advantage for us to not use the
built-in NB scheduler.

To answer your last question, we use Maestro for enterprise scheduling.

-M

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Stump,
Bob A
Sent: Wednesday, January 16, 2008 9:36 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 3rd party scheduling

I have seen a trend to stop using NetBackup for starting and monitoring
backups. The move has been to doing all command line backups from a 3rd
party scheduler as part of a true enterprise scheduling, monitoring and
management implementation. NetBackup is simply one of many products that
are controlled by the enterprise 3rd party sheduler/monitor. What are
the drawbacks to moving in this direction?

What are some of the enterprise scheduling and monitoring/management 3rd
party solutions have you recently seen? Autosys? Stonebranch?

______________

The information contained in this message is proprietary and/or
confidential. If you are not the 
intended recipient, please: (i) delete the message and all copies; (ii)
do not disclose, 
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition, 
please be aware that any message addressed to our domain is subject to
archiving and review by 
persons other than the intended recipient. Thank you.
_____________

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu