https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTU3IiwiaGFzaCI6IjBhOWJkNDYzLTg2ZDYtNGJhZC1iNmVhLTZlYTg4YjBhOThlMiJ9
SAN snapshots on HP Store Virtual P4500 left behind after backup failures
Challenge
The Veeam backup job fails but the SAN snapshot on HP Store Virtual is still created and left behind.
On the proxy you may see in the event logs 2 events, one after another: first VSS event 8229 about VSS writer failure and then event 284 from HP StoreVirtual VSS Provider about successful snapshot creation.
On the proxy you may see in the event logs 2 events, one after another: first VSS event 8229 about VSS writer failure and then event 284 from HP StoreVirtual VSS Provider about successful snapshot creation.
Cause
This happens due to incorrect behavior of HP StoreVirtual VSS Provider: in some cases it still creates and keeps a snapshot even after VSS writer failure.
Veeam always creates snapshots with the default attribute "auto release" which means that shadow copy is automatically deleted when the shadow copy requester process ends. But neither VSS subsystem, nor Veeam would know if the snapshot was created by provider after the VSS writer failure, because we send all requests about snapshot status to VSS writer. So this is impossible to track from Veeam’s side.
Veeam always creates snapshots with the default attribute "auto release" which means that shadow copy is automatically deleted when the shadow copy requester process ends. But neither VSS subsystem, nor Veeam would know if the snapshot was created by provider after the VSS writer failure, because we send all requests about snapshot status to VSS writer. So this is impossible to track from Veeam’s side.
Solution
If you see such behavior, please open a case with HP support.
KB ID:
1957
Product:
Veeam Backup & Replication
Version:
7.x 8.x
Published:
2014-11-17
Last Modified:
2020-08-13
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
