Backup Exec 21 Administrator's Guide
- Introducing Backup Exec
- 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)
- Updating Backup Exec with Veritas Update
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backing up data
- How Backup Exec catalogs work
- Job management and monitoring
- About the Job Monitor
- About the Job History
- Viewing the job log
- Error-handling rules for failed or canceled jobs
- 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 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
- Changing network and security options for Backup Exec
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Creating a custom report
- List of Backup Exec standard reports
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- GDPR Guard
- 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
- Performing manual disaster recovery
- Integration with Veritas™ Information Map
- Integration with Veritas SaaS Backup
- Forever Incremental Backup
- Appendix A. Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Backup Exec Deduplication Feature
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Backup Exec Agent for VMware
- About establishing trust for a vCenter/ESX(i) server
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. 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. 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. Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. 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. 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
- Configuring Enterprise Vault collections
- Configuring the Backup Exec Migrator to communicate with Enterprise Vault
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- About backing up Active Directory and ADAM/AD LDS
- Appendix K. Backup Exec Central Admin Server Feature
- 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. Backup Exec Advanced Disk-based Backup Feature
- Appendix M. Backup Exec NDMP Feature
- 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. 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. 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
Performing manual disaster recovery of a remote Backup Exec server or remote agent on a Windows computer
This procedure restores the computer's operating system to a pre-disaster state. It also restores the data files, except for those that a Backup Exec agent protects, such as the Agent for Microsoft Exchange Server. If Backup Exec agents protect any of the data, refer to the section in the Backup Exec Administrator's Guide on how to restore the data that is protected by the agent before beginning disaster recovery. The agent-protected data should be restored after the system recovery is complete. This procedure includes non-authoritative and authoritative restore of Active Directory for a domain controller.
These steps are intended for manual disaster recovery only. If Simplified Disaster Recovery (SDR) is enabled for the computer, you should use SDR for disaster recovery.
The following items are required for manual disaster recovery of a remote system:
A current full backup of the computer to be recovered and any subsequent incremental and differential backups.
The Windows installation media.
The database encryption key that was used to encrypt the Backup Exec Database. You should have exported the key to a secure location. You must retrieve it from that location to complete the recovery process.
If you want to perform an authoritative restore on a domain controller, DSRM credentials are needed.
If you recover a Windows computer that has BitLocker encryption enabled, you must enable BitLocker encryption again following the restore. See Microsoft's documentation for more information on BitLocker drive encryption.
Always log on to Window using the Administrator account or its equivalent during this procedure.
To run a manual disaster recovery of a remote Backup Exec server or remote agent on a Windows computer
At the remote computer, install the original version of Windows. The same Service Pack and patches need to be applied after Windows is installed. Note the following scenarios:
If you recover from an entire hard disk failure, use Windows setup to partition and format the new disk during installation. This Windows installation is necessary to provide Backup Exec with a target to which it can restore the system. The computer name, Windows directory, and the file system (such as NTFS) must be the same as the previous Windows installation. This basic installation is overwritten by the backed-up version, which restores your system configuration, application settings, and security settings.
If the system was a domain controller, in a specific domain or workgroup, do not join the domain or workgroup. Use the Computer Name Change dialog box to manually add a domain suffix to the computer name that matches the system's original domain or workgroup suffix.option on the
Change the new system name to match the original system name by performing the following steps in the order listed:
From Computer Name tab, click ., on the
If the domain or workgroup is joined, you must reestablish the domain or the workgroup trust relationship after the restore and the restart are complete.
On the Computer Name/Domain Changes dialog box, click .
If necessary, select, and then click .
Restart the system.
At the Backup Exec server, install the Backup Exec Agent for Windows on the remote computer.
After recovery, the Backup Exec logon account needs to be updated and the Backup Exec trust needs to be reestablished for the recovered remote server.
On the Backup and Restore tab, select the computer name, and then click .
Do one of the following:
If the restore methodis available, do the following in the order listed:
Click, and then click .
Click, and then click .
Select the point in time, ensuring that only the critical set is selected, and then click.
Select, and then click .
Ensure that the option, How do you want to maintain file integrity, hierarchy, and security for restore data panel.is selected, and then accept the default selections on the
For an authoritative restore of a domain controller, selectoption on the panel.
On the What additional tasks do you want to perform before and/or after a restore? panel, select any additional tasks that you want to run before or after a restore, and then click .
Schedule the job to run and then click.
On thesummary panel, click .
Do not restart the computer.
If the restore methodis not available, create a restore job and manually select individual system components for recovery. Do not restart the computer.
Your computer's operating system is now restored to a pre-disaster state, but you should not restart your system yet. Your data files have been restored if they were included in a restore job, except those protected by Backup Exec database agents.
Continue with one of the following:
For an authoritative restore of a domain controller, proceed to step 6.
If you want to perform a standalone server restore or a non-authoritative restore of a domain controller, the recovery is complete. Restart the computer after the restore job successfully completes. Proceed to step 7 to complete this procedure.
For an authoritative restore of a domain controller, do the following:
Make sure that the system is started into Directory Services Restore Mode for the first restart after the restore. Failing to do so may replicate the Active Directory once the Active Directory services are online. To prevent this replication, you can isolate the system from the network temporarily.
Pressduring startup. A menu appears that lets you diagnose and fix system startup problems.
Log on using your DSRM credentials.
Open a command prompt.
Type NTDSUTIL, and then press . For more information about running NTDSUTIL for Windows Server, see Microsoft's documentation.
Type Activate Instance NTDS, and then press .
Type Authoritative Restore, and then press .
Type the following command, and then press:
restore subtree ou=OU_Name,dc=Domain_Name,dc=xxx
In this command, <ou_name> is the name of the organizational unit that you want to restore, <domain_name> is the domain name that the OU resides in, and <xxx> is the top-level domain name of the domain controller, such as com, org, or net.
Repeat these steps as many times as necessary for the specific objects that you need to restore.
After you have finished restoring Active Directory information, exit NTDSUITIL.
Restart the computer.
When you launch Backup Exec, the program prompts you for the database encryption key file.
Complete the following steps to import the database encryption key file:
Locate the database encryption key from the secure location to which you backed it up. Backup Exec indicates the name of the key that needs to be restored.
Copy the file and then paste it in the Data folder in the directory in which you installed Backup Exec.
Log on to Backup Exec.