Backup for Files - How to Enable the Microsoft Exchange VSS Writer

Written By Tami Sutcliffe (Super Administrator)

Updated at March 31st, 2021

Situation:

The Exchange VSS writer is responsible for flushing Exchange transaction logs at the end of a successful backup. If transaction logs are not being flushed after a completely successful backup, follow this procedure to ensure that the Exchange VSS Writer is enabled.

Instructions:

Caution: If you turn on the Exchange writer, the Microsoft Windows Backup utility cannot back up the Exchange information store and the system state at the same time.

Turn on the Exchange writer only if you use a third-party backup solution, or if you want to back up the Exchange information store separately.

Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system.

We cannot guarantee that you or anyone else can solve problems that result from you using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then double-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

3. Double-click the Disable Exchange Writer value.

4. In the Value data text box, change the value from 1 to 0, and then click OK.

5. Quit Registry Editor.

6. Click Start, point to Administrative Tools, and then click Services.

7. Stop and then restart the Microsoft Exchange Information Store service.

Microsoft Windows Server 2003 uses the Volume Shadow Copy service to back up open files. The Volume Shadow Copy service uses a writer component to back up files and settings that are specific to a program, such as Microsoft SQL Server 2000 or Microsoft Exchange Server 2003. The writer component tells the Volume Shadow Copy service which files to back up and then pauses corresponding services while the backup is in progress.

Additional Information:

Information contained herein is related Microsoft KB838183 to view this article in full please visit: http://support.microsoft.com/kb/838183/en-us