Skip to guide content
WavelinkWAVELINKAJ OFFSHORE SOLUTIONS · HELP
UI 07Open workspace
Help centreGetting started & support

CORE GUIDE TOPIC · backups

About these instructions

This reader standardises presentation, not the entire procedure library. The original instructions, version labels and warnings are retained. Some topics describe the local Windows hub or earlier interface labels. They must not be read as proof that all desktop setup, imports or recovery work is available in the hosted browser.

The full wording, hosted/local scope, native Help and PDF review remains on the development list. Use only company-approved operational procedures; viewing Help does not approve a checklist, release equipment or verify work.

On this page 5 sections
  1. Save a full project backup
  2. Update the application
  3. Restore or transfer
  4. Vessel log scope in transfers
  5. Update recovery in 1.23

User instructions

Back up and update

Protect the shared record of work

Save a full project backup

Open Backups & support → Save full database backup…. Keep it in an approved protected location. It includes saved checklists, logs, inventory, box relationships, verifications, private tasks, maintenance, toolbox acknowledgements, users, original files, certificates, asset pictures and low-stock settings.

Update the application

  1. Synchronise or export device work, including separate log windows. Save a project backup.
  2. Stop the hub and close Admin. Run Setup under the same Windows account, keeping both existing Application and Project data folders.
  3. Choose Install / update. Do not uninstall first, clear browser data or relocate the project merely to update.
  4. Open the expected project with an existing account and restart at the saved address. Reload devices, confirm the version and test a practice record.

Restore or transfer

Restoring replaces the current saved project state. Coordinate with the team, preserve current work, stop the server and use Restore a hub backup. Sign in again and review unsent device work against the restored records before submitting it.

To move a complete project to another PC, use Projects → Export — choose contents, with full history, then import as a new project. Its new hub identity means inventory QR labels need reviewing and reprinting. Narrow inventory exports do not carry asset profiles, photographs, certificates or maintenance history.

An unexpected first-account screen after an update means stop and check the project and Windows account. For removal, read the separate Uninstall help: complete uninstall can permanently delete selected projects. Keep required backups outside all selected deletion folders.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Vessel log scope in transfers

Complete project copies retain logbook-to-vessel links, per-user site log rights and their access-change history. A history-bearing selected Logs transfer includes these with the retained site directory and accounts; omitting Logs omits its scope and rights too. The transfer remains administrator-only, unencrypted and not filtered to a single vessel.

A standalone .ajlogs export transfers a logbook without vessel grants. It imports as a new project-only logbook. Review its content and deliberately link it to a local vessel and users before using it in the vessel portal. It does not modify or restore the original scope automatically.

Update recovery in 1.23

Before an update changes dependencies or application files, Setup snapshots the known application files, existing private runtime, installation settings and project catalogue. On Windows it also records the affected shortcut files and uninstall registry values. This uses additional disk space; a snapshot failure stops before update commands run.

A detected installation failure attempts to restore that snapshot. The project databases, documents and browser drafts are not rolled back. If you deliberately chose a new project location and a verified copy was already made, that copy can remain; do not run it as a second hub.

If an interrupted setup is detected, the next run restores the previous installation and then asks you to close and reopen Setup so the restored locations are read again. If recovery cannot finish, preserve the reported snapshot and journal, do not launch the app, and contact support. This is not a substitute for a project backup. Real Windows and power-loss testing remains required for this release.

Review and explicitly acknowledge the sensitive, unencrypted full database copy before choosing a destination. This is not a recipient-filtered report.

Browse all Help topicsBack to topic start ↑