Hello Murilo, In ACS we have two concepts.
Volume snapshots, which are restore points that represent a point in time for a given volume. These type of snapshots can be scheduled to be taken. Moreover, in ACS, volume snapshots behave as "backups", as they are "backed up" to the secondary storage. In addition to that, with PR https://github.com/apache/cloudstack/pull/7659, we will be able to use multiple different secondary storage systems, and define what type of data they store, such as backups of snapshots, ISOs, templates, and so on. The backup behavior of snapshots depends on the parameter "snapshot.backup.to.secondary". In contrast, a "VM snapshot" may include additional information, such as memory and CPU states. Also, it will store all volumes attached to that VM, instead of just one. These are not backed up, and when using them, one cannot use volume snapshots. Besides that, this kind of snapshot limits some features available for the VM. the following operations are blocked as long as there are VM snapshots for the VM: - attach/detach volume - attach/detach VM to/from network - volume resize - changing offering - creating volume snapshots - volume migration - VM storage migration - VM scale - VM reset Regards, Gabriel
