BACKUP RESTORE DRILL

Backup and Restore Drills, Las Vegas NV

Backup and Restore Drills, Las Vegas NV — Las Vegas NV
Backup and Restore Drills, Las Vegas NV

Backups are files; recovery is a capability. Drill design, recovery objectives, and the evidence that turns a backup policy into a control.

The only metric that matters

Time to restore a working service, measured, not the time to copy a file.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

RTO and RPO stated plainly

Recovery objectives that are not written down are not objectives; they are hopes shared verbally.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Drill design

A drill that restores to a different environment proves the data; restoring to the same environment proves the process.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Immutability and ransomware

A backup reachable with production credentials is not protection from the most likely attack.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Retention versus deletion

Retention requirements and deletion obligations conflict; the resolution belongs in the design.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Verification, not completion

A backup job that reports success and produces an unreadable file is a control that lies.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Who is called

The drill should include the call, because recovery at three in the morning is a communications exercise as much as a technical one.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Record and review

The drill result is the artefact; a drill without a written result did not happen.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Recovery objectives are numbers, not adjectives

A recovery time objective is how long a service may be down; a recovery point objective is how much data may be lost. Both are business decisions expressed in numbers, and a document that says "minimal downtime" has said nothing an engineer can design against.

State both per service. A clinical API and an internal reporting database do not deserve the same objective, and applying the strictest to everything produces a backup regime nobody can afford to test, which is the same as no regime.

The measured number is what counts: the time from the decision to restore to the service working, obtained in a drill. It is always worse than the assumption, and knowing how much worse is the whole point.

Immutability, and the attack you are actually defending against

A backup reachable with production credentials is not protection against the most likely attack on a regulated estate. Immutability — an object-lock window or an offline copy — is what turns a backup into a recovery capability against ransomware.

Retention requirements and deletion obligations conflict, and the resolution belongs in the design rather than in an argument after a request. Say which data is held for how long and on what authority.

A backup job that reports success and produces an unreadable file is a control that lies. Verify by restoring and reading, not by checking the job status.

The drill includes the call

Recovery at three in the morning is a communications exercise as much as a technical one. The drill should include reaching the person who can authorise the restore, because the technical steps are usually faster than the decision to begin them.

Write the result: what was restored, into what environment, how long it took, what failed on the first attempt, and who was called. A drill without a written result did not happen, and the review is where the next drill gets better.

Test the scenario you fear most once a year — the provider account unavailable, the region impaired, the backup store credential compromised. The plan that works for the easy case and has never been tried on the hard one is a plan with an untested half.

Scope of a drill, stated plainly

Which service, which data, restored where, by whom, within what window, and what the acceptance check is. Without those six the drill is an exercise in moving files and the result cannot be compared to the objective.

Rotate the scenario. A drill that always restores the same small database proves the same path each quarter and leaves the hard dependencies untested, which is usually the identity store and the message queue.

Publish the result to the same audience that owns the risk register. The drill is evidence for the analysis, and evidence that never reaches the register is evidence nobody can produce under examination.

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide. Las Vegas, Nevada 89101.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes backup and restore drills, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.

Talk to Charles

702-559-3489 · charles@trinh.io

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026
TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.