Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 596
  • Last Modified:

Exchange 2007 CCR Cluster backup issues

We’re having an issue with not getting full backups on one of our Exchange 2007 mail stores.   We’re running Exchange 2007 with a CCR Cluster on a Server 2003 box.  Our backup software is Backup Exec 7.0.  We are getting backups of the log files but not the database.  Without a full backup it will not clear our transition logs.  Our copy status on all of the mail stores Healthy and the database is replicating from the active to the passive node.  We have had this problem since we rolled our cluster to this node.  This past weekend I did a manual reseeding of the database in an attempt to fix the problem.  It did not help.
0
BellevueAdmin
Asked:
BellevueAdmin
  • 4
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
What happens if you use the native Windows backup for the Backup of Exchange? Does that work?

Are you sure about that version of Backup Exec? 7.0 is very old and doesn't support Exchange 2007, you need 12 (IIRC) at least for support of Exchange 2007.

Simon.
0
 
BellevueAdminAuthor Commented:
I just finished running the MS Server Backup.  Got the following Error

The 'Microsoft Information Store' returned 'Error returned from an ESE function call (d).

' from a call to 'HrESEBackupRead()' additional data '-'The 'Microsoft Information Store' returned 'Error returned from an ESE function call (d).

' from a call to 'HrESEBackupRead()' additional data '-'
The operation was ended
.
0
 
BellevueAdminAuthor Commented:
I'm sorry - We are running Symantec NetBackup.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Simon Butler (Sembee)ConsultantCommented:
Looks like the database has a problem.
Have you tried failing over and backing up the database with the other server? It could be that the problem is with the physical file.

If that also fails, are you using your full capacity of databases in Exchange 2007?

If not, I would suggest that you create a new one, move all the mailboxes to the new one and drop the original.

The error you have posted is a clear sign of database corruption and in a single database platform the suggestion would be to repair the database. A database repair is not risk free though and can result in data loss. A move mailbox to a new database is risk free.

Simon.
0
 
BellevueAdminAuthor Commented:
Moving the accounts was my next step.  I wanted to see if any one had a better Idea before I started.
0
 
BellevueAdminAuthor Commented:
My plan was to move the mailboxes to another mailstore.  I was looking for confirmation we were on the right track.  Thank you for you assistance.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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