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.
Getting Started with Memory Machine
You run Memory Machine on a host equipped with one or more PMEM devices.
Installing MemVerge Memory Machine
Install MemVerge Memory Machine (Memory Machine) data service on all hosts requiring memory management.
Initializing Direct Access Devices
To initialize the server's direct access (DAX) devices and start the Distributed Persistent Memory Engine (DPME) service, use the command mvmallocd <dax device> ... [--socket=<socket>] [--format_dax].

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).
- Getting Started with Memory Machine
  You run Memory Machine on a host equipped with one or more PMEM devices.
  - Hardware Recommendations
  - Network Recommendations
    For optimal performance and consistency throughout the Memory Machine System, MemVerge either requires or recommends specific values for open port numbers, communication protocols, and other network-related configurations.
  - Software Recommendations
    MemVerge recommends that you conform to software dependencies, such as operating systems and packages, that have been tested with MemVerge products.
  - Installing MemVerge Memory Machine
    Install MemVerge Memory Machine (Memory Machine) data service on all hosts requiring memory management.
    - Installing the Data Service
      Install the data service on every data host using the Memory Machine Package File.
    - Installing the Management Service
      Install the management service using the Memory Machine Package File.
    - Initializing Direct Access Devices
      To initialize the server's direct access (DAX) devices and start the Distributed Persistent Memory Engine (DPME) service, use the command mvmallocd <dax device> ... [--socket=<socket>] [--format_dax].
    - Installing a Single-Host License
      To install or update a single-host license, use the mvmcli license update command.
    - Uploading a License
      One host in your network runs a management service. See oxy_ex-3/topics/t_mvmm_installing_the_management_service.html. You must install at least one license using this management service in order to use Memory Machine.
    - Adding a User
      Authorize a user to use Memory Machine by adding the user to the mvmm group.
  - Configuration Files
    MemVerge Memory Machine uses several YAML-formatted configuration files. Two of these, mvmallocd.yml and mvmalloc.yml contain user-configurable parameters.
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.

Initializing Direct Access Devices

To initialize the server's direct access (DAX) devices and start the Distributed Persistent Memory Engine (DPME) service, use the command mvmallocd <dax device> ... [--socket=<socket>] [--format_dax].

Before you begin

Install MemVerge Memory Machine data service on the host. See Installing the Data Service.

About this task

Before you run DPME on a data host, you must initialize the host's DAX devices. During initialization DPME writes a signature to the DAX device.

Warning: Formatting the DAX devices deletes all data on the devices. Do this only on a new installation.

Note: This is the only case where you should run DPME directly from the command line. Normally DPME runs as a service. See Starting the Distributed Persistent Memory Engine.

Procedure

Edit the names of the DAX devices in the DPME configuration file, /etc/memverge/mvmallocd.yml, to reflect the DAX devices on the host. For example:
```
PMEM: /dev/dax1.0
PMEM: /dev/dax0.0
```
See The Distributed Persistent Memory Engine Configuration File.
Configure the DAX devices using the following command:

Warning: This command erases all of the data in the PMEM.
```
# /opt/memverge/sbin/mvmallocd --format_pmem --config=config-file
```
where:

--format_pmem

instructs DPME to format the DAX devices as PMEM for use by Memory Machine.

config-file

is the file path of the DPME configuration file. The default path is /etc/memverge/mvmallocd.yml.

For example:
```
# mvmallocd --format_pmem --config=/etc/memverge/mvmallocd.yml
```
You might see a license failure message:
```
Failed to load license from /etc/memverge/license.lic: LicenseError::LICENSE_FILE_OPEN_FAILED
```
Ignore this message for now. The following message should also be displayed:
```
Formatted successfully.
```
Start DPME:
```
# systemctl start mvmallocd
#
```
See Starting the Distributed Persistent Memory Engine.

Configure the host to start DPME on startup:

# systemctl enable mvmallocd
Created symlink /etc/systemd/system/multi-user.target.wants/mvmallocd.service -> /etc/systemd/system/mvmallocd.service.
#