Veritas Backup Exec Administrator's Guide
- Introducing Backup Exec
- Installation
- Methods for installing the Agent for Windows
- Using a command prompt to install the Agent for Windows on a remote computer
- Using a command script to install the Agent for Windows
- Installing the Remote Administrator
- Installing Backup Exec using the command line (silent mode)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- Alerts and notifications
- Enabling active alerts and alert history to display on the Home tab
- Adding a recipient group for alert notifications
- Sending a notification when a job completes
- SNMP traps for Backup Exec alerts
- Disk-based and network-based storage
- Configuring disk storage
- Configuring disk cartridge storage
- Backup sets
- Cloud-based storage devices
- Amazon S3 cloud-based storage
- Google cloud-based storage
- Microsoft Azure cloud-based storage
- Private cloud-based storage
- About S3-Compatible Cloud Storage
- About the Veritas Backup Exec™ CloudConnect Optimizer
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Tape storage
- Robotic libraries in Backup Exec
- Creating robotic library partitions
- Managing tapes
- Creating media sets for tapes
- Labeling tape media
- Default media vaults
- Storage device pools
- Storage operations
- Conversion to virtual machines
- Configuration and settings
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Reports
- Creating a custom report
- List of Backup Exec standard reports
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Using Backup Exec in cluster environments
- Configurations for Backup Exec and Microsoft Cluster Servers
- Disaster recovery of a cluster
- Simplified Disaster Recovery
- Setting or changing the alternate location for the disaster recovery information file
- Creating a Simplified Disaster Recovery disk image
- Preparing to recover from a disaster by using Simplified Disaster Recovery
- Recovering a computer with Simplified Disaster Recovery
- Integration with Veritas™ Information Map
- Appendix A. Veritas Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Veritas Backup Exec Deduplication Option
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Veritas Backup Exec Agent for VMware
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Veritas Backup Exec Agent for Microsoft Hyper-V
- Backing up Microsoft Hyper-V virtual machines
- About instant recovery of a Hyper-V virtual machine
- About Recovery Ready for Hyper-V virtual machines
- Appendix E. Veritas Backup Exec Agent for Microsoft SQL Server
- Backing up SQL databases and transaction logs
- Restoring SQL databases and transaction logs
- Disaster recovery of a SQL Server
- Appendix F. Veritas Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Veritas Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Veritas Backup Exec Agent for Oracle on Windows or Linux Servers
- Configuring the Oracle Agent on Windows computers and Linux servers
- Configuring an Oracle instance on Windows computers
- Viewing an Oracle instance on Windows computers
- About authentication credentials on the Backup Exec server
- About backing up Oracle databases
- About restoring Oracle resources
- Appendix I. Veritas Backup Exec Agent for Enterprise Vault
- About backup methods for Enterprise Vault backup jobs
- Restoring Enterprise Vault
- About the Backup Exec Migrator for Enterprise Vault
- Configuring the Backup Exec Migrator
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Veritas Backup Exec Agent for Microsoft Active Directory
- Appendix K. Veritas Backup Exec Central Admin Server Option
- About installing the Central Admin Server feature
- What happens when CAS communication thresholds are reached
- About job delegation in CAS
- How to use Backup Exec server pools in CAS
- How centralized restore works in CAS
- Appendix L. Veritas Backup Exec Advanced Disk-based Backup Option
- Appendix M. Veritas Backup Exec NDMP Option
- About restoring and redirecting restore data for NDMP servers
- Viewing the properties of an NDMP server
- Viewing storage properties for an NDMP server
- Appendix N. Veritas Backup Exec Agent for Linux
- About installing the Agent for Linux
- About establishing trust for a remote Linux computer in the Backup Exec list of servers
- Editing configuration options for Linux computers
- About backing up a Linux computer by using the Agent for Linux
- About restoring data to Linux computers
- Editing the default backup job options for Linux computers
- Uninstalling the Agent for Linux
- Appendix O. Veritas Backup Exec Remote Media Agent for Linux
- About installing the Remote Media Agent for Linux
- About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers
- About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux
- About adding a Linux server as a Remote Media Agent for Linux
- Editing properties for the Remote Media Agent for Linux
- Creating a simulated tape library
- Viewing simulated tape libraries properties
- Appendix P. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
Creating a one-time conversion to a virtual machine
You can create a one-time conversion job to convert a running physical computer to a virtual machine without a separate backup job. A one-time conversion job can be scheduled to run at a later time, but it cannot be scheduled to run more than one time.
Only Full (Copy) backups are supported for this type of conversion. Incremental and differential backups are not supported for one-time conversions.
Note:
Copy backups are not supported in Hyper-V 2008 or 2008 R2. A crash-consistent conversion is created instead.
To create a one-time conversion to a virtual machine
- On the Backup and Restore tab, select the server that you want to convert to a virtual machine.
- In the Conversions group, click Convert to Virtual, and then click One-Time Convert to Virtual Machine.
- On the One-Time Convert to Virtual Machine Properties dialog box, in the Convert to Virtual box, click Edit.
- In the left pane, select Schedule to select when to run the conversion job:
To run the job immediately
Click Run now.
To schedule the conversion to run at a specific time
Click Run on, and then enter the date and time to run the job.
To create the conversion job without scheduling it
Select Create without a schedule. When you use this option, the job does not run at the time of creation and it does not have a recurring schedule. The job remains in a pending state until you choose to run it. You can use a third-party job automation or task scheduling tool to run the job later.
- (Optional) In the left pane, select Notification if you want to notify a recipient when the job completes.
- In the left pane, select Conversion Settings to set the options for the conversion.
- In the Convert for field, select either Hyper-V or VMware ESX/vCenter server.
- Configure the conversion options:
If you selected Hyper-V in step 7
Do the following to configure the conversion options:
Click the arrow in the Hyper-V server name field, select the name of the server where you want to create the virtual machine, and then click Add.
In the Destination drive or path field, enter the location on the physical computer where the virtual disks should be created. Enter a drive letter and path.
If you want to change the default virtual machine name, type the new name in the Virtual machine name field.
If you want to enable Backup Exec to overwrite a virtual machine if a virtual machine with the same name already exists, verify that the Overwrite the virtual machine if it already exists option is selected. If this option is not selected and the virtual machine name already exists, then the job fails.
In the Full path of Hyper-V Integration Components ISO image field, enter the location of your Hyper-V Integration Components ISO image. The ISO image is needed to make the virtual machine bootable.
Note:
This option is not available for Hyper-V servers that run on Windows 2016 or later. Such Hyper-V servers install integration services directly on the virtual machine either through a Windows update or a user-initiated download.
If you want to change the CPU count or amount of physical RAM for the destination virtual machine, on the Server configuration tab, enter the new amounts in the Desintation virtual machine fields.
If you want to change the disk type, the controller, or the virtual disk location for one of the disks, on the Disk configuration tab, click Edit disk configuration, and then enter the new information.
If you selected VMware ESX/vCenter server in step 7
Do the following to configure the conversion options:
Click the arrow in the ESX/vCenter server name field, and click the name of the server where you want to create the virtual machine.
Click the arrow in the Logon account field, and then select the appropriate logon account for the server that you selected.
Click Select next to the ESX/vCenter server name field. Backup Exec fills in the remaining information about the server.
Browse to select the virtual machine folder and resource pool that are associated with the server that you selected.
Note:
If you target an ESX server and select a resource pool, the newly created virtual machine is not added to the resource pool automatically. You can manually move the virtual machine into the appropriate resource pool after the conversion.
If you want to change the default virtual machine name, type the new name in the Virtual machine name field.
If you want to enable Backup Exec to overwrite a virtual machine if a virtual machine with the same name already exists, verify that the Overwrite the virtual machine if it already exists option is selected. If this option is not selected and the virtual machine name already exists, then the job fails.
In the Full path of VMware Tools ISO image field, enter the location of your VMware Tools ISO image. The path should be accessible with the default credentials. The path should also be local to the Backup Exec server. The ISO image is needed to make the virtual machine bootable.
Note:
In a CAS environment, this path should be local to the managed Backup Exec server to which the job is targeted.
If you want to change the CPU count or amount of physical RAM for the destination virtual machine, on the Server configuration tab, enter the new amounts in the Desintation virtual machine fields.
If you want to change the disk type, the controller, or the virtual disk location for one of the disks, on the Disk configuration tab, click Edit disk configuration, and then enter the new information.
- Click OK to save your selections.
- On the One-Time Convert to Virtual Machine Properties dialog box, click OK.