Arcserve & NTBackup.exe, 4mmdat.sys problem. 1

[DistressedDes]

Hi All,

I've searched but I can't put my finger on the answer to this one. I'd appreciate any help you can offer.

I am working on an NT 4.0 SP6 server. It had ArcserveIT WG 6.61 installed but the admin ran into problems with Arcserve and was unable to perform backups. I looked at Arcserve but to no avil, so I decided to remove Arcserve in order to perform an NTBackup of the Exchange 5.5 Directory and Information store. The admin has been unable to perform a backup for some months now, thats why I decided to revert back to NTBackup to try an ensure some sort of backup.

I am now getting an error in the event log referring to 4mmdat.sys device unable to load. I'm almost positive this is a consequence of the Arcserve installation. I have tried to reload the 4mmdat.sys driver, but still no luck.

The arcserve exchange agents are still intact but I have removed the main manager software.

Can someone please tell me
1. How to restore NTBackup to fully running condition.
2. How to allow NTBackup run on a computer with ArcserveIT 6.61 installed.

Thanks

 

[vschumpy]

It's possible that the previous administrator deleted all or part of the OS level driver because of its known clashes with ARCserve, so you may have to grab an updated copy from the manufacturer's website or an original NT4 CD.

At 6.61 ARCserve could do absolutely nothing to stop NT from loading tape drivers - so it's pretty much impossible for ARCserve to be stopping your NT backup from working or to stop the OS from loading system level drivers.

Only with Windows 2000, and ARCserve 2000 was the concept of device ownership introduced with the windows RSM feature.

As you've removed the main server software for ARCserve it's not as if even the tape engine could be locking the device even if ARCserve was still active.

 

[DistressedDes]

Thanks vschumpy.

The DAT drive in question is a HP surestore DAT24e which having tested on another server is supported by the supplied 4mmdat.sys driver. When trying to reload the driver I first downloaded SP6 and used the extract option. Then I pointed the driver install to that folder and performed the requested reboot, but no joy. I then used the Server 4.0. istall CD, same same, no joy. The BIOS shows that the DAT and SCSI are loading correctly.

Funny enough, on the other server mentioned, I was unable to perform a backup using NTbackup until I removed the Arcserve software. It did then however allow me to use NTBackup after the uninstall of arcserve.

thanks

 

[vschumpy]

Ok, just a check, after removing arcserve and the driver (before trying to re-install it) you rebooted the server right?

NT4 always required a reboot when adding/removing drivers for them to take effect.

Other than that it sounds as if you could have a dodgy SCSI card or cable, unless of the course the HAL/Driver model on the server in question has got completely screwed up.

 

[vschumpy]

Other than that, I would suggest posting your question in the NT Backup forum.

 

[DistressedDes]

thanks vschumpy,

I did reboot after the arcserve uninstall, however i didn't reboot between the uninstall and reinstall of the 4mmdata.sys driver. I'll try this later after working hours,

My big problem is that this server is live and the sole exchange server for a particular business. I can't afford to take any risks which may end up with a BSOD. The classic catch 22, no backup, higher risk.

thanks

 

[vschumpy]

You could backup this server remotely from a ARCserve host server which does work as long as you have the Exchange agent installed on the Exchange server itself.

 

[DistressedDes]

I have considered this (thats why I left the agents intact), but the Arcserve configuration was in such a mess that I opted for the NTbackup option. Each of the two servers mentioned had their own full copy of arcserve installed, but were in seperate domains. Would I be right in saying that cross domain backup should not be a problem?

I suspect that due to carelessness that the License information I require to do a clean install of arcserve will be hard to come by. Not for any copyright infringment reason, but purely through carelessness of previous admins (especially the individual who installed the software, whoever that was). That was the reason for my reluctance to remove the exchange agent.

thanks

 

[vschumpy]

Cross domain backup should not be an issue providing you have the appropriate trusts setup between the two domains.

Licence information for the version of arcserve you are running is held in the C:\CA_LIC directory in the ca.olf file on the machine the software is installed on. You should be ok having uninstalled the software as it shouldn't remove licence information just by uninstalling it (with this version anyway).

You'll soon know if there is a problem as you will have popup licencing dialogs and a stream of messages under CA_LIC in the application event log.

versions 6.5, 6.0 and 2.0 were all keycode required before install, 6.6, 6.61, 7.0/2000 were licenced using either RegisterIT or LicenceIT (depending on how the licences were originally purchased).

 

[DistressedDes]

I tried your suggestion regarding the reboot between 4mmday.sys removal and reinstall, and a substancial amount of sweating was done during reboots, but back to square 1 regarding the event log failure.

'The following boot-start or system-start driver(s) failed to load: 4mmdat

Well it's another thing to chalk off my list.

Taking the ca.olf file from the server, is it possible for me to do a fresh install on another computer using the info therein. I don't think I have another NT box at my disposal for Arcserve install, but I think I have Arcserve for NT and an upgrade CD for 2000. Any suggestions on how to get a 2000 box up and running with Arcserve manager, given this rather screwed up setup. (There are few things more frustrating than inheriting a system, from someone who obviously didn't have a clue, or just didn't care!)


Once again, thanks.

 

[vschumpy]

Hmm this is for sure an NT problem, but without delving deeper we aren't going to get anywhere.

You could try downloading the latest 11.5 trial which will get you up and running for 30 days (and won't prevent restores of backups thereafter).

You won't be able to install the host server on NT4, but you will be able to install the exchange agent on NT4, and you'll need to upgrade it to be able to back it up solidly although it 'may' appear to work fine without upgrading it, I wouldn't trust it for a restore. Here's the link to register for the trial:

https://www3.ca.com/Register/myCALogin.asp?url=/Register/form.aspx?cid=38489

 

[DistressedDes]

vschumpy, thanks again for your assistance. I think I'll act on another of your suggestions and post the 4mmdat.sys snag on the Nt backup forum.

By the by, during my time looking for answers, I have found quiet a bit of doubt in peoples confidence in arcserve as a reliable backup for exchange. I know it's the market standard and surely has earned such a position, but I don't want to repeat the error of purchasing a more up to date version of arcserve if I'm likely to be back in this, or a similar situation again. Any views / opinions?

 

[vschumpy]

Depends what you want out of an Exchange backup - if it's just straight IS and DS then pretty much any product can do it, if it's mailbox or brick level, then v7 and previous have some pretty serious limitations, and I could certainly understand people being sceptical about ARCserve with these versions (there are more than a few horror stories posted around the net about these versions). Later versions are much improved, but still as any software can be tempramental.

The premium/document level backup in the latest versions is for sure the best of the bunch, but it will cost you a shed load more cash, but can be extremely useful, especially if you're planning a migration in future as it can be used to copy mailboxes to other servers (including other exchange versions).

A lot of people get hung up on the whole brick/mailbox level backup thing, and to be honest that's where 80% of backup problems arise, but a few people here have just given up on brick level backup altogether and used a third party tool to extract mailbox information from the IS/DS backup instead (I forget what the name of the product is but I think DebiJo and a few others on this forum use it). It does have the advantage that you don't waste hours backing up brick level in addition to IS/DS as well.

Versions 9 and above don't support NT4 as a host server platform, but continue to offer NT4 support for agents - eg exchange, file system agents and so on. It would mean having to have your host server and tape drive on a non-NT4 server.

Hope I have not waffled on too long and the information was of some use - good luck in sorting out your driver issues on the server.

 

[DistressedDes]

Vschumpy, your contribution is much appreciated. I don't have much experience in this area (Exchange), in fact the last mail packages I had serious involvement in were ccMail and IMail. (Microsoft aren't generally on my xmas card list!, But rest assured, you are now, Thanks)

I'll endeavour to find the answer to my NTBackup 'show-stopper' for the present but if the clients are in the market for an improved backup system, I'll bare your comments in mind.

Cheers

 

[vschumpy]

In case you need it here is the link to the drivers for NT4 for the 24e on HPs site:

http://h20000.www2.hp.com/bizsuppor...=24&swLang=8&mode=2&taskId=135&swItem=co515en

 

[DistressedDes]

vschumpy,

once again, thanks. That was exactly was I was looking for. Will give it a go after working hours.

Cheers

 

[DistressedDes]

vschumpy,

reloaded underlying SCSI adapter driver and loaded your HP specific driver and hey presto. I've successfully completed a DS/IS backup. I'm as happy as a dog with two *****!

thanks for you continued support. I also offer sincere apologies for casting aspersions on arcserve when in fact, the problem lay at a lower level.

cheers

 

[vschumpy]

No problem, glad to hear you got it sorted.