Internal documentation only
This page has been marked as draft.
Opsview Disaster Recovery (DR) Installation / Upgrade
Prerequisites Copied
A Disaster Recovery agreement / software key is required and therefore Opsview Disaster Recovery cannot be run without being purchased
- If this configuration is found to be running without such an agreed purchase, then legal action will be undertaken by ITRS
- Usually Professional Services will be involved with your deployment/installation, however the below instructions details the installation and upgrade
- If you have DR installed already, then these upgrade steps are available for your use
- There is a legacy DR deployment, where these
What type of DR am I running? Copied
As of 2026, there are two existing types of DR setups, legacy and the new playbook installation method.
To tell which version you have, review the /opt/opsview/deploy/etc/opsview_deploy.yml.
If you have reference to opsview_database_other, then you are on the latest playbook installation.
- Not to be confused with
opsview_datastore_otheroropsview_orchestrator_other
Example
===
grep -ir opsview_database_other /opt/opsview/deploy/etc/opsview_deploy.yml
About Copied
This repository contains playbooks and scripts designed to simplify the installation and upgrade of the Opsview Disaster Recovery solution. The process is semi-automated using Ansible, following standard Ansible deployment practices.
By using this approach, we maintain a consistent, standardized configuration across all customer environments while reducing the risk of user error.
- NOTE: January 2026 - Currently this document only caters for the installation or upgrade of DR environments where the database is “managed”. If you have an unmanaged database, this will still require Professional Services involvement around installation and upgrades.
Installation Copied
The initial two curl command sections here will install a specific version of Opsview and then the matching version of the Opsview DR playbooks.
opsview-deploy Copied
This top curl command will download the required deployment packages for your chosen version.
- The initial example below will pull in the latest version 6 of Opsview
- If you wish to install a specific supported version, replace
6with the full string for that version, found on the Component page, (current release at writing of this document is 6.11.7)- Example: “This release deploys the Opsview repository version
6.11.7.202512171722”
- Example: “This release deploys the Opsview repository version
## This command should be run on both orchestrator servers
## Example 1:
## Run/Install latest Opsview on both Orchestrator servers
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -A boot
## Example 2:
## For specific version installation:
curl -sLo- https://deploy.opsview.com/6.11.3.202506231411 | sudo bash -s -- -A boot
opsview-deploy-dr Copied
Select your version:
## Latest
curl -sLo- https://downloads.opsview.com/opsview-support/install_opsview_dr | bash
## For version 6.11.7
curl -sLo- https://downloads.opsview.com/opsview-support/install_opsview_dr.6.11.7.202512151546 | bash
## For version 6.11.6
curl -sLo- https://downloads.opsview.com/opsview-support/install_opsview_dr.6.11.6.202510271635 | bash
## For version 6.11.5
curl -sLo- https://downloads.opsview.com/opsview-support/install_opsview_dr.6.11.5.202509180320 | bash
a
Generating the configuration Copied
This next section details two commands, one to be run on your chosen Primary Opsview orchestrator server and the other on your Secondary (known as DR) Opsview orchestrator.
These commands will generate a number of commands that are to be entered into either the Primary or Secondary (DR) server.
- It is critical to pay close attention to which command is to be entered where and in the correct order
Update the sections marked within “
## On Primary
/opt/opsview/deploy/lib/roles/opsview_dr/files/gen_initial_deploy_files -o <PRIMARY_IP> -O <DR_IP> -f <PRIMARY_FQDN> -F <DR_FQDN> -a <PRIMARY_DB_IP> -A <DR_DB_IP> -d <PRIMARY_DB_FQDN> -D <DR_DB_FQDN> -c <CNAME>
## On DR
/opt/opsview/deploy/lib/roles/opsview_dr/files/gen_initial_deploy_files -o <PRIMARY_IP> -O <DR_IP> -f <PRIMARY_FQDN> -F <DR_FQDN> -a <PRIMARY_DB_IP> -A <DR_DB_IP> -d <PRIMARY_DB_FQDN> -D <DR_DB_FQDN> -c <CNAME> --secondary
Example output you will receive:
1. Run pre-setup-host playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-pre-setup-hosts.yml
2. Run setup-hosts playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-hosts.yml
3. Run setup-hosts playbook on th-dr-o-2
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-hosts.yml
4. Run post-setup-host playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-post-setup-hosts.yml
5. Run gather machine ref playook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/gather-machine-refs.yml
6. Run gather machine ref playook on th-dr-o-2
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/gather-machine-refs.yml
7. Run setup-infrastructure playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-infrastructure.yml
8. Copy user_secrets on th-dr-o-1
source /opt/opsview/deploy/bin/rc.ansible ; ansible opsview_orchestrator,opsview_orchestrator_other -m copy -a 'src=../../opt/opsview/deploy/etc/user_secrets.yml dest=/opt/opsview/deploy/etc/user_secrets.yml mode=preserve'
9. Run setup-infrastructure playbook on th-dr-o-2
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-infrastructure.yml
10. Run post-setup-infrastructure playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-post-setup-infrastructure.yml
11. Run post-setup-opsview playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-opsview.yml
12. Active Opsview Primary Node and Apply Changes on th-dr-o-1
13. Stop opsview on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-stop-opsview.yml --tags start_stop_services,manage_crontabs
14. Run post-setup-opsview playbook on th-dr-o-2
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-opsview.yml
15. Active Opsview DR Node and Apply Changes on th-dr-o-2
16. Stop opsview on th-dr-o-2
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-stop-opsview.yml --tags start_stop_services,manage_crontabs
17. Run post-setup-opsview playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-post-setup-opsview.yml
18. Run setup-monitoring on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/setup-monitoring.yml
19. Run post-setup-monitoring playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-post-setup-monitoring.yml
20. Run setup-datastore-replication playbook on th-dr-o-1
/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/dr-setup-datastore-replication.yml
X
x