Exchange 2010 Backup : Updating Catalogs Very Long
When backing up Exchange Server 2010 it appears to backup the data with zero issues. However, it takes 20+ hours to run a Differential backup due to the length of time it takes to update the catalogs. This was an issue for us in the previous version of Backup Exec 2010 R3.The issue was not consistent though. For instance; in 2012 we had an issue inlate July andearly December. Theissue in July seemed to correct itself? The issue from December is still ongoing. The backup rate is at about 282 MB/min. Whereas while updating catalogs runs at about 1 MB/min. This definitely appears to be the issue as the entire backup is less than 10GB. The full backup runs normally and does not take an extended period of time while updating catalogs. For all Exchange backups we are running GRT. Any help would be greatly appreciated.
Exchange 2010 backups fail (sometimes)
I have had intermitent issues with one of my Exchange servers backups failing. Both servers are Exchange 2010 SP2 w/rollup 3 Only difference is the server with issues has Server 2008 Stnd SP2 (NOT R2) some nights backup is fine, and sometimes the backup fails within a minute with error e0000391 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again. and sometimes it runs about 45 minutes and errors with e000038d - Backup Exec could not back up the Exchange database because it could not find a healthy copy of the database. the remote agent is up to date on this server. It also will fail if I try to run it after it fails. I have found in the server event logs when it fails immediately Event ID 9782 - Exchange VSS Writer (instance 8afeae75-cdeb-4042-ad45-642c11cbd610:37) has completed the backup of database 'Mailbox Database 1786741976' with errors. The backup did not complete successfully, and no log files were truncated for this database. when it fails after the 45 minutes I see VSS successes. I see no errros when I check the VSS status run - VSSADMIN LIST WRITERS when I ran SGMon I was seeing this in the logs BESERVER: [11/06/12 08:46:09] [0000] [14560]"Cluster" key does not appear to be present in the registry BESERVER: [11/06/12 08:46:09] [0000] [14560] Failed to open Microsoft cluster () BESERVER: [11/06/12 08:46:09] [0000] [14560] VCS cluster keys do not appear to be present in the registry BESERVER: [11/06/12 08:46:09] [0000] [14560] Failed to open VCS cluster () Thsi server is not in a DAG Not sure if this is a MS issue or a remote agent issue.
Symentac Backup Exec 2012 enable GRT backup Exchange 2003 1022 - Error -1022 There is a disk IO error
Hi all, last Saturday, I enable GRT when backup up our exchange 2003 server using Symantect Backup Exec 2012, until this Wednesday, the GRT runs well. But yesterday, the following error message encountered, and the backup jobs failed V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-1022 There is a disk IO error. ' During these days from last Saturday until to now, i haven't change any configurations to Symantect Backup Exec 2012. AOFO & Exchange Options is as below. Does anyone can help to to avoid this error? thanks very much.``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````Exchange Incremental Backup Fails. Shadow copy instance aborted.
We have a problem with Backup Exec 12.5 when running a Exchange incremental backup. (Exchange Server 2007)Usually it completes successful, but in the last two months it has failed 5 times. Before that it never has failed. When we manually start a new run, it works fine. And it also usually works for a couple of weeks, before it encounters the error again. We get error code: E000FED1. It seems to have something to to with VSS. When I check Event Viewer I can see that it seems to backup "First Storage Group" successful, but when it move on to "Second Storage Group" the following happens: 2013-02-07 20:08:57 - Exchange VSS Writer has prepared for backup successfully. 2013-02-07 20:09:01 - Shadow copy instance 108 starting. This will be an Incremental shadow copy. 2013-02-07 20:09:01 - Exchange VVS Writer has successfully prepared the database engine... 2013-02-07 20:09:01 - Exchange VVS Writer has prepared for Snapshot successfully. 2013-02-07 20:09:01 - Information Store.. Shadow copy instance 108 freeze started. 2013-02-07 20:09:01 - MSExchangeIS.. Second Storage Group: Shadow copy instance 108 freeze started. 2013-02-07 20:09:04 - Exchange VSS Writer has frozen the storage group(s) successfully. 2013-02-07 20:09:32 - Information Store.. Shadow copy instance 108 freeze ended. 2013-02-07 20:09:32 - Error - Information Store.. Shadow copy instance 108 aborted. When I compare log above with a log from the day before when it completed successful, the diffrence is only the aborted-row. Of course, when successful, it didn't abort but instead the log reads: "Exchange VSS Writer.. has thawed the storage group(s) successfully." The time between "frozen.. successfully" and "freeze ended" logsis just 5 seconds in a successful backup, but in this failedbackup, it's 28 seconds. Could it be a timeout error? Greatful for any ideas about what is causing this failure.
Exchange not freeing vss space
Greetings - I am using Backup Exec 2010 R2, SP1 to back up Microsoft Exchange 2010. I am using "System - Use Microsoft Software Shadow Copy Provider" as my snapshot provider. On the Exchange server (which is running windows 2008 R2 Enterprise), shadow copies are "Disabled". Backups work, but I recently discover that I have over 100 gigs of "missing" space - IE: Windows file explorer reports 464 gigs used, but the individual files and folders are only taking about 300 gigs of space. When I right click on "Configure Shadow Copies" in windows file explorer, it reports that "next run time" is disabled, but shadow copies are consuming about 150 gigs on space. I'm assuming that Backup Exec is programmatically creating VSS snapshots. Unfortunately it seems that it is not cleaning up/deleting the snapshots after the backups finish running. How can I get BE to automatically clean up the snapshots? Thanks in advance!
