Backup Exec 20.1 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)
- 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
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- 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
- Performing manual disaster recovery
- Integration with Veritas™ Information Map
- 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
- 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
Restoring Microsoft SharePoint data
The Agent for Microsoft SharePoint lets you restore the following types of Microsoft SharePoint data to the original location or you can redirect the restore to a new location:
SharePoint individual items such as documents, images, sites, subsites, lists, and list items.
SharePoint web applications or portal sites and their associated content.
SharePoint farm components such as configuration databases, service applications, shared service providers, or other components.
SharePoint individual items such as documents, sites, and list items located through search.
You should keep in mind the following things when you restore SharePoint data:
When you restore SharePoint data, individual SharePoint documents are always restored to SharePoint document libraries as checked out.
The documents are checked out using the same credentials as the logon account that you use for the restore. The documents must be checked in or published by that user before other users can use them.
If you try to restore over a document that is checked out, the restore may fail. The restore fails if the document is checked out to a user that differs from the logon account credentials that are used for the restore.
Backup Exec also lets you restore individual documents, images, sites, subsites, lists, and list items from SharePoint database backups. To restore individual items from SharePoint database backups, ensure that the following Microsoft SharePoint option is selected during the backup job:
Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual objects from the database backup
Backup Exec does not support the restore of granular items from compressed databases or encrypted databases.
Backup Exec lets you redirect the restore of the following:
Redirect SharePoint file-based data, such as documents and images that have been uploaded to a document library or are attached to list items, to an NTFS file system for SharePoint Server 2010, and SharePoint Foundation 2010.
Backup Exec can extract and re-insert files directly into a SharePoint 2013 content database. However, the files cannot be selected for file system level redirection. SharePoint 2013 content databases files are stored as BLOBS, but in a shredded format. As a result, Backup Exec cannot redirect the restore of the shredded BLOBS to a file system.
Redirect the restore of individual items such as documents, sites, and list items from one site to another site.
When you redirect a restore from one site to another site, the restored items inherit the security permissions of the parent item to which they are restored. If the site is in a different SharePoint farm, the versions of SharePoint must be the same.
You must use the same logon account for the original web server and the server in the site collection when you redirect the restore. You should also ensure that both of the servers use the same NetBIOS name, fully qualified domain name, or IP address.
Restore SharePoint databases to an alternate SQL instance.
You can use the database to do the following:
Manually harvest data using the SharePoint Central Administration console in SharePoint 2010/2013.
Manually attach to a SharePoint web application.
Redirect SharePoint web application content databases to an alternate web application.
The destination for the web application must be online and be of the same topology as the web application that was backed up. If the web application is in a different SharePoint farm, the versions of SharePoint must be the same.
When you restore SharePoint Portal document library data, any documents that exist in the selected destination and that have the same name as the documents being restored may be overwritten. You can select whether they should be overwritten in the properties for the restore job.
For more information about the different types of SharePoint content, see the Microsoft SharePoint documentation.
To restore Microsoft SharePoint data
- On the Backup and Restore tab, right-click the server for which you want to restore data, and then click Restore.
- Select Microsoft SharePoint, and then click Next.
- Follow the Restore Wizard prompts to restore the data.