But, aren't we getting away from the OP's question?
I don't think Kate's really looking for advice about whether running an
external scheduler is "recommended" or even acceptable, but if you DO
run an external scheduler, are the policy priorities respected??
Paul
--
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Curtis
Preston
Sent: July 25, 2007 3:39 PM
To: Steven L. Sesar
Cc: veritas-bu@mailman.eng.auburn.edu; Greenberg, Katherine
(ISD,IT)
Subject: Re: [Veritas-bu] Priority w/ an External Scheduler?
I have a different way of handling that requirement.
---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies
________________________________
From: Steven L. Sesar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 12:31 PM
To: Curtis Preston
Cc: Greenberg, Katherine (ISD, IT);
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Priority w/ an External Scheduler?
The only other justification I can think of for using an
external scheduler, is, when there are batch processing operations
against, say, Oracle databases, which need to run during your backup
window. Using the same batch processing application, you can add a
backup to the chain. This is a very specific situation - backups of
Oracle databases and batch processing against said databases which need
to occur during the same backup window.
We toyed with the idea, but in the end, we pushed back on the
apps folks to fix their apps, so chains would run quicker and run either
before our backups begin, or after they complete. We are currently
considering hardware-based snapshot capability and array-based
replication, which will give our apps folks back some time for chains to
run.
--Steve
Curtis Preston wrote:
While I agree with Justin's response, I really don't like using
external schedulers for NetBackup unless absolutely necessary. The only
real requirement I can think of that would force me to an external
scheduler is multi-host dependencies, because external schedulers are
really good at that.
I've seen the following justifications:
1. I want a backup job to run exactly at 3 AM.
a. You can do that with NBU, good windows, and
dedicated resources.
2. I want to tell all my jobs exactly when to run.
a. Why? Stop over engineering your backup
environment. Let go and let Symantec. ;) You'll be amazed at how well
run a NBU environment can be if you just give all your backups the same
window, the same resources, and just set priorities. It's a beautiful
thing and requires VERY little maintenance.
2. An external scheduler is already hooked into our overall
reporting mechanism.
a. Lousy excuse to cripple the NBU scheduler.
Spend the time necessary to hook NBU into your overall reporting
mechanism.
Short of the one valid reason I've seen (multi-host
dependencies), you'll never approach the level of resource utilization
and efficiency that the NetBackup scheduler can give you by using an
external scheduler. For example, while NBU can have thousands of queued
jobs waiting for resource (to make sure that something is always using
the tape drives) without consuming any additional resources, doing that
with an external scheduler is impossible.
---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Greenberg, Katherine (ISD, IT)
Sent: Wednesday, July 25, 2007 10:55 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Priority w/ an External Scheduler?
Have you guys ever used an external scheduler?
I'm trying to figure out if that impacts Policy Prioritization
or not.
Since our backups aren't scheduled thru NetBackup (there are
schedules, but no windows) does prioritization come into play or no?
We're running 5.1 MP6.
TIA,
Kate
====================================================================================
La version française suit le texte anglais.
------------------------------------------------------------------------------------
This email may contain privileged and/or confidential information, and the Bank
of
Canada does not waive any related rights. Any distribution, use, or copying of
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately
from
your system and notify the sender promptly by email that you have done so.
------------------------------------------------------------------------------------
Le présent courriel peut contenir de l'information privilégiée ou
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de
votre
ordinateur toute copie du courriel reçu.
_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
