Forum Discussion

TorrenceS's avatar
TorrenceS
Level 3
15 years ago

Backup Failure Error E000035E

Hi, I am using Backup Exec 2010 R2

I have several incremental backups that fail not all incrementals fail. The full's do run without any issues.

The failure message is as follows:

e000035e - 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.

Does anyone know why this happens?

  • Hi,

    Please follow this link for the same :

    http://www.symantec.com/docs/TECH59970

    Disable any database maintenance that run on exchange database which which may be scheduled to run backups as Backup exec Full backup job needs to set a flag for the same.

    Check for any other backup utility like NTBackup, etc & disable the same.

    Run full backup job from BE exchange agent & then incremental which should work..

  • Hi,

    Please follow this link for the same :

    http://www.symantec.com/docs/TECH59970

    Disable any database maintenance that run on exchange database which which may be scheduled to run backups as Backup exec Full backup job needs to set a flag for the same.

    Check for any other backup utility like NTBackup, etc & disable the same.

    Run full backup job from BE exchange agent & then incremental which should work..

  • Thank you for your response. I am running exchange 2007 on Windows 2008 and Backup Exec 2010 R2 on Windows 2008. Does the same solution apply? Why does it only happen on some of my incrementals?

  • Yes, it does apply to this.

    It happens if any 3rd party backups messes-up with the backup flag set on the exchange database.

    So we need to make sure nothing else runs between full & incremental backup of exchange using backup exec exchange agent.

  • Hello,

    No other backups running. Windows server is not installed. What else could cause this?

  • yes, this is a backup software from MS which could be the reason, please try disabling the dprm service for the same.