Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
backingup exchange 2007
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
 Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
backingup exchange 2007 - 2.Jul.2008 10:26:55 AM
|
|
|
jkeys
Posts: 1
Joined: 2.Jul.2008
Status: offline
|
Hi everyone, we are trying to backup the exchange servers using backupexec 11d. We getting the following errors.
Backup- BMSMAIL1
V-79-57344-34110 - AOFO: Initialization failure on: "\\BMSMAIL\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 failed, but the operation can be retried (0x800423f3), State: Failed during prepare backup operation (7).
Symantec tech support states that the first error is caused by a known issue in Windows that puts the writer in an unstable state. They have sent me links to the hot fixes for this problem,
(they state that since it is in a cluster both servers must be patched) If the hot fixes do not work, Symantec states that then the only fix is to uninstall service pack 2 on both servers and reinstall, which I am sure, may cause issues with exchange. Has anyone else seen this problem and if so how did you fix it. I am very conceded about patching both servers in the cluster not to mention having to uninstall and reinstall a service pack on operational mail servers. Any help will be much appreciated! Thanks in advance.
|
|
|
|
|
RE: backingup exchange 2007 - 2.Jul.2008 11:46:56 AM
|
|
|
John Weber
Posts: 584
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline
|
Put the Backupexec down, and slowly back away. If you are lucky, it won't follow you.
Sort of half-serious. I hate what BackupExec has become since Symantec acquired Veritas. Shades of CA and ArcServe.
_____________________________
-jmw
http://tsoorad.blogspot.com
|
|
|
|
|
RE: backingup exchange 2007 - 2.Jul.2008 4:20:52 PM
|
|
|
Jesper Bernle
Posts: 221
Joined: 15.Oct.2007
From: Sweden
Status: offline
|
"I created a new full backup job that only backed up the Information Store (rather than making the IS backup part of my full set of backups). The backup ran fine and this time the logs flushed. This morning I ran a quick Incremental backup of the IS (again, as a solo job rather than part of the incremental backup that also gets files). The backup ran fine and again the logs were flushed. In their best practices for Backup Exec 12 and Exchange, Symantec says to make the IS backup separate from your file backups. I never had to do this in the past. But if I have to do that now, no problem. As long as I get a good backup!"
Taken from: https://forums.symantec.com/syment/board/message?board.id=be12_exchange&thread.id=278
Hope it helps ...
_____________________________
Jesper Bernle
Enterprise Messaging Administrator
|
|
|
|
|
RE: backingup exchange 2007 - 7.Jul.2008 1:26:35 AM
|
|
|
Exchange_Geek
Posts: 1010
Joined: 31.Dec.2006
Status: offline
|
I know this hasnt been documented any where - however few of my colleagues from Microsoft, stated that Backup Exec 11D tends to make the VSS Writers unstable "at times" and hence this causes the problems with Backups using the tool.
Now, "they" told me that when the issue was "escalated" to higher-tier Symantec support and as per few customers "they" said the issue was fixed in next version Backup Exec 12a.
Again, please confirm this with Symantec support - since its not officially released statement.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
