Veeam requires that the Exchange server is virtual. We use Veeam for all our VMs and then do another layer of Symantec Back-Up Exec for our Exchange server. If I had it my way, it'd be Veeam all the time...they have such a great product and a large plethora of resources online to help you out. They also do regional workshops to better broaden or deepen (dependent upon subject matter) knowledge.
From: Tom Miller [mailto:[email protected]] Sent: Friday, April 12, 2013 7:51 AM To: MS-Exchange Admin Issues Subject: Re: Backup Exec 2013 and Exchange 2013 issues - Symantec's response I was eventually contacted by Symantec - I had an open ticket - and was told that backups won't work with Exchange 2010 SP3 and the update for supporting it won't be out until May, but more like June. Our Symantec rep said we could try Netbackup as an option, as that support Exchange 2010 SP3. Naturally it's more expensive. I'm also looking at Veeam. On Tue, Apr 2, 2013 at 1:20 PM, Chyka, Robert <[email protected]<mailto:[email protected]>> wrote: I am interested also please. Thanks. [cid:[email protected]] From: Tom Miller [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, April 02, 2013 12:56 PM To: MS-Exchange Admin Issues Subject: Re: Backup Exec 2013 and Exchange 2013 issues - Symantec's response That would be appreciated, thanks. On Tue, Apr 2, 2013 at 10:39 AM, Steve Ens <[email protected]<mailto:[email protected]>> wrote: Symantec gave me a couple of scripts to use a while back to "fix" this issue. If you're interested I can see if I can pull them up. On Tue, Apr 2, 2013 at 4:33 AM, Tom Miller <[email protected]<mailto:[email protected]>> wrote: Thanks for the comments and it's good to know it's not just my environment at least. The backups never fail on my small databases and public folders, just the large databases. When I check on the backups, I see the backup rate getting slower as time goes by and I suppose it times out. I use backup to disk, copy to tape method. Anyone have any suggestions for a product that works? Tom On Mon, Apr 1, 2013 at 10:21 PM, Steve Ens <[email protected]<mailto:[email protected]>> wrote: My suggestion is to start tweeting to the backup exec account....that usually wakes up their tier two or three support. Sent from my FriPad On 2013-04-01, at 9:04 PM, "Chyka, Robert" <[email protected]<mailto:[email protected]>> wrote: I am using the same setup with you and encountering the same issues. I get a successful, clean, no error backup about once every 6 backups or so. I am very frustrated also. I may consider changing software packages if this doesn't get fixed soon. I really don't think this is a Microsoft issue as my exchange environment is very stable. <image001.png> From: Tom Miller [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, April 01, 2013 9:30 PM To: MS-Exchange Admin Issues Subject: Backup Exec 2013 and Exchange 2013 issues - Symantec's response I've been having issues with Backup Exec backing up my Exchange 2010 SP3 environment. I've had the same issues since we migrated to Exchange 2010 and that was on SP2. Backup Exec 2012 (and Backup Exec 2010 before I upgraded) always failed on Exchange DAGs here. This is a VMware environment. Exchange is on Windows 2008 R2 servers. My environment is simple: two CAS servers, two DAG servers. I opened a support request with Symantec about the issue. The response I received is: I would like to inform you that exchange 2010 SP3 is not yet supported by the latest version of BE at the moment. By not supported I mean that BE has not been tested with Exchange 2010 SP3 officialy. Support for the same may be expected in upcoming releases. About the VSS writers, BE calls them during the backup to take a snapshot of the databases and logs. But due to some reason the writers fail again and again and cause the backup job to fail inturn. In this case, I would suggest you to contact Microsoft Support to fix the VSS writer issue. Once fixed, you can continue taking backups successfully. Just make sure that the Advanced Open File Option is not selected in the backup as it is not recommended for exchange. Well...that sucks. I didn't know about the advanced open file. so I'll disable that and give it another try. So, what are you folks using for backup? The vss writers are always stable, at least when I check. Tom --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe exchangelist --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist ________________________________________ E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited. GEM Realty Capital, Inc. and its affiliates and subsidiaries are not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist
<<inline: image001.png>>
