Solved

Exchange 2010 - Symantec Backup Exec 2010 incremental backup fails

Posted on 2010-11-17
11
2,279 Views
Last Modified: 2012-06-27
Hello,

We use an Exchange 2010 and Backup Exec 2010 R2 for backup. We deployed a weekly full, and a daily incremental backup. The weekly full works well, but the incremental fails, we get the following error message:
Final error: 0xe000035e - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database.  You must use the Exchange Agent to run a full backup before you run a differential or incremental backup.

I've checked the store, and found the follows:

Get-MailboxDatabase -status | Select Servername,Identity,Lastfullbackup

ServerName                              Identity                                LastFullBackup
----------                              --------                                --------------
BIXMAIL                                 Mailbox Database 0314621290             2010.11.17. 4:07:57
BIXMAIL                                 Archive Database BIXMAIL                2010.11.17. 4:07:57

And eventlog (at specified time):

Exchange VSS Writer (instance 12) has successfully prepared the database engine for a full or copy backup of database 'Archive Database BIXMAIL'.

It's very interresing, because Backup Exec did not make a full backup in that time, and we do not use any other local backup (for eg. Windows Backup).

This server is a dedicated Exchange server, without any 3rd application (except BackupExec agent).

Do you have any idea, how can we turn off this full backup?
Thanks!
0
Comment
Question by:Cook77
  • 6
  • 3
  • 2
11 Comments
 
LVL 46

Expert Comment

by:noxcho
ID: 34155300
According to the error message it is asking you to use Agent to create full backup. Do you create the full backup using exactly same agent?
0
 

Author Comment

by:Cook77
ID: 34155543
Yes. We create backup ONLY by Backup Exec.
0
 
LVL 46

Expert Comment

by:noxcho
ID: 34156059
Is there any archive created by this agent?
0
 
LVL 7

Expert Comment

by:firemanf29
ID: 34163161
Do you have a Backup Exec Exchange 2010 License?  It is a separate License and cost additional.

Also make sure no one used NT Backup to backup Exchange 2010 after your Full backup was run.  If they did you will get this message as Backup Exec was not the program last used to Backup Exchange.  If they used NT Backup after your Backup Exec backup then as part of NT Backups final process it purged the Exchange transaction log files.
0
 
LVL 7

Expert Comment

by:firemanf29
ID: 34163204
One more thing.  I think backup Exec would have noted this but make sure you are not using Circular logging.  You can't do incrementals with Circular logging enabled.

I'm still leaning toward something else backed up part if not all of your Exchange store.  

I would turn logging to full in Exchange and watch it closely over the next week.  You may want to take a look at AD and see what account have access to do the backup and check the current event log to see if they logged into the server around that time or usually a few minutes before.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:Cook77
ID: 34171642
I appears, that some Exchange related service does some backup, and therefore the logs are deleted every night around 1 AM. I'm trying to figure out what service does this.
0
 

Author Comment

by:Cook77
ID: 34205128
We have a progress in the situation: we find out, that the log are truncated in the "database maintenance" time interval. 24/7 ESE is enabled, but what does this "database maintenance" do exactly?
Is it safe to turn it off?
0
 
LVL 46

Expert Comment

by:noxcho
ID: 34205273
What is doing the "database maintenance"? Exchange?
0
 

Author Comment

by:Cook77
ID: 34211015
0
 

Accepted Solution

by:
Cook77 earned 0 total points
ID: 34221646
Finally we did it. :-) This Windows server is guest OS on VMware ESX server. Every night the esx takes a snapshot from this server, and in this process through vmware tools the Exchange logs were deleted.
0
 

Author Closing Comment

by:Cook77
ID: 34255631
Finally we found the solution for this problem.
0

Featured Post

The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now