Cloud Data Manager

Prepare the environment for installation of the server by following these steps:

License key

Obtain a license key from Model9 by opening a “License" request in the Model9 service portal: https://model9.atlassian.net/servicedesk/customer/portals

The output of the z/OS command “D M=CPU” is required.

Firewall

Configure the local firewall to allow connections to ports needed by the Model9 containers. For a list of required ports, see the Model9 Before You Install 2.0.0 document.

Modify the firewall settings to all the above-mentioned port connections, or make sure the local firewall is disabled, using the following commands:

#UBUNTU
sudo systemctl stop ufw
sudo systemctl disable ufw

#RHEL
sudo systemctl stop firewalld
sudo systemctl disable firewalld

#SUSE
sudo systemctl stop SuSEfirewall2
sudo systemctl disable SuSEfirewall2

If Docker is already installed, restart the Docker service using the following command:

sudo systemctl restart docker

System parameters

The management server implements a “keep-alive” mechanism to prevent the firewall from disconnecting because of long requests to the agent during policy execution. Add the following kernel parameters to your /etc/sysctl.conf file:

net.ipv4.tcp_keepalive_time=600
net.ipv4.tcp_keepalive_intvl=30
net.ipv4.tcp_keepalive_probes=10

Apply the changes using the following command:

sudo sysctl -p

Docker

File system

The Model9 files should reside on a separate file system (other than the root file system) with enough free space to accommodate the Model9 management server and database. It is recommended to use the xfs filesystem type. Contact your Linux administrator to allocate adequate space and ensure it is mounted.

Installation files

Upload the model9-server-home zip installation file to the designated server in binary mode. Select one of the two available files according to your environment:

Create the filesystem hierarchy using the following commands:

# Change user to root
sudo su -
# Define the path to model9 installation files you uploaded earlier
export M9INSTALL=/<path>
# If you haven’t done so already, set the model9 target installation path
export MODEL9_HOME=/data/model9
# Change the directory to $MODEL9_HOME
cd $MODEL9_HOME

# Unzip the server’s installation file

# On Linux issue:
unzip $M9INSTALL/model9-v2.0.0_build_f3aba202-server.zip

# On Linux on z issue:
unzip $M9INSTALL/model9-v2.0.0_build_f3aba202-server-s390x.zip

The base installation provides a self-signed certificate for encrypting access to the user interface. To replace the default certificate for the WEB UI, see Secure web communication. Communications between the Model9 Server and the Model9 Agent are encrypted by default and further action should only be taken if site certificates are preferred.

The model9-local.yml file residing in the $MODEL9_HOME/conf/ path contains some of the default parameters. You can update them if necessary. Some of the parameters are explained below:

model9.licenseKey: <license-key>

model9.home: 'MODEL9_HOME'

model9.security.dataInFlight.skipAgentHostNameVerification: true

model9.security.dataInFlight.truststore.fileName: 'MODEL9_HOME/keys/model9-backup-truststore.jks'
model9.security.dataInFlight.truststore.type: "JKS"
model9.security.dataInFlight.truststore.password: "model9"
model9.security.dataInFlight.keystore.fileName: 'MODEL9_HOME/keys/model9-backup-server.p12'
model9.security.dataInFlight.keystore.type: "PKCS12"
model9.security.dataInFlight.keystore.password: "model9"

model9.session.timeout.minutes: 30

model9.master_agent.name: "<ip_address>"
model9.master_agent.port: <port>

# model9.objstore.resources.container.name: model9-data
# model9.objstore.endpoint.api.id: s3
model9.objstore.endpoint.url: http://minio:9000
model9.objstore.endpoint.userid: <object store access key>
model9.objstore.endpoint.password: <object store secret>

model9.runlogs.expirationScanIntervalMinutes: <min>
model9.runlogs.maxRetentionPeriodDays: <days>

dataSource.user: postgres
dataSource.password: model9
dataSource.url: jdbc:postgresql://model9db:5432/model9

Model9 full volume dumps can be used for stand-alone restore. To prepare a Bare-Metal recovery restorable volume, the stand-alone program must be installed on the server. The UI provides a special action to prepare a stand-alone copyfrom a regular full volume dump. The installation guide describes the required steps for enabling the creation of stand-alone copies. See the Model9 Administrator and User Guide for:

Creating a Stand-Alone Copy - Requirements

Creating a stand-alone copy requires the following DFDSS files to be saved in the $MODEL9_HOME/SAbackup path:

These files can be obtained from the IBM Customized Offering Driver which can be downloaded from Shopz free of charge.

Stand-Alone Restore using FTP - Requirements

To perform a stand-alone restore from removable media accessed via FTP, install the VSFTPD default server using the following command:

#Ubuntu
sudo apt-get install vsftpd

#RHEL
sudo yum install vsftpd

A local user with sudo permissions can run the following systemctl commands to enable and start the service:

sudo systemctl enable vsftpd
sudo systemctl start vsftpd

Stand-Alone Restore from a USB - Requirements

The USB device should be formatted using the FAT32 file system and can reside in any directory except for the root path.