This page describes how to provision the Model9 Management Server from the Cohesity marketplace.
The Model 9 Cloud Data Manager is featured in the Cohesity Marketplace
The output of the z/OS command “D M=CPU” is required.
The Model9 configuration and meta-data files should reside on a Cohesity view, defined as NFS only.
The name of this view must be set to model9home (case sensitive).
Mount the NFS share on a Linux machine and configure initial settings:
Change user to root
sudo su -
Mount the model9home cohesity view
mkdir -p /data/model9/nfs mount cohesity.ip.addr:/model9home /data/model9/nfs/
Set the model9 target installation path
export MODEL9_HOME=/data/model9/nfsUpload the Cohesity zip installation file to the NFSs share mount point (for example: /data/model9/nfs) in binary mode:
Upload the Cohesity zip installation file to the NFSs share mount point (for example: /data/model9/nfs) in binary mode:
Use a Linux server to mount the newly created view and unzip the uploaded installation zip file:
# Change user to root
sudo su -
# Change the directory to $MODEL9_HOME
# Unzip the server’s installation file, on Linux issue:
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. The main section is model9 (lower-case) and all parameters must be indented under the model9 title. Only hard spaces can be used to indent the hierarchies within the parameter file.
# resources.container.name: model9-data
# api.id: s3
# no.verify.ssl: true
userid: <object store access key>
password: <object store secret>
# The dataSource tag should start from first column and not under model9 tag
A valid Model9 license key as obtained in the prerequisites section. When using multiple keys for multiple CPCs, specify one of the keys in the server’s yml file. The server-initiated actions are carried out by the agent using its own defined license. The license key specified for the server is used for displaying a message regarding the upcoming expiration of the license
The agent running on z/OS which verifies the UI login credentials, hostname, IP address and port number. Specifying a distributed virtual IP address (Distributed VIPA) can provide high availability by allowing the use of agent groups and multiple agents. See the Administrator and User Guide for more details.
URL address of local or remote object storage, both HTTP and HTTPS** are supported
Access key to object storage
Secret key to object storage
The object storage api name. Default: s3
Set this parameter to true in addition to specifying api.id: s3
when using the https protocol, whether to avoid ssl certificate verifications. Using HTTPS for the object storage URL parameter enables Data-in-Flight encryption. Default: true
Update the postgresql address to point to localhost (i.e. 127.0.0.1)
The model9-stdenv.sh file residing in the $MODEL9_HOME/conf/ path contains some of the default parameters.
Update the timezone setting according to the server location.
1. Go to the Apps section in the Cohesity UI, and click on the Run App button located next to the loaded application:
2. Grant permission to access the NFS view created for Model9 (The view name is model9home).
3. Click on Run App to start the application.