Networks

Ask something
Discussion Locked

BACKUP W/BKUPEXEC 8.0 - 8.5

0 helpful
5 replies

by interpretivewoodwork

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is the situation:
I have a Compaq DeskPro/Celeron 300/256-MB ram,3Com 980 Nic, PCI video card, Seagate SCSI drive / Adaptec 3940 controller / Ecrix VHA1 tape drive, the tape drive and HD on separate channels. Have installed the latest driver for the controller, updated the bios. I am using NW 5.0 patched with the latest build sp5. Am trying to use BackUp Exec 8.5 because that is the only version compatible with the tape drive. Every time I install bkupexec and run for the first time, it abends the server 2-3 times and wont mount sys:\.Theres a patch for the backup software, but cant apply it for the same reason(no sys:\).Tried patching it before running for the first time, tried re-applying sp5 over the patched backup....cant think of any other options as of now. Could this be a
Compaq issue? I've been told not to apply any NSSD over NW by Seagate techs.Has anyone had similar problems and found a solution?

5 replies

by rogerndgreen

Hi
Currently using 7.5 and we're not going over to 8 yet, because of some of the problems like this (we found a few on our test rigs), and I don't know the tape drive. Can you use a different drive that is more widely supported?
First suggestion, can you start the server with the bare minimum of NLMs loaded, just to load BuE, and then patch it? You didn't mention what NLMs were abending.
Secondly, I have been told that there was an issue with BuE 8.x and the latest service packs for both NW 4.11 & 5.1, which are resolved by back-revving the Netware SP.
I must admit I haven't tried this on a 5.1 server yuet, but it is certainly true with a 4.11 server. The multiple abends were so bad I had to trash the dos partition on on of the duplexed drives before the server would boot (don't help you much).
Finally, a bleeding-obvious question, but, after you have restarted the server, have you vrepaired the sys volume until no more errors have occurred?

HTH

Roger

by papachuck

When you install the BE8.5 before rebooting rename the file c:\nwserver\filesys.nlm to filesys.old or some other name. then restart the server. The filesys.nlm BE puts in the C: drive is a older one that crashes the system. Also the install looksfor it and installs it automatically even if there. After changing the name I ran BE 8.5 with no problems....Hope this helps....Chuck

This discussion is closed to new replies.