Moltaro 0.0.40-beta
Release date: 2026-09-06
Runtime VM transfers can initialize an empty destination while retaining the same application and Object Storage. Recovery preserves current backup retention records, and transfer cleanup no longer mistakes a moved runtime for deletion of the application and its storage.
Highlights
Section titled “Highlights”- Restore the same application onto a newly created Runtime VM.
- Preserve existing backup pins, legal holds and file-generation metadata.
- Clean up partial target installs before recovering the source after failure.
Detailed changes
Section titled “Detailed changes”The destination installs the exact runtime captured by the selected backup and restores the same storage binding. Current file-retention control records are exported after the source stops, verified, and reapplied during restoration. Unchanged Object Storage file bodies are neither copied nor downloaded again.
Transfer cleanup removes only the obsolete local runtime, database and role; it retains the other placement and shared storage binding. The server verifies the active transfer operation before granting this cleanup authority. Normal application deletion keeps its storage-dependency checks. Application and VM ownership are unchanged.
Database and upgrade impact
Section titled “Database and upgrade impact”No Workspace or Portal schema migration. Publication updates Portal and Runtime
VM agents, but all three Managed Apps retain runtime 0.0.36-beta without
container replacement or restart. Portal activation has a short interruption;
a PortalDb recovery point and previous Portal release are retained for rollback.
The separately initiated application transfer has its own source-stop interval.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish with the two-phase PortalAndAgent mode and frozen runner. Agent
0.1.44 includes the transfer tool and must be active on both VMs. Do not
publish runtime/update packages or alter their catalogs. Existing failed jobs
are not retried by publication. Quiesce application writes and background work,
create a fresh backup matching the current runtime, then transfer to the chosen
VM. Referenced backups require the original Object Storage; retain that storage.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”Transfers require agent 0.1.44 or newer. In-place recovery and copy-as-new remain distinct operations. No application runtime, SDK, ownership or schema change. The agent-owned transfer tool does not upgrade the installed application.