Seems this did the trick but was a last resort. Hopefully people will remember the old policy name should they wish to restore :)
Very odd why it happened all of a sudden though. cheers to all Troy Schuler wrote: > Recreate the policy with a new name. NBU has problems periodically from > release to release with this. The only workaround was to delete the policy > and recreate it with a completely different name. Do not copy the policy to a > new policy. Start from scratch. > > Troy Schuler > (314) 807-6169 > [EMAIL PROTECTED] > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Markham > Sent: Friday, July 18, 2008 8:21 AM > To: veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Strange schedule problem > > And something else odd now i cannot run a manual backup of the policy. > Very strange!! > > Anyone know why that would be? > > D > > Dave Markham wrote: > >> No joy im afraid :( >> >> I tried as below and also tried stopping all daemons, moving >> /usr/openv/netbackup/db/jobs/pempersist to a .old file and restarting >> services on the master. Still no joy. >> >> I copied the policy to a new one, deleted the old one and then copied >> the copy back to the policy of the same original name and no joy. >> I have created a new schedule within the policy and that has not ran. >> >> Also now when running nbpemreq -predict -date 07/19/2008 00:00:00 it >> doesn't show the policy in the list but shows all the others. >> >> Any more suggestions? I cant seem to find a log for nbpem either and >> the man page for vxlogcfg doesn't lead me in any direction. >> >> Cheers >> >> Abhishek Dhingra1 wrote: >> >> >>> The problem is with the nbpem . >>> >>> run the command nbpemreq -resume_scheduling, and wait for some time. >>> >>> or if that didnot worked for you , kill the nbpem process, clear the >>> *pem.ior files under /usr/openv/var and restart the nbpem daemon by >>> running nbpem command. >>> >>> if above doesnot work , increease the logging level of nbpem(117) >>> using the command vxlogcfg command >>> >>> >>> Abhishek Dhingra >>> >>> IBM Global Services, Delhi, >>> Email : [EMAIL PROTECTED] >>> Mobile : +91-9818675370 >>> >>> >>> *Dave Markham <[EMAIL PROTECTED]>* >>> Sent by: [EMAIL PROTECTED] >>> >>> 17/07/08 06:34 PM >>> Please respond to >>> [EMAIL PROTECTED] >>> >>> >>> >>> To >>> "veritas-bu@mailman.eng.auburn.edu" <veritas-bu@mailman.eng.auburn.edu> >>> cc >>> >>> Subject >>> [Veritas-bu] Strange schedule problem >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Guys i have Master server (NBU 6.0MP4) and a number of media servers and >>> clients. >>> >>> One media server which is SSO Media server sharing drives is NBU 5.0MP7 >>> and has been fine but all of a sudden as stopped automatically running >>> backups. We can run manual ones fine but its as though the scheduling >>> system isnt working for it or something. Anyone any pointers as to >>> where to look? >>> >>> There isn't a bpsched log directory on the master server with NBU6 so >>> i'm a bit stuck. >>> >>> Everything else is working ok. >>> >>> Cheers >>> >>> This is all on Solaris, and please no need for replies with "Why not >>> upgrade to 6 on the media server" i know i know and i'm trying to get it >>> passed by service management. >>> >>> >>> _______________________________________________ >>> Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu >>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >>> >>> >>> >> _______________________________________________ >> Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> >> >> > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu