Hi Brian,
If you want to schedule your jobs trough C-M, and still use incremental or
differential backups, you will have to assign your jobs with backup -i from the
master. Netbackup DOES NOT support incremental backups from the client (I
believe it is a big shot coming of the product).
Control M does not know any thing, basically you ask it to schedule different
backups, Sunday full, m-f differential etc. Using backup -i -c (class) -s
(Schedule) -h Host. So you create different jobs for that.
Yes you can create a script that would re-start the job when an exit status 41
is encountered. I could think of multiple ways of doing it, just a matter of
choice. Control-M also allows you to check a file etc...
As a personal note Control-M scheduler is very powerful, but Veritas has not
been providing the tools to use it with full capacity. I have got multiple
tickets/enhancement requests open with Veritas for over a year (2-3 on some) on
these... Ohh-well...
Have a great week.
Regards,
Yucel
Message: 6
From: Brian_Drager AT Vanguard DOT com
To: veritas-bu AT mailman.eng.auburn DOT edu
Date: Wed, 31 Oct 2001 14:22:38 -0500
Subject: [Veritas-bu] NetBackup 3.4 & Control M
Looking for someone who uses Control M. We have control M in our shop for MVS &
other UNIX/NT jobs. If there a separate piece you have to by for Control M to
work with NetBackup?
I'm assuming that you still need to set up schedules for Full, Cum, & diff.
backups. You just leave the times outs. How does Control M know which schedule
to kick off whether its a daily, or weekly or a monthly schedule if you take
your days & window duration out of the schedule.
What if a backup fails with a status code 41. Will control M autostart job?
Thanks for any information.
---------------------------------------------------------
Yucel M. Erbilgic
erbilgic.ym AT pg DOT com
(513) 945-1859
|