This can be because of a corrupt image. We also faced same issue where the image cleanup was getting stuck at a particular client. We moved the client's images to a temp location and restarted the netbackup services. Image cleanup auto restarted and completed successfully.
On Wed, Jun 8, 2011 at 7:36 AM, BeDour, Wayne <wbed...@lear.com> wrote: > All: > > Our environment, HP-UX 11-31 currently running one master / media server on > NetBackup 6.5.2. We are running mostly unix / Linux backups and a couple > windows b/u’s thrown in for good measure. > > Currently, our image cleanup job hangs at the same place and will not > complete without canceling it. The Detail Status shows it processing the > same client when it hangs. > > Here is what got us to this point. Last Thursday one of our admins kicked > off a restore and didn’t notice that the window was for a few years. He > went home with the search still running. Sometime overnight the /usr/openv > filesystem filled up. The admin that kicked off the job didn’t work > Friday so the rest of us didn’t know what was going on. (We have since > flogged him and he is currently tied up..) NetBackup was taken down and > brought back up. When NetBackup came up, we couldn’t submit jobs because > the nbperm daemon wouldn’t stay up. We found a document that said “nbjm > and nbpem processes are not synchronized when this occurs, stale data is > left both in the pempersist file and the cached schedule information. As > a result, nbpem never runs the job again, since its data indicates that the > job is still active”. We followed the instructions and cleaned up the > /usr/openv/netbackup/db/jobs/pempersist file and also had to clear lock > files and the activity log database and deleted the following files: ***** > ** 063008.bpjobd.db* ,******* bpjobd.act.db******** ,******** bpjobd.db*** > ***** ,******** jobid******** ,******** jobid.lock******** ******** > pempersist2********. * The bad news was that it cleared out the activity > log for the 2 weeks which we can live with. > > So, that’s where we are, anyone know how to take care of the image cleanup > hang? > > Thanks in advance.. > > Wayne BeDour > > Unix System Administrator > > PH: 248-447-1739 > > Internet: *****wbed...@lear.com* <wbed...@lear.com> > > ********************** > ** LEGAL DISCLAIMER ** > ********************** > > This E-mail message and any attachments may contain > legally privileged, confidential or proprietary > information. If you are not the intended recipient(s), > or the employee or agent responsible for delivery of > this message to the intended recipient(s), you are > hereby notified that any dissemination, distribution > or copying of this E-mail message is strictly > prohibited. If you have received this message in > error, please immediately notify the sender and > delete this E-mail message from your computer. > > > _______________________________________________ > 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
