Hi
I had this problem before. If your server is a Compaq, and your NIC is a 6xxx, you'd probably need to check the drivers for that NIC. Go to the latest drivers and that's it.
This is posted in Legato's Web page.
Hi:
My experience is different, I am moving my customers to SDLT. It is very fast mounting, and so far we have sold 6 libraries with SDLT. No problems at all.
Regards
Hi MarcusS:
You can not do a directed recover of a Registry.
This is not a NetWorker problem. It is an NT problem. Registry is hardware dependant, meaning, it stores hardware configuration. If you are replacing just disks, no problem you can restore your registry. If you are retoring to a...
There are only two reasons why NetWorker Services would not start.
1. Databases corruption
2. Name resolution.
Any recent changes in your network?. IP changes?. Not necesarilly on the server, it could be on a storage node.
To check for corruption, just rename them one by one, first mm...
Hi All:
I am getting the most weird error. My backup server (NT), was working just fine. Suddenly, every time I run a backup on the server I get a Dr. Watson. All the backups from the clients run OK.
The Dr. Watson message is exception ocurred, access violation.
My server es NetWorker 6.1.1...
I am experiencing the same thing, after an Upgrade from 6.0.1 to 6.0.2
I checked the nsrjb.res file (it is corrupted). Just run jbconfig (previously delete jukebox AND DEVICES) and re config the whole thing, inventory it and that should be it.
What I would really recommend, is to Upgrade your NetWorker to 5.5-003, If you are unable to go directly to 6.0.1.
This use to happend with releases pre 5.5.
I know STK machines and NetWorker. It is a very good combination. It should work nicely.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.