change schedule time / nbpemreq reset

[Claudio_Veronez]

Hello,

I had a problem W/ daylight saving
and created a discussion as
https://www-secure.symantec.com/connect/forums/great-catalog-problem-daylight-saving-error

So our Great friend Andy Welburn helped me to find the root of the problem,

https://www-secure.symantec.com/connect/forums/frequency-schedule-0#comment-3635371


Basicali..

I had a date problem, Master server has ran 3 days w/ a wrong date (mars 20, 21, 22) and not (feb 20.21.22)

I have set the rignt date, but almos no job starts automatically because the

nbpemreq -predic_all  say that my jobs will run in mars 23.

Is there anyway of  "reset" or rescan the policies ?

THANKS a Lot Andy Welburn, I ĺl create a new discussion "Andy for TA now"

[David_McMullin]

What did support say when you called them?

[Claudio_Veronez]

I didn call them

should I call them? by phone or something?

where can I find it?

[Andy_Welburn]

http://www.symantec.com/business/support/overview.jsp?pid=15143

Should be links to e-mail support & Contact Technical Support on right hand side.

[Claudio_Veronez]

I'll hava to see about contrats and stuff.

[Claudio_Veronez]

We bought netbackup through SUN

I'll have to call them and see what happen. the problem is.. I have to do schedulles manually..

[Claudio_Veronez]

Any idea what should I keep trying while the suport waits?

I had said to our account manager about it, he told me that it shoul take a while.

I had created another policy and it is working fine.. the problem is..

as the policy ran w/ the Mar date, the "next backup windows" was set to Mar,


Now the date is right in FEB and the jobs won't start automatically

Any Idea??

[Claudio_Veronez]

I had removed (expired) backups w/ date MAR

and still not working..

the nbpemreq still dated to MAR


any other Idea?

[Marianne]

Claudio, the STREAMS file under ../netbackup/db/images/<client> play a role when calculating next due backup. Rename or move one client's file to something like oldSTREAM... and try the predict again.

**EDIT**
Run nbpemreq -updatepolicies after you rename/move STREAMSxxx file, then do another predict.

[David_McMullin]

She is the bomb!!

[Claudio_Veronez · Accepted solution]

Hello Marianne I have seen your post at the other discussion,

I have tryed that and didn´t worked for me.
I also tryed to remove from catalog the backups, (expire and stuff) and nothing

So I had to use the ignorance.. 
I have to rename ALL policies (copy to new)

 everything is ok now.. but 

I´m afraid of backing up in MAR


Thanks a lot .. really all of you...

- Andy Welburn - 
- David McMullin
- Marianne -   this is the seccond time she helps me (I mean saved me)

I hope some day I help you all .. I´m studing .. thanks again


I´ll set this like solution 
was a little rude solution but worked.


Thanks again

[Andy_Welburn]

I agree, it wasn't the most elegant of resolutions, but needs must as they say, & it certainly beats doing a full catalog restore back to before the "change" which would've been another option!

I wouldn't worry about backing up in March - you've already done those backups (just kidding!) - as these are effectively new policies they should not be affected by what has happened previously.