Maintaining IBM Optim Archive Enterprise Edition for z/OS

Edit online

Regular operations and maintenance tasks for IBM Optim Archive Enterprise Edition for z/OS® on zCX include starting and stopping services, monitoring resource usage and logs, updating services, and performing backups.

Starting and stopping IBM Optim services

You can control IBM Optim services using Docker Swarm commands.

To stop all services by scaling to zero replicas:

docker service scale optim-ui=0 optim-runtime=0 optim-spark=0 \
  optim-core-api=0 optim-keycloak=0 optim-metadb=0

To remove services completely:

docker service rm optim-ui optim-runtime optim-spark \
  optim-core-api optim-keycloak optim-metadb

To start services by scaling back up:

docker service scale optim-metadb=1 optim-keycloak=1 \
  optim-core-api=1 optim-runtime=1 optim-spark=1 optim-ui=1

To redeploy services after removal, run the deployment script with the required parameters.

Monitoring IBM Optim

Monitor resource usage and service status using Docker commands.

To view real-time resource statistics:

docker stats

To view service-specific status:

docker service ps optim-runtime

To follow service logs in real time:

docker service logs -f optim-runtime

To search for errors in logs:

docker service logs optim-runtime 2 > | grep -i error

To export logs to a file:

docker service logs optim-runtime > /opt/optim/logs/runtime-$(date +%Y%m%d).log

Updating IBM Optim services

To update a service to a new image version:

  1. Pull or load the new image: 
    docker pull localhost/ibm-optim/optim-ui:1.2.1-s390x
  2. Update the service: 
    docker service update --image localhost/ibm-optim/optim-ui:1.2.1-s390x optim-ui

Backing up and restoring IBM Optim

Use the backup and restore script to protect your data and configurations.

To create a backup:

./scripts/optim-backup-restore-s390x.sh backup --path /opt/optim/backups

To include encryption keys for cross-host restoration:

./scripts/optim-backup-restore-s390x.sh backup \
  --path /opt/optim/backups \
  --encryption-key

To restore from a backup:

./scripts/optim-backup-restore-s390x.sh restore \
  --backup-file /opt/optim/backups/optim_20260315_120000.tar
Important: Stop all services except the metadata database before restoring.

Recommended maintenance

The following table provides recommended maintenance schedules:

Frequency Tasks
Daily
  • Check service status: docker service ls
  • Review error logs
  • Monitor disk usage: df -h
Weekly
  • Backup databases
  • Review job history
  • Check for updates
Monthly
  • Apply security patches
  • Archive old logs
  • Review and optimize database performance

Tuning performance

Adjust memory profiles based on workload and available resources. The deployment script supports 3 memory profiles:

  • Small (32 GB RAM): Spark driver 512 MB, executor 2 GB
  • Medium (64 GB RAM): Spark driver 1024 MB, executor 4 GB (default)
  • Large (128 GB+ RAM): Spark driver 2048 MB, executor 8 GB

Monitor the Spark UI at port 8480 to analyze job performance and identify optimization opportunities.