Yes right on.  I had a Symantec technician work on my issue for a total of 8 
hours over 2 days and he pretty much gave up.  He told me he was going ot do 
some more research and get back to me.  That was 3 weeks ago.

BTW he didn't put blame on my Exchange 2010 environment even once.
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Monday, April 01, 2013 10:10 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup Exec 2013 and Exchange 2013 issues - Symantec's response

VSS specifications did not change for Exchange 2010 sp3.

They did for Exchange 2013.

Any compliant implementation for Exchange 2010 should work regardless of the 
service pack.

From: Chyka, Robert [mailto:bch...@medaille.edu]
Sent: Monday, April 1, 2013 10:05 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup Exec 2013 and Exchange 2013 issues - Symantec's response

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.

[cid:3366368584_1217441]

From: Tom Miller [mailto:tominyorkt...@gmail.com]
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 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

<<inline: image001.png>>

Reply via email to