- Knowledge Base Listing Page
- SAN snapshots on HP Store Virtual P4500 left behind after backup failures
SAN snapshots on HP Store Virtual P4500 left behind after backup failures
| KB ID: | 1957 |
| Product: | Veeam Backup & Replication |
| Version: | 7.x 8.x |
| Published: | 2014-11-17 |
| Last Modified: | 2020-08-13 |
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.