Argh, quick update. It turns out that I CAN write SOME older DDS-4 cartridges. One which I was able to read with Networker's "scanner" command I was also able to relabel and write to with a new Networker backup - about 3.0GB at an average write speed of 2.0MB/sec.
However, other DDS-4...
I have a variety of DDS-2, DDS-4, and one DDS-5 tape drives, with a shelf full of tape cartridges, exhibiting the following symptom since a few months ago (I haven't had time to deal with it lately, and, yes, I haven't run a backup in months...):
The DDS-2 drives still work fine. They work fine...
I applied Windows Server 2003 Service Pack 2 (which includes the updated tape.sys intended to address the performance problem referenced by Rif123 - thanks), and it did not correct the problem. Sigh.
Any other ideas folks? I really do appreciate your help, even though this (probably) isn't a...
NTBACKUP has the same problem, as noted above.
RSM is set to Manual, and does not auto-start even when new hardware is detected.
I realize this is not specifically, or at least not obviously, a Networker problem. I appreciate any attempts to help.
Any other ideas?
Thanks!
-Jay
Thank you very much for the suggestion, speculos. Please pardon my ignorance as to how to implement your suggestion. My programming dates back to UNIX in the 1980s and early 1990s, not Windows in the 2000s! :-/
How do I script to call the SetPriority method for nsrexecd.exe ? Is it something...
How can I configure a Windows XP client so that when nsrexecd runs and when it kicks off any save (or other) child processes, the process priority of nsrexecd, save &etc are all "LOW" (per Windows XP process priority possibilities)?
I want to make sure that more time critical jobs (such as TV...
I had a hard drive fail, and wanted to restore the whole system from NSR backups. I installed the new hard drive, installed Windows XP again, loaded the Networker client, ran Recover, and right-clicked on C:
It took more than an hour for nothing to come back in the Recover window. It seems...
Yeah, I thought about that and tried it. It took more than an hour for nothing to come back after I selected the C:\ drive. It seems that I have some kind of massive inefficiency problem on the Networker server (nsrindexd ran at ~90% CPU for that entire time).
To get a clearer picture of what...
I have a WinXP system. The hard drive failed. I replaced it with a newer larger hard drive. I have complete Networker backups (v6.2) of the system, including C:\ (the only drive letter in the system), SYSTEM STATE:, SYSTEM DB:, and SYSTEM FILES:.
What is the right order of steps to take to...
I believe that Exchange Module v4.0 is compatible with Networker 6.2. I'll try an upgrade of the Network server to 7.1, though as this has worked before without the error, I'm not sure that's it at all.
To help with the diagnoses, how do I prevent Networker from "suppressing" lines of output...
DavinaTreiber posted that Networker 6.2 does not support Windows Server 2003.
The error message:
* exchangeserver.mydomain.org:MSEXCH:MB svmain(908): begin_mb_item_backup() failed with status = 0x80040108
* exchangeserver.mydomain.org:MSEXCH:MB profile(134): MAPI Profile: Name does not exist...
I have Legato Networker v6.2 installed on a Windows Server 2003 system also running Exchange Server 2003. Exchange module v4.0 is installed to back up Exchange. I'm seeing this:
NetWorker Savegroup: (alert) Exchange completed, 1 client(s) (exchangeserver.mydomain.org Failed)
Start time...
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.