Skip to main content

Incident recovery

When Jiandu stops or documents cannot be opened, preserve evidence and originals before changing anything.

First response​

  1. Stop repeated automated restarts if they are overwriting useful logs.
  2. Record the exact error, time, Jiandu version, and last known successful action.
  3. Check disk/database capacity and whether storage endpoints are reachable.
  4. Confirm only one Jiandu process is using the installation.
  5. Snapshot or copy the current database, blob storage state, configuration, and logs using your platform's safe procedures.
  6. Do not run a migration, cleanup, or restore over the only copy.

Choose recovery, not experimentation​

If the root cause is clear and reversible—such as an expired certificate or unavailable object store—restore that dependency and recheck readiness. If database or archive integrity is uncertain, restore the latest verified backup into a new isolated destination.

Use the Owner token only as break-glass access. Do not rotate or replace recovery material during an unrelated outage unless compromise is part of the incident.

After service returns​

Open representative originals, verify restricted access, and check connectors for backlogs or duplicates. Write down the cause, the observed warning signs, and one change that would detect or prevent a repeat.

Start with the error message guide when Jiandu provides a stable message.