We are conducting a DR test and have restore jobs getting an hour glass for up to 10 minutes before queuing. Then they queue for 5 minutes or so before running. This is for Windows 2003 SP2, Netbackup 6.0 MP5 using an ADIC I2000 Scalar Library with...
This question is for Netbackup 6.0 MP6 running on Windows. I am retiring one of my master server environments. Can I take the tapes from that enivironment that are now scratch, relabel them with different barcode labels, and use them in another Ne...
I have 2 Netbackup 6.0 Windows environments. I want to verify that the backups I have scheduled actually run. I know I can run nbpemreq -predict -date 12/04/2007 to determine jobs to run today for example. I was thinking I could run a bpdbjobs com...
Are there any special Netbackup procedures for when the time changes? I've never had any problems before when the time changed, but last night I had probably 50 jobs fail with error 58 among other things. I restarted the jobs and they seem to be ok...
I setup a NOM 6.0 MP5 server, Windows 2003 SP2. I am only seeing some of the information in the NOM web console. The only thing I see are my drives and media. I see no jobs, alerts, services etc. My master server is shown as partially online. I f...
You mentioned you expanded your library...Did you add more tape drives also?
If you added tape drives you have potentially less queueing so more tapes are used at the same time and you get less data per tape. I actually downed some drives in one o...
Thanks for the feedback. Support said it was a known issue in DR and we sent some logs, but no resolution was found. We managed through it and got all of the restores done. I had already verified DNS etc. I put hosts files on all systems trying b...
Thanks for the feedback. I ran through the process. I used the GUI to do this. I right-clicked the media and selected Label. I unchecked "Verify media label before performing operation" and selected ok. The tape was loaded and the label process ...
Thanks for the information, but will that tell me if a job did not run. If a job doesn't run due to some type of scheduler issue then there are no errors to look at. I had this problem in 4.5 and 5.1 (maybe) where I saw no errors in activity monito...
I would approach this a couple of different ways. First, since 5.1 is being end of lifed this month I believe. Then perhaps you can get them to allow you to install a new 6.0 environment with new catalog etc. This is what I did. I use my old 5.1...