Exchange 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?Solved13KViews1like10CommentsExchange lässt sich nicht mehr sichern
Hallo! Wir haben BackupExec 2010 R3 im Einsatz mit "Agent for MS Exchange Server", "Active Directory Recovery Agent" und "Remote Agent for Windows and Netware Servers". Backup Exec läuft auf einem Server 2003 R2 mit allen Servicepacks und Updates Exchange läuft auf einem Server 2003 R2 64bit mit allen Servicepacks und Updates. Der Remote Agent wurde auf dem Server aktualisiert. Das Problem: Bis letzte Woche wurde der Exchange-Server problemlos gesichert - auch eine Wiederherstellung war kein Problem. Leider habe ich dann das SP2 von BackupExec eingespielt und die 5 angebotenen Hotfixes. Seither lässt sich Exchange nicht mehr sichern und wir bekommen folgende Fehlermeldung: V-79-57344-34070 - AOFO: Initialisierung fehlgeschlagen: "Microsoft Information Store". Advanced Open File Option verwendet: Microsoft Volume Shadow Copy Service (VSS). Fehler im Snapshot-Provider (0xE0008516): Die für einen Snapshot angegebenen Ressourcen verfügen über keine gültigen Daten. Überprüfen Sie, ob Dateien gelöscht oder umbenannt wurden. Ausführliche Angaben finden Sie in der Windows-Ereignisanzeige. Der Link zur entsprechenden Supportseite erzählt irgendwas von Advanced Open File Option - welche nicht verwendet wird. Dies habe ich vorhin überprüft. In der Auswahlliste der Sicherungsjobs wird der Microsoft Information Store seit den Updates nicht mehr angezeigt. Lediglich im Registerreiter "Auswahldetails anzeigen" stehen die Einträge nach wie vor drinnen: \\servername.domäne.inhouse\Microsoft Information Store\First Storage Group|*.* /SUBDIR \\servername.domäne.inhouse\Microsoft Information Store\Second Storage Group|*.* /SUBDIR Kennt dieses Problem jemand und hat vielleicht eine Lösung dafür? Ansonsten müsste ich BackupExec komplett de- und wieder installieren (OHNE irgendwelchen Updates) und hoffen, dass das Programm danach wieder so läuft wie es soll. Das wäre die letzte Option, denn alle Versuche die Exchange-Sicherung seit einigen Tagen wieder zum laufen zu bringen, sind fehlgeschlagen. Vielen Dank10KViews0likes12CommentsExchange 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.7KViews2likes10CommentsBE 2012 and Data Domain w/ DDBoost
Background: So we have Backup Exec 2012 and two Data Domain DD620's. We have all the required licensing including the Data Domain DD Boost and replication licenses. I have installed the Open Storage Technology (OST) plugin 2.5.0.3 as suggested for the version of BE. Both DD boxes are visable and connected to my BE server. I have foud some documentation and a video that explains some of what I am looking for but not entirely and most of it is for BE2010. The BE 2012 documentation from DD is not up to date yet. I am trying to setup backups as my tape drive has had enough and is not working properly. Anyone I have talked to just says you backup to it, then I continue finding little things that need to be done. No verify, no precompression, some said no deduplication in the job, other said server side dedupe because DDBoost manages it with OST plugin. Too much information and not enough people knowing what to tell me. The DD weekend support guys don't know the software titles they just know the hardware. I need help now unfortunately... Question: What settings do I use for Backups? I have Active Directory, Exchange, SharePoint, and SQL agents.6.4KViews1like32CommentsThe VSS Writer timed out (0x800423f2)
Hello We have a problem with the VSS Writer with several customers, but no solution found on the Symantec/Microsoft forums. The costumers are running SBS 2008, Service pack 2 and Exchange 2007 Sp3, all windows updates are installed. These customers are running Symantec Backup Exec 2010 R3 with SP1 and all the latest hotfixes. The problem is that we can't backup the exchange database. It only works when we do a IIS reset, the backup will work one day, and fails the day after. Backup V-79-57344-65233 - AOFO: Initialization failure on: "\\SBSMICHOEL\Microsoft Information Store\First Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). All the VSS writers are stable. No errors. The backup of the exchange database is now running separately from the daily backup, daily backup runs fine. Exchange Not. Can anyone help me with these? Greetz TomSolved6.1KViews1like2CommentsVSS Writer "retryable error" Exchange 2010 Windows 2008R2
I have seen many posts about this error, but most of them are for Exchange 2003 or 2007 or Windows 2003. This is happening on: Backup Exec 2010 R3 Windows 2008 R2, SP1 Exchange 2010 SP1 RU4 Preferred Server list has passive node first "Let Backup Exec automatically choose ..." is enabled AOFO turned off GRT enabled Error happens repeatedly, but not consistently Backup- DAGName2V-79-57344-65233 - AOFO: Initialization failure on: "\\DAGName\Microsoft Information Store\DataBase1". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare backup operation (7). The VSS Writer list always shows "retryable error" for the Microsoft Exchange Replication Writer, and the condition only occurs on this database, which is the largest of 5 databases, at 500GB, and is the last DB to be backed up. Followed all recommendations found so far: AOFO turned off, tried re-registering VSS, but a re-boot of the passive node is the only thing that works ... sometimes. Again, no consistency, not even in the failures or successes. The past 2 nightly backups failed while the previous 3 ran successfully. Re-booting the Exchange server(s) to fix this error is ludicrous, as well as costly to our user community. Anyone have an idea of wheer/how to pursue this?5.9KViews1like5CommentsBackup Exec Become Very slow rate job after Windows Update
This is my third thread for the same problem in the same server, everytime that i make Windows Update, The job to Backup Mailbox Databases become very Slow. I have a server with 2008 R2 with backup exec 2010 R3 installed and four Hyper-V servers, CAS-HUB server, Mailbox Server, Blackberry Server and a DC server. i have two Backup job, one for Mailboxes Databases, and othet for the four Hyper-V, Mailboxes job run in the morning, and Hyper-V job run at night. Normally Mailbox job run between 5 and 6 hours, between 2600 and 3000 MB/s job rate for 600 GB of data. The other Job run between 5 and 6 hours, Between 3000 to 4000 MB/s for 900 GB of data. Everytime that i make Windows Update on the Phisical Server, the Mailbox job become very slow between 500 and 600 MB/s and it take between 19 to 20 Hours, i search in several forums, blog, tech support guides, and there isn´t solution for my case. The Jod to Backup Hyper-V dont have any problem, run normally. is OK is this occurs one or two times, but is everytime, i decided install Windows Update in the phisical server every four month, but this isn´t a correct security police in the company, my only solution when this happend is uninstall-reinstall the Backup exec Server, but i make the windows update last week-end, and i Unnistall-Reinstall 3 times and the problema continue. This time Unnistall-Reinstall dont solve my problem, and when i did this, i have to restat the server, wich i do early in the morning when nobody is using the email service. I dont know what else to do, Symantec support dont give any solution about this topic. If any body can help, the Backup is over LTO 4 tapes, Drivers are update, Backup Exec 2010 R3 full patches. The Mailbox is exchange 2010.5.7KViews1like7CommentsExchange Information Store not available in selection list
I have a new backup server with Backup Exec 2010 R3. I am trying to backup the Information store on the Exchange 2007 (SP1) server but it is not available on the selection list. I can backup the flat files of the server. I do have the Exchange agent license. Troubleshooting: Uninstalled and reinstalled remote agent on the Exchange server (several times) Uninstalled and reinstalled the Exchange option on the media server Did a "repair" of Backup Exec on the media server Ran BE_Support Tool.exe (in the RAWS directory) on the Exchange Server. No Warnings. (It did originally say that I needed to run a VSS hotfix which I did). Permmissions all check out. Ran remote agent in debug mode. some dlls "not found": Example: bedsxchg.dll could not be loaded: The specified module could not be found. The following article talks about this issue with BUE 12. http://www.symantec.com/business/support/index?page=content&id=TECH58430 SSolved4.7KViews3likes34CommentsError: 0xe0000393 (V-79-57344-915) Cannot extract mailbox messages from the Exchange backup.
For the last few days I've been getting the following error message. I've tried restarting the server and manually backing up the Exchange database using the ntbackup utility which did complete successfully. Has anyone else had this problem? Any ideas/solutions? V-79-57344-915 - Unable to complete the operation for the selected resource using the specified options. The following error was returned when opening the Exchange Database file: '-528 The current log file is missing. ' Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors Server Information: Windows 2003 SBS, Backup Exec 2010 R2Solved4.5KViews1like53Comments