Link to home
Start Free TrialLog in
Avatar of ICantSee
ICantSeeFlag for United States of America

asked on

Backup Exec 2012 backing up Exchange DAG. Error querying writer status error

We are backing up an Exchange environment that has 48 GB of data. The program that we use is Symantec Backup Exec 2012 SP1a. The information is being backed up to a Tandberg LT04 tape library.

The transfer rate drops below 20 MB per minute and the backup eventually fails with the "error querying writer status" error.

The SQL cluster is backing up at over 1000 MB per minute.

Why the difference is transfer rates? Is there anything I can do to speed this up?
Avatar of Haresh Nikumbh
Haresh Nikumbh
Flag of India image

have you check Vss writers status on the server?

to check vss writer status run following command on command prompt

vssadmin list writers

Also check it out below link

http://www.symantec.com/business/support/index?page=content&id=TECH27875
Avatar of ICantSee

ASKER

Thank you for your response.

Odd... I ran the command all entries said "stable... No error"

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32> VSSADMIN LIST WRITERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {9ea36756-b049-40f4-b446-8091962b50a9}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {ad077ab4-5b79-4276-9192-ebe08c2a161d}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b670ac8f-b9ec-4481-8efe-4f0343338827}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {7efb278d-f1e6-42a1-8d05-6e6a048c409f}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {6b2d6004-ef64-4505-94ac-bd5c0a7d524e}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {711dd748-19c7-4859-a107-c47ef38f8230}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b9874ad8-048d-49ea-bbe8-b86084610557}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {815af8a7-325f-47f3-ae94-19660b4df73e}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {a154763d-9690-4ead-b24a-3f21928a7f85}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {4e7171a4-9f98-420a-8697-f1071e7297a7}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5cf5bee5-eeca-4610-8ac3-e8aafd3b78ca}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {b523f5f1-ca4a-4145-879f-b6f419a0fce9}
   State: [1] Stable
   Last error: No error

Any additional feedback will be appreciated.
Here is a copy of the BE log for that job...

User generated image
If this is the full output of the command "vssadmin list writers" then it looks like hyper-V writer is missing.

check below link
http://www.symantec.com/connect/forums/backup-exec-2012-v-79-57344-65233-snapshot-technology-initialization-failure
ASKER CERTIFIED SOLUTION
Avatar of ICantSee
ICantSee
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
issue still isn't resolved but at least the backups are working