• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 523
  • Last Modified:

Veritas 9 backup fails on Exchange 2003 server:

I have Exchange 2003 running on server 2000.  The exchange program files are on the System drive c: and the information store/ mailboxes are on the E: (data) drive---80gig IDE.  There are about 60 mailboxes and the store is about 3.5 gig.  Every night veritas 9.0 runs a backup of the Store, public folders, mailboxes and system state.
The other night, just after the backup, the data drive went flacky and corrupted the store.  I thought the drive died as I could not see it in windows explorer.  I pulled the drive to get the model/size and reinstalled it.  Low and behold, the drive was seen, Exchange started, but the folders and store wouldn't mount as they were corrupted.
I used Paragon's Drive Backup 9.0 Server to backup the drive to an external USB drive.  I then replaced the IDE drive with a 250 gig drive (smallest new I could find locally).  The computer, being older, only recognized 120 gig which was fine.  I restored the DB9.0 image to the new drive which went fine.  I then attempted the Veritas Restore and received errors saying it could not attached to the device.  After much time I tried restoring to the original drive which worked.  I then cloned the old drive to the new drive, changed the drive letter to match the original drive and installed it.  Up it came the store and folders and all seems(ed) fine until I resumed the regular backup.  
The job completion Status says, Completed status: failed, Final Error Code: a0008488, Final error description: Access is denied., Final error category: Security Errors
The exceptions list states: Backup-  Warning:\ \ server\MS Information Store\First Storage group\Mailbox Store() is a corrupt file.  This file cannot verify. This is true as well for the public folder store and log file. The same warnings are listed under Exceptions Verify.
Any Ideas on what might be going on?  E-mail seems to be working fine other than this.
Thanks for any help ---SM
0
smantz
Asked:
smantz
  • 6
  • 4
1 Solution
 
honmapogCommented:
Try using NTBackup to make a backup of the Information Store - does that succeed?
When Backup Exec prints this error, how much data does it indicate it has backed up for the Information Store resource? Does the amount of bytes correspond to the Information Store database sizes (edb and stm files).
Any events in the application event log at the time of this failure?
You may want to run isinteg on the database - make sure to have a vaild database backup before though.

0
 
smantzAuthor Commented:
Hello there,
As far as using NT Backup, I thought I read where Server 2000's version doesn't support Exchange server backups, at least natively.  The only error in the application log  is:
Source: Backup Exec
Event I.D. 34113
Backup Exec Alert: Job Failed
(Server: "SMHSCS-MAIL1") (Job: "Friday Info Store") Friday Info Store -- The job failed with the following error: Access is denied.
I attached an XML log file.  The extension was changed to allow an upload.
I have studied many articles on accounts needed to make this work.  I'm not sure why the System Logon Account  created for the backups worked and now doesn't?
Any ideas are appreciated.
SM


BEX02762.txt
0
 
honmapogCommented:
NTBackup on Windows 2000 should be able to back up Exchange 2003. See http://groups.google.co.uk/group/microsoft.public.exchange.admin/browse_thread/thread/4e277b94dbeec153 and the last paragraph in http://support.microsoft.com/kb/298901 suggests the same.

Have another look in Exchange System Manager. If you run the "Delegate Control" wizard from the Organisation level, is the account you use a Exchange Full Administrator. Also check permissions on the Storage Group and Mailbox Store levels.

Just a wild guess: you wouldn't have installed SP2 for Exchange as part of the recovery steps I hope. It's not officially supported by Backup Exec 9.1 (http://seer.entsupport.symantec.com/docs/261695.htm)

If you create a different backup job, can you still expand and select the Exchange databases in the selection list of the new backup job?
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
smantzAuthor Commented:
Well,
A little out of order:  SP2 was on the original drive and since I cloned it, it's on the new one.
I can create  a new job and add whatever I want to the backup, maiboxes, store, public folders, system state.  I will say however, I can not change Resource Credentials on the Storage Group or System State.
The Delegation is Exchange Full Administrator.  The name is domain\admin.  Security Permission on the Mailbox Store by default, has inherited allow on all boxes except, "Receive As and Send As".  These inherit "Deny".
It was my understanding, even changing these to allow, will not overide the inherited deny.
The job seems to cancel immediately after starting.
I'll check your links and see if I find something new.
--SM
0
 
smantzAuthor Commented:
I forgot to say, those permissions are on the admin user.
0
 
honmapogCommented:
What do you mean by "I can not change Resource Credentials on the Storage Group or System State"? What happens exactly? What error message do you get?

Is the current logon account you're using for the job the same domain\admin account that was delegated Full Exchange Administrator rights?
0
 
smantzAuthor Commented:
They are greyed out and you cannot "check" them.  It's yes to the second question.  I feel something happened when I cloned the drive and somehow it's affecting credentialing even though everything else seems to work.  Maybe I should un-install veritas and re-install it and see what happens.
What do you think?  Also, I am using an external usb hard drive for the backup.  Maybe I should clear it out or try a new one.  I assume the credentialing issue resides with Veritas and the exchange interaction.  Is there a way in exchange to check out the actual linking of the drive (store) to the program?
0
 
honmapogCommented:
Check if any errors show up in the security event log when you get the backup error.
Maybe you could reinstall Backup Exec, but if you're facing permission issues with the accounts, it may not help much.
0
 
smantzAuthor Commented:
Well, the security log has one item total  and it is from November of 2006.  I can tell you that the mailboxes and public folders backup and verify.  It is the store (Mailbox and Public Store and Log files) and system state that are failing which, are the two items I can't get to on the "Backup Job Setup-Resource Credentials-Change" (grayed out).  I would have thought everything would have failed.
Also, I do notice that the "Receive AS" and "Send AS" in the security Tab of the Mailbox and Public Stores is an inherited "Deny" permission.  I think I have followed most of the articles for creating a new backup group and giving them Delegation Rights and Store permissions.  I might retry that.
One last item, the Backup "Test Run" succeeds with no errors.  I thought this checked all permissions?
0
 
smantzAuthor Commented:
Thanks for all the help and sorry it didn't pan out.  I reinstalled BE and some of the new errors indicate corrupt stores.  Sorry it took so long to get back.
--SM
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now