Snapshot Statuses
A snapshot has four possible values with respect to its persistence status: Incomplete, Created, Persisted and Error.
Snapshot Creation
A snapshot consists of two components that combine to represent the "frozen" process. The first component is the memory state data, which resides in PMem and is managed by the MemVerge Memory Allocation Service (MVMAS).
The second component can be thought of as metadata. This is all the data that isn't represented by the state of memory. This includes file descriptors, address space indexes, mount points, and more. The metadata resides in a conventional (non-PMem) file system. This can be a local drive, an NFS mount, or any other file system not managed by MVMAS.
- Metadata is copied to the Memory Machine data directory. See The Memory Machine Configuration File.
- Memory state data that is not yet in MVMAS-controlled PMem is flushed to PMem. This is typically data in the DRAM tier memory.
Snapshot Status Values
The following are possible statuses with respect to the snapshot creation process. See Snapshot Creation.
- Incomplete
- Metadata has been saved, but memory state data is missing. This can happen if PMem maintained by MVMAS is forcibly erased. It can also happen in the moment when a snapshot is being moved to a new host.
- Created
- The snapshot metadata is saved and the memory state data is complete but is still being flushed to PMem. The snapshot can be restored at this point, but if the server loses power (or is restarted), the snapshot is ruined.
- Persisted
- Metadata has been saved and memory state data is contained entirely in PMem managed by MVMAS. The snapshot can be restored and is safe from server power interruptions.
- Error
- This indicates an error when Memory Machine queries the state of the snapshot. For example, the connection to the MVMAS could be lost as the query is being sent. The snapshot is not necessarily lost, but it is not currently available.