07-18-2008 06:15 AM
07-18-2008 11:40 AM
05-13-2009 07:27 AM
05-13-2009 08:24 AM
05-13-2009 10:20 AM
09-17-2009 06:02 AM
09-17-2009 06:18 AM
09-17-2009 07:56 PM
There is a bug with version 6.5.2 to 6.5.3. As far as I can recall, you will need to upgrade to at least 6.5.3.1 or higher to remove the problem.
The bug that occurs is around using calendar schedules which will only run a specific backup/schedule once per day. If you do a manual backup earlier on in the day, the schedule backup will not run later (you can use nbpemreq command to take a look at what is scheduled to run for a specific date).
Until you can upgrade your system you should be able to work around the problem when you have to run a job manually by running the job manually again when it is scheduled to run. If you leave the job (skipping the scheduled run) it should run fine the next day.
Bit of a pain but the upgrade will solve the actual problem
09-21-2009 06:56 AM
09-21-2009 04:23 PM
09-23-2009 09:27 AM
09-23-2009 12:53 PM
I would be willing to bet that applying 6.5.4 DID address your issue - although I'm not sure which specific issue you were experiencing, so I can't prove it by throwing you a specific Etrack number.
There have been A LOT of scheduling fixes between 6.5.1 and 6.5.4, and you can check the Tech Alerts and 6.5.4 READMEs if you don't believe me. I see over a dozen resolved Etracks containing "schedule" in the 6.5.4 README alone - and that's JUST counting in the 6.5.4 section!
(This is part of why we in Support always harp on you to always have the latest Release Update installed.)
I WILL say that recreating your policy from scratch may also have helped towards your resolution, too, though. :)