Search results for query: *

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

Networker 7.3.2 build 364 on a P4 Windows Server 2003 SP1 system, all Windows patches applied (except .Net Framework v3.0). Java Runtime Environments loaded are: 1.4.2_13 (not enabled) 1.5.0_11 (enabled) 1.6.0_01 (not enabled) Two SCSI tape drives installed: Seagate/Archive Python 02779 DDS2...

Wow, thanks! I need to look in to MSDN now to turn this in to reality; I really appreciate the detailed script example and the pointer! -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...

Ugh. Thanks for confirming that it isn't just my system. -Jay

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...

Unfortunately, Exchange module 3.0 does not support Exchange 2003. A client configured: MSEXCH: MSEXCH:MB .. produces this output (=====emphasis===== mine): * cheshire7.ad.felines.org:MSEXCH: savegrp: suppressed 7 lines of output * cheshire7.ad.felines.org:MSEXCH: ===================== *...

Here's what fixed this: Migrate all FSMO roles to the new 2003-based DC, including GC. Demote 2000-based DC to member server. Rename 2000-now-just-a-member-server to fully comply with the DNS name of the domain (For historical reasons, it was reset4.felines.org instead of...

NW 6.2, Exchange Module 4.0, Exchange Server 2003. From reading the manuals for the Exchange Module, it looks like there is no such thing as an incremental backup of the items within a single mailbox. This results in my 600MB mailbox being backed up EVERY night. That adds up to a lot of...

As the problem has occurred on two possible client systems - on a Windows XP workstation which had a previous Outlook profile on it, and the other the Windows 2003 Server Enterprise Edition itself where Exchange 2003 is running and has never had any Outlook profiles on it, I'm sure it's not the...

I did a quick MSDN search. The "WebClient" service in Windows XP appears to be the client component for WebDAV (which I just learned from these articles means "WWW Distributed Authoring and Versioning"). As I don't know what the client end of WebDAV is for - the only place...