Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Snapshots of VMs with an incorrect date are not deleted by alert management actions

Snapshots of VMs with an incorrect date are not deleted by alert management actions

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,233 Votes: 0 Revisions: 10

Overview

 

The Delete Snapshot alert trigger management action does not delete snapshots of Hyper-V VMs. The issue can occur for more than one Hyper-V VM on the same host.

Environment

NPM on Hyper-V

Cause

The snapshots of the affected VMs are displayed with an incorrect creation date in the list of snapshots in the Delete Snapshots dialog.

Resolution


When a virtual machine snapshot is created in a Hyper-V environment, the creation date of the snapshot is saved incorrectly. This is a known issue with Hyper-V.

If a virtual machine contains a snapshot with a creation date that is lower than the minimum SqlDateTime value (January 1, 1753), the date is considered invalid, and the Delete Snapshot action by design does not delete the snapshot.

For more information, see the Hyper-V documentation and the Microsoft Technet forums.

Last modified

Tags

Classifications

Public