Clone Windows File History backups to a new drive without breaking restores
Clone Windows File History backups to a different drive while preserving catalog files and the directory layout needed by the Restore interface. FileHistoryClone, created by Tomoyuki Ohya, automates the migration process and offers a command-line mode and winget install for deployment. It targets Windows power users and sysadmins who must move File History repositories without losing versioned restore access, especially when upgrading storage or consolidating backup drives.
What the tool actually does during a migration
The tool copies File History data while keeping the exact directory structure and metadata the Windows Restore interface expects. It clones backup folders and associated catalog files rather than performing a generic file copy, which addresses the common failure where Windows stops recognising previous versions after a manual transfer. The tool runs from a lightweight executable and can be invoked interactively or via its command-line interface for scripted migrations.
How it affects system resources and scanning
The tool has a small footprint and requires no complex installation, so it runs with minimal background impact. Because it performs targeted file-system writes to the destination drive rather than scanning the whole system, typical operations consume little CPU and RAM on desktop machines. The command-line mode lets administrators schedule or batch migrations without opening a GUI, reducing interactive load during working hours.
Is it safe and who should operate it
The app preserves backup metadata and catalog files, which means it writes data in the same structure Windows reads; that behaviour reduces the risk of breaking restores. It does not require elevated system redesigns, but an administrator should stop File History or ensure no concurrent writes during cloning to avoid inconsistent copies. The tool suits administrators and advanced users comfortable with command-line deployment and storage maintenance.
Practical recommendation and a single operational caveat
Use the tool when you need dependable migration of File History repositories and prefer a transparent, scriptable process. Before cloning, pause or disable active File History jobs to prevent partial copies. The tool works well for administrators moving backup stores, but avoid running it against an actively writing backup to prevent inconsistency.
