Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Interaction with vSphere Virtual Environment > Impact of Snapshot Operations > Snapshot Open

Snapshot Open

Previous page Next page Print this Topic

Table of contents

Simply having a snapshot open for a running VM involves some performance penalty on the VM, the ESX(i) host and the underlying storage. The host has to track the I/O, split writes to the snapshot file, update the snapshot file metadata. This extra overhead, in turn, impacts the host (primarily, with slower I/O).

This is generally most notable for VMs with significant write load, and has less impact on read performance.

From a storage perspective, VMs running with an open snapshot require the additional space to store the snapshot data, and additional I/O load on the datastore. Once again, this is generally more noted on systems with significant write I/O load.


Also, remember that vMotion cannot be performed for VMs with an open snapshot.

Table of contents