Observed restore
Recovery Path Walkthrough
A half-day sitting with an operator through one recovery path, from the first menu to the last confirmation, with a short path sheet afterwards.
Klang practice
Backup Vertex Base keeps usage notes from live work: the menus opened, the confirmations skipped, the restore path taken because a lorry was waiting. The record is for people who already have those features and need to know how they are used.
01
We do not arrive with a product to install. A practitioner from Backup Vertex Base takes a chair where the backup or recovery screens can be seen, brings a notebook, and stays for ordinary work. If a restore is needed that day, we watch the restore. If the day is only overnight-copy checks and a quiet afternoon, we write that too.
The subject is app analytics in the older sense: a written account of feature use. Backup schedules, recovery menus, restore points, failback steps, and the paper lists operators keep beside the keyboard all belong in the note. What does not belong is a score, a ranking of vendors, or a claim that unused menus are always a fault.
Most of our days are in Klang and greater Selangor. Intake calls are in English or Bahasa Malaysia. The written note uses the feature names as they appear on your screens.
Flagship
Two or three ordinary workdays beside the people who run backup and recovery. You receive a dated usage note organised by feature, then a ninety-minute briefing to read it together.
The review is for operations leads and application owners who can show a recovery menu and still cannot say, without guessing, which of those items an operator opened last week. We do not take the keyboard. We do not run production restores without your operator present.
From RM 4,800 for one recovery path, two observation days, the written note, and the briefing.
Also booked
These sit beside the flagship review. They are not renamed versions of it.
Observed restore
A half-day sitting with an operator through one recovery path, from the first menu to the last confirmation, with a short path sheet afterwards.
Findings session
A sitting with managers to read an existing usage note aloud, mark which unused recovery features still matter, and agree who will watch those steps next.
Return visit
A planned return to the same operators to see whether the recovery steps you marked after a review are now part of ordinary work.
From a Shah Alam receiving floor
“They sat through two ordinary receiving days, not a showcase restore. The note named the point-in-time picker we never open when a lorry is waiting.”
Farah Nordin · Operations lead · Backup Feature Usage Review
Field notes
11 March 2026
A drill that finishes on time can still leave half the recovery menu untouched. Here is how we read that gap in notes from Klang sites.
1 April 2026
A paper log beside the operator, filled at natural pauses, still beats an empty promise of automatic tracking.
02
Write from the contact page with the application name, the backup or recovery features you care about, and a week when operators can host observers. We reply from the Klang office within two working days with dates, what we will not do (install software, take administrator rights, run an unplanned restore), and a starting figure or a request for a short intake call.
If you only need one recovery path witnessed, book a walkthrough instead of a full review. If you already have our note, book a briefing. Rates and what moves a quote sit on the rates page.