Assist-Netopa
asked on
SBS 2008 Exchange Logs not clearing after Full Backup
Experts,
We have taken over support of an SBS 2008 machine and the Exchange transaction logs are not being cleared even after FULL SBS 2008 Windows Server Backup on a nightly basis.
I have compared the VSS writers between this SBS 2008 and another one. On the problem SBS there are only the following writers:
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-5 31aa6355fc 4}
Writer Instance Id: {07084cbf-098b-4701-8a01-2 79befc28e7 8}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7 1dbb18f848 5}
Writer Instance Id: {061b346b-400a-4f44-af06-b 01e42aa7e6 5}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3 bee2926fd7 f}
Writer Instance Id: {719f9c11-0cdb-41ee-84dd-3 23fc13e5fd 2}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7 847f01fc64 f}
Writer Instance Id: {bb6d38a7-71d0-43e9-addc-1 52581aa3a4 a}
State: [1] Stable
Last error: No error
On the working server there are a great deal more writers:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1 050253ae22 0}
Writer Instance Id: {60c18ad8-2c87-4c91-a8b4-b e8271ff1d5 1}
State: [1] Stable
Last error: No error
Writer name: 'SharePoint Services Writer'
Writer Id: {c2f52614-5e53-4858-a589-3 8eeb25c618 4}
Writer Instance Id: {b662770c-ff6c-486e-939c-1 3cfcfb0e74 b}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a 0c4db26912 a}
Writer Instance Id: {bb4b5d33-c086-4603-8ac3-6 78d4baed22 5}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-5 31aa6355fc 4}
Writer Instance Id: {2c17cee9-a8b5-4506-b719-1 6a794a1cba 2}
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2 958fb88ce2 9}
Writer Instance Id: {b2b03188-8da7-4e76-a081-8 47ab71c159 3}
State: [1] Stable
Last error: No error
Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e 5d5097e367 4}
Writer Instance Id: {c4fe32ce-d933-4f26-91bf-3 bf315fd6dc 1}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4 c6fea9e93a d}
Writer Instance Id: {0302e9f7-37eb-4c86-b95c-6 94a35044a5 7}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1 f8c654603f 6}
Writer Instance Id: {3975dd2f-668e-4d64-9512-c 9baa1c007f c}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {c0613cdc-c0fe-4c4f-bbab-6 1ea9539b4b a}
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-6 3063e3a1f8 6}
Writer Instance Id: {91cb4cbb-53d5-4a57-8de6-5 4bc860879a f}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7 1dbb18f848 5}
Writer Instance Id: {4ba3ea8e-06da-41f6-b712-3 ca5b9ff7f7 b}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3 cf38448475 7}
Writer Instance Id: {348f4977-0826-4062-a43d-e 2020006535 a}
State: [1] Stable
Last error: No error
Writer name: 'SPSearch VSS Writer'
Writer Id: {57af97e4-4a76-4ace-a756-d 11e8f0294c 7}
Writer Instance Id: {61f1c09f-5752-4ede-90a3-2 6e7b33fcbc d}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d 5bc721bb18 a}
Writer Instance Id: {e5c828ba-29f4-4b84-af08-d 304e4b9b8d 8}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7 847f01fc64 f}
Writer Instance Id: {63a56723-e903-43d7-a676-9 59140a8bdf 0}
State: [1] Stable
Last error: No error
Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-c cd9bdc624c b}
Writer Instance Id: {bae802d8-4c39-45e8-9b2a-1 a9ff6bcb6f 9}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6 ca8b293836 6}
Writer Instance Id: {dd91915d-2808-473c-a935-1 2435da87a7 9}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3 bee2926fd7 f}
Writer Instance Id: {86615212-cb35-4bc1-8d1b-b 5f5781603b a}
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6 c267a62974 1}
Writer Instance Id: {0a52a170-4cc6-47e4-a378-e 94f0b01638 2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f 328f07ac1e 0}
Writer Instance Id: {2ec690db-9d5b-4d21-aad4-c ae0fb88d76 8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4 9d8f43532f 0}
Writer Instance Id: {8bf227f7-c2dc-46f9-8bcd-2 f4348a7df5 f}
State: [1] Stable
Last error: No error
They previously used Storagecraft Backup before we took over however we preferred to use the build in tools. Could it be that the missing VSS writers (exchange in particular) has meant that the logs are not being cleared up until the last known full backup?
Could Storagecraft have removed the built in writers and used it's own?
How would we repair/replace the missing writers?
The Exchange Server 2007 is only on SP1 build level but the Exchange aware issue mentioned here did not affect SBS 2008:
http://blogs.technet.com/b/exchange/archive/2008/06/18/3405615.aspx
We are hesitant to install the latest SP's and RU's given there are writers missing.
We have taken over support of an SBS 2008 machine and the Exchange transaction logs are not being cleared even after FULL SBS 2008 Windows Server Backup on a nightly basis.
I have compared the VSS writers between this SBS 2008 and another one. On the problem SBS there are only the following writers:
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-5
Writer Instance Id: {07084cbf-098b-4701-8a01-2
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7
Writer Instance Id: {061b346b-400a-4f44-af06-b
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3
Writer Instance Id: {719f9c11-0cdb-41ee-84dd-3
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7
Writer Instance Id: {bb6d38a7-71d0-43e9-addc-1
State: [1] Stable
Last error: No error
On the working server there are a great deal more writers:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1
Writer Instance Id: {60c18ad8-2c87-4c91-a8b4-b
State: [1] Stable
Last error: No error
Writer name: 'SharePoint Services Writer'
Writer Id: {c2f52614-5e53-4858-a589-3
Writer Instance Id: {b662770c-ff6c-486e-939c-1
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a
Writer Instance Id: {bb4b5d33-c086-4603-8ac3-6
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-5
Writer Instance Id: {2c17cee9-a8b5-4506-b719-1
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2
Writer Instance Id: {b2b03188-8da7-4e76-a081-8
State: [1] Stable
Last error: No error
Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e
Writer Instance Id: {c4fe32ce-d933-4f26-91bf-3
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4
Writer Instance Id: {0302e9f7-37eb-4c86-b95c-6
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1
Writer Instance Id: {3975dd2f-668e-4d64-9512-c
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {c0613cdc-c0fe-4c4f-bbab-6
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-6
Writer Instance Id: {91cb4cbb-53d5-4a57-8de6-5
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7
Writer Instance Id: {4ba3ea8e-06da-41f6-b712-3
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3
Writer Instance Id: {348f4977-0826-4062-a43d-e
State: [1] Stable
Last error: No error
Writer name: 'SPSearch VSS Writer'
Writer Id: {57af97e4-4a76-4ace-a756-d
Writer Instance Id: {61f1c09f-5752-4ede-90a3-2
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d
Writer Instance Id: {e5c828ba-29f4-4b84-af08-d
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7
Writer Instance Id: {63a56723-e903-43d7-a676-9
State: [1] Stable
Last error: No error
Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-c
Writer Instance Id: {bae802d8-4c39-45e8-9b2a-1
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6
Writer Instance Id: {dd91915d-2808-473c-a935-1
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3
Writer Instance Id: {86615212-cb35-4bc1-8d1b-b
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6
Writer Instance Id: {0a52a170-4cc6-47e4-a378-e
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f
Writer Instance Id: {2ec690db-9d5b-4d21-aad4-c
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4
Writer Instance Id: {8bf227f7-c2dc-46f9-8bcd-2
State: [1] Stable
Last error: No error
They previously used Storagecraft Backup before we took over however we preferred to use the build in tools. Could it be that the missing VSS writers (exchange in particular) has meant that the logs are not being cleared up until the last known full backup?
Could Storagecraft have removed the built in writers and used it's own?
How would we repair/replace the missing writers?
The Exchange Server 2007 is only on SP1 build level but the Exchange aware issue mentioned here did not affect SBS 2008:
http://blogs.technet.com/b/exchange/archive/2008/06/18/3405615.aspx
We are hesitant to install the latest SP's and RU's given there are writers missing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.symantec.com/business/support/index?page=content&id=TECH143084