Article Number: 000130945
PowerStore Alerts: Scheduled Snap Alerts
Summary: PowerStore Scheduled Snap alerts occured due to Internal errors, No free slot for creation, Supported only for VM’s which are vVol based, Insufficient available space on the virtual machine, Snapshot Limit Reached, The system is busy, Data Path failed and limits reached issues. ...
Article Content
Symptoms
When Dell PowerStore encounters a problem, an error alert is generated to help identify the issue. This article explains the different possible causes and the relevant solutions for these error alerts. If your problem is not resolved despite the solution provided, check the technical support contact options.
Note: Cannot find the information you need? Let us know via the feedback form at the bottom of this article.
Note: Cannot find the information you need? Let us know via the feedback form at the bottom of this article.
Cause
Cause for respective alerts has been updated in the Resolution section.
Resolution
| Alert ID | POLICY_SCHEDULED_SNAP_CLEANUP_FOR_VIRTUAL_MACHINE_FAILED |
| Alert Text | Expired virtual machine snapshot(s) cleanup failed with error %(error_message_key) |
| Error Code | (0x00906D01) |
| Description | Removal of an expired scheduled virtual machine snapshots failed. |
| Resolution | Cause Internal errors detected: One or more internal errors detected while deleting expired virtual machine snapshot. Solution Virtual machine snapshot deletion is done by triggering corresponding operation in vCenter using its web Application Program Interface (API)
|
| Alert ID | POLICY_SNAP_REMOVING_FOR_VIRTUAL_MACHINE_FAILED |
| Alert Text | Removing the closest expiring snapshot %(snap_name) for vm %(source_name) failed with error %(error_message_key) |
| Error Code | (0x00906C01) |
| Description | Removal of a scheduled virtual machine snapshot failed. |
| Resolution | Cause Internal errors detected: One or more internal errors detected while deleting scheduled virtual machine snapshot. Solution Virtual machine snapshot deletion is done by triggering corresponding operation in vCenter using its web Application Program Interface (API).
|
| Alert ID | POLICY_SCHEDULED_SNAP_CREATION_FROM_VIRTUAL_MACHINE_NO_SLOT_FOR_SCHEDULED_SNAPSHOT |
| Alert Text | Skipping creation of scheduled snapshot from virtual machine %(source_name) because there is no free slot for scheduled snapshot |
| Error Code | (0x00906B04) |
| Description | Creation of a scheduled virtual machine snapshot failed. |
| Resolution | Cause No free slot for creation: Scheduler system detected that there is no free slot for creation the next scheduled virtual machine snapshot. It means that all the virtual machine snapshots in current hierarchy are created by the user. Scheduler system is unable to free the slot for creation the next scheduled snapshot. Solution To continue creation of scheduled virtual machine snapshots there must be at least one free slot. Manually deletion of user created snapshot will free slot for scheduler system and will allow the scheduler to create the snapshot. Another way to recover from this alert is to remove and create a new protection policy from the corresponding virtual machine. Note: all existing snapshots will not be impacted after removing the protection policy. |
| Alert ID | POLICY_SCHEDULED_SNAP_CREATION_FROM_VIRTUAL_MACHINE_NOT_VVOL_DISK_DETECTED |
| Alert Text | Skipping creation of scheduled snapshot from virtual machine %(source_name) because there is no free slot for scheduled snapshot. |
| Error Code | (0x00906B03) |
| Description | Creation of a scheduled virtual machine snapshot failed. |
| Resolution | Cause Supported only for VM’s which are vVol based: Creation of scheduled virtual machine snapshots is supported only for virtual machines which are vVol based. It means that virtual machine is created only on vVol storage containers and has only vVol based disks. Current virtual machine is not vVol based. Solution Ensure the virtual machine backed by the vVol storage and has only disks which are based on vVol storages. Removal of all non vVol based disks will allow scheduler to create next scheduled snapshot. Another way to recover this alert is to remove protection policy from the corresponding virtual machine. |
| Alert ID | POLICY_SCHEDULED_SNAP_CREATION_FROM_VIRTUAL_MACHINE_INSUFFICIENT_DISK_SPACE |
| Alert Text | Skipping creation of scheduled snapshot from virtual machine %(source_name) because there is no space for a snapshot |
| Error Code | (0x00906B05) |
| Description | Creation of a scheduled virtual machine snapshot failed |
| Resolution | Cause Insufficient available space on the virtual machine: Insufficient available space on the virtual machine storage for creation the next scheduled virtual machine snapshot. Solution
|
| Alert ID | POLICY_SCHEDULED_SNAP_CREATION_FROM_VIRTUAL_MACHINE_GENERIC_FAIL |
| Alert Text | Scheduled snap creation from %(source_name) using %(rule_name) failed with error %(error_message_key) |
| Error Code | (0x00906B07) |
| Description | Creation of a scheduled virtual machine snapshot failed |
| Resolution | Cause Internal errors detected: One or more internal errors detected while creation of scheduled virtual machine snapshot. Solution Virtual machine snapshot creation is done by triggering corresponding operation in vCenter using its web Application Program Interface (API).
5.a) In this case the following event will be raised: '0x00906B07 Creating a snapshot from <VM name> using the <snapshot rule name> rule failed with error: An internal error occurred in VM services. Contact your support provider'
5.b) Find the snapshots in VM snapshot list and delete them. On the screenshot below snapshot named 'rule0.IO0.2022-10-20T09:30:00Z 000000000' should be deleted. Select the snapshot and click 'Delete' button.
|
| Alert ID | POLICY_SCHEDULED_SNAP_CREATION_FROM_VOLUME_GROUP_FAILED POLICY_SCHEDULED_SNAP_CREATION_FROM_VOLUME_FAILED |
| Alert Text | Scheduled snapshot creation from %(source_name) using the %(rule_name) rule failed with error: %(error_message_key) |
| Error Code | (0x00906E01) (0x00906501) |
| Description | The user has a protection policy created which contains a snapshot rule that is executed on a chosen interval. That protection policy is applied to a Volume or Volume Group, which results in snapshots being taken of those storage resources. This alert informs the user that one or more of those snapshot operations has failed. |
| Resolution | Cause Snapshot Limit Reached: One of the snapshot limits has been reached. In the initial version of PowerStore the limitations are:
Solution Snapshots need to be deleted in order to get below the limit so that new snapshots can be created. |
| Alert ID | POLICY_SCHEDULED_SNAP_CLEANUP_FOR_VOLUME_GROUP_FAILED POLICY_SCHEDULED_SNAP_CLEANUP_FOR_VOLUME_FAILED |
| Alert Text | Expired snapshot %(snap_name) cleanup failed with error: %(error_message_key) |
| Error Code | (0x00906F01) (0x00906701) |
| Description | This alert reports that one or more snapshots failed to be deleted by the system. When a scheduled snapshot is created it is given an expiration time based on the requested 'retention' which is configured for the snapshot rule that is creating the snapshot. When that expiration time is reached the snapshot the system will attempty to automatically delete the snapshot. |
| Resolution 1 | Cause The system is busy: The system has an internal trashbin with a static size, and if that trashbin fills up and the system does not have the cycles to empty it, then its possible that deletion of a storage resource will fail. Solution Do nothing. The system will retry the delete of that storage resource later and it should succeed if the trashbin has the necessary space. |
| Resolution 2 | Cause Datapath failed to complete the bulk delete request: An internal error occurred within the system. Solution Do nothing. The system will retry the delete of that storage resource later. If the alert persists contact technical support. |
| Alert ID | POLICY_SCHEDULED_SNAP_APPLIANCE_LIMIT_REACHED |
| Alert Text | Scheduled snapshots were not created because the appliance limit of %(max_snaps_per_appliance) would have been exceeded |
| Error Code | (0x00907001) |
| Description | This alert is reported if one or more snapshot operations has failed because the appliance in question has reached its limit of snapshots and no additional snapshots can be created. |
| Resolution | Cause Limits reached: The system has a defined limit for the maximum number of snapshots allowed per appliance. Solution One or more of the following: 1. Manually delete snapshots 2. Lower the retention time on a snapshot rule so that snapshots will expire and be deleted more quickly. |
Article Properties
Affected Product
PowerStore
Last Published Date
05 May 2024
Version
6
Article Type
Solution