Skip to content
Docs

restore

Put an App's data back as a Backup holds it.

The tool of basemodo restore, on the local MCP and the remote one. It changes things, so an agent's client may ask you before it runs.

Its volume (the database and every file under /data) becomes what it was when the Backup was taken: everything written since is gone, so take a Backup first if it may be needed. The Backup stays, and the App runs again afterwards. Restoring a deleted App's last Backup brings the App back.

Arguments

  • backup (text, required): The Backup to restore: its id, as basemodo backups lists it or basemodo backup --json prints it.
  • approval (text): The Charge Approval an Admin approves on basemodo.com, as a refused restore gave it, when a deleted App comes back beyond the Apps (or the Always On Apps) its Workspace pays for: wait until it is approved, then restore with it.

On the remote MCP

The same on the remote MCP.

Answer

It answers {"app", "backup"}. A Backup that does not exist or expired is an error with code backup_not_found. A deleted App beyond what its Workspace pays for asks an Admin for a Charge Approval, as deploy does: with --json or no terminal, an error with code charge_required, its "charges" and its "approval"; --approval waits until it is approved, then restores.