Recent content by Almow

Backup server and client are W2K - SP2. Servers are on an isolated backup network with Gig NIC in backup server and 100 full NIC in the client. All other applications on the client are not experiencing any issues. Almo

I have a W2K backup server and client. Backup server has a Gig NIC and the client is 100mgbt. Ran Blaster and after 1.8 Gig it failed. In the client log file I have: START cceexc10 Tue Oct 15 09:14:56 2002 send -- bad syscall (22) Invalid argument Sent 0 pings Does anyone know what this...

Having an issue where client backups are hanging on W2K clients. save even hangs from the command line. After the client is rebooted backups are successful for a variable amount of time before a hang occurs again. Running v6.0.2. Any ideas? Almo [bull]

Has anyone every used Legato's "Blaster" network testing program? I'm not sure I want to try it in a production environment because it, of course, is not a supported product. Any hazards? Also, is it worth the effort? Almo [bull]

oodeano, Do you have a Legato case number. I would like to cross reference with Legato, if that's okay with you. Almo

We see the problem with v6.1.1 too and have also had a case open with Legato for months. Funny that they told us that no other customers have reported the problem. Some things never change! :-S We have noticed that the cleaning required light does light up on the tape drive when the problem...

Also, make sure that the Model of the library is "Digital TL810 Series" and not "Standard SCSI Jukebox". I have noticed that the autodetect will sometimes assign the model to standard. If so, you will need to recreate the library or hack the nsrjb.res with wordpad to change...

You are correct that No. 4 in my previous thread is high maintenance for the servers file. For that reason, we use No. 1 with terminal server or a remote console software like PC-DUO. If you use a standard servers file as mentioned you will never need to update the servers file and stop and...

In my mind there are four types of directed recovery senarios with the GUI. 1) Logged onto the target system and restore the backup from another source system. 2) Logged onto the backup server and push a restore by selecting the source and destination client as the target. 3) Logged onto the...

You can also run "nsrck -m". This will rebuild the b-tree index entries in the media database. I have found that this usually fixes this fetch error, but I also agree with previous replies.

We have turned off the auto clean function as well, but still get the cleaning required error...read open error: The device has indicated that cleaning is required before further operations are attempted. And yes, we see the problem during loading/reading/labeling of tapes. And as you stated...

I have never seen this problem, but it sounds like you are having index issues/corruption. I would suggest. 1) Leave the "NetWorker Backup and Recover Server" service down and stop the "NetWorker Remote Exec" service. 2) Check for any active "nsr" processes and...

Do not use the "-d" option. This is for deleting volumes from the media database for a given location. Good Luck!

Actually the location field is maintained in the media database and can be updated with the "mmlocate" command from the command line or with the GUI. From the command line you can clear the location field by using the "-c" option and volume label. Must be a limitation to...

We are having a problem where periodically tape drives will get a "cleaning require" status in the NetWorker GUI. When this happens the tape is somehow moved back to its slot in the library and NetWorker goes into a vicious cycle of trying to verify the label and eject the tape that...