Home
Using the Command Line Interface
You can administer and use MemVerge Memory Machine using the Command Line Interface (CLI) on any installed host.
Using Snapshots in the Memory Machine CLI
Use the mvmcli command from the CLI on a Memory Machine host to capture the state of a running process, then later restore the running process to the state captured in the snapshot.
Using Snapshots in Memory Machine
Capturing a snapshot is almost instantaneous, requiring only that a small amount of metadata be saved to a storage device.
Preparing a System for Snapshots
Snapshots can be captured on a host on which Memory Machine is properly configured and the data service is running.

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.
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.
- MemVerge Memory Machine Administration
  MemVerge Memory Machine can be installed and run using CLI commands.
- Using Snapshots in the Memory Machine CLI
  Use the mvmcli command from the CLI on a Memory Machine host to capture the state of a running process, then later restore the running process to the state captured in the snapshot.
  - Using Snapshots in Memory Machine
    Capturing a snapshot is almost instantaneous, requiring only that a small amount of metadata be saved to a storage device.
    - Preparing a System for Snapshots
      Snapshots can be captured on a host on which Memory Machine is properly configured and the data service is running.
    - Snapshot Dependencies
      Capturing or restoring a snapshot with an established IP connection requires the iptables-utils package. MemVerge recommends installing iptables-utils on any data server on which ZeroIO Snapshot is used.
    - Capturing a Snapshot with CLI
      Capture snapshots of a running application with the Memory Machine CLI utility, mvmcli.
    - Listing Snapshots
      List snapshots using the mvmcli snapshot list command.
    - Restoring Snapshot Images
      Restore a snapshotted application image with the Memory Machine CLI utility, mvmcli.
    - Removing Snapshots
      Remove snapshots with the mvmcli snapshot rm command.
    - Copying Snapshots
      You can export and import snapshots – copy them to conventional storage and back into PMEM – using the mvmcli command. See oxy_ex-3/topics/t_mvmm_copying_a_snapshot_to_the_same_host.html. You can also clone an instance, creating an exact duplicate that can be run concurrently with the original process. See oxy_ex-3/topics/t_mvmm_cloning_an_instance.html.
- Troubleshooting
- Preparing Intel Optane DC PMEM
  Prepare PMEM for use by configuring the Intel Optane DC Direct Access (DAX) devices in AppDirect AppDirect mode.
- Preparing to Run an Application
  Normally you run applications by using the mm wrapper script supplied with Memory Machine. See oxy_ex-3/topics/t_mvmm_running_an_application_with_mvmm.html. If you do not use the mm to run your application, you must set up the Memory Machine environment manually before running the application.
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.

Preparing a System for Snapshots

Snapshots can be captured on a host on which Memory Machine is properly configured and the data service is running.

ZeroIO Snapshot can be used to capture a snapshot of an application that is running in an environment for which:

The LD_PRELOAD environment variable contains the file path to the Transparent Memory Service (mvmalloc.so) file.
The MVMALLOC_CONFIG environment variable contains the file path to the Memory Machine configuration file (mvmalloc.yml).
The DPME is running. See Starting the Distributed Persistent Memory Engine.
The mvnsnapd service is running. See Running Memory Machine Services.
Sufficient free PMEM exists to contain the application's in-memory data. This can be a relatively small amount if a previous snapshot of the process already exists.