Exchange Backup Fails: 0xe00002f7 / V-79-57344-759 / VFF Open Failure
Hello, we are using Backup Exec 2010 R3 SP4 (Ver 13.0 Rev. 5204 (64Bit)) on Windows Server 2008 R2. This Server is doing a Backup of an Exchange 2010 Server running on another Windows Server 2008 R2 via Remote Agent for Windows Servers. The backup is running two times a day: In the middle of the day to disk. In the night to tape. The Backup was running fine for several years. Since 3 weeks the backup to tape fails, while the backup to disk still works fine. Nothing was changed. The error is (translated): _______________________________________________________________________ Completed status: Failed Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-759 _______________________________________________________________________ and: _______________________________________________________________________ Backup- \\"servername"\Microsoft Information Store\PRIVDB02 V-79-57344-759 - Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources. _______________________________________________________________________ What we have already tried: -Restart Server -Update Backup Exec to newest Version -Install Hotfix TECH164659 -Solutions from this articles: http://www.symantec.com/business/support/index?page=content&id=TECH128187 http://www.symantec.com/connect/forums/0xe00002f7-cannot-extract-mailbox-messages-exchange-backup-0 -deleting an recreating the backup-job -delting and reinstalling the remote agent -deleting Files on Exchange Server to get more free disk space -defining max cache size for Exchange Information Store to get more free RAM -Installing all Windows an Exchange Updates (Exchange 2010 SP3 Update Rollup 7) Nothing of the above did help, we are still getting the same error on backup to Tape while Backup to Disk runs fine. Can anyone help? Thanks Error in original language: _______________________________________________________________ Sichern- \\"servername"\Microsoft Information Store\PRIVDB02 V-79-57344-759 - Der Vorgang für die ausgewählte Ressource unter Verwendung der angegebenen Optionen konnte aus folgendem Grund nicht beendet werden: Fehler beim Öffnen des VFF. Dies kann durch zu geringen Arbeits- oder Festplattenspeicher verursacht werden. Auftrag beendet am Donnerstag, 25. September 2014 um 04:59:04 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe00002f7 - Ein Extrahieren der Mailbox-Nachrichten aus dem Exchange-Backup ist nicht möglich. Im Auftragsprotokoll finden Sie zusätzliche Informationen. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-759 _______________________________________________________________Solved9.7KViews2likes10CommentsExchange 2013 backup fails with Backup Exec 2014
For the past week I've been having failures with my backup of Exchange. I get the errors: V-79-57344-34070 - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted. All databases are mounted. The VSS list writes are all stable. Not sure what to do again. Any suggestions?Solved13KViews1like10CommentsIncremental backup of exchange logs windows errors
Well the title says it all; We are running Full/Incremental backups (BE 2015) on our Exchange 2007 stores. BE reports that full and incremental backups are succesfull however on the Exchange server we are getting Event Error 206 (ESE) : Log Name: Application Source: ESE Description: MSExchangeIS (7244) First Storage Group: Database D:\ExchangeDB\Mailbox Database.edb cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. Which is immediately followed by error 57920 (Backup Exec): An error occured while preparing Microsoft Exchange Server \\EXCHANGE\First Storage Group to back up database. Error code 0xC8000230 Error message: The database missed a previous full backup before the incremental backup. What gives here? BE 2015 shows everything to be in order. I have tried removing the exchange logs, tried deleting and recreating the jobs, run full backups then new incrementals 9 ways to sunday with no change at all. Any advice would be greatly appreciated! Andy2.5KViews0likes9CommentsAfter Exchange upgrade backups no longer working
Hi, I recently upgraded our Exchange Infrastructure (Database Availability Group) from Exchange Server2013 Cumulative Update 5 to Exchange Sever 2013 CU 11. I also upgraded Exchange on the Backup Server (Media Server) to Exchange Server 2013 CU11. I have restarted both members of the DAG and the Backup Exec Server but keep getting the following error when trying to backup the DAG: - "Backup- MIEXCH1.Marine.ie V-79-57344-34070 - Snapshot Technology: Initialization failure on: "Microsoft Information Store". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted. Check the Windows Event Viewer for details. " Any troubleshooting steps much appreciated. We are running Backup Exec 2014 Version 14.1 Rev 1786. Is Exchange Server 2013 CU11 supported in this version of Backup Exec? thanks,576Views1like1Comment0xe000035e - Backup Exec Agent for Microsoft Exchange wurde nicht verwendet
Hello, we have a problem with Backup Exec 2014 14.1 Rev 1786. We use an Exchange 2010 on a Windows Server 2008 R2 in the VM and the Problem is, that Backup Exec don't Save the Exchange. On Saturday run a Full Backup and from Monday-Friday runs incremental. The Problem is, the Full Backup run without Problems, but the incremental abort with the Notice "Endgültiger Fehler: 0xe000035e - Backup Exec Agent for Microsoft Exchange wurde nicht verwendet, um das letzte vollständige Backup dieser Datenbank zu erstellen. Führen Sie ein vollständiges Backup mit Exchange Agent aus, bevor Sie ein Differenziell- oder inkrementelles Backup ausführen. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-862" On the Exchange the Agent is installed and was used with the Full Backup. GRT is disabled(we tested with anabled) and Advanced Open File is activ. Have some a Solution?890Views0likes2CommentsBE2014 - W2012R2 -> Exchange 2010 - E00027
Enviroment : Both, Exchange and BE Server are VM on the same VMWare Host. Backup Strategy - direct using RAWS BE Server BE2014 W2012R2 16 GB Ram TEMP - 2 TB free space BE Global Options Dedupe B2D 10 TB iSCSI NAS System Backup Target Exchange 2010 R3 W2008R2 32GB RAM Exchange Job Options : GRT on, B2D Dedupe, Server-side dedupe, Catalogue after the job immed. AOFO off Backup Schema Full - GRT ON Inc. Daily - GRT ON Inc. Nightly - GRT ON Problem Full Backup will end successful and the catalogue job after it. Incr. Backup will end successful but not the catalogue job after it. ErrorE00027 Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors V-79-57344-759 - Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources. Backup break always after 118GB of data. Tried solutions which didnt help Antivurs off Registry change : OnHostTemp Restart Updates Next steps SGMON full debug starts shortlySolved1.2KViews0likes9CommentsGRT backups of Exchange not truncating
When we do a GRT backup of our virtual Exchange server (Windows Server 2008 Ent) through our hyper-v host (Windows Server 2012 R2) with GRT enabled this does not truncate our logs. There are no errors on the job and says it's successful. When I check back in the log directory of exchange, all the logs from the databases still exist and have not been flushed. I'm running Backup Exec 2014 with SP2 + HF227745 Side note; when we run a backup of the Exchange server as if it were a physical machine the logs are truncated without issue (so it leads me to believe that this is not an issue with our Exchange server) I have a ticket out with Symantec for over 2 months now and the tech(s) that are assigned to my case don't seem to be making much leeway in steps to figure out what's wrong so I wanted to see if anyone else has experienced this issue and found a resolution?663Views0likes2CommentsError 0xe0008516 backing up Exchange 2013 after applying BE 15 "Feature Update 1"
We are running a single Exchange Server 2013 SU5 running on Windows Server 2012 R2 Backup provided with BackupExec 15 (14.2 rev 1180) running on Windows Server 2012 R2 All went well until we installed the recent Backup Exec "Feature Update". The Exchange backup fails with Auftrag beendet am Mittwoch, 16. September 2015 um 13:45:38 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe0008516 - Die für den Snapshot angegebene Datenbank wurde nicht gesichert, da die Datenbank nicht bereitgestellt war. Endgültige Fehlerkategorie: Systemfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-34070 The linked KB article leads nowhere. Exchange itself runs without any problems and certainly the database IS provided. I upgarded all agents and tripple checked the login configuration, rebooted both the backup server and the exchange server. I even created a new full backup job that only selected the entire "Exchange Information Store" with a single "Mailbox Database" and "PublicFolder Database". Same Error I did a thorrough research that resulted in "check your VSS writers" most of the time, so I checked the VSS writers with vssadmin list writers and I get a list of healty writers, but there is no “Microsoft Exchange Writer” listed as is presumably shuld(?) There is NO "exwriter.dll" anywhere on this server and since I doubt the Backup Exec Feature update deleted this one, i'm confident that there never was one. I DO have a "Microsoft Volume Shadow Copy Provider" service and if I start that one manually, it shuts down "clean" a few minutes later without any complaint. I DO have a "Exchange Extension for Server Backup" sevice that does quite the same. I CAN make a backup with the standard windows backup which successfully utilizes VSS Neiter the event log on the Exchange server nor the one on the backup server show anything useful I tried with and without the "granular" option. I'm quite clueless now how to proceede. The backup log is attached for a full backup from before the update that went well and one after the update that failed. Thanks for any help on this, RobertSolved2.3KViews0likes3Comments