Operate

Prepare an upgrade or removal

Protect data and installation identity while waiting for a qualified 1.0.0 upgrade path.

Establish a tested upgrade path

A general RC1-to-1.0.0 upgrade procedure is not established by the fresh-install release. Record the current version, build, platform, database provider and node topology. The release must name the tested starting version and package before an in-place upgrade can be documented.

Protect the installation first

While normal access is available, export required information and back up the databases, protected installation state and external documents using backup guidance. Keep the issued activation and acceptance receipts. Verify restoration in an approved environment before depending on it.

Plan the change

Review the release-specific sequence for the primary installation and approved nodes, service interruption, schema changes, readiness checks and recovery. A successful fresh install does not establish an upgrade or rollback path. Follow the tested procedure once supplied.

Review removal separately

Read the exact installer’s removal options and their effect on protected identity, databases and external storage before confirming. An uninstall is not a substitute for backup. Registration expiry retains customer data and blocks ordinary exports after the allowance cutoff.

Pūnaha Docs

Search the guides

Enter at least two characters.

    Product screen

    View the full screenshot