Upgrade Velox
Upgrade only with a release-specific runbook that identifies compatible starting versions, binary and ProgramData changes, database scripts and rollback boundaries. Services do not establish that every required database upgrade has run.
Plan and prepare
- Confirm the supported starting and target releases and review release notes.
- Inventory executables, ProgramData assets, system connections, service identities, modules and external dependencies.
- Take and test restorable database and required filesystem/configuration backups.
- Obtain approved packages, checksums and ordered VxConfig/VxData scripts.
- Define downtime, verification, rollback decision point and owners.
Upgrade
- Disable triggers and stop Velox services so processing cannot change state.
- Apply database changes in the runbook's order and verify each reported version.
- Deploy the target binaries and matching ProgramData assets without mixing releases.
- Preserve environment configuration while reconciling deliberate template changes.
- Start Designer first and verify connections and configuration loading.
- Start services, then complete the installation verification before re-enabling work gradually.
Recovery
Do not copy old binaries over a database already upgraded unless the runbook explicitly supports it. If the recovery threshold is reached, stop services and restore the coordinated database, binary and filesystem/configuration set. Reconcile any external side effects produced after the backup point.