Veritas™ System Recovery 21 Management Solution Administrator's Guide
- Introducing Veritas System Recovery Management Solution
- Installing Veritas System Recovery Management Solution
- Getting started with Veritas System Recovery Management Solution
- About the Veritas System Recovery 21 Management Solution Home page
- Starting Veritas System Recovery 21 Management Solution
- Sending feedback to Veritas
- Preparing to manage the backups of client computers
- Discovering client computers on the network
- Installing the Symantec Management Agent on client computers
- Installing the Veritas System Recovery Plug-in on computers
- Uninstalling the Veritas System Recovery Plug-in on computers
- Installing Veritas System Recovery 21 and later or Veritas System Recovery 21 and later Linux Edition on client computers
- Installing Veritas System Recovery 18 or 16 on client computers
- Installing Veritas System Recovery 18 or 16 Linux Edition on client computers
- Uninstalling Veritas System Recovery-related products and components from client computers
- Generating the LightsOut Restore package in Veritas System Recovery 21 Management Solution
- Generating the LightsOut Restore 18 and 16 package
- Configuring and installing LightsOut Restore 21, 18, or 16 on client computers
- Uninstalling LightsOut Restore from client computers
- Updating the settings of a package
- Uninstalling Veritas System Recovery-related products from the Symantec Management Platform
- Adding or removing recovery point passwords
- About managing recovery point destinations
- Configuring a Dedicated Offsite Copy task
- About viewing filters
- About organizational views
- About managing Veritas System Recovery license policies
- Adding Veritas System Recovery license policies
- Deleting Veritas System Recovery license policies
- Assigning Veritas System Recovery licenses to client computers
- Unassigning Veritas System Recovery licenses from client computers
- Checking the license status of Veritas System Recovery on client computers
- Managing backups
- About backup policies
- Creating a basic backup policy
- Creating an advanced backup policy
- Creating an independent backup task
- Deploying a backup policy
- Deploying an existing backup policy as soon as possible
- Viewing the status of computers within a backup policy
- Editing a backup policy
- Editing the schedule of a backup policy
- Renaming a backup policy
- Disabling a backup policy
- Disabling a backup schedule
- Deleting a backup policy
- Viewing Veritas System Recovery details for a client computer
- Managing recovery points
- Managing the conversion of recovery points to virtual disks
- Managing Cloud Storage
- Remote recovery of drives and computers
- Local recovery of files, folders, drives, and computers
- About recovering lost data locally
- Recovering a computer locally
- Starting a computer locally by using Veritas System Recovery Disk
- Checking a hard disk for errors
- Recovering a computer locally by using a Veritas System Recovery Disk
- About using Restore Anyware to recover locally to a computer with different hardware
- Recovering files and folders locally by using Veritas System Recovery Disk
- About using the networking tools in Veritas System Recovery Disk
- Viewing the properties of a recovery point
- Viewing the properties of a drive within a recovery point
- About the Support Utilities on Veritas System Recovery Disk
- Monitoring computers and processes
- Appendix A. About backing up databases
- Appendix B. About Active Directory
- Appendix C. Backing up Microsoft virtual environments
- Appendix D. About Veritas System Recovery 21 Management Solution and Windows Server 2008 Core
- Index
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 21 Management Solution 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 21 Management Solution 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 21 Management Solution 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: