Home
Overview and Installation
Getting started with MemVerge Memory Machine requries that you understand some background information about how persistent memory works. You can then install Memory Machine on a server and begin monitoring memory usage and capturing application snapshots.
Introduction to MemVerge Memory Machine
MemVerge Memory Machine (Memory Machine) enables applications to expand from volatile memory (DRAM) into persistent memory (PMEM).
Understanding Snapshots
A snapshot is a static image of a running application's process tree. You can use Memory Machine ZeroIO Snapshot to almost instantly capture a snapshot, then later just as quickly restore the running process to the state captured in the snapshot.

Overview and Installation
Getting started with MemVerge Memory Machine requries that you understand some background information about how persistent memory works. You can then install Memory Machine on a server and begin monitoring memory usage and capturing application snapshots.
- Introduction to MemVerge Memory Machine
  MemVerge Memory Machine (Memory Machine) enables applications to expand from volatile memory (DRAM) into persistent memory (PMEM).
  - Introduction to PMEM
    Using volatile memory (DRAM) and persistent memory (PMEM) in combination enables applications to expand memory capacity relatively cheaply and to persist memory data objects, a capability that previously was only possible by writing to storage devices.
  - Transparent Memory Service
    The Transparent Memory Service (TMS) intercepts Linux glibc.so function calls and reroutes them to the Distributed Persistent Memory Engine (DPME), which manages the MemVerge PMEM store.
  - Differences Between Memory Machine Editions
    Memory Machine is available in two editions, Standard Edition for managing memory on individual hosts and Advanced Edition for managing clusters of hosts at the enterprise level.
  - The Distributed Persistent Memory Engine
    MemVerge Distributed Persistent Memory Engine (DPME) is at the heart of Memory Machine. DPME manages memory allocation to volatile memory (DRAM) and persistent memory (PMEM) for all applications run under Memory Machine.
  - The Control Path Service
    The Control Path Service (CPS) is a management service (as opposed to a data service) that manages aspects of Memory Machine not having to do with data.
  - Understanding Snapshots
    A snapshot is a static image of a running application's process tree. You can use Memory Machine ZeroIO Snapshot to almost instantly capture a snapshot, then later just as quickly restore the running process to the state captured in the snapshot.
- Getting Started with Memory Machine
  You run Memory Machine on a host equipped with one or more PMEM devices.
Using the Memory Machine Dashboard
You can view system resources and performance metrics, and create and restore snapshots in MemVerge Memory Machine using the Memory Machine Dashboard, a web UI application running on one of the installed hosts.
Using the Command Line Interface
You can administer and use MemVerge Memory Machine using the Command Line Interface (CLI) on any installed host.
Working with Applications
MemVerge provides additional instructions for some popular applications supported by Memory Machine, either to assist with complex setup or to support additional functionality.

Understanding Snapshots

A snapshot is a static image of a running application's process tree. You can use Memory Machine ZeroIO Snapshot to almost instantly capture a snapshot, then later just as quickly restore the running process to the state captured in the snapshot.

Restriction: ZeroIO Snapshot is available only in Memory Machine Advanced Edition.

When you use ZeroIO Snapshot to create a snapshot, Memory Machine takes these steps:

Attaches to the application
Flushes any application data in the DRAM tier to PMEM
Freezes the application
Copies a small subset of the application data (metadata) to a local or mapped storage device

Since the application data in PMEM does not need to be written to another persistent store, the Memory Machine process is much faster than an application-capture process that writes the entire snapshot to traditional storage media.

A running application has a unique process ID (PID) within the host's runtime system. This PID is stored with other metadata when a snapshot is captured. When the snapshot is restored, it runs under its original PID.

The ability to take a fast snapshot of a large application enables a number of valuable features, including:

Periodic backup of partially completed work
Crash-tolerant database recovery
Exporting and importing in-process application instances
Cloning in-process application instances