We have two physical machines running Windows 7 that control legacy operational software. Upgrading the operating system is unfortunately not possible, and the systems cannot be virtualized.
We currently use Veeam Backup & Replication 13, but it reports warnings and errors because the Data Mover service can no longer be updated on these older devices. Backups still complete for now, but we are concerned that they may eventually stop, and we cannot clear the compatibility warnings.
Ideally, we would like to keep centralized management and maintain backup copies on our NAS, Wasabi, or rotated hard drives. If that is not practical, we may need to use an older Veeam Agent locally on each machine and back up to removable storage.
What backup or disaster-recovery approach would you recommend for only two legacy bare-metal Windows 7 systems?
2 Answers
A practical option is to use an older imaging tool that still supports Windows 7, such as Disk2VHD or another legacy-compatible product. Disk2VHD can create a full virtual-disk image without requiring the machine to become part of a virtual environment. A scheduled wrapper can automate the process to a separate volume or backup share.
Keep in mind that the image should be treated as a recovery artifact: periodically verify that it is readable and, if possible, perform a test restore on spare hardware.
If the operating system and application rarely change, a full image does not necessarily need to run every day. Make and verify a complete disk image, then schedule frequent backups of only the business data, configuration files, or database. This reduces compatibility problems and backup traffic while still giving you a way to rebuild the machine after disk failure.
Also keep at least one offline or disconnected copy. Legacy Windows systems are much easier to protect when the backup media cannot be reached by malware on the production network.
That approach works especially well when the application data is stored separately from the operating system. Before relying on it, confirm exactly where the program keeps its database, configuration, licenses, and any files needed for recovery.