Running Memory Machine Services

Memory Machine data services must be running to enable PMEM management, snapshot operations, and connection to the Memory Machine Management Center (M3C).

The Distributed Persistent Memory Engine (DPME) and the snapshot services, mvsnapd and mvcsnapd, must be started after Memory Machine is installed and should be configured to start automatically on host restart. See Starting Data Services.

Important: Do not confuse the mvsnapd and mvcsnapd services. The mvsnapd service is Memory Machine's standalone snapshot service. The mvcsnapd service is the multi-node snapshot service. (Think of the added "c" as standing for "cluster".)

You might also be required to restart some or all of these services for maintenance or troubleshooting.

Since DPME is the heart of Memory Machine, it is documented thoroughly elsewhere in this guide. See Using the Distributed Persistent Memory Engine. To understand how DPME works and what it does, see The Distributed Persistent Memory Engine. For more in-depth information about how to use DPME to initialize memory and run applications, see Initializing Direct Access Devices.


The Memory Machine management services, M3C (mmctl) and Memory Machine Agent (mmagent), start automatically after installation and on host restart.

M3C runs on one host. Memory Machine Agent must run on all data hosts sharing a multi-host license.