Hello, friend!
In this case, we can discuss the create VM snapshot issue.
Issue description
Snapshot performance + lotus Domino cpu consuming |
Reason
VM disk almost consumed |
Summary
You can check carefully the below snapshot limitation:
Usage Requirements
If actual available space on the data store used by the VM for which a snapshot is being created is less than 10%, stop the snapshot creation operation. To create a snapshot for a VM, the data store used by the VM must have sufficient storage space. If the datastore space is insufficient, you can use the following methods to handle this issue:
If the data store is created on virtualized SAN storage, follow operations described in Expanding Capacity for a Data Store (Provided by a Virtualized SAN Device) to expand data store capacity.
If VMs that use the data store can be migrated, follow the operations described in Migrating Disks on a Data Store to migrate disks of some VMs to other data stores.
If the data store is created on local hard disks, delete unused disks on the data store.
Multiple snapshots can be created for one VM. If a VM is being restored using a snapshot, other snapshots of the VM are not affected.
A maximum of 32 snapshots can be created for one VM. Created snapshots can only be manually deleted.
Snapshots can be created only for VMs that use storage whose type is Advanced SAN, FusionStorage, Local VIMS, VIMS, or NAS.
Snapshots cannot be created for VMs that use storage whose type is a local disk, SAN, or local RAM disk. The VM snapshot does not contain content in the VM disks.
If a shared disk is attached to a VM, memory snapshots, consistency snapshots, and quiescent VM file system snapshots cannot be created for the VM. The common snapshot created for the VM does not contain data on the shared disk.
If Not taken into snapshots is set for a disk, the disk will not be backed up when a snapshot is taken for the VM where the disk is located.
Memory snapshots can be created for a VM in the hibernating state, and common snapshots can be created for a VM in the stopped state.
If a memory snapshot is taken for a running VM during VM snapshot creation, the memory snapshot stores the VM disk data at that time. If a memory snapshot is not taken for a running VM during VM snapshot creation, the disk data in the VM snapshot may be inconsistent with the disk data on the VM at that time.
After a snapshot is taken for a VM, the created delta disks will occupy the storage resources in the data store. Therefore, you are advised to limit the number of snapshots to be taken to prevent storage resource shortage.
Do not perform any operation on a VM when a snapshot is being created for the VM.
When you create snapshots for a running VM, the VM will be paused and you cannot perform any operation on the VM. You can use the following formula to calculate the duration when the VM is paused: VM pause duration (in seconds) = [0.1 x VM disk size (in TB) + 0.6]. If snapshots need to be created for more than one disk of the VM, the total VM pause duration equals to the sum of the pause duration for each VM disk. For example, snapshots need to be created for 11 VM disks that consist of one 64 TB disk and ten 10 GB disks. Then, the VM pause duration is about 13 seconds. The pause duration for the 64 TB VM disk is about 7seconds (0.1 x 64 + 0.6). The pause duration for a 10 GB VM disk is about 0.6 seconds.
Do not perform any operation that is related to the memory snapshot of the VM when one of the following tasks are in progress:
Live migrating the VM
Upgrading Tools
Adding CPUs when the VM is in the running state
Restarting, hibernating, or stopping the VM
A snapshot can be created for only one VM on a host at a time.
A consistency snapshot can be created only when the following conditions are met:
The VM does not have a shared disk attached.
The VM disk type is Local VIMS, VIMS, FusionStorage, or NAS.
The VM OS is Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2.
To online create a snapshot for a VM, ensure that the number of VM CPU cores is less than or equal to 64. For a Linux VM, the number of CPU cores must be less than or equal to 32. Due to guest OS reasons, greater than 32 CPU cores for a Linux VM will lead to snapshot creation failure with high probability.
For the Lotus Domino CPU usage, I recommend checking with the related vendor as this layer can not be analyzed from the Huawei side,
For the disk expanstion you can check below how to expand the disk:
Expand Capacity of a Disk
Expand the capacity of a disk on a VM when required. You can expand the disk capacity of a VM only when the following requirements are met:
The virtual data store or FusionStorage is used.
No snapshots have been created for the disk. If any snapshots have been created for the disk, delete the snapshots before expanding the disk capacity.
The disk is not the system disk of a linked clone.
For a VM in the FusionCompute hypervisor, the capacity of the VM disk to be expanded is greater than or equal to 4 GB.
You cannot expand the disk capacity when the VM is running if the disk is created on NAS storage and the disk is in common configuration mode.
If the VM is in the FusionCompute hypervisor, you can expand the disk capacity of a VM when the VM is in the Stopped or Running state. If the VM is in the other hypervisor, you can expand the disk capacity of a VM only when the VM is in the Stopped state.
Choose VM Management > Disks, locate the row that contains the target disk, click More, and select Expand Capacity.
Determine the VM scenario and make capacity expansion take effect.
If the VM is in the following scenario, restart the VM:
a. The VM is in the Running state.
b. The disk is created on a Local Pome, LUN Pome, or NAS storage.
c. The VM does not run one of the following OSs:
Windows Server 2003
Windows Server 2008
Windows XP
Windows 7
If the VM is in the following scenario, power cycle the VM:
a. The VM is in the Running state.
b. The disk is created on FusionStorage.
The VM OS recognizes newly expanded disk capacity as an unallocated partition. Therefore, you need to merge the partition or create a partition to identify the expanded disk capacity. For detailed operation methods, search from the Internet or Forum.
Setting the I/O Upper Limit of a Disk
Configure the input/output (I/O) upper limit for a disk to prevent that the disk deteriorates the performance of other VMs due to excessive I/O. If the I/O upper limit is set to a low value, the VM may respond slowly or even cannot get started.
You can configure the I/O upper limit only when the VM is in the Running, Stopped, or Hibernated state. VRM VMs in the FusionCompute hypervisor and VMs created in the VMware hypervisor do not support this operation.
Choose VM Management > Disks, locate the row that contains the target disk, click More, and select Set I/O Upper Limit.
That's all, thanks!
