Symantec Backup Exec 15 Administrator's Guide
7 likes12,356 views
The document provides instructions for administrators on how to use Symantec Backup Exec 15, including installation, configuration, backup and recovery procedures. It covers topics such as installing Backup Exec agents, configuring backup jobs, monitoring job status, managing storage, and restoring data. Contact and licensing information is also included for Technical Support and maintenance contracts.
![Table 14-3 Types of encryption keys (continued)
DescriptionKey type
Anyone can use the key to encrypt data during a backup job,
but users other than the key owner must know the pass
phrase. If a user other than the key owner tries to restore the
encrypted data, Backup Exec prompts the user for the pass
phrase. If you cannot supply the correct pass phrase for the
key, you cannot restore the data.
Restricted
Pass phrases
Encryption keys require a pass phrase, which is similar to a password. Pass phrases
are usually longer than passwords and are comprised of several words or groups
of text. A good pass phrase is between 8 and 128 characters. The minimum number
of characters for 128-bit AES encryption is eight. The minimum number of characters
for 256-bit AES encryption is 16. Symantec recommends that you use more than
the minimum number of characters.
Note: Hardware encryption that uses the T10 standard requires 256-bit AES. Backup
Exec does not let you enable hardware encryption for a job unless it uses at least
a 16-character pass phrase.
Also, a good pass phrase contains a combination of upper and lower case letters,
numbers, and special characters. You should avoid using literary quotations in pass
phrases.
A pass phrase can include only printable ASCII characters, which are characters
32 through 126. ASCII character 32 is the space character, which is entered using
the space bar on the keyboard. ASCII characters 33 through 126 include the
following:
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ
[]^_‘abcdefghijklmnopqrstuvwxyz{|}~
See “Encryption key management” on page 578.
Encryption key management
When a user creates an encryption key, Backup Exec marks that key with an
identifier based on the logged-on user’s security identifier. The person who creates
the key becomes the owner of the key.
See “Using encryption with Backup Exec” on page 575.
578Configuration and settings
Encryption key management](https://image.slidesharecdn.com/beadminen-150408145958-conversion-gate01/85/Symantec-Backup-Exec-15-Administrator-s-Guide-578-320.jpg)
Symantec Backup Exec 15 Administrator's Guide
- 1. Symantec Backup Exec 15 Administrator's Guide
- 2. Documentation version: 15 Legal Notice Copyright © 2015 Symantec Corporation. All rights reserved. Last updated: February 5, 2015 Symantec, the Symantec Logo, the Checkmark Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
- 3. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com
- 4. Technical Support Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec’s support offerings include the following: ■ A range of support options that give you the flexibility to select the right amount of service for any size organization ■ Telephone and/or Web-based support that provides rapid response and up-to-the-minute information ■ Upgrade assurance that delivers software upgrades ■ Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis ■ Premium service offerings that include Account Management Services For information about Symantec’s support offerings, you can visit our website at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Contacting Technical Support Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: ■ Product release level ■ Hardware information
- 5. ■ Available memory, disk space, and NIC information ■ Operating system ■ Version and patch level ■ Network topology ■ Router, gateway, and IP address information ■ Problem description: ■ Error messages and log files ■ Troubleshooting that was performed before contacting Symantec ■ Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/ Customer service Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues: ■ Questions regarding product licensing or serialization ■ Product registration updates, such as address or name changes ■ General product information (features, language availability, local dealers) ■ Latest information about product updates and upgrades ■ Information about upgrade assurance and support contracts ■ Information about the Symantec Buying Programs ■ Advice about Symantec's technical support options ■ Nontechnical presales questions ■ Issues that are related to CD-ROMs, DVDs, or manuals
- 6. Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: customercare_apac@symantec.comAsia-Pacific and Japan semea@symantec.comEurope, Middle-East, and Africa supportsolutions@symantec.comNorth America and Latin America
- 7. Technical Support ............................................................................................... 4 Chapter 1 Introducing Backup Exec 15 ............................................. 37 About Backup Exec ...................................................................... 37 How Backup Exec works ................................................................ 37 Chapter 2 Installation ........................................................................... 39 About the Backup Exec installation process and licensing options .......... 40 Backup Exec preinstallation checklist ............................................... 43 Running the Environment Check before installing or upgrading Backup Exec .................................................................................... 44 Microsoft SQL Server 2008 Express Edition components installed with Backup Exec ......................................................................... 46 Backup Exec’s standard features ..................................................... 47 System requirements for Backup Exec .............................................. 49 Installing Backup Exec by using the Installation Wizard ........................ 52 Installing additional Backup Exec options to the local Backup Exec server .................................................................................. 62 Push-installing Backup Exec to remote computers .............................. 64 Methods for installing the Agent for Windows ..................................... 72 Push-installing the Agent for Windows to remote computers ............ 73 Installing updates to the Agent for Windows on remote computers ....................................................................... 79 Installing the Agent for Windows in an Active Directory network .......................................................................... 80 Using a command prompt to install the Agent for Windows on a remote computer .............................................................. 84 Using a command script to install the Agent for Windows ................ 87 Installing the Remote Administrator ................................................. 88 Installing the Remote Administrator using the command line ........... 89 Running the Remote Administrator ............................................. 91 Installing Backup Exec using the command line (silent mode) ................ 94 Command line switches for silent mode installation of Backup Exec .............................................................................. 94 Creating and using installation parameter files ............................ 103 Contents
- 8. Installing a trial version of Backup Exec agents and options ................. 104 About the installation log .............................................................. 104 Viewing the Installation Summary Report ......................................... 105 Repairing Backup Exec ................................................................ 106 Updating Backup Exec with LiveUpdate .......................................... 106 Viewing installed updates ............................................................. 109 Viewing license information ........................................................... 109 Backup Exec maintenance contract information ................................ 110 Updating expired maintenance contracts ................................... 110 Managing maintenance contract customer numbers .................... 111 About upgrading from previous versions of Backup Exec to Backup Exec 15 .............................................................................. 111 Upgrade checklist for Backup Exec 2010 and earlier .................... 113 Using the Migration Report to determine how existing jobs changed after an upgrade to Backup Exec 15 ................................... 115 Post-installation tasks .................................................................. 116 Uninstalling Backup Exec ............................................................. 117 Uninstalling Backup Exec using the command line ............................. 117 Uninstalling Backup Exec options from the local Backup Exec server ................................................................................. 118 Chapter 3 Getting Started .................................................................. 120 About the Backup Exec Administration Console ................................ 120 Displaying the version information for Backup Exec ........................... 123 How to sort, filter, and copy information on the Backup Exec Administration Console .......................................................... 123 Customizing views on the Backup Exec Administration Console ........... 125 Configuring the Home tab ............................................................. 126 Configuring the Symantec RSS Reader ........................................... 130 Creating a disaster preparation plan (DPP) ...................................... 131 Getting started with backups ......................................................... 133 Chapter 4 Backups ............................................................................... 136 How to prepare for your first backup with Backup Exec ....................... 138 Required user rights for backup jobs ............................................... 139 About the list of servers on the Backup and Restore tab ..................... 139 Adding servers that you want to back up to the list of servers on the Backup and Restore tab ......................................................... 140 Removing servers from the list of servers on the Backup and Restore tab ..................................................................................... 141 Creating a server group ............................................................... 142 Hiding or viewing server groups on the Backup and Restore tab ........... 143 8Contents
- 9. Adding servers to a server group ................................................... 143 Removing servers from a server group ............................................ 144 Editing a server group .................................................................. 144 Moving servers to the Retired Servers server group ........................... 145 Moving retired servers back to the All Servers server group ................. 146 Removing server groups from Backup Exec ..................................... 146 Backing up data ......................................................................... 146 How Backup Exec backs up and restores volumes that are enabled for deduplication in Windows ............................................. 156 How Backup Exec backs up and restores Microsoft Virtual Hard Disk (vhd) files ............................................................... 157 About selecting data to back up .................................................... 157 Changing the order in which backup sources are backed up ................ 163 Excluding files from backups ......................................................... 166 Including specific files with a backup job's backup selections ............... 169 About backing up critical system components ................................... 171 Backup Exec Shadow Copy Components file system ......................... 175 Backup methods in Backup Exec ................................................... 176 Configuring backup methods for backup jobs ................................... 184 How Backup Exec determines if a file has been backed up .................. 187 Configuring Backup Exec to automatically delete files after a backup ............................................................................... 190 Configuring network options for backup jobs ..................................... 192 Running the next scheduled backup job before its scheduled time ................................................................................... 193 Editing backup definitions ............................................................. 194 Testing credentials for backup sources ............................................ 199 Replacing the credentials for a backup source .................................. 200 Creating new credentials for a backup source ................................... 201 Deleting retired or unused backup sources from the Credentials pane .................................................................................. 202 How job scheduling works in Backup Exec ....................................... 203 Including a specific date in the schedule for a backup job .................... 204 Preventing backup jobs from running on a specific date ...................... 206 Viewing all scheduled backup jobs on a calendar .............................. 207 Adding a stage to a backup definition .............................................. 207 Editing a stage ........................................................................... 209 Duplicating backup sets or a job history manually .............................. 209 Running a test run job manually ..................................................... 214 Verifying backed up data manually ................................................. 215 Copying data from a virtual tape library to a physical tape device using DirectCopy to tape ................................................................ 217 9Contents
- 10. Chapter 5 Restores ............................................................................... 219 Methods for restoring data in Backup Exec ...................................... 220 Searching for data to restore ......................................................... 222 Restoring data from a server, a backup set, a backup job, or a storage device ................................................................................ 222 Restoring file system data ............................................................ 226 Performing a complete online restore of a Microsoft Windows computer ............................................................................ 227 Restoring System State ............................................................... 228 Installing a new Windows Server domain controller into an existing domain by using a redirected restore ........................................ 230 Restoring Backup Exec Shadow Copy Components .......................... 232 Restoring utility partitions or Unified Extensible Firmware Interface system partitions .................................................................. 233 About restoring encrypted data ...................................................... 234 About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec ................................................................. 234 Canceling a restore job ................................................................ 234 How Backup Exec catalogs work ................................................... 235 Configuring default options for catalogs ..................................... 236 Cataloging backup sets ................................................................ 238 Chapter 6 Job management and monitoring .................................. 240 How to monitor and manage jobs in Backup Exec ............................. 240 About the Job Monitor .................................................................. 242 Viewing job activity details for active jobs ................................... 244 Canceling an active job .......................................................... 244 Holding jobs ........................................................................ 245 Removing the hold on jobs ..................................................... 246 Holding the job queue ............................................................ 247 Removing the hold on the job queue ......................................... 247 Running a scheduled job immediately ....................................... 248 Changing the priority for a scheduled job ................................... 249 Deleting scheduled jobs ......................................................... 250 About the Job History .................................................................. 251 Viewing the history of a job ..................................................... 252 Deleting a job from the Job History ........................................... 252 Running a job from the Job History ........................................... 253 Viewing the job log ..................................................................... 254 Finding text in the job log ........................................................ 254 Printing the job log ................................................................ 256 Saving the job log ................................................................. 256 10Contents
- 11. Linking from the job log to the Symantec Technical Support website ......................................................................... 257 How to use job logs with vertical applications .............................. 257 Configuring default job log options ............................................ 258 Error-handling rules for failed or canceled jobs .................................. 259 Creating a custom error-handling rule ....................................... 260 Enabling or disabling error-handling rules .................................. 261 Deleting a custom error-handling rule ........................................ 261 Enabling an error-handling rule for a failed job ............................ 262 Custom error-handling rule for recovered jobs ............................ 262 About the cluster failover error-handling rule ............................... 263 List of job statuses in Backup Exec ................................................. 264 Setting job status and recovery options ........................................... 269 Chapter 7 Alerts and notifications .................................................... 272 Alerts and notifications in Backup Exec ........................................... 273 Where to find alerts in Backup Exec ............................................... 274 Enabling active alerts and alert history to display on the Home tab ..................................................................................... 276 Active alerts properties .......................................................... 277 Viewing the alert history for a server or a storage device ..................... 278 Deleting an alert from alert history .................................................. 278 Copying alert text to a document or email ........................................ 279 Filtering alerts ............................................................................ 279 Viewing the job log from an alert .................................................... 280 Responding to active alerts ........................................................... 280 Clearing all informational alerts manually ......................................... 281 Setting up notification for alerts ...................................................... 281 Configuring email or text message notification for alerts ...................... 282 Adding recipients for notification .................................................... 284 Adding a recipient group for alert notifications ................................... 286 Removing a recipient from a group ........................................... 287 Disabling email or text message alert notification for a recipient ............ 287 Editing recipient notification properties ............................................ 288 Deleting recipients ...................................................................... 288 Configuring alert categories .......................................................... 289 Assigning recipients to receive notifications for specific alert categories ........................................................................... 291 Sending a notification when a job completes .................................... 291 Notification options for jobs ..................................................... 292 Disabling notifications for a specific alert category ............................. 292 Configuring default alert settings .................................................... 293 11Contents
- 12. Enabling or disabling pop-up alerts ................................................. 294 SNMP traps for Backup Exec alerts ................................................ 295 Installing and configuring the SNMP system service ..................... 298 Installing the Windows Management Instrumentation performance counter provider ............................................................. 298 Installing the Windows Management Instrumentation provider for SNMP .......................................................................... 299 Uninstalling the Windows Management Instrumentation performance counter provider ........................................... 299 Uninstalling the Windows Management Instrumentation provider for SNMP ...................................................................... 299 Chapter 8 Disk-based and network-based storage ....................... 300 Features and types of disk-based storage and network-based storage ............................................................................... 300 Storage trending statuses for disk storage and virtual disks ................. 303 Setting low disk space thresholds on disk-based storage .................... 304 Configuring disk storage ............................................................... 305 Changing the location of a disk storage device ............................ 307 Editing disk storage properties ................................................. 308 How to restore data from a reattached or reinserted disk-based storage device ................................................................................ 314 Configuring disk cartridge storage .................................................. 315 Editing disk cartridge properties ............................................... 316 Editing disk cartridge media properties ...................................... 320 How data lifecycle management (DLM) deletes expired backup sets on disk-based storage ........................................................... 322 Backup sets .............................................................................. 329 Changing the expiration date of backup sets on disk-based storage ......................................................................... 332 Retaining backup sets on disk-based storage to prevent them from expiring .................................................................. 333 Releasing retained backup sets on disk-based storage ................. 334 Viewing the contents or properties of backup sets ....................... 335 Chapter 9 Legacy backup-to-disk folders ........................................ 337 Legacy backup-to-disk folders ...................................................... 337 Changing the name or description of a legacy backup-to-disk folder ........................................................................... 338 Changing the buffered read setting for a legacy backup-to-disk folder ........................................................................... 338 Changing the location of a legacy backup-to-disk folder ................ 339 12Contents
- 13. Recreating a legacy backup-to-disk folder and its contents ............ 340 Restoring data from a legacy backup-to-disk folder ...................... 340 Chapter 10 Tape storage ....................................................................... 343 Support for tape drives and robotic libraries ...................................... 344 About the Virtual Tape Library Unlimited Drive Option ........................ 345 About the Library Expansion Option ............................................... 345 Adding or replacing devices with the Hot-swappable Device Wizard ................................................................................ 345 Installing Symantec tape device drivers .......................................... 347 Editing tape drive properties .......................................................... 348 Viewing tape drive statistics .......................................................... 353 Robotic libraries in Backup Exec .................................................... 353 Requirements for setting up robotic library hardware .................... 354 Inventorying robotic libraries when Backup Exec services start ............................................................................. 355 Configuring barcode rules for a robotic library ............................ 355 Initializing a robotic library when the Backup Exec service starts ............................................................................ 359 Defining a cleaning slot ......................................................... 360 Editing robotic library properties ............................................... 360 Creating robotic library partitions .................................................... 361 Changing the name of a robotic library partition ........................... 363 Adding or removing tape drives in a robotic library partition ........... 363 Reassigning a slot base number for robotic libraries ..................... 363 Editing robotic library slot properties ......................................... 364 Removing or reconfiguring robotic library partitions ...................... 365 Managing tapes ......................................................................... 366 Default media sets ................................................................ 367 Overwrite protection periods and append periods in media sets ............................................................................. 370 Creating media sets for tapes .................................................. 374 Changing the overwrite protection period or the append period for a media set ................................................................... 377 Changing the name and description of a media set ...................... 379 Changing the media vault or vaulting periods for a media set ................................................................................... 379 Deleting a media set .............................................................. 380 Renaming a media set ........................................................... 380 Media overwrite protection levels for tape media ......................... 380 Overwriting allocated or imported tape media ............................. 381 13Contents
- 14. How Backup Exec searches for overwritable media in tape drives ................................................................................... 381 Viewing tapes that are used by a job ......................................... 384 Labeling tape media .................................................................... 384 About labeling imported tape media ......................................... 386 How barcode labels become media labels for tapes ..................... 386 Renaming a tape media label ................................................. 387 How WORM media is used in Backup Exec ..................................... 387 Default media vaults .................................................................... 388 Changing the name or description of a media vault ...................... 389 Creating media vault rules to move tape media to and from media vaults ........................................................................... 390 Updating the tape media location in media vaults ........................ 391 Deleting a media vault ........................................................... 391 Moving tape media to a vault ................................................... 392 Retiring damaged tape media ....................................................... 392 Deleting tape media .................................................................... 393 Erasing tape or disk cartridge media ............................................... 393 About cataloging tape or disk cartridge media that contains encrypted backup sets ......................................................................... 395 Associating tape media with a media set ......................................... 395 Editing tape media properties ........................................................ 396 Tape media rotation strategies ....................................................... 398 Chapter 11 Storage device pools ......................................................... 402 Creating storage device pools ....................................................... 402 Specifying a default selection method for a device in a storage device pool ................................................................................... 405 Viewing jobs, job histories, and active alerts for a storage device pool ................................................................................... 405 Adding or removing devices in a storage device pool ......................... 406 Chapter 12 Storage operations ............................................................ 407 About storage operation jobs ......................................................... 408 Storage tab overview in Backup Exec ............................................. 409 Using the Configure Storage wizard ................................................ 412 Viewing details for multiple storage devices ...................................... 415 Sending a notification when a scheduled storage operation job completes ........................................................................... 416 Scheduling a storage operation job ................................................ 416 Editing global settings for storage ................................................... 423 Sharing storage devices ............................................................... 432 14Contents
- 15. Deleting a storage device ............................................................. 433 Changing the state of a storage device to online ............................... 434 Renaming a storage device .......................................................... 434 Viewing jobs, job histories, backup sets, and active alerts for storage devices ............................................................................... 435 Cataloging a storage device .......................................................... 435 Scanning a storage device ........................................................... 436 Inventorying a storage device ........................................................ 437 Inventorying and cataloging a storage device ................................... 438 Pausing and unpausing a storage device ......................................... 438 Disabling and enabling a storage device .......................................... 439 Initializing a robotic library ............................................................ 439 Formatting a tape as a WORM tape ................................................ 440 Retensioning a tape .................................................................... 440 Formatting a tape in a tape drive .................................................... 440 Ejecting media from a disk cartridge or tape drive .............................. 441 Cleaning a robotic library drive ...................................................... 442 Importing media to Backup Exec ................................................... 443 Exporting media and expired media ................................................ 450 Locking and unlocking the robotic library’s front portal ........................ 453 Backup Exec server and storage device states ................................. 459 Chapter 13 Conversion to virtual machines ...................................... 463 How conversion of physical computers to virtual machines works in Backup Exec ....................................................................... 463 Requirements for conversion to virtual machine jobs .......................... 471 Converting to a virtual machine simultaneously with a backup job ......... 472 Converting to a virtual machine after a backup job ............................. 477 Adding a conversion to virtual machine stage to a backup job .............. 483 Converting to a virtual machine from a point in time ........................... 488 Creating a one-time conversion to a virtual machine .......................... 490 Setting default options for conversion to virtual machine jobs ............... 494 Chapter 14 Configuration and settings .............................................. 498 Changing default backup job settings .............................................. 500 Configuring schedules for backup jobs ............................................ 504 Configuring storage options for backup jobs ..................................... 512 Configuring automatic test run jobs for backup jobs ........................... 518 Configuring automatic verify operations for backup jobs ...................... 519 Configuring delayed catalog operations to improve backup performance ........................................................................ 521 Configuring Advanced Open File options for backup jobs .................... 525 15Contents
- 16. Configuring checkpoint restart ....................................................... 528 Configuring Backup Exec to work with Symantec Endpoint Protection ........................................................................... 530 Configuring pre/post commands for backup jobs ............................... 532 Configuring file and folder options for backup jobs ............................. 537 Setting default schedule options for rule-based jobs and run now jobs ................................................................................... 544 Excluding dates from the backup schedule for all backups .................. 547 Removing dates from the list of excluded dates ................................. 549 Exporting a list of dates that are excluded from all backups to another server ................................................................................. 550 Changing the default preferences .................................................. 550 Configuring the default setting for backing up multiple servers or applications ......................................................................... 551 Configuring database maintenance and security ............................... 552 Exporting the Backup Exec Database encryption key ......................... 555 Refreshing Backup Exec Database encryption keys ........................... 557 Configuring encryption for the connection to the Backup Exec Database ............................................................................ 558 Scheduling Backup Exec to check logon accounts ............................. 562 Configuring Backup Exec to discover data to back up ......................... 563 Adding discovered servers to the list of servers in Backup Exec ........... 565 Backup networks ........................................................................ 566 Changing network and security options for Backup Exec ..................... 568 Using Backup Exec with firewalls ................................................... 570 Backup Exec ports ................................................................ 572 Backup Exec listening ports .................................................... 574 About enabling a SQL instance behind a firewall ......................... 575 Using encryption with Backup Exec ................................................ 575 Encryption key management ......................................................... 578 Creating encryption keys .............................................................. 579 Replacing an encryption key ......................................................... 581 Deleting encryption keys .............................................................. 582 Granular Recovery Technology ...................................................... 583 Setting default Granular Recovery Technology (GRT) options .............. 589 DBA-initiated job templates ........................................................... 590 Creating DBA-initiated job templates ............................................... 591 Editing DBA-inititated job templates ................................................ 592 Deleting DBA-initiated job templates ............................................... 592 Storage options for DBA-initiated jobs ....................................... 593 General options for DBA-initiated jobs ....................................... 598 Network options for DBA-initiated jobs ...................................... 598 Duplicate job settings for DBA-initiated jobs ............................... 599 16Contents
- 17. Backup Exec logon accounts ........................................................ 603 Creating a Backup Exec logon account ..................................... 605 Editing a Backup Exec logon account ....................................... 607 Changing the password for a Backup Exec logon account ............. 609 Replacing a Backup Exec logon account ................................... 609 Deleting a Backup Exec logon account ...................................... 610 Changing your default Backup Exec logon account ...................... 611 Creating a new Backup Exec System Logon Account ................... 612 Copying logon account information to another Backup Exec server ........................................................................... 613 Testing logon accounts .......................................................... 613 Starting and stopping Backup Exec services .................................... 614 Changing the credentials for a service account ................................. 614 Changing startup options for Backup Exec services ........................... 616 Configuring audit logs .................................................................. 617 Viewing the audit log ................................................................... 618 Removing entries from the audit log ................................................ 618 Saving an audit log to a text file ..................................................... 619 Copying configuration settings to another Backup Exec server ............. 619 Viewing server properties ............................................................. 620 Chapter 15 Reports ................................................................................ 622 Reports in Backup Exec ............................................................... 622 Running a report now .................................................................. 624 Scheduling a report ..................................................................... 624 Creating a custom report .............................................................. 626 Adding or removing fields on a custom report ............................. 630 Changing filters for a custom report .......................................... 631 Changing the way data is grouped or sorted in a custom report ........................................................................... 633 Changing graph options in custom reports ................................. 634 Previewing custom reports ...................................................... 634 Copying a custom report ........................................................ 635 Saving a report ........................................................................... 635 Printing a report from the Backup Exec Report Viewer ........................ 636 Viewing completed reports ............................................................ 636 Editing a report ........................................................................... 637 Re-running a completed report ...................................................... 637 Deleting a report ........................................................................ 637 Setting defaults for standard and custom reports ............................... 638 Viewing report properties .............................................................. 639 List of Backup Exec standard reports .............................................. 640 17Contents
- 18. Alert History report ................................................................ 645 Alert History By Backup Exec Server report ................................ 646 Archive Job Success Rate report ............................................. 646 Archive Selections by Archive Rules and Retention Categories report ........................................................................... 647 Audit Log report .................................................................... 648 Backup Job Success Rate report ............................................. 648 Backup Recommendations report ............................................ 648 Backup Resource Success Rate report ..................................... 649 Backup Sets by Media Set report ............................................. 649 Backup Size By Resource report .............................................. 650 Daily Device Utilization report .................................................. 651 Deduplication Device Summary report ...................................... 652 Deduplication Summary report ................................................ 653 Device Summary report ......................................................... 653 Disk Storage Summary report ................................................. 654 Error-Handling Rules report .................................................... 655 Event Recipients report .......................................................... 656 Exchange Mailbox Group Archive Settings report ........................ 657 Failed Archive Jobs report ...................................................... 657 Failed Backup Jobs report ...................................................... 658 File System Archive Settings report .......................................... 659 Jobs Summary report ............................................................ 659 Managed Backup Exec Servers report ...................................... 660 Media Audit report ................................................................ 662 Media Errors report ............................................................... 663 Media Required for Recovery report ......................................... 663 Media Summary report .......................................................... 664 Media Vault Contents report .................................................... 664 Move Media to Vault report ..................................................... 665 Operations Overview report .................................................... 666 Overnight Archive Summary report ........................................... 668 Overnight Summary report ...................................................... 669 Problem Files report .............................................................. 670 Recently Written Media report ................................................. 671 Resource Protected Recently report ......................................... 671 Resource Risk Assessment report ............................................ 672 Restore Set Details by Resource report ..................................... 673 Retrieve Media from Vault report .............................................. 673 Robotic Library Inventory report ............................................... 674 Scheduled Server Workload report ........................................... 675 Scratch Media Availability report .............................................. 675 Test Run Results report .......................................................... 676 18Contents
- 19. Vault Store Usage Details report .............................................. 677 Vault Store Usage Summary report .......................................... 678 Chapter 16 Troubleshooting Backup Exec ........................................ 679 Troubleshooting hardware-related issues in Backup Exec ................... 680 How to get more information about alerts and error messages ............. 684 Troubleshooting backup issues in Backup Exec ................................ 684 Troubleshooting failed components in the SAN ................................ 687 Troubleshooting offline storage devices in a SAN ....................... 687 Finding hardware errors in a SAN ............................................ 689 Resetting the SAN ................................................................ 690 Bringing storage devices online after an unsafe device removal event in a SAN ............................................................... 691 How to improve Backup Exec's performance .................................... 691 Accessing Symantec Online .......................................................... 692 Searching the Symantec Knowledge Base ....................................... 693 Contacting Backup Exec Technical Support ..................................... 693 Using Symantec Remote Assistance .............................................. 694 Managing your Backup Exec support cases ..................................... 694 About Backup Exec diagnostic tools ............................................... 694 Running the Symantec Help Tool (SymHelp) .................................... 695 Generating a diagnostic file for troubleshooting Backup Exec ............... 696 Command line switches for a diagnostic file ............................... 697 Running the begather utility to troubleshoot Backup Exec components on Linux servers ................................................................... 700 Using the Backup Exec Debug Monitor for troubleshooting .................. 701 About the Backup Exec debug tool ................................................. 701 Chapter 17 Using Backup Exec in cluster environments ................ 702 About Backup Exec and clusters .................................................... 703 Requirements for clustering Backup Exec in a Microsoft Cluster Server environment ........................................................................ 703 How Backup Exec works in a Microsoft Cluster Server environment ........................................................................ 705 Requirements for installing Backup Exec on a Microsoft Cluster Server ................................................................................ 705 Installing Backup Exec on a Microsoft Cluster Server ........................ 707 Upgrading Backup Exec on a Microsoft cluster ................................. 708 Installing additional Backup Exec options on a Microsoft cluster .......... 708 Uninstalling Backup Exec from a Microsoft cluster ............................. 709 Creating storage device pools for Microsoft Cluster Servers ................ 709 Specifying a different failover node ................................................. 710 19Contents
- 20. Designating a new central administration server in a Microsoft Cluster Server ................................................................................ 711 Configurations for Backup Exec and Microsoft Cluster Servers ............. 713 Two-node cluster with locally attached storage devices ................. 714 Two-node cluster with tape devices on a shared SCSI bus ............ 715 Configuring a shared SCSI bus for tape devices .......................... 716 Multi-node clusters on a fibre channel SAN with the Central Admin Server Option ................................................................ 718 Using the Central Admin Server Option with Microsoft clusters and a storage area network ............................................................. 719 About backing up Microsoft Cluster Servers ..................................... 720 About restoring data to a Microsoft cluster ....................................... 721 Disaster recovery of a cluster ........................................................ 721 Using Simplified Disaster Recovery to prepare for disaster recovery of a cluster .................................................................... 722 Recovering nodes on the cluster using Simplified Disaster Recovery ...................................................................... 723 Recovering Backup Exec on a Microsoft cluster using Simplified Disaster Recovery .......................................................... 724 Recovering the entire cluster using a manual disaster recovery procedure ..................................................................... 724 Restoring the Microsoft Cluster Server data files ............................... 725 Recovering all shared disks in a Microsoft cluster .............................. 726 Recovering Backup Exec in a Microsoft cluster ................................. 727 Changing the Quorum disk signature for clusters on Windows Server 2003 .................................................................................. 727 Manually joining two cluster disk groups and resynchronizing volumes .............................................................................. 728 Troubleshooting clusters .............................................................. 728 Chapter 18 Simplified Disaster Recovery .......................................... 730 About Simplified Disaster Recovery ................................................ 730 Requirements for using Simplified Disaster Recovery ........................ 731 Preparing computers for use with Simplified Disaster Recovery ............ 734 How to ensure that backups are enabled for Simplified Disaster Recovery ............................................................................ 738 How Simplified Disaster Recovery uses disaster recovery information files .................................................................................... 740 Setting or changing the alternate location for the disaster recovery information file ..................................................................... 742 Changing the default path for the disaster recovery information files .............................................................................. 743 20Contents
- 21. Disaster recovery information file data paths .............................. 743 Creating a Simplified Disaster Recovery disk image ........................... 745 Contents of the Simplified Disaster Recovery disk image .............. 755 User scenarios when a user starts the Create Recovery Disk Wizard .......................................................................... 756 Preparing to recover from a disaster by using Simplified Disaster Recovery ............................................................................ 757 Hardware replacement during disaster recovery .......................... 758 Prepare to recover IBM computers with Simplified Disaster Recovery ...................................................................... 759 Recovering a computer with Simplified Disaster Recovery ................... 760 Recovery notes for using Simplified Disaster Recovery with storage pools and storage spaces ................................................. 766 Recovery notes for using Simplified Disaster Recovery with Exchange, SQL, SharePoint, CASO, Hyper-V hosts, and the Deduplication Option ....................................................... 769 Advanced Disk Configuration on the Recover This Computer Wizard ................................................................................ 770 Appendix A Symantec Backup Exec Agent for Windows ................. 774 About the Agent for Windows ........................................................ 774 Requirements for the Agent for Windows ......................................... 775 Stopping and starting the Agent for Windows .................................... 776 Establishing a trust between the Backup Exec server and a remote computer ............................................................................ 777 About the Backup Exec Agent Utility for Windows .............................. 777 Starting the Backup Exec Agent Utility ...................................... 778 Viewing the activity status of the remote computer in the Backup Exec Agent Utility ........................................................... 779 Viewing the activity status of the remote computer from the system tray .............................................................................. 779 Starting the Backup Exec Agent Utility automatically on the remote computer ...................................................................... 780 Setting the refresh interval on the remote computer ..................... 780 About publishing the Agent for Windows to Backup Exec servers ......................................................................... 781 Adding Backup Exec servers that the Agent for Windows can publish to ...................................................................... 781 Editing Backup Exec server information that the Agent for Windows publishes to ................................................................... 782 Removing Backup Exec servers that the Agent for Windows can publish to ...................................................................... 783 21Contents
- 22. Configuring database access for Oracle operations ..................... 784 Removing a security certificate for a Backup Exec server that has a trust with the Agent for Windows ..................................... 786 Using the Backup Exec Agent Utility Command Line Applet ................. 786 Backup Exec Agent Utility Command Line Applet switches .................. 787 Appendix B Symantec Backup Exec Deduplication Option ............ 791 About the Deduplication Option ..................................................... 792 Deduplication methods for Backup Exec agents ................................ 794 Requirements for the Deduplication Option ...................................... 795 Installing the Deduplication Option ................................................. 800 Configuring an OpenStorage device ............................................... 801 Editing the properties of an OpenStorage device ............................... 803 Specifying a Backup Exec server that has proximity to a shared OpenStorage device ............................................................. 805 Creating or importing deduplication disk storage ............................... 806 Editing the properties of a deduplication disk storage device .......... 808 Changing the password for the logon account for deduplication disk storage ................................................................... 813 Selecting storage devices for direct access sharing ........................... 814 Editing server properties for direct access .................................. 815 Changing the location of a deduplication disk storage device ............... 816 Sharing a deduplication device between multiple Backup Exec servers ............................................................................... 818 How to use client-side deduplication ............................................... 818 How to set up backup jobs for deduplication ..................................... 819 Using optimized duplication to copy deduplicated data between OpenStorage devices or deduplication disk storage devices .......... 820 Copying deduplicated data to tapes ................................................ 823 Using deduplication with encryption ................................................ 823 Restoring a deduplication disk storage device or deduplicated data ................................................................................... 824 Disaster recovery of deduplication disk storage devices ..................... 824 Disaster recovery of OpenStorage devices ....................................... 825 Appendix C Symantec Backup Exec Agent for VMware ................... 827 About the Agent for VMware ......................................................... 827 Requirements for using the Agent for VMware .................................. 828 Using the Agent for VMware with Windows Server 2012 ..................... 829 About installing the Agent for VMware ............................................. 830 Adding VMware vCenter Servers and ESX/ESXi hosts to the list of servers on the Backup and Restore tab ..................................... 830 22Contents
- 23. Viewing details about VMware resources ......................................... 831 Installing the Agent for Windows on VMware virtual machines .............. 832 Push-installing the Agent for Windows to VMware virtual machines ............................................................................ 833 Backing up VMware data .............................................................. 834 Setting default backup options for virtual machines ...................... 839 How Backup Exec automatically backs up new VMware virtual machines during a backup job .......................................... 843 Using Granular Recovery Technology (GRT) with the Agent for VMware ........................................................................ 843 How delayed cataloging works with VMware virtual machine backups ........................................................................ 846 Restoring VMware virtual machines and vmdk files ............................ 848 Appendix D Symantec Backup Exec Agent for Microsoft Hyper-V .......................................................................... 855 About the Agent for Microsoft Hyper-V ............................................ 855 Requirements for using the Agent for Microsoft Hyper-V ..................... 857 About installing the Agent for Microsoft Hyper-V ................................ 859 Using the Agent for Hyper-V with Windows Server 2012/2012 R2 ......... 860 Disk space optimization with the Agent for Hyper-V ........................... 863 Adding a Hyper-V host to the list of servers on the Backup and Restore tab ..................................................................................... 864 Viewing details about Hyper-V resources ......................................... 865 Installing the Agent for Windows on Hyper-V virtual machines .............. 866 Push-installing the Agent for Windows to Hyper-V virtual machines ............................................................................ 867 Backing up Microsoft Hyper-V virtual machines ................................. 868 Setting default backup options for Hyper-V ................................. 873 How Backup Exec automatically protects new virtual machines during a backup job ......................................................... 875 Using Granular Recovery Technology (GRT) with the Agent for Hyper-V ........................................................................ 876 About backing up and restoring highly available Hyper-V virtual machines ...................................................................... 878 How delayed cataloging works with Hyper-V virtual machine backups ........................................................................ 878 Restoring Microsoft Hyper-V virtual machines ................................... 880 23Contents
- 24. Appendix E Symantec Backup Exec Agent for Microsoft SQL Server ............................................................................. 885 About the Agent for Microsoft SQL Server ........................................ 885 Requirements for using the SQL Agent ........................................... 887 About installing the SQL Agent ...................................................... 888 Backup strategies for SQL ............................................................ 888 Adding SQL Servers to the list of servers on the Backup and Restore tab ..................................................................................... 890 Configuring Backup Exec to run a consistency check before every SQL backup ............................................................................... 890 Using snapshot technology with the SQL Agent ................................ 891 Using database snapshots for SQL Server ....................................... 892 Backing up SQL databases and transaction logs ............................... 894 Setting default backup options for SQL Server ............................ 906 Restoring SQL databases and transaction logs ................................. 916 Restoring the SQL master database ......................................... 918 Restarting SQL using database copies ...................................... 919 Disaster recovery of a SQL Server ................................................. 921 Manual recovery of a SQL Server ............................................ 923 Appendix F Symantec Backup Exec Agent for Microsoft Exchange Server .......................................................... 924 About the Backup Exec Exchange Agent ......................................... 925 Requirements for using the Exchange Agent .................................... 926 Granting permissions on the Exchange Server to enable database backups and restores, and Granular Recovery Technology operations ........................................................................... 930 About installing the Exchange Agent ............................................... 934 Adding Exchange Servers and database availability groups to the list of servers on the Backup and Restore tab .................................. 935 Managing preferred server configurations for Microsoft Exchange Database Availability Groups .................................................. 935 Recommended configurations for Exchange .................................... 938 Requirements for accessing Exchange mailboxes ............................ 939 Backup strategies for Exchange ..................................................... 940 How Granular Recovery Technology works with the Exchange Information Store ................................................................. 942 Snapshot and offhost backups with the Exchange Agent ..................... 944 Backing up Exchange data ........................................................... 946 Setting default backup options for Exchange Server ..................... 952 Restoring Exchange data ............................................................. 957 24Contents
- 25. Disaster recovery of an Exchange Server ........................................ 963 Appendix G Symantec Backup Exec Agent for Microsoft SharePoint .................................................................... 965 About the Agent for Microsoft SharePoint ........................................ 966 About installing the Agent for Microsoft SharePoint ............................ 966 Requirements for the Agent for Microsoft SharePoint ......................... 966 Using the Agent for Microsoft SharePoint with SharePoint Server 2010/2013 and SharePoint Foundation 2010/2013 ...................... 967 Using the Agent for Microsoft SharePoint with SharePoint Server 2007 and Windows SharePoint Services 3.0 ...................................... 968 Adding a Microsoft SharePoint server farm to the list of servers on the Backup and Restore tab ......................................................... 969 Backing up Microsoft SharePoint data ............................................. 969 Setting default backup options for SharePoint ............................. 973 Restoring Microsoft SharePoint data ............................................... 976 Disabling or enabling communication between a Microsoft SharePoint web server and Backup Exec .................................................. 978 Viewing or changing SharePoint farm properties ............................... 979 Disaster recovery of Microsoft SharePoint 2010/2013 data .................. 980 Disaster recovery of Microsoft SharePoint 2007 data ......................... 984 Appendix H Symantec Backup Exec Agent for Oracle on Windows or Linux Servers ......................................... 987 About the Backup Exec Oracle Agent ............................................. 987 About installing the Oracle Agent ................................................... 988 Configuring the Oracle Agent on Windows computers and Linux servers ............................................................................... 989 Configuring an Oracle instance on Windows computers ................ 990 Viewing an Oracle instance on Windows computers ..................... 994 Editing an Oracle instance on Windows computers ...................... 995 Deleting an Oracle instance on Windows computers .................... 996 Enabling database access for Oracle operations on Windows computers ..................................................................... 996 Configuring an Oracle instance on Linux servers ......................... 999 Viewing an Oracle instance on Linux servers ............................ 1001 Editing an Oracle instance on Linux servers ............................. 1002 Deleting an Oracle instance on Linux servers ............................ 1002 Enabling database access for Oracle operations on Linux servers ....................................................................... 1003 About authentication credentials on the Backup Exec server .............. 1004 25Contents
- 26. Setting authentication credentials on the Backup Exec server for Oracle operations ......................................................... 1005 Deleting an Oracle server from the Backup Exec server’s list of authentication credentials ............................................... 1006 About Oracle instance information changes .................................... 1007 About backing up Oracle databases .............................................. 1007 About backing up Oracle RAC databases ................................. 1009 About performing a DBA-initiated backup job for Oracle .............. 1010 Oracle backup options ......................................................... 1011 About restoring Oracle resources ................................................. 1012 About DBA-initiated restore for Oracle ..................................... 1015 Oracle restore options ......................................................... 1016 About redirecting a restore of Oracle data ................................ 1016 Oracle advanced restore options ........................................... 1017 Performing a redirect restore of an Oracle 12c database using Backup Exec ............................................................... 1018 Requirements for recovering the complete Oracle instance and database using the original Oracle server ........................... 1022 Recovering the complete Oracle instance and database using the original Oracle server ..................................................... 1022 Requirements for recovering the complete Oracle instance or database to a computer other than the original Oracle server ......................................................................... 1023 Recovering the complete Oracle instance or database to a computer other than the original Oracle server .................... 1024 Best practices for Backup Exec 15 Agent for Oracle on Windows or Linux Servers ..................................................................... 1025 Appendix I Symantec Backup Exec Agent for Enterprise Vault ............................................................................. 1028 About the Agent for Enterprise Vault ............................................. 1028 Requirements for the Enterprise Vault Agent ................................... 1032 About installing the Enterprise Vault Agent ..................................... 1033 About backup methods for Enterprise Vault backup jobs ................... 1033 Enterprise Vault backup options ............................................. 1036 About backing up Enterprise Vault components ............................... 1037 About consistency checks for Enterprise Vault databases and Compliance and Discovery Accelerator databases ..................... 1040 Restoring Enterprise Vault .......................................................... 1040 Enterprise Vault restore options ............................................. 1042 About restoring individual files and folders with the Enterprise Vault Agent .................................................................. 1045 26Contents
- 27. About automatic redirection of Enterprise Vault components under an Enterprise Vault server ............................................... 1045 Redirecting a restore for an Enterprise Vault component ............. 1046 Configuring Enterprise Vault to use the name of the new SQL Server that holds the Directory database ........................................... 1048 Best practices for the Enterprise Vault Agent .................................. 1050 About the Backup Exec Migrator for Enterprise Vault ........................ 1050 Backup Exec Migrator for Enterprise Vault requirements ............. 1051 How the Backup Exec Migrator works ..................................... 1051 About using staged migrations with Backup Exec and the Backup Exec Migrator ............................................................... 1055 About Backup Exec Migrator events ........................................ 1056 About Backup Exec Migrator logs ........................................... 1056 About deleting files migrated by Backup Exec Migrator ............... 1057 Configuring the Backup Exec Migrator ..................................... 1058 About viewing migrated Enterprise Vault data ........................... 1066 About retrieving migrated Enterprise Vault data ......................... 1067 About the Partition Recovery Utility ......................................... 1068 Enterprise Vault logon account ..................................................... 1071 Enterprise Vault options .............................................................. 1072 Appendix J Symantec Backup Exec Agent for Lotus Domino ......................................................................... 1073 About the Agent for Lotus Domino Server ...................................... 1074 Lotus Domino Agent requirements ................................................ 1074 About installing the Lotus Domino Agent on the Backup Exec server ............................................................................... 1076 About the Lotus Domino Agent and the Domino Attachment and Object Service (DAOS) .................................................................. 1076 Best practices for restoring the missing .nlo files ........................ 1077 Viewing Lotus Domino databases ................................................ 1078 About backing up Lotus Domino databases .................................... 1078 About selecting backup options for Lotus Domino databases ....... 1080 Lotus Domino Agent backup options ....................................... 1080 About automatic exclusion of Lotus Domino files during volume-level backups .................................................... 1081 About supported Lotus Domino database configurations ............. 1081 About Lotus Domino transaction logs ...................................... 1082 About restoring Lotus Domino databases ....................................... 1083 Restoring Lotus Domino databases ........................................ 1084 Lotus Domino Agent restore options ....................................... 1086 About redirecting restore jobs for Lotus Domino databases .......... 1088 27Contents
- 28. About redirecting the restore of DAOS NLO files ........................ 1089 How to prepare for disaster recovery on a Lotus Domino server .......... 1089 Recovering a Lotus Domino server from a disaster .......................... 1089 About disaster recovery of a Lotus Domino server using archive logging ............................................................................. 1091 Disabling the monitor change journal ............................................ 1091 Recovering the Lotus Domino server, databases, and transaction logs when archive logging is enabled ............................................ 1092 Re-enabling the monitor change journal ......................................... 1093 Recovering a Lotus Domino server that uses circular logging ............. 1094 Appendix K Symantec Backup Exec Agent for Microsoft Active Directory ...................................................................... 1096 About the Agent for Microsoft Active Directory ................................. 1096 Requirements for the Agent for Microsoft Active Directory ................. 1097 About backing up Active Directory and ADAM/AD LDS ..................... 1098 Editing options for Active Directory and ADAM/AD LDS backup jobs ............................................................................ 1099 Microsoft Active Directory backup job options ........................... 1101 About restoring individual Active Directory and ADAM/AD LDS objects .............................................................................. 1102 Appendix L Symantec Backup Exec Central Admin Server Option ........................................................................... 1105 About the Central Admin Server Option ......................................... 1106 Requirements for installing CASO ................................................ 1108 How to choose the location for CASO storage and media data .......... 1109 About installing the Central Admin Server Option ............................. 1111 Push-installing a managed Backup Exec server from the central administration server ..................................................... 1112 Managed Backup Exec Server Configuration options .................. 1118 Installing a managed Backup Exec server across a firewall ......... 1119 Upgrading an existing CASO installation ........................................ 1122 Changing a Backup Exec server to a central administration server ............................................................................... 1124 Changing a Backup Exec server to a managed Backup Exec server ............................................................................... 1125 Deleting a managed Backup Exec server from a CASO environment ....................................................................... 1128 Renaming a central administration server ....................................... 1130 Renaming a managed Backup Exec server .................................... 1130 28Contents
- 29. How to reduce network traffic in CASO .......................................... 1132 CASO distributed, centralized, and replicated catalog locations .......... 1132 Changing the settings for a managed Backup Exec server ................. 1134 What happens when CASO communication thresholds are reached ............................................................................ 1145 Enabling or disabling communications between the managed Backup Exec server and the central administration server ......................................................................... 1146 Alerts and notifications in CASO ................................................... 1146 Enabling managed Backup Exec servers to use any available network interface card .................................................................... 1147 About job delegation in CASO ..................................................... 1148 About copying jobs instead of delegating jobs in CASO ............... 1148 About adding storage devices in a CASO environment ..................... 1149 How data lifecycle management (DLM) works in a CASO environment ....................................................................... 1149 Obtaining media audit information for a managed Backup Exec server ............................................................................... 1150 How to use Backup Exec server pools in CASO ............................. 1150 Selecting a Backup Exec server pool for backups ...................... 1151 Creating a Backup Exec server pool ....................................... 1152 Adding managed Backup Exec servers to a Backup Exec server pool ........................................................................... 1152 Deleting a Backup Exec server pool ........................................ 1153 Removing a managed Backup Exec server from a Backup Exec server pool .................................................................. 1153 How centralized restore works in CASO ......................................... 1154 How CASO restores data that resides on multiple storage devices ....................................................................... 1155 About recovering failed jobs in CASO ............................................ 1156 Pausing or resuming a managed Backup Exec server ...................... 1158 Stopping or starting Backup Exec services for a managed Backup Exec server ....................................................................... 1158 Viewing managed Backup Exec server properties ............................ 1159 Viewing the settings for a central administration server ..................... 1162 Disaster recovery in CASO ......................................................... 1164 Troubleshooting CASO .............................................................. 1165 Running the Backup Exec Utility for CASO operations ...................... 1167 Uninstalling Backup Exec from the central administration server ........ 1167 Uninstalling Backup Exec from a managed Backup Exec server ......... 1168 29Contents
- 30. Appendix M Symantec Backup Exec Advanced Disk-based Backup Option ............................................................ 1169 About the Advanced Disk-based Backup Option .............................. 1169 How to use synthetic backups in place of recurring full backups .......... 1170 Configuring off-host backup options for a backup job ........................ 1171 Setting default backup options for the Advanced Disk-based Backup Option .............................................................................. 1173 About true image restore for synthetic backups ............................... 1175 How to use off-host backup to process remote computer backups on the Backup Exec server ........................................................ 1177 Troubleshooting off-host backups ................................................. 1180 Appendix N Symantec Backup Exec NDMP Option ......................... 1184 Features of the NDMP Option ...................................................... 1184 Requirements for using the NDMP Option ...................................... 1185 About installing the NDMP Option ................................................. 1186 Adding NDMP servers to Backup Exec .......................................... 1186 Sharing the tape drives on NDMP servers between multiple Backup Exec servers ...................................................................... 1188 NDMP backup options for NDMP servers ....................................... 1188 NDMP server backup selections .................................................. 1190 How to use patterns to exclude files and directories from an NDMP server backup .................................................................... 1191 Supported configurations for duplicating data from NDMP servers ............................................................................. 1193 About restoring and redirecting restore data for NDMP servers ........... 1193 NDMP server restore options ................................................. 1194 Setting the default backup options for the NDMP Option ................... 1197 Viewing the properties of an NDMP server ..................................... 1198 NDMP server properties ....................................................... 1198 Viewing storage properties for an NDMP server .............................. 1199 Storage properties for an NDMP server ................................... 1199 Appendix O Symantec Backup Exec Agent for Linux ...................... 1201 About the Agent for Linux ........................................................... 1202 About open files and the Agent for Linux ........................................ 1202 Requirements for the Agent for Linux ............................................ 1202 About installing the Agent for Linux ............................................... 1203 Installing the Agent for Linux ................................................. 1204 About the Backup Exec operators (beoper) group for the Agent for Linux ...................................................................... 1206 30Contents
- 31. About establishing trust for a remote Linux computer in the Backup Exec list of servers ............................................................. 1207 Establishing trust and adding a remote Linux computer to the Backup Exec list of servers ............................................. 1208 Adding additional Backup Exec servers to which the Agent for Linux can publish information ........................................................ 1208 About configuring the Agent for Linux ............................................ 1209 Excluding files and directories from all backup jobs for Linux computers ......................................................................... 1210 Editing configuration options for Linux computers ............................ 1210 Configuration options for Linux computers ................................ 1211 About backing up a Linux computer by using the Agent for Linux ........ 1218 Linux backup options ........................................................... 1219 About backing up and restoring Novell Open Enterprise Server (OES) components ....................................................... 1220 About restoring data to Linux computers ........................................ 1222 About restoring Novell OES components ................................. 1222 Restore job options for Linux computers .................................. 1222 Editing the default backup job options for Linux computers ................ 1223 Default backup job options for Linux computers ......................... 1224 Uninstalling the Agent for Linux .................................................... 1225 Manually uninstalling the Agent for Linux ................................. 1226 Run-time scripts to remove when manually uninstalling the Agent for Linux ...................................................................... 1227 Starting the Agent for Linux daemon ............................................. 1228 Stopping the Agent for Linux daemon ............................................ 1229 Troubleshooting the Agent for Linux .............................................. 1229 Appendix P Symantec Backup Exec Agent for Mac ........................ 1235 About the Agent for Mac ............................................................. 1236 Requirements for the Agent for Mac .............................................. 1236 About the Backup Exec admin group on Macintosh systems .............. 1236 Creating the Backup Exec admin group manually on Macintosh systems ...................................................................... 1237 About installing the Agent for Mac ................................................ 1238 Installing the Agent for Mac ................................................... 1238 Uninstalling the Agent for Mac ..................................................... 1241 Manually uninstalling the Agent for Mac ................................... 1242 About configuring the Agent for Mac ............................................. 1243 Editing configuration options for Macintosh computers ................ 1244 Configuration options for Macintosh computers ......................... 1244 Starting the Agent for Mac .......................................................... 1249 31Contents
- 32. Stopping the Agent for Mac ........................................................ 1250 About establishing trust for a remote Macintosh system in the Servers list .................................................................................... 1250 Establishing trust and adding a remote Macintosh computer to the Backup Exec Servers list ........................................... 1250 Adding additional Backup Exec servers to which the Agent for Mac can publish information ........................................................ 1251 About backing up data by using the Agent for Mac ........................... 1252 Editing the default backup options for Macintosh systems ............ 1252 About excluding files and directories from backup jobs for Macintosh computers ..................................................... 1254 About restoring Macintosh systems ............................................... 1255 Macintosh restore options ..................................................... 1255 Troubleshooting the Agent for Mac ............................................... 1255 Appendix Q Symantec Backup Exec Remote Media Agent for Linux ............................................................................. 1257 About the Remote Media Agent for Linux ...................................... 1258 How the Remote Media Agent for Linux works ................................ 1259 Requirements for the Remote Media Agent for Linux ........................ 1260 About open files and the Remote Media Agent for Linux .................... 1261 About installing the Remote Media Agent for Linux ........................... 1261 Installing the Remote Media Agent for Linux ............................. 1262 Uninstalling the Remote Media Agent for Linux ............................... 1265 Starting the Remote Media Agent for Linux daemon ......................... 1266 Stopping the Remote Media Agent for Linux daemon ....................... 1266 About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers .......................................... 1267 Establishing trust and adding a Remote Media Agent for Linux computer to the Backup Exec list of servers ........................ 1267 Adding additional Backup Exec servers to which Remote Media Agent for Linux can publish ............................................................ 1268 Finding simulated tape library files ................................................ 1268 About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux ................................................................... 1269 Creating the Backup Exec operators (beoper) group manually for the Remote Media Agent for Linux .................................... 1270 About adding a Linux server as a Remote Media Agent for Linux ....... 1270 Adding a Linux server as a Remote Media Agent for Linux .......... 1271 Remote Media Agent for Linux options .................................... 1271 Changing the port for communications between the Backup Exec server and the Remote Media Agent for Linux .................................... 1273 32Contents
- 33. About creating storage device pools for devices attached to the Remote Media Agent for Linux ......................................................... 1273 Editing properties for the Remote Media Agent for Linux .................. 1274 Remote Media Agent for Linux properties ................................. 1274 Deleting a Remote Media Agent for Linux from the Backup Exec list of servers .......................................................................... 1275 Sharing a Remote Media Agent for Linux between multiple Backup Exec servers ...................................................................... 1275 About backing up data by using the Remote Media Agent for Linux ................................................................................ 1276 About restoring data by using the Remote Media Agent for Linux ........ 1276 About the Tape Library Simulator Utility ......................................... 1277 Creating a simulated tape library .................................................. 1278 Simulated Tape Library options .............................................. 1279 Viewing simulated tape libraries properties ..................................... 1279 Simulated tape library properties ............................................ 1280 Deleting a simulated tape library .................................................. 1280 Managing simulated tape libraries from the command line ................. 1281 Command line switches for the Tape Library Simulator Utility ............. 1282 Troubleshooting the Remote Media Agent for Linux ......................... 1283 Appendix R Symantec Backup Exec Storage Provisioning Option ........................................................................... 1286 Features of the Storage Provisioning Option ................................... 1287 Requirements for the Storage Provisioning Option ........................... 1288 About installing the Storage Provisioning Option .............................. 1288 Viewing storage array components in Backup Exec .......................... 1289 Configuring a storage array by using the Configure Storage Wizard .............................................................................. 1289 Editing properties for a storage array and its physical disks ................ 1291 About the Any Virtual Disk Storage device pool in the Storage Provisioning Option ............................................................. 1291 About virtual disks in the Storage Provisioning Option ....................... 1292 Editing default options for a virtual disk on a storage array ........... 1294 Configuring a virtual disk on a storage array ............................ 1299 Editing properties for unconfigured virtual disks on a storage array .......................................................................... 1299 Editing properties of virtual disks on storage arrays .................... 1300 Adding a hot spare by using the Configure Storage Wizard ................ 1305 Changing a hot spare by using the Configure Storage Wizard ............ 1306 Detecting a new storage array ..................................................... 1306 Renaming a virtual disk or storage array ........................................ 1307 33Contents
- 34. Identifying the physical disks of a virtual disk by using the blink feature .............................................................................. 1308 Troubleshooting the Storage Provisioning Option ............................. 1309 Appendix S Symantec Backup Exec Archiving Option ................... 1310 About the Archiving Option .......................................................... 1311 Requirements for both the Exchange Mailbox Archiving Option and the File System Archiving Option ............................................ 1312 Requirements for the Exchange Mailbox Archiving Option ........... 1314 Requirements for the File System Archiving Option .................... 1317 About granting permissions on the Exchange Server for the Backup Exec service account in the Archiving Option .......... 1318 How to calculate disk space requirements for the Exchange Mailbox Archiving Option ................................................ 1324 How to calculate disk space requirements for the File System Archiving Option ........................................................... 1327 Installing the Backup Exec Archiving Option ................................... 1330 About using the command line to install the Backup Exec Exchange Mailbox Archiving Option .................................. 1331 About the Internet Information Services (IIS) 7.0 role services installed by Backup Exec ................................................ 1331 About uninstalling or reinstalling the Archiving Option ................. 1333 About installing Enterprise Vault on a Backup Exec server on which the Archiving Option is installed ............................... 1334 About Enterprise Vault services for the Archiving Option ............. 1334 Repairing the Backup Exec Archiving Option ............................ 1335 How the Archiving Option works ................................................... 1335 Types of data not included in archive jobs ................................ 1336 Best practices for the Archiving Option .......................................... 1337 About creating an archive job ...................................................... 1338 Viewing the servers that have archiving jobs ............................. 1339 Setting archive job options .................................................... 1339 Editing default settings for the Archiving Option ............................... 1344 Default settings for the Archiving Option .................................. 1344 About single instance storage of archived items .............................. 1347 Enabling single instance storage of archived items ..................... 1348 About synchronizing archive permissions and settings ...................... 1348 About vault stores in the Archiving Option ...................................... 1349 Editing or viewing vault store properties ................................... 1350 Vault store properties ........................................................... 1350 About deleting an Archiving Option vault store .......................... 1351 Deleting a vault store ........................................................... 1352 34Contents
- 35. About vault store partitions in the Archiving Option ........................... 1352 Editing vault store partition properties ...................................... 1353 Vault store partition properties ............................................... 1353 About archives in the Archiving Option .......................................... 1354 Editing archive properties ..................................................... 1354 Deleting an archive ............................................................. 1355 Archive properties ............................................................... 1355 About Archiving Option operation entries in the audit log ................... 1356 About Exchange mailbox groups in archive jobs .............................. 1356 Managing Exchange mailbox groups ....................................... 1357 Manage mailbox groups options ............................................. 1358 Mailbox group options for mailbox group details ........................ 1359 About deleting archived data from its original location ....................... 1361 About archive settings in the Archiving Option ................................. 1361 Manage Archive Settings options ........................................... 1361 Archive Settings Details ....................................................... 1362 About retention categories for archived items ............................ 1364 About managing index locations in the Backup Exec Archiving Option .............................................................................. 1368 Viewing index locations ........................................................ 1369 Adding a new index location .................................................. 1369 Deleting an index location ..................................................... 1370 Opening or closing an index location ....................................... 1370 Manage Index Locations options ............................................ 1371 About restoring items from the archives ......................................... 1372 About searching for data in the archives ........................................ 1373 About deleting data from the archives ............................................ 1373 Deleting data from the archives .............................................. 1374 Delete from Archive options .................................................. 1374 About backing up and restoring the Archiving Option components from a remote Backup Exec server ................................................ 1375 Preventing the deletion of expired archived items from an archive ....... 1375 About backing up Archiving Option components .............................. 1375 Archive Option backup options ............................................... 1378 About consistency checks for Archiving Option databases ........... 1379 About disabling backup mode for Archiving Option components ................................................................. 1379 About restoring an Archiving Option component .............................. 1380 About running the Backup Exec Utility to complete redirected restores of Archiving Option components ........................... 1381 Running the Backup Exec Utility to complete a redirected restore of the Archiving Option databases .................................... 1382 35Contents
- 36. Running the Backup Exec Utility before redirecting the restore of an Archiving Option vault store partition ............................. 1383 Running the Backup Exec Utility before redirecting the restore of Archiving Option index files ............................................. 1383 Running the Backup Exec Utility to complete Archiving Option operations ................................................................... 1384 About moving Archiving Option components to a new location ............ 1385 Troubleshooting archive jobs ....................................................... 1386 Viewing the Enterprise Vault event log for Archiving Option events ........................................................................ 1386 Reports for the Archiving Option ................................................... 1386 About Backup Exec Virtual Vault ................................................. 1387 About the Backup Exec Outlook Add-In ................................... 1389 About installing the Backup Exec Outlook Add-In to end users' computers ................................................................... 1389 About configuring Outlook in cached Exchange mode ................ 1394 Best practices for Virtual Vault ............................................... 1394 About the Vault Cache ......................................................... 1395 About Vault Cache synchronization ......................................... 1396 About preemptive caching .................................................... 1397 About the temporary cache location on the Backup Exec server ......................................................................... 1398 About enabling and disabling Virtual Vault ............................... 1399 Appendix T Accessibility and Backup Exec ...................................... 1401 About accessibility and Backup Exec ............................................ 1401 About keyboard shortcuts in Backup Exec ...................................... 1402 Home tab keyboard shortcuts ................................................ 1403 Backup and Restore tab keyboard shortcuts ............................. 1403 Job Monitor tab keyboard shortcuts ........................................ 1411 Storage tab keyboard shortcuts .............................................. 1414 Reports tab keyboard shortcuts .............................................. 1422 General keyboard navigation within the Backup Exec user interface ...................................................................... 1423 Keyboard navigation within dialog boxes in Backup Exec ............ 1423 List box navigation in Backup Exec ............................................... 1424 Tabbed dialog box navigation in Backup Exec ................................. 1424 About setting accessibility options ................................................ 1425 Glossary ........................................................................................................... 1426 Index ................................................................................................................. 1433 36Contents
- 37. Introducing Backup Exec 15 This chapter includes the following topics: ■ About Backup Exec ■ How Backup Exec works About Backup Exec Symantec Backup Exec 15 is a high-performance data management solution for Windows® servers networks. With its client/server design, Backup Exec provides fast, reliable backup and restore capabilities for servers, applications, and workstations across the network. Backup Exec is available in several configurations that can accommodate networks of all sizes. In addition, Backup Exec's family of agents and options offer solutions for scaling your Backup Exec environment and extending platform and feature support. See “How Backup Exec works” on page 37. How Backup Exec works You use the Backup Exec Administration Console to interact with Backup Exec for tasks like submitting backups, restoring data, configuring storage, and monitoring jobs. You can run the Administration Console from the Backup Exec server, which is a Windows server on which Backup Exec is installed, or from a remote computer. After backups, restores, or other operations are created, the Backup Exec server processes the jobs or delegates the jobs for processing in multi-Backup Exec server environments. Backup Exec includes the following features: ■ Convenient backup scheduling 1Chapter
- 38. Backup Exec administrators can set up scheduled backups for Windows and Linux computers across the network. Backup Exec's flexible calendar-based administration lets you easily schedule backups for processing during off-peak hours. ■ Complete system recovery Backup Exec's Simplified Disaster Recovery takes all of the guesswork out of recovering an entire system. While configuring a backup, you get a clear indication that you have selected the data that is necessary to perform a Simplified Disaster Recovery-enabled backup. After you back up a computer's critical system components, use the Create Simplified Disaster Recovery Disk Wizard to create a Simplified Disaster Recovery disk image. You can then use the disk image to perform a disaster recovery of the computer. ■ Comprehensive monitoring and intuitive mechanisms for everyday tasks The Job Monitor provides a single location to monitor and manage all of your backup, restore, installation, and storage operation jobs. The Home tab lets you view statistics for your entire Backup Exec environment. From the Servers view, you can monitor the backup status for all of the computers on your network. Interactive alerts display the situations that require your attention. Backup results can be viewed from a backup's job history. The job history contains statistics, errors, and other information pertaining to the backup. Backup Exec’s catalog is a database of all backed-up data, and Backup Exec uses the catalog to track restore selections. Wizards guide you through most Backup Exec operations, including the creation of backup and restore jobs, and the configuration of storage. ■ Automated data lifecycle management for disk-based storage Backup Exec uses data lifecycle management to automatically delete expired backup sets on disk storage, disk cartridge media, deduplication storage, storage arrays, and virtual disks. You specify how long to keep backup data when you create a backup job that is sent to a disk-based storage device. When the amount of time to keep the backup data expires, the data lifecycle management feature deletes the backup sets and reclaims the disk space for use by new backup sets. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. ■ Simplified device and media management Backup Exec uses the Advanced Device and Media Management (ADAMM) feature to manage data retention on tapes. ADAMM expires the backup sets that are stored on media according to a set of rules that you apply to the media. 38Introducing Backup Exec 15 How Backup Exec works
- 39. Installation This chapter includes the following topics: ■ About the Backup Exec installation process and licensing options ■ Backup Exec preinstallation checklist ■ Running the Environment Check before installing or upgrading Backup Exec ■ Microsoft SQL Server 2008 Express Edition components installed with Backup Exec ■ Backup Exec’s standard features ■ System requirements for Backup Exec ■ Installing Backup Exec by using the Installation Wizard ■ Installing additional Backup Exec options to the local Backup Exec server ■ Push-installing Backup Exec to remote computers ■ Methods for installing the Agent for Windows ■ Installing the Remote Administrator ■ Installing Backup Exec using the command line (silent mode) ■ Installing a trial version of Backup Exec agents and options ■ About the installation log ■ Viewing the Installation Summary Report ■ Repairing Backup Exec ■ Updating Backup Exec with LiveUpdate ■ Viewing installed updates 2Chapter
- 40. ■ Viewing license information ■ Backup Exec maintenance contract information ■ About upgrading from previous versions of Backup Exec to Backup Exec 15 ■ Post-installation tasks ■ Uninstalling Backup Exec ■ Uninstalling Backup Exec using the command line ■ Uninstalling Backup Exec options from the local Backup Exec server About the Backup Exec installation process and licensing options The Backup Exec installation wizard guides you through the process of installing Backup Exec and its agents and options. Using the installation wizard, you can install Backup Exec and its agents and options on a local computer or you can push-install them to a remote computer. The computer on which Backup Exec is installed is called the Backup Exec server. Additionally, you can install the Remote Administrator, which lets you administrate the Backup Exec server from a remote Windows server or workstation. Note: You cannot install Backup Exec or the Agent for Windows on a volume that has been enabled for deduplication in Windows or on an ReFS volume. When you install Backup Exec, you have the following licensing options: 40Installation About the Backup Exec installation process and licensing options
- 41. Table 2-1 Licensing options DescriptionItem You can type the serial numbers that are listed on your license certificate. Serial numbers contain one letter and 10 numbers, such as M0123456789. After you add your serial numbers, Backup Exec polls the Symantec Web service to verify the serial numbers. An Internet connection is required to enable Backup Exec to verify the serial numbers. Note: Serial numbers from previous versions of Backup Exec cannot activate the most recent version of Backup Exec. The following are the two types of Backup Exec serial numbers: ■ Product activation serial numbers activate Backup Exec products and features. ■ Maintenance contract serial numbers activate the maintenance for your Backup Exec products. Maintenance contract serial numbers cannot activate Backup Exec products and features. See “Backup Exec maintenance contract information” on page 110. Enter serial numbers manually 41Installation About the Backup Exec installation process and licensing options
- 42. Table 2-1 Licensing options (continued) DescriptionItem You can import your Symantec License Files (.slf) from a network share or from a local drive. You may receive Symantec License Files in an email with your license certificate or you may need to go to the Symantec Licensing Portal website to obtain them. From the Symantec Licensing Portal website, you receive one file with all of the serial numbers that you registered. From the email, you receive multiple files with one serial number in each file. After installation, the .slf files can be found in the following locations: ■ In Windows 2003: C:Program FilesCommon FilesSymantec SharedLicenses ■ In Windows 2008 and later: C:ProgramdataSymantec SharedLicenses Import licenses from the Symantec License File A 60-day trial version is available for Backup Exec and many of its agents and options. If you do not enter any serial numbers or Symantec license files during the installation process, a trial version is installed. If you enter a serial number or license file for Backup Exec, trial versions of many of the agents and options are available. Install a 60-day trial version After Backup Exec is installed, you can install additional agents and options from the Backup Exec user interface. You can install additional agents and options on the Backup Exec server or push-install Backup Exec or the Agent for Windows to remote computers. Installation from a command line is also available. Command line installation is called silent mode installation. The silent mode installation uses the Setup.exe program on the Backup Exec installation media. Backup Exec may install the following additional products during the installation process: ■ Symantec LiveUpdate 42Installation About the Backup Exec installation process and licensing options
- 43. ■ Microsoft Report Viewer 2010 SP1 ■ Microsoft.NET Framework 4.5.2 ■ Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update ■ Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update ■ Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update ■ Microsoft Visual C++ 2012 Redistributable Package ■ Microsoft SQL Server 2008 R2 Express with SP2 See “Installing Backup Exec by using the Installation Wizard” on page 52. See “Installing additional Backup Exec options to the local Backup Exec server” on page 62. See “Push-installing Backup Exec to remote computers” on page 64. See “Push-installing the Agent for Windows to remote computers” on page 73. See “Installing Backup Exec using the command line (silent mode)” on page 94. See “Backup Exec preinstallation checklist” on page 43. Backup Exec preinstallation checklist Before you install Backup Exec, you should do the following: ■ Run the Backup Exec Environment Check on the computer on which you want to install Backup Exec. The Environment Check analyzes the computer to make sure that the installation process can complete. If Backup Exec finds any configuration issues that can be fixed during the installation, or that may prevent the installation, warnings appear. Although the Environment Check runs automatically during installation, you may want to run it manually before you install Backup Exec or before you back up data with Backup Exec. See “Running the Environment Check before installing or upgrading Backup Exec” on page 44. ■ Check the Backup Exec Hardware Compatibility List to confirm that your storage device hardware is supported in this version of Backup Exec. You can find a list of compatible types of storage in the Backup Exec hardware compatibility list: http://entsupport.symantec.com/umi/v-269-2 43Installation Backup Exec preinstallation checklist
- 44. ■ Install the storage device hardware (controller, drives, robotic libraries) on the Backup Exec server. Refer to the documentation that is included with your storage device hardware for installation instructions. Use the appropriate Windows hardware setup functions to configure your controller and storage devices. Refer to your Microsoft Windows documentation for more information. You can find a list of compatible types of storage in the Backup Exec hardware compatibility list: http://entsupport.symantec.com/umi/v-269-2 ■ Check your Windows security settings to make sure that they work properly with the Backup Exec service account. See “Changing the credentials for a service account” on page 614. ■ Ensure that port 50104 and 50106 are available for use by the Backup Exec Management Service. ■ If the drive on which you want to install Backup Exec is encrypted or compressed, and you want to use a default SQL Express database, verify that an unencrypted and uncompressed drive is available for SQL Express installation ■ Check the computer name of the computer on which you want to install Backup Exec. It should only use standard ANSI characters. You may receive errors if you install Backup Exec on a computer with a name that uses non-standard characters. ■ If you want to install Backup Exec to a non-English version of Windows, download the Microsoft SQL Server 2008 R2 Express with SP2 setup file for the language that you want to install from the Microsoft website before you install Backup Exec if all of the following are true: ■ You want to use a local Backup Exec SQL Express instance. ■ You have non-English SQL Server instances on the computer on which you want to install Backup Exec. Running the Environment Check before installing or upgrading Backup Exec The Symantec Backup Exec Environment Check is a utility that runs on a computer automatically during installation and that reports the following: ■ If the computer meets the minimum requirements for installation, such as the operating system, disk and physical memory, and sufficient logon account privileges. See “System requirements for Backup Exec” on page 49. ■ If the third-party software that uses Backup Exec ports is configured correctly. 44Installation Running the Environment Check before installing or upgrading Backup Exec
- 45. ■ If required components are installed, and if they are compatible with Backup Exec. ■ If previous versions of Backup Exec and Backup Exec options are installed. ■ If storage device hardware and associated drivers are properly installed and recognized by the Windows operating system. One of the following results is reported for each item: Table 2-2 Environment Check results DescriptionResult There are no incompatibilities to prevent the Backup Exec installation. For hardware, this result indicates that the hardware configuration is recognized by Backup Exec. Passed An incompatibility with Backup Exec exists. Some of the issues may be resolved during the Backup Exec installation. A warning does not prevent Backup Exec from installing. However, if the issues are not resolved during installation, jobs may fail. Warning An incompatibility with Backup Exec exists, and it will cause the installation to fail. Action is required before you can successfully install Backup Exec. Failed Although the Environment Check runs automatically during installation, you may want to run it manually before installing Backup Exec or before backing up data with Backup Exec. To check your environment before installing 1 From the installation media browser (Browser.exe), click Preinstallation, and then click Backup Exec. 2 Click Next. 3 Do any of the following: Check Local Environment Check.To check the configuration of the local computer Check Remote Environment Check.To check the configuration of a remote computer 4 Click Next. 5 If you checked Remote Environment Check in step 3, do one of the following, and then click Next: 45Installation Running the Environment Check before installing or upgrading Backup Exec
- 46. Do the following: ■ Click Add Server From List. ■ Select the computer from the list, and then click Next. To select the name of a computer from a list Do the following: ■ Click Add Server Manually. ■ In the Domain field, type the name of the domain. ■ In the Computer Name field, type the name of the computer. ■ Click OK. ■ Type the user name and password for this computer. ■ Click OK. To add the name of a computer manually Do the following: ■ Select the computer from the list. ■ Click Remove. To remove the name of a computer from the list of computers on which the Environment Check runs 6 Review the results of the Environment Check, and then to save the results, check Save Results To. To change the location where the Environment Check results are saved, click Change Path to browse to a new location. 7 Click Finish. Microsoft SQL Server 2008 Express Edition components installed with Backup Exec The Backup Exec installation program installs Microsoft SQL Server 2008 R2 Express with SP2 components that are required to run Backup Exec. Backup Exec prompts you to do one of the following: ■ Install the required Microsoft SQL Server Express components with Backup Exec and create a default Backup Exec instance. This is the recommended action. Note: SQL Express can be installed on a server that runs other instances of SQL Express or full versions of SQL. 46Installation Microsoft SQL Server 2008 Express Edition components installed with Backup Exec
- 47. ■ Select a Microsoft SQL Server 2005 (SP4) or SQL Server 2008/2012 instance that already exists on the network on which you want to run Backup Exec. If you choose to install Backup Exec into an existing SQL Server 2005 or 2008 instance, make sure that one of the following is installed before you continue with the installation: ■ SQL Server 2005 Service Pack 4 or later ■ SQL Server 2008 Service Pack 3 or later Caution: Backup Exec may not function properly if you install it into an existing SQL Server instance that uses case-sensitive collation. Symantec recommends that you avoid installing Backup Exec to a SQL Server instance that uses case-sensitive collation. When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. When Backup Exec applies updates, the SQL instance is stopped, which may cause other databases in the same instance to lose connectivity. If a remote SQL instance is used, ensure that Backup Exec has good network connectivity with the instance to avoid errors. A default local instance of SQL Express is recommended. You cannot install multiple Backup Exec Databases on the same SQL Server instance. Note: If you are installing a managed Backup Exec server, it is recommended that you select a local Microsoft SQL Server 2005 (SP4) instance or later on which to install the Backup Exec Database for this managed server. Do not select the same SQL Server instance that is used by the central administration server. See “System requirements for Backup Exec” on page 49. Backup Exec’s standard features The following features are included with Backup Exec at no additional cost. When you install Backup Exec, you can select any of these features that you want to use. 47Installation Backup Exec’s standard features
- 48. Table 2-3 Backup Exec’s standard features DescriptionFeature Installs the Symantec tape device drivers for all supported tape devices that are attached to the server. If there are no tape devices attached to your Backup Exec server, uncheck this option. Note: You do not need to install Symantec tape device drivers if Backup Exec runs on Windows Server 2012 and later. Symantec kernel-mode drivers and tapeinst.exe are no longer installed if Backup Exec runs on Windows Server 2012 or later. See “Installing Symantec tape device drivers ” on page 347. Tape Device Drivers Installs the Backup Exec Administrator’s Guide in a pdf file format. Online Documentation Enables support for tape libraries, or optical robotic libraries and library storage systems. Backup Exec includes support for one drive in every robotic library. Each additional drive in a library requires a Library Expansion Option license. Enable Robotic Library Support Enables you to copy configuration settings and logon information between Backup Exec servers. This option is recommended for environments that contain multiple Backup Exec servers. This option is required for the Central Admin Server Option (CASO). Copy Server Configurations Installs the managed Backup Exec server component of the Central Admin Server Option (CASO). You can install managed Backup Exec servers after you install a central administration server. Managed Backup Exec server Provides support for every single-drive Virtual Tape Library (VTL). You must purchase the Virtual Tape Library Unlimited Drive Option to support additional drives in each VTL. If you select this option, the Enable Robotic Library Support option is selected automatically. You cannot uncheck Enable Robotic Library Support unless you uncheck Virtual Tape Library Support. Virtual Tape Library Support All other options and agents require the purchase of additional licenses. Installing a trial version enables many options that must be purchased separately and are not included as part of Backup Exec. 48Installation Backup Exec’s standard features
- 49. If you have a licensed version of Backup Exec, you can use a trial version of most options and agents for a specified period of time. See “Installing a trial version of Backup Exec agents and options” on page 104. System requirements for Backup Exec The following are the minimum system requirements to run this version of Backup Exec: Table 2-4 Minimum system requirements RequirementsItem You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 Note: Backup Exec 15 supports the Backup Exec server installation on 64-bit operating systems only. You cannot install a Backup Exec server on a computer that runs the Windows Server Core installation option of Windows Server 2008/2012. You can only install the Backup Exec Agent for Windows on Server Core computers. On the computers that run Windows 2003, ensure that Windows Imaging Component is installed before you install Backup Exec 15. Windows Imaging Component is required to install Backup Exec. See the Microsoft website for more information on downloading and installing Windows Imaging Component. You cannot install SQL Express or SQL Server on a Windows Server 2008 computer that is configured in a Read Only Domain Controller (RODC) role. The Read Only Domain Controller role does not let you use the local accounts that are required for SQL Express and SQL Server. When you install Backup Exec on an RODC computer you must select a remote SQL instance for the Backup Exec Database. For Windows Server 2012 and later computers, you cannot install Backup Exec or the Agent for Windows on a volume that is enabled for deduplication in Windows or an ReFS volume. Operating system You can use Backup Exec with Microsoft System Center Operation Manager (SCOM) 2007 R2 and 2012 R2. Additional application support Internet Explorer 7.0 or later.Internet browser Intel Pentium, Xeon, AMD, or compatible.Processor 49Installation System requirements for Backup Exec
- 50. Table 2-4 Minimum system requirements (continued) RequirementsItem 800 x 600Screen resolution SQL Server 2008 R2 SP2.SQL Server or SQL Express Required: 1GB RAM above the operating system's requirements for the exclusive use by Backup Exec. Recommended: 2 GB RAM (or more for better performance) Note: RAM requirements may vary depending on the operations performed, the options installed, and the specific computer configuration. For the Central Admin Server Option: 1 GB RAM is required; 2 GB RAM is recommended. Symantec Recovery Disk: 1 GB minimum (dedicated) for the multi-lingual version. Virtual Memory Recommendations: 20 MB above the Windows recommended size for total paging file size (total for all disk volumes). Refer to your Microsoft Windows documentation for instructions on how to view or set the paging file size. Memory The Backup Exec user interface displays in the format that is configured in the Region and Language settings in the Control Panel. You can change the Backup Exec display language so that you can view user interface items in a different language. If Backup Exec does not support a language, the user interface displays in English. The user interface also displays in English if the menu and dialog boxes option is set to a language other than the language you want to display the user interface. If you do not use one of the supported languages listed in Table 2-5, you must install the English language pack in Windows. User interface language 1.26 GB (Typical installation) 1.91 GB (Includes all options) Note: Disk space requirements may vary depending on the operations performed, the options installed, and the specific system configuration. The Backup Exec Database and catalogs require additional space. An additional 525 MB is required for SQL Express. Any disk storage that you use also requires additional space. Installation disk space 50Installation System requirements for Backup Exec
- 51. Table 2-4 Minimum system requirements (continued) RequirementsItem The following hardware is recommended: ■ Network interface card or a virtual network adapter card. ■ CD/DVD drive. ■ A mouse. Other Hardware You can use storage media drives, robotic libraries, removable storage devices, and non-removable hard drives. You can find a list of compatible types of storage at the following URL: http://entsupport.symantec.com/umi/V-269-2 Support is available for the first drive in each robotic library when you purchase Backup Exec. To enable support for each additional robotic library drive, you must purchase the Backup Exec Library Expansion Option. Storage Hardware Table 2-5 Supported languages for the Backup Exec user interface Language codeLanguage ZHChinese (Simplified) CHChinese (Traditional) ENEnglish FRFrench DEGerman ITItalian JPJapanese KOKorean ESSpanish RURussian PTPortuguese (Brazilian ) See “Installing Backup Exec by using the Installation Wizard” on page 52. 51Installation System requirements for Backup Exec
- 52. Installing Backup Exec by using the Installation Wizard The Backup Exec installation program provides two methods of installation: typical and custom. A typical installation is a simpler installation method than a custom installation and is designed for small or uncomplicated environments. For example, if you use a local Backup Exec server and a few Backup Exec agents or options, then a typical installation may be best for you. A custom installation is designed for large or complex environments. You can also use the custom installation method if you prefer to set all of your options. For example, if you use a remote Backup Exec server or use the Enterprise Server Option, you should perform a custom installation. With a typical installation, Backup Exec makes the following decisions for you, based on common installation scenarios: ■ Backup Exec is installed to a local Backup Exec server. ■ SQL Express is installed with the default instance. ■ Agents and options are installed if you enter the licenses for them. If you do not enter any licenses, a trial version of Backup Exec is installed. A trial version enables many options that must be purchased separately and are not included as part of Backup Exec. Note: The installation program prevents you from selecting a license for an agent or option that is not compatible with the typical installation method, such as the Enterprise Server Option or the Archiving Option. ■ LiveUpdate runs automatically. Note: Before you install, make sure that your licenses for the Backup Exec version and any agents or options that you want to install are available. Licenses are required to install Backup Exec and its agents and options. However, you can install a trial version of Backup Exec without a license. Note: If you are installing the Archiving Option, ensure that the server does not have any unformatted hard drives. The Archiving Option cannot be installed on an unformatted drive. If your server has an unformatted drive, you should either format the drive or remove it before you attempt to install the Archiving Option. Choose either the typical installation or the custom installation: 52Installation Installing Backup Exec by using the Installation Wizard
- 53. How to install a typical installation How to install a custom installation How to install a typical installation Follow these steps to install a typical installation of Backup Exec. To install a typical installation of Backup Exec 1 From the installation media browser, click Install Products, and then select Backup Exec. If the required version of Microsoft .NET Framework is not already installed on this computer, Backup Exec installs it. The Backup Exec installation program uses the Microsoft .NET Framework version 4.5.2. However, not all versions of Windows support .NET Framework 4.5.2. If the Backup Exec installation program encounters an operating system that requires the use of a different version of the .NET Framework, Backup Exec blocks the installation and provides an error message that instructs you to install the required version of .NET Framework. 2 On the Welcome panel, read the license agreement, and then click I accept the terms of the license agreement. 3 Click Next. 4 On the Installation Type panel, click Typical installation, and then click Next. The Environment Check runs automatically. 5 Review the results of the Environment Check. 6 Do one of the following: ■ If the Environment Check does not reveal any issues that may prevent a successful installation of Backup Exec, click Next. ■ If the Environment Check reveals any issues that may prevent a successful installation of Backup Exec, click Cancel to exit the wizard. Correct the issues before you attempt to install Backup Exec again. 7 Select one of the following methods to add licenses: Do the following in the order listed: ■ In the Enter a Serial number field, type the appropriate serial number from your license certificate. ■ Click Add to List. ■ Repeat for each serial number. To enter serial numbers manually Note: An Internet connection is required to validate the serial numbers. If you do not have an Internet connection, import the licenses from the Symantec License File included with your license certificate or install a trial version. 53Installation Installing Backup Exec by using the Installation Wizard
- 54. Do the following in the order listed: ■ Click Import Symantec License File. ■ Browse to the location of your license files, and then select the appropriate file. To import licenses from the Symantec License File Do not type a serial number or import a license file. Go to step 8. To install a trial version 8 Click Next. You may be prompted to enter contact information for maintenance contract serial numbers. 9 If you entered product activation serial numbers, then on the Review Licenses panel, do one of the following: Do the following in the order listed: ■ In the Select a Backup Exec edition license to install on the computer field, select the Backup Exec edition to install. ■ Check the check boxes for the agents or options you want to install. ■ Click the drop-down menu, and then select the number of licenses that you want to install. To install a licensed version of Backup Exec In the Select a Backup Exec edition license to install on the computer field, select Trial. To install a trial version 10 Click Next. 54Installation Installing Backup Exec by using the Installation Wizard
- 55. 11 On the Service Account panel, provide a user name, password, and domain for an Administrator account that the Backup Exec system services can use. You cannot install Backup Exec with an account that has a blank password on a supported Windows Server unless Windows is configured to allow it. If you try to do so, the following error message appears when Backup Exec services are created: The account name and/or password supplied is not valid. Re-enter the login information and try again. You can, however, configure Windows to allow for blank passwords. For more information, see your Windows documentation. 12 If you want to change the directory where Backup Exec files are installed, click Change, and then select a new location. If you change the directory to a new location, ensure that you select a secure location where you can store sensitive data such as passwords. 13 Click Next. 14 If the SQL Express Setup panel appears, perform the following steps to identify the location of the SQL Express setup file: ■ Click Browse. ■ Navigate to the location where you downloaded the SQL Express 2008 R2 SP2 setup file. ■ Click OK. ■ Click Next. 15 On the Remote Computers panel, do one of the following: 55Installation Installing Backup Exec by using the Installation Wizard
- 56. Do the following in the order listed: ■ Click Add. ■ Select Add a Single Computer. ■ Type the fully qualified name of the remote computer or click Browse Remote Computers to locate the remote computer. ■ Under Remote computer credentials, type the credentials that Backup Exec can use to connect to the remote servers. You must use Administrator credentials. ■ Click Next. ■ In the Destination Folder field, enter the path where you want to install the files. ■ Click Next. ■ After all of the computers in the list are validated and the list is complete, click Next. To install the Agent for Windows on one remote computer 56Installation Installing Backup Exec by using the Installation Wizard
- 57. Do the following in the order listed: ■ Click Add. ■ Select Add Multiple Computers with the Same Settings. ■ Type the fully qualified name of the remote computer or click Browse to locate the remote computer. ■ Click Add to List. Type the fully qualified name and then click Add to List for all of the remote computers for which you want to push-install the Agent for Windows. ■ Under Remote computer credentials, type the credentials that Backup Exec can use to connect to the remote servers. You must use Administrator credentials. ■ Click Next. ■ In the Destination Folder field, enter the path where you want to install the files. ■ Click Next. ■ After all of the computers in the list are validated and the list is complete, click Next. To install the Agent for Windows on multiple computers using the same settings Click Next.To proceed without push-installing the Agent for Windows 16 Review the Backup Exec installation summary, and then click Install. 17 If you installed the Agent for Windows on remote computers, on the Remote Installation dialog box, click Next. 18 When the installation is complete, you can run LiveUpdate, choose to restart the system, view the readme, or remove the Backup Exec shortcut from the desktop. 19 Click Next, and then click Finish to exit the wizard. If you chose to restart the system, the computer will restart automatically. The installation process creates an installation log named BKUPINST15.htm in one of the following directories on the computer where Backup Exec is installed. ■ For Windows 2003: %allusersprofile%Application DataSymantecBackup ExecLogs 57Installation Installing Backup Exec by using the Installation Wizard
- 58. ■ For Windows 2008 and later: %programdata%SymantecBackup ExecLogs See “About the installation log” on page 104. How to install a custom installation Follow these steps to install a custom installation of Backup Exec. To install a custom installation of Backup Exec 1 From the installation media browser, click Install Products, and then select Backup Exec. If the required version of Microsoft .NET Framework is not already installed on this computer, Backup Exec installs it. The Backup Exec installation program uses the Microsoft .NET Framework version 4.5.2. However, not all versions of Windows support .NET Framework 4.5.2. If the Backup Exec installation program encounters an operating system that requires the use of a different version of the .NET Framework, Backup Exec blocks the installation and provides an error message that instructs you to install the required version of .NET Framework. 2 On the Welcome panel, read the license agreement, and then click I accept the terms of the license agreement. 3 Click Next. 4 On the Installation Type panel, click Custom installation, and then click Next. 5 On the Menu panel, check Local Installation, and then select Install Backup Exec software and options. 6 Click Next. The Backup Exec Environment Check runs automatically after you click Next. 7 Review the results of the Environment Check. 8 Do one of the following: ■ If the Environment Check does not reveal any issues that may prevent a successful installation of Backup Exec, click Next. ■ If the Environment Check reveals any issues that may prevent a successful installation of Backup Exec, click Cancel to exit the wizard. Correct the issues before you attempt to install Backup Exec again. 9 Select one of the following methods to enter licenses: 58Installation Installing Backup Exec by using the Installation Wizard
- 59. Do the following in the order listed: ■ In the Enter a Serial number field, type the appropriate serial number from your license certificate. ■ Click Add to List. ■ Repeat for each license for each option or agent that you want to install. ■ Click Next to validate the serial numbers. To enter serial numbers manually Note: An Internet connection is required to validate the serial numbers. If you do not have an Internet connection, import the licenses from the Symantec License File or install a trial version. Do the following in the order listed: ■ Click Import Symantec License File. ■ Browse to the location of your license files, and then select the appropriate file. To import licenses from the Symantec License file Do not type a serial number or import a license file. Go to step 10. To install a trial version 10 Click Next. You may be prompted to enter contact information for maintenance contract serial numbers. 11 If you entered product activation serial numbers, on the Review Licenses panel, do one of the following: Do the following in the order listed: ■ In the Select a Backup Exec edition license to install on the computer field, select the Backup Exec edition to install. ■ Check the check boxes for the agents or options you want to install. ■ Click the drop-down menu, and then select the number of licenses that you want to install. To install a licensed version of Backup Exec In the Select a Backup Exec edition license to install on the computer field, select Trial. To install a trial version 12 Click Next. 59Installation Installing Backup Exec by using the Installation Wizard
- 60. 13 On the Configure Options panel, select any additional options that you want to install. For example, you can select additional standard features, or you can select the agents or the options that are available for a trial installation. 14 Click Next. If you selected the File System Archiving Option or the Microsoft Exchange Mailbox Archiving Option, the Archiving Option Environment Check runs in the background. The Archiving Option Environment Check verifies that the computer meets the minimum requirements for installing and configuring the options. If the computer does not meet the minimum requirements, you must uncheck the archiving options or fix the errors before you can continue with the installation. 15 If you want to install Backup Exec for any additional languages, select the language, and then click Next. 16 On the Destination panel, do the following: ■ Review the disk space requirements for the items that you selected to install. ■ If you want to change the directory where the Backup Exec files are installed, click Change, and then select a new directory or create a new folder. Symantec recommends that you do not select a mount point as the destination directory because if you delete the mount point, Backup Exec is uninstalled. 17 Click Next. 18 Provide a user name, password, and domain for an Administrator account that the Backup Exec system services can use, and then click Next. You cannot install Backup Exec with an account that has a blank password on a supported Windows Server unless Windows is configured to allow it. If you try to do so, the following error message appears when Backup Exec services are created: The account name and/or password supplied is not valid. Re-enter the login information and try again. You can, however, configure Windows to allow for blank passwords. For more information, see your Windows documentation. 19 On the Choose SQL Server panel, do one of the following to select a location to store the Backup Exec Database. 60Installation Installing Backup Exec by using the Installation Wizard
- 61. Note: The Choose SQL Server panel does not appear for upgrades. You cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BE Utility. Do the following in the order listed: ■ Click Create a local Backup Exec SQL Express instance to store the Backup Exec database. ■ To change the location of the Backup Exec SQL Express instance, click Browse. ■ Select the location, and then click OK. To create a local Backup Exec SQL Express instance Do the following in the order listed: ■ Click Use an existing instance of SQL Server 2005 SP4 or later, SQL Server 2008 SP3 or later, or SQL Server 2012. ■ Select the instance. When Backup Exec is installed into an existing instance, the automated Master database restore feature is not available. To recover the Master database, replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. See “Microsoft SQL Server 2008 Express Edition components installed with Backup Exec” on page 46. To use an existing SQL Server 2005/2008/2012 instance 20 Click Next. Backup Exec attempts to connect to the instance. 21 If the SQL Express Setup panel appears, perform the following steps to identify the location of the SQL Express setup file: ■ Click Browse. ■ Navigate to the location where you downloaded the SQL Express 2008 R2 SP2 setup file. ■ Click OK. ■ Click Next. 61Installation Installing Backup Exec by using the Installation Wizard
- 62. 22 If you are prompted, select how the Symantec Device Driver Installer should install device drivers for the tape storage devices that are connected to the server, and then click Next. Symantec recommends that you select Use Symantec device drivers for all tape devices. 23 If you are prompted, enter information or choose settings for the additional options that you want to install, and then click Next after each selection. 24 Review the Backup Exec installation summary, and then click Install. The installation process takes several minutes to complete. During the process, the progress bar may not move for several minutes. 25 When the installation is complete, you can run LiveUpdate, choose to restart the system, view the readme, or remove the Backup Exec shortcut from the desktop. 26 Click Next, and then click Finish to exit the wizard. If you chose to restart the system, the computer will restart automatically. Installing additional Backup Exec options to the local Backup Exec server You can install agents and options when you install Backup Exec. However, if you have already installed Backup Exec and want to install additional options, review the documentation for those options to ensure that your system meets all minimum requirements. The Backup Exec services may be stopped while the additional options are installed. If any active jobs are running, you are prompted to stop them, or to wait for the jobs to finish. If you have a licensed version of Backup Exec, you can use a trial version of most options and agents for a specified period of time. See “Installing a trial version of Backup Exec agents and options” on page 104. Note: If the Central Admin Server Option is installed, and you want to install additional options on a managed Backup Exec server, you can pause the managed Backup Exec server. When a managed Backup Exec server is paused, the administration server does not delegate jobs to it. When the installation is complete, un-pause, or resume, the managed Backup Exec server. See “Pausing or resuming a managed Backup Exec server” on page 1158. 62Installation Installing additional Backup Exec options to the local Backup Exec server
- 63. To install additional Backup Exec options to the local Backup Exec server 1 Click the Backup Exec button, select Installation and Licensing, and then select Install Options and Licenses on this Backup Exec Server. You may be prompted to insert the installation media. 2 Do one of the following: Do the following in the order listed: ■ In the Enter a Serial number field, type the appropriate serial number from your license certificate. ■ Click Add to List. ■ Repeat for each serial number. To enter serial numbers manually Note: An Internet connection is required to validate the serial numbers. If you do not have an Internet connection, import the licenses from the Symantec License File or install a trial version. Do the following in the order listed: ■ Click Import Symantec License File. ■ Browse to the location of your license files, and then select the appropriate file. To import licenses from the Symantec license file Do not type a serial number or import a license file. Go to step 5. To install a trial version 3 Click Next. You may be prompted to enter contact information for maintenance contract serial numbers. 4 If you entered product activation serial numbers, on the Review Licenses panel, do one of the following: Do the following in the order listed: ■ In the Select a Backup Exec edition license to install on the computer field, select the Backup Exec edition to install. ■ Check the check boxes for the agents or options you want to install. ■ Click the drop-down menu, and then select the number of licenses that you want to install. To install a licensed version of Backup Exec 63Installation Installing additional Backup Exec options to the local Backup Exec server
- 64. In the Select a Backup Exec edition license to install on the computer field, select Trial. To install a trial version 5 Click Next. 6 Do the following: ■ Check the check boxes for the additional options that you want to install. ■ Uncheck the check boxes for the options that you want to remove. 7 Click Next. 8 If you are prompted, enter information or choose settings for the additional options that you want to install. Click Next after each selection. 9 Review the Backup Exec installation summary, and then click Install. The Backup Exec services are stopped while the additional options are installed. If any active jobs are running, you are prompted to stop them, or to wait for the jobs to finish. When the installation is complete, the services are restarted. 10 Click Finish. Push-installing Backup Exec to remote computers You cannot push install Backup Exec in the following scenarios: ■ Push install from a 64-bit operating system to a 32-bit operating system ■ Push install from a 32-bit operating system to a 32-bit or a 64-bit operating system If you install Backup Exec through Terminal Services and the installation media is on a shared drive (network share) you must use a UNC path. Installation by mapped drives is not supported. You can set up multiple server installations. Backup Exec processes up to five remote computer installations concurrently. 64Installation Push-installing Backup Exec to remote computers
- 65. Note: Backup Exec installs the required version of Microsoft .NET Framework if it is not already installed on the computer where you want to push-install Backup Exec. The Backup Exec installation program uses the Microsoft .NET Framework version 4.5.2. However, not all versions of Windows support .NET Framework 4.5.2. If the Backup Exec installation program encounters an operating system that requires the use of a different version of the .NET Framework, Backup Exec blocks the installation and provides an error message that instructs you to install the required version of .NET Framework. Before you install Backup Exec to remote computers, you should review the special considerations. Table 2-6 Special considerations for installing Backup Exec to remote computers ConsiderationItem To push-install Backup Exec to a Windows Server 2003 computer, you must enable File and Printer Sharing on the Windows Firewall Exceptions list for the following ports: ■ 135 (RPC) ■ 445 (TCP) ■ 103X (mostly 1037) ■ 441 (RPC) For more information about the Windows Firewall Exceptions list, refer to your Microsoft Windows documentation. During the installation process, Backup Exec sets the Remote Launch and remote access security permissions for the Administrator’s group. You should enable the "Allow remote administration exception" group policy for the computer to which you push the installation. Windows Server 2003 SP2 65Installation Push-installing Backup Exec to remote computers
- 66. Table 2-6 Special considerations for installing Backup Exec to remote computers (continued) ConsiderationItem To push-install Backup Exec to a computer that runs Windows Server 2008 or later, you must enable the following items on the destination computer’s Windows Firewall Exceptions list ■ File and Printer Sharing ■ Windows Management Instrumentation (WMI) For more information, refer to your Microsoft Windows documentation. You cannot install Backup Exec on a volume that has been enabled for deduplication in Windows or on an ReFS volume. Windows Server 2008 or later To push-install Backup Exec to a computer that runs Symantec Endpoint Protection (SEP) version 11.0 or later, you must configure SEP to share files and printers. The file and printer sharing feature is turned off by default. Symantec Endpoint Protection (SEP) 11.0 or later Note: You can also use Microsoft’s Add or Remove Programs utility to install Backup Exec to a remote computer. See your Microsoft documentation for more information. The installation process creates an installation log named BKUPINST15.htm in one of the following directories on the computer where Backup Exec is installed. ■ For Windows 2003: %allusersprofile%Application DataSymantecBackup ExecLogs ■ For Windows 2008 and later: %programdata%SymantecBackup ExecLogs To push-install Backup Exec to remote computers 1 Do one of the following: 66Installation Push-installing Backup Exec to remote computers
- 67. Do the following steps in the order listed: ■ From the installation media browser, click Install Products, and then click Backup Exec. ■ On the Welcome panel, click Next. ■ Select I accept the terms of the license agreement, and the click Next. ■ Select Custom installation. ■ Uncheck Local Installation, and then check Remote Installation. ■ Click Next. To push-install Backup Exec to remote computers from the installation media Click the Backup Exec button, select Installation and Licensing, and then select Install Agents and Backup Exec Servers on Other Servers. To push-install Backup Exec to remote computers from the Backup Exec server 2 On the Remote Computers panel, do one of the following: Do the following in the order listed: ■ Click Add. ■ Select Add a Single Computer. ■ Select Symantec Backup Exec, and then click Next. ■ Type the fully qualified name of the remote computer or click Browse Remote Computers to locate the remote computer. To install Backup Exec on one remote computer Do the following in the order listed: ■ Click Add. ■ Select Add Multiple Computers with the Same Settings. ■ Select Symantec Backup Exec, and then click Next. ■ Type the fully qualified name of the remote computer or click Browse to locate the remote computer. ■ Click Add to List. Type the fully qualified name and then click Add to List for all of the remote computers for which you want to push install the options. To install Backup Exec on multiple computers using the same settings 67Installation Push-installing Backup Exec to remote computers
- 68. 3 Under Remote computer credentials, type the credentials that Backup Exec can use to connect to the remote servers. You must use Administrator credentials. 4 Click Next. 5 Select one of the following methods to enter licenses: Do the following in the order listed: ■ In the Enter a Serial number field, type the appropriate serial number from your license certificate. ■ Click Add to List. ■ Repeat for each license for each option or agent that you want to install. ■ Click Next to validate the serial numbers. To enter serial numbers from your license certificate Note: An Internet connection is required to validate the serial numbers. If you do not have an Internet connection, import the licenses from the Symantec License File or install a trial version. Do the following in the order listed: ■ Click Import Symantec License File. ■ Browse to the location of your license files, and then select the appropriate file. To import licenses from a Symantec License File Do not type a serial number or import a license file. Go to step 8.To install a trial version 6 Click Next. You may be prompted to enter contact information for maintenance contract serial numbers. 7 If you entered product activation serial numbers, on the Review Licenses panel, do one of the following: 68Installation Push-installing Backup Exec to remote computers
- 69. Do the following in the order listed: ■ In the Select a Backup Exec edition license to install on the computer field, select the Backup Exec edition to install. ■ Check the check boxes for the agents or options you want to install. ■ Click the drop-down menu, and then select the number of licenses that you want to install. To install a licensed version of Backup Exec In the Select a Backup Exec edition license to install on the computer field, select Trial. To install a trial version 8 Click Next. 9 On the Configure Options panel, select any additional options that you want to install. For example, you can select additional standard features, or you can select the agents or the options that are available for a trial installation. 10 In the Destination Folder field, enter the location where you want to install Backup Exec. 11 Click Next. 12 Complete the service account credentials options as follows: Type the user name for an Administrator account that the Backup Exec services can use. If the remote computer is in a domain, use a domain administrator's account or an equivalent account that is part of the domain administrator's group. If the remote computer is in a workgroup, use an administrator's account or an equivalent account that is part of the administrator's group on the computer. User Name Type the password for an administrator account that the Backup Exec services can use. Password If the computer is in a domain, select the domain in which the computer is located. If the computer is in a workgroup, select the computer name. Domain 69Installation Push-installing Backup Exec to remote computers
- 70. 13 Click Next. 14 Do one of the following to select a location on which to store the Backup Exec Database, and then click Next. Do the following in the order listed: ■ Click Create a local Backup Exec SQL Express instance to store the Backup Exec database. ■ To change the location of the database, type the new location in the Destination Folder field. To create a local Backup Exec SQL Express instance Do the following in the order listed: ■ Click Use an existing instance of SQL Server 2005 SP4 or later or SQL Server 2008/2012. ■ Select the instance. When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. See “Microsoft SQL Server 2008 Express Edition components installed with Backup Exec” on page 46. To use an existing SQL Server 2005 or SQL Server 2008 instance Backup Exec attempts to connect to the instance. This step is skipped during upgrades. 15 Click Next. 16 Make a selection for tape device drivers, and then click Next. Note: You do not need to install Symantec tape device drivers if Backup Exec runs on Windows Server 2012 and later. Symantec kernel-mode drivers and tapeinst.exe are no longer installed if Backup Exec runs on Windows Server 2012 and later. See “Installing Symantec tape device drivers ” on page 347. 17 Click Next. 70Installation Push-installing Backup Exec to remote computers
- 71. 18 If you are prompted, enter information or choose settings for additional options that are being installed, and then click Next or OK after each selection. 19 After Backup Exec validates the remote computers, you can change the list in any of the following ways: Click Add, and then click Add a Single Computer. To manually add one remote computer Click Add, and then click Add Multiple Computers with the Same Settings. To manually add multiple remote computers Click Import and Export, and then select one of the following options: ■ Select Import from File to enable Backup Exec to add the names of the remote computers from a selected list. ■ Select Import Servers Published to this Backup Exec server to enable Backup Exec to add the names of all the remote computers that are set up to publish to this Backup Exec server. You must enter remote computer logon credentials for the list of remote computers. To add multiple remote computers by importing an existing list of computers Select the remote computer that you want to change, and then click Edit. To change the product that you selected to install or to change other properties you selected for this installation Select the remote computer that you want to delete, and then click Delete. To delete a remote computer from the list Verify that Save the server list for future remote install sessions is checked. This option enables the names and the credentials of all of the remote computers to be added automatically the next time you install Backup Exec or options to these remote computers. To save this list of remote computers and the associated remote computer logon credentials 71Installation Push-installing Backup Exec to remote computers
- 72. Click Import and Export, and then click Export to File. You can select the location to save the Push_Export.xml file. This option is useful if you want to use the same list for multiple Backup Exec servers. When you import the list, you must re-enter the remote computer logon credentials. To save the list of remote computers to an XML file Right-click the name of the computer, and then click Fix Error. To fix the errors that were located during the validation Right-click the name of the computer, and then click Retry Validation. To enable Backup Exec to attempt to re-validate an invalid remote computer 20 After all of the computers in the list are validated and the list is complete, click Next. 21 Review the Backup Exec installation summary, and then click Install. See “About the installation log” on page 104. 22 Click Next, and then click Finish to exit the wizard. If you did not restart the remote computer, you may need to do it now in order for the configuration to take effect. Methods for installing the Agent for Windows You can install the Agent for Windows by using the following methods, depending on your environment: ■ Push-install the Agent for Windows to one or more remote computers from the Backup Exec server. See “Push-installing the Agent for Windows to remote computers” on page 73. ■ Add the remote computer to the list of servers and install the Agent for Windows on the remote computer. See “Adding servers that you want to back up to the list of servers on the Backup and Restore tab” on page 140. ■ Use a Microsoft Active Directory network to centrally manage the installation of the Agent for Windows to computers in the network. See “Installing the Agent for Windows in an Active Directory network” on page 80. ■ Use a command prompt. 72Installation Methods for installing the Agent for Windows
- 73. See “Using a command prompt to install the Agent for Windows on a remote computer” on page 84. ■ Use command script files. See “Using a command script to install the Agent for Windows” on page 87. Push-installing the Agent for Windows to remote computers You can push-install the Agent for Windows to remote computers from a Backup Exec server. Push installations save time by eliminating the need for local access at the target computer for the installation to be successful. You can push-install the Agent for Windows to an unlimited number of remote computers. Backup Exec can process up to five active push-installations at a time. Review the following special considerations before you install the Agent for Windows on remote computers. Table 2-7 Special considerations for installing the Agent for Windows ConsiderationItem You cannot push-install the Agent for Windows when the remote computer is in the ForceGuest configuration and it is not in a domain. ForceGuest is an operating system configuration that limits incoming users to Guest-level access. Instead, use the installation media or the network to install the Agent for Windows on the Windows computer. You can also turn off ForceGuest. Refer to your Microsoft Windows documentation for more information. See “Installing Backup Exec using the command line (silent mode)” on page 94. ForceGuest configuration Backup Exec installs a command-line version of the Agent for Windows on the computers that run the Server Core installation option of Windows Server 2008/2012. The Backup Exec Agent Utility command-line applet is installed with the Agent for Windows. This applet lets you monitor Backup Exec operations on the remote computer. See “Backup Exec Agent Utility Command Line Applet switches” on page 787. Server core option of Windows Server 2008/2012 73Installation Methods for installing the Agent for Windows
- 74. Table 2-7 Special considerations for installing the Agent for Windows (continued) ConsiderationItem You cannot install the Agent for Windows on a volume that is enabled for deduplication in Windows or on an ReFS volume. Windows deduplication and ReFS volumes To push-install Backup Exec options to a Windows Server 2003 SP2 computer, you must enable File and Printer Sharing on the Windows Firewall Exceptions list for the following ports: ■ 135 (RPC) ■ 445 (TCP) ■ 103X (mostly 1037) ■ 441 (RPC) For more information about the Windows Firewall Exceptions list, refer to your Microsoft Windows documentation. You must install .NET Framework 2.0 SP2 on any Windows Server 2003 computers before you begin the installation. During the installation process, Backup Exec sets the Remote Launch and remote access security permissions for the Administrator’s group. You should enable the "Allow remote administration exception" group policy for the computer to which you push the installation. Windows Server 2003 SP2 74Installation Methods for installing the Agent for Windows
- 75. Table 2-7 Special considerations for installing the Agent for Windows (continued) ConsiderationItem To push-install Backup Exec options to a computer that runs Windows Vista/ Server 2008/Server 2008 R2/7/ 8/8.1/Server 2012/Server 2012 R2, you must enable certain items on the destination computer’s Windows Firewall Exceptions list. You must enable the following items: ■ File and Printer Sharing ■ Windows Management Instrumentation (WMI) For more information, refer to your Microsoft Windows documentation. To push-install to a computer that runs the supported Backup Exec server, the destination computer must be part of a domain. For more information, refer to the Microsoft knowledge base. Windows Vista/ Server 2008/Server 2008 R2/7/ 8/8.1/Server 2012/Server 2012 R2 To push-install options to a computer that runs Symantec Endpoint Protection (SEP) version 11.0 or later, you must configure SEP to share files and printers. File and printer sharing is turned off by default. Symantec Endpoint Protection 11.0 or later When you connect to a remote computer from the Backup Exec server, you must establish a trust between the Backup Exec server and the remote computer to ensure secure communication. To establish the trust, you must add the remote computer to the list of servers on the Backup and Restore tab. See “About the list of servers on the Backup and Restore tab” on page 139. Trust the Backup Exec server and remote computer The installation process creates an installation log named BKUPINST15.htm on the computer where Backup Exec is installed, and also creates an installation log named RAWSinst15.htm on the remote computer. See “About the installation log” on page 104. 75Installation Methods for installing the Agent for Windows
- 76. If there are problems installing the Agent for Windows using this method, you can try to manually install the Agent for Windows. See “Using a command prompt to install the Agent for Windows on a remote computer” on page 84. To push-install the Agent for Windows to remote computers 1 Do one of the following: Do the following steps in the order listed: ■ From the installation media browser, click Installation, and then click Backup Exec. ■ On the Welcome panel, select I accept the terms of the license agreement, and the click Next. ■ Click Custom installation. ■ Uncheck Local Installation, and then check Remote Installation. ■ Click Next. To push-install the Agent for Windows to remote computers from the installation media Click the Backup Exec button, select Installation and Licensing, and then select Install Agents and Backup Exec Servers on Other Servers. To push-install the Agent for Windows to remote computers from the Backup Exec server 2 Do one of the following Do the following steps in the order listed: ■ On the Remote Computers panel, click Add. ■ Select Add a Single Computer. ■ Select Agent for Windows, and then click Next. ■ Type the fully qualified name of the remote computer or click Browse Remote Computers to locate the remote computer. To install the Agent for Windows on one remote computer 76Installation Methods for installing the Agent for Windows
- 77. Do the following steps in the order listed: ■ On the Remote Computers panel, click Add. ■ Select Add Multiple Computers with the Same Settings. ■ Select Agent for Windows, and then click Next. ■ Type the fully qualified name of the remote computer or click Browse to locate the remote computer. ■ Click Add to List. Type the fully qualified name and then click Add to List for all of the remote computers for which you want to push install the options. To install the Agent for Windows on multiple computers using the same settings 3 Under Remote computer credentials, type the credentials that Backup Exec can use to connect to the remote servers. You must use Administrator credentials. 4 Click Next. 5 In the Destination Folder field, enter the path where you want to install the files. 6 Click Next. 7 After Backup Exec validates the remote computers, you can change the list in any of the following ways: Click Add, and then click Add a Single Computer. To manually add one remote computer Click Add, and then click Add Multiple Computers with the Same Settings. To manually add multiple remote computers 77Installation Methods for installing the Agent for Windows
- 78. Click Import and Export, and then select one of the following options: ■ Select Import from File to enable Backup Exec to add the names of the remote computers from a selected list. ■ Select Import Servers Published to this Backup Exec server to enable Backup Exec to add the names of all the remote computers that are set up to publish to this Backup Exec server. You must enter remote computer logon credentials for the list of remote computers. To add multiple remote computers by importing an existing list of computers Select the remote computer that you want to change, and then click Edit. To change the product that you selected to install or to change other properties you selected for this installation Select the remote computer that you want to delete, and then click Delete. To delete a remote computer from the list Verify that Save the server list for future remote install sessions is checked. This option enables the names of all of the remote computers and their credentials to be added automatically the next time you want to install Backup Exec or options to these remote computers To save this list of remote computers and the associated remote computer logon credentials Click Import and Export, and then click Export to File. You can select the location to save the XML file. This option is useful if you want to use the same list for multiple Backup Exec servers. When you import the list, you must re-enter the remote computer logon credentials. To save the list of remote computers to an XML file Right-click the name of the computer, and then click Fix Errors. To fix the errors that were located during the validation Right-click the name of the computer, and then click Retry Validation. To enable Backup Exec to attempt to re-validate an invalid remote computer 8 After all of the computers in the list are validated and the list is complete, click Next. 78Installation Methods for installing the Agent for Windows
- 79. 9 Review the Backup Exec installation summary, and then click Install. See “About the installation log” on page 104. 10 Click Next, and then click Finish to exit the wizard. If you did not restart the remote computer, you may need to do it now in order for the configuration to take effect. Installing updates to the Agent for Windows on remote computers When a Backup Exec server is updated with patches, an alert is generated to warn you that the Agent for Windows on remote computers must be updated with the same patches. Additionally, in the properties for the remote computer, the property Do the updates installed on this server match the updates installed on the backup server indicates whether the remote computer is up to date with the Backup Exec server. From the Backup Exec console, you can update the remote computers immediately, at a scheduled time, or on a recurring schedule. You can also update a group of remote computers together. See “Updating Backup Exec with LiveUpdate” on page 106. To install updates for the Agent for Windows 1 On the Backup and Restore tab, right-click the remote computer or the group that needs to be updated. 2 Select Update. 79Installation Methods for installing the Agent for Windows
- 80. 3 On the Install Updates dialog box, select the option for when you want to install the updates. Select this option to create a recurring schedule for the job. Recurrence If you choose to make the job recur on a schedule, configure the frequency with which the job recurs. You can select to run the job in hourly, daily, weekly, monthly, or yearly increments. Recurrence Pattern Enter the date on which you want the schedule to take effect. Starting on View all the scheduled jobs on the calendar to check for scheduling conflicts. Calendar Specify the maximum amount of time after the scheduled start time at which you want Backup Exec to consider the job to be missed and reschedule it. Keep the job scheduled for x hours before it is rescheduled Specify the amount of time after the job's scheduled start time at which you want Backup Exec to cancel the job if it is still running. Cancel the job if it is still running x hours after its scheduled start time Select this option to run the job immediately without scheduling any more instances of it for the future. Run now with no recurring schedule Select a specific date on which to run the job without scheduling any more instances of it for the future. Run on Select this option to enable Backup Exec to automatically restart the remote computer, if required. Restart the computer automatically after installing the updates to the Symantec Backup Exec Agent for Windows when a restart is required 4 Click OK. Installing the Agent for Windows in an Active Directory network You can centrally manage the installation of the Backup Exec Agent for Windows to computers in an Active Directory network. You configure the installation once, and then use a Group Policy Object to assign that installation to computers in an 80Installation Methods for installing the Agent for Windows
- 81. Organizational Unit. The options are installed automatically whenever a computer in the Organizational Unit is started. Note: Review your organization’s deployment plans before you implement a rollout of the Backup Exec Agent for Windows to client computers. You should also review your Group Policy Desktop Management and Active Directory documentation. Table 2-8 How to install the Agent for Windows in an Active Directory Network DescriptionAction A transform contains the changes that you want to make to the Windows Installer package for the Agent for Windows when a computer starts, such as the installation path. Requirements to create a transform are as follows: ■ The computer on which you want to create the transform must have Microsoft Windows 2003 or later. ■ Any Windows Server 2003 computers on which you want to install the Agent for Windows must be running .NET Framework 2.0 SP2. ■ The computers on which you want to install the Agent for Windows must be running MSXML 6.0 SP2. ■ The computers on which you want to install the Agent for Windows must be running Microsoft Visual C++ Runtime 8.0/9.0/10.0/11.0. You can configure a Group Policy object to deploy all of the Microsoft Visual C++ Runtime components or install them manually on each Agent for Windows computer. For more information about configuring a Group Policy object, see your Microsoft Windows documentation. ■ Only assignment to computers is supported. Assignment to users is not supported. Create a transform for the Agent for Windows. See the section called “Creating a transform” on page 82. 81Installation Methods for installing the Agent for Windows
- 82. Table 2-8 How to install the Agent for Windows in an Active Directory Network (continued) DescriptionAction You must copy the transform that you create, and the Backup Exec RAWS32 or RAWSX64 directory, to the distribution point. Create a distribution point (share) that contains the source file of the Agent for Windows that you want to install. See the section called “Creating a software distribution point (share)” on page 83. The software is installed automatically when the computers in the Organizational Unit are started. Configure a Group Policy Object to assign the transform and the RAWS32 or RAWSX64 directory in the distribution point to computers in an Active Directory Organizational Unit. See the section called “Configuring a Group Policy Object” on page 83. Creating a transform To create a transform 1 Do one of the following: ■ From the Backup Exec installation media browser, click Install Products, and then click Agent for Windows. ■ From a Backup Exec server on which Backup Exec is installed, go to Program FilesSymantecBackup ExecAgentsRAWS32 or RAWSX64 and double-click Setup.exe. 2 On the Welcome panel, click Next. 3 On the Install Type panel, click Create a Transform to use Active Directory to install the Agent for Windows, and then click Next. 4 On the Install Option panel, in the Destination Folder area, enter the path where you want to install the files. 5 Click Next. 6 Enter a file name and a path where the transform will be created, and then click Next. Use a meaningful file name for the transform. For example, the name can include the names of the options in the transform and the platform you plan to apply the transform to, such as AgentDefaultPathNoPublishing. 7 To create the transform, click Install. 8 After the transform is created, set up a distribution point for the source files. 82Installation Methods for installing the Agent for Windows
- 83. Creating a software distribution point (share) To install the Agent for Windows in an Active Directory network, you must create a software distribution point after you create a transform. Table 2-9 How to create a software distribution point (share) DescriptionStep Create a shared folder, and then set permissions so that the client computers that will run the installation have access to the shared folder. Step 1 Copy the following directories from the Backup Exec server to the shared folder: ■ RAWS32 or RAWSX64 ■ MSXML ■ VCRedist ■ DotNetFx By default, these folders are located in Program FilesSymantecBackup ExecAgents. Step 2 Copy the transform from the path where it was created to the RAWS32 or RAWSX64 directory on the shared folder. Step 3 Configure a Group Policy Object to deploy the source files. Step 4 Configuring a Group Policy Object To install the Agent for Windows in an Active Directory network, you must configure a Group Policy Object after you create a software distribution point and create a transform. To configure a Group Policy Object to deploy the software 1 From the Active Directory snap-in that manages users and groups, click Properties, and create a new Group Policy Object or edit an existing one. Refer to your Microsoft Windows documentation for information on creating a Group Policy Object. 2 Under Computer Configuration, expand Software Settings. 3 Right-click Software Installation, click New, and then click Package. 83Installation Methods for installing the Agent for Windows
- 84. 4 On the File Open dialog box, browse to the software distribution point by using the Universal Naming Convention (UNC) name, for example, server nameshare name, select the package file, and then click Open. 5 Select the package file Symantec Backup Exec Agent for Windows.msi, and then click Open. 6 When you are prompted, apply the Advanced Option. 7 After Active Directory checks the MSI package, on the General Properties tab, make sure that the correct versions of the options are being installed. 8 On the Deployment tab, set up the configuration for your environment. Make sure the option Make this 32-bit x86 application available to WIN64 machines is not selected. If you want the Agent for Windows to be uninstalled if the computer is removed from the Organization Unit, select the option Uninstall this application when it falls out of the scope of management. 9 On the Modifications tab, click Add, browse to the share, and select the transform that you created. 10 Select Open, and make any other changes that are necessary, and then click OK. 11 Close all of the dialog boxes. When a computer in the Organizational Unit that you specified is started, the transform is processed and the options that you specified are installed. 12 View the installation log that is created on the destination computers to verify the installation of the Agent for Windows. Using a command prompt to install the Agent for Windows on a remote computer You can install the Agent for Windows by using a command prompt. The installation process creates an installation log named RAWSinst15.htm. See “About the installation log” on page 104. 84Installation Methods for installing the Agent for Windows
- 85. To use a command prompt to install the Agent for Windows on a remote computer 1 At a remote computer, map a drive letter to the Agents directory. By default, the Agents directory is located at the following path: Program FilesSymantecBackup ExecAgents or you can copy the following folders to the same local directory: RAWS32, MSXML, VCRedist, and DotNetFx folders To install to a 32-bit computer: RAWSX64, MSXML, VCRedist, and DotNetFx folders To install to a 64-bit computer: 2 Open a command prompt and type the drive letter that you mapped in step 1 and the following path: RAWS32To install to a 32-bit computer: RAWSX64To install to a 64-bit computer: 85Installation Methods for installing the Agent for Windows
- 86. 3 Do one of the following: Run the following command: setup.exe /RANT32: /S: /DISADVRT: To install the Agent for Windows to a 32-bit computer without publishing enabled Run the following command: setup.exe /RANT32: /S: /ADVRT: Backup Exec server name 1 Backup Exec server name 2 To install the Agent for Windows to a 32-bit computer with publishing enabled Run the following command: setup.exe/RANT32: /S: /BOOT: To install the Agent for Windows to a 32-bit computer and restart the computer automatically Run the following command: setup.exe /RAWSX64: /S: /DISADVRT: To install the Agent for Windows to a 64-bit computer without publishing enabled Run the following command: setup.exe /RAWSX64: /S: /ADVRT: Backup Exec server name 1 Backup Exec server name 2 To install the Agent for Windows to a 64-bit computer with publishing enabled Run the following command: setup.exe /RAWSX64 /S: /BOOT: To install the Agent for Windows to a 64-bit computer and restart the computer automatically The Agent for Windows is installed on the remote computer in the following directory: Program FilesSymantecBackup ExecRAWS32 If you installed the Agent for Windows to a 32-bit computer: Program FilesSymantecBackup ExecRAWSx64 If you installed the Agent for Windows to a 64-bit computer: Using a command prompt to uninstall the Agent for Windows from a remote computer You can uninstall the Agent for Windows by using a command prompt. 86Installation Methods for installing the Agent for Windows
- 87. To use a command prompt to uninstall the Agent for Windows from a remote computer 1 At the remote computer, map a drive letter to the Agent for Windows directory using the following path: Program FilesSymantecBackup ExecAgentsRAWS32 To uninstall the Agent for Windows from a 32-bit computer: Program FilesSymantecBackup ExecAgentsRAWSX64 To uninstall the Agent for Windows from a 64-bit computer: 2 Open a command prompt, and then type the drive letter that you mapped in step 1. 3 Run the following command: setup.exe /RANT32: /S: /U: The /S: parameter is used to run the operation in silent mode, without the benefit of a user interface. The /U: parameter specifies an uninstall operation. To uninstall the Agent for Windows from a 32-bit computer: setup.exe /RAWSX64: /S: /U:To uninstall the Agent for Windows from a 64-bit computer: See “Using a command prompt to install the Agent for Windows on a remote computer” on page 84. Using a command script to install the Agent for Windows You can use command script files to install the Agent for Windows. The command script files are included in the Backup Exec installation directory. The installation process creates an installation log named RAWSinst15.htm. See “About the installation log” on page 104. 87Installation Methods for installing the Agent for Windows
- 88. To use a command script to install the Agent for Windows 1 Map a drive letter to the Agents directory on a Backup Exec server. By default, the Agents directory is located at the following path: Program FilesSymantecBackup ExecAgents 2 Do one of the following: In the RAWS32 directory, double-click setupaa. To install the Agent for Windows on a 32-bit computer In the RAWSX64 directory, double-click setupaax64. To install the Agent for Windows on a 64-bit computer Using a command script to uninstall the Agent for Windows A command script file is available to uninstall the Agent for Windows. To use a command script to uninstall the Agent for Windows 1 Map a drive letter to the Agents directory on a Backup Exec server. By default, the Agents directory is located at the following path Program FilesSymantecBackup ExecAgents 2 Do one of the following: In the RAWS32 directory, double-click Uninstallaaofo. To uninstall the Agent for Windows from a 32-bit computer In the RAWSX64 directory, double-click Uninstallaaofox64. To uninstall the Agent for Windows from a 64-bit computer 3 Restart the remote computer. See “Using a command script to install the Agent for Windows” on page 87. Installing the Remote Administrator The Remote Administrator lets you administer the Backup Exec server from a remote Windows server or workstation. To support the Remote Administrator, the Backup Exec system services must be running on the Backup Exec server that you want to administer. 88Installation Installing the Remote Administrator
- 89. Note: Backup Exec does not support the Remote Administrator on 32-bit operating systems. You cannot use the Remote Administrator to administer the servers that have different versions of Backup Exec installed. However, you can use side-by-side installations of the Remote Administrator to manage different versions of Backup Exec. To install the Remote Administrator 1 From the installation media browser, click Install Products. 2 Click Backup Exec. 3 On the Welcome panel, select I accept the terms of the license agreement, and then click Next 4 On the Installation Type panel, select Custom installation, and then click Next. 5 Check Local Installation, and then click Install Remote Administration Console only. 6 Click Next. 7 On the Destination panel, do the following: ■ Review the disk space requirements for the installation. ■ To change the location where the files are installed, click Change to select another directory for the installation. 8 Click Next. 9 Review the Backup Exec installation summary, and then click Install. 10 Click Next, and then click Finish to exit the wizard. See “Running the Remote Administrator” on page 91. Installing the Remote Administrator using the command line You can use silent mode installation to install the Remote Administrator. Options for the Remote Administrator are specified with the use of additional command switches. 89Installation Installing the Remote Administrator
- 90. Note: Backup Exec does not support the Remote Administrator on 32-bit operating systems. You cannot use the Remote Administrator to administer the servers that have different versions of Backup Exec installed. However, you can use side-by-side installations of the Remote Administrator to manage different versions of Backup Exec. To install the Remote Administrator using the command line 1 Open a Windows command prompt. 2 Change to the drive containing the Backup Exec installation media. 3 Change to the following directory: bewinntinstallbex64 4 Type setup /RA: and the appropriate switches. For example: setup /RA: /S: The command line switches used for silent mode installation of the Remote Administrator are described in the following table. Remember the following general rules for using these switches: ■ Substitute values appropriate for your environment for values in italics; for example, substitute your password for password. ■ Enclose the value in quotation marks if it contains spaces, such as "Program FilesSymantecBackup Exec". Table 2-10 Command line switches for Remote Administrator silent mode installation DescriptionAdditional SwitchesSwitch Installs Remote Administrator using the options that are specified with the additional switches. /RA: 90Installation Installing the Remote Administrator
- 91. Table 2-10 Command line switches for Remote Administrator silent mode installation (continued) DescriptionAdditional SwitchesSwitch Specifies the local path where Remote Administrator will be installed. Otherwise, the default path Program FilesSymantecBackup Exec is used. /DEST:"drive:path" Installs the online documentation. /DOCS: Lets you select all install options without actually installing the Backup Exec software. This option can be used with the /CPF: switch. /NOINSTALL: Creates a file containing all of the installation parameters provided. Note that the file is not encrypted, which exposes parameters such as the password. /CPF:"pathfilename.cpf" Provides help on all command-line operations, usage, and special switches. -? See “Installing Backup Exec using the command line (silent mode)” on page 94. Running the Remote Administrator The Remote Administrator lets you administer the Backup Exec server from a remote Windows server or workstation. To support the Remote Administrator, the Backup Exec server requires that the Backup Exec system services must be running. 91Installation Installing the Remote Administrator
- 92. You may be prompted for a user name and password to browse some network shares even if you are logged into the Remote Administrator computer under an account that is valid for those shares. Provide a domain-qualified user name and password when prompted (for example, domain1howard). For workgroup accounts, when logging in between different workgroups, you can provide only a user ID when prompted, and leave the workgroup line blank. Note: Backup Exec does not support the Remote Administrator on 32-bit operating systems. You cannot use the Remote Administrator to administer the servers that have different versions of Backup Exec installed. However, you can use side-by-side installations of the Remote Administrator to manage different versions of Backup Exec. See “Installing the Remote Administrator ” on page 88. To run the Remote Administrator 1 Click Start. 2 Point to Programs, and then click Symantec Backup Exec. If you are connecting to a Remote Administration Console from a Backup Exec server, click the Backup Exec button, and then select Connect to Backup Exec Server. 92Installation Installing the Remote Administrator
- 93. 3 Select the appropriate options. Select this option to access the Backup Exec Services Manager to stop and start services or to set the logon credentials that are used to run the services. Manage services Enter the name of the Backup Exec server. You can select the name from the list or type the name of the server if you are running the Remote Administrator from a Backup Exec server. Each server in the domain that has Backup Exec installed automatically appears in the list box. Server name Enter an administrator user name for the server to which you want to connect. Enter the user name using the DomainUsername format. You cannot log on to the Remote Administration Console with a user name that has a blank password on Windows Server 2003/2008 and Vista computers. You must configure Windows to allow blank passwords. Otherwise, the error message "Logon failure: user account restriction" appears. For more information, see your Windows documentation. User name Enter the password for the user.Password Enter the domain to which the user belongs. Enter the name of the domain that was used in the User name option. Domain The status of the local services appears at the bottom of this dialog box. If you try to connect to a server and the connection fails, this dialog box displays the services status for the server you attempted to connect to. 4 Click OK. 93Installation Installing the Remote Administrator
- 94. Installing Backup Exec using the command line (silent mode) Installing Backup Exec using the command line is referred to as silent mode installation. This method of installation uses the setup.exe program on the Backup Exec installation media, a series of command switches, and the /S: switch. Requirements for Command Line Installation include the following: ■ Backup Exec installation media. ■ Administrator privileges on the computer where you want to install, configure, or uninstall Backup Exec. The installation process creates an installation log named BKUPINST15.htm on the computer where Backup Exec is installed. See “About the installation log” on page 104. To install Backup Exec using the command line (silent mode) 1 Open a Windows command prompt. 2 Change to the drive containing the Backup Exec installation media. 3 Change to the following directory: bewinntinstallbex64 4 Type setup /TS: and the appropriate switches. For example: setup /TS: /USER:<user> /DOM:domain /PASS:password /SLF:C:pathslf.slf,C:pathslf2.slf /S: See “Command line switches for silent mode installation of Backup Exec” on page 94. If you use the command line switches without the /S: switch, the Backup Exec installation program launches with the command line parameters as defaults for the installation options. For example, if /S: had been left in the above example, the Backup Exec installation program launches with the user name, domain, password, and license appearing on the installation dialog boxes. 5 Press Enter. Command line switches for silent mode installation of Backup Exec The command line switches used for silent mode installation of Backup Exec are described in the following table. The following are general rules for using these switches: 94Installation Installing Backup Exec using the command line (silent mode)
- 95. ■ Substitute values appropriate for your environment for the values that are shown in italics. For example, substitute a user name for user. ■ Enclose the value in quotation marks if it contains spaces, such as "Operations Weekly Backup". See “Installing Backup Exec using the command line (silent mode)” on page 94. Table 2-11 Command line switches for silent mode installation of Backup Exec DescriptionAdditional SwitchesSwitch Installs Backup Exec using the options that are specified with the additional switches. The /USER:user, /DOM:dm, /PASS:pw switches are required. /TS: Required. Specifies an existing user, domain, and password for the Backup Exec system service account. Silent mode installation does not create a user. Note: When using /PASS:, if a quote is needed as part of the password, specify it as ". For example, if the password is pass"word, type it as /PASS:pass"word. If the characters " are used as part of the password, you must precede each character with a . For example, if the password is pass"word, type it as /PASS:pass"word. /USER:user /DOM:dm /PASS:pw Specifies the local path where Backup Exec is installed. Otherwise, the default path Program FilesSymantecBackup Exec is used. /DEST:drive:path Installs the online documentation./DOCS: 95Installation Installing Backup Exec using the command line (silent mode)
- 96. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Installs the Backup Exec language resource files. Specify one or more of the following switches with the Backup Exec language switch to indicate which language files you want to install: ■ EN installs English. ■ DE installs German. ■ ES installs Spanish. ■ FR installs French. ■ IT installs Italian. ■ PT installs Portuguese. ■ RU installs Russian. ■ JP installs Japanese. ■ KO installs Korean. ■ ZH installs Simplified Chinese. ■ CH installs Traditional Chinese. The following example shows how the /BELANG switch can be used to install English, German, and Spanish: /BELANG:"EN DE ES" /BELANG:language Lets you select all install options without installing the Backup Exec software. This option can be used with the /CPF: switch. /NOINSTALL: Creates a file containing all of the installation parameters provided. Note that the file is not encrypted, which exposes parameters. /CPF:pathfilename.cpf 96Installation Installing Backup Exec using the command line (silent mode)
- 97. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Specifies one or more licenses to use for installing Backup Exec and additional options. Licenses are not required to install the Remote Administrator. You may specify up to 99 licenses. If none are specified, then a trial copy of Backup Exec is installed. The following examples show how the /SLF switch can be used: /SLF:C:pathslf1.slf /SLF:C:pathslf1.slf,C:path slf2.slf, C:path slf3.slf Note: If you install a license for an option or agent, you must also type a switch that specifies the option or agent. The switches that specify an option or agent are included in this table. /SLF:slf file Disables the option to send Backup Exec usage data to Symantec over the web. /DISABLETELEMETRY: Automatically initiates a restart of the computer during a silent install or uninstall. /BOOT: 97Installation Installing Backup Exec using the command line (silent mode)
- 98. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Note: None of the additional /TD switches are supported for Windows Server 2012 or later. /TD:NEW installs tape drivers only for the drives that do not have drivers loaded. /TD:ALL installs tape drivers for all drives. /TD:NONE does not install tape device drivers. Note: To install the Symantec tape drivers in Windows 2008 R2, the Windows driver signing policy must be set to Ignore. However, for Windows 2003/2008 the driver installation fails when the signing policy is set to Ignore. You can install the drivers using Symantec Device Driver Installer (tapeinst.exe) instead. See your Microsoft Windows documentation for more information about the signing policy. /TD:NEW, ALL, or NONE Installs the Backup Exec Database to the specified SQL server. /DBSERVER:serverinstance Specifies if a copy of your current Backup Exec Database should be stored during an upgrade of Backup Exec. /BACKUPDATA: 98Installation Installing Backup Exec using the command line (silent mode)
- 99. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Specifies the location to store the Backup Exec Database during an upgrade of Backup Exec. The folder you select must be empty. A copy of your current Backup Exec Database is placed in the location that you specify and is used if the upgrade fails. Note: This switch is ignored if the corresponding /BACKUPDATA: switch is not specified. /BACKUPDIR: Installs the default instance of SQL Express in the specified folder. /DBINSTPATH: SQL Express destination folder Skips the installation of Symantec LiveUpdate. /NOUPDATE: Installs the Agent for Windows and enables publishing. /ADVRT:Backup Exec server name Installs the Agent for Windows without publishing it. /DISADVRT: Specifies the location of the language-specific install package for Microsoft SQL Server 2008 R2 Express Edition with SP2. /SQLXSETUP:SQL Express Install Package Installs the Library Expansion Option. This option is not supported for Windows Server 2012 or later. /LOADER: Installs the QuickStart Edition. You must enter a QuickStart license to install this edition. /QUICKSTART: Installs the standard Backup Exec Edition. You must enter a Backup Exec license to install this edition. /BEWS: Installs the Not For Resale Edition. You must enter a Not For Resale license to install this edition. /NFR: 99Installation Installing Backup Exec using the command line (silent mode)
- 100. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Installs the Trial Edition./TRIAL: Installs the Small Business Edition. You must enter a Small Business Edition license to install this edition. /SMALLBUSINESS: Installs the Essential Protection Edition. You must enter an Essential Protection license to install this edition. /ESSENTIAL: Installs the Total Protection Edition. You must enter a Total Protection license to install this edition. /TOTAL: Installs the V-Ray Edition. You must enter a V-Ray license to install this edition. /VRAY: Installs the Capacity Edition. You must enter a Capacity license to install this edition. /CAPACITY: Installs the Capacity Edition Lite. You must enter a Capacity Edition Lite license to install this edition. /CAPACITYLITE: Installs the Agent for Applications and Databases. /APPLICATIONS: Installs the Agent for VMware and Hyper-V. /VIRT: Installs the Enterprise Server Option. You must use one or both of the following switches with the Enterprise Server Option switch to indicate which options you want to install. ■ /CASO: Installs the Central Admin Server Option. ■ /ADBO: Installs the Advanced Disk-based Backup Option. /ENTSERVER: 100Installation Installing Backup Exec using the command line (silent mode)
- 101. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Installs the Advanced Disk-based Backup Option. You must use /ENTSERVER: with this switch. /ADBO: Installs the Central Admin Server Option. You must use /ENTSERVER: with this switch. /CASO: Creates a managed Backup Exec server for use with the Central Admin Server Option. /MMS:CAS server name /CASOPVLLOCAL:1 indicates that device and media data is stored locally on the managed server. Use this switch with /MMS:. /CASOPVLLOCAL:0 indicates that device and media data is stored on the administration server. Use this switch with /MMS:. /CASOPVLLOCAL: <1 or 0> Enables unrestricted access to catalogs and backup sets for restore. This switch is used with the /MMS:<CAS server name> switch and it replaces the /SSO:<primary server name> switch. /ACCESSCATALOGSANDRESTORE: Installs the Agent for Windows./NTA: Installs the Agent for Mac./MAC: Installs the NDMP Option./NDMP: Installs the Agent for Linux./RALS: Installs the Storage Provisioning Option./STORPROV: Installs the basic Storage Provisioning Option. /FIXEDSPO: Installs the Deduplication Option./DEDUPE: 101Installation Installing Backup Exec using the command line (silent mode)
- 102. Table 2-11 Command line switches for silent mode installation of Backup Exec (continued) DescriptionAdditional SwitchesSwitch Installs the Exchange Mailbox Archiving Option. This switch is used with the /APPLICATIONS: switch. /EXCHARCH: Installs the File System Archiving Option. /NTFS: Installs the VTL Unlimited Drive Option./VTL: Installs the Remote Media Agent for Linux. /RMAL: Installs the Copy Server Configuration option. /COPYCONFIG: Specifies a fully-qualified DNS alias for the Exchange Mailbox Archiving Option. /BEAODNSALIAS: Specifies the location of the index files for the Exchange Mailbox Archiving Option. The default location is %ProgramFiles%SymantecBackup ExecArchiveIndex. /BEAOINDEXPATH: Specifies the location of the temporary cache for the Exchange Mailbox Archiving Option. The default location is %ProgramFiles%SymantecBackup ExecAOCache. /BEAOCACHEPATH: Specifies the maximum size of the temporary cache location for the Exchange Mailbox Archiving Option. The default size is 10 GB. /BEAOCACHESIZE: Provides help on all command-line operations, usage, and special switches. -? 102Installation Installing Backup Exec using the command line (silent mode)
- 103. Creating and using installation parameter files If you use the command line switches without the /S: switch, the Backup Exec installation program launches with the command line parameters as defaults for the installation options. For example, suppose you type: SETUP /TS: /USER:user /DOM:domain /PASS:password /SLF:"C:path nameslf1.slf" The Backup Exec installation program is launched. The screens that let you enter the logon credentials and the license will appear with the information you provided on the command line. You can also use the /CPF: command to create a parameter file that contains all of the command line options you provided. This parameter file can then be used to provide the options for installing either Backup Exec or the Remote Administrator. Note that the file is not encrypted, which exposes parameters such as the password. To create installation parameter files 1 Open a Windows command prompt. 2 Change to the drive containing the Backup Exec installation media. 3 Change to the following directory: BEWINNTINSTALLBex64 4 Type setup /TS: and the appropriate switches, including /CPF: and the full path name of the parameter file. For example, type: setup /TS: /USER:user /DOM:domain /PASS:password /SLF:"C:path nameslf1.slf" /CPF:"A:file name" /S: Backup Exec will be installed on your server and a parameter file containing the user name, domain, password, and license will be saved to a removable device. You can use this parameter file to install to another computer. To use installation parameter files 1 Open a Windows command prompt. 2 Change to the drive containing the Backup Exec installation media. 3 Change to the following directory: BEWINNTINSTALLBex64 4 Type:SETUP /PARAMS:"A:file name" /S: 5 If you want to overwrite a parameter, specify the new parameter. For example, to change the password, type:SETUP /PARAMS:"A:file name" /PASS:new password /S: 103Installation Installing Backup Exec using the command line (silent mode)
- 104. Installing a trial version of Backup Exec agents and options You can install a trial version of most Backup Exec agents and options at any time after the core product is licensed. Each agent and each option has its own independent trial period. When a trial period is about to expire, Backup Exec warns you with an alert. You can view a list of agents and options that are available for a trial period. You can also view the amount of time that is left in each individual trial period. See “Viewing license information” on page 109. To install a trial version of Backup Exec agents and options 1 Click the Backup Exec button, select Installation and Licensing, and then select Install Options and Licenses on this Backup Exec Server. 2 Click Next. Do not enter serial numbers or a Symantec License file. 3 Click Next. 4 Select the agents or options that you want to evaluate. 5 Click Next. 6 If you are prompted, enter information or choose settings for the additional options that you want to install. Click Next after each selection. 7 Read the Backup Exec installation review, and then click Install. The Backup Exec services are stopped while the additional options are installed. If any active jobs are in progress, you are prompted to stop them, or to wait for the jobs to finish. When the installation is complete, the services restart. 8 Click Finish. About the installation log Backup Exec creates an installation log file, named BKUPINST15.htm, when you install Backup Exec and when you install patches. This log file can help you troubleshoot installation problems. The log file provides links to tech notes for the most common errors. If you install the Agent for Windows, a log file called RAWSinst15.htm is also created. 104Installation Installing a trial version of Backup Exec agents and options
- 105. In addition, the text in the log file uses the following colors so you can identify warnings and errors: Table 2-12 Installation log colors IndicatesThis color Normal operationsBlack Warning messagesOrange Error messagesRed The BKUPINST15.htm file is located in the following locations: ■ For Windows 2003: %allusersprofile%Application DataSymantecBackup ExecLogs ■ For Windows 2008 and later: %ProgramData%SymantecBackup ExecLogs Note: The ProgramData folder is a hidden folder. If you do not see the ProgramData folder, refer to the Microsoft Windows documentation for instructions on how to display hidden folders. Viewing the Installation Summary Report Backup Exec creates an Installation Summary Report that includes the configuration settings that you selected during the installation process. The Installation Summary Report is updated with the product name and serial numbers when you install additional agents or options. It is also updated when you remove agents or options from Backup Exec. The Installation Summary Report is stored in the following locations: ■ For Windows 2003: %allusersprofile%Application DataSymantecBackup ExecLogsInstallSummary<computer name>.htm ■ For Windows 2008 and later: %programdata%SymantecBackup ExecLogsInstallSummary<computer name>.htm The Installation Summary Report is available for viewing from the Backup Exec Administration Console or the Home tab at any time after the installation has completed. To view the Installation Summary Report ◆ Do one of the following: 105Installation Viewing the Installation Summary Report
- 106. Click the Backup Exec button, select Installation and Licensing, and then select Installation Summary Report. To view the Installation Summary Report from the Administration Console On the Home tab, in the Installation and Upgrades group, click Installation Summary Report. To view the Installation Summary Report from the Home tab Repairing Backup Exec If you have missing or corrupted Backup Exec files or registry keys on the local Backup Exec server, run the Repair option. The program stops all Backup Exec services, reinstalls corrupted files and registry keys, reinstalls tape devices (standalone drives and libraries), and restarts the services. The database is not reinstalled. Any changes that are made to Backup Exec program files and registry keys are reset to the original settings. To repair Backup Exec 1 Close the Backup Exec application. 2 From the Windows Control Panel, select the option to uninstall a program. 3 Select Symantec Backup Exec 15, and then click Change. 4 Select Local installation and Repair, and then click Next. Ensure that the Remote installation option is not selected. 5 If you are prompted to enter credentials for the Backup Exec service account, type the correct credentials, and then click Next. 6 Select Install. You may be prompted to insert the installation media. 7 Click Finish. Updating Backup Exec with LiveUpdate Symantec LiveUpdate, which provides updates of Backup Exec, is installed automatically with Backup Exec. Backup Exec installs the latest version of LiveUpdate. If a previous version of LiveUpdate is detected on the computer, Backup Exec upgrades it. LiveUpdate can be run manually or can be configured to run automatically. If you enable the automatic update option, you can configure LiveUpdate to poll the main 106Installation Repairing Backup Exec
- 107. Symantec web server on a scheduled interval. By default, LiveUpdate checks for updates every Sunday night at 10pm. If there is an update, LiveUpdate notifies you with an alert. The automatic update option only searches for Backup Exec updates. It does not show updates for other Symantec products that use LiveUpdate. Likewise, when LiveUpdate is scheduled to automatically update other Symantec products, it does not search for Backup Exec updates. In addition to scheduling LiveUpdate, you can also run it manually at any time. You can access LiveUpdate from Backup Exec, but you cannot access it from the Windows Start menu. If LiveUpdate installs any files, the BKUPINST15.htm installation log file is updated with information about those files. Note: During the installation and update process, the Backup Exec services are stopped and started one time during a LiveUpdate session, regardless of the number of updates that are being installed. All selected patches are installed in order. When LiveUpdate installs updates on the Backup Exec server, it also determines if computers on which the Agent for Windows is installed have the latest updates. If you do not have the latest updates you receive an alert to install the updates. You can use the LiveUpdate Administrator Utility with LiveUpdate. The LiveUpdate Administrator Utility allows an administrator to modify LiveUpdate so that network users can download program and virus definition updates from an internal server rather than going to the Symantec LiveUpdate server over the Internet. Scheduling automatic Backup Exec updates using LiveUpdate You can schedule LiveUpdate to check for updates as follows: ■ Every day at a specific time ■ Every week on a specific day of the week and at a specific time ■ Every month on a specific day of the month and at a specific time When you schedule automatic updates through Backup Exec, the settings apply only to updates for Backup Exec. Changes that you make to the LiveUpdate schedule for Backup Exec do not affect the schedule for any other software applications that use LiveUpdate. At the scheduled time, LiveUpdate automatically connects to the appropriate website, and then determines if your files need to be updated. Depending on the options that you select, Backup Exec either downloads and installs the files in the proper location or sends an alert to notify you that updates are available. Backup Exec sends the following LiveUpdate alerts: 107Installation Updating Backup Exec with LiveUpdate
- 108. Table 2-13 LiveUpdate alerts WhenBackup Exec sends this alert An update is installed successfully.LiveUpdate Informational Alert An update is installed successfully. However, you must restart the computer. LiveUpdate Warning Alert An update fails to install.LiveUpdate Error Alert To schedule automatic updates using LiveUpdate 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings. 2 In the left pane, select LiveUpdate. 3 Select Check for updates automatically according to a schedule. 4 Select the schedule to check for updates. 5 Do one of the following: ■ Select Download and install all available updates automatically if you want the updates to be installed automatically. ■ Select Send an alert when updates are available; do not download or install updates if you do not want the updates to be installed automatically, but do want to receive notification that updates are available. 6 Click OK. Running LiveUpdate manually You can either set a schedule for LiveUpdate or run LiveUpdate manually at any time to check for updates. You can configure LiveUpdate to run in either Interactive mode or Express mode. Interactive mode gives you the flexibility to choose which updates you want to install. Express mode automatically installs all of the Backup Exec updates. For information about how to change the LiveUpdate mode, see the LiveUpdate documentation. Note: By default, LiveUpdate is configured for Interactive mode. If you change it to Express mode you must cancel the LiveUpdate session and restart it before the change takes place. 108Installation Updating Backup Exec with LiveUpdate
- 109. To run LiveUpdate manually 1 Click the Backup Exec button, select Installation and Licensing, and then select LiveUpdate. 2 Do one of the following: Click Start.If LiveUpdate is set for Express mode Click Next.If LiveUpdate is set for Interactive mode See “Viewing installed updates” on page 109. See “Installing updates to the Agent for Windows on remote computers” on page 79. Viewing installed updates You can view the service packs that are installed on a Backup Exec server. You must be logged on with administrator privileges. If a service pack is installed before another service pack, that service pack no longer displays as installed since the later service pack contains the earlier service pack A hot fix that is offered after the service pack is released is displayed with the previous service pack. To view installed updates ◆ Click the Backup Exec button, select Installation and Licensing, and then select Installed Updates. Viewing license information You can view information about the Backup Exec options that are licensed and installed on a Backup Exec server. You can also view a list of agents and options that are available for a trial, as well as how much time is left in each individual trial period. To view license information ◆ Click the Backup Exec button, select Installation and Licensing, and then select License Information. 109Installation Viewing installed updates
- 110. Backup Exec maintenance contract information After you purchase maintenance contracts for your Backup Exec products, Symantec automatically updates the Symantec Licensing Portal website with your maintenance contract information. Maintenance contract information includes the contract serial number and the contract expiration date. To retrieve the contract expiration dates, you enter your maintenance contract serial numbers in the installation wizard. The installation wizard connects to the Symantec Web service, at which point you may be prompted to enter customer and technical contact information. The installation wizard then retrieves the maintenance contract information for each contract that you have purchased. Backup Exec then uses the contract expiration information to automatically set Backup Exec alerts that remind you to renew the maintenance contracts before they expire. Reminder alerts are set at 30-day, 60-day, and 90-day intervals, based on the expiration date of the maintenance contract. If you do not renew the maintenance contract, an alert is sent when the maintenance contract expires. All Backup Exec products and maintenance contracts have Symantec serial numbers. The serial numbers appear on the printed certificate that you receive with your order. To determine the correct serial numbers to enter in the installation wizard, look for the Maintenance/Subscription columns on your certificate. Each maintenance contract specifies a start date and an end date; these dates appear in the Maintenance/Subscription columns. To view Backup Exec maintenance contract information ◆ Click the Backup Exec button, select Installation and Licensing, and then select Maintenance Contract Information. See “Updating expired maintenance contracts” on page 110. Updating expired maintenance contracts When your maintenance contracts expire, follow these steps to update them. Note: You cannot use the Remote Administrator on a remote Windows server or workstation to update maintenance contracts. Table 2-14 How to update expired maintenance contracts Additional informationStep Access the Symantec Licensing Portal website to purchase new contracts. Purchase new maintenance contracts. 110Installation Backup Exec maintenance contract information
- 111. Table 2-14 How to update expired maintenance contracts (continued) Additional informationStep The new serial numbers should arrive by email within two to five business days of the purchase date. Wait for your new serial numbers to arrive. Use the option Install options and licenses on this Backup Exec server on the Installation and Licensing menu, which is accessed from the Backup Exec button. Launch the installation wizard from the Backup Exec Administration Console. After you select the expired serial numbers from the list, use the Remove option. Use the installation wizard to add the new serial numbers, and then remove the expired serial numbers. See “Backup Exec maintenance contract information” on page 110. Managing maintenance contract customer numbers Backup Exec provides a place where you can store all of your maintenance contract customer numbers. You need to provide these numbers when you call technical support. To manage maintenance contract customer numbers 1 Click the Backup Exec button, select Installation and Licensing, and then select Maintenance Contract Customer Numbers. 2 Do one of the following: ■ To add a new customer number, click New, and then enter your customer number and any notes for this number. ■ To remove a customer number, select the number from the list, and then click Delete. 3 Click Close. About upgrading from previous versions of Backup Exec to Backup Exec 15 You can use the Backup Exec installation media to upgrade from Backup Exec version 12.5 or later to the current version. You do not need to uninstall the previous version of Backup Exec before upgrading; the current version is installed over the 111Installation About upgrading from previous versions of Backup Exec to Backup Exec 15
- 112. previous version. Separate installations of different versions of Backup Exec cannot exist on the same computer. Note: You cannot upgrade to Backup Exec 15 from earlier versions of Backup Exec that run on a 32-bit operating system because installation of Backup Exec on 32-bit operating systems is no longer supported. Backup Exec 15 supports the Backup Exec server installation on 64-bit operating systems only. However, you can install the Agent for Windows on 32-bit operating systems. Most settings, all catalogs, and all data directories from previous versions of Backup Exec are kept, unless you choose to remove them. This version of Backup Exec can read and restore data from any previous version of Backup Exec or Backup Exec for NetWare, except where Symantec has made end-of-life decisions. Note: Upgrading to the current version of Backup Exec from a version before 12.5 requires a multi-step process. For example, to upgrade from Backup Exec 11.x to Backup Exec 15, you must first upgrade to a version such as Backup Exec 12.5 or Backup Exec 2010 before you can upgrade to Backup Exec 15. When you upgrade from previous versions, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version and some of your jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report that you must review and acknowledge before Backup Exec continues the upgrade process. In this report, you can see how your jobs were migrated. Customized descriptions for previous versions of Backup Exec Managed Media Servers and Remote Agents are not migrated to Backup Exec 2012 or later. If you want to add a customized description for a server after you upgrade, you can type the description in the server's Properties tab. See “Using the Migration Report to determine how existing jobs changed after an upgrade to Backup Exec 15” on page 115. Backup Exec 15 provides backward compatibility as follows: ■ Backup Exec 15 can communicate with Backup Exec 12.5 Remote Agent for Windows Systems and later. ■ Backup Exec supports side-by-side installations of the Remote Administration Console for Backup Exec 2010 and later. For example, you can have a Remote Administration Console for Backup Exec 2012 and a Remote Administration Console for Backup Exec 15. 112Installation About upgrading from previous versions of Backup Exec to Backup Exec 15
- 113. ■ Backup Exec 15 Central Admin Server Option server can communicate with Backup Exec 2010 R3 (with the most recent service packs) for the purpose of rolling upgrades. A Remote Administration Console that uses a previous version of Backup Exec cannot be used with a Backup Exec server on which the current version is installed. For example, a Backup Exec 2010 Remote Administration Console cannot manage a Backup Exec 15 Backup Exec server. Before you upgrade Backup Exec, do the following: ■ Delete the job histories and the catalogs that you no longer need to shorten the upgrade window. ■ Run a database maintenance job. ■ Verify that all available updates are installed for your current version of Backup Exec. ■ Locate your license information and verify that your licenses are current. You must enter license information for Backup Exec 15 when you upgrade. You cannot change the configuration of your Backup Exec servers or the database location during the upgrade process. For example, you cannot change an administration server to a managed server. If you want to change the configuration of your Backup Exec servers, do it either before or after you upgrade to the current version. If you want to change the database location after the upgrade, use BEUtility. Note: If you upgrade from a previous version of Backup Exec that uses a non-English version of Windows, you must download the SQL Server 2008 R2 Express with SP2 setup file for that language from the Microsoft website. See “Installing Backup Exec by using the Installation Wizard” on page 52. Upgrade checklist for Backup Exec 2010 and earlier Before you upgrade from a previous version of Backup Exec to the current version, do the following: ■ Ensure that your backups are up to date. Symantec recommends that you always run full backups before and after you upgrade the applications or operating systems on any backup sources. ■ Review the overwrite protection periods of the media sets that are on disk storage. Extend the overwrite protection periods of the media sets that you want to keep longer. Changes have been made to the way that Advanced Device and Media Management (ADAMM) handles the overwrite protection for the media sets that 113Installation About upgrading from previous versions of Backup Exec to Backup Exec 15
- 114. are on disk-based storage. Previous versions of Backup Exec let the media sets expire but did not delete them from the disk, which can cause your disk storage to become full and jobs to fail. Backup Exec 15 now proactively frees disk space through a process that reclaims the disk space for use by new backup sets. Backup Exec 15 uses the disk reclamation process called data lifecycle management (DLM) instead of ADAMM to manage the data retention of backup sets on disk-based storage. DLM automatically deletes the expired backup sets on disk-based storage and reclaims the disk space for use by new backup sets. DLM deletes backup sets after the amount of time that you specify when you create a backup job expires. For the jobs that you upgrade, DLM deletes the backup sets for which the overwrite protection period is expired. If you want to review or change the overwrite protection periods of your expired backup sets after you upgrade, you can temporarily disable DLM, make any changes to the data retention of backup sets, and then re-enable DLM. For more information, see the following URL: http://entsupport.symantec.com/umi/V-269-45 ■ Disable your antivirus software. ■ Check the Backup Exec Software Compatibility List (SCL) and the Hardware Compatibility List (HCL) to verify that the applications that you want to back up and your storage devices are supported with this version of Backup Exec. You can find the SCL and HCL at the following URLs: http:entsupport.symantec.com/umi/V-269-1 http:entsupport.symantec.com/umi/V-269-2 ■ Download all available upgrades and hot fixes for the version of Backup Exec that you want to install. ■ Plan to perform the upgrade when system downtime won't affect users. ■ Ensure that your serial numbers or Symantec License Files are available. You must enter new Backup Exec 15 license information during the upgrade. For details on updated licensing, see the Backup Exec Licensing Guide at the following URL: http://entsupport.symantec.com/umi/V-269-50 ■ Review the following topics in the Backup Exec 15 Administrator's Guide: ■ System requirements for Backup Exec See “System requirements for Backup Exec” on page 49. ■ How data lifecycle management (DLM) deletes expired backup sets on disk-based storage See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. 114Installation About upgrading from previous versions of Backup Exec to Backup Exec 15
- 115. ■ About upgrading from previous versions of Backup Exec See “About upgrading from previous versions of Backup Exec to Backup Exec 15” on page 111. ■ Review the document Best practices for installing Backup Exec on the Backup Exec knowledge base. ■ Review the document What's Different in Backup Exec 2014 and Backup Exec 15 to learn about product-level differences at the following URL: http://www.symantec.com/docs/DOC5216 Using the Migration Report to determine how existing jobs changed after an upgrade to Backup Exec 15 When you upgrade Backup Exec 15 from a previous version other than Backup Exec 2012, your existing definitions, configurations, and jobs are converted automatically to the current version. When the jobs are migrated, some of the jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report for you to view and acknowledge. In this report, you can see how your jobs were migrated. The information that is included in the Migration Report cannot be recreated after the upgrade completes. Symantec recommends that you review the Migration Report thoroughly to determine how your existing jobs have changed and how you may need to adjust your jobs manually. The Migration Report is available for viewing from the Backup Exec Administration Console or the Home tab at any time after the migration completes. The Migration Report is stored in the following path: Program FilesSymantecBackup ExecDataMigrationReportFilesData-Migration-Report.html. Note: To view the Migration Report, JavaScript must be enabled in your web browser. If the server on which you installed Backup Exec does not have a browser with JavaScript enabled, you can copy the Migration Report to another server that has JavaScript enabled. 115Installation About upgrading from previous versions of Backup Exec to Backup Exec 15
- 116. To view the Migration Report ◆ Do one of the following: Click the Backup Exec button, select Installation and Licensing, and then select Migration Report. To view the Migration Report from the Administration Console On the Home tab, in the Installation and Upgrades group, click Migration Report. To view the Migration Report from the Home tab See “Configuring the Home tab” on page 126. Post-installation tasks For best results, do the following after installing Backup Exec: ■ Create disk storage so that Backup Exec can automatically manage the lifecycle of your backup data. See “Configuring disk storage” on page 305. ■ Make sure that your storage devices are connected and configured properly. ■ Decide what types of storage devices you want to use for your backup jobs. You can configure storage devices when you prepare your Backup Exec environment. ■ Understand how Backup Exec provides overwrite protection for your tape media. See “Media overwrite protection levels for tape media” on page 380. ■ Understand the default media set for tape media and its four-week overwrite protection period. See “Default media sets” on page 367. ■ Understand Data Lifecycle Management. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. ■ Learn about creating new media sets with different retention periods. See “Creating media sets for tapes” on page 374. ■ Decide which credentials you want your Backup Exec logon account to use when browsing and making backup selections. You can use an existing Backup Exec logon account, or create a new one. See “Backup Exec logon accounts” on page 603. ■ Configure a secure connection to the Backup Exec Database 116Installation Post-installation tasks
- 117. See “Configuring encryption for the connection to the Backup Exec Database” on page 558. Uninstalling Backup Exec Use Microsoft’s Add or Remove Programs option to remove Backup Exec from a computer. For additional information on Add or Remove Programs, refer to your Microsoft documentation. Uninstalling Backup Exec also removes Symantec tape class drivers. If you reinstall Backup Exec and want to use Symantec tape class drivers, you must reinstall them. To uninstall Backup Exec 1 Close Backup Exec. 2 From the Windows Control Panel, select the option to uninstall a program. 3 Select Symantec Backup Exec 15, and then click Uninstall. 4 When you are prompted to confirm that you want to uninstall Backup Exec from your computer, click Yes. 5 Select whether you want to remove only the Backup Exec program files or Backup Exec and all of its associated files. 6 Click Next. If the uninstall program fails, click View Installation Log File for additional information. 7 If you are prompted, restart the computer. See “Uninstalling Backup Exec options from the local Backup Exec server” on page 118. Uninstalling Backup Exec using the command line If Backup Exec is already installed, you can use the setup.exe program to uninstall Backup Exec program files and Backup Exec data. To uninstall Backup Exec using the command line 1 Open a Windows command prompt. 2 Change to the drive containing the Backup Exec installation media. 117Installation Uninstalling Backup Exec
- 118. 3 Change to the following directory: bewinntinstallbex64 4 To remove the Backup Exec program files but keep all of the Backup Exec data, type: SETUP /UNINSTALL: To remove the Backup Exec program files and the Backup Exec data, type: SETUP /REMOVEALL: See “Installing Backup Exec using the command line (silent mode)” on page 94. Uninstalling Backup Exec options from the local Backup Exec server The Installation Wizard removes Backup Exec options from the local Backup Exec server. All corresponding files, registry keys, and configurations are removed. Note: Symantec license files remain on the server after options are uninstalled. Do not delete the Symantec license files while Backup Exec is installed. Deleting the Symantec license files causes the trial version to go into effect. To uninstall Backup Exec options from the local Backup Exec server 1 Click the Backup Exec button, select Installation and Licensing, and then select Install Options and licenses on this Backup Exec Server. 2 On the Add Licenses panel, click Next. 3 On the Review Licenses panel, uncheck the check boxes for the licenses that want to remove. 4 Click Next. 5 On the Configure Options panel, verify that the option you want to remove is not checked, and then click Next. 6 Uncheck the check box for the language that you want to remove. 7 Click Next. 8 If you are prompted to enter credentials for the Backup Exec service account, type the correct credentials, and then click Next. 118Installation Uninstalling Backup Exec options from the local Backup Exec server
- 119. 9 Read the installation summary, and then click Install to start the process. 10 When the Installation Wizard has completed, click Finish. See “Uninstalling Backup Exec” on page 117. 119Installation Uninstalling Backup Exec options from the local Backup Exec server
- 120. Getting Started This chapter includes the following topics: ■ About the Backup Exec Administration Console ■ Displaying the version information for Backup Exec ■ How to sort, filter, and copy information on the Backup Exec Administration Console ■ Customizing views on the Backup Exec Administration Console ■ Configuring the Home tab ■ Configuring the Symantec RSS Reader ■ Creating a disaster preparation plan (DPP) ■ Getting started with backups About the Backup Exec Administration Console Use the Backup Exec Administration Console to run backups, restore data, monitor jobs, configure storage, and run reports. 3Chapter
- 121. Figure 3-1 Backup Exec Administration Console Tabs Backup Exec button Groups Columns Selection pane Details pane Status bar The administration console screen includes the following components: Table 3-1 Administration console components DescriptionItem The Backup Exec button displays on the upper left side of the administration console. To display the options in the Backup Exec button, click the Backup Exec button, select the menu name, and then select an option. You can launch Backup Exec operations by clicking options from a menu. Backup Exec button 121Getting Started About the Backup Exec Administration Console
- 122. Table 3-1 Administration console components (continued) DescriptionItem Tabs at the top of the screen let you navigate Backup Exec. You can access the following views from the navigation bar: ■ Home. Provides quick access to the Backup Exec information that you use frequently. Customize the Home view by adding or deleting items. ■ Backup and Restore. Create a backup or restore job. ■ Job Monitor. Monitor and manage backup, restore, installation, and storage operation jobs. ■ Storage. Configure storage, run storage operations, and manage media. ■ Reports. View, print, save, and schedule reports about the Backup Exec server, operations, and device and media usage, and create custom reports. View reports in Backup Exec in PDF or HTML format, and save and print reports in PDF, XML, HTML, Microsoft Excel (XLS), and comma-separated value (CSV) formats Tabs Groups display on the tabs in the administration console, and contain the commands that initiate actions such as creating a new backup job or configuring storage. The commands in the groups are dynamic, changing according to the selection. Some commands are unavailable until you select an item on the console screen or until you run a prerequisite task. Groups Customize columns by doing any of the following actions: ■ Drag and drop columns to change their location. ■ Right-click a column heading to select the columns to display or to sort and filter the column content. ■ Click the column heading to change the order of the column. For example, names of reports display in alphabetical order by default. To display report names in reverse alphabetical order, click the Name column heading on the Reports view. Columns Select items to work with, such as servers to back up or restore.Selection pane 122Getting Started About the Backup Exec Administration Console
- 123. Table 3-1 Administration console components (continued) DescriptionItem Additional details appear for the server that you select in the list of servers. The Details pane lists the resources for the selected server and the selection status, backup status, and logon account information for each resource. When you select a Hyper-V host or VMware host in the list of servers, the Details pane includes the following details: ■ The last 7 days of backup jobs ■ The date of the last backup ■ The date of the next scheduled backup You can also restore data and filter the list of guest virtual machines from this pane. Details pane The status bar appears on the bottom of the administration console and provides information about the Backup Exec server, jobs that are running or are scheduled, alerts, and services. Status bar Click F5 to refresh the user interface on the administration console.Refresh Displaying the version information for Backup Exec You can display information about the version of Backup Exec that is installed. To display the version information for Backup Exec 1 Click the Backup Exec button, select Help and Documentation, and then click About Backup Exec. 2 Click OK. How to sort, filter, and copy information on the Backup Exec Administration Console You can customize the information that displays on the Backup and Restore tab, the Job Monitor tab, and the Storage tab. You can do any or all of the following actions: ■ Choose a default configuration that Backup Exec provides, such as Servers with Active Jobs or Failed Jobs. ■ Specify a sort order for the columns that appear in the views. 123Getting Started Displaying the version information for Backup Exec
- 124. ■ Specify the values that you want to use to filter the information that Backup Exec displays. ■ Specify the columns that you want to appear and the order in which they should appear. ■ Create and save a configuration to use again. ■ Copy list items to the Clipboard and then copy them to any application that supports copy-and-paste. To sort or filter information on the Backup Exec Administration Console 1 Do one of the following: On the Backup and Restore tab, in the Views group, click Sort and Filter. To customize a view of the computers in the list of servers On the Storage tab, in the Views Group, click List, and then click Sort and Filter. To customize a view of the storage devices 2 Do any of the following: Click Configurations and select a configuration. To select a default configuration, such as Servers with Failed Backups, or to select a configuration that you created and saved previously Click Sort, choose the options as appropriate, and then click OK. To specify an ascending or descending sort order for the columns Click Filter, choose the options as appropriate, and then click OK. To specify one or more columns to filter for specific values Click Columns, choose the options as appropriate, and then click OK. To specify the columns that you want to display and the order in which they should appear Click Save, choose the options as appropriate, and then click OK. To create and save a configuration 124Getting Started How to sort, filter, and copy information on the Backup Exec Administration Console
- 125. To edit a configured view 1 Do one of the following: On the Backup and Restore tab, in the Views group, click Sort and Filter. To edit a configuration from the Backup and Restore tab On the Storage tab, in the Views group, click Sort and Filter. To edit a configuration from the Storage tab 2 Click Configurations. 3 Select the configuration that you want to edit, and then click the pencil icon. To delete a configured view 1 Do one of the following: On the Backup and Restore tab, in the Views group, click Sort and Filter. To delete a configuration from the Backup and Restore tab On the Storage tab, in the Views group, click Sort and Filter. To delete a configuration from the Storage tab 2 Click Configurations. 3 Select the configuration that you want to delete, and then click the delete icon. To copy information on the Backup Exec Administration Console 1 On any tab except the Home tab, right-click an item in the list view. 2 Click Copy. 3 Open any application that supports copy-and-paste, and then paste the information. Customizing views on the Backup Exec Administration Console You can customize how you view the information that displays on the Backup and Restore tab, the Job Monitor tab, and the Storage tab. 125Getting Started Customizing views on the Backup Exec Administration Console
- 126. Table 3-2 Views on the Backup Exec Administration Console DescriptionView Displays the information in a view that provides descriptive text. Standard Displays the information in a view that conserves space. Compact Displays the items in a hierarchical view. This view is disabled for the list of servers on the Backup and Restore tab. Tree Displays the items in a list that you can sort by columns. This view is disabled for the list of servers on the Backup and Restore tab. List To customize views on the Backup Exec Administration Console ◆ On the Backup and Restore tab, the Job Monitor tab, or the Storage tab, in the Views group, click Standard, Compact, Tree, or List. Note: The Tree and List view is disabled for the list of servers on the Backup and Restore tab. Configuring the Home tab You can configure the Home tab by selecting the items that you want to display. You can drag and drop items to move them to another location on the Home tab or you can maximize a single item. The Home tab items contain Backup Exec data and links to features that you use frequently. To configure the Home tab 1 On the Home tab, in the Layout group, click the layout for the items that you want to display. 2 In the System Health and Support groups, select the check box for the items that you want to display. 3 Drag the items to a column and position in which you want them to display to further customize the Home tab. You can configure the Layout, and hide or display items in the System Health and the Support groups. 126Getting Started Configuring the Home tab
- 127. Restoring the Home tab's default layout You can quickly restore the Home tab to its default configuration at any time. To restore the Home tab's default configuration ◆ On the Home tab, in the Layout group, click Reset Home Tab. Layout group You can select one of the following layout configurations to display the items on the Home tab. Table 3-3 Home Tab Layout items DescriptionItem Displays the Home tab items in one column.One Column Displays the Home tab items in two columns.Two Columns Displays the Home tab items in two columns with a narrow panel and a wide panel. Narrow/Wide Displays the Home tab items in three columns. Three Columns Restores the contents of the Home tab to the default configuration. Reset Home Tab System Health group The items in the System Health group provide overviews of alerts, backup jobs, backup size data, storage status, the Symantec ThreatCon Level, and Simplified Disaster Recovery. You can select the following items to display on the Backup Exec Home tab. 127Getting Started Configuring the Home tab
- 128. Table 3-4 System Health group items DescriptionItem Lets you view all alerts that have not received a response. You can filter the alerts to view specific types of alerts, the source of the alerts, and the amount of time that alerts occurred. You can display any or all of the following types of alerts: ■ Error ■ Warning ■ Attention Required ■ Information Active Alerts Lets you view the property and response information for alerts. Alert History Provides a summary view of the backup job status for the servers that are backed up or available for backup. Backup Status Provides a summary view of the amount of data that is backed up. You can customize the number of days for which you display information about the backup size. You can also select the type of backups that display. Backup Size Provides a summary view of the amount of space that is available on your storage. The storage information includes the total capacity that displays the amount space that is used for the different types of data. Storage Status Provides an overall view of global Internet security level. Symantec's ThreatCon levels are based on a 1-4 rating system, with level 4 being the highest threat level. You must have Symantec Endpoint Protection 11.0 or later installed on the same computer as Backup Exec to view this item. Symantec ThreatCon Level 128Getting Started Configuring the Home tab
- 129. Table 3-4 System Health group items (continued) DescriptionItem Provides a status of whether the Simplified Disaster Recovery disk image has been created. If the Simplified Disaster Recovery disk image has not been created, you can click the Create Disaster Recovery link to launch a wizard that guides you through the process. See “About Simplified Disaster Recovery” on page 730. Simplified Disaster Recovery Support group The items in the Support group provide technical support, documentation, licensing and maintenance contracts, and the Symantec RSS Reader resources. You can select the following items to display on the Backup Exec Home tab. Table 3-5 Support group items DescriptionItem Provides the following support options to help you understand product features and functionality or troubleshoot issues: ■ Backup Exec Tech Center ■ Backup Exec Technical Support ■ Best Practices ■ Use MySupport to manage new or existing support cases ■ Symantec Remote Assistance ■ Register to receive notifications ■ Get Backup Exec updates Technical Support Provides the following documentation options to help you understand product features and functionality or troubleshoot issues: ■ View Readme ■ View Administrator's Guide (PDF) ■ View Administrator's Guide Addendum (PDF) Documentation 129Getting Started Configuring the Home tab
- 130. Table 3-5 Support group items (continued) DescriptionItem Provides the following licensing and maintenance options to help you manage maintenance contracts and licenses: ■ View license information ■ View maintenance contract information Licensing and Maintenance Lets you view and add Backup Exec and Symantec RSS feeds. Symantec RSS Reader Provides the following reports: ■ Migration report ■ Installation Summary report This item only displays when you upgrade Backup Exec to a later version. See “Using the Migration Report to determine how existing jobs changed after an upgrade to Backup Exec 15” on page 115. See “Viewing the Installation Summary Report” on page 105. Installation and Upgrades Configuring the Symantec RSS Reader You can customize the Symantec RSS Reader and select the default Backup Exec feeds that display in the reader. You can add additional Symantec and Backup Exec RSS feeds or remove RSS feeds. The Symantec RSS Reader sorts articles by the date and the time. The reader displays the last entry of an article in the RSS feed; however, you can choose to view the full article. The Symantec RSS Reader refreshes the RSS feeds every 15 minutes when the item is open in the Home tab. If the RSS feed is not open in the reader, the RSS feed does not refresh. To view an article in the Symantec RSS Reader 1 On the Home tab, in the Support group, select the Symantec RSS Reader check box. 2 In the Symantec RSS Reader, click the arrow next to the RSS feed that contains the article. 130Getting Started Configuring the Symantec RSS Reader
- 131. 3 Click the hyperlink for the article that you want to open. The Symantec RSS Reader opens a new window that contains a portion of the article from the RSS feed. 4 Click Go to full Article to open Internet Explorer and view the entire contents of the article. To customize the Symantec RSS feeds to the Symantec RSS Reader 1 On the Home tab, in the Support group, select the Symantec RSS Reader check box. 2 In the Symantec RSS Reader, click the pencil icon to add an RSS feed. 3 Enter any of the following: Indicates the location of the RSS feed that you want to add to the Symantec RSS Reader. URL Indicates the name of the RSS feed that you want to display in the Symantec RSS Reader. Name Shows a list of Symantec RSS feeds that you can add to the Symantec RSS Reader. Click here to see more Symantec RSS feeds 4 Click OK. To remove an RSS feed from the Symantec RSS Reader 1 On the tab, in the Support group, select the Symantec RSS Reader check box. 2 Do one of the following: Clear the check box of the Backup Exec RSS feed. To remove a default Backup Exec RSS feed Click the red X next to the name of the RSS feed. To remove an RSS feed that you added to the Symantec RSS Reader Creating a disaster preparation plan (DPP) Disaster preparation planning is the implementation of strategies and procedures that minimize damage in the event a catastrophe destroys your data. The following basic methods are available for disaster recovery: 131Getting Started Creating a disaster preparation plan (DPP)
- 132. ■ Automated recovery. Backup Exec’s Simplified Disaster Recovery (SDR) option automates the disaster recovery process for Windows computers. ■ Manual recovery. You can manually recover both local and remote Windows computers. The purpose of a Disaster Preparation Plan (DPP) is to return to an operational status as quickly as possible. Backup Exec is a crucial component of the DPP. The DPP you put in place with your Backup Exec system should be customized to your network environment. For more information about how to perform a manual disaster recovery, click the following URL: http://entsupport.symantec.com/umi/V-290-706 While environments vary in different organizations, consider the following elements when creating a comprehensive DPP. Table 3-6 Key elements of a DPP DescriptionElement The hardware devices on your network (CPUs, drives, video) are susceptible to damage from many disaster situations. Uninterruptible power supplies (UPS), surge protectors, and security monitoring devices are the equipment most often used today to protect hardware. If you do not already have these items in place, you should consider installing them. The initial investment could be justified many times over in the event of a disaster. Hardware protection Make sure that proper precautions are taken by everyone to implement plans for network interruptions. For example, the phones in the sales department won’t stop ringing because the server is down, so orders may have to be handwritten until the server is up again. Each department should work out strategies for such occurrences. If the proper precautions are taken, the server can be rebuilt quickly and operations can still continue. The ability to maintain business operations during a disaster period A well-designed backup strategy that includes a strong media rotation scheme plays a key role in quickly restoring your file server. A sound backup strategy. 132Getting Started Creating a disaster preparation plan (DPP)
- 133. Table 3-6 Key elements of a DPP (continued) DescriptionElement It is imperative that you regularly move the backed-up data to an off-site storage facility. If you use disk as your storage medium, consider adding a stage to duplicate backups to other storage This ensures that if something happens to your facility, all of your backups are not destroyed. Depending on the importance of your data, you may choose to use several off-site storage facilities. Off-site and duplicate stage backups. A person or group of people should constantly supervise your organization’s disaster preparation efforts. This person or group should install and maintain hardware protection devices, make sure all departments have a plan if the server goes down temporarily, and make sure that backups are made and rotated off-site regularly. Document your Disaster Preparation Plan for reference purposes. Effective DPP management See “Getting started with backups” on page 133. Getting started with backups After you install Backup Exec, you can run a backup job. The following table describes the recommended process for getting started. Table 3-7 Getting started with backups DescriptionStep You must have a configured storage device before you can run any backup jobs. If no storage devices are already configured, such as tape drives or robotic libraries, then you can use the Configure Storage wizard to set up storage devices in Backup Exec. The wizard guides you through configuring all of the storage that Backup Exec supports. To start the wizard, on the Storage tab, in the Configure group, click Configure Storage. The wizard guides you through the rest of the process. See “Using the Configure Storage wizard” on page 412. 1. Configure storage 133Getting Started Getting started with backups
- 134. Table 3-7 Getting started with backups (continued) DescriptionStep You can use the default Backup Exec logon account, which is the system logon account for the Backup Exec server. Backup Exec uses the system logon account by default for most backups. The system logon account contains the credentials of the Backup Exec service account. If the service account does not have rights to access the data that you select for backup, you can use the Logon Account Wizard. Use this wizard to create additional logon accounts that do contain the necessary credentials for accessing that data. To start the Logon Account Wizard, click the Backup Exec button. Select Configuration and Settings > Logon Accounts > Logon Account Wizard. See “Backup Exec logon accounts” on page 603. 2. Configure Backup Exec logon accounts You can back up any of the computers on which you installed the appropriate Backup Exec agent, such the Agent for Windows, or the Agent for Mac. If you didn't install a Backup Exec agent on a computer, you can do so now. On the Backup and Restore tab, in the Servers group, click Add, and then click the appropriate selection. The wizard guides you through the rest of the process. To start a backup job, on the Backup and Restore tab, select the computer that you want to back up and then in the Backups group, click Backup. Click a menu item, such as Back Up to Disk. You can click Edit to change any of the defaults, or you can click OK to accept all of the defaults and let Backup Exec schedule the job. See “Backing up data” on page 146. 3. Run a backup job 134Getting Started Getting started with backups
- 135. Table 3-7 Getting started with backups (continued) DescriptionStep By default, Backup Exec selects all the data on a computer for backup, including the critical system components that you need to perform a full system restore by using SDR. SDR-enabled backups are those backups for which all of the critical system components are selected for backup. You must have SDR-enabled backups to use Backup Exec to rebuild a computer and restore it to a functional state. See “How to ensure that backups are enabled for Simplified Disaster Recovery” on page 738. After you have run SDR-enabled backups for all of the computers that you want to protect, you should create a Simplified Disaster Recovery (SDR) disk image. On the Backup and Restore tab, in the Restores group, click Create Disaster Recovery Disk. The wizard guides you through the rest of the process. See “Creating a Simplified Disaster Recovery disk image” on page 745. 4. Create the Simplified Disaster Recovery disk image 135Getting Started Getting started with backups
- 136. Backups This chapter includes the following topics: ■ How to prepare for your first backup with Backup Exec ■ Required user rights for backup jobs ■ About the list of servers on the Backup and Restore tab ■ Adding servers that you want to back up to the list of servers on the Backup and Restore tab ■ Removing servers from the list of servers on the Backup and Restore tab ■ Creating a server group ■ Hiding or viewing server groups on the Backup and Restore tab ■ Adding servers to a server group ■ Removing servers from a server group ■ Editing a server group ■ Moving servers to the Retired Servers server group ■ Moving retired servers back to the All Servers server group ■ Removing server groups from Backup Exec ■ Backing up data ■ About selecting data to back up ■ Changing the order in which backup sources are backed up ■ Excluding files from backups ■ Including specific files with a backup job's backup selections 4Chapter
- 137. ■ About backing up critical system components ■ Backup Exec Shadow Copy Components file system ■ Backup methods in Backup Exec ■ Configuring backup methods for backup jobs ■ How Backup Exec determines if a file has been backed up ■ Configuring Backup Exec to automatically delete files after a backup ■ Configuring network options for backup jobs ■ Running the next scheduled backup job before its scheduled time ■ Editing backup definitions ■ Testing credentials for backup sources ■ Replacing the credentials for a backup source ■ Creating new credentials for a backup source ■ Deleting retired or unused backup sources from the Credentials pane ■ How job scheduling works in Backup Exec ■ Including a specific date in the schedule for a backup job ■ Preventing backup jobs from running on a specific date ■ Viewing all scheduled backup jobs on a calendar ■ Adding a stage to a backup definition ■ Editing a stage ■ Duplicating backup sets or a job history manually ■ Running a test run job manually ■ Verifying backed up data manually ■ Copying data from a virtual tape library to a physical tape device using DirectCopy to tape 137Backups
- 138. How to prepare for your first backup with Backup Exec Before you back up data, you should develop a backup strategy that includes the backup method, frequency, and data retention methods that are appropriate for your organization. A backup strategy is the collection of procedures you implement as a solution for backing up your environment. You may have different strategies for different areas of the organization. You may need to analyze your backup environment to determine the following: ■ How much data needs to be backed up? ■ How long will the backups take? ■ How much storage is required? For more information, go to the following URL: http://entsupport.symantec.com/umi/V-269-38 Before you run a backup job, you should ensure that you have the proper user rights. See “Required user rights for backup jobs” on page 139. You must also configure storage before creating backup jobs. You can set up Backup Exec to use specific storage devices or logical groupings of devices, such as storage pools. Specifically, you might want to perform the following tasks to help you manage storage hardware and media most effectively: ■ Create disk-based storage so that Backup Exec can automatically manage backup data retention. See “Configuring disk storage” on page 305. ■ Set up storage device pools to load-balance jobs. See “Creating storage device pools” on page 402. ■ Create media sets to manage data retention for tape cartridge media. See “Default media sets” on page 367. ■ Configure deduplication disk storage to optimize storage and network bandwidth. See “About the Deduplication Option” on page 792. ■ Configure vault stores for the Archiving Option. See “About vault stores in the Archiving Option” on page 1349. 138Backups How to prepare for your first backup with Backup Exec
- 139. Required user rights for backup jobs To perform any backup operations, the following Windows user rights are required for the service account and any Backup Exec logon accounts: ■ Act as part of the operating system. ■ Create a token object. ■ Back up files and directories. ■ Restore files and directories. ■ Manage auditing and security log. ■ Logon as a batch job (only for Windows Vista and later). For more information about user rights in Windows operating systems, see your Microsoft documentation. See “Changing the credentials for a service account” on page 614. See “Backup Exec logon accounts” on page 603. About the list of servers on the Backup and Restore tab You can view a list of servers on the Backup and Restore tab. The servers that display in the list include any servers that Backup Exec discovered during an upgrade, any servers that you manually add to Backup Exec, and any servers that Backup Exec discovers during a catalog operation. Servers must be added to the list so that you can select them for backup jobs. You can also monitor server activity and job status from the list of servers. By default, Backup Exec displays a server's alerts, backup status, and a calendar of the last seven days of backup jobs. It also displays the date and time of the previous and upcoming scheduled backups. You can customize the columns on this list to display additional information. You can select to view any of the following details about each server in the list: ■ Server ■ Server type ■ Version of the server ■ Backup Exec version ■ Data source types 139Backups Required user rights for backup jobs
- 140. ■ Backup selections ■ Active alerts ■ Status ■ Last seven days of backup jobs ■ Last backup ■ Next backup ■ Percent complete ■ Elapsed time ■ Byte count ■ Average job rate ■ Description Windows servers must have the Agent for Windows installed on them before you can add them to the list of servers. When you add Windows servers to Backup Exec, you have the option to install the Agent for Windows to them remotely. If you no longer want to monitor or back up a server with Backup Exec, you can remove it from the list of servers. See “Adding servers that you want to back up to the list of servers on the Backup and Restore tab” on page 140. See “Removing servers from the list of servers on the Backup and Restore tab” on page 141. Adding servers that you want to back up to the list of servers on the Backup and Restore tab Before you can create a backup definition, you must add the servers that you want to protect to the list of servers on the Backup and Restore tab. You can add servers during the push-installation process or you can complete the following procedure to add servers at any time. 140Backups Adding servers that you want to back up to the list of servers on the Backup and Restore tab
- 141. To add servers to the list of servers 1 On the Backup and Restore tab, in the Servers and Virtual Hosts group, click Add. 2 Complete the steps to add a server or servers to the list of servers. Note: If Backup Exec discovered servers using the Discover Data to Back Up option, they display on the Browse dialog box under the heading Servers without an Agent for Windows installed. See “Adding discovered servers to the list of servers in Backup Exec” on page 565. See “About the list of servers on the Backup and Restore tab” on page 139. Removing servers from the list of servers on the Backup and Restore tab If you no longer want to monitor or back up a server with Backup Exec, you can remove it from the list of servers on the Backup and Restore tab. You can no longer back up or restore data from servers after you remove them from the list of servers. Note: If you remove a server from the list and it has scheduled jobs pending, the jobs are deleted. The jobs do not run as scheduled. Do not remove a server from the list of servers if you still want to back up that server. You should not use this procedure to delete a managed Backup Exec server from a CASO environment. You should remove managed Backup Exec servers using the Storage tab. See “Removing a managed Backup Exec server from a Backup Exec server pool” on page 1153. To remove servers from the list of servers 1 On the Backup and Restore tab, right-click the server that you want to remove from the list of servers. 2 Click Remove. 3 Click Yes to confirm that you want to remove the server from the list of servers. See “About the list of servers on the Backup and Restore tab” on page 139. 141Backups Removing servers from the list of servers on the Backup and Restore tab
- 142. Creating a server group Server groups are a way to organize and view server information in the list of servers. You can create server groups based on any criteria. You may want to group servers with a specific type of data or servers that reside in a specific location. Then, when you view server groups, only the server group that you select displays in the list of servers on the Backup and Restore tab. Viewing server groups lets you quickly monitor the status of all of the servers in the group at a glance. You can also back up an entire server group. See “Backing up data” on page 146. Backup Exec comes with two preconfigured server groups. The All Servers server group contains all of the servers in the list of servers. The Retired Servers server group is intended for any servers that you no longer actively monitor with Backup Exec. Servers no longer appear in the All Servers server group after you move them to the Retired Servers server group. To create a server group 1 On the Backup and Restore tab, in the Views group, click Groups. 2 Click Add. 3 In the Group name field, type a name for the server group that you want to create. You may want to name the server group to indicate the type of servers in the group or the location at which the servers reside, for example. 4 In the Description field, type a description for the server group. 5 (Optional) Do any of the following to filter the servers in your environment so that you can find the servers that you want to add to the server group: In the Server type field, select the type of server for which you want to search. To filter servers by type In the Data type field, select the type of data that the server for which you want to search contains. To filter servers by data type In the Name contains field, type all or part of the server name. To filter servers by name 6 In the Servers group box, select the servers that you want to add to the server group, and then click OK. See “Hiding or viewing server groups on the Backup and Restore tab” on page 143. See “Adding servers to a server group” on page 143. See “Removing servers from a server group” on page 144. 142Backups Creating a server group
- 143. See “Editing a server group” on page 144. See “Moving servers to the Retired Servers server group” on page 145. See “Removing server groups from Backup Exec” on page 146. Hiding or viewing server groups on the Backup and Restore tab You view server groups on the Groups pane. The Groups pane is enabled by default when you install Backup Exec. If you do not use server groups, you can hide the Groups pane. Double-click a server group on the Groups pane to view more detailed information about the server group's jobs, job history, and any active alerts. To hide or view server groups on the Backup and Restore tab 1 On the Backup and Restore tab, in the Views group, click Groups. 2 Select Show Server Groups. The Show Server Groups option lets you hide or show the Groups pane to the left of the list of servers. See “Creating a server group” on page 142. Adding servers to a server group You can add servers to an existing server group. To add servers to a server group 1 On the Backup and Restore tab, in the Groups pane, right-click the group to which you want to add a server. 2 Select Edit. 3 In the Servers group box, select the servers that you want to add to the server group. You can use the following fields to filter the list of servers so that you can find the server that you want to add: ■ Server type ■ Data type ■ Name contains 4 Click OK. 143Backups Hiding or viewing server groups on the Backup and Restore tab
- 144. See “Creating a server group” on page 142. Removing servers from a server group You can remove servers from an existing server group. To remove servers from a server group 1 On the Backup and Restore tab, in the Groups pane, right-click the group from which you want to remove a server. 2 Select Edit. 3 In the Servers group box, deselect the servers that you want to remove from the server group. You can use the following fields to filter the list of servers so that you can find the server that you want to remove: ■ Server type ■ Data type ■ Name contains 4 Click OK. See “Creating a server group” on page 142. Editing a server group You can edit an existing server group by changing the group's name or description. To edit a server group 1 On the Backup and Restore tab, in the Groups pane, right-click the group that you want to edit. 2 Select Edit. 3 Do any of the following, as necessary: In the Group name field, type the new name for the server group. To change the server group's name In the Description field, type the new description for the server group. To change the server group's description 4 Click OK. See “Creating a server group” on page 142. 144Backups Removing servers from a server group
- 145. Moving servers to the Retired Servers server group You can retire servers from Backup Exec by moving them to the Retired Servers server group. The Retired Servers server group is intended for any servers that you no longer actively monitor with Backup Exec. You can still view any information about the retired servers on the Backup and Restore tab by clicking on the Retired Servers server group. However, the retired servers no longer appear in the All Servers server group with the servers that you regularly back up and monitor. It may be useful to retire servers if you use Backup Exec to monitor a large number of servers. You cannot create new backup jobs for any servers that are in the Retired Servers server group. However, any scheduled backup jobs still run on retired servers. You can restore data from retired servers. If you retire a server and then you decide that you want to move it back to the All Servers server group, you can click on it and drag it from the Retired Servers server group to the All Servers server group. To retire servers from server groups 1 On the Backup and Restore tab, in the Groups pane, right-click Retired Servers. 2 Click Edit. 3 (Optional) Do any of the following to filter the servers in your environment so that you can find the servers that you want to retire: In the Server type field, select the type of server for which you want to search. To filter servers by type In the Data type field, select the type of data that the server for which you want to search contains. To filter servers by data type In the Name contains field, type all or part of the server name. To filter servers by name 4 In the Servers group box, select the servers that you want to retire and then click OK. See “Creating a server group” on page 142. 145Backups Moving servers to the Retired Servers server group
- 146. Moving retired servers back to the All Servers server group You can retire servers from Backup Exec by moving them to the Retired Servers server group. The Retired Servers server group is intended for any servers that you no longer actively monitor with Backup Exec. See “Moving servers to the Retired Servers server group” on page 145. If you retire a server and then you decide that you want to begin monitoring it again, you can reactivate the server. You reactivate the server by moving it from the Retired Servers server group to the All Servers server group. To reactivate retired servers 1 On the Backup and Restore tab, in the Groups pane, click Retired Servers. 2 In the Servers pane, select the server that you want to reactivate. 3 Drag the server to the All Servers group in the Groups pane and drop it there. See “Creating a server group” on page 142. Removing server groups from Backup Exec If you no longer want to use a server group, you can remove it from Backup Exec. Removing a server group does not affect the servers in the group. It only removes the association between the servers and your ability to see them in the group. You can still back up and monitor servers after you remove the server group to which they belong. You cannot remove either the All Servers server group or the Retired Servers server group. To remove server groups 1 On the Backup and Restore tab, in the Groups pane, right-click the server group that you want to delete. 2 Click Remove. 3 Confirm that you want to remove the server group. See “Creating a server group” on page 142. Backing up data When you want to back up data, you create a container that is called the backup definition. Backup definitions contain backup selections, job templates, and stages. 146Backups Moving retired servers back to the All Servers server group
- 147. Table 4-1 Backup definition contents DescriptionItem Backup selections include any servers, volumes, or data that you have selected to back up. Backup selections Job templates are the collection of settings that Backup Exec uses to create jobs. Backup job settings can include scheduling options, storage device options, or backup methods for selected types of data, for example. When you want to run a backup, Backup Exec combines the job template with the backup selections to create a backup job that runs according to the options that you specified. Backup definitions always contain one job template that uses the full backup method, but recurring jobs can also contain incremental, differential, or data-specific job templates. See “Backup methods in Backup Exec” on page 176. Job templates Stages are optional tasks that you can run with backup jobs. Backup definitions can contain one or more stages. You can create stages that duplicate your backup data, create virtual machines with your backup data, or archive your backup data. Stages 147Backups Backing up data
- 148. Figure 4-1 Backup Definition (with backup selections, full and incremental backup job templates, and a duplicate stage) Backup Exec offers many choices for creating backup jobs to protect your data, including the following: ■ Create a recurring backup definition to back up the full or partial contents of a single server or multiple servers If you select to back up multiple servers or applications, you can create separate backup definitions for each server or application. Alternatively, you can create one backup definition that includes all servers and applications. If you create separate backup definitions, it is easier to identify problems when backup jobs fail. Also, if an issue arises with one server that causes a backup job to fail, the other backup jobs can still complete successfully. If you create one backup definition that includes all of your servers and applications, it takes less work to monitor the job status. You can select a default method for backing up multiple servers in the Backups dialog box in the Backup Exec Settings. See “Configuring the default setting for backing up multiple servers or applications” on page 551. Note: You cannot back up multiple servers with a synthetic backup job or a conversion to virtual job. 148Backups Backing up data
- 149. ■ Create a backup definition to run only once A one-time backup only runs once without any recurring instances. You may want to use a one-time backup to create a baseline for a server before you upgrade it or install new software. After Backup Exec finishes running a one-time backup, it deletes the job rather than saving it with your recurring jobs. If you want to view information about a one-time backup after the job is complete, you can still view its job history. Warning: Data lifecycle managemnt deletes all expired backup sets that are created by a one-time backup job. DLM does not keep the last backup set after the retention date expires if the backup set is from a one-time backup. To prevent the backup sets from being automatically deleted, you can manually retain specific backup sets or you can change the expiration date of the backup set. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. ■ Create a new backup definition using an existing backup definition's settings If you want to create a backup definition that is similar to an existing backup definition, you can apply the existing definition's settings to a new definition. Any backup methods, job settings, and stages are copied into a new backup definition for the server or servers that you selected to back up. All that you have to do is select the backup selections. You can override any of the job settings, if necessary. ■ Create a server group out of similar computers and back up the entire group at once Server groups are a way to organize and view server information in the list of servers. You can create server groups based on any criteria. You may want to group servers with a specific type of data or servers that reside in a specific location. You can also edit existing backup definitions to modify their schedules, backup selections, or other settings. To protect remote computers, you must install the Agent for Windows on the remote computer. The Agent for Windows is a system service that runs on Windows servers and workstations. It provides efficient backup processing by locally performing the tasks that, in typical backup technologies, require extensive network interaction. See “Methods for installing the Agent for Windows” on page 72. To back up data 1 Select one of the following methods to back up data: 149Backups Backing up data
- 150. Complete the following steps: ■ On the Backup and Restore tab, select the server, servers, or server group that you want to back up. ■ Right-click the server, servers, or server group. ■ On the Backup menu, select the backup option that you want to use. To create recurring backup jobs Complete the following steps: ■ On the Backup and Restore tab, select the server, servers, or server group that you want to back up. ■ In the Backups group, click One-Time Backup. ■ Select the backup option that you want to use. To create one-time backups Complete the following steps: ■ On the Backup and Restore tab, right-click the server or servers that you want to back up. You cannot reuse a backup definition's settings to create a backup job for a server group. ■ On the Backup menu, select Create a New Backup Using the Settings from an Existing Backup. ■ On the Backup Job Selection dialog box, select the backup definition that contains the settings that you want to copy. ■ Click OK. To create a new backup definition using the settings from an existing backup definition Complete the following steps: ■ On the Backup and Restore tab, in the Groups pane, right-click the server group that you want to back up. ■ On the Backup menu, select the backup option that you want to use. To create a backup definition for a server group 2 In the Name field, type a name for the backup definition. 3 In the Description field, type a description for the backup definition. 150Backups Backing up data
- 151. 4 In the Selections box, click Edit. 5 To add additional servers to the backup definition: ■ Click Add. ■ Select the server or servers that you want to add to the backup definition. ■ Click OK. 6 Select the data that you want to back up. Servers are selected in their entirety by default. If you do not want to back up the entire server, double-click the server name to see all of the contents. Select the check boxes for each item that you want to back up. Note: Deselecting a server's critical system components creates backup sets that cannot be used for some restore scenarios. See “About backing up critical system components” on page 171. 7 Click OK. 151Backups Backing up data
- 152. 8 In the Backup box, click Edit. Note: If you copied the backup settings from an existing backup definition or if you do not want to change any of the existing or default settings, you can skip to step 13 9 In the left pane, click Schedule, and then select when you want the backup job or jobs to run. 10 In the left pane, click Storage, and then select the storage device that you want to use for the backup job or jobs. 152Backups Backing up data
- 153. 11 In the left pane, select any additional options that apply to the backup job or jobs. The remaining options in the left pane are optional. The options vary depending on what you selected to back up. For example, you might want to set up notifications so that users can receive email or texts regarding this backup definition. Select this option to specify the network interface that Backup Exec uses to access remote computers. Network See “Configuring network options for backup jobs” on page 192. Select this option to configure Backup Exec to notify specified recipients when the backup job is completed. Notification Each backup job and stage can be configured with different notification recipients. Backup Exec can notify people by email or text message. See “Notification options for jobs” on page 292. Select this option to configure a test job that automatically tests storage capacity, credentials, and media integrity. Test Run The test job can help you determine if there are any problems that might keep the backup job from completing successfully. See “Configuring automatic test run jobs for backup jobs” on page 518. Select this option to create a job that automatically verifies whether all of the data was successfully backed up when the job is completed. Verify A verify job can also help you determine whether the media you use is defective. See “Configuring automatic verify operations for backup jobs” on page 519. 153Backups Backing up data
- 154. Select this option to configure the delayed catalog operation for any GRT-enabled jobs. You can choose to run a delayed catalog operation, schedule the catalog operation for another time, or choose to not run a delayed catalog operation. See “Configuring delayed catalog operations to improve backup performance” on page 521. Delayed Catalog Select this option to configure the snapshot settings that Backup Exec uses to process the backup job. Snapshot technology lets Backup Exec capture any files that are open when a backup job runs. You can also enable checkpoint restart, which lets you resume interrupted backup jobs. See “Configuring Advanced Open File options for backup jobs” on page 525. See “Configuring checkpoint restart” on page 528. Advanced Open File Select this option to configure off-host backup processing for the backup job. See “Configuring off-host backup options for a backup job” on page 1171. Advanced Disk-based Backup Select this option to configure Backup Exec to work with Symantec Endpoint Protection. You can configure the backup job to run automatically when the Symantec ThreatCon reaches a specified level. Integrating your backup jobs with Symantec Endpoint Protection helps make sure that your vital data is safely backed up as soon as global threats are detected. See “Configuring Backup Exec to work with Symantec Endpoint Protection” on page 530. Security Select this option to configure any commands that you want to run either before the backup job begins or after the backup job is completed. See “Configuring pre/post commands for backup jobs” on page 532. Pre/Post Commands Select this option to configure how Backup Exec processes file system attributes such as junction points and symbolic links. See “Configuring file and folder options for backup jobs” on page 537. Files and Folders 154Backups Backing up data
- 155. Select this option to configure Enterprise Vault options. See “Enterprise Vault backup options” on page 1036. Enterprise Vault Select this option to configure options for any Linux or Macintosh computers that are included in the backup job. See “Linux backup options” on page 1219. See “Default backup job options for Macintosh systems” on page 1252. Linux and Macintosh Select this option to configure options for any Lotus Domino data that is included in the backup job. See “Lotus Domino Agent backup options” on page 1080. Lotus Domino Select this option to configure options for any Microsoft Active Directory data that is included in the backup job. See “Microsoft Active Directory backup job options” on page 1101. Microsoft Active Directory Select this option to configure options for any Microsoft Exchange data that is included in the backup job. See “Backing up Exchange data” on page 946. Microsoft Exchange Select this option to configure options for any virtual machines that are included in the backup job. See “Backing up Microsoft Hyper-V virtual machines” on page 868. See “Backing up VMware data” on page 834. Virtual Machines Select this option to configure options for any Microsoft SharePoint data that is included in the backup job. See “Backing up Microsoft SharePoint data” on page 969. Microsoft SharePoint Select this option to configure options for any Microsoft SQL data that is included in the backup job. See “Backing up SQL databases and transaction logs” on page 894. Microsoft SQL Select this option to configure options for any NDMP data that is included in the backup job. See “NDMP backup options for NDMP servers” on page 1188. NDMP 155Backups Backing up data
- 156. Select this option to configure options for any Oracle data that is included in the backup job. See “Oracle backup options” on page 1011. Oracle Select this option to configure how Backup Exec works with any archiving stages in the backup definition. See “Archive Option backup options” on page 1378. Archive Option Select this option to exclude specific files or specific types of files from backups. See “Excluding files from backups” on page 166. Exclusions 12 When you are finished selecting all applicable options for the backup definition, click OK. 13 (Optional) You can add stages to this backup definition to duplicate your data, create virtual machines with your backup data, or archive your backup data. Note: You cannot add a stage to one-time backups. See “Adding a stage to a backup definition” on page 207. 14 Click OK to save the backup definition settings. The backup jobs and stages run at the time that you selected. See “Creating a server group” on page 142. See “Editing backup definitions” on page 194. See “About selecting data to back up ” on page 157. See “Changing the order in which backup sources are backed up” on page 163. How Backup Exec backs up and restores volumes that are enabled for deduplication in Windows Windows Server 2012 introduced native file system deduplication. When a Windows volume deduplicates data, the deduplicated data is considered to be optimized. Data in its original, non-deduplicated format is considered to be non-optimized. Backup Exec supports the backup of volumes that have Windows deduplication enabled. If you back up optimized data, Backup Exec backs it up in its original, non-optimized format. Ensure that you have enough space to back up the non-optimized data on the backup target before you run the backup job. The optimized files are not affected on the backup source itself. 156Backups Backing up data
- 157. When you restore the data that you backed up, Backup Exec restores the files as non-optimized. Ensure that you have enough disk space to restore the non-optimized data. You should free space on the volume on which you want to restore the files. Run a Windows garbage collector to optimize the space on the volume before you run the restore. How Backup Exec backs up and restores Microsoft Virtual Hard Disk (vhd) files Microsoft Windows 2008 R2 gave users the ability to create native Virtual Hard Disk (vhd) files. A vhd file is a virtual hard disk contained in a single file. For more information about vhd files, see your Microsoft Windows documentation. Backup Exec gives you the ability to back up and restore native vhd files. If a native vhd file is not mounted, you can back up and restore it with the volume on which it resides. If a native vhd file is mounted to a drive letter or to an empty folder path, the file is skipped during backup jobs. You cannot include a mounted vhd as part of your backup selections. To back up the data in a mounted vhd file, select its mount point in the backup selections. See “Backing up data” on page 146. You can also redirect a restore job to a native vhd if you use Microsoft Windows 2008 R2 or later. When you redirect a restore job to a native vhd, Backup Exec creates a vhd file that expands dynamically as you save data to it. The file expands until it reaches 2040 GB, which is the maximum size for a native vhd file. You can create one vhd file with data from all redirected backup sets or you can create a vhd file for each backup set. Backup Exec's Agent for Hyper-V supports Microsoft vhdx files: See “Using the Agent for Hyper-V with Windows Server 2012/2012 R2” on page 860. About selecting data to back up When you back up a server, Backup Exec includes all of the data on the server in the backup selections by default. If you want to modify the backup selections, you can click Edit in the Selections box on the Backup Definitions Properties dialog box. 157Backups About selecting data to back up
- 158. Figure 4-2 Selections box on the Backup Definition Properties dialog box See “Backing up data” on page 146. Instead of backing up all of the data on a server, you can select drives, folders, files, System State, network shares, or databases on the Browse tab. To expand or collapse the view for an item, click the arrow next to it or double-click the item's name. To view the contents of an item, double-click the item’s icon. The item’s contents appear in the right frame of the backup selections view. You can traverse file levels from either side of the window by clicking folders and subfolders as they appear. You can explicitly select any item on the Browse tab by right-clicking the item and selecting Make Item a Required Selection. Explicitly selected backup sources are included in the backup selections. You can explicitly select critical resources to ensure that you can perform an SDR recovery, conversion to a virtual machine, or a complete online restore. Explicitly selected backup sources are usually backed up before any backup sources that are dynamically included in the backup. When you browse remote selections, Backup Exec requires a valid logon account to expand the computer contents. If the default logon account does not enable access to a remote selection, Backup Exec prompts you to select another existing 158Backups About selecting data to back up
- 159. logon account. You can also create a new logon account that can access the selection. See “Testing credentials for backup sources” on page 199. See “Replacing the credentials for a backup source” on page 200. See “Creating new credentials for a backup source” on page 201. To include data in the backup, select the check box next to the drive or directory that you want to back up. Figure 4-3 Selecting data for a single server This topic includes the following information: Including and excluding specific files or subdirectories Selecting multiple servers or applications Selecting critical system components Using fully qualified domain names in backup selections Including and excluding specific files or subdirectories The Selection Details tab lets you include or exclude files for backups by specifying file attributes. Exclusions apply to all of the jobs in a backup definition. You can do any of the following on the Selection Details tab: 159Backups About selecting data to back up
- 160. ■ Include or exclude subdirectories. For example, you can choose to back up a parent folder without backing up any folders that reside inside it. ■ Include only modified files. For example, you can choose to back up only the files that have changed since the last backup job. ■ Include only read-only files. ■ Include or exclude files by file name attributes. For example, you can select only files with .txt extensions, or exclude files with .exe extensions from a backup. If you exclude files by an attribute that does not exist, all files of that type are excluded. For example, excludes based on SQL database dates result in global SQL excludes since SQL databases do not have date attributes. ■ Select only any files that fall within a specified date range. For example, you can select any files that were created or modified during the month of December. ■ Specify the files that have not been accessed in a specified number of days. For example, you can select the files that have not been accessed in 30 days from your "My Documents" folder. Then, run a full backup job for which you select the method to back up and delete the files. The Backup Exec Archive Option offers more features for data archiving. See “About the Archiving Option” on page 1311. See “Excluding files from backups” on page 166. See “Including specific files with a backup job's backup selections” on page 169. Selecting multiple servers or applications If you select to back up data from multiple servers or applications, you can create separate backup definitions for each server or application. Alternatively, you can create one backup definition that includes all servers and applications. If you create separate backup definitions, it is easier to identify problems when backup jobs fail. Also, if an issue arises with one server that causes a backup job to fail, the other backup jobs can still complete successfully. If you create one backup definition that includes all of your servers and applications, it takes less work to monitor the job's status. You can select a default method for backing up multiple servers in the Backups dialog of the Backup Exec Settings. See “Configuring the default setting for backing up multiple servers or applications” on page 551. Selecting critical system components When all the critical system components are included in your backup job selections, the Simplified Disaster Recovery indicator on the selections pane reads ON. If you deselect one or more critical system component files, the indicator changes to OFF. 160Backups About selecting data to back up
- 161. Figure 4-4 Simplified Disaster Recovery indicator is ON in the Backup Definition Properties dialog box Simplified Disaster Recovery indicator 161Backups About selecting data to back up
- 162. Figure 4-5 Simplified Disaster Recovery indicator is ON in the Backup Selections dialog box See “About backing up critical system components” on page 171. If you deselect any critical system components, it can disqualify your backup data from being used in certain types of restore scenarios. You must include all critical system components in your backup selections if you intend to use any of the following restore scenarios: ■ Simplified Disaster Recovery ■ Conversion to virtual machines ■ Complete online restore of a Microsoft Windows computer Using fully qualified domain names in backup selections You can enter fully qualified domain names in Backup Exec anywhere that you can enter a computer name. In addition, Backup Exec can show fully qualified domain names where computer names are listed. For fully qualified domain names, the following rules apply: ■ The maximum number of characters for each label (the text between the dots) is 63 ■ The maximum total number of characters in the fully qualified name is 254, including the dots, but excluding the 162Backups About selecting data to back up
- 163. ■ The name cannot include the following characters: * | < > ? Symantec does not recommend using both fully qualified domain names and non-qualified domain names. Symantec recommends using fully qualified domain names. For example, if you have a computer named Test_Computer, you can have two selections for it. One selection is called Test_Computer. The fully qualified selection is called Test_Computer.domain.company.com. In this case, Backup Exec treats each selection as a separate computer, even though both selections are for the same computer. For any backup jobs that use the short computer name, the catalog contains the short computer name. For any backup jobs that use the fully qualified name, the catalog contains the fully qualified name. See “Changing the order in which backup sources are backed up” on page 163. Changing the order in which backup sources are backed up After you make selections for a backup job, you can configure Backup Exec to process those selections in a certain order. You can create backup jobs where your most important backup sources are backed up first, for example. You must select a backup source to reorder the source or any of its children. If a backup source is included dynamically in the backup, you cannot specify the order in which any of its children are backed up. Any time that you include or exclude a backup source, it creates an entry in the backup's selection details. You can reorder any of the entries that appear on the Selection Details tab. You can explicitly select any item on the Browse tab by right-clicking the item and selecting Make Item a Required Selection. Explicitly selected backup sources are included in the backup selections. You can explicitly select critical resources to ensure that you can perform an SDR recovery, conversion to a virtual machine, or a complete online restore. Explicitly selected backup sources are usually backed up before any backup sources that are dynamically included in the backup. There are some limitations to which backup sources can be reordered: ■ Any backup sources that reside on branches in the browse tree must be backed up together. Branches are containers for backup sources in the browse tree. Individual applications appear in the Backup Exec browse tree as branches. If you have a server which contains SharePoint, SQL, and Exchange data, each application appears as a branch. You can change the backup order of individual items on a branch, but you cannot change the order of items across multiple branches. 163Backups Changing the order in which backup sources are backed up
- 164. For example, if you want to back up a volume and a SQL database, each of the SQL instances must be backed up in succession. You can change the order in which the SQL instances are backed up. You cannot back up a SQL instance and then the volume before backing up the other SQL instances, however. ■ All of the data that resides on a specific backup source is treated as a single item. You can change the order in which the backup sources are backed up in relation to one another. You can also change the order in which the data on a backup source is backed up. However, you cannot reorder the data across multiple backup sources. For example, if you back up two volumes, you can select which volume should be backed up first. You can also select the order in which the data on each volume is backed up. However, you cannot back up some of the data from one volume and then the other volume before backing up the rest of the data on the first volume. ■ Some system resources cannot be reordered. For example, Shadow Copy Components and System State backup sources must always be backed up last. 164Backups Changing the order in which backup sources are backed up
- 165. To change the order in which backup sources are backed up 1 Create or edit a backup definition. 2 In the Selections box, click Edit. . 3 Do one of the following: In the left pane of the Backup Selections dialog box, use the up and down arrows to configure the order of the servers or applications. Backup Exec backs up the servers or applications at the top first. To reorder the servers in a backup definition with multiple servers 165Backups Changing the order in which backup sources are backed up
- 166. Do the following: ■ In the left pane of the Backup Selections dialog box, select the server that contains the resources that you want to reorder. ■ In the right pane of the Backup Selections dialog box, select the Selection Details tab. ■ To reorder the backup sources when a server is selected in its entirety, you must insert the individual selections that you want to reorder: ■ Click Insert, and then select Insert Selection. ■ Select the backup source that you want to reorder, and then click OK. Repeat this step for each backup source that you want to reorder. ■ In the right pane of the Backup Selections dialog box, use the up and down arrows to configure the order of the backup sources. Backup Exec backs up the backup sources at the top first. ■ Click OK. To reorder the backup sources within a server 4 Click OK. See “Backing up data” on page 146. See “About selecting data to back up ” on page 157. Excluding files from backups You can exclude specific files or types of files from backups if you want to ensure that they do not get backed up. For example, you may not want to back up any mp3 files, read-only files, or files from specific directories. You can exclude files from backups in any of three ways: ■ Exclude files from backup jobs When you exclude files from individual backup jobs, the exclusions do not affect any of the other backup jobs in the related backup definition. The job-level exclusions also do not affect any of your other backup definitions. The exclusion applies only to the backup job to which you apply it. You cannot apply a job-level exclusion to Full backups. ■ Exclude files from backup definitions 166Backups Excluding files from backups
- 167. When you exclude files from backup definitions, the exclusions do not affect any of your other backup definitions. The exclusions apply only to any jobs in that backup definition. ■ Exclude files globally from all backups When you globally exclude files from all backups, the exclusions apply to all of your backup definitions. Backup Exec automatically skips any global exclusions when you run backup jobs. To exclude files from backups 1 Do any of the following: Complete the following steps: ■ Create or edit a backup definition. ■ In the Backup box, click Edit. ■ In the left pane, select Exclusions. ■ Click Insert. To exclude files from a backup job Complete the following steps: ■ Create or edit a backup definition. ■ In the Selections box, click Edit. ■ On the Selection Details tab, click Insert and then select Add Backup-Level Exclusion. To exclude files from a backup definition 167Backups Excluding files from backups
- 168. Complete the following steps: ■ Click the Backup Exec button. ■ Select Configuration and Settings, and then select Job Defaults. ■ Click Exclude Selections. ■ Click Insert. To globally exclude files from all backups 2 Complete any of the following fields to identify the files that you want to exclude: Enter the name of the volume or drive that you want to exclude from backups. Resource name Enter the path of the folder and/or subfolder that contains the files that you want to exclude. You can use wildcard characters. Use a question mark ( ? ) to represent any single character. Use two asterisks ( ** ) to represent any number of characters. Path Enter the name of a specific file that you want to exclude from the backup. You can use wildcard characters. Use a question mark ( ? ) to represent any single character. Use two asterisks ( ** ) to represent any number of characters. For example, to exclude all files with a .exe extension, type "**.exe". Name 168Backups Excluding files from backups
- 169. 3 Complete any of the following options, as necessary: Select this option to exclude the contents of all of the subfolders when you select a directory. Apply to subdirectories Select this option to exclude only the files that have been modified in the directory that you specified. Only modified files Select this option to exclude only read-only files in the directory that you specified. Only read-only files Select this option to exclude the files that were created or modified during a specific time period. You must select the beginning and ending dates for the time period. Files dated Select this option to exclude any files that have not been accessed in a specific number of days. You must enter the number of days. Files not accessed in X days 4 Click OK. See “About selecting data to back up ” on page 157. See “Including specific files with a backup job's backup selections” on page 169. Including specific files with a backup job's backup selections When you create a backup definition, you create a list of backup selections. The backup selections are the files and data that you want to back up when the backup jobs run. You can include additional specific files or backup sources with the rest of your backup selections. When you include files with a job's backup selections, you can select certain conditions which must be met for the file to be included. For example, you may want to include any read only files that reside in a specific directory. When you include a file with a backup job's backup selections, Backup Exec backs up the regular backup selections and it includes the file or files that you specifically selected. To include specific files with a backup job's backup selections 1 Create or edit a backup definition. 2 In the Selections box, click Edit. 3 On the Selection Details tab, click Insert and then select Insert Selection. 169Backups Including specific files with a backup job's backup selections
- 170. 4 Complete any of the following fields to identify the files that you want to include: Enter the name of the volume or drive that you want to include in the backup. Resource name Enter the path of the folder and/or subfolder that contains the files that you want to include. You can use wildcard characters. Use a question mark ( ? ) to represent any single character. Use two asterisks ( ** ) to represent any number of characters. Path Enter the name of a specific file that you want to include in the backup. You can use wildcard characters. Use a question mark ( ? ) to represent any single character. Use two asterisks ( ** ) to represent any number of characters. For example, to include all files with a .exe extension, type "**.exe". Name 5 Complete any of the following options as necessary: Select this option to include the contents of all of the subfolders when you select a directory. Apply to subdirectories Select this option to include only the files that have been modified in the directory that you specified. Only modified files Select this option to include only read-only files in the directory that you specified. Only read-only files Select this option to include the files that were created or modified during a specific time period. You must select the beginning and ending dates for the time period. Files dated Select this option to include any files that have not been accessed in a specific number of days. You must enter the number of days. Files not accessed in X days 6 Click OK. See “About selecting data to back up ” on page 157. See “Excluding files from backups” on page 166. 170Backups Including specific files with a backup job's backup selections
- 171. About backing up critical system components Backup Exec is configured to automatically back up the critical system components that you need to perform a full system restore. Backing up critical system components ensures that you are capable of recovering your computers in the event of a disaster. When all the critical system components are included in your backup job selections, the Simplified Disaster Recovery indicator on the selections pane reads ON. If you deselect one or more critical system component files, the indicator changes to OFF. Figure 4-6 Simplified Disaster Recovery indicator is ON in the Backup Definition Properties dialog box Simplified Disaster Recovery indicator 171Backups About backing up critical system components
- 172. Figure 4-7 Simplified Disaster Recovery indicator is ON in the Backup Selections dialog box You must include all critical system components in your backup selections if you intend to use any of the following restore scenarios: ■ Simplified Disaster Recovery See “About Simplified Disaster Recovery” on page 730. ■ Conversion to virtual machines See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. ■ Complete online restore of a Microsoft Windows computer See “Performing a complete online restore of a Microsoft Windows computer” on page 227. Some restore scenarios are only available for certain data types and Backup Exec agents. Additionally, you must select a specific backup method for some data types if you intend to use a physical-to-virtual conversion or a backup-to-virtual conversion. 172Backups About backing up critical system components
- 173. Table 4-2 Restore scenarios by data type Simplified Disaster Recovery Can Be Performed Backup- to-Virtual Conversion Can Be Performed Physical- to-Virtual Conversion Can Be Performed Complete Online Restore Can Be Performed Operating System and Applications Are Installed and Functional File System or Agent Name YesYesYesYesYesActive Directory NoNoNoNoYesActive Directory Lightweight NoNoNoNoYesArchiving Option YesNoNoYesYesCSV YesNoNoYesYesEFI NoNoNoNoYesEnterprise Vault NoYes, any incremental or differential backups must use the block-level backup method Yes, any incremental or differential backups must use the block-level backup method NoYesExchange Agent YesYesYesYesYesFAT NoNoNoNoYesHyper-V Agent NoNoNoNoYesLotus Agent YesYesYesYesYesNTFS NoNoNoNoYesOracle RMAN Windows Agent YesNoNoYesYesReFS 173Backups About backing up critical system components
- 174. Table 4-2 Restore scenarios by data type (continued) Simplified Disaster Recovery Can Be Performed Backup- to-Virtual Conversion Can Be Performed Physical- to-Virtual Conversion Can Be Performed Complete Online Restore Can Be Performed Operating System and Applications Are Installed and Functional File System or Agent Name YesYesYesYesYesShadow Copy Components NoNoNoNoYesSharePoint Agent NoYes, any incremental or differential backups must use the block-level backup method Yes, any incremental or differential backups must use the block-level backup method NoYesSQL Agent YesYesYesYesYesSystem State YesNoNoYesYesUtility Partition NoNoNoNoYesVMware Agent YesNoNoYesYesWindows Deduplication You cannot individually select critical system components as backup selections. You must select the entire server to ensure that all critical system components are included in the backup. When you select to back up a server, Backup Exec includes all of the server's system devices and application agents. Backup Exec dynamically discovers and protects all critical and non-critical system devices and application agents. You can explicitly exclude any non-critical devices or application data from the backup selections without affecting your ability to perform a full system restore. You can exclude Microsoft Exchange data from your backup, for example, and still use the backup sets to perform a disaster recovery. 174Backups About backing up critical system components
- 175. The following system resources are considered critical and they must be included in backups if you want to be able to use the backup sets to perform a full system restore: ■ System volume (including EFI and utility partitions) ■ Boot volume (excluding operating system) ■ Services application volumes (boot, system, and automatic startup) ■ System State devices and volumes (including Active Directory, System Files, etc.) ■ Windows Recovery Partition (WinRE) on any applicable versions of Windows Backup Exec Shadow Copy Components file system The Backup Exec Shadow Copy Components file system uses Microsoft’s Volume Shadow Copy Service to protect critical operating system and application service data, and third-party application and user data on Windows Server 2003/2008 computers. Volume Shadow Copy Service allows a computer to be backed up while applications and services are running by providing a copy of a volume when a backup is initiated. Applications do not need to be shut down to ensure a successful volume backup. Volume Shadow Copy Service enables third-party vendors to create snapshot plug-ins, or Writers, for use with this shadow copy technology. A Writer is specific code within an application that participates in the Volume Shadow Copy Service framework to provide point-in-time, recovery-consistent operating system and application data. Writers appear as Shadow Copy Components, which are listed as data in backup and restore selections. Only Writers that have been tested for use with Backup Exec are available for selection in the backup selections. Other Writers may be displayed in the selections, but they cannot be selected for backup. If you select a volume that contains Shadow Copy data for backup, Backup Exec determines which Shadow Copy files should not be included in a volume-level backup. These files will be automatically excluded for backup by a feature called Active File Exclusion. If this exclusion did not happen during a non-snapshot backup, these files would appear as "in use - skipped." If this exclusion did not happen during a snapshot backup, the files would be backed up in a possible inconsistent state, which could create restore issues. The Windows SharePoint Services feature pack utilizes a SQL (MSDE) instance called SHAREPOINT as a repository for shared information and collaboration data. On Windows Server 2003/2008, in the absence of a Symantec SQL Agent 175Backups Backup Exec Shadow Copy Components file system
- 176. installation, the SQL SHAREPOINT instance can be protected by the Shadow Copy Components file system. If the SQL Agent is installed, then the SQL SHAREPOINT instance can be protected by the SQL Agent. Note: If Windows SharePoint Services is installed using an instance name other than the default SHAREPOINT instance name, then it cannot be protected by the Shadow Copy Components file system. In that case, the Symantec SQL Agent must be used to protect the SQL SHAREPOINT instance. Windows Small Business Server 2003 Standard and Premium contain a SQL (MSDE) instance called SBSMONITORING as a repository for server-related activity data. In the absence of a Symantec SQL Agent installation, the SQL SBSMONITORING instance can be protected by the Shadow Copy Components file system. If the SQL Agent is installed, then the SQL SBSMONITORING instance can be protected by the SQL Agent. Backup methods in Backup Exec When you create a backup definition, you must select backup methods for each backup job. The backup method determines what data Backup Exec backs up. The standard backup methods are full, differential, and incremental. However, you can also select specific types of backup methods for some agents and types of data. Each backup definition must contain one backup job that uses the full backup method. This initial full backup job establishes a baseline by backing up all of the data that you selected. Then, you can add additional differential or incremental backup jobs to the backup definition. You can select to use data-specific backup methods instead of the standard backup methods by selecting the appropriate backup method on the options page for that agent. This topic includes the following information: Full backup method Differential backup method Incremental backup method Backup method advantages and disadvantages Backup methods for specific types of data Full backup method Full backups include all of the data that was selected for backup. Backup Exec detects that the server was backed up. 176Backups Backup methods in Backup Exec
- 177. Note: You should perform a full backup of your server to establish a baseline for disaster recovery. Duplicate backups, which include all selected data, are a type of full backup. Duplicate backups do not affect any tape media rotation strategy because the archive bit is not reset. Symantec recommends that you always run full backups before and after you upgrade, update, or modify any backup sources. This recommendation applies to any significant operating system and application configuration or modifications. Table 4-3 Backup sources and scenarios for which a full backup is recommended Scenarios for which a full backup is recommendedBackup source You should run a full backup when you: ■ Upgrade to a new version of the operating system. ■ Update the existing operating system using Windows Update. Note: You should run a full backup before you apply the update. Apply the update and then restart the computer. Then you should run another full backup. ■ Add, modify, or remove any server roles or features. Operating system You should run a full backup when you: ■ Install new applications. ■ Upgrade applications to new versions. ■ Update the existing version of applications. Applications You should run a full backup when you: ■ Upgrade to a new version of Backup Exec. Note: Any recurring jobs that are migrated to a new version of Backup Exec retain their existing schedules. You should manually run a full backup for any existing jobs before any incremental backups or differential backups run. ■ Update the existing version of Backup Exec using LiveUpdate. ■ Make configuration changes. Backup Exec Running full backups before and after each of these scenarios helps to ensure that you can restore back to the previous configuration, if necessary. 177Backups Backup methods in Backup Exec
- 178. Differential backup method Differential backups include all files that have changed since the last full backup or incremental backup. The difference between differential and incremental backups is that differential backups are cumulative. After a differential backup, each subsequent differential backup backs up the same files as the previous differential backup. It also backs up as any new files or changed files dating back to the last full backup or incremental backup. Note: In a backup definition that includes a differential task, all of the backup tasks must use storage devices that the same Backup Exec server can access. By default, Backup Exec uses the Windows Change Journal to determine if files were previously backed up. You can also configure Backup Exec to use a file's modified time or archive bit to determine if the file was backed up. Note: You cannot use Backup Exec catalogs to determine if files were backed up for any differential backups. See “Configuring file and folder options for backup jobs” on page 537. Differential backups allow much easier restoration of an entire device than incremental backups since fewer backups are required. Using fewer media also decreases the risk of having a restore job fail because of media errors. Incremental backup method Incremental backups include only the files that have changed since the last full or incremental backup. The difference between incremental and differential backups is that incremental backups are not cumulative. Each incremental backup creates a baseline. After the incremental backup, the subsequent incremental backup or differential backup backs up only any new files or changed files dating back to the baseline. Note: In a backup definition that includes an incremental task, all of the backup tasks must use storage devices that the same Backup Exec server can access. By default, Backup Exec uses the Windows Change Journal to determine if files were previously backed up. You can also configure Backup Exec to use a file's modified time, archive bit, or the Backup Exec catalogs to determine if the file was backed up. See “Configuring file and folder options for backup jobs” on page 537. 178Backups Backup methods in Backup Exec
- 179. Incremental backups take much less time than full or differential backups to complete. They also require less storage space for backed up data since only any files that have changed since the last backup are backed up. Backup method advantages and disadvantages Each backup method has advantages and disadvantages. Table 4-4 Backup method Advantages and Disadvantages DisadvantagesAdvantagesMethod ■ Redundant backups Most of the files on your file server do not change. Each full backup that follows the first is merely a copy of what has already been backed up. Full backups require more storage. ■ Full backups take longer to perform Full backups can be time consuming, especially when you have other servers on the network that need to be backed up (for example, agent workstations, remote servers). ■ Files are easy to find Full backups include all the data that you selected to back up. Therefore, you don’t have to search through several backup sets to find a file that you need to restore. ■ A current backup of your entire system is available on one backup set If you run a full backup of your entire system and then need to restore it, all of the most current information is located in one place. Full 179Backups Backup methods in Backup Exec
- 180. Table 4-4 Backup method Advantages and Disadvantages (continued) DisadvantagesAdvantagesMethod ■ Redundant backups All of the files that were created or modified since the last full backup are included; thus creating redundant backups. ■ Files are easy to find Restoring a system that is backed up with a differential method requires fewer backups. Differentials require the latest full backup, any subsequent incremental backups, and the latest differential backup. Restoring differentials is less time consuming than restoring incrementals. Restoring incrementals requires the latest full backup and all incremental backups that were created since the full backup. ■ Less time is required for backup and restore Differential backups take less time to restore than full backups. Faster recovery is possible in disaster situations because you only need backup sets from the latest full backup, any subsequent incremental backups, and the latest differential backup to fully restore a server. Differential ■ Backups are spread across multiple backup sets Since multiple backup sets are required in a disaster situation, recovering a server can take longer. In addition, the backup sets must be restored in the correct order to effectively bring the system up to date. ■ Better use of storage Only the files that have changed since the last backup are included, so much less data storage space is required. ■ Less time is required for backup Incremental backups take much less time than full and differential backups to complete. Incremental Consider the following backup strategy scenario: 180Backups Backup methods in Backup Exec
- 181. You want to implement a backup strategy for the office file server. All backup strategies begin with a full backup (the backup of an entire server using the full backup method). So you create and submit a full backup job to run at the end of the day on Friday. Most files on the server, such as operating system files and application files seldom change. Therefore, you decide that you can save time and storage by using incremental backups or differential backups. You opt to use incremental backups. You schedule a job to run at the end of each day, Monday through Thursday, with the incremental backup method. On Friday, your backup sets contain all of the data on the file server. Backup Exec changes all of the files' statuses to backed up. At the end of the day on Monday, the incremental job runs and only the files that were created or changed are backed up. When the incremental job completes, Backup Exec turns off the archive bit, showing that the files have been backed up. On Tuesday through Thursday, the same events happen. If your file server then crashed on Thursday, you would restore each backup in the order in which it was created. You would begin with Friday's backup and proceed through Wednesday's backup. If you had decided to perform differential backups on Monday through Thursday, you would have only needed Friday's and Wednesday's backup sets. Friday's backup sets would have included all of the data from the original backup. Wednesday's backup sets would have included every file that had been created or changed since Friday's backup. Backup methods for specific types of data Agents and options may have specific types of backup methods. By default, each backup definition contains a backup job that limits the available backup method to the initial full backup for most data types. You can configure additional backup jobs that contain special backup methods for specific types of data. You can name the job templates for those backup jobs so that they have additional meaning to your organization's overall backup strategy. See “Configuring backup methods for backup jobs” on page 184. When you create a backup definition that contains more than one backup method for multiple data types, it is called a mixed backup in the Job Monitor. 181Backups Backup methods in Backup Exec
- 182. Table 4-5 Available Backup Methods By Data Type Job type and backup methodData type Initial full: ■ Full - Back up files Additional backup methods for files and folders: ■ Full - Back up files ■ Full Copy - Back up files (copy) ■ Differential - Back up changed files since the last full ■ Incremental - Back up changed files since the last full or incremental Files and Folders Initial full: ■ Full - Back up components Additional backup methods for Enterprise Vault: ■ Full- Back up components ■ Differential - Back up component changes since the last full ■ Incremental - Back up component changes since the last full or incremental Enterprise Vault Initial full: ■ Full - Back up databases and logs (reset archive bit) Additional backup methods for Lotus Domino: ■ Full - Back up databases and logs (reset archive bit) ■ Incremental - Back up changed databases and logs (reset archive bit) Lotus Domino Initial full: ■ Full - Back up databases and logs (truncate logs) ■ Full Copy - Back up databases and logs Additional backup methods for Microsoft Exchange: ■ Full - Back up databases and logs (truncate logs) ■ Full Copy - Back up databases and logs ■ Differential - Back up logs ■ Incremental - Back up logs (truncate logs) Microsoft Exchange 182Backups Backup methods in Backup Exec
- 183. Table 4-5 Available Backup Methods By Data Type (continued) Job type and backup methodData type Initial full: ■ Full - Back up virtual machines Additional backup methods for virtual machines: ■ Full - Back up virtual machines ■ Differential - Back up virtual machine changes since the last full ■ Incremental - Back up virtual machine changes since the last full or incremental Virtual Machines Initial full: ■ Full - Back up databases ■ Full Copy - Back up databases (copy) Additional backup methods for Microsoft SharePoint: ■ Full - Back up databases ■ Full Copy - Back up databases (copy) ■ Differential - Back up database changes since the last full ■ Differential (block-level) - Back up database changes since the last full - use with convert to virtual machine job ■ Incremental (block-level) - Back up database changes since the last full or incremental - use with convert to virtual machine job ■ Log - Back up and truncate transaction log Microsoft SharePoint Initial full: ■ Full - Back up databases ■ Full Copy - Back up databases (copy) Additional backup methods for Microsoft SQL: ■ Full - Back up databases ■ Full Copy - Back up databases (copy) ■ Automatic - Back up transaction log if enabled and then back up database changes since the last full or incremental ■ Log - Back up and truncate transaction log ■ Log No Truncate - Back up without truncating transaction log ■ Differential - Back up database changes since the last full ■ Differential (block-level) - Back up database changes since the last full - use with convert to virtual machine job ■ Incremental (block-level) - Back up database changes since the last full or incremental - use with convert to virtual machine job ■ Database Snapshot - Read-only point-in-time copy of databases Microsoft SQL 183Backups Backup methods in Backup Exec
- 184. Table 4-5 Available Backup Methods By Data Type (continued) Job type and backup methodData type Initial full: ■ Level 0 - Full backup Additional backup methods for NDMP: ■ Level 0 - Full backup ■ Level 1 - Incremental (backs up new or modified files since level 0) ■ Level 2 - Incremental (backs up new or modified files since level 1) ■ Level 3 - Incremental (backs up new or modified files since level 2) ■ Level 4 - Incremental (backs up new or modified files since level 3) ■ Level 5 - Incremental (backs up new or modified files since level 4) ■ Level 6 - Incremental (backs up new or modified files since level 5) ■ Level 7 - Incremental (backs up new or modified files since level 6) ■ Level 8 - Incremental (backs up new or modified files since level 7) ■ Level 9 - Incremental (backs up new or modified files since level 8) NDMP (all) Initial full: ■ Full - Back up selections Additional backup methods for Oracle: ■ Full - Back up selections ■ Differential - Back up changes since the last full ■ Incremental - Back up changes since the last full or incremental Oracle Initial full: ■ Full - Back up components Additional backup methods for Archive Option: ■ Full - Back up components ■ Differential - Back up component changes since the last full ■ Incremental - Back up component changes since the last full or incremental Archive Options Configuring backup methods for backup jobs When you create a backup definition, you must select backup methods for each backup job. The backup method determines what data Backup Exec backs up. The standard backup methods are full, differential, and incremental. However, you can also select specific backup methods for some agents and types of data. See “Backup methods in Backup Exec” on page 176. 184Backups Configuring backup methods for backup jobs
- 185. By default, each backup definition contains one backup job with an initial full backup method that cannot be changed and a backup job with the incremental backup method. You can replace the incremental job with a differential job, add additional incremental or differential backup jobs, or change the backup methods to data-specific backup methods for certain types of data. Each backup method can be given a unique name to help make it more easily identifiable. To configure backup methods for backup jobs 1 Create or edit a backup definition. 2 In the Backup box, click Edit. 3 In the left pane, click Schedule. 4 (Optional) To add additional backup jobs to the backup definition, complete the following steps: ■ Click Add a Backup Job. ■ Select the type of backup method that you want to use for the new backup job. Note: You can change the backup method to a data specific one for specific agents and types of data later. 185Backups Configuring backup methods for backup jobs
- 186. 5 Type a name for each backup job that you want to configure a backup method for in the Job template name field. 6 (Optional) To change any of the backup methods that you selected into a data-specific backup method, complete the following steps: ■ In the left pane, select the agent or data type for which you want to configure the data-specific backup method. For example, if you want to select a data-specific backup method for SQL data, select Microsoft SQL. ■ In the Backup method field, select the data-specific backup method for each applicable backup job. 186Backups Configuring backup methods for backup jobs
- 187. 7 Click OK. How Backup Exec determines if a file has been backed up If you use the incremental or the differential backup method as part of your backup strategy, Backup Exec must know when a file has been modified. Full backups include all of the data that you selected to back up. Subsequent incremental and differential backups back up only new files and any files that have changed. Whenever a file is created or changed, a computer's file system notes and records the change. You can specify the method by which Backup Exec determines if a file needs to be backed up in the Files and Folders options when you create a backup job. Backup Exec uses the method that you choose to determine when a file is created or changed. This topic includes the following information: 187Backups How Backup Exec determines if a file has been backed up
- 188. Modified time Archive bit Catalogs How Backup Exec uses the change journal to determine which files have changed Resolving change journal errors Modified time When Backup Exec runs a full backup or incremental backup job, the time that the backup job starts is recorded in the Backup Exec Database. Backup Exec adds the time of the backup job to the Backup Exec Database only if the full backup job completes successfully. The next time that you run an incremental backup job or a differential backup job, Backup Exec compares the file system time to the backup time. If the file system time is later than the time that is recorded in the database, the file is backed up. If the file's modified time is older than the previous backup's modified time, that file is not backed up. If the job does not complete successfully, subsequent differential or incremental backup jobs back up all of the data instead of only the data that has changed. Note: A file's last modified date and timestamp do not change when the file is copied or moved. To ensure that the files are protected, run a full backup after you copy or move files. When you run an incremental backup job, Backup Exec records a new time in the Backup Exec Database. The database time is not updated for differential backup jobs. When you select the modified time method, Backup Exec uses the Windows change journal to determine if a file has changed since the last time it was backed up. If the change journal is not available, Backup Exec compares the file information to the previous backup time to determine if the file has changed. Using modified time lets Backup Exec run more accurate incremental backups or differential backups even if other processes have modified files' archive bits. Archive bit Backup Exec uses the archive bit from the file system to determine if a file has changed since the last time it was backed up. When you use the archive bit, Backup Exec turns the archive bit off when a file is backed up. Turning off the archive bit indicates to Backup Exec that the file has been backed up. If the file changes again before the next backup job, the bit is turned on again. Backup Exec backs up the file in the next backup. 188Backups How Backup Exec determines if a file has been backed up
- 189. If the next backup job is a full backup job or an incremental backup job, the bit is turned off when the backup job completes. If the next backup job is a differential backup job, the archive bit is left intact. Catalogs Backup Exec compares path names, modified time, deleted and renamed files and folders, and other attributes. When you select the catalog method, Backup Exec uses the Windows change journal to determine if a file has changed since the last time it was backed up. If the change journal is not available, Backup Exec compares the file information to previous catalogs to determine if it has changed. The catalog method is only available if the Advanced Disk-based Backup Option (ADBO) is installed. Note: The off-host backup feature of ADBO does not support the catalog method. See “Configuring file and folder options for backup jobs” on page 537. How Backup Exec uses the change journal to determine which files have changed When you choose the modified time backup method or the catalog backup method for files, Backup Exec uses the update sequence number (USN) change journal. Backup Exec scans the change journal to get a list of the changed files to back up, rather than scanning all files. Use of the change journal reduces the amount of time that Backup Exec requires to perform an incremental backup or a differential backup. You cannot disable the use of the change journal for either the modified time backup method or the catalog backup method. If the change journal is not already enabled on the volume, then Backup Exec automatically enables it. The volume must support change journals. For example, NTFS and ReFS volumes support change journals, but FAT volumes do not. When Backup Exec enables the change journal, it sets the change journal defaults as shown in Table 4-6. Backup Exec does not modify settings for a change journal that already exists. Table 4-6 Change journal defaults set by Backup Exec DefaultsVolume size ■ Change Journal Max Size: 32 MB ■ Allocation Delta: 4 MB 128 GB or larger ■ Change Journal Max Size: 16 MB ■ Allocation Delta: 2 MB Over 64 GB - 127 GB 189Backups How Backup Exec determines if a file has been backed up
- 190. Table 4-6 Change journal defaults set by Backup Exec (continued) DefaultsVolume size ■ Change Journal Max Size: 8 MB ■ Allocation Delta: 1 MB Over 4 GB - 63 GB ■ Change Journal Max Size: 1 MB ■ Allocation Delta: 256 KB 4 GB or less Note: The Windows Boot Volume is preconfigured by Windows with default values. Resolving change journal errors If change journal errors occur, then Backup Exec uses the modified time backup method or the catalog backup method without using the change journal. When change journal errors occur, you can try the following solutions: ■ Select the Using archive bit backup method for files. ■ Select the file backup method that was not in use when the change journal errors occurred. For example, if you selected the Modified time method and change journal errors occurred, then select the Using catalogs method and run the backup again. ■ Increase the size of the change journal database. Refer to your Microsoft documentation for information on how to use fsutil to query, create, modify, or delete the change journal. ■ Avoid using the local Backup Exec server to back up itself when the Backup Exec server is installed on the Windows Boot volume. Instead, use a remote Backup Exec server to back up the local server, or install the Backup Exec server on a data volume. Note: The off-host backup feature of ADBO does not support the catalog backup method for files. Configuring Backup Exec to automatically delete files after a backup When you run a full backup, you can select to back up the files and then delete them. The Delete selected files and folders after successful backup option lets you free disk space on your server by deleting files and folders from the server after 190Backups Configuring Backup Exec to automatically delete files after a backup
- 191. they are successfully backed up. Backup Exec backs up the selected data, verifies the backup sets, and then deletes the data from the server. You can back up and delete files for full backups only. See “Configuring file and folder options for backup jobs” on page 537. Backup Exec performs a verify operation after the data is backed up. If the verify operation fails, the job stops and you are notified. If you get a verification failure, view the job log. Try to correct the problem, and then retry the job. After the data is backed up and verified, Backup Exec deletes the selected data. The job log contains a list of the data that is deleted. You can enable the checkpoint restart option for a full backup job that uses the Delete selected files and folders after successful backup option. If the job fails and is resumed, the files are not deleted from the source volume after the backup completes. The Backup Exec Archive Option offers more features for data archiving. See “About the Archiving Option” on page 1311. To configure Backup Exec to automatically delete files after a backup 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure Backup Exec to automatically delete files. To configure Backup Exec to automatically delete files after all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure Backup Exec to automatically delete files for specific backup jobs 2 In the left pane, click Files and Folders. 3 Select Delete selected files and folders after successful backup. Note: You can select to delete files and folders only for full backups. 4 Click OK. 191Backups Configuring Backup Exec to automatically delete files after a backup
- 192. Configuring network options for backup jobs You can configure options for how Backup Exec works with your network. Backup Exec contains global network and security settings that apply to all jobs. See “Changing network and security options for Backup Exec” on page 568. You can override the global network settings when you create backup jobs if the global settings do not apply in a particular instance. Complete the steps in the following procedure to configure network options for individual backup jobs. Note: Network options differ in CASO environments. To configure network options for backup jobs 1 Create a new backup definition or edit an existing backup definition. 2 In the Backup box, click Edit. 3 In the left pane, click Network. 4 Complete the following options: Select the name of the network interface card that connects the Backup Exec server to the network that you want to use for this backup job. The list includes all available network interfaces on the Backup Exec server. Network interface Select the protocol you want to use for this backup job. The options are as follows: ■ Use any available protocol ■ IPv4 ■ IPv6 Protocol Select the 32-bit number that determines the subnet to which the network interface card belongs. Subnet Select this option to let Backup Exec use any available network if the remote system that you selected for backup or restore is not part of the specified backup network. If you do not select this option and the remote system is not part of the specified backup network, the job fails. Backup Exec cannot access the data from the remote system. Allow use of any available network interface, subnet, or protocol for Backup Exec agents not bound to the above network interface, subnet, or protocol 192Backups Configuring network options for backup jobs
- 193. Click this option to view the Media Access Control (MAC) address, adapter type, description, IP addresses, and subnet prefixes for the interface that you selected for the backup network. Interface Details Select this option to let a job use any network interface to access Backup Exec agents if the selected network interface is unavailable. Enabling this option lets the managed Backup Exec server use an alternate network interface to run any important backup jobs that would otherwise fail. This option is available only if the Central Admin Server Option (CASO) is installed. See “About the Central Admin Server Option” on page 1106. Allow managed Backup Exec server to use any network interface to access Backup Exec agents 5 Click OK. See “Backup networks” on page 566. Running the next scheduled backup job before its scheduled time You can run the next scheduled backup job in a backup definition at any time. You may want to run a scheduled backup job early to ensure that important data gets backed up or to make sure that a scheduled job completes successfully. Running a scheduled backup job early does not affect its regular schedule. The job still runs normally as scheduled. To run the next scheduled backup job 1 On the Backup and Restore tab, do one of the following: ■ To run the next scheduled backup for a single server's backup jobs, right-click the server name. ■ To run the next scheduled backup for multiple servers' backup jobs, Shift + click or Ctrl + click the server names, and then right-click one of the selected servers. 2 Click Run Next Backup Now. 3 Click Yes to confirm that you want to run the job or jobs now. See “Backing up data” on page 146. 193Backups Running the next scheduled backup job before its scheduled time
- 194. Editing backup definitions You can edit existing backup definitions. You can modify any existing backup definition's backup selections or the backup job settings for any backup jobs that it contains. The backup selections include any servers, volumes, or data that you have selected to back up. Backup job settings can include scheduling options, storage device options, or backup methods for selected types of data, for example. You can also add a stage to an existing backup definition to duplicate your backup data, create virtual machines with your backup data, or archive your backup data. See “Adding a stage to a backup definition” on page 207. If you choose to edit more than one backup definition at once, you can edit only the properties that the definitions have in common. For example, if you choose to edit two backup definitions at once and the definitions use different schedules, you cannot edit the schedules. If you do not see the settings that you want to edit, repeat this procedure, but select only one definition to edit at a time. Note: You cannot edit a backup definition while one of its backup jobs is running. This topic includes the following procedures: To edit a backup definition's backup selections or select user shares to back up To edit a backup definition's job settings To edit a backup definition's backup selections or select user shares to back up 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab, do one of the following: ■ To edit backups for a single server, right-click the server name. ■ To edit backups for multiple servers, Shift + click or Ctrl + click the server names, and then right-click one of the selected servers. ■ Click Edit Backups. Note: If the server or servers that you selected have multiple backup definitions, select the definitions that you want to edit on the Backup Job Selection dialog box and then click OK. To edit backups from the Backup and Restore tab 194Backups Editing backup definitions
- 195. Complete the following steps: ■ On the Job Monitor tab, do one of the following: ■ To edit a single backup, right-click the job name. ■ To edit multiple backups at once, Shift + click or Ctrl + click the job names, and then right-click one of the selected jobs. ■ Click Edit. To edit backups from the Job Monitor tab 195Backups Editing backup definitions
- 196. Complete the following steps: ■ On the Storage tab, double-click the storage device or storage pool for the backup that you want to edit. ■ On the Job History pane, do one of the following: ■ To edit a single backup, right-click the backup. ■ To edit multiple backups, Shift + click or Ctrl + click the backups and then right-click one of the selected backups. Note: You can only edit any backup jobs that have previously run from the Storage tab. ■ Click Edit Backup. To edit backups from the Storage tab 2 In the Selections box, click Edit. 3 To add additional servers to the backup definition: ■ Click the Add (+) button. ■ Select the server or servers that you want to add to the backup definition. You can also click New Server to add a new server to Backup Exec. 196Backups Editing backup definitions
- 197. ■ Click OK. 4 Select the data that you want to back up. Servers are selected in their entirety by default. If you do not want to back up the entire server, double-click the server name to see all of the contents. Select the check boxes for each item that you want to back up. Note: Deselecting a server's critical system components creates backup sets that cannot be used for some restore scenarios. See “About backing up critical system components” on page 171. 5 Click OK. 6 When you are finished editing the backup definition, click OK on the Backup Properties dialog box. To edit a backup definition's job settings 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab, do one of the following: ■ To edit backups for a single server, right-click the server name. ■ To edit backups for multiple servers, Shift + click or Ctrl + click the server names, and then right-click one of the selected servers. ■ Click Edit Backups. Note: If the server or servers that you selected have multiple backup definitions, select the definitions that you want to edit on the Backup Job Selection dialog box and then click OK. To edit backups from the Backup and Restore tab Complete the following steps: ■ On the Job Monitor tab, do one of the following: ■ To edit a single backup, right-click the job name. ■ To edit multiple backups at once, Shift + click or Ctrl + click the job names, and then right-click one of the selected jobs. ■ Click Edit. To edit backups from the Job Monitor tab 197Backups Editing backup definitions
- 198. Complete the following steps: ■ On the Storage tab, double-click the storage device or storage pool for the backup that you want to edit. ■ On the Job History pane, do one of the following: ■ To edit a single backup, right-click the backup. ■ To edit multiple backups, Shift + click or Ctrl + click the backups and then right-click one of the selected backups. Note: You can only edit any backup jobs that have previously run from the Storage tab. ■ Click Edit Backup. To edit backups from the Storage tab 2 In the Backup box, click Edit. 3 In the left pane, select the backup job setting that you want to modify. The options vary depending on what you selected to back up. 4 Make any necessary changes. 198Backups Editing backup definitions
- 199. 5 When you are finished modifying any applicable options for the backup, click OK. 6 When you are finished editing the backup definition, click OK on the Backup Properties dialog box. See “Backing up data” on page 146. Testing credentials for backup sources Backup Exec lists the backup sources and their associated credentials for each server that you monitor on the Credentials pane. If Backup Exec does not have the correct credentials to access content, any attempts to back up that content fail. Symantec recommends that you test to make sure that you have the appropriate credentials to access the content that you want to back up. If a credentials test fails, you can enter new credentials for the content so that Backup Exec can access it. You can test the credentials that are associated with a backup source at any time from the Credentials pane. You can also test the credentials when you create a backup definition. Note: You cannot test credentials for virtual machines, but the job runs if you provide the correct credentials. If the job fails, you may need to retry the job with different credentials. Complete any of the following procedures to test credentials for backup sources: To test the credentials that are associated with a backup source To test the credentials for all of the backup sources in a specific backup definition To test the credentials for a specific backup source in a specific backup definition To test the credentials that are associated with a backup source 1 On the Backup and Restore tab, double-click the server whose credentials you want to test. 2 In the left pane, click Credentials. 3 Select the backup source that you want to test. 4 In the Credentials group, click Test Credentials. The Credential Status field displays the results of the test. 199Backups Testing credentials for backup sources
- 200. To test the credentials for all of the backup sources in a specific backup definition 1 Create a new backup or edit an existing backup. 2 In the Selections box, click Test/Edit Credentials. 3 Click Test All. The Credential Status field displays the results of the test. 4 Click OK. To test the credentials for a specific backup source in a specific backup definition 1 Create a new backup or edit an existing backup. 2 In the Selections box, click Test/Edit Credentials. 3 Select the backup source. 4 Click Test Selected. The Credential Status field displays the results of the test. 5 Click OK. See “Replacing the credentials for a backup source” on page 200. See “Creating new credentials for a backup source” on page 201. See “Deleting retired or unused backup sources from the Credentials pane” on page 202. Replacing the credentials for a backup source Backup Exec lists the backup sources and their associated credentials for each server that you monitor on the Credentials pane. If Backup Exec does not have the correct credentials to access content, any attempts to back up that content fail. Symantec recommends that you test to make sure that you have the appropriate credentials to access the content that you want to back up. If a credentials test fails, you can enter new credentials for the content so that Backup Exec can access it. If you need to change the credentials that are associated with a backup source, you can do so at any time on the Backup and Restore tab from the Credentials pane. You can also change a backup source's credentials when you create or edit backups. To replace the credentials for a backup source ◆ Do one of the following: 200Backups Replacing the credentials for a backup source
- 201. To replace the logon account that is associated with a backup source on the Credentials pane Complete the following steps: ■ On the Backup and Restore tab, double-click the server whose credentials you want to view. ■ In the left pane, click Credentials. ■ In the Logon Account field, select the logon account that you want to use for the backup source. ■ Click Apply. Complete the following steps: ■ Create a new backup or edit an existing backup. ■ In the Selections box, click Test/Edit Credentials. ■ In the Logon Account field, select the logon account that you want to use for the backup source. ■ Click OK. To replace the logon account that is associated with a backup source in a backup definition See “Testing credentials for backup sources” on page 199. See “Creating new credentials for a backup source” on page 201. See “Deleting retired or unused backup sources from the Credentials pane” on page 202. Creating new credentials for a backup source Backup Exec lists the backup sources and their associated credentials for each server that you monitor on the Credentials pane. If Backup Exec does not have the correct credentials to access content, any attempts to back up that content fail. If the credentials for a backup source change, you must enter the new credentials in Backup Exec and associate them with the backup source. You can create new credentials for a backup source at any time on the Credentials pane. You can also create new credentials for a backup source when you create or edit backup definitions. To create new credentials for a backup source 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab, double-click the server for which you want to create new credentials. ■ In the left pane, click Credentials. To create new credentials for a backup source on the Credentials pane 201Backups Creating new credentials for a backup source
- 202. Complete the following steps: ■ Create a new backup or edit an existing backup. ■ In the Selections box, click Test/Edit Credentials. To create new credentials for a backup source in a backup definition 2 In the Logon Account field next to the backup source, select <new logon account>. 3 In the User name field, type the user name for the new logon account. 4 In the Password field, type the password for the new logon account. 5 In the Confirm password field, type the password again to confirm it. 6 In the Account name field, type a unique name for the new logon account. 7 In the Notes field, type any optional notes to explain how the Backup Exec logon account is used. 8 Select This is a restricted logon account if you want the Backup Exec logon account to be used only by the owner of the logon account and those who know the password. If this option is not selected, the Backup Exec logon account is created as a common account. Common accounts are the shared accounts that all users can access. 9 Select This is my default account to make this account your default Backup Exec logon account, which is used to browse, make selections, or restore data on your local computers and remote computers 10 Click OK. See “Testing credentials for backup sources” on page 199. See “Replacing the credentials for a backup source” on page 200. See “Deleting retired or unused backup sources from the Credentials pane” on page 202. Deleting retired or unused backup sources from the Credentials pane Backup Exec lists the backup sources and their associated credentials for each server that you monitor on the Credentials pane. If you remove one of the backup sources from your environment, it still displays in the list of backup sources on the Credentials pane. You can delete retired or unused backup sources from the pane to help make it easier to manage. Backup Exec browses and discovers resources during normal operations. If the backup source that you delete still exists in your 202Backups Deleting retired or unused backup sources from the Credentials pane
- 203. environment, Backup Exec will add it to the list of resources again the next time that it is discovered. You should only delete backup sources from the Credentials pane if they no longer exist in your environment. To delete retired or unused backup sources from the Credentials pane 1 On the Backup and Restore tab, double-click the server that contains the backup source that you want to delete from the Credentials pane. 2 In the left pane, click Credentials. 3 Select the backup source that you want to delete from the Credentials pane. 4 In the Credentials group, click Delete Selected Resource. Backup Exec removes the backup source from the list. Note: If you try to delete a backup source that is used in a backup definition, Backup Exec does not delete that backup source. When you delete a backup source that still exists in your environment, Backup Exec repopulates the list with the backup source the next time it browses your environment. See “Testing credentials for backup sources” on page 199. See “Replacing the credentials for a backup source” on page 200. See “Creating new credentials for a backup source” on page 201. How job scheduling works in Backup Exec Backup Exec lets you configure the time and the frequency for which you want to run backup jobs. You can run jobs immediately, once on a specific day and time, or more than once according to a schedule. Backup Exec lets you use minutes, hours, days, weeks, months, or years as measurements of time to create a recurring pattern for the schedule. Alternatively, you can select specific days of the month to create a recurring schedule on which jobs should run. This topic includes the following information: Availability window Scheduling conflicts Including and excluding dates Availability window Backup Exec has additional scheduling options that you can use to ensure that the job does not run outside of your availability window. The availability window is the 203Backups How job scheduling works in Backup Exec
- 204. time range when your backup sources are available to be backed up. You can configure how long you want an incomplete job to remain scheduled before Backup Exec reschedules the job and changes its completion status to Missed. You can also configure the job to automatically be canceled if it is running for too long after its scheduled start time. These options help ensure that backup jobs do not affect your system resources during critical hours. See “Configuring schedules for backup jobs” on page 504. Scheduling conflicts Backup Exec resolves scheduling conflicts between two backup jobs by running the less common job and skipping the more common job. If a full backup job and an incremental or differential backup job are scheduled to run at the same time, Backup Exec runs the full backup. The incremental backup or differential backup is skipped and it runs again at its next scheduled time. Full backup jobs always supersede incremental and differential backup jobs. If two backup jobs of the same type are scheduled to run at the same time, Backup Exec runs the less frequently scheduled job. The more frequently scheduled job is skipped. The skipped backup job runs again at its next scheduled time. For example, if a monthly job and a daily job are scheduled to run at the same time, Backup Exec runs the monthly job. The daily job is skipped and it runs on the following day per its normal schedule. Including and excluding dates The Exclude Dates option lets you exclude specific dates from the schedule. For example, you can exclude holidays from your normal backup schedule. You can use the Include Dates option to include dates with your backup schedule. When you include a date with your backup schedule, the backup job runs on the included date, even if it is not normally scheduled to run on that date. You may want to schedule an include date to run an extra backup job, outside of the job's normal schedule. See “Preventing backup jobs from running on a specific date” on page 206. See “Including a specific date in the schedule for a backup job” on page 204. Including a specific date in the schedule for a backup job You can include specific dates with your backup schedule for a backup job. When you include a date with your backup schedule, the backup job runs on the included date, even if it is not normally scheduled to run on that date. You may want to schedule an include date to run an extra backup job, outside of the job's normal 204Backups Including a specific date in the schedule for a backup job
- 205. schedule. Scheduling an include date does not affect a backup job's normal schedule. Note: Included dates are applied to the job schedule before excluded dates. When any excluded dates are applied, they may overwrite the included dates if there are any conflicts. Therefore, if you select the same date as both an included date and an excluded date, Backup Exec excludes the date from your backup schedule. See “Preventing backup jobs from running on a specific date” on page 206. To include a specific date in the schedule for a backup job 1 Create or edit a backup definition. 2 In the Backup box, click Edit. 3 In the left pane, click Schedule. 4 Click the Recurrence field for the job to which you want to include a date. 5 On the Include/exclude dates tab, click Include dates. 6 Do one of the following: Complete the following steps: ■ In the Select Date field, type the date that you want to include with the backup schedule. ■ Click Add. Note: You can add only one date at a time. To manually enter the date Click the date that you want to include with the backup schedule. The calendar displays 3 months at a time. You can navigate forward and backward to view additional months by clicking the arrows. Note: You can select only one date at a time. To select the date from the calendar 7 Click OK. See “How job scheduling works in Backup Exec” on page 203. 205Backups Including a specific date in the schedule for a backup job
- 206. Preventing backup jobs from running on a specific date You can exclude specific dates, such as holidays, from your backup schedule for individual backup jobs. When you exclude dates for a specific backup job, only that backup job is affected by the exclude date. The job does not run on the excluded date, even if it is normally scheduled to run. After the exclude date, the job resumes running on its normal schedule. Note: Included dates are applied to the job schedule before excluded dates. When any excluded dates are applied, they may overwrite the included dates if there are any conflicts. Therefore, if you select the same date as both an included date and an excluded date, Backup Exec excludes the date from your backup schedule. See “Including a specific date in the schedule for a backup job” on page 204. To prevent backup jobs from running on a specific date 1 Create or edit a backup definition. 2 In the Backup box, click Edit. 3 In the left pane, click Schedule. 4 Click the Recurrence field for the job to which you want to add an exclude date. 5 On the Include/exclude dates tab, click Exclude dates. 6 Do one of the following: Complete the following steps: ■ In the Select Date field, type the date that you want to exclude from the backup schedule. ■ Click Add. Note: You can add only one date at a time. To manually enter the date 206Backups Preventing backup jobs from running on a specific date
- 207. Click the date that you want to exclude. The calendar displays 3 months at a time. You can navigate forward and backward to view additional months by clicking the arrows. Note: You can select only one date at a time. To select the date from the calendar 7 Click OK. See “How job scheduling works in Backup Exec” on page 203. Viewing all scheduled backup jobs on a calendar You can view all of your scheduled backup jobs for a month, for a week, or for a day on a calendar. It can be helpful to view your backup jobs in the calendar format to make sure there are no scheduling conflicts. You may want to check the calendar before you create a new job. To view all scheduled backup jobs on a calendar 1 On the Backup and Restore tab, in the Backups group, click Backup Calendar. 2 When you are finished viewing the calendar, click Close. See “How job scheduling works in Backup Exec” on page 203. Adding a stage to a backup definition Stages are the additional tasks that you can run with backup jobs as part of the backup definition. You may choose to add stages to the backup definition to customize it. You can add one or more stages for virtualization, duplication, and archiving when you create a backup definition. Stages can also be added to existing backup definitions. For example, you may create a backup job that backs up any important data that must be sent off-site. You can add a duplicate stage to the backup definition that contains that job. The duplicate stage automatically sends the backup data to tape storage when the backup job is complete. Then you can take the tape off-site to ensure that your data is safe. 207Backups Viewing all scheduled backup jobs on a calendar
- 208. Table 4-7 Types of stages DescriptionStage Creates a duplicate copy of your backup and sends it to disk storage. Duplicate to Disk Creates a duplicate copy of your backup and sends it to tape storage. Duplicate to Tape Creates a virtual machine from your backup sets after the backup job is complete. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Convert to Virtual Machine After Backup Creates a virtual machine from your backup sets while the backup job is running. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Convert to Virtual Machine Simultaneously with Backups Creates an archive job to archive the selected file system shares and folders and Exchange mailboxes to a vault store. See “About the Archiving Option” on page 1311. Archive To add a stage to a backup definition 1 Create or edit a backup definition. Note: You cannot add a stage to one-time backups. 2 In the Backup box, click Add Stage. 3 Select the type of stage that you want to add. You can add multiple stages to a backup definition. 4 In the stage box, click Edit. 5 In the left pane, click Schedule, and then select when you want the stage to run. 6 In the left pane, click Storage, and then select the storage device that you want to use for this stage. 208Backups Adding a stage to a backup definition
- 209. 7 Select any additional options that apply to this stage. 8 When you are finished selecting all applicable options for this stage, click OK. Repeat this procedure for each stage that you want to add to the backup definition. See “Backing up data” on page 146. See “Editing a stage” on page 209. Editing a stage You can edit a stage that is part of a backup definition. To edit a stage 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab, right-click the server that contains the backup definition with the stage that you want to edit. ■ Click Edit Backups. ■ If the server has more than one backup definition, select the definition that contains the stage that you want to edit, and then click OK. To edit a stage from the Backup and Restore tab Complete the following steps: ■ On the Job Monitor tab, right-click the job that contains the stage that you want to edit. ■ Click Edit. To edit a stage from the Job Monitor tab 2 Click Edit in the box that contains the stage that you want to edit. 3 Make any necessary changes. 4 When you are finished making changes to the stage, click OK on the Backup Properties dialog box. See “Adding a stage to a backup definition” on page 207. Duplicating backup sets or a job history manually You can configure a duplicate stage to automatically duplicate backup data after a backup job runs. You may want to duplicate data to have an extra copy to send off-site, for example. 209Backups Editing a stage
- 210. See “Adding a stage to a backup definition” on page 207. You can also manually duplicate backup data from completed jobs at any time. When you duplicate backed up data from completed jobs, you select the backup sets or job history that you want to duplicate. The data that you select is read from the source and written to the selected destination, such as a drive, drive pool, or backup folder. You can encrypt the duplicated data. You can schedule when this type of job runs, but it only runs one time. You can select to duplicate one or more individual backup sets or you can duplicate an entire job history. You should duplicate backup sets if you want to duplicate only the data that was backed up in a specific backup job instance. When you duplicate a job history, Backup Exec includes all of a backup definition's dependent backup sets. For example, if you select to duplicate an incremental backup job, Backup Exec automatically duplicates all incrementals dating back to, and including, the last full backup job. This topic includes the following information: Duplicating data from a virtual device to a physical device To duplicate backup sets To duplicate job history Duplicating data from a virtual device to a physical device You can use a duplicate backup job to copy data directly from a virtual device to a physical device. Software encryption cannot be applied to a duplicate backup job when you copy data directly from a virtual device to a physical device. You must either disable DirectCopy or select not to encrypt the job. See “Copying data from a virtual tape library to a physical tape device using DirectCopy to tape” on page 217. If you duplicate any Oracle backup sets that were created with multiple data streams, note the following: ■ Backup Exec converts the multiple data streams to a sequential data stream during the duplication job. ■ A restore job from the duplicated copy may be slower than a restore job from the original media. To duplicate backup sets 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets that you want to duplicate. 2 In the left pane, click Backup Sets. 210Backups Duplicating backup sets or a job history manually
- 211. 3 Do one of the following: ■ To duplicate a single backup set, right-click the backup set. ■ To duplicate multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Select Duplicate. 5 In the Schedule group box, select when you want Backup Exec to run the duplicate job: Select Run now.To run the duplicate job immediately Select Run on, and then enter the date and time.To schedule the job for a later time Select Create without a schedule. You can schedule the job to run later using an external scheduling tool. To schedule the job to run later using an external scheduling tool Click Submit job on hold. The job is created with an On Hold status. It remains on hold until you remove the hold on it. To submit the job on hold 6 In the Storage field, select the storage device to which you want to copy the backup sets. 7 In the Keep for field, select the amount of time that you want Backup Exec to keep the backup sets. The media is protected from being overwritten for the amount of time that you specify. Select Use source retention to keep the backup sets for the same amount of time as the source backup sets that you want to duplicate. 8 Do any of the following: In the Compression field, select the type of compression. To enable compression for the duplicate backup sets 211Backups Duplicating backup sets or a job history manually
- 212. Complete the following steps: ■ In the Encryption type field, select the type of encryption. ■ In the Encryption key field, select the encryption key that you want to use or select Manage keys to create a new key. To enable encryption for the duplicate backup sets Select Verify at the end of the job.To run a verify operation on the duplicate backup sets 9 On the Duplicate Job dialog box, click OK. To duplicate job history 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the job history that you want to duplicate. ■ In the left pane, click Job History. ■ Do one of the following: ■ To duplicate a single job history, right-click the job history. ■ To duplicate multiple job histories, Shift + click or Ctrl + click the job histories, and then right-click one of the selected job histories. To duplicate job history from the Backup and Restore tab or the Storage tab Complete the following steps: ■ On the Job Monitor tab, do one of the following: ■ To duplicate a single job history, right-click the job history. ■ To duplicate multiple job histories, Shift + click or Ctrl + click the job histories, and then right-click one of the selected job histories. To duplicate job history from the Job Monitor tab 2 Click Duplicate. 212Backups Duplicating backup sets or a job history manually
- 213. 3 In the Schedule group box, select when you want Backup Exec to run the duplicate job: Select Run now.To run the duplicate job immediately Select Run on, and then enter the date and time.To schedule the job for a later time Select Create without a schedule. You can schedule the job to run later using an external scheduling tool. To schedule the job to run later using an external scheduling tool Click Submit job on hold. The job is created with an On Hold status. It remains on hold until you remove the hold on it. To submit the job on hold 4 In the Storage field, select the storage device to which you want to copy the job history. 5 In the Keep for field, select the amount of time that you want Backup Exec to keep the job history. The media is protected from being overwritten for the amount of time that you specify. Select Use source retention to keep the job history for the same amount of time as the source job history that you want to duplicate. 6 Do any of the following: In the Compression field, select the type of compression. To enable compression for the duplicate job history Complete the following steps: ■ In the Encryption type field, select the type of encryption. ■ In the Encryption key field, select the encryption key that you want to use or select Manage keys to create a new key. To enable encryption for the duplicate job history Select Verify at the end of the job.To run a verify operation on the duplicate job history 7 On the Duplicate Job dialog box, click OK for each duplicate job that you create. 213Backups Duplicating backup sets or a job history manually
- 214. Running a test run job manually Test run jobs attempt to determine if a scheduled backup could possibly fail when you run it. When you run a test job, no data is backed up. Instead, Backup Exec checks your storage capacity, credentials, and media to find potential errors. If there is an error, the job continues to run until it is completed. The error appears in the job log. You can also configure Backup Exec to send a notification to a designated recipient. During a test run job, the following things may cause a job to fail: ■ Logon credentials are incorrect. ■ Storage capacity is not sufficient. ■ Tape cartridge media or disk cartridge media is not available. ■ Overwritable media is not available for an overwrite job. ■ Appendable media is not available for an append job. A test run job checks the media capacity that is available for the selected job. However, you can check if there is enough available media for multiple test run jobs in the Test Run Results Report. See “Test Run Results report” on page 676. You can configure test run jobs to run automatically before your scheduled backup jobs. Or you can manually run a test run job at any time. Before you run a test run job, Symantec recommends that you run backup jobs to your storage devices first. Backup Exec does not recognize the capacity of a storage device until an actual backup job sends data to the device. If you create a test run job before any other jobs, Backup Exec cannot check that the device has sufficient capacity to perform the backup job. After at least one backup job has sent data to a device, Backup Exec can determine the capacity. To run a test job manually 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab, double-click the server that contains the job you want to test. ■ In the left pane, click Jobs. To run a test job from the Backup and Restore tab 214Backups Running a test run job manually
- 215. Select the Job Monitor tab.To run a test job from the Job Monitor tab 2 Right-click the job that you want to test, and then click Test Run. 3 Click Yes to confirm that you want to run the test job now. See “Configuring automatic test run jobs for backup jobs” on page 518. Verifying backed up data manually Backup Exec can perform a verify operation to make sure that the media can be read after a backup job has been completed. Symantec recommends that you verify all backed up data to ensure the integrity of the collection of data and the media on which it resides. By default, Backup Exec automatically verifies backed up data at the end of a backup job. However, you can also schedule the verify operation to take place at a later time or disable the verify operation altogether. You can change Backup Exec's verify options as part of the default backup settings or for individual backup jobs. See “Configuring automatic verify operations for backup jobs” on page 519. You can also choose to manually run a verify operation on a backup set or a job history at any time. You can verify backup sets if you want to verify only the data that was backed up in a specific backup job instance. If you want to verify a backup definition and all of its dependent backup sets, you can verify a job history. For example, if you want to verify a backup definition that used incremental backups, Backup Exec verifies all incrementals dating back to, and including, the last full backup. This topic includes the following procedures: To verify specific backup sets To verify a job history To verify specific backup sets 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup set or backup sets that you want to verify. 2 In the left pane, click Backup Sets. 3 Do one of the following: ■ To verify a single backup set, right-click the backup set. 215Backups Verifying backed up data manually
- 216. ■ To verify multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Click Verify. 5 In the Schedule group box, select when you want Backup Exec to run the verify operation: Select Run now.To run the verify operation immediately Select Run on, and then enter the date and time.To schedule the operation for a later time Select Create without a schedule. You can schedule the verify operation to run later using an external scheduling tool. To schedule the job to run later using an external scheduling tool 6 Click OK. To verify a job history 1 Do one of the following: Complete the following steps: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the job history that you want to verify. ■ In the left pane, click Job History. ■ Do one of the following: ■ To verify a single job history, right-click the job history. ■ To verify multiple job histories, Shift + click or Ctrl + click the job history, and then right-click one of the selected job histories. To verify a job history from the Backup and Restore tab or the Storage tab On the Job Monitor tab, do one of the following: ■ To verify a single job history, right-click the job history. ■ To verify multiple job histories, Shift + click or Ctrl + click the job histories, and then right-click one of the selected job histories. To verify a job history from the Job Monitor tab 2 Click Verify. 216Backups Verifying backed up data manually
- 217. 3 In the Schedule group box, select when you want Backup Exec to run the verify operation: Select Run now.To run the verify operation immediately Select Run on, and then enter the date and time.To schedule the operation for a later time Select Create without a schedule. You can schedule the verify operation to run later using an external scheduling tool. To schedule the job to run later using an external scheduling tool 4 Click OK. Copying data from a virtual tape library to a physical tape device using DirectCopy to tape Backup Exec's DirectCopy to tape option enables data to be copied from a virtual tape library directly to a physical tape device during a duplicate backup job. The Backup Exec server coordinates the duplicate job, but it does not copy the data. Instead, the virtual tape library copies the virtual tape image directly to the physical device. The Backup Exec server records information about the data in the catalog. Because the information about the copied data is in the catalog, you can restore data from either the virtual tape library or the physical device. The job log for the duplicate backup job indicates that DirectCopy to tape is enabled. To use DirectCopy to tape, both the source device and the destination device must be NDMP-enabled. If the devices are not NDMP-enabled, then Backup Exec performs a regular duplicate backup job. Both hardware encryption and software encryption are supported with DirectCopy to tape. For software encryption, both the source backup set and the destination backup set must use software encryption. Note: If you select disk storage as the destination device for a duplicate job with DirectCopy to tape enabled, Backup Exec performs a regular duplicate job. 217Backups Copying data from a virtual tape library to a physical tape device using DirectCopy to tape
- 218. Table 4-8 How to use DirectCopy to tape to copy data from a virtual tape library to a physical device For more informationNotesStep See “Backing up data” on page 146. See “Configuring storage options for backup jobs” on page 512. Select a virtual tape library as the storage destination. Create a regular backup job. See “DBA-initiated job templates” on page 590. See “Storage options for DBA-initiated jobs” on page 593. See “Duplicate job settings for DBA-initiated jobs” on page 599. In the DBA-initiated job settings: ■ Select a physical tape device as the destination. ■ Select Enable DirectCopy to tape. Create a duplicate backup job. 218Backups Copying data from a virtual tape library to a physical tape device using DirectCopy to tape
- 219. Restores This chapter includes the following topics: ■ Methods for restoring data in Backup Exec ■ Searching for data to restore ■ Restoring data from a server, a backup set, a backup job, or a storage device ■ Restoring file system data ■ Performing a complete online restore of a Microsoft Windows computer ■ Restoring System State ■ Installing a new Windows Server domain controller into an existing domain by using a redirected restore ■ Restoring Backup Exec Shadow Copy Components ■ Restoring utility partitions or Unified Extensible Firmware Interface system partitions ■ About restoring encrypted data ■ About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec ■ Canceling a restore job ■ How Backup Exec catalogs work ■ Cataloging backup sets 5Chapter
- 220. Methods for restoring data in Backup Exec Backup Exec provides guided Search and Restore methods to assist you when you search for or restore backed up data. If you have installed the Archiving Option, you can also search for and restore archived data. From Search or Restore on the Backup and Restore tab, you can do the following: ■ Restore data to the location from which it was originally backed up or redirect the restore to another location. ■ Start the restore job immediately or schedule it to run at a future time. Note: The Restore Wizard displays only up to 30,000 items. If you want to restore data from a folder that contains more than 30,000 items, you should search for the item that you want to restore. You can use search criteria such as the type of data and the date of the original backup to help reduce the number of items that displays. Table 5-1 Guided methods to search for and restore data DescriptionMethod Lets you select multiple servers on which to search for backup sets. Then, you can choose to restore the data, or you can copy and save the search criteria and the results to the clipboard. You can then email the results to the person who requested the restore to ensure that you have found the correct data before you restore it. To start the Search Wizard, on the Backup and Restore tab, select one or more servers, and then in the Restores group, click Search. See “Searching for data to restore” on page 222. Search 220Restores Methods for restoring data in Backup Exec
- 221. Table 5-1 Guided methods to search for and restore data (continued) DescriptionMethod Lets you browse the backup sets from a single server, and then restore the data. You can restore file system data, System State data, Backup Exec Shadow Copy Components, utility partitions or UEFI system partitions, and more. You can also perform a complete online restore of a Windows computer if the computer was fully selected for a backup. By default, backup jobs include all necessary components that are required for a complete restore. To start the Restore Wizard, on the Backup and Restore tab, select a server, and then in the Restores group, click Restore. See “Restoring data from a server, a backup set, a backup job, or a storage device” on page 222. See “Performing a complete online restore of a Microsoft Windows computer” on page 227. Restore Lets you recover Windows computers after a hard drive failure. The Simplified Disaster Recovery wizards guide you in preparing for disaster recovery, and in recovering a local computer or a remote computer to its pre-disaster state. See “About Simplified Disaster Recovery” on page 730. Simplified Disaster Recovery See “Restoring file system data” on page 226. See “Restoring System State ” on page 228. See “Restoring Backup Exec Shadow Copy Components” on page 232. See “Restoring utility partitions or Unified Extensible Firmware Interface system partitions” on page 233. See “Restoring Exchange data” on page 957. See “Restoring SQL databases and transaction logs” on page 916. See “About restoring Oracle resources” on page 1012. See “Restoring VMware virtual machines and vmdk files” on page 848. See “Restoring a deduplication disk storage device or deduplicated data” on page 824. See “About restoring items from the archives” on page 1372. See “About restoring an Archiving Option component” on page 1380. 221Restores Methods for restoring data in Backup Exec
- 222. See “Restoring Microsoft SharePoint data” on page 976. See “Restoring Enterprise Vault” on page 1040. See “About restoring data to Linux computers” on page 1222. See “About restoring Lotus Domino databases” on page 1083. Searching for data to restore You can select one server or multiple servers on which to search for backup sets. Then, you can choose to restore the data, or you can copy and save the search criteria and the results to the clipboard. You can then email the results to the person who requested the restore to ensure that you have found the correct data before you restore it. Backup Exec creates separate restore jobs for each server that you restore data to. The Search Wizard supports only the following types of data: ■ Files and folders ■ Exchange and SharePoint backup sets for which Granular Recovery Technology was enabled ■ Archived file system data and archived Exchange mailbox data Note: You cannot search the backup sets for any data that was backed up from virtual machines. To search for data to restore 1 On the Backup and Restore tab, right-click the server or servers on which you want to search for data, and then click Search. 2 Follow the Search Wizard prompts to search for and restore data. Restoring data from a server, a backup set, a backup job, or a storage device You can restore data by launching the Restore Wizard directly from a server, from backup sets, from completed backup jobs, and from storage device media. You can also perform a complete online restore of a Windows computer if the computer was fully selected for a backup. By default, backup jobs include all necessary components that are required for a complete restore. 222Restores Searching for data to restore
- 223. See “Performing a complete online restore of a Microsoft Windows computer” on page 227. Table 5-2 Restore methods More informationRestore method Restoring data from a serverTo restore from a server To restore data from a backup setTo restore from a backup set Restoring data from a completed backup jobTo restore from a completed backup job Restoring data from storage device mediaTo restore from storage device media Note: If the File Server Resource Manager (FSRM) is running on the server that you are restoring, the job may fail with an "out of disk space" error. If this occurs, disable RSRM, and then run the job again. Restoring data from a server You can browse the backup sets from a single server, and then restore the data. Note: If you back up and then rename a server, the new server name and the old server name both appear on the Backup and Restore tab. The status next to the new server name indicates that it is backed up. However, you should select the icon with the old server name to restore any data that you backed up before you changed the server name. To restore data from a server 1 On the Backup and Restore tab, in the list of servers, or on the Job Monitor tab, right-click a server that has been backed up. 2 Click Restore. 3 Follow the Restore Wizard prompts to restore the data. Restoring data from a completed backup job You can restore data from a completed backup job. When you restore data from backup jobs, you can only choose data that is contained in the backup sets that the backup job produced. To restore data from a completed backup job 1 Do one of the following: 223Restores Restoring data from a server, a backup set, a backup job, or a storage device
- 224. ■ On the Backup and Restore tab, in the list of servers, double-click a server that has been backed up. ■ In the Jobs view, expand a backup definition. ■ Under the backup definition, right-click the backup job from which you want to restore data. ■ Select Restore backup sets created by this job. To restore data from the Backup and Restore tab ■ On the Job Monitor tab, in the Jobs pane, right-click a server that has been backed up. ■ Select Restore backup sets created by this job. To restore data from the Job Monitor tab 2 Follow the Restore Wizard prompts to restore the data. Restoring data from a backup set You can restore data from the backup sets that appear on the Backup and Restore tab. When you restore data from backup sets, you can only choose data that is contained in the backup sets. To restore data from a backup set 1 On the Backup and Restore tab, in the list of servers, double-click a server that has been backed up. 2 In the Backup Sets view, expand a backup set from which you want to restore. 3 Right-click the backup set from which you want to restore data 4 Click Restore. 5 Follow the Restore Wizard prompts to restore the data. Restoring data from storage device media You can restore data from the media that are contained in the storage devices that appear on the Storage tab. When you restore data directly from storage device media, you can only restore data that is contained in the backup sets on the media. The Restore Wizard prompts you to select options for each type of data, and then submits a separate job for each type of data. When you restore from storage device media, you can restore multiple types of data. Separate restore jobs are submitted for each type of data. To restore data from storage device media 1 Select from the following: 224Restores Restoring data from a server, a backup set, a backup job, or a storage device
- 225. Do the following in the order listed: ■ On the Storage tab, in the All Storage view, navigate to the storage device from which you want to restore. ■ Double-click the disk storage device, and then click Backup Sets on the left. ■ Right-click the backup set from which you want to restore, and then click Restore. To restore from a disk storage device Do the following in the order listed: ■ On the Storage tab, in the All Storage view, expand Tape and Disk Cartridge Media. ■ Navigate to the media that contains the data that you want to restore. ■ Right-click the media from which you want to restore, and then click Restore. To restore from tape drive media or a disk cartridge media Do the following in the order listed: ■ On the Storage tab, in the All Storage view, navigate to the robotic library from which you want to restore. ■ Expand the robotic library. ■ Double-click Slots. ■ In the Slots view, right-click the slot that contains the media from which you want to restore, and then click Restore. To restore from media within a robotic library 2 Follow the Restore Wizard prompts to restore the data. 3 (Optional) To restore multiple types of data, proceed through the Restore Wizard and select the appropriate options for the type of data that you select. Then, do the following: ■ On the summary page, click Continue to submit the job and return to the page that lists the different types of data. The Job Submitted column displays an icon to indicate that the restore job for the first type of data has been submitted. ■ Select the next type of data and the appropriate restore options for that type of data. If you do not want to restore the other types of data, you can click Cancel to exit the Restore Wizard without affecting any of the jobs that you already submitted. 225Restores Restoring data from a server, a backup set, a backup job, or a storage device
- 226. ■ After you configure jobs for each type of data, the Continue button changes to a Finish button. When you click Finish, Backup Exec submits the final restore job, and then closes the Restore Wizard. Restoring file system data When you restore files, folders, or volumes, you can restore to a point-in-time or you can restore from a backup set. If you know which backup set, completed backup job, or storage device media contains the data that you want to restore, you can start the Restore Wizard from there. Otherwise, you can select a server and then start the Restore Wizard. See “Restoring data from a server, a backup set, a backup job, or a storage device” on page 222. To restore file system data 1 On the Backup and Restore tab, right-click the server for which you want to restore data, and then click Restore. 2 Select Files, folders, or volumes, and then click Next. 226Restores Restoring file system data
- 227. 3 Do one of the following: Select File and folder backups to a point-in-time. To restore the data to a point-in-time at which the backup set was created Note: When you restore file system data to a point-in-time, you select a backup set to restore. The backup set represents the file system data at the specific point-in-time at which it was backed up. Backup Exec automatically restores any related backup sets that are required to restore the file system data to its state at the point-in-time. Select File and folder backups from a backup set. To restore file and folder backups from a backup set Note: When you restore file system data from a backup set, you select a backup set to restore. Backup Exec restores the file system data exactly as it exists in the backup set that you select. No dependent backup sets are selected for the restore. Select Files and folders located through Search. To search for files and folders 4 Click Next, and then follow the Restore Wizard prompts to restore the data. Performing a complete online restore of a Microsoft Windows computer You can perform a complete online restore of a Microsoft Windows computer if the computer was fully selected for a backup. You select the backup set time from which you want to recover the computer. All required backup sets are automatically selected. You can select additional backup sets to restore as appropriate. You cannot redirect the restore of the computer. To run a complete online restore of a Microsoft Windows computer 1 On the Backup and Restore tab, right-click the computer that you want to restore, and then click Restore. 2 Select A Microsoft Windows computer that was fully selected for a backup, and then click Next. 227Restores Performing a complete online restore of a Microsoft Windows computer
- 228. 3 Select Complete online restore of a computer, or restore system components, and then click Next. 4 Follow the Restore Wizard prompts to restore the data. See “About backing up critical system components” on page 171. See “Methods for restoring data in Backup Exec” on page 220. Restoring System State Depending on the version of Microsoft Windows, service pack levels, and features that are installed, you can restore the following system state data: ■ Active Directory ■ Automated system recovery ■ Background Intelligent Transfer Service ■ COM+ Class Registration database ■ Dynamic Host Configuration Protocol ■ Event logs ■ File Server Resource Manager ■ Internet Information Service (IIS) ■ Microsoft Search Service ■ Network Policy Server ■ Registry ■ Remote Storage ■ Removable Storage Manager ■ Shadow Copy Optimization Writer ■ System files ■ Terminal Server Licensing ■ Terminal Services Gateway ■ Windows Deployment Services ■ Windows Management Instrumentation Note: To restore the Windows Internet Name Service (WINS), you must also restore the registry. You cannot restore WINS by itself. 228Restores Restoring System State
- 229. If the server is a certificate server, then System State includes the Certificate Services database. If the server is a domain controller, then System State includes the Active Directory services database and the SYSVOL directory. See “About the Agent for Microsoft Active Directory” on page 1096. You must restart the computer after you restore System State data. Warning: You should not cancel a System State restore job. Canceling this job can leave the server unusable. If you know which backup set, completed backup job, or storage device media contains the data that you want to restore, you can start the Restore Wizard from there. Otherwise, you can select a server and then start the Restore Wizard. See “Restoring data from a server, a backup set, a backup job, or a storage device” on page 222. Note: When you restore the System State, Backup Exec may create the following temporary directory: %SystemRoot%F52E2DD5-CE7D-4e54-8766-EE08A709C28E After the restore job finishes, you can delete the directory. To restore System State 1 On the Backup and Restore tab, right-click the computer for which you want to restore System State, and then click Restore. 2 Select Complete online restore of a computer, or restore system components, and then click Next. 3 Follow the Restore Wizard prompts to restore the data. 4 After you restore System State data, restart the computer. See “About backing up critical system components” on page 171. See “Performing a complete online restore of a Microsoft Windows computer” on page 227. Restoring System State to a domain controller To restore System State to a computer that is a domain controller, you must start the computer in safe mode. Then, use the Directory Services Restore Mode to perform the restore. 229Restores Restoring System State
- 230. To replicate Active Directory to the other domain controllers that exist in the domain, you must perform an authoritative restore of the Active Directory. An authoritative restore ensures that the restored data is replicated to all of the servers. Performing an authoritative restore includes running Microsoft's Ntdsutil utility after Backup Exec restores System State, but before you restart the server. For more information about authoritative restore and the Ntdsutil utility, see your Microsoft documentation. To restore System State to a domain controller 1 Retart the destination server in Directory Services Restore Mode. See your Microsoft documentation for details on how to do this. 2 Open the services. 3 For each Backup Exec service listed, do the following in the order listed: ■ Click Properties. ■ On the Log On tab, click This account. ■ Enter a user account with local administrator’s rights, and then click OK. ■ Right-click the service, and then click Start. 4 After the Backup Exec services have started, run the Restore Wizard to restore System State. See “Methods for restoring data in Backup Exec” on page 220. 5 In the Restore Wizard, enable the option Mark this server as the primary arbitrator for replication when restoring SYSVOL in System State. 6 Restart the server before you restore more data. Installing a new Windows Server domain controller into an existing domain by using a redirected restore To install a new Windows Server domain controller into an existing domain, the Active Directory and SYSVOL data must be replicated to the new domain controller. If there is a large amount of data to be replicated or if the connection between the domain controllers is slow, the replication time can be lengthy. The amount of data to be replicated and the connection speed also affects the Active Directory Application Mode replication time. To decrease the replication time for Active Directory and Active Directory Application Mode, you can use the Microsoft Windows feature called Install from Media. For Active Directory, use the Install from Media feature. Restore the system state backup sets of an existing domain controller in the domain in which you want to 230Restores Installing a new Windows Server domain controller into an existing domain by using a redirected restore
- 231. add a new domain controller. Then, perform a redirected restore of the system state backup sets to the destination domain controller. For Active Directory Application Mode, you can back up data using the ADAM Writer. Then, you can perform a redirected restore of the data from the ADAM backup to the destination computer. See “About the Agent for Microsoft Active Directory” on page 1096. For more information, refer to your Microsoft documentation. Table 5-3 How to install a new Windows Server domain controller into an existing domain by using a redirected restore DescriptionStep Back up the System State data of an active Windows Server domain controller that is in the target domain. You should back up the data to some type of removable storage, such as a disk cartridge device or a tape. See “Backing up data” on page 146. Step 1 Attach the storage that contains the System State data to the computer that you want to install into the destination domain. Note: Symantec recommends that you encrypt the storage. Use caution when transporting it to the location of the destination domain. Step 2 Inventory and catalog the storage. See “Inventorying and cataloging a storage device” on page 438. Step 3 Redirect the restore of the system state backup sets to a temporary location on a volume or directory on the destination computer. See “Restoring System State ” on page 228. Step 4 Start the domain controller installation by doing the following in the order listed: ■ On the destination computer, click Start, and then click Run. ■ Type dcpromo /adv, and then click OK. ■ Click Next when the Active Directory Installation Wizard appears. ■ Select Additional domain controller for an existing domain, and then click Next. ■ Select From these restored backup files, enter the temporary location to which you redirected the restore of the System State data, and then click Next. ■ Complete the Active Directory Installation Wizard by following the prompts on the screen. Step 5 231Restores Installing a new Windows Server domain controller into an existing domain by using a redirected restore
- 232. Table 5-3 How to install a new Windows Server domain controller into an existing domain by using a redirected restore (continued) DescriptionStep Complete the domain controller installation.Step 6 Restart the computer that has the new domain controller.Step 7 Expire any remaining system state backup sets that you redirected to the temporary location. See “Changing the expiration date of backup sets on disk-based storage” on page 332. Step 8 Restoring Backup Exec Shadow Copy Components The Backup Exec Shadow Copy Components file system uses Microsoft’s Volume Shadow Copy Service to protect third-party application and user data on Windows computers. You can restore the items in Backup Exec Shadow Copy Components individually or together. The following items are contained in Backup Exec Shadow Copy Components: ■ Backup Exec Deduplication Disk Storage ■ Distributed File System Replication (DFSR) ■ OSISoft PI Server data When you restore domain-based Microsoft Distributed File System (DFS) namespaces, you must also restore the Active Directory to the same point-in-time. Domain-based DFS namespaces reference information that resides in the Active Directory. If you restore the namespaces without restoring Active Directory to the same point-in-time, that information is not restored and you may receive errors in the DFS Management Console. If you know which backup set, completed backup job, or storage device media contains the data that you want to restore, you can start the Restore Wizard from there. Otherwise, you can select a server and then start the Restore Wizard. See “Restoring data from a server, a backup set, a backup job, or a storage device” on page 222. To restore Backup Exec Shadow Copy Components 1 On the Backup and Restore tab, right-click the server, and then click Restore. 2 Select Shadow Copy Components, and then click Next. 3 Follow the Restore Wizard prompts to restore the data. 232Restores Restoring Backup Exec Shadow Copy Components
- 233. See “Methods for restoring data in Backup Exec” on page 220. See “Restoring System State ” on page 228. Restoring utility partitions or Unified Extensible Firmware Interface system partitions You can select utility partitions or Unified Extensible Firmware Interface (UEFI) partitions for restore. Utility partitions are small partitions that OEM vendors such as Dell, Hewlett-Packard, and IBM install on the disk. These partitions contain system diagnostic and configuration utilities. UEFI partitions are the small partitions that the operating system creates. The UEFI system partitions contain the critical system files, such as bootmgr and BOOTBCD files. Requirements for restoring utility partitions are as follows: ■ You must recreate the utility partitions before you restore any data. ■ You must have Administrator rights. ■ You cannot redirect the restore of a utility partition to another computer. ■ You can only restore the utility partitions that belong to the same vendor. For example, you cannot restore Dell utility partitions to a Compaq utility partition. ■ The size of the utility partition to which you restore the data must be equal to or greater in size than the utility partition that was backed up. If you know which backup set, completed backup job, or storage device media contains the data that you want to restore, you can start the Restore Wizard from there. Otherwise, you can select a server and then start the Restore Wizard. See “Restoring data from a server, a backup set, a backup job, or a storage device” on page 222. To restore utility partitions or UEFI system partitions 1 On the Backup and Restore tab, right-click the computer for which you want to restore utility partitions or UEFI system partitions, and then click Restore. 2 Select one of the following, and then click Next: ■ Utility partition ■ Unified Extensible Firmware Interface system partition 3 Follow the Restore Wizard prompts to restore the data. See “Methods for restoring data in Backup Exec” on page 220. 233Restores Restoring utility partitions or Unified Extensible Firmware Interface system partitions
- 234. About restoring encrypted data Encrypted backup sets are identified in the restore selection list by an icon with a lock on it. When you select encrypted data to restore, Backup Exec automatically validates the encryption key for the data. If the encryption key that was used to back up the data is still in the Backup Exec Database, then Backup Exec selects that encryption key automatically. However, if the encryption key cannot be located, Backup Exec prompts you to provide the pass phrase for the encryption key that was used to back up the data. If you enter the correct pass phrase, Backup Exec recreates the key. When you use a restricted encryption key to back up data, users other than the key owner must enter the pass phrase to restore data. See “Using encryption with Backup Exec” on page 575. See “Encryption key management” on page 578. About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec Backup Exec supports restoring NetWare SMS volume backups to non-SMS volumes. For example, the data that is backed up with Backup Exec for NetWare Servers or Novell’s SBackup can be restored to the Backup Exec server or to another network share. You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 Canceling a restore job Warning: Canceling a restore job while it is in progress may result in unusable data and can leave the disk in an unusable state. To avoid canceling a restore job, you can redirect the restore to a noncritical destination. Then, copy the data to a final destination when the job completes successfully. You should not cancel a System State restore job. Canceling a System State restore job can leave the system unusable. 234Restores About restoring encrypted data
- 235. To cancel a restore job 1 On the Job Monitor, right-click the job that you want to cancel. 2 Click Yes when you are prompted if you are sure that you want to cancel the job. See “Canceling an active job” on page 244. How Backup Exec catalogs work While backing up data, Backup Exec creates a catalog that contains information about the backup sets and about the storage device on which the backup sets are stored. When you select data to restore, Backup Exec uses the catalog information to find the restore selections and the storage devices on which they reside. When a storage device is fully cataloged, you can do the following: ■ View information on all the directories and files that are contained in each backup set. ■ Search for files to restore. Backup Exec fully catalogs each backup job. However, if the catalogs are truncated, only backup set information is listed. You cannot view files or file attributes. The amount of information in the catalog is determined by whether you choose to truncate the catalogs after a specific amount of time. Catalogs reside on the Backup Exec server and on the storage device to which you sent the backup job. To restore the data that was backed up by another installation of Backup Exec, you must first run a catalog operation on the storage device on the local Backup Exec server. The catalog for a backup job that was run on one installation of Backup Exec does not exist on another installation of Backup Exec. When you enable Granular Recovery Technology (GRT) for Exchange, SharePoint, or virtual machine backups, a catalog operation runs after the backup operation by default. The delayed catalog operation runs once every 24 hours, even if you schedule more than one GRT-enabled backup to run in the same period. Because the catalog operation runs at a different time, the GRT-enabled backup job does not block another scheduled GRT-enabled backup job from starting on time. You can schedule a delayed catalog operation. See “Configuring default options for catalogs” on page 236. See “Cataloging a storage device” on page 435. See “About cataloging tape or disk cartridge media that contains encrypted backup sets” on page 395. 235Restores How Backup Exec catalogs work
- 236. See “Configuring delayed catalog operations to improve backup performance” on page 521. Configuring default options for catalogs You can configure the default options for catalogs to specify the defaults that are best suited for your environment. See “How Backup Exec catalogs work” on page 235. To configure default options for catalogs 1 Click the Backup Exec button, click Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, click Catalog. 3 Edit any of the following options: Catalogs the media in tape drives and disk cartridges by starting with the lowest known tape number in the tape family. For example, if you don’t have the first tape, the catalog job starts with the second tape. If you uncheck this option, the catalog job begins on the tape that you specify. If you uncheck Request all media in the sequence for catalog operations, then you cannot select the option Use storage-based catalogs. This option is enabled by default. Request all media in the sequence for catalog operations 236Restores How Backup Exec catalogs work
- 237. Lets Backup Exec read the catalog information from the storage device. Storage-based catalogs allow quick cataloging of the backup sets that are not included in the Backup Exec server-based catalog. An example is when you want to catalog backup sets that another installation of Backup Exec creates. Storage-based catalogs enable backup sets to be cataloged in minutes, rather than the hours that are required with traditional file-by-file cataloging methods. To create a new catalog by having Backup Exec read each file block, clear this option. You should clear this option only if normal catalog methods are unsuccessful. Note: Symantec recommends that you always attempt to use storage-based catalogs first before clearing this option. If you uncheck Request all media in the sequence for catalog operations, then the option Use storage-based catalogs is unavailable. This option is enabled by default. The Use storage-based catalogs option must be enabled for the following restore scenarios: ■ If you use the NDMP option, this option must be enabled so that NAS server backup sets can be cataloged. See “About restoring and redirecting restore data for NDMP servers” on page 1193. ■ If you use the Advanced Disk-based Backup Option, this option must be enabled to use the true image restore capability. See “About true image restore for synthetic backups” on page 1175. ■ If you use Simplified Disaster Recovery, this option must be enabled to use the backup sets as part of an SDR recovery operation. See “Preparing computers for use with Simplified Disaster Recovery” on page 734. ■ If you back up a virtual machine to tape, this option must be enabled to perform a Granular Recovery Technology enabled restore with the backup sets. See “Granular Recovery Technology” on page 583. Use storage-based catalogs 237Restores How Backup Exec catalogs work
- 238. Retains only the header information and removes all file details and directory details after the specified amount of time. This option reduces the size of the catalogs considerably. After the catalogs have been truncated, the files and directories cannot be restored until you recatalog the storage. See “Cataloging a storage device” on page 435. The last access date is not reset when catalogs are truncated. You can perform a full restore of backup sets from truncated catalogs. This option does not apply to synthetic backup jobs. This option is not enabled by default. Truncate catalogs after Designates a path on the volume for the catalog files. If the path does not exist, you are prompted to create the path. The default path is C:Program FilesSymantecBackup ExecCatalogs. Note: Symantec recommends that you use Backup Exec Utility to change the catalog location. If you change the location using the Catalog path field, you must also manually copy the existing catalogs to the new location, and then restart the Backup Exec services. Refer to the following URL for more information: https://www.symantec.com/docs/TECH210578 Catalog path 4 Click OK. Cataloging backup sets Before you can restore or verify data, the data must be cataloged. While backing up data, Backup Exec creates a catalog that contains information about the backup sets and about the storage device on which the backup sets are stored. However, you can manually catalog backup sets at any time. To catalog backup sets 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets that you want to catalog. 2 In the left pane, click Backup Sets. 238Restores Cataloging backup sets
- 239. 3 Do one of the following: ■ To catalog a single backup set, right-click the backup set. ■ To catalog multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Click Catalog. Backup Exec runs the catalog operation. See “Backup sets ” on page 329. See “How Backup Exec catalogs work” on page 235. 239Restores Cataloging backup sets
- 240. Job management and monitoring This chapter includes the following topics: ■ How to monitor and manage jobs in Backup Exec ■ About the Job Monitor ■ About the Job History ■ Viewing the job log ■ Error-handling rules for failed or canceled jobs ■ List of job statuses in Backup Exec ■ Setting job status and recovery options How to monitor and manage jobs in Backup Exec Backup Exec provides many ways to monitor and manage your backup, restore, and storage operation jobs. Job monitoring You can monitor your active jobs and scheduled jobs from the Job Monitor tab or from the Jobs list on the Backup and Restore tab or the Storage tab. You can monitor the types of jobs that are active and scheduled, the state and status of the jobs, the schedule, and other details. The status of reports can be monitored from the Reports tab. 6Chapter
- 241. Table 6-1 Places where you can monitor jobs More informationLocation where you can monitor jobs The Job Monitor provides a single location to monitor and manage all of your backup, restore, installation, and storage operation jobs. The Job Monitor is divided into two panes. The Jobs pane displays the details of all of your active jobs and scheduled jobs. The Job Histories pane displays the details about all of your jobs that ran recently. By default, all recent jobs appear in the Job Histories pane. You can change the default by filtering the Job Histories view. Note: Report jobs do not appear on the Job Monitor. To monitor and manage report jobs, go to the Reports tab. The Job Monitor tab When you double-click a server name on the Backup and Restore tab, details for that server become available. You can view the backup and restore jobs that are scheduled and active for the selected server. You can also see the history of backup and restore jobs that were processed on the selected server. The Backup and Restore tab When you double-click a storage device name on the Storage tab, details for that storage device become available. You can view the storage operation jobs that are scheduled and active for the selected storage device. You can also see the history of storage operation jobs that were processed for the selected storage device. The Storage tab On the Reports tab, you can see the scheduled reports in the See Upcoming report group, and you can see a list of reports that completed in the See Completed report group. The Reports tab Job management Backup Exec includes many features that enable you to manage backup jobs, restore jobs, and storage operation jobs. 241Job management and monitoring How to monitor and manage jobs in Backup Exec
- 242. You can manage jobs in the following ways: ■ Edit scheduled jobs. ■ Delete scheduled jobs. ■ Cancel active jobs. ■ Change the priority of scheduled jobs. ■ Run a scheduled job immediately. ■ Hold a job or the job queue. ■ Run a test of the backup job. ■ View the job activity details, such as job statistics and system information, for an active job. ■ View the history of a job. See “Editing backup definitions” on page 194. See “Viewing job activity details for active jobs” on page 244. See “Deleting scheduled jobs” on page 250. See “Canceling an active job” on page 244. See “Changing the priority for a scheduled job” on page 249. See “Running a scheduled job immediately” on page 248. See “Holding jobs” on page 245. See “Holding the job queue” on page 247. See “Running a test run job manually” on page 214. About the Job Monitor The Job Monitor provides a single location to monitor and manage all of your backup, restore, installation, and storage operation jobs. The Job Monitor is divided into two panes. The Jobs pane displays the details of all of your active jobs and scheduled jobs. The Job History pane displays the details about all of your jobs that ran recently. By default, all recent jobs appear in the Job History pane. You can change the default by filtering the Job History view. Note: Report jobs do not appear on the Job Monitor. To monitor and manage report jobs, go to the Reports tab. 242Job management and monitoring About the Job Monitor
- 243. You can manage active and scheduled jobs in the Jobs pane on the Job Monitor in the following ways: ■ Edit scheduled jobs. ■ Delete scheduled jobs. ■ Cancel active jobs. ■ Change the priority of scheduled jobs. ■ Run a scheduled job immediately. ■ Hold a job or the job queue. ■ Run a test backup job. ■ View the job activity details for an active job. ■ View the history of a job. In the Job History pane of the Job Monitor, you can manage completed jobs in the following ways: ■ Run the job again immediately. ■ View the job log. ■ Delete the job. ■ View the job history details. ■ Enable error-handling rules. ■ Duplicate job histories. ■ Run a verify backup job. ■ Edit the settings for a backup job. From the Job Monitor, you can restore data from the backup sets of a completed backup job. Additionally, you can view the backup calendar. See “How to monitor and manage jobs in Backup Exec” on page 240. See “Running a test run job manually” on page 214. See “Duplicating backup sets or a job history manually” on page 209. See “Verifying backed up data manually” on page 215. See “Editing backup definitions” on page 194. 243Job management and monitoring About the Job Monitor
- 244. Viewing job activity details for active jobs When a job is running, you can view details for the job, such as the percent complete, job rate, and byte count. To view details for active jobs 1 Do one of the following: Select the Job Monitor tab.To view job activity from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device on which the job is running. ■ In the left pane, click Jobs. To view job activity from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then click View Job Activity. Canceling an active job You can cancel a job that is in progress. If the job is scheduled, it runs again at the next scheduled time. It may take several minutes for a job to cancel. While Backup Exec processes the cancelation of a job, the Cancel Pending status appears in the Job Status column. To cancel an active job 1 Do one of the following: Select the Job Monitor tab.To cancel the job from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is running. ■ In the left pane, click Jobs. To cancel the job from the Backup and Restore tab or the Storage tab 2 Right-click the active job that you want to cancel, and then click Cancel. 3 Click Yes to confirm the cancelation of the job. 244Job management and monitoring About the Job Monitor
- 245. See “List of job statuses in Backup Exec” on page 264. Holding jobs Active and scheduled jobs can be placed on hold. When you place an active job on hold, the job continues to run until it is complete. However, the next scheduled occurrence of that job is placed on hold. When you place a job on hold, the status in the Job Status column changes to On Hold. To hold jobs 1 Do one of the following: Select the Job Monitor tab.To place a job on hold from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is running or is scheduled to run. ■ In the left pane, click Jobs. To place a job on hold from the Backup and Restore tab or the Storage tab 2 Do one of the following: Select the job from the list of jobs, and then in the Jobs group, click Hold. Then select Hold Job. To hold a single job In the Jobs group, click Hold, and then click Hold All Active Jobs. You may need to click Yes to confirm that you want to hold all of the active jobs. Note: This option is available only from the Job Monitor. To hold all active jobs In the Jobs group, click Hold, and then click Hold All Scheduled Jobs. You may need to click Yes to confirm that you want to hold all of the scheduled jobs. Note: This option is available only from the Job Monitor. To hold all scheduled jobs See “Removing the hold on jobs” on page 246. 245Job management and monitoring About the Job Monitor
- 246. Removing the hold on jobs You can remove the hold on a job at any time. When you remove the hold on a job, the status in the Job Status column changes to the job's original status, such as Active or Scheduled. To remove the hold on jobs 1 Do one of the following: Select the Job Monitor tab.To remove the hold on jobs from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is on hold. ■ In the left pane, click Jobs. To remove the hold from jobs from the Backup and Restore tab or the Storage tab 2 Do one of the following: Select the job from the list of jobs, and then in the Jobs group, click Hold. Then select Hold Job to remove the check mark. Note: If the job that you want to hold is part of a backup definition, you may need to double-click the job definition to view the job. To remove the hold on a single job In the Jobs group, click Hold, and then click Hold All Active Jobs to remove the check mark. You may need to click Yes to confirm that you want to remove the hold on all of the active jobs. Note: This option is available only from the Job Monitor. To remove the hold on all active jobs In the Jobs group, click Hold, and then click Hold All Scheduled Jobs to remove the check mark. You may need to click Yes to confirm that you want to remove the hold on all of the scheduled jobs. Note: This option is available only from the Job Monitor. To remove the hold on all scheduled jobs 246Job management and monitoring About the Job Monitor
- 247. See “Holding jobs” on page 245. Holding the job queue You can place the entire job queue on hold to make changes to your environment. The server is paused to place the job queue on hold. When the job queue is on hold, only active jobs continue to run unless you choose to cancel them. No other jobs can run until the job queue is taken off hold. To place the job queue on hold 1 Do one of the following Select the Job Monitor tab.To place the job queue on hold from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is running or scheduled to run. ■ In the left pane, click Jobs. To place the job queue on hold from the Backup and Restore tab or the Storage tab 2 In the Jobs group, click Hold, and then click Hold Job Queue. 3 Click Yes. 4 If active jobs are running, select the active jobs that you want to cancel, and then click OK. See “Removing the hold on the job queue” on page 247. Removing the hold on the job queue When you remove the hold on the job queue, the server is unpaused and jobs then run according to the schedule. To remove the hold on the job queue 1 Do one of the following Select the Job Monitor tab.To remove the hold on the job queue from the Job Monitor tab 247Job management and monitoring About the Job Monitor
- 248. Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job queue is on hold. ■ In the left pane, click Jobs. To remove the hold on the job queue from the Backup and Restore tab or the Storage tab 2 In the Jobs group, click Hold, and then click Hold Job Queue to remove the check box. See “Holding the job queue” on page 247. Running a scheduled job immediately You can run a scheduled job immediately. The job will also run on the next scheduled occurrence. To run a scheduled job immediately 1 Do one of the following: Select the Job Monitor tab.To run the job from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is scheduled to run. ■ In the left pane, click Jobs. To run the job from the Backup and Restore tab or the Storage tab 2 Right-click the scheduled job that you want to run, and then click Run Now. Note: If the scheduled job is part of a backup definition, you may need to double-click the job definition to view the scheduled job. See “Changing the priority for a scheduled job” on page 249. See “Deleting scheduled jobs” on page 250. 248Job management and monitoring About the Job Monitor
- 249. Changing the priority for a scheduled job The priority determines the order that jobs run. If two jobs are scheduled to run at the same time, the priority you set determines which job runs first. The priority is changed for all occurrences of the scheduled job. The priority of the job is displayed in the Priority column in the Jobs list. This option is most useful if there are limited storage devices in your environment, but you want certain jobs to have priority access to the devices. A ready job that has a higher priority runs before a ready job that has a lower priority. A ready job that has a higher priority also runs before a ready job that has an earlier scheduled start time. If multiple jobs are ready to run but must wait for a storage device to become available, then Backup Exec determines which jobs to run first. Backup Exec reviews the job priority and the scheduled start time of the job. You can set the job priority when you do the following tasks: ■ Select storage options when you create or edit a backup job ■ View scheduled jobs in the Job Monitor tab ■ View a server's scheduled jobs from the Jobs pane on the Backup and Restore tab If you change the job priority in the storage options or on the Jobs pane, you can choose from the following levels of priority: ■ Highest ■ High ■ Medium ■ Low ■ Lowest If you change the job priority from the Job Monitor, you can only increase or decrease the job priority. You cannot specify a level. To change the priority for a scheduled job 1 Do one of the following: Select the Job Monitor tab.To change the job's priority from the Job Monitor tab 249Job management and monitoring About the Job Monitor
- 250. Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is scheduled to run. ■ In the left pane, click Jobs. To change the job's priority from the Backup and Restore tab or the Storage tab 2 Right-click the scheduled job, and then click Change Priority. Note: If the job is part of a backup definition, you may need to double-click the job definition to view the job. 3 Select the new priority. Deleting scheduled jobs Deleting a scheduled job removes all scheduled occurrences of the job. To delete only the occurrence of a scheduled job on a specific date, you can edit the schedule to remove that date. Note: If a backup definition includes more than one type of job, then you cannot use the Delete option to delete an individual job from the definition. Instead, you must edit the job definition to remove the scheduled job. To delete a scheduled job 1 Do one of the following: Select the Job Monitor tab.To delete a scheduled job from the Job Monitor tab 250Job management and monitoring About the Job Monitor
- 251. Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job is scheduled to run. ■ In the left pane, click Jobs. To delete a scheduled job from the Backup and Restore tab or the Storage tab 2 Right-click the scheduled job, and then click Delete. Note: If the job is part of a backup definition, you may need to double-click the job definition to view the job. 3 Click Yes. See “How to monitor and manage jobs in Backup Exec” on page 240. About the Job History The Job History displays a list of completed and failed backup, restore, and storage operation jobs. The Job History appears on the lower pane of the Job Monitor tab. It also appears when you select a server on the Backup and Restore tab, and when you select a storage device on the Storage tab. From the Job History, you can do any of the following: ■ View the job log. ■ Delete a job. ■ Rerun a job. ■ Duplicate the data from a completed backup job. ■ Verify a backup job. ■ Enable error-handling rules for a failed job. See “Running a job from the Job History” on page 253. See “Viewing the job log ” on page 254. See “Deleting a job from the Job History” on page 252. See “Enabling an error-handling rule for a failed job” on page 262. See “Duplicating backup sets or a job history manually” on page 209. See “Verifying backed up data manually” on page 215. 251Job management and monitoring About the Job History
- 252. Viewing the history of a job The job history shows statistics for all occurrences of a job. To view the history of a job 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To view the history of a job from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To view the history of a job from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then click View Job History. Deleting a job from the Job History You can delete a job from the Job History, or have Backup Exec automatically delete the job history using database maintenance. If you delete a job, it is removed from the computer and cannot be recovered. To delete a job from the Job History 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To delete a job from the Job History on the Job Monitor tab 252Job management and monitoring About the Job History
- 253. Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To delete a job from the Job History on the Backup and Restore tab or the Storage tab 2 Right-click the job that you want to delete, and then click Delete. You can select multiple jobs by selecting a job, and then pressing the <Ctrl> or <Shift> keys while you click other jobs that you want to select. This lets you perform tasks such as Delete on more than one job at a time, as long as the jobs are of similar type. You can delete up to 2500 jobs from the Job History. If you attempt to delete more than 2500 jobs, you are prompted to continue with the deletion. 3 Click Yes. See “About the Job History” on page 251. See “Configuring database maintenance and security” on page 552. Running a job from the Job History After a job runs, the job moves to the Job History. You can run a completed job again from the Job History. To run a job from the Job History 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To run a job from the Job History on the Job Monitor tab ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To run a job from the Job History on the Backup and Restore tab or the Storage tab 2 Right-click the job that you want to run, and then click Run Now. See “About the Job History” on page 251. 253Job management and monitoring About the Job History
- 254. Viewing the job log You can view detailed job-related properties for each job that has been processed. You can save a copy of the job log to a location of your choice or you can print the job log. To view the job log 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To view the job log from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To view the job log from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then select View Job Log. 3 Do any of the following: ■ Click Find to search for a particular word, phrase, or file name. ■ Click Save As to save a copy of the job log to the location of your choice. ■ Click Print to print the job log. Finding text in the job log You can search for specific text in the job log. Backup Exec searches only the sections that are expanded. To search the entire job lob, you should select the Expand All option. To find text in the job log 1 Do one of the following: On the Job Monitor tab, in the Job Histories pane, locate the job for which you want to search the job log. To find text in the job log from the Job Monitor tab 254Job management and monitoring Viewing the job log
- 255. Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To find text in the job log from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then click View Job Log. 3 Click Find. 4 In the Find field, type the text that you want to find. 5 Select any of the following additional options to facilitate your search: Check this check box if you want Backup Exec to search for the whole word you typed. If you do not select this option, Backup Exec finds the text that includes part of the word. For example, if you search for the word "file" and do not select this option, Backup Exec finds all occurrences of "file", "files", "filed", and any other words that contain "file". If you do select this option, Backup Exec finds only the occurrences of "file". Match whole word only Check this check box if you want Backup Exec to search for words using the exact capitalization that you typed. For example, if you search for the word "File" and select this option, Backup Exec finds all occurrences of "File", but does not find any occurrences of "file". Match case Check this check box if you want Backup Exec to highlight the text that matches the search criteria. The option is selected by default. Highlight all matches 6 Click Next to find the next occurrence of the text. See “Viewing the job log ” on page 254. 255Job management and monitoring Viewing the job log
- 256. Printing the job log If your Backup Exec server is connected to a printer, you can print the job log for a completed job. To print the job log 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To access the job log from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To access the job log from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then select View Job Log. 3 Click Print. 4 Select the printer that you want to use, and then click Print. See “Saving the job log” on page 256. Saving the job log Backup Exec provides the ability to save the job log to a location on your hard drive or network. In addition, you can select the format in which to save the file; as a complete webpage, a web archive, an HTML-only webpage, or a text file. To save the job log 1 Do one of the following: On the Job Monitor tab, locate the job in the Job Histories pane. To access the job log from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To access the job log from the Backup and Restore tab or the Storage tab 2 Right-click the job, and then select View Job Log. 256Job management and monitoring Viewing the job log
- 257. 3 Click Save As. 4 Select the location where you want to save the job log. See “Printing the job log” on page 256. Linking from the job log to the Symantec Technical Support website Errors that are reported in the job log have a unique code, called a Unique Message Identifier (UMI). These codes contain hyperlinks that you can click to go to the Symantec Technical Support website. From the website, you can access technical notes and troubleshooting tips that are related to a specific message. UMI codes establish unique message codes across all Symantec products. Some alerts also contain a UMI. For example, if a Warning alert appears when a job fails, the alert includes the UMI code. You can create or enable an error-handling rule for errors. These rules let you set options to retry or stop a job when the error occurs. See “Error-handling rules for failed or canceled jobs” on page 259. To link from the job log to the Symantec Technical Support website 1 Do one of the following: Select the Job Monitor tab.To link to the job log from the Job Monitor tab Do the following: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To link to the job log from the Backup and Restore tab or the Storage tab 2 Right-click a job, and then select View Job Log. 3 Scroll to the Job Completion Status section. 4 Click the UMI code, which appears as a blue hyperlink. How to use job logs with vertical applications The Backup Exec Administration Console provides a view of the job logs in HTML format. If necessary, you can convert the job logs to a text format for use with vertical applications. To convert a job log file to a text format, load the Backup Exec Management Command Line Interface, and then type the following at a command prompt: 257Job management and monitoring Viewing the job log
- 258. Get-BEJobLog "pathnamejob log filename" For example, to display the job log C:program filesSymantecBackup ExecDatabex00001.xml in text format to the command prompt, you would type: Get-BEJobLog "C:program filesSymantecBackup ExecDatabex00001.xml" To redirect the job log to a file, you would type one of the following: Get-BEJobLog "C:program filesSymantecBackup ExecDatabex00001.xml" > bex00001.txt See “Viewing the job log ” on page 254. Configuring default job log options You can configure default options for job logs that specify the amount of detail you want to include in the completed job log. For the jobs that produce large job logs, you may want to reduce the amount of detail in the job log. The size of the job log increases proportionally to the level of detail that is configured for the job log. To configure default job log options 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, click Job Logs. 3 Select the appropriate options. Select this option to include the following information in the job log: ■ Job name ■ Job type ■ Job log name ■ Backup Exec server name ■ Storage device ■ Starting date and time ■ Errors encountered ■ Ending date and time ■ Completion statistics This option also includes the names of files that were skipped, the name of the media set, the backup type and results of the verify operation if one was performed. Summary information only 258Job management and monitoring Viewing the job log
- 259. Select this option to include summary information and a list of all processed subdirectories in the job log. Summary information and directories processed Select this option to include summary information, processed subdirectories, and a list of all the file names that were processed in the job log. Summary information, directories, and files processed Select this option to include summary information, processed subdirectories, a list of all the file names and their attributes in the job log. This option increases the job log size significantly. Summary information, directories, files, and file details Enter a prefix to add to the job logs that are processed. The default prefix is BEX. The job log file name consists of Prefix_ServerName_Count. Prefix is the label that you enter in this field, ServerName is the name of the Backup Exec server that ran the job, and Count is the number of job logs that this job has produced Prefix for the job log file name Select this option to attach the job logs in an HTML format when an email notification is sent. Attach job logs as HTML Select this option to attach the job logs in a text format when an email notification is sent. Attach job logs as text Shows the current location of the job log. To change the path you can use BE Utility. Job log path See “Viewing the job log ” on page 254. Error-handling rules for failed or canceled jobs You can enable default rules or create custom rules to set retry options and final job disposition for failed or canceled jobs. Retry options let you specify how often to retry a job if it fails and the time to wait between retry attempts. The final job disposition lets you either place the job on hold until you can fix the error, or reschedule the job for its next scheduled service. 259Job management and monitoring Error-handling rules for failed or canceled jobs
- 260. Each default error-handling rule applies to one category of errors, such as Network Errors or Security Errors. Default error-handling rules are disabled by default, so you must edit a rule and enable the rules that you want to use. You cannot delete default error-handling rules, add specific error codes to a category, or add new error categories. Before the error-handling rules will apply, the final error code must be in an error category that is associated with a rule, and the rule must be enabled. To apply an error-handling rule for a specific error code that is in an error category, you can create a custom error-handling rule. You can select up to 28 error codes in an error category that a custom error-handling rule can apply to. You can also add an error code to an existing custom rule. A custom error-handling rule named "Recovered Jobs" is created when Backup Exec is installed and is enabled by default. This rule applies retry options and a final job disposition to jobs that fail and that are not scheduled to run again. See “Creating a custom error-handling rule” on page 260. If both a custom error-handling rule and a default error-handling rule apply to a failed job, the settings in the custom rule are applied to the job. Note: If the server on which Backup Exec is installed is in a cluster environment, the Cluster Failover error-handling rule is displayed on the list of error-handling rules. This rule is enabled by default. See “About the cluster failover error-handling rule” on page 263. Creating a custom error-handling rule You can create custom rules to set retry options and final job disposition for failed or canceled jobs. See “Error-handling rules for failed or canceled jobs” on page 259. To create a custom error-handling rule 1 Click the Backup Exec button, select Configuration and Settings, and then select Error-handling rules. 2 Click New. 3 Check Enable error-handling rule. 4 In the Name field, type a name for this rule. 5 In the Error category list, select the category of error that you want this rule to apply to. 260Job management and monitoring Error-handling rules for failed or canceled jobs
- 261. 6 Under Available errors, check the check box of the error code that you want this rule to apply to. You can select up to 28 error codes. 7 If you want Backup Exec to retry the job after it fails, check Retry job, and then enter the number of times you want to retry the job and how often you want to retry the job. The maximum number of retries is 99. The maximum retry interval is 1440 minutes. 8 Under Final job disposition, select the way you want to handle the job after the maximum number of retries. If you choose the option to place the job on hold until the error condition is cleared manually, you must manually remove the hold from the job after you manually clear the error condition. 9 Click OK. See “Custom error-handling rule for recovered jobs” on page 262. See “About the cluster failover error-handling rule” on page 263. Enabling or disabling error-handling rules Follow these steps to enable or disable specific error-handling rules. To enable or disable error-handling rules 1 Click the Backup Exec button, select Configuration and Settings, and then select Error-handling rules. 2 Select the rule that you want to enable or disable, and then click Edit. 3 Do one of the following: ■ To enable the rule, check Enable error-handling rule. ■ To disable the rule, clear the Enable error-handlng rule check box 4 Click OK. See “Error-handling rules for failed or canceled jobs” on page 259. Deleting a custom error-handling rule A custom error-handling rule can be deleted at any time. A default error-handling rule cannot be deleted. 261Job management and monitoring Error-handling rules for failed or canceled jobs
- 262. To delete a custom error-handling rule 1 Click the Backup Exec button, select Configuration and Settings, and then select Error-handling rules. 2 Select the custom rule that you want to delete, and then click Delete. 3 Click Yes to confirm that you want to delete the rule. See “Error-handling rules for failed or canceled jobs” on page 259. Enabling an error-handling rule for a failed job You can create custom rules to set retry options and final job disposition for failed jobs. To enable an error-handling rule for a failed job 1 Do one of the following: Select the Job Monitor tab.To enable an error-handling rule from the Job Monitor tab On the Backup and Restore tab or the Storage tab, in the left pane, select Job History. To enable an error-handling rule from the Backup and Restore tab or the Storage tab 2 Right-click the failed job, and then select Error Handling. 3 Check the Enable error-handling rule check box. 4 Complete the remaining options for this rule. Custom error-handling rule for recovered jobs Backup Exec includes a custom error-handling rule called "Recovered Jobs" to recover the jobs that failed with specific errors. This rule is created when Backup Exec is installed and is enabled by default. The retry options for this rule are to retry the job twice, with an interval of five minutes between the retry attempts. The final job disposition is to place the job on hold until you have manually cleared the error condition. The following table describes the error codes that are selected by default for the Recovered Jobs custom error-handling rule. 262Job management and monitoring Error-handling rules for failed or canceled jobs
- 263. Table 6-2 Error codes for recovered jobs custom error-handling rule DescriptionError code The displayed error message is: The Backup Exec job engine system service is not responding. 0xE00081D9 E_JOB_ENGINE_DEAD The displayed error message is: The local job has been recovered. No user action is required. 0xE0008820 E_JOB_LOCAL RECOVERNORMAL The displayed error message is: The remote job has been recovered. No user action is required. 0xE000881F E_JOB_REMOTE RECOVERNORMAL The displayed error message is: Job was recovered as a result of Backup Exec RPC service starting. No user action is required. 0xE0008821 E_JOB_STARTUP RECOVERY Note: If the Central Admin Server Option is installed, additional error codes are selected. See “Error-handling rules for failed or canceled jobs” on page 259. See “About the cluster failover error-handling rule” on page 263. About the cluster failover error-handling rule If the Backup Exec server is installed in a cluster environment, the cluster failover error-handling rule is displayed on the list of error-handling rules. This rule is enabled by default. You cannot configure any options for this rule. You can only enable or disable the cluster failover error-handling rule. The cluster failover error-handling rule and the Enable checkpoint restart option in Advanced Open File backup options work together to enable you to resume jobs from the point of failover. The Enable checkpoint restart option is dependent on the cluster failover error-handling rule; if you disable the rule, the option is automatically disabled to match the rule’s setting See “Error-handling rules for failed or canceled jobs” on page 259. 263Job management and monitoring Error-handling rules for failed or canceled jobs
- 264. List of job statuses in Backup Exec Backup Exec displays various job statuses for active, completed, and scheduled jobs. See the section called “Active job statuses” on page 264. See the section called “Completed job statuses” on page 265. See the section called “Scheduled job statuses” on page 267. Active job statuses The following statuses may appear for the jobs that are active: Table 6-3 Active job statuses DescriptionStatus The operation is underway.Running The job has been initiated, but Backup Exec is actively looking for a suitable drive or media. Queued Backup Exec cannot process the Cancel request immediately. This status is displayed until the job is actually canceled. The job is then displayed in the job history with a status of Canceled. Cancel Pending The media is being loaded and positioned on the target device. Loading Media This status can indicate any or all of the following: ■ Backup Exec is calculating the amount of data that will be backed up, if the Display progress indicators for backup jobs option is enabled in the Preferences section of Backup Exec settings. See “Changing the default preferences” on page 550. ■ Backup Exec is waiting for a pre-command or a post-command to complete. ■ Backup Exec is retrieving the set maps and is positioning the tape to the append point location for an append job. Pre-processing Backup Exec is processing a snapshot operation.Snapshot processing The device that the job was sent to is paused. See “Pausing and unpausing a storage device” on page 438. Device Paused 264Job management and monitoring List of job statuses in Backup Exec
- 265. Table 6-3 Active job statuses (continued) DescriptionStatus The Backup Exec server is paused. See “Pausing or resuming a managed Backup Exec server” on page 1158. Server Paused The Backup Exec services have become unresponsive. See “Setting job status and recovery options” on page 269. Stalled You must insert media for the job to continue.Media Request Communications between the managed Backup Exec server and the central administration server have not occurred within the configured time threshold. See “Enabling or disabling communications between the managed Backup Exec server and the central administration server” on page 1146. Communication Stalled No communication about jobs is being received at the central administration server from the managed Backup Exec server. The configured time threshold has been reached. See “Enabling or disabling communications between the managed Backup Exec server and the central administration server” on page 1146. No Communication Backup Exec is running a consistency check of the databases before backup. Consistency check Backup Exec is updating the catalog information.Updating Catalogs Completed job statuses The following statuses may appear for the jobs that were completed: Table 6-4 Job completion status DescriptionStatus The job completed without errors.Successful The job completed, but some files were in use, skipped, or corrupted. Completed with exceptions 265Job management and monitoring List of job statuses in Backup Exec
- 266. Table 6-4 Job completion status (continued) DescriptionStatus The job ran in a cluster environment and was active on one computer, and then the cluster performed a failover and the job was restarted on another computer in the cluster. Two separate sets of job history are available when a job is failed over. The first job history includes the failed over status and the second job history includes the status that is appropriate for the completed job. Failed over The status is the same as the failed over status, however the Enable checkpoint restart option was selected. Resumed The administrator terminated the operation as it was running.Canceled The Cancel the job if it is still running x hours after its scheduled start feature was enabled and the job was not completed within the specified timeframe. Canceled, timed out The operation took place, but one or more significant errors occurred. The job log should indicate what caused the errors so that you can decide if you want to run the job again. For example, if a job failure occurred due to a lost connection during job processing, you could choose to resubmit the job when the connection is restored. If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data that was written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations. A failed job has an error message in the Errors section of the job log with a link to the Symantec Technical Support website. A job may fail for the following reasons: ■ The storage device that was selected for the job was not available when the job ran. ■ The logon account that was used in the backup job is incorrect. Verify that the logon account information is valid for the resource being backed up. ■ A problem occurred with the storage device when the job ran. ■ The computer being backed up was shut down before or during the backup job. Failed The job was active when the status of the managed Backup Exec server was changed from Communication Stalled to No Communication. The custom error-handling rule for Recovered Jobs was applied to the job. Recovered 266Job management and monitoring List of job statuses in Backup Exec
- 267. Table 6-4 Job completion status (continued) DescriptionStatus The job did not run during the scheduled time window. The job is rescheduled to run based on the time window that you configured. Missed Scheduled job statuses The following statuses may appear for the jobs that are scheduled: Table 6-5 Scheduled job statuses DescriptionStatus The scheduled job will not run because of a scheduling issue. See “Setting default schedule options for rule-based jobs and run now jobs” on page 544. Invalid Schedule The job was ready to be sent for processing, but the time window for the job closed. See “Setting default schedule options for rule-based jobs and run now jobs” on page 544. Not in time window The job has been placed on hold.On Hold A temporary state that displays when Backup Exec is applying an error-handling rule that is enabled to retry the job. See “Custom error-handling rule for recovered jobs” on page 262. Queued 267Job management and monitoring List of job statuses in Backup Exec
- 268. Table 6-5 Scheduled job statuses (continued) DescriptionStatus The job is ready to run, but cannot for one of the following reasons: ■ Internal error. No devices are available, but the cause is unknown. ■ Invalid job. The job type is unknown; there may be an internal error or the database is corrupted. ■ Invalid target. This type of storage device no longer exists. ■ Backup Exec server not available. ■ No license for option name. A license must be purchased and installed on the Backup Exec server. ■ No Backup Exec servers are available. ■ No Backup Exec servers are available in Backup Exec server pool. ■ Specified destination storage device pool is empty. ■ Specified destination device is not in Backup Exec server pool. ■ Specified destination device not on local Backup Exec server. ■ Specified destination storage device pool on local Backup Exec server is empty. ■ The destination storage device cannot be a storage pool. ■ The destination storage device cannot be a Backup Exec server. ■ Another job is running in the system that is blocking execution of this job. This job will run after the other job completes. ■ Invalid input. ■ Incompatible Resumes. ■ No server license available. ■ No multi-server license available. ■ No Windows license. ■ No Windows server. ■ Need local Backup Exec server. ■ Local server is not a Backup Exec server. ■ No idle storage devices are available. ■ No eligible storage devices within the storage pool are available. ■ Blocked by an active, linked duplicate backup sets job. Ready 268Job management and monitoring List of job statuses in Backup Exec
- 269. Table 6-5 Scheduled job statuses (continued) DescriptionStatus The job is scheduled to run in the future. The scheduled jobs that are linked to another job, such as a job to duplicate backup sets, will not display a scheduled job status. Scheduled The job is ready, but the Backup Exec server has been paused. No jobs are dispatched while the Backup Exec server is paused. See “Pausing or resuming a managed Backup Exec server” on page 1158. Server Paused A state that the scheduled job transitions through as it is being sent for processing. To Be Scheduled The job cannot run because one or more of the settings in the backup definition cannot be satisfied. The Rule Blocked status may appear for any of the following reasons: ■ A job cannot run until another job has completed. Example: If you added a duplicate stage to a backup definition and the source backup job has not yet completed, the duplicate job is blocked until the source backup job completes. Example: If a job definition includes both a full backup and an incremental backup, the full backup must run first. If you try to run the associated incremental backup job before the full backup job has completed, the incremental backup job is blocked until the full backup completes. ■ A server for a job cannot be changed until the linked jobs complete. ■ A server for a job cannot be changed until another job completes. ■ A job cannot run because multiple jobs are scheduled to run at the same time. Rule Blocked Setting job status and recovery options If the Backup Exec services become unresponsive or jobs no longer run, you can set the threshold at which Backup Exec changes the status of active jobs to stalled. You can also set the threshold at which Backup Exec fails the jobs that were stalled, and then recovers them. 269Job management and monitoring Setting job status and recovery options
- 270. By lowering the amount of time before Backup Exec reaches the threshold for changing a job’s status to stalled, you can receive an earlier notification that jobs have stalled. A shorter time between the stalled and recovered thresholds also allows Backup Exec to fail and then recover the stalled jobs earlier. However, setting the thresholds too low may force a job to be recovered when it is not necessary. Backup Exec recovers the jobs by using the custom error-handling rule named Recovered Jobs. This custom error-handling rule is created and enabled when Backup Exec is installed, and specifies that stalled, failed, and recovered jobs are retried two times, with an interval of five minutes between the retries. Jobs that are stalled and then failed and recovered by Backup Exec because of unresponsive Backup Exec services are displayed differently in Backup Exec than the jobs that fail because of errors in normal daily activities. The stalled/failed/recovered jobs are not indicated in red text in the job history as other failed jobs are. Instead, these jobs are displayed in gray text with a job status of Recovered. In the job history, the error category is listed as Job Errors. The job history indicates the type of internal communication error that occurred and that the job was recovered. Based on the type of error that occurred, a log file may or may not be associated with the recovered job. To set job status and recovery options 1 Click the Backup Exec button, click Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, click Job Status and Recovery. 3 Set the thresholds for stalled and recovered jobs. Enter the amount of time you want to wait before Backup Exec changes an unresponsive job's status to Stalled. Stalled Enter the amount of time you want to wait before Backup Exec fails jobs that stalled and then recovers them. A custom error-handling rule named Recovered Jobs is applied to recovered jobs. If this rule is disabled, then any other error-handling rules that have been enabled will apply to the recovered jobs. If no error-handling rules apply to the job, then the job fails. Recovered 4 Click OK. 270Job management and monitoring Setting job status and recovery options
- 271. See “List of job statuses in Backup Exec” on page 264. See “Custom error-handling rule for recovered jobs” on page 262. 271Job management and monitoring Setting job status and recovery options
- 272. Alerts and notifications This chapter includes the following topics: ■ Alerts and notifications in Backup Exec ■ Where to find alerts in Backup Exec ■ Enabling active alerts and alert history to display on the Home tab ■ Viewing the alert history for a server or a storage device ■ Deleting an alert from alert history ■ Copying alert text to a document or email ■ Filtering alerts ■ Viewing the job log from an alert ■ Responding to active alerts ■ Clearing all informational alerts manually ■ Setting up notification for alerts ■ Configuring email or text message notification for alerts ■ Adding recipients for notification ■ Adding a recipient group for alert notifications ■ Disabling email or text message alert notification for a recipient ■ Editing recipient notification properties ■ Deleting recipients ■ Configuring alert categories 7Chapter
- 273. ■ Assigning recipients to receive notifications for specific alert categories ■ Sending a notification when a job completes ■ Disabling notifications for a specific alert category ■ Configuring default alert settings ■ Enabling or disabling pop-up alerts ■ SNMP traps for Backup Exec alerts Alerts and notifications in Backup Exec An alert is any event or condition in Backup Exec that is important enough to display a message or require a response from you. Backup Exec includes many alert categories and four alert types. Alert categories are the events or the conditions that cause alerts. Alert categories encompass many circumstances or problems that affect the system, jobs, media, or storage sources. Each alert category can include one or more events that generate an alert. For example, a Job Failed error may occur for many reasons. The alert severity levels can help you to determine which alerts need immediate attention and which alerts require a response. The following alert severity levels are used in Backup Exec: Table 7-1 Alert severity DescriptionItem Indicates the issues that require a response before the job or operation can continue. Attention required Indicates the issues that affect job processing or the integrity of your backup. These alerts cannot be disabled and cannot be configured to be cleared automatically. You must respond to them manually. Error Indicates the conditions that may or may not cause jobs to fail. You should monitor the conditions and take actions to resolve them. Warning Provides status messages for the conditions that you might want to know about. Informational By default, most alerts are enabled, which means that they appear in the Active Alerts pane when they occur. You can disable warning alerts and informational alerts by editing alert category properties. However, error alerts and attention 273Alerts and notifications Alerts and notifications in Backup Exec
- 274. required alerts cannot be disabled. You can filter the alerts so that only specific alerts appear. See “Configuring alert categories” on page 289. From the Home tab, you can view all active alerts or filter the alerts to view only specific alert severities or only the alerts that occurred on certain dates. On the Backup and Restore tab, when you double-click a server, you can see the active alerts that are specific to that server. Similarly, on the Storage tab, when you double-click a type of storage, you can see the active alerts that are specific to that storage device. Alerts remain in the Active Alerts pane until they receive a response. You can respond to an alert manually or you can configure Backup Exec to respond to some alerts automatically after a specified length of time. Depending on the alert severity, a response might not be required, such as with informational alerts. After you respond to an alert, Backup Exec moves it to the alert history. Alert history is available on the Home tab, the Backup and Restore tab, and the Storage tab. In addition, an Alert History report is available from the Reports tab. See “Alert History report” on page 645. See “Responding to active alerts” on page 280. You can configure notifications to inform recipients when alerts occur. For example, you can notify a backup administrator by email or cell phone text message when a critical alert occurs. See “Setting up notification for alerts” on page 281. To assist with hardware troubleshooting, Backup Exec displays alerts for SCSI event ID 9 (storage timeout), ID 11 (controller error), and ID 15 (storage not ready). Where to find alerts in Backup Exec You can find alerts in multiple locations on the Backup Exec Administration Console. 274Alerts and notifications Where to find alerts in Backup Exec
- 275. Table 7-2 Where alerts appear on the Backup Exec Administration Console DetailsLocation of alerts To see a list of active alerts on the Home tab, ensure that the Active Alerts check box is checked in the System Health group. To see a list of alerts in alert history, ensure that the Alert History check box is checked in the System Health group. From the Active Alerts widget on the Home page, you can respond to alerts, view the job log, clear all informational alerts, or view the details of specific alerts. Home tab On the Backup and Restore tab, active alerts are listed for each server on the list of servers. Also, when you double-click a server, you can select Active Alerts in the left pane to display all of the active alerts for that server. When you select Active Alerts in the left pane, the Show Alert History option also becomes available in the Alerts group at the top of the dialog box. Additionally, you can click the alert icon next to a server name to view the alerts for that server. Backup and Restore tab On the Storage tab, active alerts are listed for each storage device on the list of storage devices. Also, when you double-click a storage device, you can select Active Alerts in the left pane to display all of the active alerts for that device. When you select Active Alerts in the left pane, the Show Alert History option also becomes available in the Alerts group at the top of the dialog box. Additionally, you can click the alert icon next to a storage device name to view the alerts for that device. Storage tab 275Alerts and notifications Where to find alerts in Backup Exec
- 276. Table 7-2 Where alerts appear on the Backup Exec Administration Console (continued) DetailsLocation of alerts The Backup Exec status bar shows the number of active alerts for each type of alert. Double-click in the Alerts section of the Backup Exec status bar to see a list of all the active alerts and the alert history, along with details of those alerts. Backup Exec status bar If you have minimized Backup Exec, the Backup Exec icon on the Windows status bar flashes when a Backup Exec alert is triggered. When you maximize Backup Exec, the pop-up alerts appear. Windows status bar Alert pop-up windows appear when an alert is triggered. The color of the alert pop-up corresponds to the type of alert; red for error alerts, yellow for warning alerts, purple for attention-required alerts, and blue for informational alerts. If more than three alerts are available, the pop-up lists the number of alerts that are pending and the color of the pop-up indicates the most severe of the alert types. For example, if three informational alerts and two error alerts have occurred, the pop-up alert indicates that five alerts have arrived. Additionally, the pop-up color will be red to indicate that error alerts are part of the group of new alerts. You can respond to attention required alert types directly from the pop-up. Pop-up window Enabling active alerts and alert history to display on the Home tab The Active Alerts pane appears on the Home tab by default. If it does not appear, follow these steps to show the alert details. Optionally, you can also enable a history of all alerts for the server to appear on the Home tab. To view active alerts and alert history on the Home tab ◆ On the Home tab, in the System Health group, do any of the following: 276Alerts and notifications Enabling active alerts and alert history to display on the Home tab
- 277. Check the Active Alerts check box to see a list of active alerts.■ ■ Check the Alert History check box to see a list of all alerts that occurred on the server. See “Active alerts properties ” on page 277. Active alerts properties Properties for active alerts can be viewed on the Home tab or in the details for a backup job, a restore job, or a type of storage. See “Enabling active alerts and alert history to display on the Home tab” on page 276. Table 7-3 Properties for active alerts DescriptionItem Indicates the severity of the alert. The severity helps you determine how quickly you want to respond. The following alert severity levels may appear: ■ Error ■ Warning ■ Information ■ Attention Required Severity Indicates the condition that caused the alert. Categories include Database Maintenance, General Information, Device Error, or Job Failed. Category Indicates the text of the error message.Message Shows the date and time when the alert was received.Date and Time Indicates the name of the job that triggered the alert. This column is blank if a job triggered the alert, such as for general information alerts. Job Name Shows the name of the storage device on which the alert occurred.Storage Shows the name of the server on which the alert occurred.Server 277Alerts and notifications Enabling active alerts and alert history to display on the Home tab
- 278. Table 7-3 Properties for active alerts (continued) DescriptionItem Indicates the cause of the alert. Alerts can originate from one of the following sources: ■ System ■ Job ■ Storage ■ Media Source Viewing the alert history for a server or a storage device After you respond to an alert, Backup Exec moves it to the alert history. To view the alert history for a server or a storage device 1 On the Backup and Restore tab or the Storage tab, double-click the item for which you want to view the alert history. 2 In the left pane, click Active Alerts. 3 In the Alerts group, select Show Alert History. Deleting an alert from alert history Follow these steps to delete an alert from the alert history. To delete an alert from alert history 1 Access the alert history from any of the following locations: ■ In the Backup Exec status bar, double-click in the Alerts area. ■ On the Backup and Restore tab, double-click a server. In the left pane, select Active Alerts, and then click Show Alert History. ■ On the Storage tab, double-click a storage device. In the left pane, select Active Alerts, and then click Show Alert History. 2 On the Alerts dialog box, select the Alert History tab. 3 Right-click the alert that you want to remove from the alert history, and then click Delete. 4 Click Yes to confirm that you want to delete the alert. 278Alerts and notifications Viewing the alert history for a server or a storage device
- 279. Copying alert text to a document or email Backup Exec gives you the ability to copy alert information to a document, such as Notepad or Microsoft Word, or to an email. When you copy alert text to a word-processing application or to an email, Backup Exec formats the alert text in a table. Alert text that is copied to Notepad displays in plain text. To copy the text of an alert to a document or email 1 Access the list of alerts from any of the following locations: ■ In the Backup Exec status bar, double-click in the Alerts area. ■ On the Backup and Restore tab, double-click a server. In the left pane, select Active Alerts. ■ On the Storage tab, double-click a storage device. In the left pane, select Active Alerts. 2 On the Alerts dialog box, select either the Active Alerts tab or the Alert History tab, depending on whether the alert you want to copy is active or in the alert history. 3 Right-click the alert that you want to copy, and then click Copy. Note: You can also select an alert, and then press Ctrl + C as a shortcut to copy the alert text. In addition, you can copy multiple alerts by using Shift + Click or Ctrl + Click. 4 Open the document or email to which you want to copy the alert text, right-click in the document or email, and then select Paste. Filtering alerts You can filter the alerts that appear in the Active Alerts pane on the Home tab. Filters are useful when you have many alerts and you want to only view specific alert types. Alerts can be filtered by severity, time, and source. For example, you can choose to view only the error alerts that occurred during the last 12 hours for jobs. 279Alerts and notifications Copying alert text to a document or email
- 280. To filter alerts 1 On the Home tab, locate the Active Alerts pane. If the Active Alerts pane does not appear, you must enable the alert details. See “Enabling active alerts and alert history to display on the Home tab” on page 276. 2 Use any combination of the following options to filter the alerts list: ■ In the Source field, select the source of the alerts that you want to view. ■ In the Time field, select the time frame for which you want to view alerts. ■ In the Severity field, select the severity levels of the alerts that you want to view, such as Error or Warning. Viewing the job log from an alert The job log provides detailed job information, storage and media information, job options, file statistics, and job completion status for completed jobs. You can access the job log from the alerts that were generated for jobs. To view the job log from an alert 1 Access the Active Alerts pane on the Home tab, the Backup and Restore tab, or the Storage tab. 2 Right-click the alert for which you want to view the job log, and then select View Job Log. 3 Do any of the following: ■ To search for a specific word or phrase, click Find. Type the text you want to find, and then click Next. Be sure to expand all sections of the job log. The Find feature searches only the expanded sections of the job log. ■ To print the job log, click Print. To print the log, you must have a printer attached to your system and configured. ■ To save the job log as an .html file or a .txt file, click Save As and then select the file name, file location, and file type. Responding to active alerts You can respond to active alerts and continue or cancel the operation, depending on the alert condition. By default, Backup Exec displays all enabled alerts, and all 280Alerts and notifications Viewing the job log from an alert
- 281. alerts that require a response. If you have set filters, only those alerts that are selected appear in addition to any alerts that require a response. If you click Close on the alert response dialog box, the dialog box closes, but the alert remains active. To clear the alert, you must select a response such as OK, Yes, No, or Cancel. You can configure automatic responses for some alert categories. See “Configuring alert categories” on page 289. Some alerts provide a Unique Message Identifier (UMI) code. This code is a hyperlink to the Symantec Technical Support website. You can access the technical notes that are related to the alert. To respond to an active alert 1 Access the Active Alerts pane on the Home tab, the Backup and Restore tab, or the Storage tab. 2 Right-click the alert that you want to respond to, and then click Respond or Respond OK. 3 Click a response for the alert, such as Respond OK or Respond. Clearing all informational alerts manually You can configure individual alert categories to be cleared automatically after a certain period of time. Informational alerts may be generated often, so you may want to clear all informational alerts manually before the system moves them automatically. To clear all informational alerts manually 1 Access the Active Alerts pane on the Home tab, the Backup and Restore tab, or the Storage tab. 2 Right-click an informational alert, and then select Clear All Informational Alerts. See “Configuring alert categories” on page 289. Setting up notification for alerts You can configure Backup Exec to notify recipients when alerts occur. Setting up notifications for alerts is a three-step process. 281Alerts and notifications Clearing all informational alerts manually
- 282. Table 7-4 How to set up notification for alerts ActionStep Configure the method you want to use to notify the recipient. The notification methods are text message or email. See “Configuring email or text message notification for alerts” on page 282. Step 1 Add the contact information for the people or groups that you want to receive notifications. See “Adding recipients for notification” on page 284. See “Adding a recipient group for alert notifications” on page 286. Step 2 Assign each recipient to the receive notifications for specific alert categories. See “Assigning recipients to receive notifications for specific alert categories” on page 291. See “Configuring alert categories” on page 289. See “Sending a notification when a job completes” on page 291. Step 3 Configuring email or text message notification for alerts You can set up Backup Exec to send email or text messages to specified recipients when an alert occurs. Email notification requires an email account to be used as the sender. For example, you might want to use an email account for the backup administrator or the IT administrator. To configure email notifications, enter the name of the sender's mail server, the port number that the server uses, and the sender's name and email address. You can also set up Backup Exec to authenticate the emails that are sent for alerts. Table 7-5 Types of notification DescriptionNotification type Backup Exec uses SMTP for email notifications and supports authentication and Transport Layer Security (TLS). Notification email messages can be sent to Microsoft Outlook, Lotus Notes, and web-based email applications, such as Gmail or Yahoo mail. Email notification 282Alerts and notifications Configuring email or text message notification for alerts
- 283. Table 7-5 Types of notification (continued) DescriptionNotification type For a text message notification, Backup Exec attempts to format the message to contain fewer than 144 characters to meet text messaging protocol restrictions. By limiting a notification to fewer than 144 characters, the notification is more likely to be sent in a single text message instead of broken up into multiple messages. However, the text messaging service provider determines how the notifications are delivered. Text message notifications are sent in the following formats: ■ Job-related notification: Backup Exec: <Server Name> : <Job Name> : <Status> ■ Alert-related notification: Backup Exec: <Server Name> : <Alert Type> Text message notification After the sender's email information has been entered, then information about recipients can be set up. Note: An SMTP-compliant email system, such as a POP3 mail server, is required for email notifications. Note: After you configure email or text message notification, you cannot remove the configuration to disable notifications. However, you can disable notification for individual recipients. To configure Backup Exec to send email or text notification for alerts 1 Click the Symantec Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Email and Text Notification. 3 Set up the sender's email and/or text messaging information. 283Alerts and notifications Configuring email or text message notification for alerts
- 284. Do the following: ■ Under Email configuration, enter the name of the mail server, the port number that the mail server uses, and the sender's name and email address. ■ If you want to authenticate the email information that you entered, check Enable email authentication, and then enter the user name and password for the sender's email account. If you want to send alert notifications by email In Text message service provider address, enter the fully-qualified domain name of the sender's text messaging service provider. Example: If a company called "MyPhone" provides text messaging services, then enter "MyPhone.com" in the Text message service provider address field. You can override this default address for the individuals who do not use this provider. Note: Text message notification is sent as SMTP mail to an email address that is provided by a text messaging service provider. To enable notification by text message, you must enter the information about the sender's email account in the Email configuration section in addition to the fully-qualified domain name of the default text messaging service provider. If you want to send alert notifications by text message 4 Click OK. You can now add information about the recipients who need to receive alert notifications. See “Adding recipients for notification” on page 284. Adding recipients for notification Individuals or groups can be set up to receive notifications when alerts occur in Backup Exec. When you set up an individual recipient, you indicate whether the person wants to receive notifications by email, text message, or both. A group recipient contains the individual recipients that you select. Each individual within a 284Alerts and notifications Adding recipients for notification
- 285. group receives notifications by the method that is indicated for the individual; email, text message, or both. Note: Information about the notification sender must be configured before recipients can be configured. See “Configuring email or text message notification for alerts” on page 282. To add recipients for email or text message notification 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, click Add a recipient. 4 In the Name field, type the name of the recipient. 5 Select the method of notification for this recipient: Check Send notifications by email, and then enter the person's email address. To limit the number of emails that are sent within a specific amount of time, check Send no more than x emails within x minutes/hours, and then enter the maximum number of emails to send in a specific time period. To send emails to this recipient 285Alerts and notifications Adding recipients for notification
- 286. Check Send notifications by text message, and then enter the person's cell phone number and text message service provider's address. Note: If the recipient is located in a different country, you must include the exit code of the country from which the message is generated and the country code for the country in which the recipient is located. For example, the exit code for the United States is 011. The country code for Italy is 39. To send a message from the United States to a recipient that is located in Italy, enter 011 39 and the recipient's phone number. The phone number can include spaces and the following characters: ■ Opening and closing quotes ■ Period ■ Plus sign ■ Dash ■ Opening and closing parentheses ■ Forward slash To limit the number of text messages that are sent within a specific amount of time, check Send no more than x text messages within x minutes/hours, and then enter the maximum number of text messages to send in a specific time period. To send text messages to this recipient 6 Click OK. You can now assign the recipients to the alert categories for which they should receive notifications. See “Assigning recipients to receive notifications for specific alert categories” on page 291. Adding a recipient group for alert notifications Groups are configured by adding recipients as group members. A group contains one or more recipients and each recipient receives the notification message. A group can only include individuals. A group cannot contain other groups. 286Alerts and notifications Adding a recipient group for alert notifications
- 287. To add a recipient group for alert notifications 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, click Add a group. 4 In the Name field, type a unique name for this notification group. 5 To add members to the group, select recipients from the All recipients list, and then click Add to move them to the Selected recipients list. To remove members from the group, select recipients from the Selected recipients list, and then click Remove to move them to the All recipients list. 6 When you have completed the group, click OK. The group is added to the list of recipients on the Manage Recipients dialog box. See “Adding recipients for notification” on page 284. Removing a recipient from a group When you remove a recipient from a group, the recipient no longer receives the notifications that the group is configured to receive. The recipient continues to receive notifications for which the recipient is configured to receive as an individual recipient. To remove a recipient from a group 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, double-click the group that contains the recipient. 4 Under Selected recipients, select the recipient that you want to remove, and then click Remove. Disabling email or text message alert notification for a recipient If a person no longer wants to receive alert notifications, you can disable notifications for that person. 287Alerts and notifications Disabling email or text message alert notification for a recipient
- 288. Note: Instead of disabling notifications completely, you can also change the alert categories for which a recipient receives notifications. See “Disabling notifications for a specific alert category” on page 292. To disable email or text message alert notification for a recipient 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, select the name of the recipient, and then click Edit. 4 Do any of the following: ■ To disable email notifications, clear the Send notifications by email check box. ■ To disable text message notifications, clear the Send notifications by text message check box. 5 Click OK. Editing recipient notification properties You can edit the recipient notification properties at any time and change the recipient information, such as an email address or cell phone number. For a group, you can add recipients to the group or remove recipients from the group. To edit the recipient notification properties 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, select the recipient that you want to edit. 4 Click Edit. 5 Edit the properties for the selected recipient. 6 Click OK. Deleting recipients You can delete the recipients that do not want to receive notification messages. The recipient is permanently removed upon deletion. Alternatively, you can disable notification for recipients. 288Alerts and notifications Editing recipient notification properties
- 289. See “Disabling notifications for a specific alert category” on page 292. See “Disabling email or text message alert notification for a recipient” on page 287. To delete a recipient 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Notification Recipients. 3 On the Manage Recipients dialog box, select the recipient that you want to delete. 4 Click Delete. 5 Click Yes to confirm that you want to delete this recipient. 6 Click OK. Configuring alert categories Alert categories are the events or the conditions that cause alerts. Alert categories encompass many circumstances or problems that affect the system, jobs, media, or storage sources. Each alert category can include one or more events that generate an alert. For example, a Job Failed error may occur for many reasons. The alert types can help you to determine which alerts need immediate attention and which alerts require a response. You can set up alert categories to enable or disable alerts and to determine what actions should take place when an alert occurs. Most alerts are enabled by default, however the following alert categories are initially disabled: ■ Backup job contains no data ■ Job Start ■ Job Success You can disable alert categories if they are informational or warning alerts. You cannot disable alert categories if they are error or attention required alerts. Each time you change the alert configuration, it is recorded in the audit log. You can view the audit log at any time to view the changes that were made to the alert category. To configure alert category properties 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Alert Categories. 3 Under Alert category, select the alert that you want to configure. 289Alerts and notifications Configuring alert categories
- 290. 4 Under Category Properties, select the appropriate options. Enables or disables the alert. You cannot disable error and attention required alerts. Enable alerts for this category Sends the job log to the recipient that is configured for notification. If you select this Include the job log with email notifications option, be sure to select at least one recipient from the Send notification to the following recipients area at the bottom of the dialog box. Enters the alert into the Windows Event Viewer. The Windows Event log displays all the property information for the alert. Record event in the Windows Event Log If a link appears in the Windows Event log you can search the Symantec Technical Support website for information about the Event ID. Indicates whether SNMP notifications are enabled or cleared for the alert. SNMP must be installed to use this option. Send SNMP notifications Lets you enter the number of minutes, hours, or days you want the alert to remain active before it is cleared. Automatically clear after X hours/minutes Note: Error alerts cannot be cleared automatically, so this option is disabled for error alerts. Indicates the response that you want Backup Exec to send automatically when Respond with the alert is cleared. This option is available only for the Media Overwrite and Media Insert alert categories and only when the Automatically clear after x days/hours/minutes option is selected. The choices are Cancel, No, Yes, or OK. 290Alerts and notifications Configuring alert categories
- 291. Lets you select the name of a recipient to notify when this type of alert occurs. You must have recipients configured to use this option. If the recipient to which you want to send notifications is not in the list, click Manage Recipients to add the recipient. Send notification to the following recipients 5 Repeat steps 2 - 4 to configure additional alert categories. 6 Click OK to save the properties that you selected. Assigning recipients to receive notifications for specific alert categories After you have set up notification recipients, you should determine the alert categories for which they should receive notifications. For example, some recipients may only want to receive notifications about job failures and tape errors while other recipients may want to receive notifications for all error alert categories. To assign recipients to receive notifications for specific alert categories 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Alert Categories. 3 Select an alert category from the list. 4 If the category is not enabled, click Enable alerts for this category. 5 Under Send notification to the following recipients, check the check box next to the name of every recipient that needs to receive notifications for the selected alert category. 6 Click OK. Sending a notification when a job completes You can assign recipients to be notified when a job completes. Recipients must be set up before you can set up notification. To send a notification when a job completes 1 Create a new job or edit an existing job. 2 On the Backup Options dialog box, in the left pane, click Notification. 291Alerts and notifications Assigning recipients to receive notifications for specific alert categories
- 292. 3 Select the check box for each recipient that you want to notify when each type of job completes. 4 To send the job log with the notification to an email address, check Include job log in email notifications. 5 You can continue selecting other options from the Options dialog box or click OK. Notification options for jobs When you set up or edit a job, you can select recipients to receive notification when the job completes. See “Sending a notification when a job completes” on page 291. Table 7-6 Notification options for jobs DescriptionItem Shows the names of the individual and group recipients. Recipient name Indicates Recipient for an individual recipient or Group for a group recipient. Recipient type Enables Backup Exec to include a copy of the job log with the notification. This option applies only to email recipients. The maximum attachment size, in kilobytes, can be configured in the following registry key: HKLMSoftwareSymantecBackup Exec for WindowsBackup ExecServerMax Notification Attachment Size The attachment size can also be determined by the settings on your mail server. Include job log in email notifications Lets you add, edit, or delete recipients.Manage Recipients Lets you view or change the properties of a selected recipient. Properties Disabling notifications for a specific alert category When a recipient no longer needs to receive notifications for an alert category, you can stop the notification. 292Alerts and notifications Disabling notifications for a specific alert category
- 293. To disable notifications for a specific alert category 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Alerts and Notifications, and then select Alert Categories. 3 Under Alert category, select the category for which a recipient no longer needs to receive notification. 4 Under Send notifications to the following recipients, clear the check box next to the recipient for whom you want to stop notification. 5 Click OK. See “Disabling email or text message alert notification for a recipient” on page 287. Configuring default alert settings The default alert settings let you enable or disable the pop-up alerts for the four types of alerts and also to determine how long those pop-up alerts remain on the screen. If you disable the pop-up alerts for a particular alert type, that alert type still appears in the list of active alerts in other parts of the Backup Exec Administration Console, unless you have filtered that same alert type from the list of active alerts. To configure default alert settings 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Backup Exec Settings, and then select Alerts. 3 If you want to receive a reminder alert to renew your maintenance contracts, check Send an alert remider to renew your maintenance contracts on, and then enter a date. 293Alerts and notifications Configuring default alert settings
- 294. 4 In the Display pop-up alerts for the following alert types group box, check the check boxes for the types of alerts that you want to see in a pop-up alert. Clear the check boxes for the types of alerts that you do not want to see in a pop-up alert. Informational alerts provide status messages for the conditions that you might want to know about. They do not require a response and are not critical. The pop-up informational alerts have a blue color. Informational Error alerts indicate the issues that affect job processing or the integrity of your backup. You must respond to them manually. The pop-up error alerts have a red color. Error Warning alerts indicate the conditions that may or may not cause jobs to fail. You should monitor the conditions and take actions to resolve them. The pop-up warning alerts have a yellow color. Warning Attention required alerts indicate the issues that require a response before a job or an operation can continue. You can respond to this type of alert directly from the pop-up. The pop-up attention-required alerts have a purple color. Attention required 5 In the Number of seconds to display pop-up alerts field, enter the amount of time you want pop-up alerts to remain on the screen. 6 Click OK. Enabling or disabling pop-up alerts By default, Backup Exec displays informational, error, warning, and attention required alert types in pop-up alert windows when an error occurs. You can change the default settings so that you see only the types of alerts that are important to you. To enable or disable pop-up alerts 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Backup Exec Settings, and then select Alerts. 294Alerts and notifications Enabling or disabling pop-up alerts
- 295. 3 In the Display pop-up alerts for the following alert types group box, check the check boxes for the types of alerts that you want to see in a pop-up alert. Clear the check boxes for the types of alerts that you do not want to see in a pop-up alert. 4 Click OK. SNMP traps for Backup Exec alerts SNMP (Simple Network Management Protocol) is a method by which a network can be monitored from a central location. SNMP-enabled network applications like Backup Exec report to an SNMP console (a management workstation). The console receives messages (traps) from Backup Exec regarding status and error conditions. An MIB is available in the WINNTSNMPlanguage directory on the Backup Exec installation media that you can load into your SNMP console. The Object Identifier prefix for Symantec is: 1.3.6.1.4.1.1302 Backup Exec SNMP traps (messages) have unique object IDs and may include up to four strings. The following SNMP trap types are supported: Table 7-7 SNMP traps String 4String 3String 2String 1Object IDTrap Type product, version, revision machine nameBackup Exec: Application initializing 1302.3.1.1.9.1Product Start product, version, revision machine nameBackup Exec: Application terminating 1302.3.1.1.9.2Product Stop local or remote Operator name job namemachine nameBackup Exec: Job canceled by Operator 1302.3.1.2.8.2Job Canceled detail messagejob namemachine nameBackup Exec: Job failed 1302.3.1.2.8.1Job Failed detail messagejob namemachine nameBackup Exec: Storage device requires attention 1302.3.2.5.3.3Storage device requires human intervention 295Alerts and notifications SNMP traps for Backup Exec alerts
- 296. Table 7-7 SNMP traps (continued) String 4String 3String 2String 1Object IDTrap Type detail messagejob namemachine nameBackup Exec: robotic library device requires attention 1302.3.2.4.3.3Robotic library requires human intervention detail messagejob namemachine nameSDR full backup success 1302.3.1.4.2.1.2Simplified Disaster Recovery Message detail messagejob namemachine nameThe application has encountered an error 1302.3.1.1.9.3Backup Exec system error detail messagejob namemachine nameInformation on normal events 1302.3.1.1.9.4Backup Exec general information detail messagejob namemachine nameThe job succeeded 1302.3.1.2.8.3Job Success detail messagejob namemachine nameThe job succeeded, but there was a problem 1302.3.1.2.8.4Job Success with exceptions detail messagejob namemachine nameThe job has started 1302.3.1.2.8.5Job Started detail messagejob namemachine nameThe job succeeded, but there was no data 1302.3.1.2.8.6Job Completed with no data detail messagejob namemachine nameThe job has a warning 1302.3.1.2.8.7Job Warning detail messagejob namemachine nameThe device has encountered an error 1302.3.1.5.1.1.1PVL Device Error detail messagejob namemachine nameThe device has encountered a warning 1302.3.1.5.1.1.2PVL Device Warning detail messagejob namemachine nameNormal device information 1302.3.1.5.1.1.3PVL Device Information detail messagejob namemachine nameDevice requires attention 1302.3.1.5.1.1.4PVL Device Intervention 296Alerts and notifications SNMP traps for Backup Exec alerts
- 297. Table 7-7 SNMP traps (continued) String 4String 3String 2String 1Object IDTrap Type detail messagejob namemachine nameThere is an error with the media 1302.3.1.5.2.1.1PVL Media Error detail messagejob namemachine nameThere may be a problem with the media 1302.3.1.5.2.1.2PVL Media Warning detail messagejob namemachine nameNormal media information 1302.3.1.5.2.1.3PVL Media Information detail messagejob namemachine nameMedia requires attention 1302.3.1.5.2.1.4PVL Media Intervention detail messagejob namemachine nameThere is an error with the catalog 1302.3.1.5.3.1.1Catalog Error detail messagejob namemachine nameThere is a TapeAlert error 1302.3.1.5.4.1.1Tape Alert Error detail messagejob namemachine nameThere is a TapeAlert warning 1302.3.1.5.4.1.2Tape Alert Warning detail messagejob namemachine nameNormal TapeAlert information 1302.3.1.5.4.1.3Tape Alert Information detail messagejob namemachine nameThere is a database maintenance error 1302.3.1.5.5.1.1Database Maintenance Error detail messagejob namemachine nameNormal database maintenance information 1302.3.1.5.5.1.2Database Maintenance Information detail messagejob namemachine nameThere is a software update error 1302.3.1.5.6.1.1LiveUpdate Error detail messagejob namemachine nameThere is a software update warning 1302.3.1.5.6.1.2LiveUpdate Warning detail messagejob namemachine nameNormal software update information 1302.3.1.5.6.1.3LiveUpdate Information detail messagejob namemachine nameThere is an install warning 1302.3.1.5.7.1.1Install Update Warning 297Alerts and notifications SNMP traps for Backup Exec alerts
- 298. Table 7-7 SNMP traps (continued) String 4String 3String 2String 1Object IDTrap Type detail messagejob namemachine nameNormal Install information 1302.3.1.5.7.1.2Install Update Information See “Installing and configuring the SNMP system service” on page 298. Installing and configuring the SNMP system service To receive Backup Exec traps at the SNMP console, you must configure the SNMP system service with the SNMP console's IP address. SNMP starts automatically after installation. You must be logged on as an administrator or a member of the Administrators group to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure. To install the SNMP system service and configure it to send traps to the SNMP console 1 From the Windows Control Panel, select Add/Remove Programs. 2 Click Add/Remove Windows Components. 3 In Add/Remove Windows Components, select Management and Monitoring Tools, and then click Details. When selecting the component, do not select or clear its check box. 4 Select Simple Network Management Protocol, and then click OK. 5 Click Next. Installing the Windows Management Instrumentation performance counter provider Windows Management Instrumentation (WMI) is an infrastructure through which you can monitor and control system resources. Backup Exec includes performance counter and SNMP providers that can be manually installed and used with WMI. To install the WMI performance counter provider 1 Insert the Backup Exec Installation media. 2 At the command prompt, type the following: mofcomp <CD Drive Letter>:winntwmibackupexecperfmon.mof 298Alerts and notifications SNMP traps for Backup Exec alerts
- 299. Installing the Windows Management Instrumentation provider for SNMP Windows Management Instrumentation (WMI) is an infrastructure through which you can monitor and control system resources. Backup Exec includes performance counter and SNMP providers that can be manually installed and used with WMI. To use the WMI SNMP provider you must set up SNMP notification. To install the WMI SNMP provider 1 Before you install the SNMP provider that is included with Backup Exec, you must have the Microsoft SNMP provider installed on your system. For more information, refer to your Microsoft documentation. 2 Insert the Backup Exec Installation media. 3 At the command prompt, type the following: mofcomp <CD Drive Letter>:winntwmisnmpengbkupexecmib.mof Uninstalling the Windows Management Instrumentation performance counter provider You must uninstall the Windows Management Instrumentation (WMI) performance counter provider and the WMI SNMP provider separately. To uninstall the WMI performance counter provider ◆ At the command line, type: mofcomp <CD Drive Letter>:winntwmideletebackupexecperfmon.mof Uninstalling the Windows Management Instrumentation provider for SNMP You must uninstall the Windows Management Instrumentation (WMI) performance counter provider and the WMI SNMP provider separately. To uninstall the WMI SNMP provider ◆ At the command line, type: Smi2smir /d Backup_Exec_MIB 299Alerts and notifications SNMP traps for Backup Exec alerts
- 300. Disk-based and network-based storage This chapter includes the following topics: ■ Features and types of disk-based storage and network-based storage ■ Storage trending statuses for disk storage and virtual disks ■ Setting low disk space thresholds on disk-based storage ■ Configuring disk storage ■ How to restore data from a reattached or reinserted disk-based storage device ■ Configuring disk cartridge storage ■ How data lifecycle management (DLM) deletes expired backup sets on disk-based storage ■ Backup sets Features and types of disk-based storage and network-based storage Features of disk-based storage include the following: ■ Automatic discovery of locally accessible disk volumes. ■ Disk space monitoring. Alerts are sent when the disk space thresholds that you set are reached. ■ Storage trending analysis that provides predictions of low disk space for disk storage and virtual disks. 8Chapter
- 301. ■ Data lifecycle management, which automatically deletes expired backup sets and reclaims the disk space for use by new backup sets. Disk-based storage includes the following types of storage: Table 8-1 Types of disk-based storage DescriptionTypes of disk-based storage Disk storage is a location on a locally attached internal hard drive, a USB device, a FireWire device, or a network-attached storage device to which you can back up data. See “Configuring disk storage” on page 305. Disk storage Disk cartridges are a type of storage that usually remains attached to the Backup Exec server while you remove the media, such as RDX. If you are not sure if the storage has removable media, you can open the Computer folder on your Windows computer. The devices that contain removable media are listed. See “Configuring disk cartridge storage” on page 315. Disk cartridge devices Deduplication disk storage is a disk-based backup folder that is located on the Backup Exec server and which provides integrated deduplication. You must install the Symantec Backup Exec Deduplication Option to use this data-reduction strategy that optimizes storage and network bandwidth. See “About the Deduplication Option” on page 792. Deduplication disk storage Storage arrays and virtual disks are available with the Symantec Backup Exec Storage Provisioning Option, which lets you configure, manage, and monitor storage arrays that are attached to the Backup Exec server. See “Features of the Storage Provisioning Option” on page 1287. Storage arrays and virtual disks 301Disk-based and network-based storage Features and types of disk-based storage and network-based storage
- 302. Table 8-1 Types of disk-based storage (continued) DescriptionTypes of disk-based storage Vault stores are disk-based containers for the archived data that Backup Exec archives from one server. You must install the Symantec Backup Exec Archiving Option before you can use vault stores. See “About the Archiving Option” on page 1311. Vault stores Network-based storage includes NDMP servers, OpenStorage devices, and the Remote Media Agent for Linux. Table 8-2 Types of network storage DescriptionType of storage NDMP servers are network-attached storage (NAS) that supports the Network Data Management Protocol (NDMP) to allow the use of devices that are attached to the servers. See “Features of the NDMP Option” on page 1184. NDMP servers OpenStorage devices are network-attached storage that supports Symantec's OpenStorage technology. See “Configuring an OpenStorage device” on page 801. OpenStorage devices The Remote Media Agent for Linux lets you back up data from remote computers to the storage devices that are directly attached to a Linux server. You can also back up to a simulated tape library on a Linux server. See “About the Remote Media Agent for Linux ” on page 1258. Remote Media Agent for Linux See “Storage trending statuses for disk storage and virtual disks” on page 303. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. 302Disk-based and network-based storage Features and types of disk-based storage and network-based storage
- 303. See “Backup sets ” on page 329. Storage trending statuses for disk storage and virtual disks Backup Exec gathers disk usage information for disk storage and virtual disks. Backup Exec then performs statistical analysis of used disk space and free disk space. The analysis provides an estimate of how many days remain before the disk storage or virtual disk is full. Alerts provide information about whether the current disk space resources are sufficient, and can help you plan when to increase disk space. Table 8-3 Storage trending statuses DescriptionStorage trending status An estimate of the remaining number of days of storage space, based on the current usage of disk space. Remaining storage: x days This status may appear for any of the following reasons: ■ The disk storage device has not been configured long enough to get a statistical estimate. Note: After you create disk storage, Backup Exec may take approximately one month to gather enough information to provide a storage estimate. ■ This storage may be on a managed Backup Exec server that is currently in a rolling upgrade. History of used space is still being gathered The environment contains enough disk space to meet storage requirements for the next 30 days. Current storage is sufficient A storage trend cannot be obtained. Unusual increases or decreases in the amount of free disk space in the last 30 days can cause this status. No estimate due to an inconclusive history of used space 303Disk-based and network-based storage Storage trending statuses for disk storage and virtual disks
- 304. Table 8-3 Storage trending statuses (continued) DescriptionStorage trending status Backup Exec has not collected enough sample data for statistical analysis. Note: After you create disk storage, Backup Exec may take approximately one month to gather enough information to provide a storage estimate. Not enough statistical information is available See “Configuring disk storage” on page 305. See “Features of the Storage Provisioning Option” on page 1287. Setting low disk space thresholds on disk-based storage You can change the default values for three levels of low disk space conditions. When the storage device's used capacity reaches this threshold, Backup Exec sends an alert, and the data lifecycle management feature immediately searches the device for expired backup sets that it can delete. Data lifecycle management also runs on a disk cartridge if the cartridge reaches capacity during a backup job. The backup may not need to span to another cartridge if data lifecycle management deletes enough expired backup sets. If a job does span and you insert a new disk cartridge that is full, data lifecycle management deletes expired backup sets on the new cartridge. To set low disk space thresholds on disk-based storage 1 On the Storage tab, double-click the storage on which you want to change the low disk space thresholds. 2 In the left pane, click Properties. 3 Change the value on any or all of the following properties: ■ Low disk space. The first low disk space threshold at which you want Backup Exec to send an alert. The default value is 25%. ■ Low disk space - Warning. The second low disk space threshold at which you want Backup Exec to send an alert. The default value is 15%. This threshold must be less than the Low disk space threshold. 304Disk-based and network-based storage Setting low disk space thresholds on disk-based storage
- 305. ■ Low disk space - Critical. The third low disk space threshold at which you want Backup Exec to send an alert. The default value is 5%. This threshold must be less than the Warning threshold. 4 Click Apply. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Configuring disk storage Disk storage is a location on a locally attached internal hard drive, a USB device, a FireWire device, or a network-attached storage device to which you can back up data. You specify how long you want to keep the data that you back up to disk storage when you create a backup job. Backup Exec's data lifecycle management feature automatically deletes expired backup sets and reclaims the disk space. If you want to keep the backup data longer than the period that you specify when you create the backup job, you should create a duplicate backup job. A duplicate backup job can copy the backup data from the original storage device to tape media or to disk cartridge media, which you can then send for long-term or off-site storage. You can also keep the backup sets from automatically expiring by retaining the backup sets. Backup Exec then retains all dependent backup sets as well. To be eligible for configuration as disk storage, a disk must have at least 1 GB of disk space and cannot be configured as deduplication disk storage. Although you can configure disk storage and deduplication disk storage on the same disk, it is not recommended. When you create disk storage on a disk that is attached to the network, you must specify the path to an existing share. You should use the server name in the UNC path rather than an IP address. Note: Before you create the disk storage on a network share, you must give read and write permissions to the Backup Exec service account. The Backup Exec service account is on the Backup Exec server that you want to access the network share. When you create disk storage on a local disk, Backup Exec lets you specify any of the following locations: ■ Volumes with or without drive letters. You can create only one disk storage on a volume. ■ Unformatted partitions. 305Disk-based and network-based storage Configuring disk storage
- 306. Backup Exec formats and partitions the drive for you, if necessary. ■ Drives that do not have partitions. Backup Exec creates a folder named BEControl on the root of the volume. Do not delete or edit the contents of the BEControl folder, and do not copy it to other volumes or drive letters. In Windows Explorer, the backup files that the disk storage device contains display with a .bkf file extension. Each disk storage device also contains a file named changer.cfg and a file named folder.cfg, which store information about the backup files. Do not delete or edit the changer.cfg or folder.cfg files. A subfolder with a prefix of IMG in the name may display in a disk storage device. This subfolder appears if the option to enable Granular Recovery Technology (GRT) was selected for backup, or if you select the disk storage device as storage for backup data. You must use the Configure Storage wizard to create disk storage. In the Configure Storage wizard, Backup Exec provides a list of disks on which you can create disk storage. The disks do not appear in the list in the alphabetical order of the drive letter. Instead, the disk that appears first in the list has the most amount of disk space. You can select any disk that you want, but the disk that Backup Exec recommends for use appears at the top of the list. The disk that you use as the system drive always appears last in the list. Symantec recommends that you do not configure disk storage on the system drive. Note: If Windows data deduplication is enabled on the disk storage volume, Backup Exec excludes the backup data in the folder BEData from deduplication, unless the BEData folder already exists. Backup Exec must exclude backup data from deduplication for you to use Simplified Disaster Recovery (SDR) to perform a local recovery of the Backup Exec server. If Windows data deduplication is enabled on the disk storage volume, local disaster recovery using SDR fails. The Windows Preinstallation Environment (Windows PE) that SDR uses cannot read the files that Windows data deduplication processes. To configure disk storage 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Do one of the following: Click Disk-based storage, and then click Next. If the Central Admin Server Option is not installed 306Disk-based and network-based storage Configuring disk storage
- 307. Do the following in the order listed: ■ Select the Backup Exec server on which you want to configure storage, and then click Next. ■ Click Disk-based storage, and then click Next. If the Central Admin Server Option is installed 3 Click Disk storage, and then click Next. 4 Enter a name and description for the disk storage device, and then click Next. 5 Specify if you want to create the disk storage device on a local disk or on a network share, enter the location or path, and then click Next. 6 Specify how many write operations to let run at the same time on this disk storage device, and then click Next. 7 Review the summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the disk storage device See “Changing the location of a disk storage device” on page 307. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Changing the location of a disk storage device You can change the location of an existing disk storage device. You must have a different volume available to which you can move the files in the BEData folder. Note: When you copy files from the original disk storage device to the new location, do not copy .cfg files. 307Disk-based and network-based storage Configuring disk storage
- 308. To change the location of a disk storage device 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Click Disk storage, and then click Next. 3 Enter a different name and description than the original disk storage device, and then click Next. 4 Specify a different drive letter than the original disk storage device, and then click Next. 5 Specify the number of write operations that you want to let run at the same time on this disk storage device, and then click Next. 6 Review the summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the disk storage device 7 In Windows Explorer, copy and paste the following files from the BEData folder on the original volume to the BEData folder on the new volume: ■ .Bkf files ■ Any subfolders with a prefix of IMG in the name 8 In Windows Explorer, delete all of the files from the original disk storage device. 9 On the Backup Exec Administration Console, on the Storage tab, right-click the original disk storage device, and then click Delete. 10 Rename the new disk storage device with the name of the original disk storage device. 11 Right-click the new disk storage device, and then click Inventory and Catalog. See “Inventorying and cataloging a storage device” on page 438. See “Configuring disk storage” on page 305. Editing disk storage properties You can edit disk space management settings for the disk storage device. 308Disk-based and network-based storage Configuring disk storage
- 309. To edit disk storage properties 1 On the Storage tab, double-click the storage for which you want to edit properties. 2 In the left pane, click Properties. 3 Edit any of the following options: Displays the name of the disk storage. You can edit this field. Name Displays a description of the disk storage. You can edit this field. Description Prevents Backup Exec from deleting expired backup sets on this disk storage when you reattach the disk storage to the Backup Exec server. Otherwise, Backup Exec's data lifecycle management feature deletes any backup sets that are expired and reclaims the disk space. The default value is No. This option applies only when the disk storage has been detached from the Backup Exec server for the number of days that you specify in the global setting. The default number of days is 14. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. See “Backup sets ” on page 329. See “How to restore data from a reattached or reinserted disk-based storage device” on page 314. Limit Backup Exec to read-only operations Displays the maximum file size on the disk storage. The data from the backup job is contained in a file on the disk. The default value is 50 GB or the capacity of the disk storage. Maximum file size 309Disk-based and network-based storage Configuring disk storage
- 310. Creates the file when the backup job starts by preallocating space incrementally, according to the size of the increment that you set in Preallocation increment. As the job uses the disk space, more disk space is preallocated up to the maximum file size. When the job completes, the file size is then reduced to the amount of disk space that the job used. For example, if you enable preallocation and set the preallocation increment to 4 GB, then 4 GB of disk space is preallocated when the job starts. After the job uses 4 GB, then Backup Exec allocates another 4 GB. Disk space continues to be preallocated by 4 GB until the job completes. If the job only uses 13 GB of the 16 GB that was allocated, then the file size is reduced to 13 GB. The default value is Disabled. Preallocate disk space incrementally up to the maximum file size Displays the amount of disk space by which to increase the file size. The file size increases by this increment as the job requires disk space, up to the maximum file size. The default value is 1 GB. Preallocation increment Indicates if Backup Exec automatically detects the preferred settings for the block size and buffer size for the disk storage. The default value is Enabled. If you disable this setting, you can then choose the block size and buffer size to use. Auto detect block and buffer size 310Disk-based and network-based storage Configuring disk storage
- 311. Displays the size of the blocks of data that are written to new media in this disk storage device if the option Auto detect block and buffer size is disabled. The default is the preferred block size. Some storage devices provide better performance when larger block sizes are used. The preferred block size can range from 512 bytes to 64 kilobytes or larger. If you use a storage device that supports larger block sizes, you can change the block size. However, if the option to change the block size is unavailable, you must configure the device to use a larger size. See the manufacturer’s documentation for help in configuring the device. Backup Exec does not ensure that the storage device supports the requested block size. If the requested block size is not supported, it defaults to its standard block size. If the device does not support block size configuration, this option is unavailable. Block size Displays the amount of the data that is sent to the disk storage device on each read or write request if the option Auto detect block and buffer size is disabled. The buffer size must be an even multiple of the block size. Depending on the amount of memory in your system, increasing this value may improve storage performance. Each type of storage device requires a different buffer size to achieve maximum throughput. If the preferred block size is greater than 64 KB, the default buffer size is the same as the default block size. If the preferred block size is less than 64 KB, then the default buffer size is 64 KB. Buffer size 311Disk-based and network-based storage Configuring disk storage
- 312. Displays the critically low disk space threshold at which you want Backup Exec to send an alert. The color of the capacity bar on the Storage tab turns red to indicate critically low available space. Backup Exec sends alerts when the amount of free disk space drops below the low disk space threshold, and again if it drops below the warning threshold. The amount of free disk space does not include the disk space that is reserved for non-Backup Exec operations. You can change the value of the threshold. This threshold must be less than the warning threshold. The default value is 5%. Low disk space - Critical Displays the low disk space threshold at which you want Backup Exec to send an alert. The color of the capacity bar on the Storage tab turns orange to indicate a low disk space condition. If free disk space drops below the warning threshold to the critical threshold, another alert is sent. The amount of free disk space does not include the disk space that is reserved for non-Backup Exec operations. You can change the value of the threshold. This threshold must be less than the low disk space threshold. The default value is 15%. Low disk space - Warning 312Disk-based and network-based storage Configuring disk storage
- 313. Displays the low disk space threshold at which you want Backup Exec to send an alert. The color of the capacity bar on the Storage tab turns yellow to indicate the first of three low disk space conditions. If free disk space drops below this threshold to the amount that is specified in the warning threshold, another alert is sent. If free disk space drops below the warning threshold to the critical threshold, another alert is sent. The amount of disk space does not include the disk space that is reserved for non-Backup Exec operations. When low disk space reaches this threshold, data lifecycle management immediately searches the device for expired backup sets that it can delete. You can change the value of the threshold. The default value is 25%. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Low disk space Displays the amount of disk space to set aside for applications other than Backup Exec. The default value is 10 MB. Disk space to reserve for non-Backup Exec operations Indicates if Backup Exec automatically detects the preferred settings for read and write buffers for the disk storage. Auto detect settings Indicates the following when the setting is enabled: ■ You do not want Backup Exec to automatically detect settings for this disk storage device. ■ You want this disk storage to allow buffered read, which is the reading of large blocks of data. Enabling buffered reads may provide increased performance. Buffered read 313Disk-based and network-based storage Configuring disk storage
- 314. Indicates the following when the setting is enabled: ■ You do not want Backup Exec to automatically detect settings for this disk storage device. ■ You want this disk storage to allow buffered write, which is the writing of large blocks of data. Buffered write Displays the number of concurrent write operations that you want to allow to this disk storage device. Concurrent write sessions 4 Click Apply. See “Configuring disk storage” on page 305. How to restore data from a reattached or reinserted disk-based storage device If the backup sets on a disk storage device or a disk cartridge expire while that device is detached, Backup Exec deletes the catalogs for those backup sets. To restore from those backup sets at some future time, you must run an inventory and catalog operation on the device when you reattach it. When you run the inventory and catalog operation, Backup Exec sets a new expiration date for each backup set by using the backup set's original retention setting, calculated from the current date. Backup Exec also resets the expiration date for any backup set on the storage device that expires within seven days of the current date. If you want the backup sets to expire, you can disable the storage device property Limit Backup Exec to read-only operations. To find this option, on the Storage tab, right-click the storage device, click Details, and then click Properties. Do not run an inventory and catalog operation. Backup Exec reclaims the disk space on that storage device during data lifecycle management. You can also delete the backup sets. See “Inventorying and cataloging a storage device” on page 438. See “Backup sets ” on page 329. 314Disk-based and network-based storage How to restore data from a reattached or reinserted disk-based storage device
- 315. Configuring disk cartridge storage Disk cartridges are a type of storage that usually remains attached to the Backup Exec server while you remove the media, such as RDX. If you are not sure if the storage has removable media, you can open the Computer folder on your Windows computer. The devices that contain removable media are listed. Backup Exec uses data lifecycle management to automatically expire the backup sets that are stored on disk cartridge media. The backup sets on disk cartridge media are kept for the amount of time that you specify in the backup job properties. Backup Exec automatically reclaims the space as the backup data expires. You can keep the backup sets from automatically expiring by retaining the backup sets. Backup Exec then retains all dependent backup sets as well. You must use the Configure Storage wizard to configure a disk cartridge device. Available storage operations for disk cartridges and media are dependent on the type of disk cartridge that you have. For example, fewer operations are available for USB memory sticks than are available for RDX devices. To configure disk cartridge storage 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Do one of the following: Click Disk-based storage, and then click Next. If the Central Admin Server Option is not installed Do the following in the order listed: ■ Select the Backup Exec server that you want to configure storage for, and then click Next. ■ Click Disk-based storage , and then click Next. If the Central Admin Server Option is installed 3 Click Disk cartridge device, and then click Next. 4 Enter a name and description for the disk cartridge device, and then click Next. 5 Specify where the disk cartridge device is located, and then click Next. 6 Review the summary, and then do one of the following: 315Disk-based and network-based storage Configuring disk cartridge storage
- 316. Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the disk cartridge device See “Editing disk cartridge properties” on page 316. Editing disk cartridge properties You can edit settings for the disk cartridge storage. See “Configuring disk cartridge storage” on page 315. To edit disk cartridge properties 1 On the Storage tab, double-click the disk cartridge for which you want to edit properties. 2 In the left pane, click Properties. 3 Edit any of the following options: Displays the name of the disk cartridge. Disk cartridge names cannot exceed 128 characters. You can rename the disk cartridge. Name Displays a description of the disk cartridge. You can change the description. Description Displays the maximum file size on the disk cartridge. The data from the job is contained in a file on the disk cartridge. The default value is 50 GB or the capacity of the disk cartridge media. Maximum file size 316Disk-based and network-based storage Configuring disk cartridge storage
- 317. Creates the file when the job starts by preallocating space incrementally, according to the size of the increment that you set in Preallocation increment. As the job uses the disk space, more disk space is preallocated up to the maximum file size. When the job completes, the file size is then reduced to the amount of disk space that the job used. For example, if you enable preallocation and set the preallocation increment to 4 GB, then 4 GB of disk space is preallocated when the job starts. After the job uses 4 GB, then Backup Exec allocates another 4 GB. Disk space continues to be preallocated by 4 GB until the job completes. If the job only uses 13 GB of the 16 GB that was allocated, then the file size is reduced to 13 GB. The default value is Disabled. Preallocate disk space incrementally up to the maximum file size Displays the amount of disk space by which to increase the file size if the option to preallocate disk space is enabled. The file size increases by this increment as the job requires disk space, up to the maximum file size. The default value is 1 GB. Preallocation increment Indicates if Backup Exec automatically detects the preferred settings for the block size and buffer size for the disk storage. The default value is Enabled. If you disable this setting, you can then choose the block size and buffer size to use. Auto detect block and buffer size 317Disk-based and network-based storage Configuring disk cartridge storage
- 318. Displays the size of the blocks of data that are written to new media in this disk cartridge if the option Auto detect block and buffer size is disabled. The default is the preferred block size. Some storage devices provide better performance when larger block sizes are used. The preferred block size can range from 512 bytes to 64 kilobytes or larger. If you use the storage that supports larger block sizes, you can change the block size. However, if the option to change the block size is unavailable, you must configure the device to use a larger size. See the manufacturer’s documentation for help in configuring the storage. Backup Exec does not ensure that the storage device supports the requested block size. If the requested block size is not supported, it defaults to its standard block size. If the storage does not support block size configuration, this option is unavailable. Block size Displays the amount of the data that is sent to the disk cartridge on each read or write request if the option Auto detect block and buffer size is disabled. The buffer size must be an even multiple of the block size. Depending on the amount of memory in your system, increasing this value may improve storage performance. Each type of storage requires a different buffer size to achieve maximum throughput. If the preferred block size is greater than 64 KB, the default buffer size is the same as the default block size. If the preferred block size is less than 64 KB, then the default buffer size is 64 KB. Buffer size 318Disk-based and network-based storage Configuring disk cartridge storage
- 319. Displays the disk space threshold at which the color of the capacity bar on the Storage tab turns red to indicate critically low available space. Backup Exec does not send low disk space alerts for disk cartridge devices. You can change the value of the threshold, but it must be less than the warning threshold. The default value is 5%. See “Storage tab overview in Backup Exec” on page 409. Low disk space - Critical Displays the disk space threshold at which the color of the capacity bar on the Storage tab turns orange to indicate a low disk space condition. Backup Exec does not send low disk space alerts for disk cartridge devices. You can change the value of the threshold, but it must be less than the low disk space threshold. The default value is 15%. See “Storage tab overview in Backup Exec” on page 409. Low disk space - Warning Displays the disk space threshold at which the color of the capacity bar on the Storage tab turns yellow to indicate the first of three low disk space conditions. Backup Exec does not send low disk space alerts for disk cartridge devices. When the disk cartridge media reaches this threshold, the data lifecycle management feature immediately searches this disk cartridge media for expired backup sets that it can delete You can change the value of the threshold. The default value is 25%. See “Storage tab overview in Backup Exec” on page 409. Low disk space 319Disk-based and network-based storage Configuring disk cartridge storage
- 320. Indicates if Backup Exec automatically detects the preferred settings for read and write buffers for the disk cartridge. The default value is Enabled. Auto detect settings Indicates the following when the setting is enabled: ■ You do not want Backup Exec to automatically detect settings for this disk cartridge. ■ You want this disk cartridge to allow buffered read, which is the reading of large blocks of data. Enabling buffered read operations may provide increased performance. The default value is Enabled. If you disable Auto detect settings, this setting also changes to Disabled. Buffered read Indicates the following when the setting is enabled: ■ You do not want Backup Exec to automatically detect settings for this disk cartridge. ■ You want this disk cartridge to allow buffered write, which is the writing of large blocks of data. The default value is Enabled. If you disable Auto detect settings, this setting also changes to Disabled. Buffered write 4 Click Apply. Editing disk cartridge media properties You can edit the properties of the disk cartridge media. See “Configuring disk cartridge storage” on page 315. To edit disk cartridge media properties 1 On the Storage tab, double-click the disk cartridge device that contains the media. 2 In the left pane, click Media. 320Disk-based and network-based storage Configuring disk cartridge storage
- 321. 3 Edit any of the following options: Displays the media label that Backup Exec assigns automatically or that the administrator assigns. Media label You can edit the media label, which is limited to 32 characters. Editing the label changes the name of the media in the Backup Exec user interface. Displays the original media label if the media is imported media. You can edit the Media description media description to make it a more descriptive label. The description is limited to 128 characters. Keeps the media description when you select Yes in the drop-down box. The Preserve description media description is kept until an overwrite backup job runs or an erase or label storage operation job runs. By default, the media description is not retained. This option is set to No by default. 321Disk-based and network-based storage Configuring disk cartridge storage
- 322. Prevents Backup Exec from deleting expired backup sets on this disk cartridge media when you reinsert the cartridge media into the storage device. If you select Yes in the drop-down menu, then Backup Exec's data lifecycle management feature deletes any backup sets that are expired and reclaims the disk space. The default value is No. This option applies only when the disk cartridge media is absent from the Backup Exec server for the number of days that you specify in the global setting. By default, the number of days that the disk cartridge media must be absent before this option takes effect is 30 days. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. See “Backup sets ” on page 329. See “How to restore data from a reattached or reinserted disk-based storage device” on page 314. Limit Backup Exec to read-only operations 4 Click Apply. Howdatalifecyclemanagement(DLM)deletesexpired backup sets on disk-based storage Backup Exec uses data lifecycle management (DLM) to automatically delete expired backup sets on disk storage, disk cartridge media, deduplication storage, storage arrays, and virtual disks. You specify how long to keep backup data when you create a backup job that is sent to a disk-based storage device. When the amount of time to keep the backup data expires, the data lifecycle management feature deletes the backup sets and reclaims the disk space unless there are dependent backup sets such as incrementals. By default, Backup Exec keeps the most recent backup sets that are necessary to restore any backed-up component of a server, even if the backup sets expire. If backup sets are dependent on other backup sets, then Backup Exec does not delete the backup set until all expiration dates on the backup sets are reached. Even if 322Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 323. the backup set is displayed as expired, the data is available until all dependent backup sets expire as well. For example, you create a backup definition that contains a full backup and an incremental backup for the C: volume on a server. The first full backup runs, followed by the first incremental backup, and then the second incremental backup. The second full backup runs, followed by the third incremental backup, and then the fourth incremental backup. No more backups are run. All of the backup sets created by these backups eventually expire and are deleted by DLM. However, the backup sets that resulted from the second full backup and the third and fourth incremental backups are kept. Backup Exec keeps these related backup sets because they are the most recent backup sets that you need to restore the C: volume. By keeping the last related backup sets, you have the data to restore the volume. Warning: DLM deletes all expired backup sets that are created by a one-time backup job. DLM does not keep the last backup set after the retention date expires if the backup set is from a one-time backup. To prevent the backup sets from being automatically deleted, you can manually retain specific backup sets or you can change the expiration date of the backup set. If you retain a backup set, Backup Exec then retains all dependent backup sets as well. See “Retaining backup sets on disk-based storage to prevent them from expiring” on page 333. See “Changing the expiration date of backup sets on disk-based storage” on page 332. DLM searches for expired backup sets to delete from disk-based storage at the following times: ■ Every hour. DLM starts for the first time 1 hour after you install Backup Exec and the Backup Exec service starts, and then runs every hour after that. If you restart the Backup Exec service, the hourly DLM cycle also restarts. ■ When the low disk space threshold for disk-based storage is reached. The low disk space threshold is a storage device property. When the storage device's used capacity reaches this threshold, DLM immediately searches the device for the expired backup sets that it can delete. ■ When you manually expire a backup set. When you manually expire a backup set on a standalone Backup Exec server, DLM runs immediately on the storage device on which the backup set is located. 323Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 324. In a Central Admin Server Option (CASO) environment, if you manually expire a backup set from the central administration server, DLM immediately runs on the server on which the backup set was created. The server can be either the central administration server or the managed Backup Exec server. DLM runs only on the storage device from which the backup set was manually expired. If you manually expire a backup set from a managed Backup Exec server, DLM runs immediately on the storage device from which the backup set was manually expired. To monitor the backup sets that data lifecycle management deletes, you can view the Backup Set Retention category in the audit log. You can also run the audit log report to view the backup sets that data lifecycle management deletes. See “Configuring audit logs” on page 617. See “Audit Log report” on page 648. Storage options that can affect how data lifecycle management deletes backup sets are described in the following table: 324Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 325. Table 8-4 Storage options in Backup Exec that affect data lifecycle management DescriptionStorage option This global setting lets Backup Exec delete expired backup sets, even if they are the last remaining backup sets that you need to restore a server. Use this option when you want to delete backup data after a period of time. Alternatively, you can manually delete backup sets. Warning: If you enable this option, the data that you need to restore a server may not be available. The following conditions may cause you to lose backup sets when you enable this option: ■ If the backup sets from the last full backup job expire before the next full backup runs. Ensure that when you create jobs, the backup sets are kept longer than the amount of time between full backups. ■ If the backup job fails or is missed, and is not rerun before the backup sets expire. Monitor any failed or missed jobs, and ensure that you rerun them before the backup sets from the previous full backup expire. Note: In a Central Admin Server Option (CASO) environment, this option is only available on the central administration server. If you enable this option on the central administration server, DLM deletes all expired backup sets on the central administration server as well as on all of the managed Backup Exec servers. This option deletes all expired backup sets on both centrally managed and locally managed Backup Exec servers in a CASO environment. To access this option, click the Backup Exec button > Configuration and Settings > Backup Exec Settings > Storage. See “Editing global settings for storage” on page 423. Allow Backup Exec to delete all expired backup sets 325Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 326. Table 8-4 Storage options in Backup Exec that affect data lifecycle management (continued) DescriptionStorage option This global setting prevents Backup Exec from deleting expired backup sets on any disk-based storage device as soon as you reattach it. When you limit Backup Exec to read-only operations, you have time to review any expired backup sets and determine if you want to keep them before data lifecycle management deletes them. To keep expired backup sets, you can retain them or change the expiration date. See “Retaining backup sets on disk-based storage to prevent them from expiring” on page 333. See “Changing the expiration date of backup sets on disk-based storage” on page 332. Backup Exec is limited to read-only operations only on the disk-based storage devices that are detached from the Backup Exec server for the specified number of days. To access this option, click the Backup Exec button > Configuration and Settings > Backup Exec Settings > Storage. See “Editing global settings for storage” on page 423. Limit Backup Exec to read-only operations on a disk-based storage device if it has been detached for x number of days 326Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 327. Table 8-4 Storage options in Backup Exec that affect data lifecycle management (continued) DescriptionStorage option This global setting prevents Backup Exec from deleting expired backup sets on any disk cartridge as soon as you insert it into a disk cartridge device. When you limit Backup Exec to read-only operations, you have time to review any expired backup sets and determine if you want to keep them before data lifecycle management deletes them. To keep expired backup sets, you can retain them or change the expiration date. See “Backup sets ” on page 329. Backup Exec is limited to read-only operations only on the disk cartridges that are detached from the Backup Exec server for the specified number of days. To access this option, click the Backup Exec button > Configuration and Settings > Backup Exec Settings > Storage. See “Editing global settings for storage” on page 423. Limit Backup Exec to read-only operations on a disk cartridge if it has not been inserted for x number of days 327Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 328. Table 8-4 Storage options in Backup Exec that affect data lifecycle management (continued) DescriptionStorage option This device property prevents data lifecycle management from running on a specific disk-based or disk cartridge storage device that you reattach or reinsert it. This option applies only when the storage device has been absent from the Backup Exec server for the number of days that you specify in either of the two previous global settings described in this table. To access this option, on the Storage tab, right-click the device, click Details, and then click Properties. See “Editing disk storage properties” on page 308. See “Editing disk cartridge properties” on page 316. See “Editing the properties of a deduplication disk storage device” on page 808. See “Editing properties of virtual disks on storage arrays” on page 1300. Limit Backup Exec to read-only operations 328Disk-based and network-based storage How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
- 329. Table 8-4 Storage options in Backup Exec that affect data lifecycle management (continued) DescriptionStorage option This device property is the first of three low disk space conditions. When the storage device's used capacity reaches this threshold, the data lifecycle management feature immediately searches the device for expired backup sets that it can delete. Data lifecycle management also runs on a disk cartridge if the cartridge reaches capacity during a backup job. The backup may not need to span to another cartridge if data lifecycle management deletes enough expired backup sets. If a job does span and you insert a new disk cartridge that is full, data lifecycle management deletes expired backup sets on the new cartridge. To access this option, on the Storage tab, right-click the device, click Details, and then click Properties. See “Setting low disk space thresholds on disk-based storage” on page 304. Low disk space You should review the best practices for data lifecycle management at the following URL: http://entsupport.symantec.com/umi/V-269-43 Backup sets A backup set is a collection of the data that you back up from a single source of content. A single source of content can be a server or a Microsoft Exchange data set, for example. If you select multiple sources of content, Backup Exec creates multiple backup sets. When you run a backup job, Backup Exec creates the backup sets and writes them on storage. To restore data, you select the backup sets that contain the data that you want to restore. Backup Exec keeps the backup sets that are stored on disk storage and disk cartridge media for as long as you specify in the backup job properties. By default, the amount of time that backup sets are stored is based on the type of backup job and its schedule. 329Disk-based and network-based storage Backup sets
- 330. For example, you can specify to keep the backup sets from a full backup for two weeks on a disk-based storage device. After two weeks, the backup sets expire and Backup Exec uses the data lifecycle management feature to delete the backup sets and reclaim that disk space. If you later create an incremental backup job, Backup Exec keeps the full backup sets for two weeks, plus the amount of time that it keeps the incremental backup sets. If you keep the incremental backup sets for four weeks, then Backup Exec keeps the full backup sets for six weeks. The data from a full backup job is kept as long as the data from its associated incremental backup jobs. Backup Exec does not reclaim the disk space for backup sets from a job that depends on another job until the data retention expires for all of the associated jobs. Even if the backup set is displayed as expired, the data is available until all dependent backup sets expire as well. Backup Exec manages the retention of backup sets differently depending on the type of storage to which you back up the data. Table 8-5 Storage types and backup set retention Backup data retentionType of storage Backup Exec uses data lifecycle management to automatically delete expired backup sets from disk-based storage. By default, Backup Exec keeps the most recent backup sets that are necessary to restore any backed-up component of a server, even if the backup sets expire. Even if the backup set is displayed as expired, the data is available until all dependent backup sets expire as well. For disk-based storage and any disk cartridges that you reattach to the Backup Exec server after a specified number of days, you can prevent Backup Exec from reclaiming that disk space. A global setting limits Backup Exec to read-only operations on disk-based storage or a disk cartridge if it has been detached for a specified number of days. You can also limit Backup Exec to read-only operations per disk storage or disk cartridge by enabling the setting on the device properties. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. See “How to restore data from a reattached or reinserted disk-based storage device” on page 314. Disk storage, disk cartridge devices, deduplication disk storage, storage arrays and virtual disks 330Disk-based and network-based storage Backup sets
- 331. Table 8-5 Storage types and backup set retention (continued) Backup data retentionType of storage Backup Exec uses the Advanced Device and Media Management (ADAMM) feature to manage data retention on tape cartridge media. ADAMM expires the backup sets that are stored on media according to a set of rules that you apply to the media. Backup sets are not automatically deleted from tape cartridge media, but they can be overwritten, depending on the rules that you specify. The set of rules that manages tape cartridge media is called a media set. You create media sets that specify append periods, overwrite protection periods, and vaulting periods. See “Default media sets” on page 367. Tape cartridge media You can perform the following actions on backup sets that are on disk-based storage: ■ Change the expiration date of backup sets to keep them longer or expire them immediately. ■ Extend the amount of time that you keep backup sets by retaining them. ■ Release any backup sets that are retained to let them expire automatically. For all backup sets, including those on tape cartridge media, you can perform the following actions: ■ Catalog backup sets so that you can view the data that is contained in the backup sets and search for files to restore. ■ View the contents of backup sets and browse the backed up data that is contained in them. ■ View the system properties and job properties of backup sets. See “Changing the expiration date of backup sets on disk-based storage” on page 332. See “Retaining backup sets on disk-based storage to prevent them from expiring” on page 333. See “Releasing retained backup sets on disk-based storage” on page 334. See “Cataloging backup sets” on page 238. See “Viewing the contents or properties of backup sets” on page 335. 331Disk-based and network-based storage Backup sets
- 332. Changing the expiration date of backup sets on disk-based storage You can change the expiration date of backup sets that are on disk-based storage to keep them for a longer or shorter amount of time. You can also expire backup sets immediately, if you no longer want to keep them. Data lifecycle management (DLM) automatically deletes expired backup sets from disk-based storage. When you manually expire backup sets, Backup Exec checks those backup sets to ensure that no other backup sets are dependent upon them. Backup sets from incremental and differential jobs are dependent upon the backup sets that come from the full backup job in the same backup definition. You cannot expire only the backup sets that come from the full backup job because the dependent backup sets would not function without them. When Backup Exec detects dependent backup sets, it gives you the option to expire the backup sets and any dependent backup sets. When you manually expire a backup set on a standalone Backup Exec server, data lifecycle management (DLM) runs immediately on the storage device on which the backup set is located and deletes the expired backup set. In a Central Admin Server Option (CASO) environment, if you manually expire a backup set from the central administration server, DLM immediately runs on the server on which the backup set was created and deletes the expired backup set. The server can be either the central administration server or the managed Backup Exec server. DLM runs only on the storage device from which the backup set was manually expired to delete the expired backup set. If you manually expire a backup set from a managed Backup Exec server, DLM runs immediately on the storage device from which the backup set was manually expired and deletes the expired backup set. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. To change the expiration date of backup sets on disk-based storage 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets. 2 In the left pane, click Backup Sets. 3 Do one of the following: ■ To change the expiration date for a single backup set, right-click the backup set. ■ To change the expiration date for multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Do either of the following: 332Disk-based and network-based storage Backup sets
- 333. ■ Click Expire. Backup Exec displays the backup set and any dependent backup sets. ■ To expire the backup sets and any dependent backup sets, click Yes or Yes To All . To expire backup sets immediately ■ Click Expiration. ■ Enter the new expiration date in the Expiration field. ■ Click OK. To change the expiration date of backup sets See “Backup sets ” on page 329. Retaining backup sets on disk-based storage to prevent them from expiring You can prevent backup sets on disk-based storage from automatically expiring by retaining the backup sets. Backup Exec retains all dependent backup sets as well. For example, if you choose to retain an incremental backup set, Backup Exec retains all backup sets dating back to, and including, the last full backup job. You may need to retain backup sets for legal purposes, such as compliance with data retention laws. After you retain a backup set, Backup Exec prevents the backup set from expiring indefinitely. If you decide that you no longer need to retain a backup set, you must release it so that it can expire automatically. Data lifecycle management (DLM) automatically deletes expired backup sets from disk-based storage. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. To retain backup sets on disk-based storage to prevent them from expiring 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets that you want to retain. 2 In the left pane, click Backup Sets. 3 Do one of the following: ■ To retain a single backup set, right-click the backup set. ■ To retain multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Click Retain. 333Disk-based and network-based storage Backup sets
- 334. 5 In the Reason to retain backup sets field, select the reason that you want to retain the backup sets. You can choose from the following options: Select this option if the reason for retaining the backup sets is a legal one. You may have to retain backup sets to comply with corporate or regulatory data retention policies. Legal Select this option if the reason for retaining the backup sets is something other than a legal one. User defined 6 In the Explanation field, type any additional information about why you retained the backup sets. Entering an explanation in this field can help remind you why you retained the backup sets or for how long they should be retained. 7 Click OK. See “Backup sets ” on page 329. See “Releasing retained backup sets on disk-based storage” on page 334. Releasing retained backup sets on disk-based storage You can override the retention period for backup sets that are on disk-based storage by manually retaining them. When you choose to retain backup sets on disk-based storage, Backup Exec prevents the backup sets from automatically expiring when their retention period is over. You can manually retain backup sets indefinitely. If you no longer need the retained backup sets, you can allow them to expire. First, you need to remove the backup sets' retained status. Then Backup Exec expires the backup sets automatically according to the backup sets' storage settings. Data lifecycle management (DLM) automatically deletes expired backup sets from disk-based storage. To release retained backup sets on disk-based storage 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets that you want to release. 2 In the left pane, click Backup Sets. 3 Do one of the following: ■ To release a single backup set, right-click the backup set. ■ To release multiple backup sets, Shift + click or Ctrl + click the backup sets, and then right-click one of the selected backup sets. 4 Click Retain. 334Disk-based and network-based storage Backup sets
- 335. 5 Select Do not retain. 6 Click OK. See “Backup sets ” on page 329. See “Retaining backup sets on disk-based storage to prevent them from expiring” on page 333. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Viewing the contents or properties of backup sets After you complete a backup job, you can view the data that is contained in the backup sets that are created. Viewing the contents of backup sets can help you to confirm what data was backed up. You may also want to view the contents of backup sets before you run a restore job to verify the data that they contain. You can also view the following backup set properties: ■ Backup source ■ Backup date ■ Expiration date ■ Backup method ■ Size ■ Location ■ Backup set description ■ Data encryption ■ True image ■ Server name ■ Catalog file name ■ Snapshot To view the contents or properties of backup sets 1 On the Backup and Restore tab or the Storage tab, double-click the server or the storage device that is related to the backup sets that you want to view. 2 In the left pane, click Backup Sets. 335Disk-based and network-based storage Backup sets
- 336. 3 Double-click the backup set that you want to view. Note: On the Backup and Restore tab, you must expand the backup source to see the backup set. 4 Do either of the following: In the left pane, click Contents. The contents of the backup set display in the left pane in a tree view. You can expand folders and drives to view their contents in the right pane. To view the contents of the backup sets In the left pane, click Properties.To view the properties of the backup sets See “Backup sets ” on page 329. 336Disk-based and network-based storage Backup sets
- 337. Legacy backup-to-disk folders This chapter includes the following topics: ■ Legacy backup-to-disk folders Legacy backup-to-disk folders In previous versions of Backup Exec, the backup-to-disk feature let you back up data to a folder on a hard disk. These legacy backup-to-disk folders are now read-only. You can continue to inventory, catalog, and restore data from a backup-to-disk folder. You can use remote Simplified Disaster Recovery to perform a disaster recovery from backup-to-disk folders. In Windows Explorer, the backup-to-disk folders display in the path you specified when you added the folders. The backup-to-disk files display with a .bkf file extension. Each backup-to-disk folder also contains a file named changer.cfg and a file named folder.cfg, which store information about the backup-to-disk files. Note: Do not delete or edit the changer.cfg or folder.cfg files. A subfolder with a prefix of IMG in the name may display under a backup-to-disk folder. In previous versions, Backup Exec created this subfolder when the following conditions were met in a backup job: ■ The option to enable Granular Recovery Technology (GRT) was selected. ■ A backup-to-disk folder was selected as storage for the backup data. 9Chapter
- 338. You cannot send backup data to a backup-to-disk folder. Symantec recommends that you back up data to a disk-based storage device. See “Features and types of disk-based storage and network-based storage” on page 300. See “Restoring data from a legacy backup-to-disk folder” on page 340. See “Changing the location of a legacy backup-to-disk folder” on page 339. See “Recreating a legacy backup-to-disk folder and its contents” on page 340. Changing the name or description of a legacy backup-to-disk folder You can edit the name and description of a backup-to-disk folder. See “Legacy backup-to-disk folders ” on page 337. To change the name or description of a legacy backup-to-disk folder 1 On the Storage tab, double-click the backup-to-disk folder for which you want to edit the name or description. 2 In the left pane, click Properties. 3 Change either of the following properties: Displays the name of the backup-to-disk folder. Backup-to-disk folder names must not exceed 128 characters. Name Displays the description of the backup-to-disk folder. Description 4 Click Apply. Changing the buffered read setting for a legacy backup-to-disk folder You can change the buffered read setting for a legacy backup-to-disk folder so that it is enabled, or disabled. To change the buffered read setting for a legacy backup-to-disk folder 1 On the Storage tab, double-click the backup-to-disk folder for which you want to change the buffered read and write settings. 2 In the left pane, click Properties. 3 Change any of the following properties: 338Legacy backup-to-disk folders Legacy backup-to-disk folders
- 339. Indicates if Backup Exec automatically detects the preferred settings for read buffers for the backup-to-disk folder. Auto detect buffers Indicates the following when the setting is Enabled: ■ You do not want Backup Exec to automatically detect settings for this backup-to-disk folder. ■ You want this backup-to-disk folder to allow buffered reads, which is the reading of large blocks of data. Enabling the buffered reads setting may provide increased performance. Buffered reads 4 Click Apply. Changing the location of a legacy backup-to-disk folder You can change the location of a legacy backup-to-disk folder. See “Legacy backup-to-disk folders ” on page 337. To change the location of a legacy backup-to-disk folder 1 On the Storage tab, right-click the original legacy backup-to-disk folder, and then click Delete. 2 Create a folder that has a different name and location than the existing legacy backup-to-disk folder. 3 In Windows Explorer, copy and paste all of the following files and folders to the new folder: ■ .Bkf files ■ .Cfg files ■ Any subfolders with a prefix of IMG in the name 4 In Windows Explorer, delete all of the files from the original backup-to-disk folder. 5 On the Backup Exec Administration Console, on the Storage tab, in the Configure operation group, click Configure Storage. 339Legacy backup-to-disk folders Legacy backup-to-disk folders
- 340. 6 Follow the prompts to import the legacy backup-to-disk folder from the new location. See “Restoring data from a legacy backup-to-disk folder” on page 340. 7 Right-click the backup-to-disk folder, and then click Inventory and Catalog. Recreating a legacy backup-to-disk folder and its contents If you have deleted a backup-to-disk folder from Backup Exec, but not from the disk, you can recreate the backup-to-disk folder and the files in it. You must know the name and path of the original backup-to-disk folder to retrieve it. If you deleted a backup-to-disk folder from the disk, you cannot recreate it. See “Legacy backup-to-disk folders ” on page 337. To recreate a legacy backup-to-disk folder and its contents 1 On the Storage tab, in the Configure operation group, click Configure Storage. 2 Follow the prompts to import the legacy backup-to-disk folder that you want to recreate. See “Restoring data from a legacy backup-to-disk folder” on page 340. 3 Right-click the backup-to-disk folder, and then click Inventory and Catalog. See “Inventorying and cataloging a storage device” on page 438. Restoring data from a legacy backup-to-disk folder You must import an existing legacy backup-to-disk folder into Backup Exec to restore data from it. When you import a backup-to-disk folder, you cannot use the root of a volume or an administrative UNC share as the path. The administrative shares are ADMIN$, IPC$, and one for each local disk drive letter, such as C$, D$, and so on. Note: When you import a legacy backup-to-disk folder, all of the backup data on that folder is set to expire one year from the data that the folder is imported. You can keep the data longer, or expire the data earlier. See “Changing the expiration date of backup sets on disk-based storage” on page 332. See “Retaining backup sets on disk-based storage to prevent them from expiring” on page 333. 340Legacy backup-to-disk folders Legacy backup-to-disk folders
- 341. To restore data from a legacy backup-to-disk folder 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Do one of the following: Select Disk-based Storage, and then click Next. If the Central Admin Server Option is not installed Do the following in the order listed: ■ Select the Backup Exec server on which you want to import a legacy backup-to-disk folder, and then click Next. ■ Select Disk-based Storage, and then click Next. If the Central Admin Server Option is installed 3 Select Import a legacy backup-to-disk folder, and then click Next. 4 Enter a name and description for the legacy backup-to-disk folder, and then click Next. 5 Enter the path to the existing legacy backup-to-disk folder, and then click Next. 6 Review the summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To import the legacy backup-to-disk folder 7 When the legacy backup-to-disk folder appears on the Storage view, right-click the folder, and then click Inventory and Catalog. Note: Depending on the number of backup sets involved, this operation may take a long time to complete. Consider running this operation during off-peak hours. 341Legacy backup-to-disk folders Legacy backup-to-disk folders
- 342. 8 On the Storage tab, in the All Storage view, navigate to the legacy backup-to-disk folder from which you want to restore. 9 Right-click the legacy backup-to-disk folder, and then click Restore. 342Legacy backup-to-disk folders Legacy backup-to-disk folders
- 343. Tape storage This chapter includes the following topics: ■ Support for tape drives and robotic libraries ■ About the Virtual Tape Library Unlimited Drive Option ■ About the Library Expansion Option ■ Adding or replacing devices with the Hot-swappable Device Wizard ■ Installing Symantec tape device drivers ■ Editing tape drive properties ■ Viewing tape drive statistics ■ Robotic libraries in Backup Exec ■ Creating robotic library partitions ■ Managing tapes ■ Labeling tape media ■ How WORM media is used in Backup Exec ■ Default media vaults ■ Retiring damaged tape media ■ Deleting tape media ■ Erasing tape or disk cartridge media ■ About cataloging tape or disk cartridge media that contains encrypted backup sets ■ Associating tape media with a media set 10Chapter
- 344. ■ Editing tape media properties ■ Tape media rotation strategies Support for tape drives and robotic libraries When you install Backup Exec, it automatically recognizes all tape storage that is attached to the Backup Exec server. Tape storage includes tape drives, robotic libraries, virtual tape libraries, and simulated tape libraries. When you install Backup Exec, support for the following items is included: ■ The first robotic library drive per robotic library. ■ Every single-drive virtual tape library. Support for additional drives is available with the Library Expansion Option and the Virtual Tape Library Unlimited Drive Option. You can use the Configure Storage wizard to perform the following actions for tape storage: ■ Partition robotic library slots. ■ Install Symantec tape device drivers. Note: You do not need to install Symantec tape device drivers if Backup Exec runs on Windows Server 2012 and later. Symantec kernel-mode drivers and tapeinste.exe are no longer installed if Backup Exec runs on Windows Server 2012 and later. See “Installing Symantec tape device drivers ” on page 347. ■ Replace or add hot-swappable storage on a Backup Exec server without having to restart the server. ■ Create media sets to manage the backup data on tapes. See “About the Virtual Tape Library Unlimited Drive Option ” on page 345. See “About the Library Expansion Option ” on page 345. See “Default media sets” on page 367. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. 344Tape storage Support for tape drives and robotic libraries
- 345. About the Virtual Tape Library Unlimited Drive Option When you install Backup Exec, support for every single-drive virtual tape library is included. The Virtual Tape Library Unlimited Drive Option enables support for all additional drives in each virtual tape library. To install the Virtual Tape Library Unlimited Drive Option, add a license. You can find a list of compatible types of storage in the Backup Exec Hardware Compatibility List: http://entsupport.symantec.com/umi/v-269-2 You can find license information for the Virtual Tape Library Unlimited Drive Option in the Backup Exec Customer Pricing and Licensing Guide: http://entsupport.symantec.com/umi/V-269-21 See “Installing additional Backup Exec options to the local Backup Exec server” on page 62. About the Library Expansion Option When you install Backup Exec, support for the first drive in every robotic library is included. The Library Expansion Option enables support for each additional drive in a robotic library. To install the Library Expansion Option, add a license. You can find a list of compatible types of storage in the Backup Exec Hardware Compatibility List: http://entsupport.symantec.com/umi/v-269-2 You can find license information for the Library Expansion Option in the Backup Exec Customer Pricing and Licensing Guide: http://entsupport.symantec.com/umi/V-269-21 See “Installing additional Backup Exec options to the local Backup Exec server” on page 62. Adding or replacing devices with the Hot-swappable Device Wizard Use the Hot-swappable Device Wizard to replace or add hot-swappable storage on a Backup Exec server without having to restart the server. 345Tape storage About the Virtual Tape Library Unlimited Drive Option
- 346. If you remove and then reconnect Universal Serial Bus (USB) tape devices to the USB port, you must run the Hot-swappable Device Wizard to allow Backup Exec to rediscover the devices. For iSCSI-attached devices, you must list the device as a Persistent Target in the iSCSI control panel applet, and then run the Hot-swappable Device Wizard. Listing the device as a Persistent Target lets Backup Exec rediscover the device whenever you restart the Backup Exec server. After you start the Hot-swappable Device Wizard, you are prompted to close the Backup Exec Administration Console. The Hot-swappable Device Wizard waits until any jobs that were processing are completed. The wizard pauses the Backup Exec server and stops the Backup Exec services. You can then add or replace any storage devices. The wizard detects the new device or replaced device, and adds information about the device to the Backup Exec database. The wizard is then completed, and you can reopen the Backup Exec Administration Console. Any new storage appears in the Storage tab, and usage statistics for the storage begin accumulating. You can enable the new storage in a storage device pool. Any replaced storage appears in the Storage tab, in the All Storage view with a status of Offline. Note: Start the Symantec Hot-swappable Device Wizard before you add or replace storage. To add or replace devices with the Hot-swappable Device Wizard 1 Do one of the following: In the iSCSI control panel applet, add the storage to the Persistent Targets list. Continue with the next step. For iSCSI-attached storage: Continue with the next step.For any other hot-swappable storage: 2 On the Storage tab, in the Configure group, click Configure Storage. 3 When you are prompted for the type of storage that you want to configure, select Tape Storage, and then click Next. 4 Select Run the Hot-swappable Device Wizard, click Next, and then follow the on-screen prompts. 346Tape storage Adding or replacing devices with the Hot-swappable Device Wizard
- 347. Installing Symantec tape device drivers You can use the Configure Storage wizard to install tape device drivers and to delete entries for tape devices that are not available, have been removed, or are turned off. This topic includes the following information: Symantec kernel-mode tape drivers and tapeinst.exe Before you install Symantec tape device drivers, do the following: ■ Ensure that Backup Exec supports the tape device. You can find a list of compatible types of storage in the Backup Exec hardware compatibility list: http://entsupport.symantec.com/umi/V-269-2 ■ Run the Windows Device Manager to ensure that it lists the tape device. ■ Get the latest Backup Exec device drivers. To get the latest device drivers installed to the Backup Exec installation folder 1 Click the Backup Exec button, select Technical Support, and then click Latest Backup Exec Device Drivers. 2 Run the Symantec Device Driver Installation Wizard, in the following procedure. To install Symantec tape device drivers by using the Configure Storage wizard 1 On the Storage tab, in the Configure group, click Configure Storage. 2 On the wizard panel, select Tape Storage, and then click Next. 3 Select Install tape device drivers, and then click Next. 4 On the Symantec Device Driver Installation Wizard, follow the on-screen prompts. Symantec kernel-mode tape drivers and tapeinst.exe Symantec kernel-mode drivers and tapeinst.exe are no longer installed if Backup Exec runs on Windows Server 2012 or later. If the Backup Exec server runs on Windows Server 2012 or later, the Configure Storage wizard option Install tape device drivers is not available, and tapeinst.exe is not available from the default Backup Exec installation location. Tapeinst.exe is the program that installs Symantec kernel-mode tape class drivers. If the Backup Exec server runs on Windows Server 2008 R2 or earlier, you can run tapeinst.exe manually, or by using the Configure Storage wizard. 347Tape storage Installing Symantec tape device drivers
- 348. If you use older or unsupported tape devices, test the devices before you use Windows Server 2012 and later to determine the functionality in case kernel-mode drivers are required. Symantec user-mode drivers now access all supported tape devices. User-mode drivers have accessed most tape devices for multiple previous versions of Backup Exec. User-mode drivers are not visible in the Windows Device Manager. When no kernel-mode drivers are installed, the Windows Device Manager may show the tape drive with a yellow exclamation mark. This display is acceptable and does not prevent the use of the device with Backup Exec and the user-mode drivers. Kernel-mode drivers from Microsoft or from the tape hardware vendor are generally acceptable for installation. Backup Exec will continue to access the tape devices through the user-mode drivers. To install Symantec tape device drivers on a Backup Exec server that run on Windows Server 2008 R2 or earlier by running tapeinst.exe 1 From the Backup Exec installation directory, double-click the tapeinst.exe file. The default installation directory is C:Program FilesSymantecBackup Exec 2 On the Symantec Device Driver Installation Wizard, follow the on-screen prompts. Editing tape drive properties You can edit the following tape drive properties. See “Support for tape drives and robotic libraries” on page 344. To edit tape drive properties 1 On the Storage tab, double-click the tape drive for which you want to edit properties. 2 In the left pane, click Properties. 348Tape storage Editing tape drive properties
- 349. 3 Edit any of the following options: Displays the name of the tape drive. You can edit this field. Name Displays the description of the tape drive. You can edit this field. Description Indicates if hardware compression is enabled. Hardware compression If this option is available, this drive is capable of supporting hardware compression. If you configure a job to use hardware compression, and hardware compression is disabled on the device, then hardware compression is unavailable and is not used. 349Tape storage Editing tape drive properties
- 350. Displays the size of the blocks of data that are written to new media in this tape drive. The default is the preferred block size. Some devices (for example, LTO devices) provide better performance when larger block sizes are used. The preferred block size can range from 512 bytes to 64 kilobytes or larger. If you use a tape drive that supports larger block sizes, you can change the tape drive’s block size. However, if the tape drive does not allow a block size as large as you want, reconfigure the host bus adapter or the tape drive. After you reconfigure the hardware and restart the Backup Exec services, check if the block size that you want to use is available. See the tape drive manufacturer’s documentation for help in configuring the device. Backup Exec does not ensure that the requested block size is supported by that tape drive. You should check the tape drive specifications to make sure that the block size is supported. If the tape drive does not support a block size, it defaults to its standard block size. If the tape drive does not support block size configuration, this option is unavailable. Block size Displays the amount of data that is sent to the tape drive on each read or write request. The buffer size must be equal to the block size or an even multiple of the block size. Depending on the amount of memory in your system, increasing this value may improve tape drive performance. Each type of tape drive requires a different buffer size to achieve maximum throughput. Buffer size 350Tape storage Editing tape drive properties
- 351. Displays the number of buffers that are allocated for this tape drive. Depending on the amount of memory in your system, increasing this value may improve device performance. Each type of tape drive requires a different number of buffers to achieve maximum throughput. If you change the buffer count, you may need to adjust the high water count accordingly. Buffer count Displays the number of buffers to be filled before data is first sent to the tape drive, and any time that the tape drive underruns. The high water count cannot exceed the buffer count. A value of 0 disables the use of high water logic; that is, each buffer is sent to the device as it is filled. The default setting provides satisfactory performance in most instances; in some configurations, throughput performance may be increased when other values are specified in this field. If you increase or decrease the buffer count, the high water count should be adjusted accordingly. If a tape drive has a high water count default of 0, it should be left at 0. High water count Returns all of the preferred configuration settings to their defaults. Reset to default settings Indicates if this tape drive reads only one block of data at a time, regardless of the size of the buffer block. This option is disabled by default. Read single block mode Indicates if this tape drive writes only one block of data at a time. This option provides greater control over the handling of data write errors. Symantec recommends that you select this option if the tape drive is shared. This option is enabled by default. Write single block mode 351Tape storage Editing tape drive properties
- 352. Indicates if this tape drive reads data without going through a Microsoft tape device API. This option allows the data to pass directly through the tape drive and allows more detailed information if device errors occur. This option is disabled by default. Read SCSI pass-through mode Indicates if this tape drive writes data without going through the Microsoft tape device API. This option allows data to pass directly through the device driver and allows more detailed information if device errors occur. Symantec recommends that you select this option if the tape drive is shared. This option is enabled by default. Write SCSI pass-through mode Displays the servers that can also use this device. See “Sharing storage devices” on page 432. Servers that share this device Indicates if barcode rules are enabled for the robotic library that this tape drive is attached to. If barcode rules are enabled, the media types are listed that this tape drive can read from and write to. Backup Exec uses the barcode rules to identify which type of media to use in a drive. You can configure barcode rules, and enable or disable barcode rules for a robotic library. See “Configuring barcode rules for a robotic library ” on page 355. Media Type Indicates if this tape drive can read from the media type. See “Configuring barcode rules for a robotic library ” on page 355. Can Read From 352Tape storage Editing tape drive properties
- 353. Indicates if this tape drive can write to this media type. See “Configuring barcode rules for a robotic library ” on page 355. Can Write To 4 Click Apply. Viewing tape drive statistics You can view statistics about tape drives. See “Support for tape drives and robotic libraries” on page 344. To view tape drive statistics 1 On the Storage tab, double-click the tape drive for which you want to view statistics. 2 In the left pane, click Statistics. Robotic libraries in Backup Exec Backup Exec’s Advanced Device and Media Management (ADAMM) feature solves the problems that are associated with typical robotic library modules. Backup Exec accesses all of the media in the robotic library and uses the media that belongs to the specified media set. If the backup job exceeds the capacity of a media, Backup Exec searches all of the media that is contained in the robotic library and finds a suitable media to use. For example, an operator has a robotic library with six slots. The operator inserts six blank tapes and targets backup jobs to various media sets within the robotic library. Backup Exec automatically allocates available tapes in the robotic library. If a job exceeds the capacity of one tape and another overwritable tape is available in the robotic library, the job automatically continues on that tape. When Backup Exec runs out of tapes, it prompts the operator to import overwritable media. In a robotic library, Backup Exec selects the oldest recyclable media in the library to use first. If more than one media that meets the requirements is found, Backup Exec selects the media in the lowest-numbered slot. For example, Backup Exec selects media in slot 2 before it selects equivalent media in slot 4. For restore jobs that use robotic libraries, Backup Exec accesses the source media regardless of its sequential placement in the magazine. For example, if the data for a restore job resides on two media in the magazine, the media do not have to be placed in adjacent slots for Backup Exec to restore the data. If Backup Exec 353Tape storage Viewing tape drive statistics
- 354. does not find the media that is required for the restore job in the robotic library, an alert is generated that requests the media that is necessary to complete the job. See “Requirements for setting up robotic library hardware” on page 354. See “Creating robotic library partitions” on page 361. Requirements for setting up robotic library hardware You can configure Backup Exec to work with robotic library drives by making associations between the robotic library’s drives, robotic arm, and Backup Exec. Backup Exec supports serialized drives. Manual configuration of serialized drives is not required. You can find a list of supported types of storage at the following URL: http://entsupport.symantec.com/umi/V-269-2 Ensure that the robotic library hardware is configured as follows: ■ Ensure that the robotic arm is set to Random mode. Refer to your robotic library documentation for more information. ■ Ensure the following for a multi-LUN robotic library: ■ The controller card is set to support multiple LUNs (if supported). ■ The target LUN for the tape drive is lower than the target LUN for the robotic library. ■ Determine which drive is the first drive in the robotic library, and then arrange the SCSI IDs to match the sequence of the drive element addresses. Refer to your robotic library documentation to determine the drive element address for each storage device. ■ Ensure that the SCSI ID of the robotic arm precedes the SCSI IDs of the drives in the robotic library. Do not use 0 or 1 because these SCSI IDs are typically reserved for boot devices. In the following example, if your robotic library has two drives, the drive with the lowest drive element address should be assigned the lower SCSI ID. Table 10-1 Example configuration for a multi-drive robotic library Drive element address SCSI IDData transfer element (storage devices ) N/A4Robotic arm 000080005Storage device 0 354Tape storage Robotic libraries in Backup Exec
- 355. Table 10-1 Example configuration for a multi-drive robotic library (continued) Drive element address SCSI IDData transfer element (storage devices ) 000080016Storage device 1 See “Robotic libraries in Backup Exec” on page 353. Inventorying robotic libraries when Backup Exec services start You can set a default so that all robotic libraries are included in the inventory job whenever Backup Exec services are started. Symantec recommends that you enable this default if media is often moved between robotic libraries. Backup Exec may take longer to start. To inventory robotic libraries when Backup Exec services start 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings. 2 In the left pane, click Storage. 3 Click Inventory robotic libraries when Backup Exec services start. 4 Click OK. See “Inventorying a storage device” on page 437. Configuring barcode rules for a robotic library If you have barcode support for a robotic library that uses different types of drives, you can create a barcode rule. Backup Exec uses the barcode rules to identify which type of media to use in a drive. When Backup Exec reads the barcode rule, it locates the type of media that corresponds to the prefix or suffix. Backup Exec then mounts the media into a drive that accepts that type of media. The barcode rules apply to all of the robotic libraries that you enable for barcode rules. By default, barcode rules are disabled. You can use the Configure Storage wizard to configure barcode rules, or you can add, edit, and delete barcode rules in the Backup Exec global settings. You can also enable or disable barcode rules in the robotic library's properties. See the section called “Configuring barcode rules for a robotic library by using the Configure Storage wizard” on page 356. See the section called “Adding, editing, and deleting barcode rules by using the Backup Exec global settings” on page 357. 355Tape storage Robotic libraries in Backup Exec
- 356. See the section called “Enabling or disabling barcode rules by using robotic library properties” on page 357. Configuring barcode rules for a robotic library by using the Configure Storage wizard To configure barcode rules for a robotic library 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Do one of the following: Click Tape storage, and then click Next.If the Central Admin Server Option is not installed Do the following in the order listed: ■ Select the Backup Exec server on which you want to configure storage, and then click Next. ■ Click Tape storage, and then click Next. If the Central Admin Server Option is installed 3 Click Configure barcode rules for a robotic library, and then click Next. 4 Select the robotic library that you want to configure barcode rules for, and then click Next. 5 To change the available barcode rules in the list, click any of the following: Do the following in the order listed: ■ Click New. ■ Click the drop-down menu, and then select a media type ■ Type the vendor name, and the barcode prefix and/or suffix. ■ Click OK. To add a new barcode rule Do the following in the order listed: ■ Select the barcode rule that you want to edit, and then click Edit. ■ Make any changes, and then click OK. To edit an existing barcode rule Select a barcode rule, click Delete, and then click Yes to confirm the deletion. To delete a barcode rule 6 Click Next. 356Tape storage Robotic libraries in Backup Exec
- 357. 7 Select a tape drive, and then for any of the listed media types, select a check box to specify if the tape drive can read from and write to that media type. Cick Next. 8 Review the summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next. ■ Click Finish. To change the barcode configuration Click Finish.To complete the barcode configuration 9 Ensure that barcode rules are enabled for the appropriate robotic libraries. Enabling or disabling barcode rules by using robotic library properties You can enable or disable barcode rules for a robotic library. By default, barcode rules are disabled for robotic libraries. To enable or disable barcode rules by using robotic library properties 1 On the Storage tab, double-click the robotic library for which you want to enable barcode rules. 2 In the left pane, click Properties. 3 In the Barcode rules field, in the drop-down menu, do one of the following: Click Enabled.To enable all barcode rules for this robotic library Click Disabled.To disable all barcode rules for this robotic library 4 Click OK. Adding, editing, and deleting barcode rules by using the Backup Exec global settings You can add, edit, or delete the barcode rules for a robotic library in the global settings for Backup Exec. All barcode rules changes apply to all of the robotic libraries for which barcode rules are enabled. 357Tape storage Robotic libraries in Backup Exec
- 358. To add, edit, or delete a barcode rule by using the Backup Exec global settings 1 Click the Backup Exec button, click Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, click Bar Code Rules. 3 Do one of the following: Click New, and then continue with the next step. To add new barcode rule Select the barcode rule that you want to edit, click Edit, and then continue with the next step. To edit an existing barcode rule Do the following in the order listed: ■ Select the barcode rule that you want to delete, and then click Delete. ■ Click Yes to confirm the deletion, and then click OK. The barcode rule is deleted. To delete an existing barcode rule 358Tape storage Robotic libraries in Backup Exec
- 359. 4 Add or change any of the following information: Click the drop-down menu and select or change the media type. Media type Enter or change the name of the robotic library manufacturer. A best practice is to use a vendor name only if there is a specific need for it and you have multiple brands of tape drives that are available This field is limited to 16 characters. Vendor Enter or change the prefix of a barcode to which you want to apply this barcode rule. A standard practice is to use a prefix to indicate a media-handling policy, such as CLN for cleaning media, or I for internal use, or O for cartdriges that are to be taken offsite. This field is limited to 16 characters. Barcode prefix Enter or change the suffix of a barcode to which you want to apply this barcode rule. A standard practice is to use a suffix to indicate the generation of the media, such as L1, L2, and so on. This field is limited to 16 characters. Barcode suffix 5 Click OK. Initializing a robotic library when the Backup Exec service starts You can initialize a robotic library whenever the Backup Exec services start. During startup, if media is in the drives in the robotic library, Backup Exec attempts to return the media to its original drive. If the media cannot be returned to the drive, an error message appears that prompts you to eject the media from the drive. You can also create a job to initialize a robotic library. See “Initializing a robotic library” on page 439. See “Robotic libraries in Backup Exec” on page 353. 359Tape storage Robotic libraries in Backup Exec
- 360. To initialize a robotic library when the Backup Exec services start 1 On the Storage tab, double-click the robotic library that you want to initialize. 2 In the left pane, click Properties. 3 In the Startup initialization field, in the drop-down menu, click Enabled. 4 Click Apply. Defining a cleaning slot Before submitting a cleaning job, you must define a cleaning slot that contains the cleaning tape. Make sure that the cleaning tape is located in the slot that you defined as the cleaning slot. After defining the cleaning slot, you can set up a cleaning job for the robotic library drive. See “Cleaning a robotic library drive” on page 442. Note: Defined cleaning slots are not inventoried when an inventory job runs. To define a cleaning slot 1 On the Storage tab, expand the robotic library, and then double-click Slots. 2 Double-click the slot that contains the cleaning tape. 3 In the Cleaning slot field, click the drop-down menu, and then click Yes. 4 Click Apply. Editing robotic library properties You can view robotic library properties. See “Robotic libraries in Backup Exec” on page 353. To view robotic library properties 1 On the Storage tab, double-click the robotic library for which you want to view properties. 2 In the left pane, click Properties. 360Tape storage Robotic libraries in Backup Exec
- 361. 3 Edit the following options as appropriate: Displays the name of the robotic library. You can edit this field. Name Displays the description of the robotic library. You can edit this field. By default, Backup Exec displays the device's inquiry string, which is the vendor name and product ID. Description Displays the starting slot for this robotic library. Backup Exec determines what the starting slot should be for this type of library. Some robotic libraries have slots that start at 0. Other libraries start at 1. You can change the starting slot if necessary. First slot number 4 Click OK. Creating robotic library partitions You can group one or more robotic library slots into partitions. Partitioning robotic library slots provides you with more control over which tape is used for backup jobs. When you create robotic library partitions, Backup Exec creates a storage device pool for each partition. Jobs that you send to a partition's storage device pool run on the media that is located in the partition’s slots. For example, if you set up a partition that contains slots 1 and 2 and you want to run a weekly backup only on the media in these slots, you would submit the job to the storage device pool for the partition that contains slots 1 and 2. The storage device pools for robotic library partitions appear in the drop-down menu for the Storage field when you edit the backup job. All storage device pools for a robotic library partition have the same name and display the slot ranges for the partition in parentheses within the name. Partitions can include any number of robotic library slots. Depending on the robotic library configuration, the first slot may be numbered 1 or 0. If the robotic library uses a zero-based slot configuration, the Configure Storage wizard uses slot 0 as the first slot for partition 1 and adjusts the starting slot accordingly for all other partitions. See “Reassigning a slot base number for robotic libraries” on page 363. When the robotic library is partitioned, Backup Exec searches for the oldest recyclable media in the specified partition only. If more than one media is found that meets the requirements, Backup Exec then selects the media in the 361Tape storage Creating robotic library partitions
- 362. lowest-numbered slot; for example, media in slot 2 is selected before equivalent media in slot 4. You can create a partitioning scheme that best suits your environment. For example, some administrators may create partitions based on users and groups, while others may create partitions according to operation types. To create robotic library partitions 1 Do one of the following: Do the following in the order listed: ■ On the Storage tab, in the Configure group, click Configure Storage. ■ Select Tape storage, and then click Next. ■ Select Configure robotic library partitions, and then click Next. ■ Select the robotic library to configure partitions for, and then click Next. To view all of the robotic libraries that you can configure partitions for Do the following in the order listed: ■ On the Storage tab, right-click the robotic library for which you want to create partitions. ■ Click Configure partitions. To configure partitions for a specific robotic library 2 Specify the number of partitions to create, enter the number of slots for each partition, and then click Next. 3 Review the storage configuration summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the partitions See “Changing the name of a robotic library partition” on page 363. 362Tape storage Creating robotic library partitions
- 363. Changing the name of a robotic library partition You can change the name of a robotic library partition. See “Creating robotic library partitions” on page 361. To change the name of a robotic library partition 1 On the Storage tab, double-click the robotic library partition. 2 In the left pane, click Properties. 3 Change the name of the robotic library partition. 4 Click Apply. Adding or removing tape drives in a robotic library partition You can add or remove tape drives in a robotic library partition. See “Creating robotic library partitions” on page 361. To add or remove tape drives in a robotic library partition 1 On the Storage tab, double-click the robotic library partition. 2 In the left pane, click Properties. 3 Do either of the following: Do the following in the order listed: ■ Click Add. ■ In the devices list that appears, select the tape drive that you want to add, and then click OK. To add a tape drive to the robotic library partition Select the tape drive that you want to remove, and then click Remove. To remove a tape drive from the robotic library partition 4 Click Apply. Reassigning a slot base number for robotic libraries Backup Exec automatically assigns slot base numbers for robotic libraries. If necessary, you can reassign how robotic library slots are displayed in Backup Exec. Slot base numbers in some robotic libraries start at 0, while slots in other robotic libraries start at 1. If the robotic library uses a zero-based slot configuration, you can reassign how the slots are displayed. See “Robotic libraries in Backup Exec” on page 353. 363Tape storage Creating robotic library partitions
- 364. To reassign a slot base number for robotic libraries 1 On the Storage tab, double-click the robotic library for which you want to reassign a slot base number. 2 In the First slot number field, click the drop-down menu to change the base number. 3 Click Apply. Editing robotic library slot properties You can edit the properties of a robotic library slot. See “Robotic libraries in Backup Exec” on page 353. To edit robotic library slot properties 1 On the Storage tab, double-click the robotic library. 2 In the left pane, click Slots. 3 Double-click the slot for which you want to view properties and then click Properties. 4 To view another slot's properties, click the drop-down menu at the top center of the window, and then click a slot number. 364Tape storage Creating robotic library partitions
- 365. 5 Edit any of the following options. Indicates if this slot has been defined as a cleaning slot. If Yes is displayed, this slot has been defined as a cleaning slot. Before you can submit a cleaning job, you must define a cleaning slot that contains the cleaning tape. Make sure that the cleaning tape is located in the slot that you define as the cleaning slot. After defining the cleaning slot, you can set up a cleaning job for the robotic library drive. Note: Defined cleaning slots are not inventoried when an inventory job runs. See “Cleaning a robotic library drive” on page 442. Cleaning slot Keeps the media description when you select Yes in the drop-down menu. The media description is kept until an overwrite backup job runs or an erase or label storage operation job runs. By default, the media description is not retained. This option is set to No by default. Preserve description 6 Click Apply. Removing or reconfiguring robotic library partitions You can remove or reconfigure robotic library partitions. To remove robotic library partitions 1 On the Storage tab, right-click the robotic library that contains the partitions that you want to remove or reconfigure. 2 Click Configure partitions. 3 Click Remove all robotic library partitions, and then click Next. 4 Review the storage configuration summary, and then do one of the following: 365Tape storage Creating robotic library partitions
- 366. Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To remove the partitions To reconfigure robotic library partitions 1 On the Storage tab, right-click the robotic library that contains the partitions that you want to remove or reconfigure. 2 Click Configure partitions. 3 Click Reconfigure robotic library partitions, and then click Next. 4 Specify the number of partitions to create, enter the number of slots for each partition, and then click Next. 5 Review the storage configuration summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the partitions See “Reassigning a slot base number for robotic libraries” on page 363. Managing tapes For tape media, you can perform the following actions: ■ Protect data from being overwritten. ■ Set up media rotation strategies. ■ Track the location of media. ■ Label media automatically. ■ Read and track the media labels that have barcodes. 366Tape storage Managing tapes
- 367. ■ Collect and report media statistics. The Advanced Device and Media Management (ADAMM) feature in Backup Exec automatically selects the tape media for jobs. Backup Exec keeps track of all tape media that is loaded into the attached storage device. Backup Exec also keeps track of the media that is offline and the media that has been placed in media vaults. For data that is kept on tapes, Backup Exec uses media sets to apply overwrite protection periods and append periods to manage the expiration of backup sets. A media set consists of the following rules that apply to tape media: ■ How long to protect the data on the media from overwrite. This is called the overwrite protection period. ■ How long to append data to a media. This is called the append period. ■ When and where to send media for vaulting. Media that are associated with a media set are allocated media. Allocated media have current append and overwrite protection periods. Media that are associated with a media set but have expired overwrite protection periods are recyclable media. See “Default media sets” on page 367. See “Tape media rotation strategies” on page 398. See “Creating media sets for tapes” on page 374. Default media sets When you install Backup Exec, default system media sets and default user media sets are created automatically. When you add tapes to Backup Exec by importing media, Backup Exec associates the tape with one of the system media sets. Note: You should not associate scratch media with a media set that you create. When a backup job runs, Backup Exec automatically moves the media from the Scratch Media set to the required media set as needed. See “Importing media to Backup Exec ” on page 443. You cannot modify the properties of system media sets. System media sets are described in the following table: 367Tape storage Managing tapes
- 368. Table 10-2 Default system media sets DescriptionName Displays all media that is imported from another installation of Backup Exec. See “Cataloging a storage device” on page 435. Backup Exec and Windows NT Backup Media Displays all cleaning media. See “Cleaning a robotic library drive” on page 442. Cleaning Media Displays all media that is imported from a product other than Backup Exec. See “About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec” on page 234. See “Cataloging a storage device” on page 435. Foreign Media Displays all media that you have taken out of service, usually because of an excessive number of errors. After you associate a media with the retired media set, Backup Exec does not select it for backup jobs. The media is still available for restore operations, if it has not been damaged. Retired Media protects media from being used (overwritten). If Backup Exec cannot recognize data on a tape, then it moves the tape to Retired Media. If you want to reuse the tape, erase or label the tape. These operations write a new header to the tape that Backup Exec can recognize. After the tape is erased or labeled, Backup Exec moves it to the Scratch Media set. You can delete the media that is in Retired Media to remove it from Backup Exec. You may want to delete media if you have a lot of off-site media that you do not want to recycle. You can also delete media if you throw away the media. See “Erasing tape or disk cartridge media” on page 393. See “Retiring damaged tape media” on page 392. Retired Media 368Tape storage Managing tapes
- 369. Table 10-2 Default system media sets (continued) DescriptionName Displays all media that can be overwritten. New, blank, and erased media are automatically associated with the Scratch Media set. See “Overwrite protection periods and append periods in media sets” on page 370. Scratch Media Backup Exec creates the following default user media sets: Table 10-3 Default user media sets DescriptionName Displays all tape media that you associate with this media set. If you use the backup job defaults that are set when you install Backup Exec, the media set Keep Data for 4 Weeks is the default media set for all backup jobs that you send to tape storage. This media set protects data from being overwritten for four weeks and allows the media to be appended to for six days. You can edit and rename Keep Data for 4 Weeks after installation. Therefore, it may not continue to appear in the Media view or in the backup job defaults as Keep Data for 4 Weeks. Keep Data for 4 Weeks Displays all tape media that you associate with this media set. When you associate media with this media set, data is not overwritten unless you perform any of the following actions on the media: ■ Erase ■ Label ■ Format ■ Associate the media with the scratch media set You can append data to this media for an infinite period (until the media is full). You can edit and rename Keep Data Infinitely - Do Not Allow Overwrite after installation. Therefore, it may not continue to appear in the Media view or in the backup job defaults as Keep Data Infinitely - Do Not Allow Overwrite. Keep Data Infinitely - Do Not Allow Overwrite 369Tape storage Managing tapes
- 370. You can change the default media set for backup jobs by doing one of the following: ■ Create new media sets that have the append and overwrite protection periods set to the time intervals that accommodate your data retention strategy. Then, specify the media set that is most appropriate when you create a backup job. For example, you can create a media set that keeps data for 60 days, and a media set that keeps data for 90 days. ■ Select the other default media set Keep Data Infinitely - Do Not Allow Overwrite when you create a backup job. The risk that is associated with the media set Keep Data Infinitely - Do Not Allow Overwrite is that you can use all of your scratch media. You must continually add new tape or disk cartridge media to Backup Exec. Note: Symantec recommends that if you need to keep data longer than four weeks, you should duplicate it. You can duplicate the backup data from the original storage device to tape, which you can then send for long-term or off-site storage. To view all media sets ◆ On the Storage tab, double-click All Media Sets. See “Overwrite protection periods and append periods in media sets” on page 370. See “Creating media sets for tapes” on page 374. See “Creating media vault rules to move tape media to and from media vaults” on page 390. See “Duplicating backup sets or a job history manually” on page 209. See “Associating tape media with a media set” on page 395. Overwrite protection periods and append periods in media sets Each tape media is associated with a media set, which is a set of rules that manage media. These rules include overwrite protection and append periods. Table 10-4 Overwrite protection and append periods DescriptionRule The amount of time that data can be appended to tape media. It is measured from the time the media was first allocated. It can be specified in hours, days, weeks, or years. Append period 370Tape storage Managing tapes
- 371. Table 10-4 Overwrite protection and append periods (continued) DescriptionRule The amount of time that tape media is protected from being overwritten. The period is measured from the time of the last write to the media, that is, at the end of the last append or overwrite job. It can be specified in hours, days, weeks, or years. When the overwrite protection period is over, the media becomes recyclable and can be overwritten. The overwrite protection period begins when the backup job is completed. If there is an append period, the overwrite protection period begins again each time an append job completes. Because the overwrite protection period does not begin until the job completes, the amount of time that is required to complete the job affects when the media can be overwritten. You may shorten the overwrite protection period to take into account the amount of time a job may run. For example, you set the overwrite protection period for seven days. You also set the append period for four days to ensure that data is not overwritten for at least seven days. The data can be appended to the media for the next four days. The last data that is appended to this media is retained for at least seven days. Note: Any media can be overwritten if the overwrite protection level is set to None. See “Media overwrite protection levels for tape media” on page 380. Overwrite protection period Your tape media rotation strategy must balance between the need to save data as long as possible, and the fact that tape media are not in infinite supply. The media set rules allow Backup Exec to identify which tape media can be written to and which tape media are overwrite-protected. You should consider the use of disk storage for backup data. See “Configuring disk storage” on page 305. The following graphic shows the relationship between the append period and the overwrite protection period. 371Tape storage Managing tapes
- 372. Figure 10-1 Append periods and overwrite protection periods The append period begins when the media is allocated to a media set. APPENDPERIOD OVERWRITEPROTECTIONPERIOD The overwrite protection period is measured from the time of the last write to the media. During the append period, data can be added to the media. Any data already on the media is protected against loss. The append period ends. After the append period expires, and while the overwrite protection period is still active, data cannot be added to the media. Any data already on the media is protected against loss. The overwrite protection period expires. After the overwrite protection period expires, the media becomes recyclable. This means that new data can be written to the beginning of the media by a new backup job (causing loss of the original data). New data Old data TIMETIMETIME The media cannot be Overwritten by another job during this interval. (However, you could erase the media or associate it with scratch media.) The append and overwrite protection periods that you specify apply to all the data on the media. 372Tape storage Managing tapes
- 373. Each time data is written to a media, the time remaining in the overwrite protection period is reset, and the countdown is restarted. Figure 10-2 How overwrite protection periods are reset 1 1 2 3 4 The media can be overwritten at this time The media can be overwritten at this time Second Day Fifth Day Normal Bkup The media can be overwritten at this time First Day Append period = 5 days Append period = 5 days Append period = 5 days Protection period 14 days Time in days Protection period 14 days 1 3 2 21 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Protection period 14 days Time in days Time in days Normal Bkup Normal Bkup 1 Normal Bkup Normal Bkup Normal Bkup Normal Bkup Normal Bkup The amount of time that is required to complete the job affects when the media can be overwritten. For example, suppose that you create a media set named Weekly with an overwrite protection period of seven days. You also specify an append period of zero days, and you schedule a full backup job to run each Friday at 20:00. When it is time for the full backup to run at 20:00 the following Friday, the job cannot run. The first backup job that ran the previous Friday did not complete until 21:10. The overwrite protection period for the Weekly media set still has 70 minutes remaining. To prevent this situation, you can shorten the overwrite protection period to account for the amount of time a job may run. For this example, the scheduled job recurring at 20:00 can run if the overwrite protection period is set to six days instead of seven days. 373Tape storage Managing tapes
- 374. Creating media sets for tapes A media set consists of the rules that specify the following: ■ Append periods ■ Overwrite protection periods ■ Media vaults ■ Amount of time to move media to and from the media vault The media set rules apply to all of the media that you associate with the media set. Note: You must have already created a media vault before you are prompted to add media vault rules in a media set. See “Default media sets” on page 367. To create a media set for tapes 1 On the Storage tab, expand Tape and Disk Cartridge Media . 2 Double-click All Media Sets. 3 Under User Media Sets, right-click a media set, and then click Create media set. 4 Enter a name and a description for the media set, and then click Next. 5 Specify how long you want to keep data in this media set from being overwritten, and then click Next. 6 Specify how long you want to allow data to be appended to media in this media set, and then click Next. 7 Review the summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To create the media set Editing media set properties You can edit the following properties for media sets: 374Tape storage Managing tapes
- 375. ■ Name of a media set. ■ Overwrite protection and append periods for a media set. ■ Media vault and the vaulting periods associated with a media set. See “Default media sets” on page 367. To edit media set properties 1 On the Storage tab, expand Tape and Disk Cartridge Media . 2 Double-click All Media Sets. 3 Double-click the media set for which you want to edit properties. 4 In the left pane, click Properties. 5 Change any of the following information: Displays the name of the media set.Name Displays the description of the media set.Description 375Tape storage Managing tapes
- 376. Displays the length of time in hours, days, weeks, or years to retain the data on the media before the media can be overwritten. Regardless of the overwrite protection period that is set, media can be overwritten if you perform the following operations on it: ■ Erase ■ Label ■ Associate it with the Scratch Media Set ■ Set the Media Overwrite Protection Level to None ■ Format Because of the method Backup Exec uses to compute time, the unit of time that you enter may be converted. For example, if you enter 14 days, the next time you view this property, it may be displayed as two weeks. The default period is Infinite - Don’t Allow Overwrite, which protects the media from being overwritten for 1,000 years. See “Overwrite protection periods and append periods in media sets” on page 370. Overwrite protection period Displays the length of time in hours, days, or weeks that data can be added to media. Because of the method Backup Exec uses to compute time, the unit of time that you enter may be converted. For example, if you enter 14 days, the next time you view this property, it may be displayed as two weeks. The append period starts when the first backup job is written to this media. The default period is Infinite - Allow Append, which allows data to be appended until the media capacity is reached. Append period 376Tape storage Managing tapes
- 377. Displays the media vault that stores the media that is associated with this media set. See “Default media vaults” on page 388. Media vault to use with this media set Displays the time period after which this media is reported as ready to be moved to this vault. Move media to this vault after Displays the time period after which this media is reported as ready to be returned from this vault. Return media from this vault after 6 Click Apply. Changing the overwrite protection period or the append period for a media set You can change the length of time to retain data on media that are associated with a media set. You can also change the length of time to add data to media that are associated with a media set. See “Overwrite protection periods and append periods in media sets” on page 370. To change the overwrite protection period or the append period for a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media . 2 Double-click All Media Sets. 3 Double-click the media set for which you want to change the overwrite protection period or the append period. 4 In the left pane, click Properties. 5 Change the following information as appropriate: 377Tape storage Managing tapes
- 378. Displays the length of time in hours, days, weeks, or years to retain the data on the media before the media can be overwritten. Regardless of the overwrite protection period that is set, media can be overwritten if you perform the following operations on it: ■ Erase ■ Label ■ Associate it with the Scratch Media Set ■ Set the Media Overwrite Protection Level to None ■ Format Because of the method Backup Exec uses to compute time, the unit of time that you enter may be converted. For example, if you enter 14 days, the next time you view this property, it may be displayed as two weeks. The default period is Infinite - Don’t Allow Overwrite, which protects the media from being overwritten for 1,000 years. Overwrite protection period Displays the length of time in hours, days, or weeks that data can be added to media. Because of the method Backup Exec uses to compute time, the unit of time that you enter may be converted. For example, if you enter 14 days, the next time you view this property, it may be displayed as two weeks. The append period starts when the first backup job is written to this media. The default period is Infinite - Allow Append, which allows data to be appended until the media capacity is reached. Append period 6 Click Apply. 378Tape storage Managing tapes
- 379. Changing the name and description of a media set You can change the name and description of a media set. To change the name and description of a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media . 2 Double-click All Media Sets. 3 Double-click the media set for which you want to change the name or description. 4 In the left pane, click Properties. 5 Change the name and/or the description of the media set, and then click Apply. Changing the media vault or vaulting periods for a media set You can change the media vault that stores this media set, and you can change the time periods for when you want to move media to a vault or return media from a vault. See “Default media vaults” on page 388. To change the media vault or vaulting periods for a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media . 2 Double-click All Media Sets. 3 Double-click the media set for which you want to change the media vault or vaulting periods. 4 In the left pane, click Properties. 5 Change the folloiwng information as appropriate: Displays the media vault that stores the media that is associated with this media set. Media vault to use with this media set Displays the time period after which this media is reported as ready to be moved to this vault. Move media to this vault after Displays the time period after which this media is reported as ready to be returned from this vault. Return media from this vault after 6 Click Apply. 379Tape storage Managing tapes
- 380. Deleting a media set If you delete a media set that has scheduled jobs associated with it, you are prompted to associate the jobs to another media set. Caution: Ensure that the media set that you associate the jobs with has the appropriate overwrite protection and append periods. See “Default media sets” on page 367. To delete a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media. 2 Double-click All Media Sets. 3 Right-click the media set that you want to delete, and then click Delete. 4 When you are prompted to delete the media set, click OK. Renaming a media set When you rename a media set, any jobs that use that media set display the new media set name. See “Default media sets” on page 367. To rename a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media. 2 Double-click All Media Sets. 3 Right-click the media set that you want to rename, and then click Details. 4 In the left pane, click Properties. 5 In the Name field, type the new name that you want to assign to this media set, and then click Apply. Media overwrite protection levels for tape media The media overwrite protection level is a global setting that supersedes the media set’s overwrite protection period. Although the terms are similar, the media overwrite protection level and the media overwrite protection period are different. The media overwrite protection period is a time interval that changes from one media set to another. The media overwrite protection level specifies whether to overwrite scratch, imported, or allocated media, regardless of the media’s overwrite protection period. 380Tape storage Managing tapes
- 381. Use the media overwrite protection level to specify the type of media that you want to be available for overwrite backup jobs. See “Overwrite protection periods and append periods in media sets” on page 370. Overwriting allocated or imported tape media Media that are associated with a media set are called allocated media. Media that are imported from another installation of Backup Exec, or from another product are called imported media. Backup Exec protects allocated and imported media from being overwritten when full or partial overwrite protection is used. However, you can let Backup Exec overwrite allocated and imported media before the data overwrite protection period expires, and without setting the media overwrite protection level to None. The following methods are available: ■ Associate the media with the Scratch Media Set. The media is overwritten when it is selected for an overwrite job. ■ Erase the media. Erased media is automatically recognized as scratch media and is overwritten immediately. ■ Label the media. The Label Media operation immediately writes a new media label on the media, which destroys any data that is contained on the media. ■ Format the media. Formatting destroys any data that is contained on the media. ■ Change the overwrite protection period for the media set so that it is expired. See “Managing tapes” on page 366. See “Deleting tape media” on page 393. See “Editing global settings for storage” on page 423. How Backup Exec searches for overwritable media in tape drives Media overwrite options set the order in which Backup Exec searches for overwritable media in tape drives. When Backup Exec searches for overwritable media for a backup job, it searches for either scratch media or media that has an expired overwrite protection period. You are prompted to select one of the following options that you want Backup Exec to use first: ■ Overwrite scratch media before overwriting recyclable media that is contained in the destination media set. 381Tape storage Managing tapes
- 382. If you choose to overwrite scratch media before recyclable media, more media may be required for the same number of jobs. However, the recyclable media may be preserved longer for possible recovery. ■ Overwrite recyclable media that is contained in the destination media set before overwriting scratch media. If you choose to overwrite recyclable media before scratch media, the same media is re-used more frequently than if you overwrite scratch media before recyclable media. In a storage device pool for tape drives, Backup Exec selects the oldest recyclable media in the storage device pool to use first. In a robotic library, Backup Exec selects the oldest recyclable media in the library to use first. If the robotic library is partitioned, Backup Exec searches for the oldest recyclable media in the targeted partition only. Caution: Symantec recommends that you physically write-protect media containing critical data. Use the write-protect tab on the media cartridge to protect against unintentional move or erase operations, or expired overwrite protection periods. The following table describes the order in which Backup Exec searches for media to use for an overwrite job. Table 10-5 How Backup Exec searches for overwritable media in tape drives Media is overwritten in tape drives in this order:Overwrite protection level and overwrite option: 1 Scratch media 2 Recyclable media in the destination media set 3 Recyclable media in any media set Full + Overwrite scratch media first Note: This combination provides the most protection against overwriting media. 1 Recyclable media in the destination media set 2 Scratch media 3 Recyclable media in any media set Full + Overwrite recyclable media first 1 Scratch media 2 Recyclable media in the destination media set 3 Recyclable media in any media set 4 Media that is imported from another installation of Backup Exec, or from another product Partial + Overwrite scratch media first 382Tape storage Managing tapes
- 383. Table 10-5 How Backup Exec searches for overwritable media in tape drives (continued) Media is overwritten in tape drives in this order:Overwrite protection level and overwrite option: 1 Recyclable media in the destination media set 2 Scratch media 3 Recyclable media in any media set 4 Media that is imported from another installation of Backup Exec, or from another product Partial + Overwrite recyclable media first 1 Scratch media 2 Recyclable media in the destination media set 3 Recyclable media in any media set 4 Media that is imported from another installation of Backup Exec, or from another product 5 Allocated media in any media set None - No overwrite protection + overwrite scratch media first Warning: This options is not recommended because it does not protect data from being overwritten. 1 Recyclable media in the destination media set 2 Scratch media 3 Recyclable media in any media set 4 Media that is imported from another installation of Backup Exec, or from another product 5 Allocated media in any media set None - No overwrite protection + overwrite recyclable media first Warning: This options is not recommended because it does not protect data from being overwritten. In addition to setting overwrite protection levels, you must set overwrite options, which set the order in which Backup Exec searches for overwritable media. The most obvious candidates for backup jobs that require overwritable media are scratch media and recyclable media. Recyclable media have expired overwrite protection periods. Backup Exec searches for these types of media first when a backup requires tape media to overwrite. The search pattern is different according to whether you have selected Full, Partial, or None. The media indicate that a type of media set is examined for availability. See “Editing global settings for storage” on page 423. See “Default media vaults” on page 388. 383Tape storage Managing tapes
- 384. Viewing tapes that are used by a job To see which tapes are used for a job, review the Device and Media Information section of the job log. See “Managing tapes” on page 366. To view the tapes that are used by a job 1 Do any of the following: Select the Job Monitor tab.To view the job log from the Job Monitor tab Do the following in the order listed: ■ On the Backup and Restore tab or the Storage tab, double-click the server or the storage device where the job ran. ■ In the left pane, click Job History. To view the job log from the Backup and Restore tab or the Storage tab 2 Right-click the job, and the select View Job Log. 3 Review the information in the section Device and Media Information. Labeling tape media Media labels identify the tapes that you use in Backup Exec. When a new, blank, or unlabeled tape is used during a backup operation, Backup Exec automatically labels the tape media. This label consists of a prefix that identifies the cartridge type, and an incrementing number. For example, if the media is a 4mm tape, then the prefix is 4M, followed by 000001. The next media label generated for an unlabeled 4mm tape would be 4M000002, and so on. Another type of media label used by Backup Exec is the media ID, which is a unique label assigned by Backup Exec to the individual tape media used in Backup Exec. The media ID is used internally by Backup Exec to keep statistics on each media. Because the media label or barcode label for tape media can be changed, Backup Exec must use the media ID to preserve continuity in record keeping for each individual tape media. You cannot change or erase the media ID. The media ID has no effect on the media label, or on your ability to rename, label, or erase tape media. At times, you may need to use the media ID to distinguish the tape media that have duplicate media labels. Duplicate labels can be automatically generated in instances when Backup Exec is reinstalled or media from another Backup Exec installation is used. You can view the media ID in a media’s property page. 384Tape storage Labeling tape media
- 385. Write the media label on an external label that is fixed to the outside of the physical tape cartridge. Whenever you change the media label, you should also change the external label to match. The following methods are available in Backup Exec to change a tape media label: ■ Write a new media label on the tape media. The Label operation destroys any data on the media. ■ Rename the media. Renaming the tape media changes the name of the media in the display, but does not write the new label to the media until an overwrite operation occurs. The data on the media is viable until the media is overwritten. ■ Edit the label. Editing the label changes the name of the tape media in the display, but does not write the new label to the media until an overwrite operation occurs. The data on the media is viable until the media is overwritten. Note: Media that use barcode labels cannot be renamed. When you try to label the media that use barcode labels, the job logs report successfully completed jobs. However, the media label names do not change. To label media 1 On the Storage tab, do either of the following: ■ Right-click the drive that contains the tape that you want to label. ■ Double-click Slots, and then right-click the slot that contains the tape that you want to label. 2 Click Label. The following warning appears: This operation is performed on the current media in the drive or slot. If the media has changed since the last inventory ran, the media label in the next dialog may not match the media in the selected device. 3 Click OK. 4 Type the name that you want to use as the media label for this media. 5 To erase all data on the media and re-label the media, click OK. 6 Write this same media label on an external label that is fixed to the outside of the physical media. 7 (Optional) View the job history for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. 385Tape storage Labeling tape media
- 386. See “Renaming a tape media label ” on page 387. See “How barcode labels become media labels for tapes” on page 386. About labeling imported tape media Tape media that is imported from another installation of Backup Exec, or from another product is called imported media. Backup Exec does not automatically relabel imported media. Backup Exec reads the imported tape media’s existing label and displays the label in either the Backup Exec and Windows NT Backup Media media set or in the Foreign Media media set. If the media overwrite protection level is set to Partial or None, the imported media may be selected for a job and be overwritten. The imported media is automatically labeled when it is overwritten during a job. If you want to label a specific imported media while maintaining full media overwrite protection for other imported media, erase the specific media and then label it. The original media label of the imported tape media is displayed in the media's properties. You can edit the media description in the media’s property page to make it a more descriptive label. See “Erasing tape or disk cartridge media” on page 393. How barcode labels become media labels for tapes If there is a barcode label on the physical tape cartridge, and if the robotic library has a barcode reader, the barcode label automatically becomes the media label. For example, robotic library 1 has barcode support. During a backup operation, Backup Exec requests a new media or an overwritable media for the operation. A new media with the barcode label 'ABCD' is inserted in the robotic library magazine and the barcode reader scans the barcode ID. Backup Exec selects this media for the operation and detects that a barcode label has been assigned to the media. Backup Exec automatically uses the barcode label and continues the operation. If a barcode label is the media label, then you cannot change the media label in Backup Exec. To change a barcode label and use a media label, you must remove the physical barcode label from the media cartridge. Or, you can use the media in a device that does not have a barcode reader. When you change magazines or insert new media in a magazine, you can use the Scan operation to quickly update slot information. See “Labeling tape media” on page 384. See “Scanning a storage device” on page 436. 386Tape storage Labeling tape media
- 387. Renaming a tape media label You can rename a tape media's label and description. The new label is not written to the tape media until an overwrite operation occurs. All of the data that is on the media is preserved until the next overwrite job. However, the new media label is stored in the database and is displayed for that media. To write a new media label to the media immediately, use the Label operation. The media’s contents are erased. If you rename a tape media, and then use it in another installation of Backup Exec, that media is imported to the Backup Exec and Windows NT Media media set. The media’s original media label is displayed. The renamed label is not transferred to other installations of Backup Exec. Note: If a barcode label is the media label, then you cannot change the media label in Backup Exec. See “Labeling tape media” on page 384. To rename a tape media label 1 On the Storage tab, right-click the tape drive or slot that contains the media that you want to relabel, and then click Details. 2 In the left pane, click Media Properties. 3 In the Media label field, enter a new label name. 4 To change the description, enter a new description in the Media description field. 5 Click Apply. How WORM media is used in Backup Exec Write once, read many (WORM) data storage is used to keep the data that has a long retention period. Data can be written to WORM media one time only. After it is written to, the media can be appended to, but it cannot be overwritten, erased, or reformatted. When WORM media is used in a media set, the overwrite protection period is not applied to it, but the append period is applied. New WORM media is WORM media that has not been written to. When new WORM media is introduced into Backup Exec, it is placed in the Scratch Media set. After the WORM media has been written to one time, you cannot move it to the Scratch media set. You can move WORM media to the Retired Media set to delete it from Backup Exec, but you cannot erase it or reformat it. 387Tape storage How WORM media is used in Backup Exec
- 388. You can format a tape as a WORM tape if the tape drive supports the operation. See “Formatting a tape as a WORM tape” on page 440. When you select the option to use WORM media, Backup Exec verifies that the destination device is or contains a WORM-compatible drive. Backup Exec also verifies that the WORM media is available in the drive. If WORM media or a WORM-compatible drive is not found, an alert is sent and the backup job may fail. See “Configuring storage options for backup jobs” on page 512. Default media vaults A media vault is a logical representation of the actual physical location of specified tape media. You can create media vaults to keep track of where media is physically stored, such as a scratch bin, or an off-site location. Backup Exec creates default media vaults to let you view all media that are online, offline, or in a media vault. You must run the Configure Storage wizard to update the location of tape media in media vaults. From the Configure Storage wizard, you can print reports that detail which tape media are ready to move to and return from the vault. You can also update the location of the media if you choose to move them. However, you must physically collect the tape media, and move the media to and from the vault. The location of the tape media is updated in the Backup Exec Database, but the media is not ejected or exported. If Backup Exec detects that the media is in a robotic library, you are prompted to export media. If you choose to export the media, an export media job runs. If your environment includes remote sites, you should create separate media sets for each remote site. Then, the reports contain details on which media are ready to be moved for a specific site. Table 10-6 Default media vaults DescriptionDefault media vault Displays the media that are available in tape drives or robotic libraries. You cannot add or move media to the online media vault. Backup Exec does that automatically. If you move media from the online media vault to another media vault, the media's overwrite protection period and append period remain in effect. Online Tape Media 388Tape storage Default media vaults
- 389. Table 10-6 Default media vaults (continued) DescriptionDefault media vault Displays the media that are on-site but are not in tape drives or robotic libraries, and are not in media vaults. Media appear in the offline media vault if you use Backup Exec to remove media from a tape drive or robotic library. You can add media to the offline media vault from another media vault. An inventory operation or a catalog operation moves the offline media back to the online media vault. You cannot delete or rename the offline media vault. Offline Tape Media Displays the media that are not in tape drives or robotic libraries, and have been moved to a media vault. Vaulted Tape Media displays in All Media Vaults details only after you create a media vault. Vaulted Tape Media Displays the media that are in media vaults that you create. All Media Vaults displays on the Storage tab only after you create a media vault. You can associate media vaults with media sets that you create. You specify when to move the media from a media set to the media vault. You also specify when the media is to return to the media set from the media vault. See “Creating media vault rules to move tape media to and from media vaults” on page 390. All Media Vaults See “Changing the name or description of a media vault” on page 389. Changing the name or description of a media vault You can edit the name and description of a media vault. See “Default media vaults” on page 388. To change media vaults and media vault rules, edit the properties of the media set that is associated with the media vault. 389Tape storage Default media vaults
- 390. See “Editing media set properties” on page 374. Changing the name or description of a media vault 1 On the Storage tab, expand Tape Cartridge Media Sets and Vaults, and then expand All Media Vaults. 2 Right-click the media vault for which you want to edit properties, and then click Details. 3 In the left pane, click Media Vault Properties. 4 Change the name or description of the media vault. 5 Click Apply. Media vault properties Properties for media vaults include the name and a description of the media vault. See “Changing the name or description of a media vault” on page 389. Table 10-7 Properties for media vaults DescriptionItem Displays the name of the media vault.Name Displays a description of the media vault.Description Creating media vault rules to move tape media to and from media vaults Create media vault rules to do the following: ■ Associate a media vault with the media set to which you want to send media. ■ Specify the amount of time to wait between when the media is allocated and when it is sent to the vault. ■ Specify the amount of time to wait between returning the media from the vault and when it was last written to. See “Default media vaults” on page 388. Backup Exec does not update the vault automatically. You must use the Configure Storage wizard to update the location of the tape media. You can also print or view the reports that contain details on which media are ready to be moved to and from the vault. See “Updating the tape media location in media vaults” on page 391. 390Tape storage Default media vaults
- 391. To create media vault rules to move tape media to and from media vaults 1 On the Storage tab, expand All Media Sets. 2 Right-click Keep Data for 4 Weeks, Keep Data Infinitely - Do Not Allow Overwrite, or a media set that you created, and then click Details. 3 In the left pane, click Properties. 4 Select the media vault that you want to use with the media set. 5 Specify when to move the media to the vault and when to return the media to the media set. Updating the tape media location in media vaults You can update the location of tape media that are in vaults. You can also print the reports that detail which media are ready to move to and return from the vault. However, you must physically collect the media, and move the media to and from the vault. See “Default media vaults” on page 388. To update the tape media location in media vaults 1 On the Storage tab, expand Tape Cartridge Media Sets and Vaults, and then double-click All Media Vaults. 2 Right-click the media vault for which you want to update the media location, and then click Update vault using wizard. 3 Follow the on-screen prompts. Deleting a media vault You can only delete an empty media vault. If any tape media in the vault, you must move it before you can delete the vault. You cannot delete the online media vaults or the offline media vaults. See “Default media vaults” on page 388. To delete a media vault 1 On the Storage tab, expand All Media Vaults. 2 Right-click the media vault that you want to delete, and then click Delete. 3 Click Yes when you are prompted to delete the media vault. 391Tape storage Default media vaults
- 392. Moving tape media to a vault You can use a barcode scanner to enter the media labels of tape media that you want to move to a vault. You can also type a media label into the dialog box. See “Default media vaults” on page 388. To move tape media to a vault 1 On the Storage tab, expand Tape and Disk Cartridge Media , and then double-click All Media Vaults. 2 Right-click the media vault that you want to move media to, and then click Move media to vault. 3 Follow the on-screen prompts. Retiring damaged tape media You can retire damaged tape media so that Backup Exec does not use it for backup jobs. You should associate tape media that meets or exceeds the discard thresholds that are determined by the media manufacturer with the Retired Media media set. Backup Exec tracks the soft errors that are generated by the storage device firmware. Media that exceed acceptable levels of these errors are reported as potential candidates to be discarded. To decide which tape media to retire, run a Media Errors report for the total number of errors for media, or view the properties for a specific media. Associate any media with an unacceptable level of errors to Retired Media so that you are protected against using defective media before critical backup operations begin. After you associate tape media with the Retired Media set, it is not used by Backup Exec for future backup jobs. The media is still available to be restored from if it is not damaged. To retire damaged tape media 1 On the Storage tab, expand Tape and Disk Cartridge Media. 2 Right-click Online Tape Media, and then click Details. 3 Right-click the media that you want to retire, and then click Retire. 4 Click Yes when you are prompted to retire the media. See “Deleting tape media” on page 393. See “Media Errors report” on page 663. 392Tape storage Retiring damaged tape media
- 393. Deleting tape media When you delete tape media from Backup Exec, all records of the media are removed from the Backup Exec database. These records include catalog information, media statistics, and other information that is associated with the tape media. You can only delete media when it belongs to the Retired Media set. You may want to delete tape media when the following occurs: ■ You have a lot of off-site media that you do not want to recycle. ■ You throw away damaged or old media. If you import deleted media back into Backup Exec, it is added to either the Backup Exec and Windows NT Media media set or the Foreign Media media set. Before you can restore from the media, you must catalog it. To delete tape media 1 On the Storage tab, expand Tape and Disk Cartridge Media. 2 Expand All Media Sets, right-click Retired Media, and then click Details. 3 Right-click the media that you want to delete, and then click Delete. 4 Click Yes when you are prompted to delete the media. See “Retiring damaged tape media” on page 392. Erasing tape or disk cartridge media You can erase tape media or disk cartridge media immediately, or you can schedule the erase operation. Warning: The erase operation is run on whatever media is in the drive or slot at the time when the operation runs. If the media has been changed since the last inventory operation was run, the media label that appears on the Backup Exec Administration Console may not match the media in the selected drive or slot. If media is moved unexpectedly, data loss can occur. Check any scheduled erase jobs carefully. 393Tape storage Deleting tape media
- 394. Table 10-8 Erase operations DescriptionErase operation Writes an indicator at the beginning of the media that makes the data that is contained on the media inaccessible. For most uses, the Erase media now operation is sufficient. This is the only erase operation available for disk cartridge media. Erase media now Instructs the drive to physically erase the entire media. If you have sensitive information on the media and you want to dispose of it, use the Long erase media now operation. A long erase operation on a media will take several hours to complete depending on the drive and the media capacity. Some devices do not support a long erase operation. Long erase media now Let you schedule either an Erase or Long erase operation, and lets you choose notification options. Schedule The erase operation does not change the media label. To change a tape media label, either run a Label operation or rename the media before you run an Erase operation. You cannot cancel an Erase operation after it has started. You can cancel an Erase operation that is scheduled or queued. When you schedule an erase operation, you can configure the time and frequency that you want to run the job. To erase tape or disk cartridge media now 1 On the Storage tab, right-click the drive or the robotic library slot that contains the media that you want to erase. 2 Click Erase media now, and then do one of the following: Click Erase media now.To run an erase operation immediately Click Long erase media now.To run a long erase operation immediately 3 Click Yes when you are prompted to erase the media. 394Tape storage Erasing tape or disk cartridge media
- 395. To schedule an erase operation for tape or disk cartridge media 1 On the Storage tab, right-click the drive or the robotic library slot that contains the media that you want to erase. 2 Click Erase media now, and then do one of the following: Click Schedule erase.To schedule an erase operation Click Schedule long erase.To schedule a long erase operation 3 Click Yes when you are prompted to erase the media. 4 To send notification when the job completes, in the left pane, click Notification and select the appropriate options. 5 To schedule the job, in the left pane, click Schedule and select the appropriate options. See “Scheduling a storage operation job” on page 416. 6 Click OK. About cataloging tape or disk cartridge media that contains encrypted backup sets When you catalog tape media or disk cartridge media that contains encrypted backup sets, Backup Exec attempts to find valid encryption keys for the sets in the Backup Exec database. If Backup Exec does not find a valid key, it issues an alert that instructs you to create one. After you create a valid key, you can respond to the alert to retry cataloging the encrypted set. Alternatively, you can skip the encrypted set and continue to catalog the rest of the media, or cancel the catalog job. See “Encryption key management” on page 578. Associating tape media with a media set When you create a backup job to tape media, the default media set that Backup Exec selects for you is called Keep Data for 4 Weeks. You can select other media sets when you create the backup job, or you can associate the tape media with another media set later. When you associate tape media with a media set, the tape uses the following properties of that media set: 395Tape storage About cataloging tape or disk cartridge media that contains encrypted backup sets
- 396. ■ Append periods ■ Overwrite protection periods ■ Media vaults ■ Amount of time to move media to and from the media vault. Note: You should not associate scratch or imported media with a media set. Backup Exec automatically associates scratch or imported media with a media set when a backup job requires it. See “Creating media sets for tapes” on page 374. To associate tape media with a media set 1 On the Storage tab, expand Tape and Disk Cartridge Media. 2 Double-click All Tape Media to display a list of media. 3 Right-click the tape media that you want to associate with a media set, and then click Associate with media set. 4 Select a media set from the drop-down list, and then click OK. See “Default media sets” on page 367. Editing tape media properties You can view tape media properties and edit some properties. See “Managing tapes” on page 366. To edit tape media properties 1 On the Storage tab, double-click the drive that contains the media. 2 In the left pane, click Media Properties. 396Tape storage Editing tape media properties
- 397. 3 Change any of the following options: Displays the media label that Backup Exec assigns automatically, or that the administrator assigned, or that is a pre-assigned barcode label. You can edit the media label, which is limited to 32 characters. Editing the label changes the name of the media in the display, but does not write the new label to the media until an overwrite operation occurs. When you edit a media label, try to make it a concise identifier that remains constant even when the media is reused. You should write this media label on a label that is fixed to the outside of the physical media. Duplicate labels can be automatically generated. For example, reinstalling Backup Exec or bringing media from another Backup Exec installation can cause duplication in labels. Duplicate labels are allowed, but not recommended. If a barcode is available, and a bar code-equipped device is used, then the media label automatically defaults to that barcode. Media label Displays the original media label if the media is imported media. You can edit the media description, which is limited to 128 characters, to make it a more descriptive label. Media description Keeps the media description when you select Yes in the drop-down box. The media description is kept until an overwrite backup job runs or an erase or label storage operation job runs. By default, the media description is not retained. This option is set toNo by default. Preserve description 4 Click Apply. 397Tape storage Editing tape media properties
- 398. Tape media rotation strategies Many tape media rotation strategies exist that you can use to back up your data. The most commonly used tape media rotation strategies include the following: ■ Son, which uses the same tape each day to run a full backup. ■ Father/Son, which uses multiple tapes, and includes a combination of weekly full and daily differential or incremental backups for a two-week schedule. This strategy provides backups for off-site storage . ■ Grandfather, which uses multiple tapes, and includes a combination of weekly and monthly full and daily differential or incremental backups. This strategy also provides backups for off-site storage. Son media rotation strategy The Son media rotation strategy requires the following: Table 10-9 Son media rotation strategy DescriptionItem 1 (minimum)Number of media required Last backupOverwrite protection period The Son strategy involves performing a full backup every day. Figure 10-3 Son backup strategy Week 1 Media 1 Media 1 Media 1 Media 1 Media 1 TueMon Wed Thu Fri Full Backup Although the Son strategy is easy to administer, backing up with a single media is not an effective method of backup. Magnetic media eventually wears out after many uses and the data you can restore only spans back to your last backup. 398Tape storage Tape media rotation strategies
- 399. Father/Son media rotation strategy The Father/Son media rotation strategy requires the following: Table 10-10 Father/Son media rotation strategy DescriptionItem 6 (minimum)Number of media required Two weeksOverwrite protection period The Father/Son media rotation strategy uses a combination of full and differential or incremental backups for a two-week schedule. In the Father/Son scenario, four media are used Monday through Thursday for differential or incremental backups. The other two media containing full backups are rotated out and stored off-site every Friday. The Father/Son strategy is easy to administer and lets you keep data longer than the Son strategy. The Father/Son strategy is not suitable for the stringent data protection needs of most network environments. When this backup strategy is first implemented, you must start with a full backup. Figure 10-4 Father/Son backup strategy Week 1 Media 1 Media 2 Media 3 Media 4 Media 5 TueMon Wed Thu Fri Full Backup Media 6 Media 4 Media 3 Media 2 Media 1 Week 2 Incremental or Differential Backup Grandfather media rotation strategy The Grandfather media rotation strategy requires the following: 399Tape storage Tape media rotation strategies
- 400. Table 10-11 Grandfather media rotation strategy DescriptionItem 19 (minimum)Number of media required One yearOverwrite protection period The Grandfather method is one of the most common media rotation strategies. The Grandfather method is easy to administer and comprehensive enough to allow easy location of files when they need to be restored. In the Grandfather scenario, four tapes are used Monday through Thursday for incremental or differential backups; another three tapes are used every Friday for full backups. The remaining 12 media are used for monthly full backups and are kept off-site. 400Tape storage Tape media rotation strategies
- 401. Figure 10-5 Grandfather backup strategy Week 1 Mon 1 Tue 2 Wed 3 Thu 4 Fri 5 TueMon Wed Thu Fri Full Backup Fri 7 Thu 4 Wed 3 Tue 2 Mon 1 Week 3 Incremental or Differential Backup Tue 2 Thu 4 Fri 6Wed 3Mon 1 Week 2 Tue 2 Thu 4 MonthlyWed 3Mon 1 Week 4 The Grandfather strategy is recommended because it offers a good media number to storage life ratio (19 media/1 year). You can easily incorporate more media. For example, you can perform a full backup on the last Saturday of the month to keep permanently. 401Tape storage Tape media rotation strategies
- 402. Storage device pools This chapter includes the following topics: ■ Creating storage device pools ■ Specifying a default selection method for a device in a storage device pool ■ Viewing jobs, job histories, and active alerts for a storage device pool ■ Adding or removing devices in a storage device pool Creating storage device pools A storage device pool is a group of similar types of storage devices that enables load-balancing of Backup Exec jobs. The workload is shared across the storage device pool. You can send backup jobs to specific storage devices or to a storage device pool. By default, if the specific storage device is busy, the job must wait until the storage device becomes available. When you send a job to specific storage devices, Backup Exec cannot automatically route the job to the next available storage device. When you submit a backup job to a storage device pool, by default the job is sent to the first available storage device in that pool. As other jobs are created and started, they can run concurrently on other storage devices in the storage device pool. By dynamically allocating storage devices as jobs are submitted, Backup Exec processes jobs quickly and efficiently. Storage device pools provide fault tolerance if you configure error-handling rules to resubmit a job that fails because of a storage device error. You can change the default selection method for a device in a storage device pool so that jobs are sent first to one of the following devices in the storage device pool: ■ A storage device with the least amount of free space. This setting is beneficial for manual offsite rotation strategies since the job runs to the same device until the device is full. 11Chapter
- 403. ■ A storage device with the most amount of free space. This setting is beneficial for a backup that has Granular Recovery Technology (GRT) enabled, and is sent to a disk storage device pool. GRT jobs that are sent to disk storage devices cannot span. Note: You must use the Backup Exec Management Command Line Interface to change the default to specify whether jobs are sent to a device that has the most or least free space. See “Specifying a default selection method for a device in a storage device pool” on page 405. Backup Exec creates and maintains system-defined storage device pools for disk storage, tape drives, disk cartridges, and virtual disks. Any storage devices that you configure or that you attach are automatically added to the appropriate system-defined storage device pool. You can select these storage device pools when you select the storage for a backup job. You cannot edit a system-defined storage device pool. Before you can view the default storage device pools on the Storage tab, under All Storage Pools, you must create a storage device pool. If you have the Central Admin Server Option installed, you can create managed Backup Exec server pools. Table 11-1 System-defined storage device pools maintained by Backup Exec DescriptionSystem-defined storage device pools that are maintained by Backup Exec Contains the fixed-disk storage.Any disk storage Contains the tape drives. Backup Exec creates this pool when it detects an attached tape drive or robotic library. In a tape drive storage pool, Backup Exec uses the oldest recyclable media first. Any tape drive Contains the disk cartridges that you have configured to use as storage. Backup Exec creates this pool the first time that you configure disk cartridge storage. Any disk cartridge Contains the virtual disks that are on storage arrays. Backup Exec creates this pool when you install the Storage Provisioning Option. Any virtual disk 403Storage device pools Creating storage device pools
- 404. For storage device pools that you create, you must edit the properties of the pool and check the check box next to the device before jobs can use that device in the pool. Use the Configure Storage wizard to create storage device pools. To create a storage device pool 1 On the Storage tab, in the Configure group, click Configure Storage. 2 Do one of the following: Select Storage pools, and then click Next.If the Central Admin Server Option is not installed Do the following in the order listed: ■ Select the Backup Exec server that you want to configure storage for, and then click Next. ■ Select Storage pools, and then click Next. If the Central Admin Server Option is installed 3 Select Storage device pool, and then click Next. 4 Enter a name and description for the pool, and then click Next. 5 Click the drop-down arrow, select the type of storage device pool that you want to configure, and then click Next. 6 Select all of the storage devices that you want to include in the pool, and then click Next. 7 Review the storage configuration summary, and then do one of the following: Do the following in the order listed: ■ Click the heading that contains the items that you want to change. ■ Make any changes, and then click Next until the summary appears. ■ Click Finish. To change the configuration Click Finish.To configure the storage device pool See “Adding or removing devices in a storage device pool ” on page 406. See “How to use Backup Exec server pools in CASO ” on page 1150. See “Adding or removing devices in a storage device pool ” on page 406. 404Storage device pools Creating storage device pools
- 405. See “Error-handling rules for failed or canceled jobs” on page 259. Specifying a default selection method for a device in a storage device pool The default selection method for a storage device pool is the first available storage device in a pool. You can use the Backup Exec Management Command Line Interface to specify another default selection method for a disk-based storage device pool. You can change the default setting of an existing storage device pool, or a storage device pool that Backup Exec creates. You can change the default so that jobs are first sent to one of the following devices: ■ A storage device with the least amount of free space. This setting is beneficial for manual off-site rotation strategies since the job runs to the same device until the device is full. ■ A storage device with the most amount of free space. This setting is beneficial for a backup job for which Granular Recovery Technology (GRT) is enabled, and that is sent to a disk storage device pool. A GRT job cannot span when it is sent to a disk storage device. The Backup Exec Management Command Line Interface commands are as follows: ■ New-BEStorageDevicePool sets the device selection method for a new disk-based storage device pool when you create it. ■ Set-BEStorageDevicePool sets the device selection method for an existing disk-based storage device pool. For information on how to use the Backup Exec Management Command Line Interface and the commands, view the help file named BEMCLI, located in the default installation location: C:Program FilesSymantecBackup Exec See “Creating storage device pools” on page 402. Viewing jobs, job histories, and active alerts for a storage device pool You can view the jobs that are sent to a storage device pool, and the job histories as well as any active alerts. You must create a storage pool to enable All Storage Pools to appear on the Storage tab. See “How to monitor and manage jobs in Backup Exec” on page 240. 405Storage device pools Specifying a default selection method for a device in a storage device pool
- 406. See “Alerts and notifications in Backup Exec” on page 273. To view jobs, job histories, and active alerts for a storage device pool 1 On the Storage tab, expand All Storage Pools. 2 Right-click the storage device pool for which you want to view the jobs, and then click Details. 3 In the left pane, click Jobs, Job Histories, or Active Alerts. Adding or removing devices in a storage device pool You can add or remove devices in a storage device pool. Only similar types of storage devices can belong to the same storage device pool. You cannot edit a system-defined storage device pool, such as.Any disk storage, or Any disk cartridge storage. You must create a storage device pool before All Storage Pools appears on the Storage tab. See “Creating storage device pools” on page 402. Note: To view or change the default device selection method for a storage device pool, you must use the Backup Exec Management Command Line Interface. See “Specifying a default selection method for a device in a storage device pool” on page 405. To add or remove devices in a storage device pool 1 On the Storage tab, expand All Storage Pools. 2 Double-click the storage pool for which you want to add and remove devices. 3 In the left pane, click Properties. 4 Do one or both of the following: Do the following in the order listed: ■ Click Add. ■ Select the devices that you want to add, and then click OK. To add a storage device to the pool Select the device that you want to remove, and then click Remove. To remove a storage device from a pool 5 Click Apply. 406Storage device pools Adding or removing devices in a storage device pool
- 407. Storage operations This chapter includes the following topics: ■ About storage operation jobs ■ Storage tab overview in Backup Exec ■ Using the Configure Storage wizard ■ Viewing details for multiple storage devices ■ Sending a notification when a scheduled storage operation job completes ■ Scheduling a storage operation job ■ Editing global settings for storage ■ Sharing storage devices ■ Deleting a storage device ■ Changing the state of a storage device to online ■ Renaming a storage device ■ Viewing jobs, job histories, backup sets, and active alerts for storage devices ■ Cataloging a storage device ■ Scanning a storage device ■ Inventorying a storage device ■ Inventorying and cataloging a storage device ■ Pausing and unpausing a storage device ■ Disabling and enabling a storage device 12Chapter
- 408. ■ Initializing a robotic library ■ Formatting a tape as a WORM tape ■ Retensioning a tape ■ Formatting a tape in a tape drive ■ Ejecting media from a disk cartridge or tape drive ■ Cleaning a robotic library drive ■ Importing media to Backup Exec ■ Exporting media and expired media ■ Locking and unlocking the robotic library’s front portal ■ Backup Exec server and storage device states About storage operation jobs Backup Exec provides the storage operations that help you manage storage devices and media. You can perform most storage operations by right-clicking the storage device, and then selecting the operation. Only the storage operations that are supported for that storage device or media are available on the right-click menu. Not all storage operations are available for all devices. Backup Exec treats virtual tape libraries and simulated tape libraries as physical robotic libraries. You can identify virtual tape libraries by the label VTL that displays on a library's properties pages. You can identify simulated tape libraries by the label TLS (Tape Library Simulator Utility).The virtual tape libraries and simulated tape libraries do not support all of the storage operations that are available for physical robotic libraries. You can schedule some storage operations as recurring jobs. You can specify a schedule and a recipient for notification when these jobs run. You can view all active and scheduled storage operations, and histories of storage operations on the Job Monitor tab. See “Scheduling a storage operation job” on page 416. See “Sending a notification when a scheduled storage operation job completes” on page 416. 408Storage operations About storage operation jobs
- 409. Storage tab overview in Backup Exec On the Storage tab, Backup Exec provides overview information for each storage device that you configure. You can view details for each storage device. If you want to view details for all of the storage devices on a server, you can select multiple storage devices. See “Viewing details for multiple storage devices” on page 415. You can customize the columns that appear in the All Storage view. Different columns are available from the Tree view and from the List view. Depending on the view that you select and the storage devices that are available, only some of the columns described in the following table may appear. See “How to sort, filter, and copy information on the Backup Exec Administration Console” on page 123. Table 12-1 All Storage overview DescriptionItem Indicates the name of the storage device. By default, Backup Exec provides a name for the storage device based on the type of storage and an incrementing number, such as Disk storage 0001. You can change the name of the storage device in the storage properties. See “Renaming a storage device” on page 434. Name Indicates the state of the storage device, such as if it is online, offline, disabled, or if services need to be restarted. See “Backup Exec server and storage device states” on page 459. State Identifies the parent device if there is a relationship between devices. Examples include a relationship between a tape library and a tape drive, or between a storage array and a virtual disk. This column only appears if you select the List view from the Views group at the top of the window. Parent Device Identifies the Backup Exec server on which you configured the storage device. If you share the device between multiple Backup Exec servers, the device displays for each Backup Exec server. This column only appears if you select the List view from the Views group at the top of the window. Backup Exec Server 409Storage operations Storage tab overview in Backup Exec
- 410. Table 12-1 All Storage overview (continued) DescriptionItem Displays the type of storage that is associated with the device. The storage type can include tape drives, robotic libraries, disk storage, media sets, media vaults, and so on. This column only appears if you select the List view from the Views group at the top of the window. Storage Type Indicates that an event or condition in Backup Exec has occurred for which a message is displayed or a response is required. See “Alerts and notifications in Backup Exec” on page 273. Active Alerts Indicates the estimate for the number of days of storage that is left for disk storage and virtual disk storage. See “Storage trending statuses for disk storage and virtual disks” on page 303. Storage Trending 410Storage operations Storage tab overview in Backup Exec
- 411. Table 12-1 All Storage overview (continued) DescriptionItem Displays storage capacity. Backup Exec provides overview information of used and free storage capacity, as well as capacity details for each storage that you configure. Storage capacity information is rolled up for any items that are collapsed under a storage type, such as a robotic library. The information that displays in the Capacity column includes all of the storage capacity of all of the collapsed items. When you expand the items, individual storage capacity information displays. Before capacity information can display for storage, you must inventory and catalog the storage. You can view storage capacity in the following places: ■ On the Storage tab, in the Capacity column. When you hover the mouse over the capacity bar, additional details display in the tool tip. ■ On the Backup and Restore tab, when you specify the storage for a backup job. ■ On the Home tab, in Storage Status. ■ On the Storage tab, when you view properties for disk storage devices. For disk storage and disk cartridge storage, you can set the thresholds for low disk space on the device property pages. See “Editing disk storage properties” on page 308. See “Editing disk cartridge properties” on page 316. See “How Backup Exec catalogs work” on page 235. See “Inventorying a storage device” on page 437. Capacity Displays the total amount of storage space that is available on the device. For disk storage, this column indicates the size of the volume on which the disk storage is located. For disk cartridge storage, this column indicates the size of the cartridge in the disk cartridge. For tapes, this column indicates the used native capacity and total native capacity of the media. Total Capacity Displays the amount of space that is used as storage, after any compression or deduplication operations have occurred. Used Space 411Storage operations Storage tab overview in Backup Exec
- 412. Table 12-1 All Storage overview (continued) DescriptionItem Displays how much raw backup data is backed up, before compression or deduplication have occurred. For example, if you back up 100 MB of data ten times to a deduplication disk folder, the used space is 100 MB but the amount of the backup data written is 1 GB. Backup Data Written Displays the difference between Total Capacity and Used Space. Available Space Displays the difference as a percentage between Total Capacity and Used Space. % of Available Space Displays the number of storage operation jobs, backup jobs, and restore jobs that are running on this device. Click the text in this column to see more details of all jobs that are running or that are scheduled to run. Active and Scheduled Jobs Displays the ratio of the uncompressed size of a file over its compressed size. Compression Ratio Disiplays the average speed of the jobs that run on this device. Average job rate Using the Configure Storage wizard Use the Configure Storage wizard to set up different types of storage to which you can back up data. The Configure Storage wizard creates the storage with the best possible defaults for your environment. However, you can customize all of the device's setting in the device properties. You can find a list of compatible types of storage devices in Backup Exec's Hardware Compatibility List: http://entsupport.symantec.com/umi/V-269-2 Click Configure Storage on the Storage tab to start the Configure Storage wizard. After Backup Exec is installed and the Backup Exec services are started, any storage that is attached to the Backup Exec server is automatically detected. However, you must use the Configure Storage wizard to configure the storage for backups. 412Storage operations Using the Configure Storage wizard
- 413. Table 12-2 Storage that you can configure in the Configure Storage wizard DescriptionType of storage Storage that remains attached to the server. Types of disk-based storage include the following: ■ Disk storage A location on a locally attached internal hard drive, a USB device, a FireWire device, or a NAS (network-attached storage) device. See “Configuring disk storage” on page 305. ■ Disk cartridge storage Storage that usually remains attached to the server while you remove the media. Disk cartridges use disk cartridge media such as an RDX device, or devices that appear in Windows as removable storage. See “Configuring disk cartridge storage” on page 315. ■ Deduplication disk storage A location on a hard drive that reduces the size of backups by storing only unique data. See “Creating or importing deduplication disk storage” on page 806. ■ Storage arrays See “Features of the Storage Provisioning Option” on page 1287. Disk arrays that contain multiple disk drives that support data redundancy and failover. ■ Virtual disks Virtual disk storage that consists of multiple physical disks in a storage array. See “About virtual disks in the Storage Provisioning Option” on page 1292. ■ Vault store Disk storage for the archived data that the Backup Exec Archiving Option archives from one server. See “About vault stores in the Archiving Option” on page 1349. Disk-based storage 413Storage operations Using the Configure Storage wizard
- 414. Table 12-2 Storage that you can configure in the Configure Storage wizard (continued) DescriptionType of storage Network storage includes the following: ■ NDMP servers Network attached storage (NAS) that supports the Network Data Management Protocol to allow the use of devices that are attached to the servers. See “Features of the NDMP Option” on page 1184. ■ OpenStorage devices Network-attached storage that supports Symantec's OpenStorage technology. See “Configuring an OpenStorage device” on page 801. ■ Remote Media Agent for Linux Storage that lets you back up data from remote computers to the storage devices that are directly attached to a Linux server. You can also back up to a simulated tape library on a Linux server. See “About the Remote Media Agent for Linux ” on page 1258. Network storage Tape storage includes the following: ■ Stand-alone tape drives Storage that uses a tape cartridge for reading and writing data. See “Support for tape drives and robotic libraries” on page 344. ■ Robotic libraries Storage that contains tape drives, slots, and an automated method for loading tapes. See “Robotic libraries in Backup Exec” on page 353. ■ Barcode rules See “Configuring barcode rules for a robotic library ” on page 355. ■ Virtual tape libraries (VTLs) See “About the Virtual Tape Library Unlimited Drive Option ” on page 345. Tape storage 414Storage operations Using the Configure Storage wizard
- 415. Table 12-2 Storage that you can configure in the Configure Storage wizard (continued) DescriptionType of storage Storage pools include the following: ■ Storage device pools ■ Managed Backup Exec server pools See “Creating storage device pools” on page 402. Storage pools Media sets and vaults are for tape media only, and include the following: ■ Append period ■ Overwrite protection period ■ Vaulting rules You can also run wizards to update media vaults. See “Managing tapes” on page 366. Media sets and vaults Archiving lets you configure the following items that are required when you use the Archiving Option: ■ Vault stores ■ Vault store partitions See “About vault stores in the Archiving Option” on page 1349. See “About vault store partitions in the Archiving Option” on page 1352. Archiving See “About storage operation jobs” on page 408. Viewing details for multiple storage devices You can select multiple storage devices for which you want to view all jobs, job histories, and active alerts. Viewing details for multiple storage devices lets you see all of the activity for a specific Backup Exec server. See “Storage tab overview in Backup Exec” on page 409. 415Storage operations Viewing details for multiple storage devices
- 416. To view details for multiple storage devices 1 On the Storage tab, Shift + click or Ctrl + click the storage devices, and then right-click one of the selected storage devices. 2 Click Details. 3 In the left pane, click Jobs, Job History, or Active Alerts. Sending a notification when a scheduled storage operation job completes You can assign recipients to be notified when a scheduled storage operation job completes. Recipients must be set up before you can set up notification. See “About storage operation jobs” on page 408. To send a notification when a scheduled storage operation job completes 1 Create a new scheduled storage operation job or edit an existing one. See “About storage operation jobs” on page 408. 2 On the storage operation job dialog box, in the left pane, click Notification. 3 Select the check box for each recipient that you want to notify when each type of storage operation job completes. 4 You can continue selecting other options, or click OK. See “Scheduling a storage operation job” on page 416. Scheduling a storage operation job When you schedule a storage operation job, you can configure the time and frequency that you want to run the job. See “About storage operation jobs” on page 408. To schedule a storage operation job 1 On the Storage tab, right-click the device for which you want to schedule a storage operation job. If the storage operation can be scheduled, a small arrow appears next to the operation name. 2 Click the storage operation, and then click Schedule. 3 On the storage operation job dialog box, in the left pane, click Schedule. 416Storage operations Sending a notification when a scheduled storage operation job completes
- 417. 4 Select any of the following options: Specify a recurrence schedule for the job.Recurrence Create a recurrence pattern that is measured in hours or minutes. When you select Hours, you can configure the following options: ■ Every X hour/minute Indicates the number of hours or minutes between the start time of a job and the start time of the next job instance. ■ From Designates the starting time for a job to run. ■ Between Restricts the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday. The start time and end time can span a maximum of 24 hours, however they can cross over midnight into the following day. Hours Create a recurrence pattern that is measured in days. When you select Days, you must choose between the following options: ■ Every X day Indicates the number of days between the start time of a job and the start time of the next job instance. ■ Every weekday Specifies that the job should run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays. Days 417Storage operations Scheduling a storage operation job
- 418. Create a recurrence pattern that is measured in weeks. When you create a recurrence pattern that is measured in weeks, you must configure the Every X week on field. The Every X week on specifies the number of weeks between the start time of a job and the start time of the next job instance. It also specifies the days of the week on which the job should run. Weeks 418Storage operations Scheduling a storage operation job
- 419. Months 419Storage operations Scheduling a storage operation job
- 420. Create a recurrence pattern that is measured in months. When you select Months, you must choose between the following options: ■ Day X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Every X X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Selected days of the month Specifies the weeks and days of the month on which Backup Exec runs the job. You select the days and weeks on a grid. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current week and day of the month. For example, if you create the job on the third Monday of the month, the default setting is for the job to run once a month on the third Monday. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. ■ Selected dates of the month Specifies the dates of the month on which Backup Exec runs the job. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current date of the month. For example, if you create the job on the 15th, the default setting is for the job to run once a month on the 15th. 420Storage operations Scheduling a storage operation job
- 421. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. If you select the 31st, the job runs on the last day of the month in months that do not have 31 days. For example, if you configure the job to run on the 31st, in September the job runs on the 30th instead. Create a recurrence pattern that is measured in years. When you select Years, you can configure the following options: ■ Every X year Specifies the number of years between the start time of a job and the start time of the next job instance. ■ On X Specifies the date on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected June 28th in this field, the job runs every 2 years on June 28th. ■ On the X of X Specifies the day and month on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected the fourth Thursday of June in this field, the job runs every 2 years on the fourth Thursday of June. Years Designate the starting time for the first job in the recurrence pattern. at 421Storage operations Scheduling a storage operation job
- 422. View all scheduled jobs on a calendar to check for scheduling conflicts. Calendar Specify the amount of time past the job's scheduled start time at which Backup Exec changes the job completion status to Missed. The job is rescheduled to run based on the time window that you configured. Reschedule the job if it does not start x hours after its scheduled start Specify the amount of time after the job's scheduled start time at which you want to cancel the job if it is still running. Backup Exec changes the job completion status to Canceled, timed out. Cancel the job if it is still running x hours after it scheduled start time Specify dates to include with the job schedule. The job runs on all of the dates that you select using this option, in addition to the dates that are part of its normal schedule recurrence. The job resumes its normal schedule on the next day that it is scheduled after an include date. Include dates with the schedule of this job Specify dates to exclude from the job schedule. The job does not run on any of the dates that you select using this option. It resumes its normal schedule on the next day that a job is scheduled after an excluded date. Exclude dates from the schedule for this job Run the job immediately without scheduling any more instances of it for the future. Run now with no recurring schedule Run the job at the time and date that you specify. Run on 422Storage operations Scheduling a storage operation job
- 423. Create a job without scheduling it. 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 unscheduled until you choose to run it. You can use a third-party job automation or task scheduling tool to run the job later. If you use this option to create a job, you cannot place the job on hold. You cannot place jobs on hold unless they are scheduled. Create without a schedule 5 Click OK. Editing global settings for storage You can edit the global settings that apply to the robotic libraries, tape media, and disk-based storage that are in your environment. To edit global settings for storage 1 Click the Backup Exec button, click Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, click Storage. 3 Select the appropriate options. Enable Backup Exec to inventory all of the slots in a robotic library when Backup Exec services start. Depending on the number of slots and robotic libraries, this process may take a few minutes. This option is not enabled by default. Inventory robotic libraries when Backup Exec services start 423Storage operations Editing global settings for storage
- 424. Select this option to prevent Backup Exec from overwriting tape media that are in media sets and the media that are imported from another installation of Backup Exec or from another product. See “Overwrite protection periods and append periods in media sets” on page 370. This is the safest option to choose because the tape media that is protected cannot be overwritten until one of the following actions occur: ■ The overwrite protection period for the media expires. ■ You move the media that belongs to an active media set to scratch media. ■ You erase, format, or label the media. ■ You move imported media to Scratch Media. Full - protect allocated and imported media Select this option to let Backup Exec overwrite tape media that are imported from another installation of Backup Exec or from another product, or scratch media. Media in a media set that has an overwrite protection period that has not expired (allocated media) cannot be overwritten. Symantec recommends this option if you want to use media from another installation of Backup Exec or from another product This option is enabled by default. Partial - protect only allocated media Select this option to be prompted before Backup Exec overwrites tape media that is imported from another installation of Backup Exec or from another product. You must select the option Partial - protect only allocated media. The job cannot run until you respond to this prompt. Prompt before overwriting imported media 424Storage operations Editing global settings for storage
- 425. Select this option to disable the media overwrite protection feature for media in tape drives. With this option, you are responsible for making sure that the media in tape drives are not accidentally overwritten. When an overwrite job is submitted to a tape drive and the media overwrite protection level is None, the media are overwritten. Note: This option is not recommended because it does not protect data from being overwritten. None Select this option to be prompted before Backup Exec overwrites allocated or imported media in tape drives. If you selected None, Symantec recommended that you select this option to be prompted before overwriting allocated or imported media. The job cannot run until you respond to this prompt. Prompt before overwriting allocated or imported media 425Storage operations Editing global settings for storage
- 426. Select this option to let Backup Exec overwrite scratch media first in a tape drive when an overwrite job occurs. See “How Backup Exec searches for overwritable media in tape drives ” on page 381. If no scratch media are found in any of the tape drives, Backup Exec overwrites recyclable media in the selected media set. If no recyclable media are found in the selected media set, Backup Exec searches for recyclable media in any media set. If no recyclable media are found, Backup Exec automatically searches for other media to overwrite. The media that is overwritten depends on the level of the overwrite protection that you set. If you select this option, more media may be required for the same number of jobs than if you choose to overwrite recyclable media first. This option affects the order in which Backup Exec overwrites media. If you choose to overwrite scratch media first, the recyclable media may be preserved longer for possible recovery. This option is enabled by default. Overwrite scratch media before overwriting recyclable media contained in the targeted media set 426Storage operations Editing global settings for storage
- 427. Select this option to let Backup Exec overwrite recyclable media in a tape drive in the selected media set first when an overwrite job occurs. If no recyclable media are found in any of the tape drives, Backup Exec overwrites scratch media. If no recyclable media or scratch media are found, Backup Exec searches for media to overwrite. The media that is overwritten depends on the level of the overwrite protection that you set. See “How Backup Exec searches for overwritable media in tape drives ” on page 381. If you choose to overwrite recyclable media in the selected media set first, the same media is re-used more frequently than if you choose to overwrite scratch media first. Overwrite recyclable media contained in the targeted media set before overwriting scratch media 427Storage operations Editing global settings for storage
- 428. Select this option to prevent Backup Exec from reclaiming disk space from expired backup sets on any disk-based storage device that is attached after being absent for a number of days. Backup jobs that you send to this device fail. You can change this setting per disk-based storage device in the device's properties. Before you disable this setting, you may want to view the expiration dates of the backup sets and decide if you want to keep some backup sets longer. You can change the expiration date of a backup set, or you can retain a backup set indefinitely. See “Editing disk storage properties” on page 308. See “Backup sets ” on page 329. See “How to restore data from a reattached or reinserted disk-based storage device” on page 314. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Limit Backup Exec to read-only operations on a disk-based storage device if it has been detached for Specify how long before Backup Exec is limited to read-only operations on a disk-based storage device when you reattach it. The default setting is 14 days. Number of days 428Storage operations Editing global settings for storage
- 429. Prevents Backup Exec from reclaiming disk space from expired backup sets on any disk cartridge that is inserted after being absent for a number of days. Backup jobs that you send to this device fail. You can change this setting per disk cartridge in the device's properties. Before you disable this setting, you may want to view the expiration dates of the backup sets and decide if you want to keep some backup sets longer. You can change the expiration date of a backup set, or you can retain a backup set indefinitely. See “Editing disk cartridge properties” on page 316. See “Backup sets ” on page 329. See “How to restore data from a reattached or reinserted disk-based storage device” on page 314. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. Limit Backup Exec to read-only operations on a disk cartridge if it has not been inserted for Specify the number of days that a device can be absent from the Backup Exec server, after which Backup Exec is limited to read-only operations on the device when you re-insert it. The default setting is 30 days. Number of days 429Storage operations Editing global settings for storage
- 430. Allow Backup Exec to delete all expired backup sets 430Storage operations Editing global settings for storage
- 431. Select this option to let Backup Exec delete the last full, incremental, and differential backup sets that are necessary to restore a server if the backup sets have expired. By default, Backup Exec keeps the most recent backup sets that are necessary to restore a server, even if the backup sets expire. If you allow Backup Exec to delete all of the expired backup sets for a server, you may not be able to restore that server. This option is useful if you do not want to keep data after a period of time, usually several years. However, when you enable this option, you can lose backup sets in the following conditions: ■ When the length of time that the backup data or backup sets is kept is less than the frequency of the backup. That is, the backup sets from the last full backup job expire before the next full backup runs. Ensure that when you create jobs, the backup data is kept longer than the amount of time between full backups. ■ When the backup job fails or is missed, and is not rerun before the backup sets expire. Monitor any failed or missed jobs, and ensure that you rerun them before the backup sets from the previous full backup expire. This option is not selected by default. Note: In a Central Admin Server Option (CASO) environment, this option is only available on the central administration server. If you enable this option on the central administration server, DLM deletes all expired backup sets on the central administration server as well as on all of the managed Backup Exec servers. This option deletes all expired backup sets on both centrally managed and locally managed Backup Exec servers in a CASO environment. 431Storage operations Editing global settings for storage
- 432. See “Backup sets ” on page 329. See “How data lifecycle management (DLM) deletes expired backup sets on disk-based storage” on page 322. 4 Click OK. Sharing storage devices In environments in which there is more than one Backup Exec server, those servers can share storage devices. For example, multiple Backup Exec servers in a CASO environment can share storage devices. In these environments, Backup Exec maintains a database of the shared storage device. Otherwise, the backup data that one server submits to the storage device can overwrite the data that another server submits. Note: The Enterprise Server Option must be installed before you can share storage devices between Backup Exec servers. Backup Exec servers can share the following types of storage: ■ Storage that is attached to an NDMP server ■ Deduplication disk storage ■ OpenStorage devices ■ Virtual disks ■ Disk storage ■ Remote Media Agents ■ The Backup Exec agents that are configured to send data directly to storage For disk storage devices and virtual disk, you must specify a UNC path by which the Backup Exec servers can access the storage device. Disk cartridges cannot be shared. When you share a storage device, you can select which Backup Exec servers can access the storage device. The Backup Exec server from which you added the storage device is automatically enabled to share the storage device. However, you can remove the sharing capability from that Backup Exec server at any time. For example, if you add a storage device to a central administration server, then that server can use the storage device. However, if your environment does not allow 432Storage operations Sharing storage devices
- 433. the central administration server to operate as a managed Backup Exec server, then you can remove the sharing capability from the central administration server. If you have multiple Backup Exec servers and multiple types of storage in your environment, you can select a Backup Exec server and manage the storage for it. To share a storage device 1 On the Storage tab, right-click the storage device that you want to share. 2 Click Share. 3 To share a disk storage device or a virtual disk, enter a UNC path by which the servers can access the storage device that you want to share. 4 Check the Backup Exec servers or managed Backup Exec servers that you want to share this storage device. 5 Click OK. Deleting a storage device You can delete a storage device from the Backup Exec database. If the storage device is a legacy backup-to-disk folder, a disk storage device, or a deduplication disk storage device, then Backup Exec prompts you to delete the backup sets from the Administration Console view. You can no longer view or select those backup sets from the Administration Console. However, the backup sets remain on the storage device. You must run inventory and catalog operations on the storage device before you can restore from it. You may want to delete the backup sets from the Administration Console if you move a storage device to another Backup Exec installation. However, if the move is only temporary, then you probably do not want to delete the backup sets. Keeping the backup sets lets you avoid running the inventory and catalog operations on the device when you move it back. You should also keep the backup sets if you plan to recreate the storage device. You can also use Windows Explorer to navigate to a legacy backup-to-disk folder or to a disk storage, and then delete it. If you use this method, then you cannot recreate the storage in Backup Exec. To delete a storage device 1 On the Storage tab, right-click the device that you want to delete, and then click Disable. 2 Rght-click the device again, and then click Delete. 3 When you are prompted to delete the storage device, click Yes. 433Storage operations Deleting a storage device
- 434. See “Disabling and enabling a storage device” on page 439. See “Recreating a legacy backup-to-disk folder and its contents” on page 340. See “Backup sets ” on page 329. Changing the state of a storage device to online Usually, when a device goes offline, an alert appears. The alert message provides a specific reason why the device is offline, and may include a link to the Symantec Knowledge Base for more information. Correct the problem that caused the device to go offline. Then, for tape drives, robotic libraries, and some other types of devices, you must manually change the state of the device to online. For disk storage, disk cartridge, storage arrays, and virtual disk devices, Backup Exec detects that the device is online within five minutes and automatically changes the state to online. See “Troubleshooting hardware-related issues in Backup Exec” on page 680. To change the state of a storage device to online 1 On the Storage tab, right-click the storage device that you want to change to online. 2 Click Offline to clear the check mark. Renaming a storage device You can rename a storage device that is in your environment. You cannot rename system-defined storage device pools, but you can rename any storage device pools that you create. See “About storage operation jobs” on page 408. To rename a storage device 1 On the Storage tab, double-click the storage device that you want to rename. 2 In the storage device properties, in the Name field, type the new name. 3 Click Apply. 434Storage operations Changing the state of a storage device to online
- 435. Viewing jobs, job histories, backup sets, and active alerts for storage devices You can view information that is related to a storage device. See “About storage operation jobs” on page 408. To view jobs, job histories, backup sets, and active alerts for storage devices 1 On the Storage tab, double-click the storage device for which you want to view the job history, backup sets, or active alerts. 2 In the left pane, click Jobs, Job Histories, Backup Sets, or Active Alerts. See “About the Job History” on page 251. See “How to monitor and manage jobs in Backup Exec” on page 240. See “About the Job Monitor” on page 242. See “Alerts and notifications in Backup Exec” on page 273. See “Backup sets ” on page 329. Cataloging a storage device You can run a catalog operation to do the following: ■ Log the contents of a media that was created by another installation of Backup Exec. ■ Create a new catalog on the local hard drive if the catalog for the storage device no longer exists. Before you can restore or verify data on a storage device, a catalog for that device must exist. If Backup Exec has not used this storage device before, you must run an Inventory and Catalog storage operation on the device first. Note: If a media password was used from a previous release of Backup Exec, Backup Exec catalogs the media as if it is not password-protected. Symantec recommends that you encrypt data instead. See “Using encryption with Backup Exec” on page 575. See “Inventorying and cataloging a storage device” on page 438. See “How Backup Exec catalogs work” on page 235. 435Storage operations Viewing jobs, job histories, backup sets, and active alerts for storage devices
- 436. To catalog storage 1 On the Storage tab, right-click the storage device for which you want to create a catalog. 2 Click Catalog. 3 On the catalog dialog box, click General, and then enter a name for the job. 4 Click OK. 5 (Optional) View the job log or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Scanning a storage device The scan operation gets information about the media that are in the slots, including barcode information if it is available. Then, the scan operation updates the Backup Exec database with the latest information about where the media are located. When you change magazines or insert new media in a magazine in a robotic library, use the scan operation to update the slot information. The scan job log reports the barcoded media that are in the drives and portals. If the robotic library is busy, the scan job log may not be able to read the drive and portal status. If the drives and portals can't be read, then none are displayed in the job log. For best results, run the scan when the robotic library is idle. See “About storage operation jobs” on page 408. To scan a storage device now 1 On the Storage tab, right-click the robotic library or slot that you want to scan. 2 Click Scan, and then click Scan now. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. To schedule a scan operation for a storage device 1 On the Storage tab, right-click the robotic library or slot that you want to scan. 2 Click Scan, and then click Schedule. 3 To send notification when the job completes, in the left pane, click Notification and select the appropriate options. 436Storage operations Scanning a storage device
- 437. 4 To schedule the job, in the left pane, click Schedule and select the appropriate options. See “Scheduling a storage operation job” on page 416. 5 (Optional) View the scan job log to see which barcoded media are in the slots, drives, and portals of a robotic library, or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Inventorying a storage device You can run an inventory operation to have Backup Exec read a storage device and update the Backup Exec database with information about the media that is on that device. For robotic libraries, you can inventory all of the slots in the robotic library when you change tapes. You can also select specific slots to inventory. You are not required to re-inventory slots when you add the tapes that Backup Exec requests. For example, if the data that you want to restore is on a tape that is not in the robotic library, you are prompted to insert the correct tape for the restore operation. In this case, you are not required to re-inventory the slot where the tape is inserted. When you add or remove a tape that Backup Exec does not request, you should run an inventory operation on the changed slots. You can select specific slots to inventory. If you swap tapes often, you may want to run an inventory operation on the robotic library magazine each time that you restart the Backup Exec services. For tape drives, you can run an inventory operation to mount the media in tape drives and to read the media label. If you change the media that is in a drive, run an inventory operation so that the current media's label appears in the properties. Otherwise, the previous media continues to appear in the properties. There may be a delay as the media is mounted and inventoried in a robotic library. To inventory a storage device now 1 On the Storage tab, right-click the storage device that you want to inventory. 2 Click Inventory and then click Inventory now again. The inventory operation runs. You can view the job log or click the Job Monitor tab for details about the job. To schedule an inventory job for a storage device 1 On the Storage tab, right-click the storage device that you want to inventory. 2 Click Inventory, and then click Schedule. 437Storage operations Inventorying a storage device
- 438. 3 To send notification when the job completes, in the left pane, click Notification and select the appropriate options. 4 To schedule the job, in the left pane, click Schedule and select the appropriate options. See “Scheduling a storage operation job” on page 416. 5 Click OK. 6 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. See “Inventorying robotic libraries when Backup Exec services start” on page 355. Inventorying and cataloging a storage device You can run the inventory and the catalog operations together on a storage device, if the device supports both operations. See “About storage operation jobs” on page 408. To inventory and catalog a storage device 1 On the Storage tab, right-click the storage device that you want to inventory and catalog. 2 Click Inventory and Catalog. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Pausing and unpausing a storage device You can pause a storage device to prevent scheduled jobs and new jobs from running on the storage while you perform maintenance activities. Active jobs are not affected if they start before the storage device is paused. See “About storage operation jobs” on page 408. 438Storage operations Inventorying and cataloging a storage device
- 439. To pause and unpause a storage device 1 On the Storage tab, right-click the storage device that you want to pause or unpause. 2 Do one of the following: ■ To pause the storage device, click Pause. ■ To unpause the storage device, right-click it, and then click Pause to clear the check mark. Disabling and enabling a storage device You can disable a storage device to prevent new jobs from running on it. Backup Exec does not discover disabled NDMP storage devices when the Backup Exec services start. To disable and enable a storage device 1 On the Storage tab, right-click the storage device that you want to disable or enable. 2 Do one of the following: ■ To disable the storage device, click Disable. ■ To enable the storage device, right-click it, and then click Disable to clear the check mark. Initializing a robotic library You can initialize the robotic library, which sends a startup command to the library. To initialize a robotic library 1 On the Storage tab, right-click the robotic library that you want to initialize. 2 Click Initialize. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. 439Storage operations Disabling and enabling a storage device
- 440. Formatting a tape as a WORM tape You can convert a tape to a write-once, read-many (WORM) tape if the tape drive supports the operation. DLT tape drives support the Format WORM operation. To format a tape as a WORM tape 1 On the Storage tab, right-click the tape drive that contains the tape that you want to convert to a WORM tape. 2 Click Format WORM. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. See “How WORM media is used in Backup Exec” on page 387. Retensioning a tape Before you run a backup job to a tape, you can run the tape in the tape drive from beginning to end at a fast speed. Retensioning helps the tape wind evenly and run more smoothly past the tape drive heads. Refer to the documentation that came with your tape drive to see how often to run this operation. This operation is only available if the tape drive supports retensioning. See “About storage operation jobs” on page 408. To retension a tape 1 On the Storage tab, do either of the following: ■ Right-click the drive that contains the tape that you want to retension. ■ Double-click Slots, and then right-click the slot that contains the tape that you want to retension. 2 Click Retension. 3 (Optional) View the job log or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Formatting a tape in a tape drive Backup Exec can format the tape in a drive if the drive supports formatting. Formatting a tape may take hours. Most tape drives do not support formatting. 440Storage operations Formatting a tape as a WORM tape
- 441. Caution: Formatting erases the tape. All data on the tape is destroyed. The media label that is displayed was read during the last inventory operation. The media label does not change until another inventory operation occurs. If you change the tape that is in the device but do not inventory the device, the media label that displays may not match the actual media that is in the device. See “About storage operation jobs” on page 408. To format a tape in a tape drive 1 On the Storage tab, do either of the following: ■ Right-click the tape drive that contains the tape that you want to format. ■ Double-click Slots, and then right-click the slot that contains the tape that you want to format. 2 Click Format. 3 To format the tape that is displayed, click Yes. 4 (Optional) View the job log or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Ejecting media from a disk cartridge or tape drive Backup Exec can eject the media that is in a disk cartridge or tape drive. Some devices do not support a software-driven media eject. If the media is a tape, the tape is rewound and you may be instructed to manually remove it. See “About storage operation jobs” on page 408. To eject media now from a disk cartridge or tape drive 1 On the Storage tab, right-click the disk cartridge or tape drive that you want to eject the media from. 2 Click Eject and then click Eject now. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. To schedule an eject operation for a disk cartridge or tape drive 1 On the Storage tab, right-click the disk cartridge or tape drive that you want to eject the media from. 2 Click Eject, and then click Schedule. 441Storage operations Ejecting media from a disk cartridge or tape drive
- 442. 3 To send notification when the job completes, in the left pane, click Notfication and select the appropriate options. 4 To schedule the job, in the left pane, click Schedule and select the appropriate options. See “Scheduling a storage operation job” on page 416. 5 Click OK. 6 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Cleaning a robotic library drive You can create and schedule a cleaning job for a robotic library drive. See “About storage operation jobs” on page 408. To create a cleaning job now 1 Ensure that you specify the slot that contains the cleaning tape. See “Defining a cleaning slot ” on page 360. 2 Ensure that the cleaning tape is in the defined cleaning slot and is in the same library that contains the drive that you want to clean. 3 On the Storage tab, right-click the drive that you want to clean, click Clean, and then click Clean now. 4 (Optional) View the job history or click the Job Monitor tab for details about the job. To schedule a cleaning job 1 Ensure that you specify the slot that contains the cleaning tape. 2 Ensure that the cleaning tape is in the defined cleaning slot and is in the same library that contains the drive that you want to clean. 3 On the Storage tab, right-click the drive that you want to clean, click Clean now, and then click Schedule. 4 To send a notification when the job completes, in the left pane, click Notification and select the options you want. 442Storage operations Cleaning a robotic library drive
- 443. 5 To schedule the job, in the left pane, click Schedule and select the options that you want. See “Scheduling a storage operation job” on page 416. 6 Click OK. 7 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Importing media to Backup Exec You can import media to a robotic library to add tapes to Backup Exec, or to import media that is required for a restore job. When you insert media into a robotic library, you must create an import storage operation job. The import storage operation updates the Backup Exec database with the information about the media. Backup Exec associates the media that you import with a system media set. See “Default media sets” on page 367. Note: You should not associate scratch media with a media set that you create. Backup Exec automatically moves the media to the required media set as needed. Before you import media, note the following: ■ If the media does not have a barcode, you must run the Inventory after import operation so that the current media's label appears in the properties. You can only select this operation after you select Import media now. ■ If the robotic library uses a media magazine, ensure that no jobs are currently running. Before you swap the magazine, ensure that all media are ejected from the drive and are back in the magazine slots. You can select any number of slots to import media to. The import storage operation supports robotic libraries with portals. When this storage operation job runs, Backup Exec checks the selected slots for media. If media is found, it is exported to the portals. After all of the media is exported, you are prompted to insert new media into the portal so it can be imported. This process continues until all of the requested media have been imported into the robotic library. You can also run a scan operation to update the slot information when you insert new media in a robotic library. The scan job log reports the barcoded media that are in the drives and portals. 443Storage operations Importing media to Backup Exec
- 444. See “Scanning a storage device” on page 436. To import media now 1 On the Storage tab, do one of the following ■ Expand the robotic library, right-click Slots, and then click Import media now. ■ Right-click the robotic library, and then click Import media now. 2 (Optional) View the job history or click the Job Monitor tab for details about the job. To schedule an import media job 1 On the Storage tab, do one of the following: ■ Expand the robotic library, right-click Slots, and then click Import media now. ■ Right-click the robotic library, and then click Import media now, and then click Schedule. 2 In the left pane, click Storage operations. 3 Click the drop-down menu, and select storage operation that you want to schedule: Updates the Backup Exec database with information about the media. Import Mounts the media in the drive, reads the media label, and updates the Backup Exec database. This operation is necessary for media that do not have barcodes. Inventory after import 4 To send a notification when the job completes, in the left pane, click Notification and select the appropriate options: Show the names of the individual and group recipients. Recipient name Indicate Recipient for an individual recipient or Group for a group recipient. Recipient type Add, edit, or delete recipients.Manage Recipients View or change the properties of a selected recipient. Properties 444Storage operations Importing media to Backup Exec
- 445. 5 To schedule the job, in the left pane, click Schedule and select the appropriate options. Specify a recurrence schedule for the job.Recurrence Create a recurrence pattern that is measured in hours or minutes. When you select Hours, you can configure the following options: ■ Every X hour/minute Indicates the number of hours or minutes between the start time of a job and the start time of the next job instance. ■ From Designates the starting time for a job to run. ■ Between Restricts the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday. The start time and end time can span a maximum of 24 hours, however they can cross over midnight into the following day. Hours Create a recurrence pattern that is measured in days. When you select Days, you must choose between the following options: ■ Every X day Indicates the number of days between the start time of a job and the start time of the next job instance. ■ Every weekday Specifies that the job should run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays. Days 445Storage operations Importing media to Backup Exec
- 446. Create a recurrence pattern that is measured in weeks. When you create a recurrence pattern that is measured in weeks, you must configure the Every X week on field. The Every X week on specifies the number of weeks between the start time of a job and the start time of the next job instance. It also specifies the days of the week on which the job should run. Weeks 446Storage operations Importing media to Backup Exec
- 447. Months 447Storage operations Importing media to Backup Exec
- 448. Create a recurrence pattern that is measured in months. When you select Months, you must choose between the following options: ■ Day X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Every X X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Selected days of the month Specifies the weeks and days of the month on which Backup Exec runs the job. You select the days and weeks on a grid. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current week and day of the month. For example, if you create the job on the third Monday of the month, the default setting is for the job to run once a month on the third Monday. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. ■ Selected dates of the month Specifies the dates of the month on which Backup Exec runs the job. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current date of the month. For example, if you create the job on the 15th, the default setting is for the job to run once a month on the 15th. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. 448Storage operations Importing media to Backup Exec
- 449. If you select the 31st, the job runs on the last day of the month in months that do not have 31 days. For example, if you configure the job to run on the 31st, in September the job runs on the 30th instead. Create a recurrence pattern that is measured in years. When you select Years, you can configure the following options: ■ Every X year Specifies the number of years between the start time of a job and the start time of the next job instance. ■ On X Specifies the date on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected June 28th in this field, the job runs every 2 years on June 28th. ■ On the X of X Specifies the day and month on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected the fourth Thursday of June in this field, the job runs every 2 years on the fourth Thursday of June. Years Designate the starting time for the first job in the recurrence pattern. at View all scheduled jobs on a calendar to check for scheduling conflicts. Calendar Specify the amount of time past the job's scheduled start time at which Backup Exec changes the job completion status to Missed. The job is rescheduled to run based on the time window that you configured. Reschedule the job if it does not start x hours after its scheduled start 449Storage operations Importing media to Backup Exec
- 450. Specify the amount of time after the job's scheduled start time at which you want to cancel the job if it is still running. Backup Exec changes the job completion status to Canceled, timed out. Cancel the job if it is still running x hours after it scheduled start time Specify dates to include with the job schedule. The job runs on all of the dates that you select using this option, in addition to the dates that are part of its normal schedule recurrence. The job resumes its normal schedule on the next day that it is scheduled after an include date. Include dates with the schedule of this job Specify dates to exclude from the job schedule. The job does not run on any of the dates that you select using this option. It resumes its normal schedule on the next day that a job is scheduled after an excluded date. Exclude dates from the schedule for this job Run the job immediately without scheduling any more instances of it for the future. Run now with no recurring schedule Run the job at the time and date that you specify.Run on Create a job without scheduling it. 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 unscheduled until you choose to run it. You can use a third-party job automation or task scheduling tool to run the job later. If you use this option to create a job, you cannot place the job on hold. You cannot place jobs on hold unless they are scheduled. Create without a schedule 6 Click OK 7 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Exporting media and expired media The export media operation supports robotic libraries that have portals. When this operation is run on one or more robotic library slots, the exported media is placed 450Storage operations Exporting media and expired media
- 451. in the portals. If you select more media than there are portals, the robotic library fills as many slots as possible. Then, you are prompted to remove the media from the portal. This process continues until all of the selected media have been removed from the robotic library. You can also export expired media from a robotic library. The export expired media operation lets you automate media handling in robotic libraries. This operation removes the media that Backup Exec cannot write to. You can then use the Import after export operation to add scratch media to the robotic library to prepare for the next backup. After you export the expired media from the robotic library, the expired media appears in Offline Tape. If the media is in a media set that has an applicable vault media rule, then the media appears in the vault location. You can export cleaning media with the export expired media storage operation. You can include all cleaning media, or all cleaning media that has been used more than a specified number of times. See “Importing media to Backup Exec ” on page 443. Note: Not all storage operations are available for all devices. To export media or export expired media 1 On the Storage tab, do one of the following: ■ Expand the robotic library, right-click Slots, and then click Export media. 451Storage operations Exporting media and expired media
- 452. ■ Right-click the robotic library, and then click Export. 2 Do one of the following: Click Export expired media now. The operation runs. You can view the job history for details about the job. To immediately export only the media that Backup Exec cannot write to and place it in the portal Click Export media now. The operation runs. You can view the job history for details about the job. To immediately export the media to the portal Click Import after export. The operation runs. You can view the job history for details about the job. To immediately import media after the export 3 (Optional) View the job history or click the Job Monitor tab for details about the job. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. To schedule an export media or export expired media operation 1 On the Storage tab, do one of the following: ■ Expand the robotic library, right-click Slots, and then click Export media. ■ Right-click the robotic library, and then click Export. 2 Click Schedule. 3 In the left pane, click Storage operations. 452Storage operations Exporting media and expired media
- 453. 4 Click the drop-down menu and select one of the following storage operations that you want to schedule: Places the media into the robotic library's portals. If you select more media than there are portals, the robotic library fills as many slots as possible. Then you are prompted to remove the media from the portal. This process continues until all of the selected media have been removed from the robotic library. Export Adds the scratch media to the robotic library to prepare for the next backup. Import media after export Places the expired media into the robotic library's portals. This operation lets you automate media handling in robotic libraries by removing the media that Backup Exec cannot write to. After you export the expired media from the robotic library, the expired media appears in Offline Tape. If the media is in a media set that has an applicable vault media rule, then the media appears in the vault location. Export expired media 5 To send notification when the job completes, in the left pane, click Notification and select the appropriate options. 6 To schedule the job, in the left pane, click Schedule and select the appropriate options. 7 Click OK. 8 (Optional) View the job history or click the Job Monitor tab for details about the job. Locking and unlocking the robotic library’s front portal By default, the robotic library portal is not locked, even when you run the lock storage operation. For instructions on how to lock the library portal, go to: 453Storage operations Locking and unlocking the robotic library’s front portal
- 454. http://www.symantec.com/docs/TECH67698 You must create a job to unlock the robotic library’s front portal. To unlock the robotic library’s front portal 1 On the Storage tab, right-click the robotic library that has the front portal that you want to unlock. 2 Click Unlock, and then click Unlock now. 3 (Optional) View the job history or click the Job Monitor tab for details about the job. To schedule a job to unlock the robotic library's front portal 1 On the Storage tab, right-click the robotic library that has the front portal that you want to unlock. 2 Click Unlock. 3 Click Schedule. 4 To send notification when the job completes, in the left pane, click Notification and select any of the following options: Show the names of the individual and group recipients. Recipient name Indicate Recipient for an individual recipient or Group for a group recipient. Recipient type Add, edit, or delete recipients.Manage Recipients View or change the properties of a selected recipient. Properties 5 To schedule the job, in the left pane, click Schedule and select the appropriate options. Specify a recurrence schedule for the job.Recurrence 454Storage operations Locking and unlocking the robotic library’s front portal
- 455. Create a recurrence pattern that is measured in hours or minutes. When you select Hours, you can configure the following options: ■ Every X hour/minute Indicates the number of hours or minutes between the start time of a job and the start time of the next job instance. ■ From Designates the starting time for a job to run. ■ Between Restricts the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday. The start time and end time can span a maximum of 24 hours, however they can cross over midnight into the following day. Hours Create a recurrence pattern that is measured in days. When you select Days, you must choose between the following options: ■ Every X day Indicates the number of days between the start time of a job and the start time of the next job instance. ■ Every weekday Specifies that the job should run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays. Days Create a recurrence pattern that is measured in weeks. When you create a recurrence pattern that is measured in weeks, you must configure the Every X week on field. The Every X week on specifies the number of weeks between the start time of a job and the start time of the next job instance. It also specifies the days of the week on which the job should run. Weeks 455Storage operations Locking and unlocking the robotic library’s front portal
- 456. Months 456Storage operations Locking and unlocking the robotic library’s front portal
- 457. Create a recurrence pattern that is measured in months. When you select Months, you must choose between the following options: ■ Day X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Every X X of every X month Specifies the day on which the job should run. It also indicates the number of months between the start time of a job and the start time of the next job instance. ■ Selected days of the month Specifies the weeks and days of the month on which Backup Exec runs the job. You select the days and weeks on a grid. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current week and day of the month. For example, if you create the job on the third Monday of the month, the default setting is for the job to run once a month on the third Monday. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. ■ Selected dates of the month Specifies the dates of the month on which Backup Exec runs the job. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current date of the month. For example, if you create the job on the 15th, the default setting is for the job to run once a month on the 15th. You can change the default or select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. 457Storage operations Locking and unlocking the robotic library’s front portal
- 458. If you select the 31st, the job runs on the last day of the month in months that do not have 31 days. For example, if you configure the job to run on the 31st, in September the job runs on the 30th instead. Create a recurrence pattern that is measured in years. When you select Years, you can configure the following options: ■ Every X year Specifies the number of years between the start time of a job and the start time of the next job instance. ■ On X Specifies the date on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected June 28th in this field, the job runs every 2 years on June 28th. ■ On the X of X Specifies the day and month on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected the fourth Thursday of June in this field, the job runs every 2 years on the fourth Thursday of June. Years Designate the starting time for the first job in the recurrence pattern. at View all scheduled jobs on a calendar to check for scheduling conflicts. Calendar Specify the amount of time past the job's scheduled start time at which Backup Exec changes the job completion status to Missed. The job is rescheduled to run based on the time window that you configured. Reschedule the job if it does not start x hours after its scheduled start 458Storage operations Locking and unlocking the robotic library’s front portal
- 459. Specify the amount of time after the job's scheduled start time at which you want to cancel the job if it is still running. Backup Exec changes the job completion status to Canceled, timed out. Cancel the job if it is still running x hours after it scheduled start time Specify dates to include with the job schedule. The job runs on all of the dates that you select using this option, in addition to the dates that are part of its normal schedule recurrence. The job resumes its normal schedule on the next day that it is scheduled after an include date. Include dates with the schedule of this job Specify dates to exclude from the job schedule. The job does not run on any of the dates that you select using this option. It resumes its normal schedule on the next day that a job is scheduled after an excluded date. Exclude dates from the schedule for this job Run the job immediately without scheduling any more instances of it for the future. Run now with no recurring schedule Run the job at the time and date that you specify.Run on Create a job without scheduling it. 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 unscheduled until you choose to run it. You can use a third-party job automation or task scheduling tool to run the job later. If you use this option to create a job, you cannot place the job on hold. You cannot place jobs on hold unless they are scheduled. Create without a schedule 6 Click OK. See “Viewing jobs, job histories, backup sets, and active alerts for storage devices” on page 435. Backup Exec server and storage device states Backup Exec servers and storage devices display a state that indicates their current condition. 459Storage operations Backup Exec server and storage device states
- 460. Table 12-3 Possible states for Backup Exec servers and storage devices DescriptionState The Backup Exec services and the Backup Exec deduplication services must be restarted. See “Starting and stopping Backup Exec services” on page 614. All the Backup Exec services need to be restarted on <Backup Exec server> The Backup Exec services must be restarted. See “Starting and stopping Backup Exec services” on page 614. An error occurred while discovering this device. Cycle the services on <Backup Exec server> to retry device discovery. The storage device is in use by a job.Active Configuration has failed for a local disk storage device or virtual disk. Configuration failed A local disk storage device or virtual disk is in the process of configuration. Configuring The storage device is disabled and Backup Exec cannot use it. The device is available for other applications. Disabled The storage device'a status was changed to Disabled while a job was running to the device. Disabled; Active The storage device is in a low disk space condition, but is currently in use by a job. Low disk space; Active The storage device has low disk space.Low disk space Communications have stopped between a managed Backup Exec server and a central administration server in a Central Admin Server Option environment. See “What happens when CASO communication thresholds are reached” on page 1145. No communication The disk cannot be configured because it is in a bad state, or it has failed. Not configurable The disk is available for configuration but has not yet been configured. Not configured 460Storage operations Backup Exec server and storage device states
- 461. Table 12-3 Possible states for Backup Exec servers and storage devices (continued) DescriptionState The storage device is offline. A storage device can appear offline if any of the following actions occur: ■ The device was turned off after Backup Exec started. ■ The device was being used by another application when Backup Exec started. ■ The device is removed from the server. ■ The device reports a critical error. ■ The firmware of the device was updated. Usually, when a device goes offline, an alert appears. The alert message provides a specific reason why the device is offline, and may include a link to the Symantec Knowledge Base for more information. Correct the problem that caused the device to go offline. Then, for tape drives, robotic libraries, and some other types of devices, you must manually change the state of the device to online. For disk storage, disk cartridge, storage arrays, and virtual disk devices, Backup Exec detects that the device is online within five minutes and automatically changes the state to online See “Changing the state of a storage device to online” on page 434. Offline The storage device is online.Online The storage device is paused. See “Pausing and unpausing a storage device” on page 438. Paused The storage device is paused, but is currently in use by a job. Paused; Active 461Storage operations Backup Exec server and storage device states
- 462. Table 12-3 Possible states for Backup Exec servers and storage devices (continued) DescriptionState Communications have stalled during communications between a managed Backup Exec server and a central administration server in a Central Admin Server Option environment. See “What happens when CASO communication thresholds are reached” on page 1145. Stalled The Backup Exec deduplication services should be restarted. The deduplication services are separate from the Backup Exec services so the Backup Exec services are not affected. See “Starting and stopping Backup Exec services” on page 614. The Backup Exec deduplication services need to be restarted on <Backup Exec server> The Backup Exec services must be restarted. See “Starting and stopping Backup Exec services” on page 614. The Backup Exec services on <Backup Exec server> need to be restarted A state that can occur after you add a new storage device to Backup Exec. You must restart the Backup Exec services so that the device discovery process can run again. This device has not been discovered correctly. Cycle the services on <Backup Exec server> to retry device discovery. The device has not been initialized.Uninitialized 462Storage operations Backup Exec server and storage device states
- 463. Conversion to virtual machines This chapter includes the following topics: ■ How conversion of physical computers to virtual machines works in Backup Exec ■ Requirements for conversion to virtual machine jobs ■ Converting to a virtual machine simultaneously with a backup job ■ Converting to a virtual machine after a backup job ■ Adding a conversion to virtual machine stage to a backup job ■ Converting to a virtual machine from a point in time ■ Creating a one-time conversion to a virtual machine ■ Setting default options for conversion to virtual machine jobs How conversion of physical computers to virtual machines works in Backup Exec Backup Exec provides the ability to convert a physical computer to a virtual machine in the following ways: ■ Back up a physical computer and simultaneously convert it to a virtual machine. ■ Back up a physical computer and schedule a conversion to a virtual machine to run after the backup job runs. ■ Convert existing backup sets to a virtual machine. 13Chapter
- 464. ■ Convert a running physical computer to a virtual machine without running a backup job. Note: Conversion of a physical Hyper-V host into a virtual machine is not supported. In addition, in a VMware environment, conversion of Windows Server 2012 physical servers that have 4K disks is not supported. The newly created virtual machine is bootable and is identical to the physical computer from which the virtual machine was converted, with the exception of the network cards and settings. Conversion to a virtual machine enables business continuity for both Hyper-V and VMware environments. This topic includes the following information: Conversion to virtual machine options How backup selections are processed during conversion to virtual jobs How full, incremental, and differential backups work in conversion to virtual jobs Conversion of disks or volumes larger than 2 terabytes Notes about conversion to a virtual machine running on a Windows Server 2012 Hyper-V host Notes about conversion of Exchange servers Conversion to virtual machine options You use one of the following options on the Backup and Restore tab to set up a conversion to a virtual machine: 464Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 465. Table 13-1 Conversion to virtual machine options DescriptionName of option These options run the conversion simultaneously with the backup job. Because two operations are performed at the same time, this job may take longer to run than a regular backup job. A large backup window is recommended for this option. A conversion from a full backup creates the new virtual machine. Incremental and differential backups update the virtual machine that was created from the full backup. Note: Incremental backups are preferred over differential backups because the differential backups are inefficient for conversion as compared to incremental backups. Although the backup runs simultaneously with the conversion, the backup is the primary job. Therefore, if the backup fails, then the conversion fails also. However, if the conversion fails, the backup continues to run. For a conversion failure, the job is marked as a success with exceptions. In the case of a failed conversion, the conversion process runs again during the next full backup. See “Converting to a virtual machine simultaneously with a backup job” on page 472. Back up to Disk and Simultaneously Convert to Virtual Machine Back up to Deduplication Disk Storage and Simultaneously Convert to Virtual Machine 465Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 466. Table 13-1 Conversion to virtual machine options (continued) DescriptionName of option These options let you schedule the conversion to run after the backup job. These options require a smaller backup window than the simultaneous conversion options. A conversion from a full backup creates the new virtual machine. Incremental and differential backups update the virtual machine that was created from the full backup. Note: Incremental backups are preferred over differential backups because the differential backups are inefficient for conversion as compared to incremental backups. See “Converting to a virtual machine after a backup job” on page 477. Back Up to Disk and then Convert to Virtual Machine Back Up to Deduplication Disk Storage and then Convert to Virtual Machine A conversion to a virtual machine from a point in time converts existing backup sets from a backup job in which all components that are necessary for a virtual machine conversion were selected. When all necessary components are selected for a backup job, Backup Exec identifies that job as Fully selected and the Simplified Disaster Recovery option has a status of ON. The option to convert to a virtual machine from a point in time is useful in a disaster recovery situation in which you want to quickly recover a failed server. The backup sets contain all of the critical components of the server. Additionally, you can select application data or user data to include in the conversion. Note: The option Convert from Point-in-Time becomes available for selection only after you run at least one full backup that includes all critical system components. See “Converting to a virtual machine from a point in time” on page 488. Convert to Virtual Machine from Point-in-Time 466Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 467. Table 13-1 Conversion to virtual machine options (continued) DescriptionName of option This option converts 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. See “Creating a one-time conversion to a virtual machine” on page 490. One-Time Convert to Virtual Machine You can add a stage to a backup job to convert to a virtual machine. Two types of stages are available: Convert to Virtual Machine After Backup and Convert to Virtual Machine Simultaneously with Backup. See “Adding a conversion to virtual machine stage to a backup job” on page 483. Add Stage Note: Regardless of the option that is used to initiate the conversion, Backup Exec does not power on the virtual machine after creating it. Backup Exec creates a snapshot of the virtual machine at the end of the conversion process. The snapshot is removed before the next job runs as long as the virtual machine is not powered on and the only snapshot on the virtual machine is the one that Backup Exec created. If you want to start using the virtual machine, you must manually remove the snapshot. If the converted virtual machine's host fails and you bring the virtual machine online, the existing conversion job continues to run and then fails. In this situation, you must create a new conversion job. 467Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 468. How backup selections are processed during conversion to virtual jobs When you set up a conversion to virtual job, you select the items to back up before the conversion or simultaneously with the conversion. Backup Exec may automatically exclude or include data in certain situations. The job log lists the items that were excluded from or included in the conversion. Selections are processed as follows: ■ If you exclude a volume from the backup job, then that volume is automatically excluded from the corresponding conversion job. ■ If you include an application in the backup job, the disk and volume on which that application resides are automatically included in the conversion job. ■ If you exclude a volume from the backup, the disk that is part of the volume is automatically excluded if the volume is the only thing on the disk. How full, incremental, and differential backups work in conversion to virtual jobs Conversion-to-virtual-machine jobs create a virtual machine from a full backup. Subsequent incremental and differential backup jobs update the virtual machine that was created by the full backup. Although differential backups are supported for conversion jobs, incremental backups are the preferred method for updating virtual machines. Differential backups are inefficient for conversion when compared to incremental backups. When using the incremental backup method for conversion to virtual machine jobs, keep in mind the following points: ■ Data from volumes is backed up at a filefolder level. Even if only a portion of the file has changed, the entire file is backed up. ■ The entire System State is backed up. Incremental backups are supported only for the system file components of System State; the other System State components are backed up as a full backup. ■ Block-level backup methods must be selected for SQL. After the initial incremental backup runs for SQL, block-level backups are performed for any subsequent full or incremental backups for which the Simplified Disaster Recovery option is ON. Conversion will not be performed if a block-level backup method is not selected. ■ Full backups are always performed for Active Directory. Neither incremental backups nor differential backups are supported for Active Directory. 468Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 469. Conversion of disks or volumes larger than 2 terabytes Backup Exec supports conversion of disks or volumes that are larger than 2 terabytes (TB) for VMware hosts and Hyper-V 2012 hosts. Note: If the boot volume or the system volume on the source physical computer is larger than 2 TB and you are converting to a VMware or Hyper-V 2008 R2 virtual machine, then Backup Exec cannot convert it. A boot volume cannot be split or created as a dynamic spanned volume. This limitation also applies if the boot volume on the source is larger than the destination datastore's maximum supported disk size. Backup Exec converts all disks and volumes on the destination to simple or spanned dynamic volumes. Even if the source disk is a basic disk, the converted disks on the destination will be dynamic. Since Backup Exec supports only simple and spanned dynamic volumes, if the source volume type is striped, mirror, or raid5, then Backup Exec converts that volume to either simple or spanned on the destination. The following additional information applies only to VMware: ■ Conversion of a volume that is larger than 2 TB is supported in the following situations: ■ If the volume is not a boot or system volume ■ If the volume was created on a dynamic disk ■ If the volume is an MBR disk ■ Conversion of GPT disks is not supported, regardless of the size of the volume on the disk. Conversions of GPT disks fail. ■ In situations where the VMware source disk size is larger than the destination datastore's maximum supported size, the source disk is split into multiple disks. Backup Exec splits the disk based on the destination datastore's maximum allowed size. Notes about conversion to a virtual machine running on a Windows Server 2012 Hyper-V host Before you create a job to convert a physical computer to a Windows Server 2012 Hyper-V host, review the following information: ■ Disk data is stored in vhdx files for conversion of a physical computer to a virtual machine running on a Windows Server 2012 Hyper-V host. The vhdx files can have a maximum capacity of 64 TB. The physical computer's disk sector size is maintained during the conversion. 469Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 470. ■ The conversion of physical computers that have simple GPT disks is supported. ■ The conversion of physical computers that have dynamic disks is not supported. ■ Storage Spaces and Storage Pools are not supported. ■ If the physical computer runs Windows Server 2012 with an ReFS volume, conversion to a Windows Server 2012 Hyper-V host is supported. Conversion to any previous versions of a Windows Hyper-V host is not supported, so those jobs fail ■ If the physical computer runs Windows Server 2012 with one or more Windows deduplication volumes, conversion to a Hyper-V host is possible, but it may fail. The converted disk data is not deduplicated. In other words, an unoptimized data transfer is performed. For this reason, the conversion may fail if the amount of unoptimized data is greater than the capacity of the destination volume. Notes about conversion of Exchange servers Backup Exec disables Exchange services on a newly-created virtual machine after a conversion-to-virtual job. If Exchange databases are present on a converted server, after a conversion-to-virtual job you must open the Microsoft Services Control Manager and manually restart the following Exchange services: ■ MSExchangeDagMgmt ■ MSExchangeADTopology ■ MSExchangeAntispamUpdate ■ MSExchangeDiagnostics ■ MSExchangeEdgeSync ■ MSExchangeFrontEndTransport ■ MSExchangeHM ■ MSExchangeMailboxAssistants ■ MSExchangeDelivery ■ MSExchangeSubmission ■ MSExchangeMigrationWorkflow ■ MSExchangeMailboxReplication ■ MSExchangeRPC ■ MSExchangeFastSearch ■ HostControllerService ■ MSExchangeServiceHost 470Conversion to virtual machines How conversion of physical computers to virtual machines works in Backup Exec
- 471. ■ MSExchangeThrottling ■ MSExchangeTransport ■ MSExchangeTransportLogSearch ■ MSExchangeUM ■ MSExchangeUMCR See “Requirements for conversion to virtual machine jobs” on page 471. Requirements for conversion to virtual machine jobs Before you use the conversion to virtual machine feature, review the following requirements: ■ The option Simplified Disaster Recovery must have a status of ON on the Browse tab of the Backup Selections dialog box. Note: The Agent for VMware and Hyper-V is not required for conversion to virtual machines. ■ Only Windows servers are supported. ■ In a VMware environment, if you convert a physical server to a virtual server and then want to back up the converted server, you must push-install the Agent for Windows to the converted server. Push-installing the Agent for Windows installs the Backup Exec VSS provider. Note that you need to install the Agent for Windows on the converted server even if you installed the Agent for Windows on the physical server before you converted it to a virtual server. ■ For conversion in a Hyper-V environment, the following additional requirements apply: ■ The Agent for Windows must be installed on the Hyper-V host to which the conversion is sent. ■ The maximum disk size is 2 TB for Hyper-V 2008/2008 R2 and earlier. Disks larger than 2TB are supported for Hyper-V 2012. ■ Only basic disks are supported. Dynamic disks are not supported for Hyper-V conversions. ■ Before running a conversion job that targets a Hyper-V host, disable the File Server Resource Manager (FSRM). If you do not disable FSRM, then the job may fail with an "out of disk space" error. 471Conversion to virtual machines Requirements for conversion to virtual machine jobs
- 472. Note: Conversion of a physical Hyper-V host into a virtual machine is not supported. ■ For specific operating system requirements for conversion to virtual machines, see the Backup Exec Software Compatibility List at the following URL: http://entsupport.symantec.com/umi/V-269-1 See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Converting to a virtual machine simultaneously with a backup job With this type of a conversion, the backup and the conversion run at the same time. Note: If the backup fails, then the conversion fails also. However, if the conversion fails, the backup continues to run. For a conversion failure, the job is marked as a success with exceptions and the conversion process runs again during the next full backup. To convert to a virtual machine simultaneously with a backup job 1 On the Backup and Restore tab, right-click the server that contains the data you want to back up and convert. 2 Select Backup, and then select Back up to Disk and Simultaneously Convert to Virtual Machine or Back up to Deduplication Disk Storage and Simultaneously Convert to Virtual Machine, depending on the type of storage device that you want to use. 3 Do any of the following: Do the following: ■ In the <Name of Server> box, click Edit, and then select the items to back up. Note: The option Simplified Disaster Recovery must have a status of ON. ■ Click OK. To change the backup selections 472Conversion to virtual machines Converting to a virtual machine simultaneously with a backup job
- 473. Do the following: ■ In the Backup box, click Edit, and then change the backup options as needed. ■ Click OK. To change the backup options 4 In the Conversion to Virtual box, click Edit to set the options for conversion. 5 In the Convert for field, select either Hyper-V or VMware ESX/vCenter server. 6 Configure the conversion options: 473Conversion to virtual machines Converting to a virtual machine simultaneously with a backup job
- 474. 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. ■ 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 Hyper-V in step 5 474Conversion to virtual machines Converting to a virtual machine simultaneously with a backup job
- 475. If you selected VMware ESX/vCenter server in step 5 475Conversion to virtual machines Converting to a virtual machine simultaneously with a backup job
- 476. 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. 476Conversion to virtual machines Converting to a virtual machine simultaneously with a backup job
- 477. Note: In a CASO 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. 7 Click OK. 8 On the Backup Definition Properties dialog box, click OK to create the job. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Converting to a virtual machine after a backup job Backup Exec sets up this type of conversion as a stage that runs after the backup job runs. The backup sets that are created from the backup job are used to create the virtual machine. To convert to a virtual machine after a backup job 1 On the Backup and Restore tab, right-click the server that contains the data you want to back up and convert. 2 Select Backup, and then select Back Up to Disk and then Convert to Virtual Machine or Back Up to Deduplication Disk Storage and then Convert to Virtual Machine, depending on the type of storage device that you want to use. 3 Do any of the following: 477Conversion to virtual machines Converting to a virtual machine after a backup job
- 478. Do the following: ■ In the <Name of Server> box, click Edit, and then select the items to back up. Note: The option Simplified Disaster Recovery must have a status of ON. ■ Click OK. To change the backup selections Do the following: ■ In the Backup box, click Edit, and then change the backup options as needed. ■ Click OK. To change the backup options 4 In the Conversion to Virtual box, click Edit. 5 In the left pane, select Schedule, and then select one of the following options: Do the following: ■ Select According to schedule. ■ Click the arrow in the Source field to select either all backups or the most recent full backup as the source to initiate the conversion. ■ Select Recurrence, and then click the arrow to set the recurrence pattern. To schedule the conversion to run at a specific time Do the following: ■ Select According to schedule. ■ Click the arrow in the Source field to select either all backups or the most recent full backup as the source to initiate the conversion. ■ 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. To create the conversion job without scheduling it Select Convert to virtual immediately after source task completes. To run the conversion immediately after the backup job completes 478Conversion to virtual machines Converting to a virtual machine after a backup job
- 479. 6 Optional: In the left pane, select Notification to notify selected recipients when the job completes. 7 In the left pane, select Conversion Settings to set the options for the conversion. 8 In the Convert for field, select either Hyper-V or VMware ESX/vCenter server. 9 Configure the conversion options: 479Conversion to virtual machines Converting to a virtual machine after a backup job
- 480. 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. ■ 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 Hyper-V in step 8 480Conversion to virtual machines Converting to a virtual machine after a backup job
- 481. If you selected VMware ESX/vCenter server in step 8 481Conversion to virtual machines Converting to a virtual machine after a backup job
- 482. 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. 482Conversion to virtual machines Converting to a virtual machine after a backup job
- 483. Note: In a CASO 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. 10 Click OK to save your selections. 11 On the Backup Definition Properties dialog box, click OK to create the job. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Adding a conversion to virtual machine stage to a backup job You can add a stage to a backup definition to convert a backup to a virtual machine. A conversion to virtual machine job requires that the Simplified Disaster Recovery option on the backup selections has a status of ON. This status means that all components that are necessary for virtualization are selected. Backup Exec automatically selects the necessary components when you add a stage to convert to a virtual machine. To add a conversion to virtual machine stage to a backup job 1 Create a backup job, or edit an existing job. 2 In the Backup box, click Add Stage. 3 Select Convert to Virtual Machine to set up a conversion to run after the backup job completes, or select Convert to Virtual Simultaneously With Backups to run the conversion at the same time as the backup job. 4 In the Conversion to Virtual box, click Edit. 483Conversion to virtual machines Adding a conversion to virtual machine stage to a backup job
- 484. 5 If you selected the Convert to Virtual Machine option in step 3, do the following. If you selected Convert to Virtual Simultaneously With Backups in step 3, skip to step 6. ■ In the left pane, select Schedule to schedule the conversion, and then indicate if you want to schedule the job or run it immediately after the backup job completes. ■ (Optional) In the left pane, select Notification if you want to notify a recipient when the job completes. 6 In the left pane, select Conversion Settings to set the options for the conversion. 7 In the Convert for field, select either Hyper-V or VMware ESX/vCenter server. 8 Configure the conversion options: 484Conversion to virtual machines Adding a conversion to virtual machine stage to a backup job
- 485. 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. ■ 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 Hyper-V in step 7 485Conversion to virtual machines Adding a conversion to virtual machine stage to a backup job
- 486. If you selected VMware ESX/vCenter server in step 7 486Conversion to virtual machines Adding a conversion to virtual machine stage to a backup job
- 487. 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. 487Conversion to virtual machines Adding a conversion to virtual machine stage to a backup job
- 488. Note: In a CASO 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. 9 Click OK to save your selections. 10 On the Backup Definition Properties dialog box, edit the backup job properties, and then click OK to create the job. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Converting to a virtual machine from a point in time A conversion to a virtual machine from a point in time converts existing backup sets from a backup job in which the Simplified Disaster Recovery option was enabled. The Simplified Disaster Recovery option enables all of the critical system components for a virtual machine conversion to be included in the backup job. Note: The option Convert to virtual machine from point-in-time becomes available for selection only after you run at least one full backup that includes all critical system components. The option to convert to a virtual machine from a point in time is useful in a disaster recovery situation in which you want to quickly recover a failed server. The backup sets contain all of the necessary components of the system. Additionally, you can select application data or user data to include in the conversion. 488Conversion to virtual machines Converting to a virtual machine from a point in time
- 489. To convert to a virtual machine from a point in time 1 On the Backup and Restore tab, select the server that contains the backup sets you want to convert. 2 In the Conversions group, click Convert to Virtual, and then click Convert to Virtual Machine from Point In Time. 3 On the Options dialog box, in the Selected Point-in-Time box, click Edit. 4 Select the items that you want to include in the conversion, and then click OK. 5 On the Options dialog box, in the Convert to Virtual box, click Edit 6 In the left pane, select Schedule to select when to run the conversion job: Click Run now.To run the job immediately Click Run on, and then enter the date and time to run the job. To schedule the conversion to run at a specific time 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. To create the conversion job without scheduling it 7 (Optional) In the left pane, select Notification if you want to notify a recipient when the job completes. 8 In the left pane, select Conversion Settings to set the options for the conversion 9 In the Point in time field, select the point in time that you want to use for the conversion. 10 In the Name field, select all of the components for inclusion in the conversion. 11 In the Application data or non-system user data field, select additional data to include in the conversion. 12 Click OK to save your selections. 13 On the Options dialog box, click OK. 489Conversion to virtual machines Converting to a virtual machine from a point in time
- 490. 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 1 On the Backup and Restore tab, select the server that you want to convert to a virtual machine. 2 In the Conversions group, click Convert to Virtual, and then click One-Time Convert to Virtual Machine. 3 On the One-Time Convert to Virtual Machine Properties dialog box, in the Convert to Virtual box, click Edit. 4 In the left pane, select Schedule to select when to run the conversion job: Click Run now.To run the job immediately Click Run on, and then enter the date and time to run the job. To schedule the conversion to run at a specific time 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. To create the conversion job without scheduling it 5 (Optional) In the left pane, select Notification if you want to notify a recipient when the job completes. 6 In the left pane, select Conversion Settings to set the options for the conversion. 7 In the Convert for field, select either Hyper-V or VMware ESX/vCenter server. 8 Configure the conversion options: 490Conversion to virtual machines Creating a one-time conversion to a virtual machine
- 491. 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. ■ 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 Hyper-V in step 7 491Conversion to virtual machines Creating a one-time conversion to a virtual machine
- 492. If you selected VMware ESX/vCenter server in step 7 492Conversion to virtual machines Creating a one-time conversion to a virtual machine
- 493. 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. 493Conversion to virtual machines Creating a one-time conversion to a virtual machine
- 494. Note: In a CASO 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. 9 Click OK to save your selections. 10 On the One-Time Convert to Virtual Machine Properties dialog box, click OK. See “How conversion of physical computers to virtual machines works in Backup Exec” on page 463. Setting default options for conversion to virtual machine jobs You can set default options for all conversion to virtual machine jobs. However, you can override the default options for individual jobs. To set default options for conversion to virtual machine jobs 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Job Defaults, and then select Convert to Virtual. 3 Select the default schedule options that you want conversion to virtual jobs to use: 494Conversion to virtual machines Setting default options for conversion to virtual machine jobs
- 495. Do the following: ■ Select According to schedule. ■ Click the arrow in the Source field to select either all backups or the most recent full backup as the source to initiate the conversion. ■ Select Recurrence, and then select the arrow to set the recurrence pattern. To schedule conversion to virtual jobs to run at a specific time Do the following: ■ Select According to schedule. ■ Click the arrow in the Source field to select either all backups or the most recent full backup as the source to initiate the conversion. ■ 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. To create conversion to virtual jobs without scheduling them Select Convert to virtual immediately after source task completes. To run the conversion immediately after the backup job completes 4 (Optional) In the left pane, select Notification, and then select the recipients who should receive notifications about conversion to virtual jobs. 5 In the left pane, select Conversion Settings. 6 In the Convert for field, select either Hyper-V or VMware ESX/vCenter server. 7 Configure the conversion options: 495Conversion to virtual machines Setting default options for conversion to virtual machine jobs
- 496. 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 machines, 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 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. If you selected Hyper-V in step 6 496Conversion to virtual machines Setting default options for conversion to virtual machine jobs
- 497. 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 machines. ■ Click the arrow in the Logon account field, and then select the appropriate logon account for the server that you selected. ■ 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 CASO environment, this path should be local to the managed Backup Exec server to which the job is targeted. If you selected VMware ESX/vCenter server in step 6 8 Click OK 497Conversion to virtual machines Setting default options for conversion to virtual machine jobs
- 498. Configuration and settings This chapter includes the following topics: ■ Changing default backup job settings ■ Configuring schedules for backup jobs ■ Configuring storage options for backup jobs ■ Configuring automatic test run jobs for backup jobs ■ Configuring automatic verify operations for backup jobs ■ Configuring delayed catalog operations to improve backup performance ■ Configuring Advanced Open File options for backup jobs ■ Configuring checkpoint restart ■ Configuring Backup Exec to work with Symantec Endpoint Protection ■ Configuring pre/post commands for backup jobs ■ Configuring file and folder options for backup jobs ■ Setting default schedule options for rule-based jobs and run now jobs ■ Excluding dates from the backup schedule for all backups ■ Removing dates from the list of excluded dates ■ Exporting a list of dates that are excluded from all backups to another server ■ Changing the default preferences ■ Configuring the default setting for backing up multiple servers or applications ■ Configuring database maintenance and security 14Chapter
- 499. ■ Exporting the Backup Exec Database encryption key ■ Refreshing Backup Exec Database encryption keys ■ Configuring encryption for the connection to the Backup Exec Database ■ Scheduling Backup Exec to check logon accounts ■ Configuring Backup Exec to discover data to back up ■ Adding discovered servers to the list of servers in Backup Exec ■ Backup networks ■ Changing network and security options for Backup Exec ■ Using Backup Exec with firewalls ■ Using encryption with Backup Exec ■ Encryption key management ■ Creating encryption keys ■ Replacing an encryption key ■ Deleting encryption keys ■ Granular Recovery Technology ■ Setting default Granular Recovery Technology (GRT) options ■ DBA-initiated job templates ■ Creating DBA-initiated job templates ■ Editing DBA-inititated job templates ■ Deleting DBA-initiated job templates ■ Backup Exec logon accounts ■ Starting and stopping Backup Exec services ■ Changing the credentials for a service account ■ Changing startup options for Backup Exec services ■ Configuring audit logs ■ Viewing the audit log ■ Removing entries from the audit log 499Configuration and settings
- 500. ■ Saving an audit log to a text file ■ Copying configuration settings to another Backup Exec server ■ Viewing server properties Changing default backup job settings Backup Exec is preconfigured with default settings for backup jobs. You can change the default settings for your backup jobs. When you create a backup job, the job inherits the default settings that you configure. You can override the default settings for backup jobs when you create them. Backup job settings include storage, security, and file system options for backup jobs, among other things. You can set unique backup job defaults for the following types of backup jobs: ■ Back Up to Deduplication Disk Storage Device ■ Back Up to Disk ■ Back Up to Tape ■ Duplicate to Deduplication Disk Storage Device ■ Duplicate to Tape ■ Convert to Virtual Note: Backup Exec displays only the types of backup jobs for which your system is configured. For example, if you do not have a tape drive, you do not see the Back Up to Tape option in the list of backup job types. To change default backup job settings 1 Click the Backup Exec button, select Configuration and Settings, and then select Job Defaults. 2 Select the type of backup for which you want to set default options. For example, if you want to set up the default options for backups to disk, select Back Up to Disk. The options that appear vary depending on what types of storage devices you have configured. Different default options can be configured for backup jobs to different types of storage. 500Configuration and settings Changing default backup job settings
- 501. 3 In the left pane, select the setting for which you want to configure default options. Select this option to configure default settings for the time and frequency with which you want to run backup jobs. Schedule See “Configuring schedules for backup jobs” on page 504. Select this option to configure default settings for the storage device that you want to use for backup jobs. Storage See “Configuring storage options for backup jobs” on page 512. Select this option to configure Backup Exec to notify specified recipients when backup jobs are completed. Notification Each type of backup job can be configured with different notification recipients. Backup Exec can notify people by email or text message. See “Notification options for jobs” on page 292. Select this option to configure a test job that automatically tests storage capacity, credentials, and media integrity. Test Run The test job can help you determine if there are any problems that might keep backup jobs from completing successfully. See “Configuring automatic test run jobs for backup jobs” on page 518. Select this option to create a job that automatically verifies whether all of the data was successfully backed up when jobs are completed. Verify A verify job can also help you determine whether the media you use is defective. See “Configuring automatic verify operations for backup jobs” on page 519. 501Configuration and settings Changing default backup job settings
- 502. Select this option to configure delayed catalog operations for any GRT-enabled jobs. You can choose to run a delayed catalog operation, schedule the catalog operation for another time, or choose to not run a delayed catalog operation. See “Configuring delayed catalog operations to improve backup performance” on page 521. Delayed Catalog Select this option to configure the snapshot settings that Backup Exec uses to process backup jobs. Snapshot technology lets Backup Exec capture any files that are open when a backup job runs. You can also enable checkpoint restart, which lets you resume interrupted backup jobs. See “Configuring Advanced Open File options for backup jobs” on page 525. See “Configuring checkpoint restart” on page 528. Advanced Open File Select this option to configure off-host backup processing for backup jobs. See “Setting default backup options for the Advanced Disk-based Backup Option” on page 1173. Advanced Disk-based Backup Select this option to configure Backup Exec to work with Symantec Endpoint Protection. You can configure backup jobs to run automatically when the Symantec ThreatCon reaches a specified level. Integrating your backup jobs with Symantec Endpoint Protection helps make sure that your vital data is safely backed up as soon as global threats are detected. See “Configuring Backup Exec to work with Symantec Endpoint Protection” on page 530. Security Select this option to configure any commands that you want to run either before backup jobs begin or after backup jobs are completed. See “Configuring pre/post commands for backup jobs” on page 532. Pre/Post Commands Select this option to configure how Backup Exec processes file system attributes such as junction points and symbolic links. See “Configuring file and folder options for backup jobs” on page 537. Files and Folders 502Configuration and settings Changing default backup job settings
- 503. Select this option to configure Enterprise Vault options for backup jobs. See “Enterprise Vault backup options” on page 1036. Enterprise Vault Select this option to configure options for any Linux or Macintosh computers that are included in backup jobs. See “Linux backup options” on page 1219. See “Default backup job options for Macintosh systems” on page 1252. Linux and Macintosh Select this option to configure options for any Lotus Domino data that is included in backup jobs. See “Lotus Domino Agent backup options” on page 1080. Lotus Domino Select this option to configure options for any Microsoft Active Directory data that is included in backup jobs. See “Editing options for Active Directory and ADAM/AD LDS backup jobs” on page 1099. Microsoft Active Directory Select this option to configure options for any Microsoft Exchange data that is included in backup jobs. See “Setting default backup options for Exchange Server” on page 952. Microsoft Exchange Select this option to configure options for any virtual machines that are included in backup jobs. See “Setting default backup options for virtual machines” on page 839. See “Setting default backup options for Hyper-V” on page 873. Virtual Machines Select this option to configure options for any Microsoft SharePoint data that is included in backup jobs. See “Setting default backup options for SharePoint” on page 973. Microsoft SharePoint Select this option to configure options for any Microsoft SQL data that is included in backup jobs. See “Setting default backup options for SQL Server” on page 906. Microsoft SQL 503Configuration and settings Changing default backup job settings
- 504. Select this option to configure options for any NDMP data that is included in backup jobs. See “NDMP backup options for NDMP servers” on page 1188. NDMP Select this option to configure options for any Oracle data that is included in backup jobs. See “Oracle backup options” on page 1011. Oracle Select this option to configure how Backup Exec works with any archiving stages in backup definitions. See “Archive Option backup options” on page 1378. Archive Option Select this option to exclude specific files or specific types of files from backup jobs. See “Excluding files from backups” on page 166. Exclusions 4 Select the appropriate options. 5 When you are finished configuring default options, click OK. Configuring schedules for backup jobs Backup Exec lets you configure the time and the frequency for which you want to run jobs. You can run jobs immediately, once on a specific day and time, or more than once according to a schedule. Backup Exec lets you use minutes, hours, days, weeks, months, or years as measurements of time to create a recurring pattern for the schedule. Alternatively, you can select specific days of the month to create a recurring schedule on which jobs should run. See “How job scheduling works in Backup Exec” on page 203. You can configure default options for schedules, which all your jobs inherit when you create them. Or you can override the default schedule settings when you create jobs. To configure schedules for jobs 1 Do one of the following: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure schedule settings. To configure default schedule settings for all backup jobs 504Configuration and settings Configuring schedules for backup jobs
- 505. ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure a schedule for specific backup jobs 2 In the left pane, click Schedule. 3 In the Job template name field, type the name of the job template for which you want to configure a schedule. Job templates are the collection of settings that Backup Exec uses to create jobs. Backup job settings can include scheduling options, storage device options, or backup methods for selected types of data, for example. When you want to run a backup, Backup Exec combines the job template with the backup selections to create a backup job that runs according to the options that you specified. The job template name that you enter in this field is used to create the job name. 4 In the Job name field, type the name of the job for which you want to configure a schedule. The unique job name helps you to identify backup jobs in Backup Exec. This is only available to set per job, not as a default backup job setting. 5 For each job for which you want to configure a schedule, do one of the following: Complete the following steps: ■ Select Recurrence. ■ Proceed to step 6 to configure the recurrence pattern. To configure recurring jobs Complete the following steps: ■ Select Run now with no recurring schedule. ■ Proceed to step 9. Note: This option is only available for full backup jobs. To configure jobs to run immediately without any recurrences 505Configuration and settings Configuring schedules for backup jobs
- 506. Complete the following steps: ■ Select Create without a schedule. ■ Proceed to step 10. When you use this option, the jobs do not run at the time of creation and they do not have a recurring schedule. The jobs remain unscheduled until you choose to run them. You can use a third-party job automation or task scheduling tool to run the jobs later. You can run unscheduled backup jobs later by using the Run Next Backup Now option or you can manually run the job by using the Run Now option. If you use this option to create a job, you cannot place the job on hold. You cannot place jobs on hold unless they are scheduled. To configure a job without a schedule 6 To configure the recurrence pattern, complete the following options: Select this option to create a recurrence pattern that is measured in hours or minutes. When you select Hours, you can configure the following options: ■ Every X hour/minute Indicate the number of hours or minutes between the start time of a job and the start time of the next job instance. ■ You must choose between the following options: ■ From Designate the starting time for a job to run. ■ Between Restrict the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday. The start time and end time can span a maximum of 24 hours. However, they can cross over midnight into the following day. Hours 506Configuration and settings Configuring schedules for backup jobs
- 507. Select this option to create a recurrence pattern that is measured in days. When you select Days, you must choose between the following options: ■ Every X day Indicate the number of days between the start time of a job and the start time of the next job instance. ■ Every weekday Select this option to enable the job to run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays. Days Select this option to create a recurrence pattern that is measured in weeks. When you create a recurrence pattern that is measured in weeks, you must configure the Every X week on field. The Every X week on specifies the number of weeks between the start time of a job and the start time of the next job instance. It also specifies the days of the week on which the job should run. Weeks 507Configuration and settings Configuring schedules for backup jobs
- 508. Months 508Configuration and settings Configuring schedules for backup jobs
- 509. Select this option to create a recurrence pattern that is measured in months. When you select Months, you must choose between the following options: ■ Day X of every X month Specify the day on which the job should run. Then indicate the number of months between the start time of a job and the start time of the next job instance. ■ Every X X of every X month Specify the day on which the job should run. Then indicate the number of months between the start time of a job and the start time of the next job instance. ■ Selected days of the month Specify the weeks and days of the month on which Backup Exec runs the job. You select the days and weeks on a grid. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current week and day of the month. If you create the job on the third Monday of the month, the default setting is for the job to run once a month on the third Monday. You can change the default or select additional days on which the job should run. For example, if you want the job to run on the last Friday of every month, select the check box for Friday in the last row of the grid. Any additional days that you select are added to the monthly recurrence pattern. ■ Selected dates of the month Specify the dates of the month on which Backup Exec runs the job. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current date of the month. If you create the job on the 15th, the default setting is for the job to run once a month on the 15th. You can change the default or select additional days on which the job should run. For example, if you want the job to run on the 1st and 15th of every month, select only those dates in the calendar. Any additional days that you select are added to the monthly recurrence pattern. 509Configuration and settings Configuring schedules for backup jobs
- 510. If you select the 31st, the job runs on the last day of the month in months that do not have 31 days. For example, if you configure the job to run on the 31st, in September the job runs on the 30th instead. Select this option to create a recurrence pattern that is measured in years. When you select Years, you can configure the following options: ■ Every X year Specify the number of years between the start time of a job and the start time of the next job instance. ■ You must choose between the following options: ■ On X Specify the date on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected June 28th in this field, the job runs every 2 years on June 28th. ■ On the X of X Specify the day and month on which Backup Exec runs the job. The date that you select in this field corresponds to the number of years that you selected in the Every X year field. So if you selected to run the job every 2 years and you selected the fourth Thursday of June in this field, the job runs every 2 years on the fourth Thursday of June. Years Enter the starting time for the first job in the recurrence pattern. at Enter the date on which you want the recurrence pattern to begin. The date that you enter in this field is the date on which the schedule goes into effect. You can select any date in the past or the future. If you select a date that occurred in the past, Backup Exec calculates the date of the next upcoming job and begins running recurring jobs on that date. Starting on Click this option to view all scheduled backup jobs on a calendar to check for scheduling conflicts. Calendar 510Configuration and settings Configuring schedules for backup jobs
- 511. Select this option to run the initial full backup as soon as the job is created without affecting the schedule of future jobs. Run initial full backup now in addition to the selected schedule Specify the amount of time past the job's scheduled start time at which you want Backup Exec to change the job completion status to Missed. The job is rescheduled to run based on the time window that you configured. See “List of job statuses in Backup Exec” on page 264. Reschedule the job if it does not start X hours after its scheduled start time Specify the amount of time after the job's scheduled start time at which you want to cancel the job if it is still running. Backup Exec changes the job completion status to Canceled, timed out. See “List of job statuses in Backup Exec” on page 264. Cancel the job if it is running X hours after its scheduled start time 7 To configure specific dates to include with the recurring job schedule, select the Include/exclude dates tab, and then complete the following steps: ■ Click Include dates. ■ Select the dates that you want to include with the recurring job schedule. ■ Click OK. The job runs on all of the dates that you select using this option, in addition to the dates that are part of its normal schedule recurrence. The job resumes its normal schedule on the next day that it is scheduled after an include date. See “Including a specific date in the schedule for a backup job” on page 204. 8 To configure specific dates to exclude from the job schedule, select the Include/exclude dates tab, and then complete the following steps: ■ Click Exclude dates. ■ Select the dates that you want to exclude from the recurring job schedule. ■ Click OK. The job does not run on any of the dates that you select using this option. It resumes its normal schedule on the next day that a job is scheduled after an excluded date. See “Preventing backup jobs from running on a specific date” on page 206. 511Configuration and settings Configuring schedules for backup jobs
- 512. 9 To submit jobs with an on-hold status, select Submit job on hold. You should select this option if you want to submit the job, but you do not want the job to run until a later date. The job runs later when you change the job's hold status. 10 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Configuring storage options for backup jobs Use the storage options to select the storage and media set on which you want the backup job to run. You can configure different storage devices for each backup job. For example, you may select disk storage for a full backup and a storage pool for an incremental backup in the same backup definition. You can configure storage options as default settings for all backup jobs. If you do not want to use the default storage options for a particular backup job, you can override the default setting when you create the backup job. You do not have to configure default storage options for all backup jobs, however. If you want to configure different storage options for specific backup jobs, you can configure the storage options when you create those backup jobs. To configure storage options for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure storage options. To configure default storage options for all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure storage options for specific backup jobs 2 In the left pane, click Storage. 512Configuration and settings Configuring storage options for backup jobs
- 513. 3 Complete the following options as necessary: Note: Some of these options display only in Central Admin Server Option (CASO) environments. Select the priority of access to the storage devices for backup jobs. This is only available to set per job, not as a default backup job setting. See “Changing the priority for a scheduled job” on page 249. Priority Select whether you want a job to run on devices on a specific managed Backup Exec server or on devices that are on a group of managed Backup Exec servers. This option displays only if you have the Central Admin Server Option installed. This option is an additional filter that lets you control where certain jobs are delegated. For example, to always run backups of Exchange databases only on the devices that are attached to managed Backup Exec servers in a pool named Exchange Backups, select this option. Then select the Exchange Backups Backup Exec server pool. Backup Exec server or Backup Exec server pool Select the storage device to which you want to send backup data. See “Creating storage device pools” on page 402. See “About the Any Virtual Disk Storage device pool in the Storage Provisioning Option” on page 1291. See “About the Remote Media Agent for Linux ” on page 1258. See “Features and types of disk-based storage and network-based storage” on page 300. Storage 513Configuration and settings Configuring storage options for backup jobs
- 514. 4 If you selected to configure an OpenStorage device or a deduplication disk storage device in the Storage field, select from the following options: Select this option to enable a remote computer to send data directly to an OpenStorage device or a deduplication disk storage device, and to perform client-side deduplication if the device supports it. The Backup Exec server is bypassed, which leaves the Backup Exec server free to perform other operations. If client-side deduplication cannot be performed, then either Backup Exec server deduplication or Appliance deduplication is performed. This option appears if the Deduplication Option is installed and an OpenStorage device or a deduplication disk storage device is selected in the Storage field. See “How to use client-side deduplication” on page 818. Enable the remote computer to directly access the storage device and to perform client-side deduplication, if it is supported Select this option to enable a remote computer to send data through the Backup Exec server to an OpenStorage device or a deduplication disk storage device, and to perform Backup Exec server-side deduplication if it it supported. If the Backup Exec server does not support deduplication, the data is deduplicated on an intelligent disk device, such as Symantec PureDisk or a device from a third-party vendor. This option appears if the Deduplication Option is installed and an OpenStorage device or a deduplication disk storage device is selected in the Storage field. See “About the Deduplication Option” on page 792. Enable the remote computer to access the storage device through the Backup Exec server and to perform Backup Exec server-side deduplication, if it is supported 5 In the Keep for field, enter the amount of time for which you want to keep the backup sets or job history. 6 If you selected to configure a tape device in the Storage field, complete the following options as necessary: 514Configuration and settings Configuring storage options for backup jobs
- 515. Select the media set to use for the backup job. The media set specifies the overwrite protection period and the append period for the backup data on the media. If you want to create a new media set for this backup job, click the icon to the right of the media set drop-down menu. This option is available only if you selected a tape device in the Storage field. See “Default media sets” on page 367. Media set Select this option to place the backed up data on overwritable media. Ensure that appropriate media is in the storage device that you select. Appropriate media for an overwrite job include the following: ■ Scratch media ■ Media for which the overwrite protection period has expired Allocated or imported media may also be overwritten depending on the media overwrite protection level that is set. Depending on your configuration, overwritable media is selected from scratch media or recyclable media. If the media in the storage device is not overwritable, an alert appears to prompt you to insert overwritable media. This option is available only if you selected a tape device in the Storage field. See “Managing tapes” on page 366. See “Media overwrite protection levels for tape media” on page 380. See “How Backup Exec searches for overwritable media in tape drives ” on page 381. Overwrite media 515Configuration and settings Configuring storage options for backup jobs
- 516. Select this option to append the backed up data to the specified media set if an appendable media is available. Otherwise, Backup Exec searches for an overwritable media and adds it to the media set. If the append operation fills a media, the backup job continues on an overwritable media. If the media in the storage device is not overwritable, an alert prompts you to insert overwritable media. This option is available only if you selected a tape device in the Storage field. Append to media, overwrite if no appendable media is available Select this option to append the backed up data to the specified media set if an appendable media is available. Otherwise, Backup Exec terminates the job. This option is available only if you selected a tape device in the Storage field. Append to media, terminate job if no appendable media is available Select this option to eject the media from the drive or slot when the operation completes. You can also schedule a job to eject media. This option is available only if you selected a tape device in the Storage field. See “Ejecting media from a disk cartridge or tape drive” on page 441. Eject the media after job completes Select this option to run the tape in the drive from beginning to end at a fast speed. Retensioning helps the tape wind evenly and run more smoothly past the tape drive heads. This option is available only if you select a tape drive that supports retensioning. Retension media before backup Select this option to use WORM (write once, read many) media for this backup job. Backup Exec confirms that the destination device is or contains a WORM-compatible drive, and that the WORM media is available in the drive. If WORM media or a WORM-compatible drive is not found, an alert is sent. See “How WORM media is used in Backup Exec” on page 387. Use Write once, read many (WORM) media 516Configuration and settings Configuring storage options for backup jobs
- 517. Select this option to logically move the media from the robotic library to the specified media vault. This operation moves media from robotic library slots into a portal. An alert reminds you to remove the media from the portal or from a slot. If a job requires multiple media, the export media operation starts after the backup job completes, not after each media is filled. This option is available only if you selected a tape device in the Storage field. See “Default media vaults” on page 388. Export media to vault after job completes 7 In the Compression field, select from the following options: Select this option to copy the data to the media in its original form (uncompressed). Using some form of data compression can help expedite backups and preserve storage space. Hardware data compression should not be used in environments where storage devices that support hardware compression are used interchangeably with devices that do not have that functionality. In this situation, hardware compression is automatically disabled. You can manually turn on hardware compression on the drives that support it, but this results in media inconsistency. If the drive that supports hardware compression fails, the compressed media cannot be restored with the non-compression drive. None Select this option to use STAC software data compression, which compresses the data before it is sent to the storage device. Software Select this option to use hardware data compression if the storage device supports it. If the drive does not feature data compression, the data is backed up uncompressed. Hardware (if available, otherwise none) Select this option to use hardware data compression if the storage device supports it. If the drive does not feature hardware data compression, STAC software compression is used. Hardware (if available, otherwise software) 517Configuration and settings Configuring storage options for backup jobs
- 518. 8 To configure encryption, complete the following options: Select the type of encryption that you want to use, if any. See “Using encryption with Backup Exec” on page 575. Encryption type Select the encryption key that you want to use, if you selected to use encryption. Encryption key Click this option to create a new encryption key to configure encryption for jobs. Do not use this option to replace or delete any existing encryption keys that are associated with the job. This option is available only if you select an encryption type. See “Encryption key management” on page 578. Manage Keys 9 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Configuring automatic test run jobs for backup jobs Test run jobs attempt to determine if a scheduled backup job could possibly fail when you run it. When you run a test job, no data is backed up. Instead, Backup Exec checks your storage capacity, credentials, and media to find potential errors. If there is an error, the job continues to run until it is completed. The error appears in the job log. You can also configure Backup Exec to send a notification to a designated recipient. During a test run job, the following things may cause a job to fail: ■ Logon credentials are incorrect. ■ Storage capacity is not sufficient. ■ Tape cartridge media or disk cartridge media is not available. ■ Overwritable media is not available for an overwrite job. ■ Appendable media is not available for an append job. A test run job checks the media capacity that is available for the selected job. However, you can check if there is enough available media for multiple test run jobs in the Test Run Results Report. 518Configuration and settings Configuring automatic test run jobs for backup jobs
- 519. See “Test Run Results report” on page 676. You can manually run a test run job at any time. See “Running a test run job manually” on page 214. You can also configure test run jobs to run automatically before your scheduled backup jobs as a default setting. If you do not want to run a test run job for a particular backup job, you can override the default setting when you create the backup job. You do not have to enable test run jobs as a default for all backup jobs, however. If you want to run test run jobs only for specific backup jobs, you can configure the test run job when you create those backup jobs. To configure automatic test run jobs for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure test run jobs. To enable test run jobs as a default for all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To enable a test run job for specific backup jobs 2 In the left pane, click Test Run. 3 Select Enable test run. 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Configuring automatic verify operations for backup jobs Backup Exec can perform a verify operation to make sure that the media can be read after a backup job has been completed. Symantec recommends that you verify all backed up data to ensure the integrity of the collection of data and the media on which it resides. 519Configuration and settings Configuring automatic verify operations for backup jobs
- 520. You can manually run a verify operation on a backup set or a job history at any time. You can verify backup sets if you want to verify only the data that was backed up in a specific backup job instance. If you want to verify a backup definition and all of its dependent backup sets, you can verify a job history. For example, if you want to verify a backup definition that used incremental backups, Backup Exec verifies all incrementals dating back to, and including, the last full backup. See “Verifying backed up data manually” on page 215. By default, Backup Exec automatically verifies backed up data at the end of a backup job. However, you can also schedule the automatic verify operation to take place at a later time or disable the verify operation altogether. You can change Backup Exec's verify options as part of the default backup settings or for individual backup jobs. To configure automatic verify operations for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure verify operations. To configure automatic verify operations for all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure automatic verify operations for specific backup jobs 2 In the left pane, click Verify. 520Configuration and settings Configuring automatic verify operations for backup jobs
- 521. 3 Complete the following options: Select this option to run a verify operation automatically when the backup job is completed. At the end of the job Select this option to create a verify operation and schedule it to run as a separate job when the backup job is completed. You can use the Edit option to configure options for the separate verify job. After job finishes, as a separate job Select this option to create a verify operation and schedule it to run as a separate job at a later time. You can use the Edit option to configure options for the separate verify job. As a separate scheduled job Select this option to disable the verify operation for the backup job. Do not verify data for this job 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Configuring delayed catalog operations to improve backup performance When you back up data, Backup Exec creates a catalog that contains information about the backup sets and about the storage device on which the backup sets are stored. See “How Backup Exec catalogs work” on page 235. Backup jobs that are enabled for Granular Recovery Technology (GRT) require more time to catalog because of the amount of granular information that they contain. For GRT-enabled backup jobs, the catalog operation is delayed and run as a separate operation to have less of an effect on your backup window. Because the catalog operation runs separately from the backup job, it does not prevent another scheduled backup job from starting on time. 521Configuration and settings Configuring delayed catalog operations to improve backup performance
- 522. Note: The delayed catalog feature is not supported for backup to tape jobs. If you create a GRT-enabled backup to tape job for Microsoft Exchange, Microsoft SharePoint, Microsoft Hyper-V, or VMware data, the catalog operation runs as part of the backup job. See “Granular Recovery Technology” on page 583. When you enable GRT for Microsoft Exchange, Microsoft SharePoint, Microsoft Hyper-V, or VMware backups, the delayed catalog operation runs after the backup job by default. For Exchange and SharePoint backups, the delayed catalog operation runs immediately after all full backups. It runs once every 24 hours for all incremental backups and differential backups, even if you schedule more than one GRT-enabled job to run in the 24-hour period. For Hyper-V and VMware backups, the delayed catalog operation runs immediately after all full, incremental, and differential backups by default. You can also configure the delayed catalog operation to run on a schedule if you do not want it to run immediately after the backup job. The catalog operation can be time consuming. It requires access to the storage device that is used for the backup. You may want to schedule the delayed catalog operation to run outside of your backup window so that it does not interfere with your system resources. If you schedule the delayed catalog operation, it runs only for the most recent backup set since the last catalog operation. In this situation, only the most recent backup set since the last catalog operation can be used for granular recovery. For example, if you schedule incremental backups to run every 11 hours and schedule the delayed catalog operation to run at midnight, you would have the following backup sets: ■ Full (11:00 A.M.) ■ Incremental 1 (10:00 P.M.) ■ Catalog 1 (Midnight) This job catalogs Incremental 1. ■ Incremental 2 (9:00 A.M.) ■ Incremental 3 (8:00 P.M.) ■ Catalog 2 (Midnight). This job catalogs Incremental 3. Incremental 2 is not cataloged. ■ Incremental 4 (7:00 A.M.) ■ Incremental 5 (6:00 P.M.) ■ Catalog 3 (Midnight) This job catalogs Incremental 5. Incremental 4 is not cataloged. 522Configuration and settings Configuring delayed catalog operations to improve backup performance
- 523. ■ Incremental 6 (5:00 A.M.) This backup is not cataloged. In the example, you can perform a granular recovery from Incremental 5, Incremental 3, or Incremental 1. You cannot perform a granular recovery from Incremental 2, Incremental 4, or Incremental 6. However, you can perform a full restore from any of the backup sets. You can also choose to not run a delayed catalog operation. If you do not run a delayed catalog operation for GRT-enabled Exchange and SharePoint backups, the granular information that is backed up is not cataloged for granular restore. You will not be able to search the backup sets for granular data. However, you can browse the backup sets. If you decide to restore granular data from the backup sets, Backup Exec reads and displays the granular information in the backup sets as you browse for items to restore. It takes longer to restore granular data if you do not run the delayed catalog operation. If you choose to not run the delayed catalog operation for GRT-enabled Hyper-V and VMware backups, the catalog operation runs as part of the backup job instead of delaying it to a later time. You can configure delayed catalog options as default settings for all GRT-enabled backup jobs. If the default settings are not appropriate for a particular job, you can override them when you create the job. You do not have to create default settings for delayed catalogs, however. If you want to configure delayed catalogs only for specific jobs, you can configure the settings when you create those jobs. To configure a delayed catalog operation 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure delayed catalog settings. To configure delayed catalog options for all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure delayed catalog options for specific backup jobs 2 In the left pane, click Delayed Catalog. 523Configuration and settings Configuring delayed catalog operations to improve backup performance
- 524. 3 Select one of the following options: Select this option if you do not want to run a delayed catalog operation for GRT-enabled backup jobs. Do not run a delayed catalog operation If you select this option when you back up Microsoft Exchange or Microsoft SharePoint data, the granular information that is backed up is not cataloged for granular restore. You will not be able to search the backup sets for granular data. However, you can browse the backup sets. If you decide to restore granular data from the backup sets, Backup Exec browses the backup sets for granular data as you browse for items to restore. If you select this option, it increases the amount of time that it takes to restore granular Exchange or SharePoint data. If you select this option when you back up a virtual machine, the catalog operation runs as part of the backup job. Running the catalog operation as part of the backup job increases the amount of time that it takes to complete the backup job and may delay the start of any pending backup jobs. Select this option to run the delayed catalog operation immediately after a backup job finishes. The catalog Immediately after a backup job finishes, as a separate job operation runs as a separate job. This option is the default setting for GRT-enabled backup jobs. For Exchange and SharePoint backups, the delayed catalog operation runs immediately after all full backups. It runs once every 24 hours for all incremental backups and differential backups. For Hyper-V and VMware backups, the delayed catalog operation runs immediately after all full, incremental, and differential backups. 524Configuration and settings Configuring delayed catalog operations to improve backup performance
- 525. Select this option to run the delayed catalog operation as a separate, scheduled job. Then select the start time and the days of the week on which you want the delayed catalog operation to run. If you schedule the delayed catalog operation, it runs only for the most recent backup set since the last catalog operation. In this situation, only the most recent backup set since the last catalog operation can be used for granular recovery. Note: You cannot browse backup sets for granular data or restore granular items from the backup sets until the data has been cataloged. However, you can perform a full restore from the backup sets. As a separate job, according to this schedule 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Configuring Advanced Open File options for backup jobs Backup Exec's Advanced Open File feature lets you use snapshot technology to capture any files that are open when a backup runs. You can configure Advanced Open File options as default settings for all backup jobs. If the default settings are not appropriate for a particular job, you can override them when you create the job. You do not have to create default settings for Advanced Open File options, however. If you want to use Advanced Open File options only for specific jobs, you can configure the settings when you create those jobs. To configure Advanced Open File options for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure Advanced Open File options. To configure default Advanced Open File options for all backup jobs 525Configuration and settings Configuring Advanced Open File options for backup jobs
- 526. Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure Advanced Open File options for specific backup jobs 2 In the left pane, click Advanced Open File. 3 Complete the following options: Select this option to enable the use of snapshot technology for backup jobs. Use snapshot technology Select one of the following snapshot providers for jobs: ■ Automatic - Allow VSS to select the snapshot provider. Select this option to enable VSS to select the best provider for the selected volume. The order in which a snapshot provider is selected is hardware provider and then the system provider. ■ System - Use Microsoft Software Shadow Copy Provider. ■ Hardware - Use technology provided by the hardware manufacturer. If you select multiple volumes, you must use the same type of provider to snap all of the volumes. You can snap multiple volumes with the same provider or you can use multiple providers, but you cannot use system and hardware providers as part of the same snapshot. Snapshot provider 526Configuration and settings Configuring Advanced Open File options for backup jobs
- 527. Select this option to enable the backup of multiple volumes in one job, with only one logical volume being snapped at a time. To ensure database integrity, or if a volume contains mount points, multiple volumes may need to be snapped one at a time. A volume with mount points to other volumes is considered a logical volume for snapshot purposes. Therefore, that volume and the mount point volumes are snapped together simultaneously. After the logical volume is snapped and backed up, the snapshot is detected before the next logical volume is snapped. This option increases the ability to meet the minimum quiet time that is needed to complete a snapshot. A logical volume can comprise multiple physical volumes. A single logical volume can encompass all of the volumes on which databases reside. If this option is not selected, then a snapshot for all volumes in the backup job is created simultaneously. All volumes must meet the minimum quiet time. This option is only available for local volumes. The Shadow Copy Components snapshots are created using VSS, which is reported in the job log. Process logical volumes for backup one at a time Select this option to enable the checkpoint restart option. Checkpoint restart enables Backup Exec to automatically restart a job that is interrupted. The job restarts from the point where it was interrupted instead of starting over at the beginning. Backup Exec waits two minutes after the job stops and then attempts to restart the interrupted job one time. If the job cannot be restarted automatically or if checkpoint restart is disabled, you must restart it manually. A manual restart starts the job at the beginning instead of at the point where the job was interrupted. See “Configuring checkpoint restart” on page 528. Enable checkpoint restart 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. 527Configuration and settings Configuring Advanced Open File options for backup jobs
- 528. Configuring checkpoint restart Checkpoint restart is a backup job setting that enables Backup Exec to automatically restart a job that is interrupted. The job restarts from the point where it was interrupted instead of starting over at the beginning. Backup Exec waits two minutes after the job stops and then attempts to restart the interrupted job. If the job cannot be restarted automatically or if checkpoint restart is disabled, you must restart it manually. A manual restart starts the job at the beginning instead of at the point where the job was interrupted. Note: Checkpoint restart cannot restart a backup job until it has backed up at least 32 MB of data. If a backup job fails before it has backed up at least that much data, you must run it again manually. You can enable checkpoint restart for any jobs that are configured with the storage option Overwrite media. However, if there is no available media to overwrite and the job is interrupted, it may be placed on hold until overwritable media is available. When the media is available, the job restarts from where it was interrupted. Backup Exec automatically cancels any jobs that run for too long according to the schedule settings that you selected when you created the job. If Backup Exec automatically cancels a job, it is not eligible to be restarted. If you manually cancel a job, Backup Exec does not automatically try to restart it. Note: If you use the Central Admin Server Option (CASO), any jobs that are restarted run on the same managed Backup Exec server on which the job failed. If the original Backup Exec server is not available, Backup Exec selects a different Backup Exec server on which to run the restarted job. You can enable or disable checkpoint restart in the Advanced Open File options when you create backup jobs or in the backup job defaults. See “Configuring Advanced Open File options for backup jobs” on page 525. This topic includes the following information: Technologies supported for checkpoint restart Things to consider before you use checkpoint restart Changing the default checkpoint restart settings Technologies supported for checkpoint restart Checkpoint restart is only supported for NTFS volumes. The only type of snapshot technology that is supported for checkpoint restart is VSS. 528Configuration and settings Configuring checkpoint restart
- 529. Checkpoint restart is not supported for the following: ■ FAT volumes ■ FAT32 volumes ■ UNIX computers ■ Cluster Shared Volumes (CSV) ■ Application agents ■ Incremental or differential backups ■ Jobs that use catalogs to determine if a file has been backed up See “How Backup Exec determines if a file has been backed up” on page 187. Things to consider before you use checkpoint restart You should consider the following things before you use checkpoint restart: ■ If the failure occurs in the middle of an append job, the media is no longer appendable. The media is not appendable until it is erased or overwritten, or the retention period expires. When the restart occurs, Backup Exec uses new media. You should select an appropriate media overwrite protection level to ensure that the restart does not overwrite the media that was used before the job failure. ■ If the failure occurs during a verify job or a database consistency check job, the job restarts at the beginning. ■ Full backups that were interrupted and resumed from the point of failure do not display in the Simplified Disaster Recovery Recover This Computer Wizard. However, you can restore these backup sets manually after you make the initial recovery by using the Recover This Computer Wizard. ■ You can enable the checkpoint restart option for a full backup job that uses the Delete selected files and folders after successful backup option. If the job fails and is resumed, the files are not deleted from the source volume after the backup completes. Changing the default checkpoint restart settings You can change the default checkpoint restart settings in the error-handling rules settings. You can specify the number of times that you want checkpoint restart to retry a failed job, the interval between restart attempts, and the final job disposition for any jobs that cannot be successfully restarted. 529Configuration and settings Configuring checkpoint restart
- 530. To change default checkpoint restart settings 1 Click the Backup Exec button, select Configuration and Settings, and then select Error-Handling Rules. 2 Select Checkpoint Restart, and then click Edit. 3 Select Enable error-handling rule. 4 Select Retry job. 5 Complete the following fields: Enter the maximum number of times that you want Backup Exec to retry a job that fails. Maximum retries Enter the interval of time in minutes that you want Backup Exec to wait before it attempts to restart a job. Retry interval 6 In the Final job disposition group box, select one of the following options: Select this option to have Backup Exec place the job on hold if the job cannot be completed successfully after the maximum number of retries. The job remains on hold until the error condition has been manually cleared. Place job on hold until error condition has been manually cleared Select this option to have Backup Exec reschedule the job for its next scheduled occurrence if the job cannot be completed successfully after the maximum number of retries. Reschedule job for its next scheduled service 7 (Optional) In the Notes field, type any additional notes about the error-handling rule. 8 Click OK. Configuring Backup Exec to work with Symantec Endpoint Protection You can use Symantec Endpoint Protection version 11.0 or later with Backup Exec to provide extra security when the threat of viruses or malware is high. Symantec Endpoint Protection uses a ThreatCon level to provide an overall view of global Internet security. Symantec’s ThreatCon levels are based on a 1-4 rating system, with level 4 being the highest threat level. 530Configuration and settings Configuring Backup Exec to work with Symantec Endpoint Protection
- 531. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com You can configure Backup Exec to automatically run a backup job when the ThreatCon reaches a level that you specify. You may want to configure special jobs for your most crucial data, for example. This strategy helps make sure that your vital data is safely backed up as soon as global threats are detected. You should consider the types of jobs that you want to trigger automatically and the potential effect they can have on your system resources. The ThreatCon level is updated frequently and it can be raised at any time without warning. If you configure large or resource-intensive jobs to launch automatically, they may interfere with your normal business operations. The Backup Exec server must be connected to the Internet to monitor the ThreatCon level. If the Backup Exec server is not connected to the Internet, backup jobs are not triggered when the ThreatCon level elevates. See the Administrator’s Guide for Symantec Endpoint Protection for more information about Symantec Endpoint Protection. You can configure Backup Exec to work with Symantec Endpoint Protection as a default setting for all backup jobs. If you do not want to configure integration with Symantec Endpoint Protection for a particular job, you can override the default setting when you create the job. You do not have to create default settings for Symantec Endpoint Protection integration, however. If you want to use Symantec Endpoint Protection integration only for specific jobs, you can configure the settings when you create those jobs. To configure Backup Exec to work with Symantec Endpoint Protection 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure Symantec Endpoint Protection. To configure Symantec Endpoint Protection to work with all backup jobs 531Configuration and settings Configuring Backup Exec to work with Symantec Endpoint Protection
- 532. Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure Symantec Endpoint Protection to work with specific backup jobs 2 In the left pane, click Security. 3 Complete the following options: Select this option to run automatic backups when the Symantec ThreatCon reaches the level that you specify in the Symantec ThreatCon level field. You must have Symantec Endpoint Protection 11.0 or later installed on the same computer as Backup Exec to use this feature. Run a backup job immediately when an elevated Symantec ThreatCon level is reached Select the type of backup job that you want to run when the Symantec ThreatCon level is raised. Backup job Specify the ThreatCon level at which you want automatic backups to run. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com Symantec ThreatCon level 4 Click OK. See “Changing default backup job settings” on page 500. Configuring pre/post commands for backup jobs You can configure commands that you want to run before or after all backup jobs. For example, you may want to create a pre-command to shut down a database before a backup job runs. You could also create a post-command that restarts the database after the job is completed. Conditions that you can set for these commands include the following: ■ Run the backup job only if the pre-command is successful ■ Run the post-command only if the pre-command is successful ■ Run the post-command even if the backup job fails ■ Allow Backup Exec to check the return codes (or exit codes) of the pre- and post-commands to determine if the commands completed successfully 532Configuration and settings Configuring pre/post commands for backup jobs
- 533. If the pre- or post-command returns an exit code of zero, Backup Exec considers the job to have completed successfully. Backup Exec considers any non-zero exit codes to mean that the job encountered an error. If it is critical that the job does not run if the pre-command fails, configure Backup Exec to check the return codes. Backup Exec uses the return codes to determine if the pre-command failed or completed successfully. For example, if a pre-command that shuts down a database before a backup is run fails, the database could be corrupted when the backup runs. In this situation, it is critical that the backup job does not run if the pre-command fails. If Backup Exec is configured to check the return codes and the post-command returns a non-zero code, the job log reports that the post-command failed. You may have also selected to run the job only if the pre-command is successful. Even if both the pre-command and the job run successfully, Backup Exec marks the job as failed if the post-command fails. For example, the pre-command can run successfully and shut down the database. The backup job can also run successfully. But if the post-command cannot restart the database, Backup Exec marks the job and the post-command as failed in the job log. If you select the option On each server backed up, the pre- and post-command selections apply to each server independently. The pre- and post-commands are run and completed for one server at a time before they are run on the next selected server. You can configure pre-commands and post-commands as default settings for all backup jobs. If the default settings are not appropriate for a particular job, you can override them when you create the job. You do not have to create default settings for pre-commands and post-commands, however. If you want to use pre-commands and post-commands only for specific jobs, you can configure the settings when you create those jobs. To configure pre/post commands for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure default pre/post commnands. To configure default pre/post commands for all backup jobs 533Configuration and settings Configuring pre/post commands for backup jobs
- 534. Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure pre/post commands for specific backup jobs 2 In the left pane, click Pre/Post Commands. 534Configuration and settings Configuring pre/post commands for backup jobs
- 535. 3 Complete the following options: Runs a command on the specified server before the backup job runs. Use local paths, and make sure that the paths exist on each server and are correct. Type a command to run before the backup runs Commands that require user interaction, such as prompts, are not supported. Runs the backup job only if the pre-command is successful. If the pre-command fails, the job does not run, and is marked as failed. Run job only if pre-command is successful If it is critical that the job does not run if the pre-command fails, then select Let Backup Exec check the exit codes of the commands to determine if the commands completed successfully. If a non-zero code is returned, Backup Exec interprets it to mean that the pre-command did not run successfully. The job does not run and the job status is marked as Failed. Runs a command on the specified server after the backup job runs. Use local paths, and make sure that the paths exist on each server and are correct. Type a command to run after the backup runs Commands that require user interaction, such as prompts, are not supported. Runs the post-command after the verification completes, if you configured a verify operation for the job. Run post-command after job verification completes See “Configuring automatic verify operations for backup jobs” on page 519. Runs the post-command only if the pre-command is successful. Run post-command only if pre-command is successful If it is critical that the post-command does not run if the pre-command fails, then select Let Backup Exec check the exit codes of the commands to determine if the commands completed successfully. If a non-zero code is returned for the pre-command, Backup Exec interprets it to mean that the pre-command did not run successfully. The post-command does not run. If you also select Run job only if pre-command is successful, and both the pre-command and the job are successful, but the post-command returns a non-zero code, the job log reports both the job and the post-command as failed. 535Configuration and settings Configuring pre/post commands for backup jobs
- 536. Runs the post-command regardless of whether the job is successful or not. If you also select Let Backup Exec check the exit codes of the commands to determine if the commands completed successfully and the post-command returns a non-zero code, the job log reports the post-command as failed. Run post-command even if job fails Lets Backup Exec check the return codes of the pre- and post-commands to determine if they completed successfully. Backup Exec interprets an exit code of zero from either the pre- or post-command to mean that the command completed successfully. Backup Exec interprets a non-zero code to mean that the command ended with an error. After Backup Exec checks the return codes, it continues processing according to the selections you made for running the pre- and post-commands. If this option is not selected, the success of the pre- and post-commands is not determined based on the return code. Let Backup Exec check the exit codes of the commands to determine if the commands completed successfully Runs the pre- and post-commands on this Backup Exec server only. On this Backup Exec server Runs the pre- and post-commands one time on each server that is backed up. The pre- and post-command selections apply to each server independently. If you select this option, the pre- and post-commands are run and completed for each server before Backup Exec begins processing on the next selected server. On each server backed up Designates the number of minutes Backup Exec should wait before it cancels a pre- or post-command that did not complete. The default timeout is 30 minutes. Cancel command if not completed within x minutes 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. 536Configuration and settings Configuring pre/post commands for backup jobs
- 537. Configuring file and folder options for backup jobs You can configure options for how Backup Exec processes file system attributes such as junction points and symbolic links. File and folder options can be configured as default settings for all backup jobs. If the default settings are not appropriate for a particular job, you can override them when you create the job. You do not have to create default settings for files and folders, however. If you want to configure file and folder settings only for specific jobs, you can configure the settings when you create those jobs. To configure file and folder options for backup jobs 1 Do one of the following: Complete the following steps: ■ Click the Backup Exec button, and then select Configuration and Settings. ■ Select Job Defaults, and then select the type of backup for which you want to configure default file and folder settings. To configure default file and folder options for all backup jobs Complete the following steps: ■ Create a new backup definition or edit an existing backup definition. ■ In the Backup box, click Edit. To configure file and folder settings for specific backup jobs 2 In the left pane, click Files and Folders. 3 Complete the following options: 537Configuration and settings Configuring file and folder options for backup jobs
- 538. Backup method for files 538Configuration and settings Configuring file and folder options for backup jobs
- 539. Select one of the following backup methods: ■ By modified time When Backup Exec runs a full backup job or an incremental backup job, the time that the backup job starts is recorded in the Backup Exec Database. Backup Exec adds the time of the backup job to the Backup Exec Database only if the full backup job completes successfully. The next time that you run an incremental backup job or a differential backup job, Backup Exec compares the file system time to the backup time. If the file system time is later than the time that is recorded in the database, the file is backed up. If the file's modified time is older than the previous backup's modified time, that file is not backed up. If the job does not complete successfully, subsequent differential or incremental backup jobs back up all of the data instead of only the data that has changed. Note: A file's last modified date and timestamp do not change when the file is copied or moved. To ensure that the files are protected, run a full backup after you copy or move files. When you run an incremental backup job, Backup Exec records a new time in the Backup Exec Database. The database time is not updated for differential backup jobs. When you select the modified time method, Backup Exec uses the Windows change journal to determine if a file has changed since the last time it was backed up. If the change journal is not available, Backup Exec compares the file information to the previous backup time to determine if the file has changed. Using modified time lets Backup Exec run more accurate incremental backups or differential backups even if other processes have modified files' archive bits. ■ Using archive bit Backup Exec uses the archive bit from the file system to determine if a file has changed since the last time it was backed up. When you use the archive bit, Backup Exec turns the archive bit off when a file is backed up. Turning off the archive bit indicates to Backup Exec that the file has been backed up. If the file changes again before the next backup job, the bit is turned on again. 539Configuration and settings Configuring file and folder options for backup jobs
- 540. Backup Exec backs up the file in the next backup. If the next backup job is a full backup job or an incremental backup job, the bit is turned off when the backup job completes. If the next backup job is a differential backup job, the archive bit is left intact. ■ Using catalogs Backup Exec compares path names, modified time, deleted and renamed files and folders, and other attributes. When you select the catalog method, Backup Exec uses the Windows change journal to determine if a file has changed since the last time it was backed up. If the change journal is not available, Backup Exec compares the file information to previous catalogs to determine if it has changed. Note: You cannot use Backup Exec catalogs to determine if files were backed up for any differential backups. The catalog method is only available if the Advanced Disk-based Backup Option (ADBO) is installed. Note: The off-host backup feature of ADBO does not support the catalog method. See “How Backup Exec determines if a file has been backed up” on page 187. Select this option if you want Backup Exec to check the NTFS volume for identical files. If Backup Exec finds multiple copies of a file, it backs up only one instance of that file. Single instance backup can considerably reduce the storage space that is required for your backups. Many applications automatically generate some files that have identical content. The actual amount of space that you save depends on the number of duplicate files on the volume. This option displays only if you use the Microsoft Windows Single Instance Store (SIS) feature. Warning: If the backup job does not run to completion, the file data may not be included in the backup set. Rerun the backup job until it is successfully completed. If it was an incremental backup, running the job again does not back up the same files. You must run a full or duplicate backup job to ensure that all files are backed up completely. Enable single instance backup for NTFS volumes 540Configuration and settings Configuring file and folder options for backup jobs
- 541. Select this option to back up the information for the junction points and the files and directories to which they are linked. If this check box is not selected, then only the information for the junction points is backed up. The files and directories to which the junction points are linked are not backed up. Backup Exec does not follow junction points that are automatically created by Microsoft Windows because it can cause the data to be backed up repeatedly. For more information, see the following Symantec knowledge base article: http://entsupport.symantec.com/umi/V-269-9 You cannot select any mounted drives that do not have a drive letter assigned to them. The files and directories to which they are linked are backed up regardless of whether this option is selected. If the files and directories to which the junction points are linked are also included in the backup selections, then they are backed up twice. They are backed up once during the full file and directory backup job, and again by the junction point. Warning: If a junction point is linked to a location that encompasses it, then recursion (a situation where data is backed up repeatedly) occurs. Recursion results in an error and a job failure. For example, if c:junctionpoint is linked to c:, recursion occurs when Backup Exec attempts to back up c:junctionpoint, and the backup job fails. Back up files and directories by following junction points and mount points Select this option to back up the information for any symbolic links and the files and directories to which they are linked. If you do not select this option, only the information for the symbolic links is backed up. The files and directories to which they are linked are not backed up. If the symbolic link points to files and directories on a remote computer, the files and directories on the remote computer are not backed up. Back up files and directories by following symbolic links 541Configuration and settings Configuring file and folder options for backup jobs
- 542. Select this option to back up any data that has been migrated from primary storage to secondary storage. The data is not recalled to its original location. It is backed up directly to the backup media. If this option is selected, you should not run a backup of your entire system. Backup Exec has to load the data that has been migrated to secondary storage and additional time is required for migrated data. If this check box is cleared, only the placeholder that stores the location of the data on secondary storage is backed up, not the data itself. This option should not be selected if the device used for secondary storage and backups contains only one drive. If there is only one drive, Remote Storage and Backup Exec compete for use of the drive. Back up data in Remote Storage 542Configuration and settings Configuring file and folder options for backup jobs
- 543. Select one of the following options to determine how Backup Exec processes any open files for the backup job. The options are as follows: ■ Never Backup Exec skips any open files that are encountered during the backup job. A list of any files that were skipped appears in the job log. ■ If closed within X seconds Backup Exec waits the specified time interval for files to close before it skips them and continues the backup job. If the file does not close during the specified interval, it is skipped. A list of skipped files appears in the job log. If multiple files are open, Backup Exec waits the specified time interval for each file. Depending on the number of open files, the wait may significantly increase the backup time. ■ With a lock Backup Exec attempts to open any files that are in use. If Backup Exec is able to open a file, the file is locked while it is backed up. Locking the file prevents other processes from writing to it. Backing up open files is not as effective as closing applications and allowing the files to be backed up in a consistent state. ■ Without a lock Backup Exec attempts to open any files that are in use. If Backup Exec is able to open the file, the file is not locked while it is backed up. Other applications can write data to the file during the backup operation. Warning: This option allows some files that contain inconsistent data and possibly corrupt data to be backed up. Back up open files Select the backup method that you want to use to back up files and folders for each backup job in the backup definition. See “Backup methods in Backup Exec” on page 176. Backup method 543Configuration and settings Configuring file and folder options for backup jobs
- 544. Select this option if you want Backup Exec to delete the data you selected to back up after the backup job completes successfully. Backup Exec backs up the selected data, verifies the backup sets, and then deletes the data from the server. The logon account credentials that you use to run the job must also have the rights to delete a file. Otherwise, the data is backed up, but it is not deleted. Note: This option is only available when you configure backup jobs. You cannot configure it as a default setting for all backup jobs. See “Configuring Backup Exec to automatically delete files after a backup” on page 190. Delete selected files and folders after successful backup Select this option to retain the file system's directory structure for the files that are backed up in a full backup job. This option is available only when you select the Delete selected files and folders after successful backup option. Preserve tree on back up and delete 4 Click OK. See “Changing default backup job settings” on page 500. See “Backing up data” on page 146. Setting default schedule options for rule-based jobs and run now jobs You can configure default schedule options for rule-based and run now jobs. Backup Exec applies the schedule options whenever you change a run now job or a rule-based job into a recurring scheduled job. A rule-based job is a job that is linked to another job. The rule-based job runs when the job to which it is linked is finished. An example of a rule-based job would be a duplicate stage that is configured to run when a full backup job completes. If you change the duplicate stage's schedule settings, Backup Exec uses the default schedule settings for the duplicate stage. You can override the default settings when you edit the newly scheduled job. To set default schedule options for rule-based jobs and run now jobs 1 Click the Backup Exec button, select Configuration and Settings, and then select Job Defaults. 2 Select Schedule. 544Configuration and settings Setting default schedule options for rule-based jobs and run now jobs
- 545. 3 In the Recurrence Pattern group box, select the default frequency for backup jobs: Click Hours, and then enter the frequency in the Every X hour/minute field. Choose between the following options: ■ From Designate the starting time for a job to run. ■ Between Restrict the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday. To run jobs every X hours or minutes Click Days, and then choose between the following options: ■ Every X day Indicate the number of days between the start time of a job and the start time of the next job instance. ■ Every weekeday Specifies that the job should run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays. To run jobs every X days Click Weeks, and then specify the number of weeks between the start time of a job and the start time of the next job instance in the Every X week on field. Select the days and time at which jobs should run. To run jobs every X weeks 545Configuration and settings Setting default schedule options for rule-based jobs and run now jobs
- 546. Click Months, and then choose between the following options: ■ Day X of every X month Specify the specific day on which jobs should run and indicate the number of months between the start time of a job and the start time of the next job instance. ■ Every X X of every X month Specify the day on which jobs should run and indicate the number of months between the start time of a job and the start time of the next job instance. ■ Selected days of the month Specify the days of the month on which Backup Exec should run jobs. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current week and day of the month. For example, if you create the job on the third Monday of the month, the default setting is for the job to run once a month on the third Monday. You can select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. ■ Selected dates of the month Specify the dates of the month on which Backup Exec should run jobs. The recurrence pattern that you select repeats itself every month. The default setting is for the job to run every month on the current date of the month. For example, if you create the job on the 15th, the default setting is for the job to run once a month on the 15th. You can select additional days on which the job should run. Any additional days that you select are added to the monthly recurrence pattern. If you select the 31st, the job runs on the last day of the month in months that do not have 31 days. For example, if you configure the job to run on the 31st, in September the job runs on the 30th instead. To run jobs every X months 546Configuration and settings Setting default schedule options for rule-based jobs and run now jobs
- 547. Click Years, and then enter the frequency in the Every X year field. Choose between the following options: ■ On X Specify the date on which Backup Exec should run jobs. ■ On the X of X Specify the day and month of the year on which Backup Exec should run jobs. To run jobs every X years 4 (Optional) Click Calendar to view all scheduled backup jobs on a calendar to check for scheduling conflicts. 5 In the Reschedule the job if it does not start X hours after its scheduled start time field, specify the amount of time past the job's scheduled start time at which Backup Exec changes the job completion status to Missed. The job is rescheduled to run based on the time window that you configured. 6 In the Cancel the job if it is still running X hours after its scheduled start time field, specify the amount of time after the job's scheduled start time at which you want to cancel the job if it is still running. Backup Exec changes the job completion status to Canceled, timed out. 7 Click OK. See “How job scheduling works in Backup Exec” on page 203. See “List of job statuses in Backup Exec” on page 264. Excluding dates from the backup schedule for all backups You can exclude specific dates, such as holidays, from your backup schedule. You may want to exclude holidays, for example, to ensure that Backup Exec does not run jobs on those days. You can exclude dates from the schedule for a specific backup job or you can exclude dates for all backup jobs. When you exclude dates for all backups, any scheduled backup jobs do not run on those dates. All jobs resume running on their normal schedules after the exclude date. You can still create and run backup jobs and restore jobs on excluded dates, as long as they are not scheduled. You can exclude dates in Backup Exec by selecting or typing dates on the Exclude Dates dialog box. Or you can create a text file with a list of dates to exclude and then import the text file. 547Configuration and settings Excluding dates from the backup schedule for all backups
- 548. After you create a list of dates to exclude, you can export a new text file with those dates. Exporting the text file can be useful if you want to copy your exclude dates from one Backup Exec server to another. See “Exporting a list of dates that are excluded from all backups to another server” on page 550. You can exclude dates from all backups in the job default settings or by using the backup calendar. Both features let you exclude dates from all backups. You can only import dates using the default settings. However, you may prefer to use the backup calendar because it gives you a visual representation of all of your scheduled jobs. This topic includes the following procedures: To exclude dates from the backup schedule for all backups To exclude dates from all backups using the backup calendar To exclude dates from the backup schedule for all backups 1 Click the Backup Exec button, select Configuration and Settings, and then select Job Defaults. 2 Select Exclude Dates. 3 Do any of the following: Complete the following steps: ■ In the Select Date field, type the date that you want to exclude from the backup schedule. ■ Click Add. Note: You can add only one date at a time. To manually enter the date Click the date that you want to exclude. The calendar displays 3 months at a time. You can navigate forward and backward to view additional months by clicking the arrows. Note: You can select only one date at a time. To select the date from the calendar Complete the following steps: ■ Click Browse. ■ Select the text file that contains the exclude dates. ■ Click Open. ■ Click Import. To import a list of dates 548Configuration and settings Excluding dates from the backup schedule for all backups
- 549. Complete the following steps: ■ Select the date or dates that you want to remove from the list. ■ Click Delete. To delete a date from the list of dates to exclude 4 When you are finished selecting dates, click OK. To exclude dates from all backups using the backup calendar 1 On the Backup and Restore tab, in the Backups group, click Backup Calendar. 2 Select the date that you want to exclude from the backup schedule. 3 Click Exclude Dates. 4 Click Add exclude date for all backups. Note: To remove the exclusion from a selected date, click Remove exclude date for all backups. 5 Click Close. Removing dates from the list of excluded dates If you no longer want to exclude a date from your backup schedule, you can remove it from the list of excluded dates. When you remove a date from the list of excluded dates, the date becomes part of your regular backup schedule. Any recurring jobs that normally fall on that day are now scheduled to run rather than being skipped. To remove dates from the list of excluded dates 1 Click the Backup Exec button, select Configuration and Settings, and then select Job Defaults. 2 Select Exclude Dates. 3 Select the date or dates that you want to remove from the list of excluded dates. You can also remove dates from the list of excluded dates by clicking the excluded dates on the calendar. 4 Click Delete. 5 When you are finished removing dates from the list, click OK. See “Excluding dates from the backup schedule for all backups” on page 547. 549Configuration and settings Removing dates from the list of excluded dates
- 550. Exporting a list of dates that are excluded from all backups to another server You can exclude specific dates, such as holidays, from your backup schedule. When you exclude dates, any regularly scheduled backups do not run on those dates. You can create a list of dates to exclude in Backup Exec. See “Excluding dates from the backup schedule for all backups” on page 547. You can import or export a list of dates to exclude as a text file. This may be useful if you want to copy a list of exclude dates from one Backup Exec server to another. To export a list of exclude dates 1 Click the Backup Exec button, select Configuration and Settings, and then select Job Defaults. 2 Select Exclude Dates. 3 Click Export. 4 Browse to the location where you want to save the text file. 5 Click Save. Changing the default preferences You can change the settings for how you prefer Backup Exec to display various screens, indicators, and alerts. To change the default preferences 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Preferences. 550Configuration and settings Exporting a list of dates that are excluded from all backups to another server
- 551. 3 Configure any of the following preferences: Clear this option to show the Backup Exec Administration Console instead of the splash screen when you start Backup Exec. Show splash screen at startup Select this option to display the percentage complete number while a backup job runs. These indicators appear in the Job Activity dialog box, and they let you monitor the progress of the active job. Backups might take longer to complete when this option is selected because the backup sources must be scanned to determine the amount of data to be backed up. Due to the amount of time that is required to scan the backup sources, you should not select this option when you back up remote resources. Display progress indicators for backup jobs. This requires additional time to pre-scan resource. Select this option to participate in the Symantec Backup Exec product improvement program. General Backup Exec usage and statistical information is periodically collected and sent anonymously to Symantec. Symantec uses the information to help improve the Backup Exec customer experience. Note: Although usage and statistical information is collected, Symantec never collects specific user information. Allow Backup Exec to report anonymous usage information (No personally identifiable information will be returned to Symantec). Select this option to display alternating row colors for all lists in Backup Exec. Alternating row colors can make it easier to distinguish between rows. Use alternating row colors Select this option to enable any messages that you have disabled. Re-enable 4 Click OK. Configuring the default setting for backing up multiple servers or applications You can select to back up multiple servers or applications at once using Backup Exec. You can back them up as part of one backup definition or you can back them up individually in separate backup definitions. It may be easier for you to manage 551Configuration and settings Configuring the default setting for backing up multiple servers or applications
- 552. backing up multiple servers as part of one backup definition. However, it is easier to troubleshoot job failures if each server has its own backup definition. Each time you create a backup definition that contains multiple servers or applications, you can select whether you want to create one backup definition or separate backup definitions. You can configure a default scenario for backing up multiple servers or applications so that Backup Exec automatically creates either one backup definition or separate backup definitions. To configure the default setting for backing up multiple servers or applications 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings. 2 In the left pane, select Backups. 3 Select one of the following: ■ Create one backup that includes all servers or applications ■ Create separate backups for each server or application 4 If you want Backup Exec to prompt you each time you select to back up multiple servers or applications, select Prompt each time I create a backup for multiple servers. If you disable the prompt, Backup Exec automatically uses the preference that you selected in the When creating backups for mulitple servers field. You can enable the prompt at any time. See “Backing up data” on page 146. Configuring database maintenance and security The Database Maintenance and Security option lets you manage the Backup Exec Database. Each database maintenance operation is performed independently on each database. The Backup Exec Database maintains a record of the files and data that you have configured. Database maintenance lets you perform the following: ■ Optimize database size. ■ Delete expired data. ■ Save the contents of the database files. ■ Perform a database consistency check. Backup Exec generates informational alerts at the beginning and at the end of the database maintenance process each time database maintenance is performed. 552Configuration and settings Configuring database maintenance and security
- 553. The alerts provide details about the type of maintenance that was performed on each database and the amount of time that the maintenance took to complete. If the database maintenance process fails, the alert indicates where the failure occurred and the reason for the failure. You do not have to select all the options; however, each one performs a different process that enables you to protect and maintain your database. Selecting all the options enables you to recover the database quickly and maintain optimal performance. You can also export the Backup Exec Database encryption key. The Backup Exec Database encryption key is used to secure the Backup Exec Database. The key is required for a number of disaster recovery and migration scenarios. You should export the encryption key to a safe location to ensure that you have it later. To configure database maintenance and security 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings. 2 In the left pane, click Database Maintenance and Security. 3 To enable database maintenance, select the Enable Backup Exec database maintenance option. 553Configuration and settings Configuring database maintenance and security
- 554. 4 Configure any of the following options: Select the time that you want to perform database maintenance. Perform database maintenance daily at All the maintenance occurs once a day at the time you specify. Select this option to delete expired job history, job logs, alert history, and reports from the Backup Exec Delete aged data Database after the specified number of days have passed. Select this option to keep all job history data for any media to which an overwrite protection period is currently assigned. Keep job history for data on media that have current overwrite protection periods After a media’s overwrite protection period expires, the media’s job history data can be deleted. Select this option to indicate the number of days to keep job history data in the database before it is deleted. Keep job history for specified number of days Job history data includes summary statistics for a job and details about media, devices, and any backup sets that were used to process the job. Indicate the number of days to keep job logs in the database before they are deleted. Job logs Job logs include detailed information about the job. Indicate the number of days to keep alert history data in the database before it is deleted. Alert history Alert history data includes property and response information for the alert. Indicate the number of days to keep report data in the database before it is deleted. Reports Report data includes property information about any report jobs that were generated. The report itself is not deleted. Indicate the number of days to keep audit log data in the database before it is deleted. Audit logs The audit log includes information about any operations that are performed in Backup Exec. See “Configuring audit logs” on page 617. 554Configuration and settings Configuring database maintenance and security
- 555. Select this option to check the logical consistency and physical consistency of the data in the database. The option is not checked by default. Symantec recommends that you run a consistency check periodically at a time when there is minimal activity from Backup Exec. Perform database consistency check Select this option to save the data that is contained in the database to the Backup Exec data directory so that the database backup file (BEDB.bak) can be backed up. The dump file is maintained in the data directory until the next database maintenance process is performed and then this file is overwritten. Selecting this option enables you to recover the database in the event of failure. Save contents of database to the Backup Exec data directory Select this option to organize fragmented pages and decrease the size of the physical database to 10 percent above what is actually used. Optimize database size 5 To export the database encryption key, type the path to a secure location in the Path field, and then click Export. You should export the encryption key to a safe location to ensure that you have a copy of it for later. You need the encryption key to perform disaster recovery or migrate the Backup Exec server. The key is named with a unique hash value. Backup Exec uses the name to identify the key later. See “Exporting the Backup Exec Database encryption key” on page 555. 6 Click OK. See “Configuring encryption for the connection to the Backup Exec Database” on page 558. Exporting the Backup Exec Database encryption key Backup Exec stores sensitive information in the Backup Exec Database using encryption. When you install or upgrade Backup Exec, it automatically creates a database encryption key. The database encryption key is used to encrypt information such as login account credentials and the keys that are used for encrypted backup jobs, for example. It is stored in the Data folder in the Backup Exec installation directory. 555Configuration and settings Exporting the Backup Exec Database encryption key
- 556. You are required to provide the Backup Exec Database encryption key for each of the following scenarios: ■ Performing a manual disaster recovery of a Backup Exec server ■ Performing a disaster recovery of a Backup Exec server using Simplified Disaster Recovery (SDR) ■ Migrating Backup Exec from one computer to another computer ■ Resolving any situations in which the database encryption key on the Backup Exec server is corrupted or goes missing Symantec recommends that you export the Backup Exec Database encryption key to a secure location so that you can access it later if it is needed. You should repeat the following procedure on each Backup Exec server in your environment, including the central administration server and each managed Backup Exec server in Central Admin Server Option (CASO) deployments. Note: When you perform a rolling upgrade in a CASO environment, the database encryption key for the central administration server is only generated when all of the managed Backup Exec servers are upgraded to the current version of Backup Exec. Make sure that you export the database encryption key to a location that meets the following criteria: ■ The destination is either on a physical volume that is assigned to a drive letter or a network share that is specified by a UNC path (network shares that are mapped to drive letters are not supported) ■ The destination has enough disk space ■ The destination is accessible from the Backup Exec server ■ Backup Exec has permission to write to the destination To export the Backup Exec Database encryption key 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Database Maintenance and Security. 3 In the Path field, type the location to which you want to export the encryption key. 556Configuration and settings Exporting the Backup Exec Database encryption key
- 557. 4 Click Export. The key is exported to the location that you specified. The key is named with a unique hash value. Backup Exec uses the name to identify the key later. If you want to export the key to additional locations, repeat steps 3 and 4. 5 Click OK. See “Configuring database maintenance and security” on page 552. See “Refreshing Backup Exec Database encryption keys” on page 557. See “Configuring encryption for the connection to the Backup Exec Database” on page 558. Refreshing Backup Exec Database encryption keys Backup Exec stores sensitive information in the Backup Exec Database using encryption. A database encryption key is used to encrypt information such as login account credentials and the keys that are used for encrypted backup jobs, for example. The key is stored in the Data folder in the Backup Exec installation directory. It is required for many disaster recovery and migration scenarios. Backup Exec automatically creates the Backup Exec Database encryption key. However, you may want to refresh the key if the existing key is compromised in any way. You may also be required to change the key if your organization requires that keys or passwords be changed periodically. Note: You must have a functioning database encryption key to complete the procedure below. Complete the following procedure to refresh the Backup Exec Database encryption key. To refresh Backup Exec Database encryption keys 1 In Windows, click Start and then click Run. 2 Type Regedit and then click OK. Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. You should take great care when you make changes to the Windows registry. Registry modifications should only be carried out by persons who are experienced in the use of the registry editor application. Symantec recommends that you make a complete backup of the registry and computer before making any registry changes. 557Configuration and settings Refreshing Backup Exec Database encryption keys
- 558. 3 Locate and right-click the following registry key: HKEY_LOCAL_MACHINESOFTWARESymantecBackup Exec For WindowsBackup ExecServerDatabaseEncryptionAction 4 Click Modify. 5 In the Value data field, type 2. 6 Click OK. 7 Restart all Backup Exec services. Backup Exec creates a new Backup Exec Database encryption key. Symantec recommends that you export the new key to a secure location so that you can access it later if it is needed. See “Exporting the Backup Exec Database encryption key” on page 555. Configuring encryption for the connection to the Backup Exec Database The Backup Exec Database contains sensitive information about your organization, including user account credentials and backed up data. Securing Microsoft SQL Server's connection to the Backup Exec Database is an important step in protecting your network from outside access. Microsoft recommends that you use SSL encryption any time data that is transmitted between SQL Server and an application travels across a network. Data transmission between the Backup Exec services and the SQL instance can travel across the network in the following scenarios: ■ You configure the Backup Exec Database as a centralized database and it is located on a central administration server in a CASO environment. Data can also travel across the network in variations of this scenario, for example when you use a managed Backup Exec server or when you use shared storage. ■ You use a remote SQL instance for the Backup Exec Database so that the Backup Exec services must access the database across the network. Backup Exec automatically enables SSL encryption if you use the default, local SQL Express instance called "BKUPEXEC". If you configure Backup Exec to use any other SQL Server instance, you must configure encryption yourself. SQL Server uses certificates to encrypt data. You can generate your own certificates or you can let SQL Server use an automatically generated, self-signed certificate. By default, Backup Exec uses the self-signed certificates that SQL Server automatically generates. However, Symantec recommends that you create and use your own certificates for additional security. 558Configuration and settings Configuring encryption for the connection to the Backup Exec Database
- 559. Note: Using encryption may affect the performance of communications between SQL Server and the Backup Exec Database. It involves an extra round trip across the network as well as time to encrypt and decrypt the data. Refer to the Microsoft knowledge base for more information about Secure Sockets Layer (SSL) and encrypting connections to SQL Server. To generate and install certificates for secure SQL connections (optional) You can use your own certificates or you can let SQL Server use an automatically generated, self-signed certificate. Symantec recommends that you use your own certificates for improved security. Once you have generated and installed your certificate, you can proceed to configure the secure SQL connection to the Backup Exec Database. Microsoft has requirements that must be followed when you use your own certificates for SQL Server. Certificates can be either self-signed or issued from a certification authority. Certification authorities can be either a local authority in your organization's domain or a known third-party authority. For more information about Microsoft's certification requirements, refer to the following Microsoft article: Encrypting Connections to SQL Server Before you configure encryption, you must import the certificates that you want to use into the local certificate store of the computer that hosts the Backup Exec Database. For more information about importing and installing a certificate on the server, refer to the following Microsoft article: How to: Enable Encrypted Connections to the Database Engine (SQL Server Configuration Manager When you import certificates, you should use the same user account under which the SQL Server service runs: ■ If the SQL Server is running under a default computer account such as LocalSystem, NetworkService, or LocalService, then you should use the Computer account option when you import the certificate. Selecting to manage certificates for the computer account ensures that the certificate is placed under the Personal store of the default computer account. 559Configuration and settings Configuring encryption for the connection to the Backup Exec Database
- 560. ■ If the SQL Server is running under a specific domain account, you must be logged in using the same domain account to import the certificate. When you log into the Microsoft Management Console, select the My user account option. Selecting to manage certificates for the user account ensures that the certificate is placed under the Personal store of the user who is also running the SQL service account. 560Configuration and settings Configuring encryption for the connection to the Backup Exec Database
- 561. To configure secure SQL connections to the Backup Exec Database Backup Exec automatically enables encryption for SQL connections if you use the default, local SQL Express instance called "BKUPEXEC". If you configure Backup Exec to use any other SQL Server instance, you must configure encryption yourself. You should configure the secure connection on the computer on which the SQL instance hosts the Backup Exec Database. In some Backup Exec environments, you may need to configure the secure connection more than once: 561Configuration and settings Configuring encryption for the connection to the Backup Exec Database
- 562. You must configure a secure SQL connection on each node in the cluster. If the cluster has not been created yet, configure the secure SQL connection before you run the Cluster Configuration Wizard in Backup Exec. If the cluster has already been created: ■ Bring the Backup Exec cluster offline using Windows Failover Cluster Manager. ■ Complete the following procedure on each node in the cluster. ■ Bring the Backup Exec cluster online using Windows Failover Cluster Manager. For clustered Backup Exec environments You must configure a secure SQL connection on each computer in the CASO environment, including the central administration server and any managed Backup Exec servers. For Central Admin Server Option (CASO) environments Use the SQL Server Configuration manager to edit the properties of the protocols for the server that you want to configure. If you want to configure encryption for the default, local database instance that Backup Exec installs, edit the Protocols for BKUPEXEC. Select the certificate that you want to use, if you created a certificate. Then select whether you want to force encryption for the database connection. When you have finished, restart SQL Server and the Backup Exec services from the Services Manager. For more information or instructions for configuring encrypted connections for SQL, refer to the Microsoft knowledge base. Scheduling Backup Exec to check logon accounts You can schedule Backup Exec to check that the backup sources in jobs can be accessed with the logon accounts that you selected. Checking whether your logon accounts have access to backup sources lets you diagnose and fix any access issues before you run backup jobs. If Backup Exec discovers any backup sources that cannot be accessed with the logon accounts that you selected, it reports the error in an alert. By default, Backup Exec is scheduled to check logon accounts every day at 1:00 am. You can disable the test if you do not want Backup Exec to regularly check logon accounts. You can also reschedule the test so that it occurs less frequently. 562Configuration and settings Scheduling Backup Exec to check logon accounts
- 563. To schedule Backup Exec to check logon accounts 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Logon Accounts. 3 Configure any of the following options: Select this option to test whether Backup Exec can access the backup sources in your backup jobs with the logon accounts that you selected. Check that the backup sources in jobs can be accessed with the logon accounts you selected Enter the interval for Backup Exec to test logon accounts. Backup Exec automatically tests the logon accounts at the interval that you select in this field. You can select the time at which you want Backup Exec to run the test and the number of days between tests. Perform check every X days at X Select this option to limit the logon account test to the server level. If you select this option, Backup Exec tests only whether the logon accounts can access backup sources at the server level. Any resources that reside on the server are not tested. The logon account test takes less time if you only check accounts at the server level, however it is less thorough. Check logon accounts only at the server level 4 Click OK. See “Backup Exec logon accounts” on page 603. Configuring Backup Exec to discover data to back up Backup Exec’s Discover Data to Back Up option detects new backup content within a Windows or Active Directory domain. This option lets you configure a job that searches for new server volumes, databases, or application data. By default, the data discovery operation runs at noon every day. It also runs each time the Backup Exec services are restarted. Backup Exec cancels the operation if it is still running after four hours. You can disable the operation or change the default settings in the global Backup Exec settings. The Discover Data to Back Up option performs three main tasks: ■ Discovers any top-level computers or computer contents When the data discovery operation discovers top-level computers or computer contents, it adds them to the Credentials pane on the Backup and Restore 563Configuration and settings Configuring Backup Exec to discover data to back up
- 564. tab. The operation updates any information about the computers or computer contents and their backup status. You can view information about backup sources on the Credentials pane. ■ Discovers any servers that do not have an Agent for Windows installed on them If the operation discovers any servers that do not have an Agent for Windows installed on them, Backup Exec sends you an alert. You can add the servers to the list of servers by using the Add a Server Wizard. After you add the servers to the list of servers, you can back them up and monitor them. See “Adding discovered servers to the list of servers in Backup Exec” on page 565. ■ Discovers and validates instances of the Agent for Windows The data discovery operation searches for any instances of the Agent for Windows on your network. When it finds an Agent for Windows, the operation checks the version to make sure that it is up to date. If an Agent for Windows is not up to date with the most recent version, Backup Exec sends you an alert. The data discovery operation only discovers the servers that meet the following criteria: ■ Belongs to the same domain as the Backup Exec server ■ Has the Windows Management Instrumentation (WMI) service enabled and running ■ Allows WMI access for the same user that the Backup Exec Management Service runs under Members of the server's "Administrators" group have this level of access. ■ Has firewalls that are configured to allow WMI network traffic To configure Backup Exec to discover data to back up 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Discover Data to Back Up. 564Configuration and settings Configuring Backup Exec to discover data to back up
- 565. 3 Configure any of the following options: Select this option to allow Backup Exec to discover any data that needs to be backed up. When this option is selected, Backup Exec automatically checks your network for any data that has not been backed up. Discover servers that have data that has not been backed up Lets you configure the frequency with which Backup Exec searches for any data that needs to be backed up. You can select to let Backup Exec search for any data that needs to be backed up daily, weekly, or monthly. Frequency Lets you configure the interval at which Backup Exec searches for any data that needs to be backed up. You can select different intervals based on the frequency you selected. Interval Lets you select the number of hours after which the data discovery process is canceled if it is not finished. Canceling the data discovery process can help prevent it from affecting your system resources. Cancel data discovery if not completed within 4 Click OK. Adding discovered servers to the list of servers in Backup Exec You can use the Add Server Wizard to install the Agent for Windows on any servers that Backup Exec discovers by the Discover Data to Back Up option. After you install the Agent for Windows, the server is added to the list of servers in Backup Exec. To add discovered servers to the list of servers in Backup Exec 1 On the Backup and Restore tab, in the Servers and Virtual Hosts group, click Add. 2 Select Microsoft Windows computers and servers, and then click Next. 3 Select Allow Backup Exec to establish a trust with the servers, and then click Next. 4 Click Browse. 565Configuration and settings Adding discovered servers to the list of servers in Backup Exec
- 566. 5 Expand Servers without an Agent for Windows installed to see the names of the servers that the data discovery operation discovered. 6 Select the servers on which you want to install the Agent for Windows, and then click OK. 7 In the Logon Account field, select the logon account that you want to use to access each server. 8 Click Next. 9 Select any of the following options and then click Next. Upgrades the Agent for Windows on the server that you are adding to the list of servers, if necessary. Upgrade the Backup Exec Agent for Windows to the current version automatically Restarts the remote computer after the Agent for Windows is installed. Restart the remote computer automatically after installing the Backup Exec Agent for Windows when a restart is required 10 Click Install. See “Configuring Backup Exec to discover data to back up” on page 563. Backup networks The backup network feature lets you direct any primary backup traffic that Backup Exec generates to a specific local network. Directing backup jobs to a specified local network isolates the backup data so that other connected networks are not affected when backup operations are performed. You also can use a backup network when you restore data. The feature is enabled on the Backup Exec server and lets you protect all the remote computers that reside on the specified local network. When you specify a backup network and submit a job, Backup Exec verifies that the remote computer is on the same subnet as the selected interface on the Backup Exec server. If the remote computer is on the selected subnet, then the backup operation is performed. If the remote computer is not on the selected subnet, then the job fails. However, you can set up Backup Exec to use any available network to back up remote computers. The following diagram shows an example of a backup network configuration. 566Configuration and settings Backup networks
- 567. Figure 14-1 Example of backup network backup network network ID: 128.10.0.0 subnet mask: 255.255.0.0 router A router B Backup Exec server email userdatabase user database and email user Exchange server Database server IP address: 128.10.0.1 IP address: 10.67.0.1 IP address: 128.10.0.2 IP address 128.10.0.3 corporate network network ID: 128.20.0.0 subnet mask: 255.255.0.0 IP address: 10.67.0.2 IP address: 10.67.0.3 In the example, the database server and mail server are connected to both the backup network and the corporate network. When the Backup Exec server performs backup operations, the backup data uses either the backup network or the corporate network to back up the database server. If the backup data goes through the corporate network, the amount of time it takes to back up the database server increases. The amount of time increases because the network route between the two computers is longer. Users may experience network latencies when they access the mail server since there is an increase in network traffic. In contrast, if you specify a backup network and you back up the database server, the backup data traffic is isolated to the backup network. Any users accessing the mail server are not affected. The backup network is used to perform all backup operations, unless the remote computer is not connected to the backup network. To back up any remote computers that are not connected to the backup network, choose to use any available network route. Choosing any available network lets you back up the remote computer even though it does not reside on the backup network. You can configure global network settings for all backup jobs on the Network and Security pane in the Backup Exec settings. If you want to override the global settings 567Configuration and settings Backup networks
- 568. for a particular backup job, you can configure network settings for individual jobs on the Network pane when you create backups. See “Changing network and security options for Backup Exec” on page 568. See “Configuring network options for backup jobs” on page 192. See “Using Backup Exec with firewalls” on page 570. Using IPv4 and IPv6 in Backup Exec Backup Exec supports versions 4 and 6 of the Internet Protocol (IP), which are commonly referred to as IPv4 and IPv6. You can use IPv4 and IPv6 in backup and restore networks. Support for IPv6 is dependent upon operating system support for the protocol, as well as proper network configuration. You can use Backup Exec in a mixed IPv4/IPv6 environment or an IPv4-only environment. Enter an IPv4 or IPv6 address for a computer anywhere that you can enter a computer name in Backup Exec, except in the following locations: ■ Clusters. Microsoft Windows does not support an IPv6 address as a clustered computer. ■ The Connect to Backup Exec Server dialog box. A Backup Exec agent that supports IPv6 can be backed up or restored using IPv6 only from a Backup Exec server that is IPv6-compliant. Changing network and security options for Backup Exec You can configure how Backup Exec works with your network configuration and security. The network and security options are global options that affect all Backup Exec jobs. If the global network and security settings that you configure do not apply for a specific backup job, you can change the network settings when you create the backup job. See “Configuring network options for backup jobs” on page 192. To edit network and security options 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Network and Security. 3 Configure any of the following options: 568Configuration and settings Changing network and security options for Backup Exec
- 569. Select the name of the network interface card that connects the Backup Exec server to the default network that you want to use for backup jobs. The list includes all available network interfaces on the Backup Exec server. Network interface Select the default protocol you want to use for backup jobs. The options are as follows: ■ Use any available protocol ■ IPv4 ■ IPv6 Protocol Select the 32-bit number that determines the subnet to which the network interface card belongs. Subnet Select this option to let Backup Exec use any available network if the remote system that you selected for backup or restore is not part of the specified backup network. If you do not select this option and the remote system is not part of the specified backup network, the job fails. Backup Exec cannot access the data from the remote system. Allow use of any available network interface, subnet, or protocol for Backup Exec agents not bound to the above network interface, subnet, or protocol Click this option to view the Media Access Control (MAC) address, adapter type, description, IP addresses, and subnet prefixes for the interface that you selected for the backup network. Interface Details Select this option to include user-defined shares in jobs. If you do not select this option, you cannot select user-defined shares when you create jobs. Enable selection of user shares Lets Backup Exec agents use a range of ports for communication. You enter the port range. If the first port that Backup Exec attempts to use is not available, Backup Exec attempts to use one of the other ports in the range. If none of the ports in the range is available, Backup Exec uses any available dynamic port. Default port ranges are 1025 to 65535. Symantec recommends using a range of 25 allocated ports for the remote system if you use Backup Exec with a firewall. See “Using Backup Exec with firewalls” on page 570. Enable TCP dynamic port range 569Configuration and settings Changing network and security options for Backup Exec
- 570. Lets you specify the port that Backup Exec uses for communication between the Backup Exec server and the remote computer for both DBA and Backup Exec server-initiated operations. By default, Backup Exec uses port 5633. If you change the port number on the remote Windows or Linux computer, you must also change it on the Backup Exec server. Then you must restart the Backup Exec Job Engine service on the Backup Exec server. See “About Oracle instance information changes” on page 1007. Use a custom port to receive operation requests from the Oracle server Lets you enable software encryption that complies with FIPS 140-2 standards. If you select this option, you must use a 256-bit AES encryption key. This option is available only for Windows computers. You must stop and restart the Backup Exec services for this change to take effect. Use FIPS 140-2 compliant software encryption Lets you create a new encryption key or manage existing encryption keys. Manage Keys 4 Click OK. See “Backup networks” on page 566. Using Backup Exec with firewalls In firewall environments, Backup Exec provides the following advantages: ■ The number of ports that are used for backup network connections is kept to a minimum. ■ Open ports on the Backup Exec server and remote systems are dynamic and offer high levels of flexibility during browsing, backup, and restore operations. ■ You can set specific firewall port ranges and specify backup and restore networks within these ranges. You can use specific ranges to isolate data traffic and provide high levels of reliability. Note: The Agent for Windows is required to perform remote backups and restores. 570Configuration and settings Using Backup Exec with firewalls
- 571. Firewalls affect system communication between a Backup Exec server and any remote systems that reside outside the firewall environment. You should consider special port requirements for your firewall when you configure Backup Exec. Symantec recommends that you open port 10000 and make sure that it is available on the Backup Exec server and any remote systems. In addition, you must open the dynamic port ranges that Backup Exec uses for communications between the Backup Exec server and Backup Exec agents. When a Backup Exec server connects to a remote system, it initially uses port 10000. The agent listens for connections on this predefined port. The Backup Exec server is bound to an available port, but additional connections to the agent are initiated on any available port. When you back up data, up to two ports may be required on the computer on which the agent is installed. To support simultaneous jobs, you must configure your firewall to allow a range of ports large enough to support the number of simultaneous operations desired. If there is a conflict, you can change the default port to an alternate port number by modifying the %systemroot%System32driversetcservices file. You can use a text editor such as Notepad to modify your NDMP entry or add an NDMP entry with a new port number. You should format the entry as follows: ndmp 9999/tcp #Network Data Management Protocol Note: If you change the default port, you must change it on the Backup Exec server and all remote systems that are backed up through the firewall. When you set up TCP dynamic port ranges, Symantec recommends that you use a range of 25 allocated ports for the remote computer. The number of ports that remote computers require depends on the number of devices you protect and the number of tape devices you use. You may need to increase these port ranges to maintain the highest level of performance. Unless you specify a range, Backup Exec uses the full range of dynamic ports available. When performing remote backups through a firewall, you should select a specific range on the Network and Security settings dialog box. To browse systems through a firewall 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings. 2 In the left pane, select Network and Security. 571Configuration and settings Using Backup Exec with firewalls
- 572. 3 Verify that a dynamic range of ports has been set for the Backup Exec server and the Backup Exec agent and that the firewall is configured to pass these port ranges and the 10000 port (which is used for the initial connection from the Backup Exec server to the Backup Exec agent). Port 6101 must be open to browse Windows systems in the backup selections tree. 4 Click OK. See “Backup Exec ports” on page 572. See “Backup Exec listening ports” on page 574. See “About enabling a SQL instance behind a firewall” on page 575. Backup Exec ports You may have special port requirements for Backup Exec if you use a firewall. Firewalls sometimes affect system communications between a Backup Exec server and remote systems that reside outside the firewall environment. See “Using Backup Exec with firewalls” on page 570. The following table provides more information about which ports Backup Exec and its agents and options use: Table 14-1 Backup Exec ports Port TypePortService or Process TCP6101Backup Exec Agent Browser (process=benetns.exe) TCP10000Backup Exec Agent for Windows (process=beremote.exe) TCP3527, 6106Backup Exec server (process=beserver.exe) 572Configuration and settings Using Backup Exec with firewalls
- 573. Table 14-1 Backup Exec ports (continued) Port TypePortService or Process TCP UDP A port number between 1024 and 5000 (Windows 2003) or between 49152 and 65535 (Windows 2008). See Microsoft's documentation for more information on assigning the TCP/IP port numbers that are required to communicate with SQL through a firewall. MSSQL$BKUPEXEC (process=sqlservr.exe) Random port unless configured otherwise Agent for Oracle on Windows or Linux Servers TCPDefault NDMP port, typically 10000 Agent for Linux TCP10082Backup Exec deduplication engine (process=spoold.exe) TCP10102Backup Exec deduplication manager (process=spad.exe) TCP50104, 50106Backup Exec Management Service (process= BackupExecManagementService.exe) UDP88Kerberos TCP, UDP135NETBIOS UDP137NETBIOS Name Service UDP138NETBIOS Datagram Service TCP139NETBIOS Session Service TCP445NETBIOS TCP3106DCOM/RPC TCP6103Agent for Windows 573Configuration and settings Using Backup Exec with firewalls
- 574. Table 14-1 Backup Exec ports (continued) Port TypePortService or Process TCP103xPush Install - Check for conflicts in message queue for CASO, which is part of beserver.exe TCP441Push Install TCP25 outbound from Backup Exec server SMTP email notification TCP162 outbound from Backup Exec server SNMP Backup Exec listening ports You may have special port requirements for Backup Exec if you use a firewall. Firewalls sometimes affect system communications between a Backup Exec server and remote systems that reside outside the firewall environment. See “Using Backup Exec with firewalls” on page 570. When Backup Exec is not running operations, it listens to ports for incoming communication from other services and agents. Backup Exec initially communicates with the agent using a static listening port to begin an operation. The agent and the Backup Exec server then use dynamic ports to pass data back and forth. Backup Exec uses the following listening ports: Table 14-2 Backup Exec listening ports Port TypePortService TCP6101Backup Exec Agent Browser (benetns.exe) TCP10000Backup Exec Agent for Windows (beremote.exe) TCP3527, 6106Backup Exec server (beserver.exe) TCP50104, 50106Backup Exec Management Service (process= BackupExecManagementService.exe) TCP UDP 1125 1434 MSSQL$BKUPEXEC (sqlsevr.exe) 574Configuration and settings Using Backup Exec with firewalls
- 575. Table 14-2 Backup Exec listening ports (continued) Port TypePortService TCP10000Agent for Linux (RALUS) TCP5633DBA-initiated backups for Oracle About enabling a SQL instance behind a firewall If you want to connect to a SQL instance behind a firewall, you must enable the SQL instance for communication. To enable the SQL instance for communication, you must make the SQL port static and configure the Windows Firewall. The Backup Exec SQL instance is configured to use a dynamic port by default. Each time SQL Server is started, the port number can change. You also must configure the Windows Firewall to allow connections to the SQL instance. There may be multiple ways to configure the Windows Firewall based on your system configuration. You can add sqlsvr.exe and sqlbrowser.exe to the Windows Firewall Exceptions list or you can open a port in the Windows Firewall for TCP access. Refer to the Microsoft Knowledge Base for more information or to determine which configuration is best for your network. See “Installing a managed Backup Exec server across a firewall ” on page 1119. See “Using Backup Exec with firewalls” on page 570. Using encryption with Backup Exec Backup Exec provides you with the ability to encrypt data. When you encrypt data, you protect it from unauthorized access. Anyone that tries to access the data has to have an encryption key that you create. Backup Exec provides software encryption, but it also supports some devices that provide hardware encryption with the T10 standard. Backup Exec configures encryption when you specify which storage devices that you want to use for a backup job. Backup Exec supports two security levels of encryption: 128-bit Advanced Encryption Standard (AES) and 256-bit AES. The 256-bit AES encryption provides a stronger level of security because the key is longer for 256-bit AES than for 128-bit AES. However, 128-bit AES encryption enables backup jobs to process more quickly. Hardware encryption using the T10 standard requires 256-bit AES. When you run a duplicate backup job, any backup sets that are already encrypted are not re-encrypted. However, you can encrypt any unencrypted backup sets. This topic includes the following information: 575Configuration and settings Using encryption with Backup Exec
- 576. Software encryption Hardware encryption Encryption keys Restricted keys and common keys Pass phrases Software encryption When you install Backup Exec, the installation program installs encryption software on the Backup Exec server and on any remote computers that use a Backup Exec agent. Backup Exec can encrypt data at a computer that uses a Backup Exec agent, and then transfer the encrypted data to the Backup Exec server. Backup Exec then writes the encrypted data on a set-by-set basis to tape or to disk storage. Backup Exec encrypts the following types of data: ■ User data, such as files and Microsoft Exchange databases. ■ Metadata, such as file names, attributes, and operating system information. ■ On-tape catalog file and directory information. Backup Exec does not encrypt Backup Exec metadata or on-disk catalog file and directory information. You can use software compression with encryption for a backup job. First Backup Exec compresses the files, and then encrypts them. However, backup jobs take longer to complete when you use both encryption compression and software compression. Symantec recommends that you avoid using hardware compression with software encryption. Hardware compression is performed after encryption. Data becomes randomized during the encryption process. Compression does not work effectively on data that is randomized. Hardware encryption Backup Exec supports hardware encryption for any storage devices that use the T10 encryption standard. When you use hardware encryption, the data is transmitted from the host computer to the storage device and then encrypted on the device. Backup Exec manages the encryption keys that are used to access the encrypted data. Backup Exec only supports approved devices for T10 encryption. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/v-269-2 576Configuration and settings Using encryption with Backup Exec
- 577. Note: Hardware encryption that uses the T10 standard requires 256-bit AES. Backup Exec does not let you enable hardware encryption for a job unless it uses at least a 16-character pass phrase. Encryption keys You must create encryption keys to use encryption in Backup Exec. When a user creates an encryption key, Backup Exec marks that key with an identifier based on the logged-on user’s security identifier. The person who creates the key becomes the owner of the key. If you use encryption for synthetic backups, all of the associated backups must use the same encryption key. Do not change the encryption key after the baseline is created. The encryption key that you select for the baseline backup is automatically applied to all associated backups. When you select encrypted data for restore, Backup Exec verifies that encryption keys for the data are available in the database. If any of the keys are not available, Backup Exec prompts you to recreate the missing keys. If you delete the key after you schedule the job to run, the job fails. If Backup Exec cannot locate an encryption key while a catalog job is running, Backup Exec sends an alert. You can then recreate the missing encryption key if you know the pass phrase. Simplified Disaster Recovery supports the recovery of computers with previously encrypted backup sets. If you have Simplified Disaster Recovery backups that are encrypted during backup, the Recover This Computer wizard prompts you for the pass phrase of each encrypted backup set that is required to complete the recovery. See “Encryption key management” on page 578. Restricted keys and common keys Backup Exec has the following types of encryption keys: Table 14-3 Types of encryption keys DescriptionKey type Anyone can use the key to encrypt data during a backup job and to restore encrypted data. Common 577Configuration and settings Using encryption with Backup Exec
- 578. Table 14-3 Types of encryption keys (continued) DescriptionKey type Anyone can use the key to encrypt data during a backup job, but users other than the key owner must know the pass phrase. If a user other than the key owner tries to restore the encrypted data, Backup Exec prompts the user for the pass phrase. If you cannot supply the correct pass phrase for the key, you cannot restore the data. Restricted Pass phrases Encryption keys require a pass phrase, which is similar to a password. Pass phrases are usually longer than passwords and are comprised of several words or groups of text. A good pass phrase is between 8 and 128 characters. The minimum number of characters for 128-bit AES encryption is eight. The minimum number of characters for 256-bit AES encryption is 16. Symantec recommends that you use more than the minimum number of characters. Note: Hardware encryption that uses the T10 standard requires 256-bit AES. Backup Exec does not let you enable hardware encryption for a job unless it uses at least a 16-character pass phrase. Also, a good pass phrase contains a combination of upper and lower case letters, numbers, and special characters. You should avoid using literary quotations in pass phrases. A pass phrase can include only printable ASCII characters, which are characters 32 through 126. ASCII character 32 is the space character, which is entered using the space bar on the keyboard. ASCII characters 33 through 126 include the following: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ []^_‘abcdefghijklmnopqrstuvwxyz{|}~ See “Encryption key management” on page 578. Encryption key management When a user creates an encryption key, Backup Exec marks that key with an identifier based on the logged-on user’s security identifier. The person who creates the key becomes the owner of the key. See “Using encryption with Backup Exec” on page 575. 578Configuration and settings Encryption key management
- 579. Backup Exec stores the keys in the Backup Exec database. However, Backup Exec does not store the pass phrases for the keys. The owner of each key is responsible for remembering the pass phrase for the key. To protect your keys, Symantec recommends the following: ■ Maintain a written log of the pass phrases. Keep the log in a safe place in a separate physical location from the encrypted backup sets. ■ Back up the Backup Exec database. The database keeps a record of the keys. Caution: If you do not have a backup of the Backup Exec database and do not remember your pass phrases, you cannot restore data from the encrypted media. In addition, Symantec cannot restore encrypted data in this situation. A key that is created on a Backup Exec server is specific to that Backup Exec server. You cannot move keys between Backup Exec servers. However, you can create new keys on a different Backup Exec server by using existing pass phrases. A pass phrase always generates the same key. In addition, if you delete a key accidentally, you can recreate it by using the pass phrase. If a Backup Exec database becomes corrupted on a Backup Exec server and is replaced by a new database, you must manually recreate all of the encryption keys that were stored on the original database. If you move a database from one Backup Exec server to another Backup Exec server, the encryption keys remain intact as long as the new Backup Exec server meets the following criteria: ■ Has the same user accounts as the original Backup Exec server. ■ Is in the same domain as the original Backup Exec server. See “Creating encryption keys” on page 579. See “Replacing an encryption key” on page 581. See “Deleting encryption keys” on page 582. Creating encryption keys When you create an encryption key, you select the type of encryption to use. To create an encryption key 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Network and Security. 579Configuration and settings Creating encryption keys
- 580. 3 Click Manage Keys. 4 Click New. 5 In the Key name field, type a unique name for this key. The name can include up to 256 characters. 6 In the Encryption type field, select the encryption type to use for this key. Your choices are 128-bit AES or 256-bit AES. The default type is 256-bit AES. The 256-bit AES encryption provides a stronger level of security than 128-bit AES encryption. However, backup jobs may process more slowly with 256-bit AES encryption than with 128-bit AES encryption. Hardware encryption that uses the T10 standard requires 256-bit AES. 7 In the Pass phrase field, type a pass phrase for this key. You can use only printable ASCII characters. For 128-bit AES encryption, the pass phrase must be at least eight characters. For 256-bit AES encryption, the pass phrase must be at least 16 characters. Symantec recommends that you use more than the minimum number of characters. Warning: If an encryption key that is used in a backup is no longer available, you must provide the pass phrase during restore. Without the pass phrase, the data cannot be accessed. 8 In the Confirm pass phrase field, type the pass phrase again to confirm it. 9 In the Encryption key type group box, select whether you want to create a common or restricted encryption key. If a key is common, any user of this installation of Backup Exec can use the key to back up and restore data. If a key is restricted, anyone can use the key to back up data. But only the key owner or a user who knows the pass phrase can use the restricted key to restore the encrypted data. 10 Click OK. See “Encryption key management” on page 578. See “Using encryption with Backup Exec” on page 575. 580Configuration and settings Creating encryption keys
- 581. Replacing an encryption key You can replace one encryption key with another for all backup jobs and duplicate backup set jobs. Note: You cannot replace an encryption key if it is used in a restore job. To replace an encryption key 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Network and Security. 3 Click Manage Keys. 4 Select the key that you want to replace. 5 Click Replace. 6 In the Select an encryption key to replace <key name> field, do one of the following: Select the key from the list.To use an existing key 581Configuration and settings Replacing an encryption key
- 582. Complete the following steps: ■ Click New. ■ In the Key name field, type a unique name for the key. The name can include up to 256 characters. ■ In the Encryption type field, select the type of encryption to use for this key. You can select 128-bit AES or 256-bit AES. The default type is 256-bit AES. The 256-bit AES encryption provides a stronger level of security than 128-bit AES encryption. However, backup jobs may process more slowly with 256-bit AES encryption than with 128-bit AES encryption. Hardware encryption that uses the T10 standard requires 256-bit AES. ■ In the Pass phrase field, type a pass phrase for this key. For 128-bit AES encryption, the pass phrase must be at least eight characters. For 256-bit AES encryption, the pass phrase must be at least 16 characters. Symantec recommends that you use more than the minimum number of characters. You can use only printable ASCII characters. Warning: If an encryption key that is used in a backup is no longer available, you must provide the pass phrase during restore. Without the pass phrase, the data cannot be accessed. ■ In the Confirm pass phrase field, type the pass phrase again to confirm it. ■ In the Encryption key type group box, select whether you want to create a common or restricted encryption key. ■ Click OK. To create a new key 7 Click OK. See “Encryption key management” on page 578. See “Using encryption with Backup Exec” on page 575. Deleting encryption keys You should be cautious when you delete encryption keys. When you delete an encryption key, you cannot restore the backup sets that you encrypted with that key unless you create a new key that uses the same encryption key and pass phrase as the original key. You can delete encryption keys in the following situations: 582Configuration and settings Deleting encryption keys
- 583. ■ The encrypted data on the tape has expired or the tape is retired. ■ The encryption key is not the default key. ■ The encryption key is not being used in a job. If the key is being used, you must select a new key for the job. If you delete an encryption key that is being used in a scheduled restore job, you cannot replace the key. Therefore, any scheduled restore job in which you delete an encryption key fails. To delete an encryption key 1 Click the Backup Exec button, select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Network and Security. 3 Click Manage Keys. 4 Select the key that you want to delete. 5 Click Delete. 6 Click Yes. 7 If the key is used in a job, do the following: ■ In the Select an encryption key to replace "key name" box, select the new key for the job or click New to create a new key. ■ Click OK. See “Encryption key management” on page 578. See “Using encryption with Backup Exec” on page 575. Granular Recovery Technology You can use Granular Recovery Technology (GRT) to restore certain individual items from backup sets. For example, you can use the Agent for Microsoft Exchange Server to restore an email from a backup without having to restore the entire mailbox. Or, you can use the Agent for Microsoft SharePoint to restore a list without restoring the entire site. To restore individual items, the Granular Recovery Technology feature must be enabled when you create a backup job. GRT is enabled by default for backups for the following agents: ■ Agent for Microsoft Active Directory ■ Agent for Microsoft Exchange Server 583Configuration and settings Granular Recovery Technology
- 584. ■ Agent for Microsoft SharePoint ■ Agent for VMware and Hyper-V You can restore either full backup sets or individual items from GRT-enabled backups. By default, the Agent for VMware and Hyper-V uses Granular Recovery Technology to protect files and folders at a granular level. You can also enable the granular recovery of Microsoft Exchange, SQL, SharePoint, and Active Directory application data that resides on virtual machines. When you back up data, Backup Exec creates a catalog that contains information about the backup sets and about the storage device on which the backup sets are stored. GRT-enabled backup jobs require more time to catalog because of the amount of granular information that they contain. For GRT-enabled backup jobs, the catalog operation is delayed and run as a separate operation to have less of an effect on your backup window. Because the catalog operation runs separately from the backup job, it does not prevent another scheduled backup job from starting on time. When you enable GRT for Microsoft Exchange, Microsoft SharePoint, Microsoft Hyper-V, or VMware backups, the delayed catalog operation runs after the backup job by default. For Exchange and SharePoint backups, the delayed catalog operation runs immediately after all full backups. It runs once every 24-hours for all incremental backups and differential backups, even if you schedule more than one GRT-enabled job to run in the 24 hour period. For Hyper-V and VMware backups, the delayed catalog operation runs immediately after all full, incremental, and differential backups by default. You can configure the delayed catalog operation to run on a schedule if you do not want it to run immediately after the backup job. You can also choose to not run a delayed catalog operation. See “Configuring delayed catalog operations to improve backup performance” on page 521. The following table lists the individual items you can restore for each agent. Table 14-4 Individual items that can be recovered for each agent Individual itemsAgent You can restore the following individual items: ■ Active Directory objects and attributes ■ Active Directory Application Mode (ADAM) and Active Directory Lightweight Directory Services (AD LDS) objects and attributes Agent for Microsoft Active Directory 584Configuration and settings Granular Recovery Technology
- 585. Table 14-4 Individual items that can be recovered for each agent (continued) Individual itemsAgent You can restore the following individual items: ■ Mailboxes ■ Mail messages and their attachments ■ Public folders ■ Calendar items ■ Contacts ■ Notes ■ Tasks Agent for Microsoft Exchange Server The following are examples of the individual items that can be restored: ■ Site collections ■ Sites or subsites ■ Document or picture libraries ■ Lists ■ Individual list items ■ Documents, pictures, or other files that are stored in libraries Agent for Microsoft SharePoint You can restore drives, folders, and files from virtual machines that run a Windows operating system. You can also enable the granular recovery of Microsoft Exchange, SQL, SharePoint, and Active Directory application data that resides on virtual machines. See “Using Granular Recovery Technology (GRT) with the Agent for VMware” on page 843. Agent for VMware and Hyper-V When you run a GRT-enabled backup job, Backup Exec creates media with an IMG prefix (for example, IMG00001). IMG media is a specific media type that Backup Exec creates only for GRT-enabled backup operations. When you run a GRT-enabled backup job, the IMG media stores the backup data. Note: Symantec recommends that you do not use software compression or encryption for GRT-enabled backup jobs. The compression and encryption processes are resource-intensive. Enabling either software compression or encryption can result in degraded performance for GRT-enabled backup jobs. 585Configuration and settings Granular Recovery Technology
- 586. You should consider which device you use for GRT-enabled backups before you begin. You should also consider any special requirements for the type of data you back up. Recommended devices for backups that use Granular Recovery Technology Symantec recommends that you select a disk storage device for any backups that are enabled for Granular Recovery Technology (GRT). The disk storage device should be on a volume that does not have file size limitations. An NTFS drive is an example of a volume without file size limitations. Some examples of volumes that have file size limitations include FAT and FAT32 volumes. If you must use a disk storage device on a volume with file size limitations, Backup Exec requires a staging location. Backup Exec temporarily stores a small amount of metadata in the staging location during the backup job. It deletes the data from the staging location when the backup is finished. The staging location is not necessary, however, if you use a disk storage device on a volume without file size limitations as the destination. The staging location's default path is C:temp. The volume that is used for a staging location for backup jobs should meet the following requirements: ■ It is local to the Backup Exec server ■ It does not have any file size limitations Additionally, Symantec recommends the following to avoid disk space problems: ■ It should not be a system volume ■ It should have at least 1 GB of available space Backup Exec also uses a staging location to restore GRT-enabled data from a tape or from a disk storage device on volumes with file size limitations. The staging location must be on a volume that does not have file size limitations and is local to the Backup Exec server. The staging location is not necessary if you restore GRT-enabled data from disk storage on a volume without file size limitations, such as NTFS. Backup Exec uses the staging area differently for the following types of restores: 586Configuration and settings Granular Recovery Technology
- 587. Table 14-5 Staging processes Staging processLocation of data to be restored Backup Exec copies the entire backup set or sets to the staging area. The staging area must have enough disk space for the entire backup set or sets from which you want to restore an individual item. Before you use a tape device for a GRT-enabled backup, ensure that sufficient disk space is available to perform a restore. Backup Exec deletes the data from the staging area when the restore job is complete. Tape Backup Exec must copy a small amount of metadata that is associated with the backup set to the staging area to complete the restore. Backup Exec deletes the data from the staging area when the restore job is complete. Disk storage device that is on a volume with file size limitations (such as FAT or FAT32) The staging location's default path is C:temp. You can change the default backup and restore staging locations in the Backup Exec settings. Requirements for jobs that use Granular Recovery Technology Keep in mind the following requirements when you use Granular Recovery Technology (GRT) with the agents listed: Table 14-6 Granular Recovery Technology requirements RestrictionsAgent GRT is not supported when using a Windows Server 2003 Backup Exec server to back up System State on a Windows Server 2012 or 2012 R2 computer. In this scenario the backup completes successfully, but it is not GRT-enabled. Files and Folders 587Configuration and settings Granular Recovery Technology
- 588. Table 14-6 Granular Recovery Technology requirements (continued) RestrictionsAgent You must use a Backup Exec server that is running Windows Server 2012 R2 to back up an Active Directory server that is running Windows Server 2012 R2. In a CASO environment, Backup Exec runs the backup job on the central administration server if it is running Windows Server 2012 R2 and the storage is configured locally. Otherwise, Backup Exec attempts to find a managed Backup Exec server that is running Windows Server 2012 R2 to run the job. If it cannot find one, the job completes with a status of success with exceptions and the backup sets are not GRT-enabled. If the Active Directory server is a virtual machine, Backup Exec may not be able to detect that the server is running Windows Server 2012 R2. The resulting backup may not be GRT-enabled. Agent for Microsoft Active Directory Backup Exec must have access to a uniquely named mailbox within the Exchange organization for backup and restore of the Information Store. See “Requirements for accessing Exchange mailboxes ” on page 939. Backup Exec uses a disk storage device that does not have file size limitations and is local to the Backup Exec server as the default staging location for GRT-enabled backups of Exchange. Backup Exec may use a staging location other than the one that is configured in default backup options because a disk that uses the same disk geometry as the database logs is required to perform GRT operations. However, the location does not affect the performance or the amount of disk space that is required for the operations. You can create a vhd file or vhdx file to use as the staging area instead of a physical volume, if you want to minimize the effect on your resources. Configure the vhd or the vhdx file as a large-sector volume and make sure that it is at least 1GB in size. Then mount the vhd file or vhdx file to a directory. Backup Exec automatically finds the virtual volume when it needs a staging area to back up any data that resides on a large-sector drive. Recommended devices for backups that use Granular Recovery Technology Agent for Microsoft Exchange Server 588Configuration and settings Granular Recovery Technology
- 589. Table 14-6 Granular Recovery Technology requirements (continued) RestrictionsAgent You must have a current version of the Agent for Windows installed on all of the servers that participate in the SharePoint farm. Agent for Microsoft SharePoint You can recover only individual items to virtual machines that run a Windows operating system. By default, the Agent for VMware and Hyper-V uses Granular Recovery Technology to protect files and folders at a granular level. You can also enable the granular recovery of Microsoft Exchange, SQL, SharePoint, and Active Directory application data that resides on virtual machines. If you back up a virtual machine to tape, the Use storage-based catalogs option must be enabled in the Catalog settings to ensure that you can recover individual items from the backup sets. See “Configuring default options for catalogs” on page 236. Agent for VMware and Hyper-V See “Setting default Granular Recovery Technology (GRT) options” on page 589. Setting default Granular Recovery Technology (GRT) options Backup Exec's Granular Recovery Technology (GRT) feature lets you restore certain individual items from backup sets. For example, you can use the Agent for Microsoft Exchange Server to restore an email from a backup without having to restore the entire mailbox. Or, you can use the Agent for Microsoft SharePoint to restore a list without restoring the entire site. See “Granular Recovery Technology” on page 583. You can configure default settings for Granular Recovery Technology. Backup Exec applies the default settings to any backup jobs that you configure to use GRT. To set default Granular Recovery Technology options 1 Click the Backup Exec button, and then select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select Granular Recovery Technology. 3 Configure any of the following options: 589Configuration and settings Setting default Granular Recovery Technology (GRT) options
- 590. Lets you designate a location where Backup Exec can stage temporary data during GRT-enabled backup jobs. Ensure that the location is an NTFS volume and that it is not a system volume. If the default path of C:TEMP does not meet these requirements, type a different path on the Backup Exec server where Backup Exec can stage temporary data. Backup Exec deletes the data when the backup job is completed. At least 1 GB of disk space is required. If Granular Recovery Technology (GRT) is enabled for backups, enter the path to an NTFS volume of the local Backup Exec server where Backup Exec can stage temporary data Lets you designate a location where Backup Exec can stage temporary data during GRT restore jobs. This option is applicable only when you restore individual items under the following conditions: ■ The backup of Microsoft Hyper-V, Microsoft Exchange, Microsoft SharePoint, Microsoft Active Directory, or VMware Virtual Infrastructure was enabled for Backup Exec GRT. ■ The backup is on a tape. ■ The backup is on disk storage on a volume that has size limitations. FAT and FAT32 are examples of types of volumes that have file size limitations. Type the path to a folder on an NTFS volume on this Backup Exec server. Restore data and metadata for this job are stored here temporarily before the individual items are restored. The staged data is automatically deleted when the restore job is completed. Symantec recommends that you avoid using system volumes for temporary staging locations. Enter the path to an NTFS volume of the local Backup Exec server where Backup Exec can store temporary data (Microsoft Hyper-V, Microsoft Exchange, Microsoft SharePoint, Microsoft Active Directory, and VMware) 4 Click OK. DBA-initiated job templates When you create a DBA-initiated backup operation, you can specify the default job template in Backup Exec. You can also specify a new job template that you create in Backup Exec. The job template contains the settings that Backup Exec applies to DBA-initiated jobs. Make sure that the name of the job template that you want to use is also configured in the instance information on the Windows computer. 590Configuration and settings DBA-initiated job templates
- 591. See “Configuring the Oracle Agent on Windows computers and Linux servers” on page 989. See “About performing a DBA-initiated backup job for Oracle” on page 1010. Note the following about DBA-initiated jobs: ■ DBA-initiated jobs fail when the related job template is deleted. To stop DBA-initiated jobs from running, delete the related DBA-initiated job template. ■ All DBA-initiated backup and restore jobs are deleted after the jobs have completed. ■ You cannot set minimum device requirements for DBA-initiated jobs. See “Creating DBA-initiated job templates” on page 591. See “Editing DBA-inititated job templates” on page 592. See “Deleting DBA-initiated job templates” on page 592. Creating DBA-initiated job templates You can create a new job template that Backup Exec applies to DBA-initiated jobs. To create DBA-initiated job templates 1 Click the Backup Exec button, and then select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select DBA-initiated Job Settings. 3 Click New. 4 In the left pane, select the type of options that you want to set. You determine the options that need to be set based on the needs of your environment. 5 Click OK. See “DBA-initiated job templates” on page 590. See “Storage options for DBA-initiated jobs” on page 593. See “General options for DBA-initiated jobs” on page 598. See “Network options for DBA-initiated jobs” on page 598. See “Migrator for Enterprise Vault options” on page 1062. See “Notification options for jobs” on page 292. See “Duplicate job settings for DBA-initiated jobs” on page 599. 591Configuration and settings Creating DBA-initiated job templates
- 592. Editing DBA-inititated job templates You can edit the job template settings that Backup Exec applies to DBA-initiated jobs. To edit DBA-initiated job templates 1 Click the Backup Exec button, and then select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select DBA-initiated Job Settings. 3 Select the job template that you want to edit. 4 Click Edit. 5 In the left pane, select the type of options that you want to edit. You determine the options that need to be set based on the needs of your environment. 6 Click OK. See “DBA-initiated job templates” on page 590. See “Storage options for DBA-initiated jobs” on page 593. See “General options for DBA-initiated jobs” on page 598. See “Network options for DBA-initiated jobs” on page 598. See “Migrator for Enterprise Vault options” on page 1062. See “Notification options for jobs” on page 292. See “Duplicate job settings for DBA-initiated jobs” on page 599. Deleting DBA-initiated job templates You can delete the templates that Backup Exec applies to DBA-initiated jobs if you no longer use them. To delete a job template for DBA-initiated jobs 1 Click the Backup Exec button, and then select Configuration and Settings, and then click Backup Exec Settings. 2 In the left pane, select DBA-initiated Job Settings. 3 Select the job template that you want to delete. 4 Click Delete. 5 Click Yes. See “DBA-initiated job templates” on page 590. 592Configuration and settings Editing DBA-inititated job templates
- 593. Storage options for DBA-initiated jobs You can configure storage settings for DBA-initiated jobs. See “DBA-initiated job templates” on page 590. Table 14-7 Storage options for DBA-initiated jobs DescriptionItem Specifies if you want a job to run on devices on a specific managed Backup Exec server or on devices that are on a group of managed Backup Exec servers. This option displays only if you have the Central Admin Server Option installed. This option is an additional filter that lets you control where certain jobs are delegated. For example, to always run backups of Exchange databases only on the devices that are attached to managed Backup Exec servers in a pool named Exchange Backups, select this option. Then select the Exchange Backups Backup Exec server pool. Backup Exec server or Backup Exec server pool Specifies the storage device to which you want to send backup data for the DBA-initiated jobs. See “Creating storage device pools” on page 402. See “About the Any Virtual Disk Storage device pool in the Storage Provisioning Option” on page 1291. See “About the Remote Media Agent for Linux ” on page 1258. See “Features and types of disk-based storage and network-based storage” on page 300. Storage Enables a remote computer to send data directly to an OpenStorage device or a deduplication disk storage device, and to perform client-side deduplication if the device supports it. The Backup Exec server is bypassed, which leaves the Backup Exec server free to perform other operations. If client-side deduplication cannot be performed, then either Backup Exec server deduplication or Appliance deduplication is performed. This option appears if the Deduplication Option is installed and an OpenStorae device or a deduplication disk storage device is selected in the Storage field. See “How to use client-side deduplication” on page 818. Enable the remote computer to directly access the storage device and to perform client-side deduplication, if it is supported 593Configuration and settings Deleting DBA-initiated job templates
- 594. Table 14-7 Storage options for DBA-initiated jobs (continued) DescriptionItem Enables a remote computer to send data through the Backup Exec server to an OpenStorage device or a deduplication disk storage device, and to perform Backup Exec server-side deduplication if it it supported. If the Backup Exec server does not support deduplication, the data is deduplicated on an intelligent disk device, such as Symantec PureDisk or a device from a third-party vendor. This option appears if the Deduplication Option is installed and an OpenStorage device or a deduplication disk storage device is selected in the Storage field. See “About the Deduplication Option” on page 792. Enable the remote computer to access the storage device through the Backup Exec server and to perform Backup Exec server-side deduplication, if it is supported Designates the amount of time for which you want to keep the backup sets or job history from the DBA-initiated jobs. Keep for Indicates the media set to use for the DBA-initiated jobs. The media set specifies the overwrite protection period and the append period for the backup data on the media. If you want to create a new media set for this backup job, click the icon to the right of the media set drop-down menu. This option is available only if you selected a tape device in the Storage field. See “Default media sets” on page 367. Media set 594Configuration and settings Deleting DBA-initiated job templates
- 595. Table 14-7 Storage options for DBA-initiated jobs (continued) DescriptionItem Indicates that the backup job is placed on an overwritable media. Ensure that appropriate media is in the storage device that you select. Appropriate media for an overwrite job includes the following: ■ Scratch media ■ Media for which the overwrite protection period has expired Allocated or imported media may also be overwritten depending on the media overwrite protection level that is set. Depending on your configuration, overwritable media is selected from scratch media or recyclable media. If the media in the storage device is not overwritable, an alert appears to prompt you to insert overwritable media. This option is available only if you selected a tape device in the Storage field. See “Managing tapes” on page 366. See “Media overwrite protection levels for tape media” on page 380. See “How Backup Exec searches for overwritable media in tape drives ” on page 381. Overwrite media Appends this backup job to the specified media set if an appendable media is available. Otherwise, Backup Exec searches for an overwritable media and adds it to the media set. If an append job fills a media, the backup job continues on an overwritable media. If the media in the storage device is not overwritable, an alert appears to prompt you to insert overwritable media. This option is available only if you selected a tape device in the Storage field. Append to media, overwrite if no appendable media is available Appends this backup job to the specified media set if an appendable media is available. Otherwise, Backup Exec terminates the job. This option is available only if you selected a tape device in the Storage field. Append to media, terminate job if no appendable media is available 595Configuration and settings Deleting DBA-initiated job templates
- 596. Table 14-7 Storage options for DBA-initiated jobs (continued) DescriptionItem Ejects the media from the drive or slot when the operation completes. You can also schedule a job to eject media. This option is available only if you selected a tape device in the Storage field. See “Ejecting media from a disk cartridge or tape drive” on page 441. Eject media after job completes Runs the tape in the drive from beginning to end at a fast speed. Retensioning helps the tape wind evenly and run more smoothly past the tape drive heads. This option is available only if you select a tape drive that supports retensioning. Retension media before backup Specifies the use of WORM (write once, read many) media as the default for DBA-initiated jobs. Backup Exec confirms that the destination device is or contains a WORM-compatible drive, and that the WORM media is available in the drive. If WORM media or a WORM-compatible drive is not found, an alert is sent. See “How WORM media is used in Backup Exec” on page 387. Use Write once, read many (WORM) media 596Configuration and settings Deleting DBA-initiated job templates
- 597. Table 14-7 Storage options for DBA-initiated jobs (continued) DescriptionItem Provides the following compression options: ■ None Copies the data to the media in its original form (uncompressed). Using some form of data compression can help expedite backups and preserve storage space. Hardware data compression should not be used in environments where storage devices that support hardware compression are used interchangeably with devices that do not have that functionality. In this situation, hardware compression is automatically disabled. You can manually turn on hardware compression on the drives that support it, but this results in media inconsistency. If the drive that supports hardware compression fails, the compressed media cannot be restored with the non-compression drive. ■ Software Uses STAC software data compression, which compresses the data before it is sent to the storage device. ■ Hardware (if available, otherwise none) Uses hardware data compression if the storage device supports it. If the drive does not feature data compression, the data is backed up uncompressed. ■ Hardware (if available, otherwise software) Uses hardware data compression if the storage device supports it. If the drive does not feature hardware data compression, STAC software compression is used. Compression Specifies the type of encryption that you want to use, if any. See “Using encryption with Backup Exec” on page 575. Encryption type Specifies the encryption key that you want to use, if you selected to use encryption. See “Using encryption with Backup Exec” on page 575. Encryption key Lets you manage your encryption keys. You can delete or replace existing encryption keys. You can also create a new encryption key. This option is available only if you select an encryption type. See “Encryption key management” on page 578. Manage Keys 597Configuration and settings Deleting DBA-initiated job templates
- 598. General options for DBA-initiated jobs You can configure general options for DBA-initiated jobs. See “DBA-initiated job templates” on page 590. Table 14-8 General options for DBA-initiated jobs DescriptionItem Specifies the name for this backup template. You can accept the default name that appears or enter a name. The name must be unique. Job name Describes the information in the backup set for future reference. Backup set description Performs a verify operation automatically to make sure that the media can be read after the backup has been completed. Verifying all backups is recommended. Verify after backup completes Network options for DBA-initiated jobs You can configure network options for DBA-initiated jobs. See “DBA-initiated job templates” on page 590. Note: Some of these options may not display in a CASO environment. Table 14-9 Network options for DBA-initiated jobs DescriptionItem Specifies the name of the network interface card that connects the Backup Exec server to the network that you want to use for this backup job. The list includes all available network interfaces on the Backup Exec server. Network interface Specifies the protocol you want to use for this backup job. The options are as follows: ■ Use any available protocol ■ Use IPv4 ■ Use IPv6 Protocol Displays the 32-bit number that determines the subnet to which the network interface card belongs. Subnet 598Configuration and settings Deleting DBA-initiated job templates
- 599. Table 14-9 Network options for DBA-initiated jobs (continued) DescriptionItem Lets Backup Exec use any available network if the remote system that you selected for backup or restore is not part of the specified backup network. If you do not select this option and the remote system is not part of the specified backup network, the job fails. Backup Exec cannot access the data from the remote system. Allow use of any available network interface, subnet, or protocol for Backup Exec agents not bound to the above network interface, subnet, or protocol Displays the Media Access Control (MAC) address, adapter type, description, IP addresses, and subnet prefixes for the interface that you selected for the backup network. Interface Details Lets a job use any network interface to access Backup Exec agents if the selected network interface is unavailable. Enabling this option lets the managed Backup Exec server use an alernate network interface to run any important backup jobs that would otherwise fail. This option is available only if the Central Admin Server Option (CASO) is installed. See “About the Central Admin Server Option” on page 1106. Allow managed Backup Exec server to use any network interface to access Backup Exec agents Duplicate job settings for DBA-initiated jobs You can configure duplicate job template settings for DBA-initiated jobs. See “DBA-initiated job templates” on page 590. Table 14-10 Duplicate job settings for DBA-initiated jobs DescriptionItem Enables the settings for a duplicate backup set template.Enable settings to duplicate backup sets for this job Specifies the storage device to which you want to send backup data for the duplicate DBA-initiated job. Storage Designates the amount of time for which you want to keep the backup sets or job history from the duplicate DBA-initiated job. Keep for 599Configuration and settings Deleting DBA-initiated job templates
- 600. Table 14-10 Duplicate job settings for DBA-initiated jobs (continued) DescriptionItem Indicates the media set to use for the duplicate DBA-initiated job. The media set specifies the overwrite protection period and the append period for the backup data on the media. If you want to create a new media set for this backup job, click the icon to the right of the media set drop-down menu. See “Default media sets” on page 367. Media set Indicates that the backup job is placed on an overwritable media. Ensure that appropriate media is in the storage device that you select. Appropriate media for an overwrite job include the following: ■ Scratch media ■ Media for which the overwrite protection period has expired Depending on your configuration, overwritable media is selected from scratch media or recyclable media. If the media in the storage device is not overwritable, an alert prompts you to insert overwritable media. See “Managing tapes” on page 366. See “Media overwrite protection levels for tape media” on page 380. See “How Backup Exec searches for overwritable media in tape drives ” on page 381. Overwrite media Appends this backup job to the specified media set if an appendable media is available. Otherwise, Backup Exec searches for an overwritable media and adds it to the media set. If an append job fills a media, the backup job continues on an overwritable media. If the media in the storage device is not overwritable, an alert appears to prompt you to insert overwritable media. Append to media, overwrite if no appendable media is available Appends this backup job to the specified media set if an appendable media is available. Otherwise, Backup Exec terminates the job. Append to media, terminate job if no appendable media is available 600Configuration and settings Deleting DBA-initiated job templates
- 601. Table 14-10 Duplicate job settings for DBA-initiated jobs (continued) DescriptionItem Ejects the media from the drive or slot when the operation completes. You can also schedule a job to eject media. See “Ejecting media from a disk cartridge or tape drive” on page 441. Eject media after job completes Runs the tape in the drive from beginning to end at a fast speed. Retensioning helps the tape wind evenly and run more smoothly past the tape drive heads. This option is available only if you select a tape drive that supports retensioning. Retension media before backup Specifies the use of WORM (write once, read many) media as the default for DBA-initiated jobs. Backup Exec confirms that the destination device is or contains a WORM-compatible drive, and that the WORM media is available in the drive. If WORM media or a WORM-compatible drive is not found, an alert is sent. See “How WORM media is used in Backup Exec” on page 387. Use Write once, read many (WORM) media Enables Backup Exec to coordinate the movement of data from virtual storage directly to a physical storage device. The Backup Exec server records information about the data in the catalog. Therefore, you can restore data from either the virtual storage or the physical storage. See “Copying data from a virtual tape library to a physical tape device using DirectCopy to tape” on page 217. Enable DirectCopy to tape 601Configuration and settings Deleting DBA-initiated job templates
- 602. Table 14-10 Duplicate job settings for DBA-initiated jobs (continued) DescriptionItem Provides the following compression options: ■ None Copies the data to the media in its original form (uncompressed). Using some form of data compression can help expedite backups and preserve storage space. Hardware data compression should not be used in environments where storage devices that support hardware compression are used interchangeably with devices that do not have that functionality. In this situation, hardware compression is automatically disabled. You can manually turn on hardware compression on the drives that support it, but this results in media inconsistency. If the drive that supports hardware compression fails, the compressed media cannot be restored with the non-compression drive. ■ Software Uses STAC software data compression, which compresses the data before it is sent to the storage device. ■ Hardware (if available, otherwise none) Uses hardware data compression if the storage device supports it. If the drive does not feature data compression, the data is backed up uncompressed. ■ Hardware (if available, otherwise software) Uses hardware data compression if the storage device supports it. If the drive does not feature hardware data compression, STAC software compression is used. Compression Specifies the encryption key that you want to use, if any. See “Using encryption with Backup Exec” on page 575. Encryption type Specifies the encryption key that you want to use, if you selected to use encryption. See “Using encryption with Backup Exec” on page 575. Encryption key Lets you manage your encryption keys. You can delete or replace existing encryption keys. You can also create a new encryption key. This option is available only if you select an encryption type. See “Encryption key management” on page 578. Manage Keys 602Configuration and settings Deleting DBA-initiated job templates
- 603. Table 14-10 Duplicate job settings for DBA-initiated jobs (continued) DescriptionItem Specifies the preferred source device that you want to use as the storage for the duplicate job. Preferred source device Performs a verify operation automatically to make sure that the data can be read after the backup has been completed. Verifying all backups is recommended. Verify after backup completes Backup Exec logon accounts A Backup Exec logon account stores the credentials of a user account that you use to access a computer. Backup Exec logon accounts enable Backup Exec to manage user names and passwords and can be used to browse computers or process jobs. Using Backup Exec logon accounts enables you to apply credential changes to the jobs that use them. Backup Exec logon accounts are used to browse local and remote computers. Whenever the Backup Exec logon credentials are passed between the Backup Exec server and the remote computer, the credentials are encrypted. Backup Exec logon accounts can also be associated with backup data at the device level such as shares, databases, etc. If you need to edit the credentials, you can edit the Backup Exec logon account. Any changes are applied to the selected computers that use the Backup Exec logon account. Backup Exec logon accounts are not user accounts. When you create a Backup Exec logon account, an entry for the account is entered into the Backup Exec database; no operating system accounts are created. If your user account credentials change, you must update the Backup Exec logon account with the new information. Backup Exec does not maintain a connection with the user account. You can view, create, edit, replace, and delete Backup Exec logon accounts. The following types of logon accounts are included in Backup Exec: Default Backup Exec logon account Backup Exec System Logon Account Restricted logon accounts Default Backup Exec logon account The default Backup Exec logon account enables you to browse, make selections, or restore data. The first time you start Backup Exec, you must specify a default 603Configuration and settings Backup Exec logon accounts
- 604. Backup Exec logon account using the Logon Account Wizard. You can select an existing Backup Exec logon account or create a new one. You can create multiple Backup Exec logon accounts; however, each Backup Exec user can have only one default Backup Exec logon account. Your default Backup Exec logon account enables you to perform the following: ■ Browse data. Your default Backup Exec logon account enables you to browse local and remote computers when you create backup jobs. To browse computers, each user must have a default Backup Exec logon account that is associated with their user account. The Backup Exec logon account does not have to be the same user name as the user that is used to log on to Backup Exec. For example, you are logged on to a Backup Exec server named BACKUPSERVER as the local Windows administrator. When you start Backup Exec, you are prompted to create a default Backup Exec logon account for the local administrator because one does not exist. You can create a Backup Exec logon account for the local administrator that has the credentials for a domain administrator. The Backup Exec logon account has the following properties: User name: DOMAINAdministrator Description: BACKUPSERVERAdministrator Default Account Owner: BACKUPSERVERAdministrator When you change your default Backup Exec logon account, you can use your new default Backup Exec logon account to browse computers immediately. You do not have to restart your system in order for the changes take effect. See “Changing your default Backup Exec logon account” on page 611. ■ Make backup selections. You can select a different Backup Exec logon account when you make selections for backup. If your default logon account does not have rights, the Logon Account Selection dialog box appears and lets you create or select a different Backup Exec logon account. See “Requirements for using the SQL Agent” on page 887. See “Requirements for accessing Exchange mailboxes ” on page 939. ■ Restore. You can assign Backup Exec logon accounts to computers when you create restore jobs. The default Backup Exec logon account is used unless you choose a different Backup Exec logon account when you create the restore job. Backup Exec System Logon Account The Backup Exec System Logon Account (SLA) is created when you install Backup Exec. When the SLA is created, the user name and password match the credentials that were provided during install for the Backup Exec Services credentials. The owner of the SLA is the user that installed Backup Exec. It is a common account, by default. Common accounts are the shared accounts that all users can access. See “Creating a new Backup Exec System Logon Account” on page 612. 604Configuration and settings Backup Exec logon accounts
- 605. The Backup Exec System Logon Account may have access to most or all of your data since it contains the Backup Exec Services credentials. If you want to make Backup Exec more secure, you can change the SLA to be a restricted account. You can also delete it after making another logon account the default. However, if you delete the SLA, the jobs in which it is used may fail. If the SLA is deleted, you can re-create it using the Logon Account Management dialog box. The SLA is used for the following tasks and jobs: ■ Jobs that were migrated from a previous version of Backup Exec ■ Duplicate backup data jobs ■ Command Line Applet (bemcli.exe) Restricted logon accounts Backup Exec logon accounts can be common or restricted. When you create a Backup Exec logon account, you can designate it as a restricted account. To use a restricted logon account, you must be the owner of the logon account or you must know the password for the logon account. The person who created the logon account is the owner. If you authorize only a few people to back up or restore data, you can make the logon account a restricted logon account. The main reasons to restrict a logon account are as follows: ■ To help you limit access to the computers available for backup. ■ To help you limit the computers to which you can restore. When you use a restricted logon account to select the data for a job, the logon account information is saved with the selection list. Anyone who tries to edit the job must provide the password to the restricted logon account. Backup Exec loads the selections for that job only when the password for the restricted logon account is provided. See “Creating a Backup Exec logon account” on page 605. See “Editing a Backup Exec logon account” on page 607. See “Changing the password for a Backup Exec logon account” on page 609. See “Replacing a Backup Exec logon account” on page 609. See “Deleting a Backup Exec logon account” on page 610. See “Copying logon account information to another Backup Exec server” on page 613. Creating a Backup Exec logon account You can create Backup Exec logon accounts using the Logon Account Wizard, which guides you through the creation of a Backup Exec logon account, or by using 605Configuration and settings Backup Exec logon accounts
- 606. the Logon Account Management dialog box. You can enter Backup Exec logon account property information when you create the Backup Exec logon account. However, Backup Exec assigns the Backup Exec logon account owner to the user name you used to log on to Backup Exec. The owner of the Backup Exec logon account cannot be modified. This topic includes the following information: To create a Backup Exec logon account using the Logon Account Wizard To create a Backup Exec logon account manually To create a Backup Exec logon account using the Logon Account Wizard 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Logon Accounts, and then select Logon Account Wizard. 3 Click Add a new logon account, and then click Next. 4 Type a user name and password. 5 Click Next. 6 In the Logon account name field, type the unique name for the Backup Exec logon account. 7 Under Make this account, select whether you want the account to be a common logon account or a restricted logon account. Common logon accounts are the shared accounts that all users can access. Restricted logon accounts can only be used by the owner of the logon account or by those who know the password. 8 If you want to make this the default logon account that is used to browse, make selections, and restore data on your local computers and remote computers, select The default logon account. 9 Click Next. 10 Review the options that you selected, and then click Finish to create the logon account. To create a Backup Exec logon account manually 1 Click the Backup Exec button, and then select Configuration and Settings. 2 Select Logon Accounts, and then select Manage Logon Accounts. 3 Click Add. 606Configuration and settings Backup Exec logon accounts
- 607. 4 In the User name field, type the fully qualified user name for the Backup Exec logon account. For example, type "DOMAINAdministrator". The user name is provided when you attempt to connect to a computer. The user name is not case-sensitive for the computers that are accessed. 5 In the Password field, type the password for the account. The password you enter is encrypted for security. You can leave this field blank if this Backup Exec logon account does not need a password. 6 In the Confirm password field, type the password again to verify it. 7 In the Account name field, type the unique name for the Backup Exec logon account. 8 In the Notes field, type any optional notes to explain how the Backup Exec logon account is used. 9 Select This is a restricted logon account if you want the Backup Exec logon account to be used only by the owner of the logon account and those who know the password. If this option is not selected, the Backup Exec logon account is created as a common account. Common accounts are the shared accounts that all users can access. 10 Select This is my default account to make this account your default Backup Exec logon account, which is used to browse, make selections, or restore data on your local computers and remote computers. See “Backup Exec logon accounts” on page 603. Editing a Backup Exec logon account When you edit a Backup Exec logon account, the changes are automatically applied to all the content that uses the Backup Exec logon account. Changes made to a Backup Exec logon account are applied immediately. You do not have to restart your system for the changes to take effect. You can edit the following properties for a Backup Exec logon account: ■ Type (restricted, common, or default) ■ Account name ■ Password ■ User name ■ Notes 607Configuration and settings Backup Exec logon accounts
- 608. To edit a Backup Exec logon account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the Backup Exec logon account you want to change, and then click Edit. If you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can edit the account. 4 Edit any of the following properties: Type the fully qualified user name for the Backup Exec logon account. For example, DOMAINAdministrator. The user name is provided when you attempt to connect to a computer. The user name you enter is not case sensitive for the computers that are accessed. User name Click this option to change the password for the account. The password you enter is encrypted for security. Change Password Type a unique name for the Backup Exec logon account. The user name is automatically added if you do not enter information into the field. Account name Type any optional notes indicating how the Backup Exec logon account is used. Notes Select this option to make this Backup Exec logon account a restricted logon account. Restricted logon accounts can be used only by the owner of the logon account and those who know the password. If this option is not selected, the Backup Exec logon account is a common account. Common accounts are the shared accounts that all users can access. This is a restricted logon account Select this option to make this account your default Backup Exec logon account. Your default account is used to browse, make selections, or restore data on your local computers and remote computers. This is my default account 5 On the Edit Logon Credentials dialog box, click OK. 6 On the Logon Account Management dialog box, click OK. See “Backup Exec logon accounts” on page 603. 608Configuration and settings Backup Exec logon accounts
- 609. Changing the password for a Backup Exec logon account You can change a Backup Exec logon account password using the following steps. Changes made to a Backup Exec logon account password are applied immediately. To change the password for a Backup Exec logon account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the Backup Exec logon account that you want to change, and then click Edit. If you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can edit the account. 4 Click Change Password. 5 In the Password field, type a new password. 6 In the Confirm field, re-type the password, and then click OK. 7 On the Edit Logon Credentials dialog box, click OK. 8 On the Logon Account Management dialog box, click OK. See “Backup Exec logon accounts” on page 603. Replacing a Backup Exec logon account You can replace a Backup Exec logon account within all existing jobs. The data in existing jobs that use the Backup Exec logon account will be updated to use the new Backup Exec logon account. If the new Backup Exec logon account is restricted, you must provide the password. To replace a Backup Exec logon account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the Backup Exec logon account you want to replace, and then click Replace. 609Configuration and settings Backup Exec logon accounts
- 610. 4 On the Replace Logon Account dialog box, select the Backup Exec logon account with which you want to replace the selected Backup Exec logon account. If the Backup Exec logon account is restricted and you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can select the account. 5 Click OK. See “Backup Exec logon accounts” on page 603. Deleting a Backup Exec logon account If you no longer need a Backup Exec logon account, you can delete it. You cannot delete a Backup Exec logon account in the following situations: ■ It is referenced by a job. ■ It is owned by a user who is logged on to the Backup Exec server. ■ It is set as the default Backup Exec logon account of a user who is logged on to the Backup Exec server. If a logon account is used in any of these situations, you must replace it with a different logon account before you can delete it. To delete a Backup Exec logon account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the Backup Exec logon account you want to delete, and then click Delete. 4 Do either of the following: Click Yes to confirm the deletion.If the logon account is not referenced by any backup jobs 610Configuration and settings Backup Exec logon accounts
- 611. Complete the following steps to replace the logon account with a different logon account in any referenced backup jobs. ■ On the Delete Logon Account dialog box, click Replace. ■ On the Replace Logon Account dialog box, select the Backup Exec logon account with which you want to replace the selected Backup Exec logon account. If the Backup Exec logon account is restricted and you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can select the account. The logon account that you select here replaces the previous logon account in all existing jobs and selection lists. If the logon account is referenced by backup jobs 5 Click OK. See “Backup Exec logon accounts” on page 603. See “Replacing a Backup Exec logon account” on page 609. Changing your default Backup Exec logon account You can change your default Backup Exec logon account that enables you to browse, make selections, or restore data. To change your default Backup Exec logon account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the Backup Exec logon account that you want to use as your default Backup Exec logon account, and then do one of the following: ■ Click Set as Default. ■ Click Edit, select This is my default account, and then click OK. 4 Click OK. See “Backup Exec logon accounts” on page 603. 611Configuration and settings Backup Exec logon accounts
- 612. Creating a new Backup Exec System Logon Account The Backup Exec System Logon Account enables you to perform several operations. If you delete the Backup Exec System Logon Account, you should create a new one that enables you to perform the specified operations. To create a new Backup Exec System Logon Account 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Click System Account. 4 Complete the following options: Type the fully qualified user name for the Backup Exec logon account. For example, DOMAINAdministrator. The user name is provided when you attempt to connect to a computer. The user name you enter is not case-sensitive for the computers that are accessed. User name Click this option to change the password for the account. The password you enter is encrypted for security. Change Password Type a unique name for the Backup Exec logon account. The user name is automatically added if you do not enter information into the field. Account name Type any optional notes indicating how the Backup Exec logon account is used. Notes Select this option to make this Backup Exec logon account a restricted logon account. Restricted logon accounts can be used only by the owner of the logon account and those who know the password. If this option is not selected, the Backup Exec logon account is a common account. Common accounts are the shared accounts that all users can access. This is a restricted logon account Select this option to make this account your default Backup Exec logon account. Your default account is used to browse, make selections, or restore data on your local computers and remote computers. This is my default account 5 Click OK to create the system logon account. See “Backup Exec logon accounts” on page 603. 612Configuration and settings Backup Exec logon accounts
- 613. Copying logon account information to another Backup Exec server You can copy logon account information from one Backup Exec server to a different Backup Exec server. To copy logon account information to another Backup Exec server 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Select the logon account that you want to copy, and then click Copy to Servers. 4 If prompted, enter the password for the logon account that you selected. 5 Do one of the following: ■ To add invidual servers manually, in the Server Name field, enter the name of the Backup Exec server that you want to copy the logon account information to, and then click Add ■ To add several servers from a list, click Import List, and then browse to the list of server names. 6 If you want to overwrite a logon account with the same name on the destination Backup Exec server, check Overwrite logon account if one with this description already exists on the destination server. 7 Click OK. See “Backup Exec logon accounts” on page 603. Testing logon accounts You can test Backup Exec logon accounts to ensure that they can access your backup sources before you run jobs. Testing your logon accounts before you attempt to run jobs can help prevent failures and save you time. To test logon accounts 1 Click the Backup Exec button, select Configuration and Settings, and then select Logon Accounts. 2 Select Manage Logon Accounts. 3 Click Test. 4 In the Logon Account field, select the logon account that you want to test. 5 In the Server field, select the server that you want to access with the logon account. 613Configuration and settings Backup Exec logon accounts
- 614. 6 Click Test. Backup Exec checks to make sure whether the logon account can acces the server that you selected. 7 When you are finished testing logon accounts, click Close. 8 Click OK. See “Backup Exec logon accounts” on page 603. Starting and stopping Backup Exec services You can use the Backup Exec Services Manager to start, stop, and restart Backup Exec services. To start or stop Backup Exec services 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Services. 2 Select the server for which you want to start or stop services. 3 Do any of the following: Click Start all services.To start all services for the selected server Click Stop all services.To stop all services for the selected server Click Restart all services.To restart all services for the selected server 4 Cick OK. See “Changing the credentials for a service account” on page 614. See “Changing startup options for Backup Exec services” on page 616. Changing the credentials for a service account On the Backup Exec server, all Backup Exec services run in the context of a user account that is configured for the Backup Exec system services. 614Configuration and settings Starting and stopping Backup Exec services
- 615. Note: The Backup Exec service account and the Backup Exec system logon account are set to the same user name when Backup Exec is installed. If you need to change the user name for the service account or if the service account is no longer used, then you should also change the Backup Exec system logon account to use new credentials. If this computer is in a domain, enter a Domain Administrators account, or an equivalent account that is part of the Domain Admins group. In the Domain list, select or enter the Domain name. If this computer is in a workgroup, enter an Administrators account, or an equivalent account that is part of the Administrators group on the computer. In the Domain list, select or enter the computer name. The account that you designate for Backup Exec services, whether it is a new account or an existing user account, is assigned the following rights: ■ Authenticate as any user and gain access to resources under any user identity. ■ Create a token object, which can then be used to access any local resources. ■ Log on as a service. ■ Administrative rights (provides complete and unrestricted rights to the computer). ■ Backup operator rights (provides rights to restore files and directories). ■ Manage auditing and security log. See “Required user rights for backup jobs” on page 139. Due to security implementations in Microsoft Small Business Server, the service account must be Administrator. To change the credentials for a service account 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Services. 2 On the Backup Exec Services Manager dialog box, select the appropriate server, and then select the service for which you want to change the service account. 3 Click Edit credentials. 4 Check the Change service account credentials check box. 615Configuration and settings Changing the credentials for a service account
- 616. 5 Complete the following fields: Type the current user name for the service account that you want to change. Old user name Type the current password for the service account that you want to change. Old password Type the new user name for the service account that you want to change. New user name Type the new password for the service account that you want to change. New password Type the new password again to confirm it.Confirm password Select this option to grant the service account the proper system service rights. Grant required rights to the service account 6 Click OK. 7 Click Close. See “Starting and stopping Backup Exec services” on page 614. See “Changing startup options for Backup Exec services” on page 616. Changing startup options for Backup Exec services You can change startup options for Backup Exec services. Each individual service can be configured to start automatically or manually. Or you can disable a service entirely. Services that are configured for automatic startup automatically start when the server starts. Services that are configured for manaul startup do not start automatically. You must manaually start services that are configured for manual startup. You can start, stop, or restart services in the Backup Exec Services Manager. To change service startup options 1 Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Services. 2 On the Backup Exec Services Manager dialog box, select the appropriate server, and then select the service for which you want to change startup options. 3 Click Edit credentials. 4 Check the Change startup options check box. 616Configuration and settings Changing startup options for Backup Exec services
- 617. 5 Select from the following options: Select this option to automatically start the service account at system startup. Automatic Select this option to prevent the service account from automatically starting at system startup. If you select this option, you must start the service account manually. Manual Select this option to disable the service account at system startup. Disabled 6 Click OK. 7 Click Close. See “Starting and stopping Backup Exec services” on page 614. See “Changing the credentials for a service account” on page 614. Configuring audit logs You can use audit logs to examine and review information about the operations that have been performed in Backup Exec. The audit log displays the date and time of the activity, who performed it, what the activity was, and a description of the activity. Audit logs can be configured to display information about the activities that occur for all or any of the following: ■ Alerts ■ Archive ■ Audit logs ■ Backup set retention ■ Devices and media ■ Encryption keys ■ Error-handling rules ■ Install ■ Jobs ■ Logon accounts ■ Server configuration 617Configuration and settings Configuring audit logs
- 618. You can delete the audit logs as part of the Backup Exec database maintenance, and you can save the audit log to a text file. Any changes that are made to the audit log, such as when database maintenance occurs, can also be displayed in the audit log. To configure audit logs 1 Click the Backup Exec button, select Configuration and Settings, and then select Audit Log. 2 Click Configure Logging. 3 On the Audit Log Configuration dialog box, select the check box of the category that you want to display in the audit log. Expand the category by clicking the arrow to the left of the category. Select the operations that you want to display for the category. Clear the check box of any item or operation that you do not want to display. 4 Click OK. See “Viewing the audit log” on page 618. See “Removing entries from the audit log” on page 618. See “Saving an audit log to a text file” on page 619. Viewing the audit log You can view audit logs to see when changes were made in Backup Exec and which users made the changes. To view the audit log 1 Click the Backup Exec button, select Configuration and Settings, and then select Audit Log. 2 In the Select category to view field, select the category for which you want to view audit information. 3 Use the scroll bar at the bottom of the Audit Logs window to view the whole entry, or double-click the entry to display the same information in an easy-to-read Audit Log Record. See “Configuring audit logs” on page 617. Removing entries from the audit log You can remove the entries for all categories or for a selected category. 618Configuration and settings Viewing the audit log
- 619. To remove entries from the audit log 1 Click the Backup Exec button, select Configuration and Settings, and then select Audit Log. 2 In the Select category to view field, select the category for which you want to view audit information. 3 Click Clear Category Log to remove all entries from an audit log category. If you select specific categories, only the logs that are generated for the selected categories are cleared when you click Clear Category Log. See “Configuring audit logs” on page 617. Saving an audit log to a text file You can save the audit log as a text file. To save the audit log to a text file 1 Click the Backup Exec button, select Configuration and Settings, and then select Audit Log. 2 Click Save Log to File to specify a file name and location to save the audit log entries. See “Configuring audit logs” on page 617. Copying configuration settings to another Backup Exec server If you have the Central Admin Server Option (CASO), you can copy configuration settings and logon information from one Backup Exec server to another. This copy ability lets you quickly set up a group of Backup Exec servers with the same configuration or logon settings. Note: To copy configuration settings and logon information to other Backup Exec servers, you must install the Copy Server Configurations feature. See “Installing additional Backup Exec options to the local Backup Exec server” on page 62. 619Configuration and settings Saving an audit log to a text file
- 620. To copy configuration settings to another Backup Exec server 1 Click the Backup Exec button, select Configuration and Settings, and then click Copy Settings to Other Servers. 2 Select any of the following options: Select this option to copy the default schedule settings from this Backup Exec server to another Backup Exec server. Default schedule Select this option to copy error-handling rules from this Backup Exec server to another Backup Exec server. Error-handling rules Select this option to copy the alert configuration from this Backup Exec server to another Backup Exec server. Alert configuration 3 Select the Backup Exec server or servers to which you want to copy the selected settings. If the destination server is not in the list, do one of the following: ■ To add a server manually, click Add, and then select the server or servers that you want to add to the list. ■ To import a list of servers, click Import List, browse to select the list, and then click Open. 4 Click OK. See “About the Central Admin Server Option” on page 1106. Viewing server properties You can view properties for the local Backup Exec server or any other server that you monitor with Backup Exec. You can view the following properties for the local Backup Exec server: ■ Server name ■ Server description ■ Server status ■ Version and license information ■ Date and time zone information ■ Operating system information ■ Memory and page file information 620Configuration and settings Viewing server properties
- 621. Additionally, you can view the following properties for any server that you monitor with Backup Exec: ■ Server name ■ Server description ■ Operating system information ■ Backup Exec version and license information If you have the Central Admin Server Option (CASO), you can also view information about the Backup Exec database, device and media database, and catalog database. See “Viewing the settings for a central administration server” on page 1162. To view server properties ◆ Complete either of the following as necessary: ■ Click the Backup Exec button, select Configuration and Settings, and then click Local server properties. ■ When you are finished viewing the local server properties, click OK. To view the local Backup Exec server's properties ■ On the Backup and Restore tab, double-click the server whose properties you want to view. ■ In the left pane, click Properties. To view any other server's properties 621Configuration and settings Viewing server properties
- 622. Reports This chapter includes the following topics: ■ Reports in Backup Exec ■ Running a report now ■ Scheduling a report ■ Creating a custom report ■ Saving a report ■ Printing a report from the Backup Exec Report Viewer ■ Viewing completed reports ■ Editing a report ■ Re-running a completed report ■ Deleting a report ■ Setting defaults for standard and custom reports ■ Viewing report properties ■ List of Backup Exec standard reports Reports in Backup Exec Backup Exec includes more than 40 standard reports that can provide detailed information about the alerts, devices, media, and jobs in your Backup Exec environment. In addition, Backup Exec provides the ability to create custom reports so you can create reports to fit your specific environment and needs. Both standard reports and custom reports can be run on demand at any time, can be scheduled 15Chapter
- 623. to run at a specific time, or can be scheduled to run on a recurring schedule. When you schedule a report job, you can set up email notification so that you or anyone else can be notified when the report job completes, and you can include a copy of the report in the email Reports can be viewed and printed in the following formats: ■ PDF ■ HTML ■ XML ■ Microsoft Excel (XLS) ■ Comma-separated Value (CSV) Reports are grouped on the Reports tab by category. For example, reports relating to devices are grouped in the Devices report group. To see the names and descriptions of the standard reports for a group, click the name of the appropriate report group. Note: The See Completed report group only includes the scheduled reports that have completed. Reports that were run immediately are deleted when you close the report viewer. Requirements for reports Before you attempt to run either standard reports or custom reports, review the following requirements: ■ To properly format integrated Backup Exec reports, you must configure a default printer using the Windows Control Panel Printers applet. This is required even if you do not have a printer attached to your system. For information on configuring a printer by using the Windows Control Panel Printers applet, see your Microsoft Windows documentation. ■ To run reports across multiple Backup Exec servers, you must install the Backup Exec Enterprise Server Option, even if you do not have a shared storage environment. ■ To view reports in PDF format, ensure that the latest version of Adobe Acrobat Reader is installed. Reports and the Job Monitor Reports cannot be monitored from the Job Monitor. Reports that are running, are scheduled to run, or are completed do not appear on the Job Monitor. All report operations are displayed on the Reports tab. 623Reports Reports in Backup Exec
- 624. See “Running a report now” on page 624. See “List of Backup Exec standard reports” on page 640. Running a report now When you run a report, you can specify the criteria that is used to determine the items that will be included in the report. The settings that are available for you to select depend on the type of data that can be included in the report. After the report is generated, only the items that match the criteria appear in the report. If you do not want to run the report immediately, you should use the New Scheduled Report option instead. See “Scheduling a report” on page 624. To run a report 1 On the Reports tab, under Report Groups, click the report group that contains the report that you want to run now. 2 Right-click the report you want to run, and then click Run Now. 3 If the Run Report Now - <report_name> properties page appears, select the appropriate settings for the data that you want to include in the report, and then click OK. 4 After you have finished viewing the report, click Close. Backup Exec automatically deletes the report when you close the Report Viewer. Scheduling a report You can schedule a report to run once at a specific time or multiple times on a recurring schedule. Scheduled reports are listed in the See Upcoming report group on the Reports tab. You can edit or delete scheduled reports. To schedule a report 1 On the Reports tab, under Report Groups, click the report group that contains the report that you want to schedule. 2 Right-click the report name, and then click Schedule Report. 3 Type a name for the report. 4 If any of the following options appear in the left pane, click the option name, and then enter the criteria for the data that you want to include on the report. Note that some reports do not include any of the following options. 624Reports Running a report now
- 625. ■ Backed up servers ■ Ranges ■ Audit log category ■ Job status ■ Media sets ■ Vault 5 (Optional) If you want to send an email to yourself or someone else when the report is completed, do the following: ■ In the left pane, click Notification. ■ Select an existing recipient or click Manage Recipients to add a new recipient. ■ If you want to include a copy of the report in the email notification, check Include the report in email notifications. 6 In the left pane, click Schedule, and then select one of the following scheduling options: Lets you schedule the job to run multiple times. You can set the recurrence pattern so that the job runs Recurrence Lets you run the job immediately.Run now with no recurring schedule Lets you set the date and time to run the report. Run on Lets you create and save the report, but not schedule or run the report at this time. If you select this option, you can then use an external scheduling tool to schedule the job to run at a specific time, or you can manually run the job when you are ready. Even though the job is not scheduled, the report is listed in the See Upcoming report group on the Report tab. Create without a schedule 7 Click OK. The scheduled report is saved in the See Upcoming report group. After the report runs, it is saved in the See Completed report group. See “Viewing completed reports” on page 636. 625Reports Scheduling a report
- 626. Creating a custom report You can create reports that contain information to meet the specific requirements of your organization. You choose the data to include in the report, and then determine how the data is filtered, sorted, and grouped. In addition, you can set up a pie graph or a bar graph to graphically represent the report data. Filters let you customize reports to include only the information that meets specific criteria. For example, you can use filters to find the jobs that contain a specific word, the alerts that occurred on a specific day, or the media that are in a specific location. You use filter criteria to create filter expressions. You can use one or multiple filter expressions. A filter expression consists of a field name, an operator, and a value. The following example filter expression finds all alerts for errors: Table 15-1 Filter expression for finding alerts for errors DataFilter type Alert TypeField name = (Equal)Operator ErrorsValue If you want the report to include only the alerts for errors that occurred on a specific day, add another filter expression for the date and time, as shown in the example below: Table 15-2 Filter expression for finding alerts on a specific day DataFilter type Date EnteredField name =(Equal)Operator 06/03/2014 | <time>Value Grouping fields creates sections on the report. For example, if you group by Backup Exec server, Backup Exec creates a section for each Backup Exec server that matches the filter criteria. Under each Backup Exec server’s section, the report displays the data that corresponds to the remaining fields that you selected for the report. You can sort a custom report by up to three of the fields that you have chosen for the report. When you sort on fields, Backup Exec arranges all of the data that matches the sort criteria together in the report. For example, if you sort on the 626Reports Creating a custom report
- 627. Backup Exec server field in ascending order, all data for Backup Exec server A displays first, followed by all data for Backup Exec server B, and so on. To create a custom report 1 On the Reports tab, click New Custom Report. 2 On the Custom Report dialog box, type a name and description for the report. 3 If you do not want this report to include the default header and footer settings, uncheck Use header and footer settings specified in Backup Exec Settings. The default header and footer settings can include a customized logo, a custom color for the banner, and text for the footer. These items are set in the default Backup Exec settings. See “Setting defaults for standard and custom reports” on page 638. 4 In the left pane, click Field Selection. 5 In the Category box, select a group for which you want to create a report. 6 For additional field selections, click Show advanced fields. 7 In the Available fields list, select the fields that you want to include on the report, and then click the Right arrow (>>) button to move the fields to the Fields selected for the report list. 8 After you have moved all of the fields that you want to include on the report to the Fields selected for the report list, arrange the order in which you want the fields to appear. The fields appear on the report in the order in which they are listed in the Fields selected for the report list, with the first field appearing as the first field on the left of the report. To move a field, select it from the Fields selected for the report list, and then click Move Up or Move Down to move it to the appropriate location in the list. 9 To adjust the width of the column for a field, do the following in the order listed: ■ Click the field name in the Fields selected for the report list. ■ In the Column width field, type the new width. ■ Click Set. 10 (Optional) If you want to filter the data on the report, do the following: ■ In the left pane, click Filters. ■ In the Field name list, select the field on which you want to filter data. ■ In the Operator list, select the operator that you want to use for this filter. 627Reports Creating a custom report
- 628. ■ In the Value field, type or select the specific data that you want to include on the report. ■ Click Add. ■ To combine sets of filter expressions, do any of the following: Click AND. For example, to find all backup jobs that failed, add the following expressions: ■ Status = Failed ■ Type = Backup After you set up the expressions, do the following: ■ Click AND to combine the two expressions. The combined expression is: Status = Failed AND Type = Backup To combine two filter expressions so that both expressions must be true for the result to be true Click OR. For example, to find jobs that either failed or were canceled, add the following expressions: ■ Status = Failed ■ Status = Canceled After you set up the expressions, do the following: ■ Click OR to combine Status = Failed with Status = Canceled. The combined expression is: Status = Failed OR Status = Canceled To combine two filter expressions so that one of the expressions must be true for the result to be true 628Reports Creating a custom report
- 629. Click ( ) + For example, to find backup jobs and restore jobs that failed, add the following expressions: ■ Status = Failed ■ Type = Backup ■ Type = Restore After you set up the expressions, do the following: ■ Use OR to combine Type = Backup with Type = Restore. ■ Press and hold Ctrl while you click Type = Backup and Type = Restore. ■ Click ( ) + to combine Type = Backup with Type = Restore. ■ Use AND to combine Status = Failed with (Type = Backup OR Type = Restore). The combined expression is: Status = Failed AND (Type = Backup OR Type = Restore) To combine two filter expressions into a single expression Click ( ) - For example, if you used ( ) + to combine Type = Backup with Type = Restore, it is displayed on the Filters dialog box as follows: (Type = Backup OR Type = Restore) To make the combined expression into two individual expressions, do the following: ■ Press and hold Ctrl while you click both Type = Backup and Type = Restore. ■ Click ( ) - After you separate the expressions, they are displayed without the parentheses. To separate two filter expressions that were combined into a single expression 11 (Optional) If you want to organize the report into sections, do the following: ■ In the left pane, click Grouping. ■ In the Group by list, select the field that you want to use as a group. ■ Click Ascending or Descending. Ascending order lists numbers from smallest to largest and lists letters in alphabetical order. Descending order lists numbers from largest to smallest and lists letters in reverse alphabetical order. ■ If you want to further group the data, select the fields in the Then group by lists, and then click Ascending or Descending for those fields. 629Reports Creating a custom report
- 630. A report must have at least one field that is not grouped. For example, if you select three fields to include on the report, you can group only two of the fields. If you group all of the fields, no data appears on the report because all of the data is listed in the group section titles. In addition, you must have at least four fields on the report to use all three grouping fields. 12 (Optional) If you want to sort the data on the report, do the following: ■ In the left pane, click Sort. ■ In the Sort on list, select the field on which you want to sort the data in the report. ■ Select Ascending or Descending. Ascending order lists numbers from smallest to largest and lists letters in alphabetical order. Descending order lists numbers from largest to smallest and lists letters in reverse alphabetical order. ■ If you want to further sort the data, select the fields on which you want to sort in the Then sort on lists, and then click Ascending or Descending for those fields. 13 (Optional) If you want to add a pie graph or bar graph to the report, do the following: ■ In the left pane, click Graph Options. ■ In the Graph type list, select either Bar or Pie. ■ Select the types of data that you want to include on the graph. 14 (Optional) If you want to see what the report will look like before you save it, in the left pane, click Preview. 15 Click OK to save the custom report. Adding or removing fields on a custom report To change the data that appears on a custom report, add new fields or remove existing fields. To add or remove fields on a custom report 1 On the Reports tab, under Report Groups, click Custom. 2 Right-click the report that contains the fields you want to change, and then click Edit. 3 In the left pane, click Field Selection. 4 Do any of the following: 630Reports Creating a custom report
- 631. ■ Select a category. ■ Under Available fields, select the fields you want to add, and then click the right arrow (>>) button. To add new fields to the report Under Fields selected for the report, click the field you want to remove, and then click the left arrow (<<) button. To remove fields from the report Changing filters for a custom report Use the following steps to change the existing filters on a custom report. To change filters for a custom report 1 On the Reports tab, under Report groups, click Custom Reports. 2 In the reports list, right-click the report that you want to change and then click Edit. 3 In the left pane, click Filters. 4 Create a filter by defining one or more filter expressions. Select a field name and operator, and then enter a value. Click Add. To add a new filter expression Do the following in the order listed. ■ Under Filter criteria, select the filter expression that you want to edit, and then click Edit. ■ Under Filter expression, edit the expression’s values. ■ Under Filter expression, click Update. To edit an existing filter expression Under Filter criteria, select the filter expression that you want to delete, and then click Remove. To delete a filter expression 5 To combine sets of filter expressions, do any of the following: 631Reports Creating a custom report
- 632. Click AND. For example, to find all backup jobs that failed, add the following expressions: ■ Status = Failed ■ Type = Backup After you set up the expressions, do the following: ■ Click AND to combine the two expressions. The combined expression is: Status = Failed AND Type = Backup To combine two filter expressions so that both expressions must be true for the result to be true Click OR. For example, to find jobs that either failed or were canceled, add the following expressions: ■ Status = Failed ■ Status = Canceled After you set up the expressions, do the following: ■ Click OR to combine Status = Failed with Status = Canceled. The combined expression is: Status = Failed OR Status = Canceled To combine two filter expressions so that one of the expressions must be true for the result to be true Click ( ) + For example, to find backup jobs and restore jobs that failed, add the following expressions: ■ Status = Failed ■ Type = Backup ■ Type = Restore After you set up the expressions, do the following: ■ Use OR to combine Type = Backup with Type = Restore. ■ Press and hold Ctrl while you click Type = Backup and Type = Restore. ■ Click ( ) + to combine Type = Backup with Type = Restore. ■ Use AND to combine Status = Failed with (Type = Backup OR Type = Restore). The combined expression is: Status = Failed AND (Type = Backup OR Type = Restore) To combine two filter expressions into a single expression 632Reports Creating a custom report
- 633. Click ( ) - For example, if you used ( ) + to combine Type = Backup with Type = Restore, it is displayed on the Filters dialog box as follows: (Type = Backup OR Type = Restore) To make the combined expression into two individual expressions, do the following: ■ Press and hold Ctrl while you click both Type = Backup and Type = Restore. ■ Click ( ) - After you separate the expressions, they are displayed without the parentheses. To separate two filter expressions that were combined into a single expression 6 Click OK. Changing the way data is grouped or sorted in a custom report Use the following steps to change the way data is grouped or sorted in a custom report. To change the way data is grouped or sorted in a custom report 1 On the Reports tab, under Report Groups, click Custom. 2 In the list of custom reports, right-click the report that you want to change, and then select Edit. 3 Do any of the following: ■ In the left pane, click Grouping. ■ On the Group by or Then group by list that contains the field you want to change, click the down arrow, and then select the new field to use as a group. To change the field that is used as a group ■ In the left pane, click Grouping. ■ On the Group by or Then group by list that contains the group you want to remove, click the down arrow, and then click <None>. To remove a group Click Ascending or Descending.To change the order in which data is grouped 633Reports Creating a custom report
- 634. ■ In the left pane, click Sorting. ■ On the Sort on or Then sort on list that contains the sorting option you want to change, click the down arrow, and then select the new field to use to sort the data. To change the field that is used to sort the data ■ In the left pane, click Sorting. ■ On the Sort on or Then sort on list that contains the sorting option you want to remove, click the down arrow, and then click <None>. To disable sorting Click Ascending or Descending.To change the order in which data is sorted 4 Click OK. Changing graph options in custom reports You can include a pie graph or a bar graph in custom reports. At least two fields must be selected on the Field Selection dialog box to create a pie graph, and at least three fields must be selected to create a bar graph. To change graph options in custom reports 1 On the Reports tab, under Report Groups, click Custom. 2 Right-click the report you want to edit, and select Edit. 3 In the Custom Report window, click Graph Options. 4 Change the graph title or select new fields to populate the graph. 5 Click OK. Previewing custom reports Use the preview feature to verify that you created a custom report correctly. To preview custom reports 1 On the Reports tab, under Report Groups, click Custom. 2 Right-click the report that you want to preview, and then click Edit. 3 In the left pane, click Preview. 634Reports Creating a custom report
- 635. Copying a custom report You can make one or more copies of a custom report. Each copy of the custom report resides in the Custom report group, along with the original custom report. To copy a custom report 1 On the Reports tab, under Report Groups, click Custom. 2 Right-click a custom report that you want to copy, and then click Copy. 3 Type a name for the report, and then click OK. The copy of the custom report appears in the Custom report group. Saving a report Reports can be saved to any location that you choose on your hard drive or network in any of the following formats: ■ HTML file (.htm) ■ Adobe PDF file (.pdf) ■ XML file (.xml) ■ Comma-separated value file (.csv) ■ Microsoft Office Excel workbook (.xls) You can save a report that is currently displayed on the screen or that is in the See Completed report group. To save a report 1 On the report, in the Report Viewer, click Save As. On the report, in the Report Viewer, click Save As. To save a report that is currently displayed on the screen ■ On the Reports tab, under Report Groups, click See Completed. ■ Click Save As. ■ Double-click a completed report that you want to save to a new location. To save a report that is in the See Completed report group 2 Enter the file name and location where you want to save the report. 635Reports Saving a report
- 636. 3 In the Save as type box, select a format in which to save the report. When you save a report in HTML format, both the HTML file and a .GIF image file are saved. 4 Click Save. Printing a report from the Backup Exec Report Viewer You can print reports from a locally-attached printer or a network printer. To print a report, the printer must be configured to print in the landscape mode. The following printer settings ensure that the report prints correctly: ■ On the Layout tab of the Print dialog box, under Orientation, Landscape should be selected. Note that you may need to select Preferences to access the Layout tab. ■ To print all of the pages in a multiple page report, on the Options tab of the Print dialog box, the option Print all linked documents should be selected. ■ To print all of the pages in a multiple-page report in the correct order, the first page of the report must be displayed on the screen before the print job is initiated. ■ If the report does not print correctly, you may need to change the page setup options in Internet Explorer to remove the header and footer and reduce the margins. To print a report from the Backup Exec Report Viewer 1 Run a report. See “Running a report now” on page 624. 2 On the Report Viewer, click Print. 3 Select a printer from the Windows Print dialog box. 4 Click Print. Viewing completed reports After a scheduled report runs, it is saved in the See Completed report group. To view completed reports 1 On the Reports tab, under Report Groups, click See Completed. 2 Double-click the report that you want to view. 636Reports Printing a report from the Backup Exec Report Viewer
- 637. Editing a report Use the following steps to edit the properties of a scheduled standard report or a custom report before it runs. If the report that you want to edit has been run in a previous report job, the changes you make now may affect the appearance of the reports in job history. Symantec recommends that you copy the report and then edit the copy. To edit a scheduled standard report or a custom report 1 On the Reports tab, under Report Groups, click See Upcoming. On the Reports tab, under Report Groups, click See Upcoming. To edit a scheduled standard report On the Reports tab, under Report Groups, click Custom. To edit a custom report 2 Right-click a report you want to edit, and then click Edit. 3 Edit the report properties and then click OK. Re-running a completed report You can run the reports that appear in the See Completed report group multiple times. To re-run a completed report 1 On the Reports tab, under Report Groups, click See Completed. 2 Right-click a report, and then click Retry Report Now. Backup Exec creates and runs another iteration of the report. 3 To view the report again, double-click the new report. Deleting a report Reports that you create using the Run now option are automatically deleted after you view the report. However, custom reports, completed reports, and scheduled reports can be deleted at your convenience. Note: Standard Backup Exec reports cannot be deleted. 637Reports Editing a report
- 638. To delete a report 1 On the Reports tab, under Report Groups, do one of the following: ■ To delete a custom report, click Custom. ■ To delete a scheduled report, click See Upcoming. ■ To delete a completed report, click See Completed. 2 Right-click the report that you want to delete, and then click Delete. 3