Forum Discussion
- crileyModerator
I see this problem with SSR 2013 listed in articles with a hotfix, but nowhere do I find anything on VSR 2016.
Generally speaking, any fix for a previous version will automatically be included in future releases. Without checking I cannot be sure, but the fix should already be in VSR 16.
When you see the issue, run VSSADMIN LIST WRITERS from a command prompt to confirm the status of all writers. Also run a test using DiskShadow (for this test, backup exact same volumes that you are backing up with VSR) and check the results: http://www.veritas.com/docs/000097851.
Related Content
- 10 years ago