{"id":2474,"date":"2013-11-15T08:26:29","date_gmt":"2013-11-14T22:26:29","guid":{"rendered":"http:\/\/support.cybersecure.com\/?p=2474"},"modified":"2016-06-06T12:05:12","modified_gmt":"2016-06-06T02:05:12","slug":"the-writer-failed-due-to-an-error-that-would-likely-not-occur-if-the-entire-backup-restore-or-shadow-copy-creation-process-was-restarted-vss_e_writererror_retryable","status":"publish","type":"post","link":"http:\/\/support.cybersecure.com\/?p=2474","title":{"rendered":"The writer failed due to an error that would likely not occur if the entire backup, restore, or shadow copy creation process was restarted. (VSS_E_WRITERERROR_RETRYABLE)"},"content":{"rendered":"

Error<\/h2>\n

The writer failed due to an error that would likely not occur if the entire backup, restore, or shadow copy creation process was restarted. (VSS_E_WRITERERROR_RETRYABLE)<\/span><\/p>\n

Cause<\/h2>\n

This is most often caused by the Microsoft Exchange information store VSS writer being in an unstable state.<\/p>\n

Resolution<\/h2>\n
    \n
  1. Check the exchange backup schedule is set to the recommended settings<\/a><\/li>\n
  2. Check the event viewer<\/a> for any hardware, exchange or resource (lack of RAM or paging file) issues.<\/li>\n
  3. Restart the Microsoft Exchange Information Store service.<\/li>\n
  4. Run “vssadmin list writers” – each writer should now report “State: stable” and “Last error: no error”<\/li>\n
  5. Try the backup again<\/li>\n<\/ol>\n

    Note: the exchange VSS writer going regularly into an unstable state could mean underlying hardware, driver or resource issues.<\/p>\n

    We have seen this issue on machines that are memory overloaded and\/or have very slow disk configurations, to properly resolve the issue: a) more RAM should be added to the machine and b) faster disk configuration should be upgraded on the machine.<\/p>\n

    Further reading<\/h2>\n