Calendar not working with datacenter 4.5mp3 and RH 7.3

[msleeper]

Please toss me a bone here.
I've been working with Veritas for SIX months on this. They can't seem to fix it.
Everything else works except calendar based backups on the following system:

Dell Poweredge 2500, 2X1.0GHz Proc, 2GB RAM, tons of disk.
Quantum|ATL P3000 tape library with 6 IBM LTO-1 drives.
Redhat 7.3
Veritas Datacenter 4.5mp1,2&3 all tried and failed.

Absolutely nothing shows up in the logs when the schedule is supposed to run. It doesn't even try to run.

I've also tried this on a completely different cpu/tape-robot and they haven't worked either.

Any info would be appreciated.
Thanks,
Mark Sleeper
mark.sleeper@noaa.gov

 

[PGPhantom]

I hate to tell you but ... Calendar based backups are not good. I set a few up, some worked, some did not. I ended up deleting all calendar based schedules because there are conflicts with frequency based schedules.

From my understanding FP3 (Feature Pack 3) is supposed to address this - That remains to be seen though.

For miscellaneous problems I have often found that DCOM is the cause. Run dcomcnfg and check the default security tab. There are 3 defaults, access, Launch and configuration. All three need to have the local accounts interactive, administrators and system. If any are missing - Problems arise that cannot be explained. This should be checked on all your servers but specifgically your master.

For one of your calendar based backups - Is it in a policy of it's own? If not, add it as a new schedule into an existing policy where there are frequency based full backups. I have found that full backups of the system in question are key to some of the calendar based schedules running.

 

[Sekhar]

I have a similar problem with NB Datacenter 4.5 running on Solaris 8. The calender based monthly full was supposed to start last night, but it did not.

Another problem I have with frequency based backups for the daily incrementals. I have the start window from 6pm to 2am next day. Istead of starting at 6pm, the backups start at 12am. There was no activity at all at 6pm.

I have another policy with the start window of 1 am to 9am and this one starts exactly at 1am.

Thanks in advance for your help.

Sekhar.

 

[msleeper]

Problem Solved!
After two days with a Veritas engineer in-house we've traced the problem to an issue with the Mountain Time Zone! He didn't know how or why but now the issue is with the programmers in India. Hopefully a patch will be included in the next fp/mp.