#1 Global Leader in Data Resilience

“Storage connection failure” alarm during backup/restore operation involving Storage Snapshot.

KB ID: 2433
Product: Veeam ONE | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3
Published: 2018-01-18
Last Modified: 2021-08-13
mailbox
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

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

The alarm “Storage connection failure” is displayed in Veeam ONE when performing either of the following activities in Veeam Backup & Replication:

Backup from Storage Snapshots

Restore from Storage Snapshots

While both Backup from Storage Snapshots and Restore from Storage Snapshots both involve interactions with Storage Snapshot, they each trigger this alarm for a different reason. The Cause and Solution sections of this article discuss each interaction type separately. 

Cause

Veeam ONE tracks the events that occur in the VMware Environment to determine what alarms should be displayed. Veeam ONE triggers the "Storage connection failure" alarm when the following events occurs within the VMware Environment.
vprob.storage.connectivity.lost
esx.problem.storage.connectivity.lost

Backup from Storage Snapshots

In an environment where an initiator/storage group consists of both the ESXi hosts and the Veeam Backup Proxies, Veeam will use the existing initiator/storage group instead of creating a new group. This causes the storage snapshot that is exported to the proxy to become visible to the ESXi hosts. When the job completes, the storage snapshot is then unexported and deleted. During this time, the ESXi hosts see the storage snapshot (it isn’t mounted), and when the storage snapshot suddenly disappears triggers the event in VMware which in turn triggers the alarm in Veeam ONE.

Restore from Storage Snapshots

During the restore operation, a clone of the selected storage snapshot is created and mounted to the user-selected ESXi host as a new volume. Once the restore is completed, Veeam Backup & Replication issues a command to the storage system. The storage system deletes the snapshot copy from the ESXi host and performs cleanup operations. This removal of the storage is what causes ESXi to trigger the event which in turn triggers Veeam ONE to display the alarm.

Solution

Backup from Storage Snapshots

To prevent the ESXi hosts from seeing the Storage Snapshots that are exported to the Veeam Backup Proxy, it is advisable to create a separate initiator group for backup proxies only.

Restore from Storage Snapshots

As the alarm triggered within Veeam ONE is related to an event within the VMware environment, the only way to prevent the alarm in Veeam ONE from triggering is to schedule alarm suppression when a restore occurs.

See more details of how to suppress the alarms.

More Information

Should you have any questions, contact Veeam Support.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.