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
Granting permissions on the Exchange Server to enable database backups and restores, and Granular Recovery Technology operations
A user account must access mailboxes on the Exchange Server to perform Backup Exec operations. To gain access to the Exchange Server, you must have full access permissions on the Exchange Server. If you want to restrict the access on the Exchange Server, you can grant minimal permissions that enable users to perform database backups and restores and Granular Recovery Technology (GRT) operations.
Ensure that the user account has local administrator's rights on the Exchange Server and then use one of the following methods to grant the permissions:
Grant full access permissions at the Organization Administrators or Organization Management level. Veritas recommends that the user account have full Exchange permissions on the Exchange Server to perform Backup Exec operations.
Permissions are then propagated automatically to any new Exchange Servers that you add under the level at which the permissions are assigned.
Note:
You must have Exchange administrative permissions to grant permissions to other accounts.
If the user account cannot have full Exchange permissions for Backup Exec operations, you can grant minimal permissions. Minimal permissions let users perform database backups and restores and Granular Recovery Technology operations explicitly on each Exchange Server.
If you grant permissions explicitly and then add another Exchange Server, you must grant permissions explicitly on the added server as well.
You can grant minimal permissions for a user account that let you perform database backups and restores of an Exchange Server.
To grant full permissions for Microsoft Exchange 2010 or later, use an account with the Organization Management role.
To grant minimal permissions for a user account to perform database backups and restores of an Exchange Server
- Do one of the following:
To grant permissions for a user account using the Exchange Management Console in Microsoft Exchange 2010 or the Exchange Admin Center in Microsoft Exchange 2013 or later
Add the user account to the following roles:
Public Folder Management
Recipient Management
Server Management
To grant permissions for a user account using the Exchange Management Shell
Do the following in the order listed:
Type the following command:
new-RoleGroup -Name <role group name> -Roles @("Database Copies", "Databases", "Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients", "Recipient Policies" "Mail Enabled Public Folders", "Public Folders")
For example:
new-RoleGroup -Name BackupExecRoles -Roles @("Database Copies", "Databases", "Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients", "Recipient Policies", "Mail Enabled Public Folders", "Public Folders")
Type the following command:
Add-RoleGroupMember -Identity <role group name> -Member <name of the user account>
For example:
Add-RoleGroupMember -Identity BackupExecRoles -Member BackupExecUser
You can grant minimal permissions for a user account that let you support only Granular Recovery Technology (GRT) on an Exchange Server.
For more information about recipient scope, see the Microsoft Exchange documentation.
To grant permissions for a user account to support only Granular Recovery Technology on an Exchange Server using the Exchange Management Shell
- Type the following command:
New-ManagementRole -Name "<management role name>" -Parent ApplicationImpersonation
For example:
New-ManagementRole -Name "VeritasEWSImpersonationRole" -Parent ApplicationImpersonation
- Type the following command:
New-ManagementRoleAssignment -Role "<management role assignment name>" -User <user name> -Name "<assignment name>"
For example:
New-ManagementRoleAssignment -Role "VeritasEWSImpersonationRole" -User BackupExecUser -Name "BackupExecUser-EWSImpersonation"
- Do one of the following:
For Exchange 2010
Type the following command:
New-ThrottlingPolicy -Name "<throttling policy name>"" - EWSMaxConcurrency $null -PowerShellMaxConcurrency $null -EWSMaxSubscriptions $null
For example:
New-ThrottlingPolicy -Name "VeritasEWSRestoreThrottlingPolicy" - EWSMaxConcurrency $null -PowerShellMaxConcurrency $null -EWSPercentTimeInCAS $null -EWSPercentTimeInAD $null -EWSPercentTimeInMailboxRPC $null
For Exchange 2013 or later
Type the following command:
New-ThrottlingPolicy -Name "<throttling policy name>" -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsMaxConcurrency Unlimited -ExchangeMaxCmdlets Unlimited -MessageRateLimit Unlimited -PowershellCutoffbalance Unlimited -PowershellMaxBurst Unlimited -PowershellMaxCmdlets Unlimited -PowershellMaxConcurrency Unlimited -PowershellMaxOperations Unlimited -RecipientRateLimit Unlimited -ThrottlingPolicyScope Regular
For example:
New-ThrottlingPolicy -Name "VeritasEWSRestoreThrottlingPolicy" -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsMaxConcurrency Unlimited -ExchangeMaxCmdlets Unlimited -MessageRateLimit Unlimited -PowershellCutoffbalance Unlimited -PowershellMaxBurst Unlimited -PowershellMaxCmdlets Unlimited -PowershellMaxConcurrency Unlimited -PowershellMaxOperations Unlimited -RecipientRateLimit Unlimited -ThrottlingPolicyScope Regular
- Type the following command:
Set-Mailbox -Identity <user name> -ThrottlingPolicy "throttling policy name"
For example:
Set-Mailbox -Identity BackupExecUser -ThrottlingPolicy "VeritasEWSRestoreThrottlingPolicy"
- Type the following command:
Set-ThrottlingPolicyAssocation -Identity <user name> -ThrottlingPolicy "throttling policy name"
For example:
Set-ThrottlingPolicyAssociation -Identity BackupExecUser -ThrottlingPolicy "VeritasEWSRestoreThrottlingPolicy"