Veritas™ System Recovery 21 User's Guide
- Introducing Veritas System Recovery
- Installing Veritas System Recovery
- Installing Veritas System Recovery
- Ensuring the recovery of your computer
- Creating a new Veritas System Recovery Disk
- Creation Options
- Storage and Network Drivers Options
- Customizing an existing Veritas System Recovery Disk
- About restoring a computer from a remote location by using LightsOut Restore
- Creating a new Veritas System Recovery Disk
- Getting Started
- Setting up default general backup options
- File types and file extension
- Best practices for backing up your data
- Backing up entire drives
- Backing up files and folders
- Running and managing backup jobs
- Running an existing backup job immediately
- Backing up remote computers from your computer
- Monitoring the status of your backups
- About monitoring backups
- Monitoring the backup status of remote computers using Veritas System Recovery Monitor
- Adding a remote computer to the Computer List
- Exploring the contents of a recovery point
- Managing backup destinations
- About managing file and folder backup data
- Managing virtual conversions
- Managing cloud storage
- Direct to cloud
- About creation of Amazon Machine Image (AMI) in Amazon from Veritas System Recovery backups
- About S3-Compatible Cloud Storage
- About Veritas System Recovery supporting Veritas Access
- Recovering files, folders, or entire drives
- Recovering a computer
- Booting a computer by using the Veritas System Recovery Disk
- About using the networking tools in Veritas System Recovery Disk
- Copying a hard drive
- Using the Veritas System Recovery Granular Restore Option
- Best practices when you create recovery points for use with the Granular Restore Option
- Appendix A. Backing up databases using Veritas System Recovery
- Appendix B. Backing up Active Directory
- Appendix C. Backing up Microsoft virtual environments
- Appendix D. Using Veritas System Recovery 21 and Windows Server Core
About backing up and restoring Microsoft Hyper-V virtual machines
To create a backup of a Microsoft Hyper-V virtual machine, you must back up the volumes of the computer where the virtual machine is hosted. Create either a live backup or a system state backup of the host machine. You cannot back up or restore a specific virtual machine. A live backup is created while the virtual machine is running (hot backup).
A system state backup is created in any of the following conditions:
The guest operating system on the virtual machine is not running (cold backup).
The Hyper-V VSS integration component is not installed in the virtual machine.
Note:
Veritas System Recovery is unable to back up cluster shared volumes. Because volumes in such a configuration are accessible to each of the clustered Hyper-V host computers, a given volume cannot be locked for backup . However, clustered disks can be backed up by Veritas System Recovery because one host has exclusive access to the disk.
To create a backup of a running virtual machine, the following conditions must be met:
The guest operating system must be running.
The guest computer must be running Windows Server 2008 or later.
If the guest computer is running Windows 2000, you can only create a system state backup (cold backup).
The Hyper-V VSS integration component must be installed on each virtual machine to be backed up.
If you move a virtual machine from Virtual Server 2005 to Hyper-V, first uninstall the Virtual Server 2005 integration component from the virtual machine. After you Virtual Server 2005 integration component, you can install the Hyper-V VSS integration component.
The guest virtual machine should be configured to only use basic disks, not dynamic disks.
This configuration is the default for installing a Windows virtual machine.
All the volumes on the fixed disks must support the creation of snapshots.
If you perform a backup when these conditions are not met, Veritas System Recovery creates a system state recovery point that is crash-consistent. A crash-consistent recovery point captures the virtual machine as if it had experienced a system failure or power outage.
You can restore a specific virtual machine from the recovery point of the host computer using the Recovery Point Browser. Use the Recovery Point Browser to extract the files that make up the virtual machine. The host computer recovery point must include the volume that holds the virtual machine that you want to restore.
To know about the limitations of Hyper-V when backing up databases on virtual machines, refer to the Veritas Knowledge Base:
https://www.veritas.com/support/en_US/search-results.html?keyword=V-306-2*
Find information about backing up Microsoft virtual hard disks: