System

Backup & Restore

Disaster recovery for Tel-A-Rent — Main Admin only. Employees and managers have no access.

SYSTEM PROTECTION

Site / Code

Protected by Base44 Version History — automatic on every change.

Business Data

No backup yet — create one below.

Uploaded Files

Protection starts on the first backup run.

Sensitive Documents

0 files protected at the same security level as the live documents.

AUTOMATIC WEEKLY BACKUP

Schedule: Weekly — Saturday, 10:00 PM Central
No automatic backup yet.
Next: Saturday, September 19 — 10:00 P9 C6ntrpm9/19/2026

Email Main Admin When Backup Fails

Only on failure / partial — never on success.

Last Full Verification: pending first run

Site Code Restore Points — Automatic

Base44 keeps a Version History of every change automatically — pages, layouts, components, backend functions, and entity schemas. You do not need to create these restore points: they exist for every publish, covering Coop, Live Agent, the Employee Portal, forms, and workflows.

To restore code: open Version History at the top of the Base44 chat panel, pick the known-good version, and choose Publish this version (live site) or Revert to this version (your draft).

Restoring code never touches customer records — applications, requests, live chats, and attachments all stay exactly as they are.

Create Restore Point (Manual)

Same proven engine as the weekly automatic backup: exports 44 business-data tables to a private checksum-verified file AND protects any new uploaded files. Name it before major changes (e.g. BEFORE COOP UPDATE, KNOWN GOOD PRODUCTION VERSION). Manual restore points are never automatically deleted. Zero AI — no integration-heavy operations.

Backup & Restore History

No backups yet — create your first restore point above.

Uploaded File Protection (Manifest)

0 verified protected files

No files protected yet — file protection runs with each backup.

How to Restore (High-Risk — Read First)

  1. Site code problems: restore a Base44 Version History version (above). This is the normal disaster-recovery path and cannot delete newer customer data.
  2. Before ANY restore: create a fresh manual restore point first (name it "AUTO BACKUP — BEFORE RESTORE — [date]") so a bad restore can be undone.
  3. Missing customer file: find it in the manifest above and click Restore File — recovery is per-file and never bulk.
  4. Database/data restore: there is deliberately no one-click data rollback here — restoring records is done deliberately, table by table, from a downloaded backup file with Base44's help. You choose exactly what comes back; newer records are never auto-erased.

Protected files are private storage copies verified by checksum — backups never create public URLs. Public website images (photos shown on public pages) are not sensitive attachments; their addresses are preserved inside every data backup.