Failed Backups on NT server using Microsoft Exchange

[denzilla]

I work for a non-profit agency who is a little cash deprived at this point. I know a few things about computers so I was asked to take over the computer maintanence and to call in the calvary only if needed. I'm Ok troubleshooting/fixing standalone PCs, but this whole network thing is going to give me a stroke! Here is what I know about the network so far:

1. I can reset/change passwords.
2. Create/delete/disable email accounts.
3. Give file permissions for employees.
4. Jack sh!#

As you can see, I have much to learn. Everything has been fine in my new career for all of 3 weeks and now my first major problem. In the daily log I keep seeing all these "skip" and "backup failed" messages. They haven't had a good backup since 2-25 and I'm getting worried. Here is the error:

"Storage Device "DELL1" reported an error on a request to read a data from media.

Error reported:
A tape access reached file mark.
^ ^ ^ ^ ^ "

Any help in this matter is badly needed and appreciated. I am nowhere qualified for this job. The server is running NT 4.0 with Microsoft Exchange. Please be very detailed in your suggestions. Thanks in advance for your suggestions. If you need me I'll be in a dark corner P!$$!ng myself.

 

[denzilla]

I managed to track down a number to match the error. It is error "1101" The exact version of exchange is 5.5. Other than this ,still at square 1.

 

[OzDog]

Ok Denzilla, let's take a moment.

I'll try to help, but I need a little more clarification...
1. Where are you getting this error? Is it
A) in the actual log files?
B) in the Event Logs? or
C) elsewhere (if so, where?)?
2. What software are you using for backups? Cash strapped NPA, I would assume NT Backup (built in backup program?)
3. What backup hardware are you using?
4. Has the error just started, or has it been there since you started?

According to Microsoft's support pages, they recommend contacting the supplier of the app, which is not very helpful, so let's start with the above info and go from there... Cheers,
Sam

Please let members know if you found their posts helpful.

 

[denzilla]

They printout server activity logs everyday. Its on those logs that show all these areas that were skipped and other areas where it just said "backup failed". I didn't have the pleasure of being in the building when they got the actual error code 1101. Heck, I'm so unqualified, I don't even know the backup program used. I do know that the hardware is a tape drive. I'll try and find out more information this week. One big problem is that I do 3 other jobs in addition to this. Kinda makes it hard to dive deep into something. I'll post some new info soon I hope.

 

[OzDog]

OK, I'll wait to hear back.

Can you try to get models & versions of everything possible - including the tape drive? It should be DAT, DDS, DLT or SDLT (or one of those plus a number like DLTIV).

Talk to you soon Cheers,
Sam

Please let members know if you found their posts helpful.

 

[denzilla]

OzDog,

Here is what I was able to dig up today:

The backup program in use is called "Veritas Backup"

I heard today that the network is going offline today to replace the tape drive. I guess the stuff is almost out of warranty and they want to eliminate any hardware factors. The server was made by Dell. Have you heard of this backup program? If so, any opinions about it?

I'm going to wait and see if this repairs the problem before I reply again. Either way, I'll let you know something. Thanks for your help.

 

[OzDog]

Yeah, we use Veritas version 8.6, soon to upgrade to 9 here to do our 50 servers. It's a good program.

A side note - When the drive is replaced, you need to make sure that the backup jobs within Backup Exec are set to use the new drive. It may or may not be your responsibility,. It's not hard - let me know if you need help.

Keep me posted. Cheers,
Sam

Please let members know if you found their posts helpful.

 

[mrstever]

Denzilla,

I'm pretty sure the problem you're having is with "open file handles". Exchange uses a number of database files that are constantly open and so Veritas cannot access them. As a result it gives you a backup failed in the log.

There are a couple of things you can do:

1. Purchase a copy of the Backup Exec Exchange module and install it along with the program you're using, this module will be able to handle the database files. (not likely if you're cash strapped).

2. Instruct Veritas to ignore the directory where the database files are stored (perform a search on *.edb to find them). This won't give you a complete backup but Veritas will verify all of the other files for you.

3. (risky) Still instruct Veritas to miss the database folder. Periodically stop all of the Exchange services and copy the .edb files to a backup location of your choice (ie a desktop PC). restart the services.

4. (even more risky) set a scheduled event up on the server to stop the Exchange services before the backup starts and then restart them after the backup is complete.

The problem with three and four is that when the services are stopped no e-mail can arrive or be sent and there is a chance of some mail stacked in the system of being lost. I wouldn't recommend either course but they are possibilities if you're desperate.

The bottom line is that to perform a proper backup you'll need the Veritas add-on module - that is assuming I'm right.

Hope this helps.

S

 

[zoeythecat]

Does seem like it could be a hardware issue (see following article)

http://seer.support.veritas.com/docs/231113.htm

Could be dirty tape drive too. You need to make sure you have a good backup scheme where you rotate about 5 tapes a month (for 4 - 5 weeks of backups per month).

Make sure you have the Exchange Agent (verify this by opening up your Backup Exec program, clicking on Help, and then "about backup exec". You should see all the agents you have listed here.). If you don't see Exchange Server agent then you will need to purchase this because your Exchange database will not get backed up and if you lose your Exchange IS you will not be able to restore. You should be able to convince your higher ups how important a purchase this would be.

Good luck.

 

[denzilla]

Hello everyone.

Well, we figured it out. There were 2 different problems. It was a combination of a faulty tape drive, and bad tapes. As far as I can tell, the problem is now solved. Thanks to everyone who tried to help me.