You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 5, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 5, 2026. It is now read-only.
vmrestore has merged into vmbackup (v0.6.0) — repo archived #1
vmrestore has merged into vmbackup as of vmbackup v0.6.0.
This standalone repository is now archived (read-only) and no longer maintained. The vmrestore command lives on — it ships inside the unified vmbackup package, with the same command-line interface and the same behaviour.
What this means for you
New installs: use vmbackup. Installing it gives you both vmbackup and vmrestore from one package.
Existing 0.5.x installs: keep working as-is. On upgrade to vmbackup 0.6.0, the unified package replaces the old standalone vmrestore automatically — no config changes, no migration steps.
Staying on 0.5.x: the final standalone release v0.5.4 remains downloadable here. The v0.5.4-final tag marks the last standalone commit.
vmrestorehas merged into vmbackup as of vmbackup v0.6.0.This standalone repository is now archived (read-only) and no longer maintained. The
vmrestorecommand lives on — it ships inside the unifiedvmbackuppackage, with the same command-line interface and the same behaviour.What this means for you
vmbackupandvmrestorefrom one package.0.5.xinstalls: keep working as-is. On upgrade to vmbackup0.6.0, the unified package replaces the old standalonevmrestoreautomatically — no config changes, no migration steps.0.5.x: the final standalone releasev0.5.4remains downloadable here. Thev0.5.4-finaltag marks the last standalone commit.Where things moved
Thanks to everyone who used and contributed to standalone
vmrestore. Development continues in the unified project.