We all know that if the production of a virtual machine with a snapshot of the consequences of running, not only the performance of the virtual machine is affected, but also lead to loss of control of storage space, when the snapshot is too large, delete (accurately should be called merger) snapshot crises Since the disk IO is too large, the business will Caton, the business may choose to shut down or busy time of the operation; in addition to man-made virtual machine snapshot of the virtual machine will be a snapshot, there are a lot of task or operating system needs to generate a snapshot , such as cloning boot a virtual machine, the virtual machine backup software to back up, of course, if these actions or tasks running, the snapshot will be removed before the end of the task, but if you do not perform well, they will unknowingly leave VM snapshots, snapshot can be said to be very hard to detect.
So there is no good way to know which virtual machine with a snapshot of it? It really is not easy, especially in vCenter 6.7 interface, each virtual machine can only seem to find, if you have 200 virtual machines, I'm afraid to implement time-consuming; some people would say, if the virtual machine has snapshots, vRealize Operations alarm will be prompted, but brothers, not everyone is wealthy, deployed Operations, then there is no way to understand a simple snapshot of the virtual machine it? Here I will give an environment in vSphere 6.7, to solve this problem by configuring the alarm.
6.7 vCenter open interface, the following operations to create a new alarm:
Select monitoring parameters for the "virtual machine snapshot size"
Configuration snapshot space exceeds 1GB yellow alarm is issued, 1GB is the minimum
Click "Repeat rule"
If more than 3GB, red warning is issued
This alarm create a good snapshot of the virtual machine to borrow up!
Of course, if the virtual machine snapshot space is less than 1GB, it will not trigger an alarm, it is not found by this method in less than a snapshot of the virtual machine's 1GB, but because if a virtual machine runs continuously, so that the snapshot space will continue to increase, it is easy to more than 1GB, so this method can still be found indirectly virtual machines with snapshots, snapshot occupies space in a very early age, you can take the necessary measures; the startup configuration of alarm thresholds 1GB and 3GB, you can refer to be configuration.
