Download the latest release: VSSTester.ps1
Trace while using a third-party backup solution
.\VSSTester -TraceOnly -DatabaseName "Mailbox Database 1637196748"
Enables tracing of the specified database. The user may then attempt a backup of that database and use Ctrl-C to stop data collection after the backup attempt completes.
Trace a snapshot using the DiskShadow tool
.\VSSTester -DiskShadow -DatabaseName "Mailbox Database 1637196748" -ExposeSnapshotsOnDriveLetters M, N
Enables tracing and then uses DiskShadow to snapshot the specified database. If the database and logs are on the same drive, the snapshot is exposed as M: drive. If they are on separate drives, the snapshots are exposed as M: and N:. The user is prompted to stop data collection and should typically wait until log truncation has occurred before doing so, so that the truncation is traced.
Trace a snapshot using the DiskShadow tool by volume instead of by Database
.\VSSTester -DiskShadow -VolumesToBackup D:\, E:\ -ExposeSnapshotsOnDriveLetters M, N
Enables tracing and then uses DiskShadow to snapshot the specified volumes. To see a list of available
volumes, including mount points, pass an invalid volume name, such as
-VolumesToBackup foo. The error
will show the available volumes. Volume names must be typed exactly as shown in that output.
Trace in circular mode until the Microsoft Exchange Writer fails
.\VSSTester -WaitForWriterFailure -DatabaseName "Mailbox Database 1637196748"
Enables circular tracing of the specified database, and then polls "vssadmin list writers" once per minute. When the writer is no longer present, indicating a failure, tracing is stopped automatically.
Note that script syntax and output has changed. Syntax and screenshots in the above articles are out of date.
Missing Microsoft Exchange Writer
We have seen a few cases where the Microsoft Exchange Writer will disappear after an unspecified amount of time and restarting the Microsoft Exchange Replication service. Steps on how to resolve this are linked here:
Here are the steps to verify that the local Administrators group is allowed to the COM+ Security on the computer. The script will detect if this is a possibility if we can not see the Exchange Writers and we have the registry settings set that determine this is a possibility.
- Run "dcomCnFg" from the run box or command prompt on the problem machine
- Expand Component Services then Computers
- Right Click on My Computer and select Properties
- Select the COM Security tab and select Edit Default... under Access Permissions
- If the local Administrators group is not here for Allow for Local and Remote Access, click Add... to add the local Administrators group to the Default Security permissions
- Change the locations to the computer name
- Type in "Administrators" and select Check Names. Making sure the computer account comes up
- Add Local Access and Remote Access for Allow
- Click Okay
- Click Apply and Okay
- Restart the Computer