Exchange 2010 VSS Replica Writer Errors 2008 R2

Hi Folks,  Having issues using Avamar Exchange VSS backup's.

Backup run through of Passive Node in DAG but logs do not truncate and get this error at the end of the backup:

ERROR: Selected writer 'Microsoft Exchange Replica Writer' reported an error!
   - Status: 1 (VSS_WS_STABLE)
   - Writer Failure code: 0x800423f3 (VSS_E_WRITERERROR_RETRYABLE)
999Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
I have been using Avamar for several years. I ran into a similar problem when we moved to Exchange 2010. From working with Avamar support, I found out that the only way the logs will clear is to backup the active node. The passive node will not clear the logs. Also, with Exchange 2010, unless there is a minimum number of log entries, the logs will not purge for up to 4 days. I had called MS, because on several small databases, even though my backups were successful, the logs were not purging on just those. I believe the link below is the one they sent me:

http://blogs.technet.com/b/timmcmic/archive/2012/03/12/exchange-2010-log-truncation-and-checkpoint-at-log-creation-in-a-database-availability-group.aspx

While I do not remember the VSS error I was getting, it was resolved by making a permission change to the DCOM and adding Network Services. This was done by In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties. Click on the "COM Security" tab. Select "Edit Defaults" under "Access Permissions". Click Add and Enter "Network Services", then check the "Allow" on Local Access. It should look like this when done:
 Security Changes
0
Rodney BarnhardtServer AdministratorCommented:
BTW, I have not seen any performance problems backing up the active node. Their recommendation was to select "Always" on the Options page, although I have just left it as the active writer.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.