Virtual machines (VMs) and separate boot partitions allow you to run additional operating systems on your computer. This article highlights best practices for backing up virtual machines or separate boot partitions with the Code42 app.
Common applications that create virtual machines or boot partitions include:
- Boot Camp
The Code42 app can back up the files within virtual machines or boot partitions. You can alternatively back up an image of the additional operating system. Both methods require special considerations to back up effectively.
The Code42 app does not support Universal Naming Convention (UNC) file paths (for example, //SERVERNAME/shareddir/).
- Code42 app version 6.9.0 and later does not allow you to add UNC file paths to the backup file selection.
- Earlier versions of the Code42 app do accept UNC file paths, but those files are not backed up properly and cannot be restored.
Back up files within a virtual machine or boot partition
We recommend installing an instance of the Code42 app inside the virtual machine or boot partition. This provides individual file backup and real-time backup support for those files. Alternatively, you could copy files from the virtual machine to an external drive, and back up the external drive from your primary operating system.
Back up a virtual machine
Alternatively, you may want to archive a virtual machine to use as a template for future deployments. However, this is similar to backing up operating system and application files, whereas the Code42 app is designed for backing up user files.
If you choose to use the Code42 app to back up your virtual machine, consider the following technical details about how and what to back up.
Disk images and exports
A disk image of a virtual machine contains all of the boot information and operating system files necessary to re-deploy the virtual machine. Similarly, some virtualization software allows you to export a virtual machine to a single file. You may choose to back up disk images and exports with the Code42 app; however, consider the following:
- Creating the image or export itself is typically a manual process that varies based on your virtualization software.
- Because creating an image or export is a manual process, files within the VM are not continuously protected.
- Files are not backed up individually. To restore any files from within the virtual machine, you must restore the entire virtual image or export.
- If the image is open and constantly being written to, it may be difficult to back up all of the data needed to reliably restore these files.
Our Customer Champion team cannot provide direct assistance with backing up and restoring virtual machine snapshots, disks, disk images, or exports. Consult your virtualization software manufacture's documentation for further information and considerations on backing up virtual machines.
Exported virtual machines or disk images are typically large files and may require special settings if you decide to back them up.
Snapshots are designed for short-term use as a way of returning a virtual machine to a previous state. We do not recommend backing up snapshots. Snapshots are typically created as differential files that only capture what changed since the last time a snapshot was created. A snapshot must be merged with the virtual hard disk and all previous snapshots to be re-deployed successfully.
If you know where your virtual machine software stores your virtual disk and snapshot files, it is possible to back these files up with the Code42 app. Consult your virtualization software to determine whether or not it is possible to restore a VM using the backups of your snapshot files in combination with the virtual disk file.