Skip to content
Download a free 30-day trial

BA720: Selected VSS Writer does not exist

Error code Product Applies to
BA720 BackupAssist ER BackupAssist ER v1 and later

Description

This error is usually generated when performing a VSS backup of a VSS-Aware application (such as Exchange, SQL or Hyper-V). The reason for the error is the VSS writer for the application trying to be backed up, is not accessible to BackupAssist ER.

The specific writer can be viewed by mousing over the top of the error within your backup report.

Resolution

The following are solutions for common VSS component problems. Review the list for solutions to the error you have encountered.

If you mouse-over the error, it will show you the VSS writer that generated the error and help isolate the cause.

Resolution 1 – Perform a reboot of the system

Rebooting the system resolves this warning as it refreshes all VSS components and allows any issues with the VSS writers to be refreshed which should remove any errors as well.

Resolution 2 – Check the backup selections

An error can occur if a component within a VSS application which is being backed up has been moved or deleted. E.g. An SQL database has been moved to another system or a Hyper-V guest has been deleted as it’s no longer required.

If this is the case then you need to refresh the backup selections within your backup job. You can deselect the selections which can't be accessed / found which will then remove the error.

To update or review a backup job:

  1. Open BackupAssist ER.

  2. Select the Jobs tab.

  3. Select the backup job that you want to modify from the list of jobs.

    How to modify a backup job

  4. Click the Edit button on the top menu.

  5. Select the tab containing the information or selection you want to change.

  6. Make the required update.

    Selecting the option when modify a backup job

  7. Click the Save button.

Resolution 3 – For Hyper-V guests

When troubleshooting problems with Hyper-V backups, it is important to first determine which guest/s is causing the error. You can do this by checking the Hyper-V VMSS logs, as shown below. You may also be able to identify the guest from the information in the backup report. If you are unable to identify the guest, try backing up the guests one at a time until the errant guest is found. Once it is identified, try a VSS backup on the guest itself using a trial version of BackupAssist ER. The success or failure of this backup will help to further narrow down what could be causing the error at the host level.

To view the Hyper-V VMMS logs:

  1. Click the Start button.
  2. Click Control Panel.
  3. Click System and Maintenance.
  4. Click Administrative Tools.
  5. Double-click Event Viewer.
  6. In the left hand navigation window, browse to Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS.

Resolution 4 – Check Event Viewer for more information

If there is an issue with the hardware, VSS or the operating system, Windows will usually provide entries about this issue in the Event Viewer. These entries can be used to gather more information and help resolve the error.

To use the Event Viewer

  1. Open Windows search and type Event viewer
  2. Select Event Viewer.
  3. Expand the Windows logs. You will specifically want to look at the Application and System logs.
  4. Check to see if there are any specific warnings or errors that apply to your issue and the time it may have occurred.
  5. Review the contents of the error or warning for information that may help resolve the issue.

Check for any VSS related errors or warnings being generated by the system. Resolving these should in turn resolve the backup error.

Resolution 5 – If a VSS Writer is Missing

Run the following command through a command prompt window (start > run > cmd):

vssadmin list writers

Next look for a VSS writer from the output that refers to the application mentioned when you scroll over the error in the backup report. If there is no writer listed, you may need to enable the service for the required writer in Services (Administrative tools > Services), or re-install the VSS writer's application.

For a Sharepoint VSS Writer - When you mouseover the error on the backup report, you see the GUID 35500004-0201-0000-0000-000000000000. Check the service Sharepoint 2010 VSS Writer under Administrative Tools > Services is started. This is the service which runs this VSS writer.

For a SQL VSS Writer - When you mouseover the error on the backup report, you see SQL Writer. Check the service SQL VSS Writer under Administrative Tools > Services is started, as this is the service which runs this VSS writer specifically.

Last updated Created Further assistance
10th Jul 2015 10th Feb 2009 BackupAssist ER Support page
Download a free 30-day trial