Installing in production
Object storage provides functions that protect against data loss and data corruption. Review options such as:
- WORM storage
- Versioning - retaining deleted objects for an additional period of time
The Model9 agent will fully use the network resources within the available CPU and memory limits. Refrain from using the same OSA card for production workload and backup activities. If possible, use a dedicated OSA card for Model9. Otherwise, if network resources are a constraint, activate your network QOS to manage packet priorities.
The agent installation specifies how to secure agent - server and agent - object storage communications. Perform these steps If you have not yet done so.
The agent’s performance is mainly affected by WLM definitions. When associating a WLM service class, consider its effect on policy elapsed time and on the agent’s CPU consumption. See Performance considerations for additional information.
Back up the management server regularly, excluding the following directories from the backup:
Back up the management server DB using the following command:
export MODEL9_HOME=<model9 home>
docker exec -it model9db pg_dump -p 5432 -U postgres -d model9 --compress=9 -f /tmp/model9db-$fileStamp.dump.gz
docker cp model9db:/tmp/model9db-$fileStamp.dump.gz $MODEL9_HOME/model9db-$fileStamp.dump.gz
docker exec -ti model9db rm /tmp/model9db-$fileStamp.dump.gz
Schedule life cycle management for execution on a daily basis.
When scheduling policies using the mainframe’s automatic scheduler, monitor the M9SAPI return code.