Hello. I am using netbackup 5.1 in a server environment of approx. 250 servers. I have about 12 policies that back the servers up in groups to LTO3 in an IBM robot with 13 drives. Two of the drives in the robot are configured to use LTO1 since this was the media used until about 18mos. ago. What I am seeing is that when the policies run one of the servers is taking a very long time too run and writing at about 100-200KB/ sec. When I look at the details it shows that there is an error opening or writing a DB file. It also looks like the job just hangs for hours, example a time stamp showing write at 8:00pm then the next timestamp is 2:00AM. This jobs goes beyond the backup window then the jobs in the queue fail. Do I need to get a script created to shut the DB down so the job can complete? I see this on an SMS server and an Exchange server.
I would also like to know if there is any correlation between this and the job for the catalog failing? The catalog is set up to run on a seperate single tape drive. How do I find out if the tape drive and Netbackup are configured to use any drive available to run the jobs or if they are set to run other jobs?
Thanks in advance for the help!
Start Free Trial
