11-10-2008 03:55 PM
Hello,
I'm new to Netbackup, and have just installed it in my enviornment. This last weekend was my first attempt at a full backup of my server enviornment and overall it was a success except for one issue.
I've got a Storage LifeCycle policy configured to backup to disk first, then duplicate to tape.
All my other backups successfuly duplicated to tape except for a large 800GB image. The duplication job goes for a few hours, and then another job of type "Image Cleanup" runs, which fails the Duplication job with a status of: 1: (50) client process aborted. The rince and repeat, the duplication job runs again for another few hours in an attempt to write to tape, and gets kicked again by the image cleanup job.
#1, why would the image cleanup job interupt a duplication job, is this normal?
#2, what sets the schedule for "Image Cleanup"?
Thanks for your help!
11-10-2008 09:30 PM
Error 50: Indicates the unexpected service stop, please check for unexpected service stop in evnent log.
Image Cleanup: it's a jobs used to clean the older catalog images, This job will run after a completion of backup.
I think Image Cleanup wont affect the Duplication, Kindly check for Event Logs and Veritas Logs and Let us know !!!
11-10-2008 11:43 PM
Image cleanup period is set within Host Properties/Master Servers/master server/Clean-up tab.
From the context sensitive help page:
"...
The Image cleanup property specifies the maximum interval that can elapse before an image cleanup is run. Image cleanup is run after every successful backup session (that is, a session in which at least one backup runs successfully). If a backup session exceeds this maximum interval, an image cleanup is initiated
..."
11-11-2008 06:16 AM
I looked through the windows logs on both master and media server and did not find that any service had stopped. The one thing I noticed is that the dup job runs for about 2 hours 20 min each time before it something kills it. If I look through the Netbackup Reports, both Problems and All Log Entries, there is nothing that stands out other then the error, Duplicated exited with a status of 50 (client process aborted). This morning I did not see an image cleanup job run that interupted the job, it just stopped by itself. it seems to be in a never ending cylce.
11-11-2008 08:08 AM
BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported
The above actually mentions aborts after 20 minutes, so maybe not relevant?
11-11-2008 08:46 AM
11-11-2008 05:23 PM
I opened the case and was told to install a patch associated with the following bug report
http://seer.entsupport.symantec.com/docs/313850.htm
so far more than 2.5 hours running with no errors.... keeping my fingers crossed.
11-13-2008 08:23 AM
11-25-2008 04:35 PM
May i ask what type of disk storage unit your first copy goes to? I want to do something similar but basic disk stu doesn't work with lifecycle policies.