System Update

System Update via the Ansible playbook only supports version r10 or later; earlier versions cannot be updated using this method.

Ensure you have met all requirements as outlined before proceeding.

• Target node prerequisites

• Control node configurations

The updater will check for potential data loss before proceeding. If data loss is expected, you will be prompted for confirmation.

Start the Ansible playbook for updating:

ansible-playbook start.yaml -t update

You will be prompted for your SSH and sudo passwords for authenticating the target node.

SSH password:
BECOME password[defaults to SSH password]:

Tip

If authenticating via private SSH key is possible, you can leave the value of SSH password blank. If there is no password requirement for sudo commands, you can leave the value of BECOME password blank as well.

The updater will stop all services related to IRIS+ Professional and create a backup at each version step.

Creating a backup

Ensure you have met all requirements as outlined before proceeding.

• Target node prerequisites

• Control node configurations

Start the Ansible playbook for backup creation:

ansible-playbook start.yaml -t create-backup

You will be prompted for your SSH and sudo passwords for authenticating the target node.

SSH password:
BECOME password[defaults to SSH password]:

Tip

If authenticating via private SSH key is possible, you can leave the value of SSH password blank. If there is no password requirement for sudo commands, you can leave the value of BECOME password blank as well.

The Ansible playbook will stop all services related to IRIS+ Professional, create a backup, and then restart the services.

Listing available backups

Ensure you have met all requirements as outlined before proceeding.

• Target node prerequisites

• Control node configurations

Start the Ansible playbook for backup creation:

ansible-playbook start.yaml -t list-backups

You will be prompted for your SSH and sudo passwords for authenticating the target node.

SSH password:
BECOME password[defaults to SSH password]:

Tip

If authenticating via private SSH key is possible, you can leave the value of SSH password blank. If there is no password requirement for sudo commands, you can leave the value of BECOME password blank as well.

Restoring a backup

Ensure you have met all requirements as outlined before proceeding.

• Target node prerequisites

• Control node configurations

The restoration process will result in data loss.

Start the Ansible playbook for restoring:

ansible-playbook start.yaml -t restore

The restore process will revert to the most recent backup by default. If you want to restore from a specific backup, you can provide the full path to the desired backup file.

ansible-playbook start.yaml -t restore -e "backup_source_file=/path/to/backup/file"

The restore process will first create a backup of the current setup before starting the restore. If you want to skip this backup, you can use the skip-backup tag:

ansible-playbook start.yaml -t restore,skip-backup -e "backup_source_file=/path/to/backup/file"

You will be prompted for your SSH and sudo passwords for authenticating the target node.

SSH password:
BECOME password[defaults to SSH password]:

Tip

If authenticating via private SSH key is possible, you can leave the value of SSH password blank. If there is no password requirement for sudo commands, you can leave the value of BECOME password blank as well.

During the restore process, the Ansible playbook will stop all related services, create a backup, and re-start the services.