Backup Exec 21

Administrator's Guide
Documentation version: Backup Exec 21

Legal Notice
Copyright © 2020 Veritas Technologies LLC. All rights reserved.

Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies
LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their
respective owners.

This product may contain third-party software for which Veritas 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. Refer to the Third-party Legal Notices document accompanying this
Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements

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 Veritas Technologies
LLC 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. VERITAS TECHNOLOGIES LLC
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, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. 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.
Veritas Technologies LLC
2625 Augustine Drive.
Santa Clara, CA 95054

http://www.veritas.com
Technical Support
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
the company to answer your questions in a timely fashion.
Our 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 our support offerings, you can visit our website at the following
URL:
www.veritas.com/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.veritas.com/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
■ 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 Technical Support
■ Recent software configuration changes and network changes

Licensing and registration

If your product requires registration or a license key, access our technical support
Web page at the following URL:
www.veritas.com/support

Customer service
Customer service information is available at the following URL:
www.veritas.com/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
■ Advice about technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources
If you want to contact us regarding an existing support agreement, please contact
the support agreement administration team for your region as follows:

Worldwide (except Japan) [email protected]

Japan [email protected]
 Contents

Technical Support ............................................................................................. 4

Chapter 1 Introducing Backup Exec ................................................ 36

About Backup Exec ...................................................................... 36

How Backup Exec works ................................................................ 36

Chapter 2 Installation ........................................................................... 38

About the Backup Exec installation process and licensing options

........................................................................................... 39
Backup Exec preinstallation checklist ............................................... 41
Running the Environment Check before installing or upgrading Backup
Exec .................................................................................... 42
Microsoft SQL Server Express Edition components installed with
Backup Exec ......................................................................... 45
System requirements for Backup Exec .............................................. 46
Installing Backup Exec by using the Installation Wizard ........................ 48
Installing additional agents and features to the local Backup Exec
server .................................................................................. 58
Push-installing Backup Exec to remote computers .............................. 60
Methods for installing the Agent for Windows ..................................... 68
Push-installing the Agent for Windows to remote computers ............ 68
Installing updates to the Agent for Windows on remote computers
..................................................................................... 74
Installing the Agent for Windows in an Active Directory network
..................................................................................... 75
Using a command prompt to install the Agent for Windows on a
remote computer .............................................................. 79
Using a command script to install the Agent for Windows ................ 82
Installing the Remote Administrator ................................................. 83
Installing the Remote Administrator using the command line ........... 85
Running the Remote Administrator ............................................. 87
Installing Backup Exec using the command line (silent mode) ................ 89
Command line switches for silent mode installation of Backup
Exec .............................................................................. 90
Creating and using installation parameter files .............................. 97
 Contents 8

About the installation log ................................................................ 98

Viewing the Installation Summary Report .......................................... 99
Repairing Backup Exec ................................................................. 99
Updating Backup Exec with Veritas Update ...................................... 100
Application settings for Veritas Update ...................................... 102
Viewing installed updates ............................................................. 103
Uninstalling Backup Exec updates .................................................. 104
Viewing license information ........................................................... 104
Backup Exec license contract information ........................................ 105
Updating expired license contracts ........................................... 105
Managing license contract customer numbers ............................ 106
About upgrading to Backup Exec ................................................... 107
Upgrade checklist for Backup Exec .......................................... 109
Using the Migration Report to determine how existing jobs changed
after an upgrade from a previous version of Backup Exec
.................................................................................... 110
Post-installation tasks .................................................................. 111
Uninstalling Backup Exec ............................................................. 112
Uninstalling Backup Exec using the command line ............................. 113
Uninstalling Backup Exec features from the local Backup Exec server
.......................................................................................... 113

Chapter 3 Getting Started ................................................................. 115

About the Backup Exec Administration Console ................................ 115

Displaying the version information for Backup Exec ........................... 118
Locking and unlocking the Backup Exec Console .............................. 118
How to sort, filter, and copy information on the Backup Exec
Administration Console .......................................................... 119
Customizing views on the Backup Exec Administration Console ........... 121
Configuring the Home tab ............................................................. 122
Configuring the RSS Reader ......................................................... 130
Creating a disaster preparation plan (DPP) ...................................... 131
Getting started with backups ......................................................... 133

Chapter 4 Backups .............................................................................. 135

How to prepare for your first backup with Backup Exec ....................... 137
Improving backup performance in Backup Exec ................................ 138
Troubleshooting backup performance ............................................. 141
Required user rights for backup jobs ............................................... 145
About the list of servers on the Backup and Restore tab ..................... 146
Adding servers that you want to back up to the list of servers on the
Backup and Restore tab ......................................................... 147
 Contents 9

Removing servers from the list of servers on the Backup and Restore
tab ..................................................................................... 148
Creating a server group ............................................................... 148
Hiding or viewing server groups on the Backup and Restore tab ........... 149
Adding servers to a server group ................................................... 150
Removing servers from a server group ............................................ 150
Editing a server group .................................................................. 151
Moving servers to the Retired Servers server group ........................... 151
Moving retired servers back to the All Servers server group ................. 152
Removing server groups from Backup Exec ..................................... 153
Backing up data ......................................................................... 153
How Backup Exec backs up and restores volumes that are enabled
for deduplication in Windows ............................................. 164
How Backup Exec backs up and restores Microsoft Virtual Hard
Disk (vhd) files ............................................................... 164
About selecting data to back up .................................................... 165
Changing the order in which backup sources are backed up ................ 171
Excluding files from backups ......................................................... 174
Including specific files with a backup job's backup selections ............... 177
About backing up critical system components ................................... 179
Backup Exec Shadow Copy Components file system ......................... 182
Backup methods in Backup Exec ................................................... 183
Configuring backup methods for backup jobs ................................... 191
How Backup Exec determines if a file has been backed up .................. 193
Configuring Backup Exec to automatically delete files after a backup
.......................................................................................... 197
Configuring network options for backup jobs ..................................... 198
Running the next scheduled backup job before its scheduled time
.......................................................................................... 199
Editing backup definitions ............................................................. 200
Testing credentials for backup sources ............................................ 206
Replacing the credentials for a backup source .................................. 207
Creating new credentials for a backup source ................................... 208
Deleting retired or unused backup sources from the Credentials pane
.......................................................................................... 210
How job scheduling works in Backup Exec ....................................... 210
Including a specific date in the schedule for a backup job .................... 212
Preventing backup jobs from running on a specific date ...................... 213
Viewing all scheduled backup jobs on a calendar .............................. 214
Adding a stage to a backup definition .............................................. 214
Editing a stage ........................................................................... 216
Duplicating backup sets or a job history manually .............................. 216
Running a test run job manually ..................................................... 221
 Contents 10

Verifying backed up data manually ................................................. 222

Copying data from a virtual tape library to a physical tape device using
DirectCopy to tape ................................................................ 224

Chapter 5 Restores ............................................................................. 226

Methods for restoring data in Backup Exec ...................................... 227

Searching for data to restore ......................................................... 229
Restoring data from a server, a backup set, a backup job, or a storage
device ................................................................................ 229
Restoring file system data ............................................................ 233
Performing a complete online restore of a Microsoft Windows computer
.......................................................................................... 234
Restoring System State ............................................................... 235
Installing a new Windows Server domain controller into an existing
domain by using a redirected restore ........................................ 238
Restoring Backup Exec Shadow Copy Components .......................... 240
Restoring utility partitions or Unified Extensible Firmware Interface
system partitions .................................................................. 240
About restoring encrypted data ...................................................... 241
About restoring NetWare SMS volume backups to non-SMS volumes
with Backup Exec ................................................................. 242
Canceling a restore job ................................................................ 242
How Backup Exec catalogs work ................................................... 242
Configuring default options for catalogs ..................................... 243
Moving the Backup Exec catalogs to a new directory ................... 246
Cataloging backup sets ................................................................ 247

Chapter 6 Job management and monitoring ............................... 249

How to monitor and manage jobs in Backup Exec ............................. 249

About the Job Monitor .................................................................. 251
Viewing job activity details for active jobs ................................... 253
Canceling an active job .......................................................... 253
Holding jobs ........................................................................ 254
Removing the hold on jobs ..................................................... 255
Holding the job queue ............................................................ 256
Removing the hold on the job queue ......................................... 257
Running a scheduled job immediately ....................................... 258
Changing the priority for a scheduled job ................................... 258
Deleting scheduled jobs ......................................................... 260
Retrying only failed resources ................................................. 260
Run backup job with debugging enabled ................................... 261
About the Job History .................................................................. 262
 Contents 11

Viewing the history of a job ..................................................... 263

Deleting a job from the Job History ........................................... 263
Running a job from the Job History ........................................... 264
Retrying only failed resources from the Job History ...................... 265
Run backup job with debugging enabled from the Job History
.................................................................................... 266
Viewing the job log ..................................................................... 267
Finding text in the job log ........................................................ 267
Printing the job log ................................................................ 269
Saving the job log ................................................................. 269
Linking from the job log to the Veritas Technical Support website
.................................................................................... 270
How to use job logs with vertical applications .............................. 270
Configuring default job log options ............................................ 271
Error-handling rules for failed or canceled jobs .................................. 272
Creating a custom error-handling rule ....................................... 273
Enabling or disabling error-handling rules .................................. 274
Deleting a custom error-handling rule ........................................ 274
Enabling an error-handling rule for a failed job ............................ 275
Custom error-handling rule for recovered jobs ............................ 275
About the cluster failover error-handling rule ............................... 276
List of job statuses in Backup Exec ................................................. 277
Setting job status and recovery options ........................................... 282

Chapter 7 Alerts and notifications ................................................... 285

Alerts and notifications in Backup Exec ........................................... 286
Where to find alerts in Backup Exec ............................................... 287
Enabling active alerts and alert history to display on the Home tab
.......................................................................................... 289
Active alerts properties .......................................................... 290
Viewing the alert history for a server or a storage device ..................... 291
Deleting an alert from alert history .................................................. 291
Copying alert text to a document or email ........................................ 292
Filtering alerts ............................................................................ 292
Viewing the job log from an alert .................................................... 293
Responding to active alerts ........................................................... 293
Clearing all informational alerts manually ......................................... 294
Setting up notification for alerts ...................................................... 294
Configuring email or text message notification for alerts ...................... 295
Adding recipients for notification .................................................... 297
Adding a recipient group for alert notifications ................................... 299
Removing a recipient from a group ........................................... 300
 Contents 12

Disabling email or text message alert notification for a recipient ............ 300
Editing recipient notification properties ............................................ 301
Deleting recipients ...................................................................... 301
Configuring alert categories .......................................................... 302
Assigning recipients to receive notifications for specific alert categories
.......................................................................................... 304
Sending a notification when a job completes .................................... 304
Notification options for jobs ..................................................... 305
Disabling notifications for a specific alert category ............................. 305
Configuring default alert settings .................................................... 306
Enabling or disabling pop-up alerts ................................................. 307
SNMP traps for Backup Exec alerts ................................................ 308
Installing and configuring the SNMP system service ..................... 310
Installing the Windows Management Instrumentation performance
counter provider ............................................................. 311
Installing the Windows Management Instrumentation provider for
SNMP .......................................................................... 311
Uninstalling the Windows Management Instrumentation
performance counter provider ........................................... 312
Uninstalling the Windows Management Instrumentation provider
for SNMP ...................................................................... 312

Chapter 8 Disk-based and network-based storage ................... 313

Features and types of disk-based storage and network-based storage

.......................................................................................... 313
Storage trending statuses for disk storage and virtual disks ................. 315
Setting low disk space thresholds on disk-based storage .................... 316
Configuring disk storage ............................................................... 317
Changing the location of a disk storage device ............................ 320
Editing disk storage properties ................................................. 321
How to restore data from a reattached or reinserted disk-based storage
device ................................................................................ 327
Configuring disk cartridge storage .................................................. 328
Editing disk cartridge properties ............................................... 329
Editing disk cartridge media properties ...................................... 333
How data lifecycle management (DLM) deletes expired backup sets
on disk-based storage ........................................................... 335
Backup sets .............................................................................. 341
Changing the expiration date of backup sets on disk-based storage
.................................................................................... 344
Retaining backup sets on disk-based storage to prevent them
from expiring .................................................................. 345
 Contents 13

Releasing retained backup sets on disk-based storage ................. 346

Viewing the contents or properties of backup sets ....................... 347

Chapter 9 Cloud-based storage devices ...................................... 349

About cloud-based storage devices ................................................ 349

Amazon S3 cloud-based storage ................................................... 350
Requirements for configuring an Amazon S3 cloud-based storage
device .......................................................................... 350
Configuring storage for Amazon cloud storage ............................ 351
Google cloud-based storage ......................................................... 353
Requirements for configuring a Google cloud-based storage device
.................................................................................... 353
Configuring storage for Google cloud storage ............................. 354
Microsoft Azure cloud-based storage .............................................. 356
Requirements for configuring a Microsoft Azure cloud-based
storage device ............................................................... 356
Configuring storage for Microsoft Azure cloud storage .................. 357
Private cloud-based storage ......................................................... 358
Requirements for configuring a private cloud-based storage device
.................................................................................... 358
Creating a cloud instance for a private cloud .............................. 360
Configuring storage for a private cloud-based storage device
.................................................................................... 360
Viewing and editing existing cloud instances for a private cloud
.................................................................................... 362
Deleting a cloud instance for a private cloud ............................... 362
About S3-Compatible Cloud Storage .............................................. 363
Configuring S3-Compatible Cloud Storage with Backup Exec
.................................................................................... 364
Notes for cloud-based storage devices ............................................ 365
Editing the properties of a cloud-based storage device ....................... 366
Best practices for using cloud-based storage .................................... 368
Changing default cloud storage settings .......................................... 369
About the Backup Exec™ CloudConnect Optimizer ........................... 370
Configuring the Backup Exec™ CloudConnect Optimizer .............. 371

Chapter 10 Legacy backup-to-disk folders ..................................... 374

Legacy backup-to-disk folders ...................................................... 374
Changing the name or description of a legacy backup-to-disk
folder ........................................................................... 375
Changing the buffered read setting for a legacy backup-to-disk
folder ........................................................................... 375
 Contents 14

Changing the location of a legacy backup-to-disk folder ................ 376

Recreating a legacy backup-to-disk folder and its contents ............ 377
Restoring data from a legacy backup-to-disk folder ...................... 377

Chapter 11 Tape storage ..................................................................... 380

Support for tape drives and robotic libraries ...................................... 381

Adding or replacing devices with the Hot-swappable Device Wizard
.......................................................................................... 381
Installing tape device drivers ........................................................ 382
Editing tape drive properties .......................................................... 384
Viewing tape drive statistics .......................................................... 389
Robotic libraries in Backup Exec .................................................... 389
Requirements for setting up robotic library hardware .................... 390
Inventorying robotic libraries when Backup Exec services start
.................................................................................... 391
Configuring barcode rules for a robotic library ............................ 391
Initializing a robotic library when the Backup Exec service starts
.................................................................................... 395
Defining a cleaning slot ......................................................... 396
Editing robotic library properties ............................................... 396
Creating robotic library partitions .................................................... 397
Adding or removing tape drives in a robotic library partition ........... 398
Reassigning a slot base number for robotic libraries ..................... 399
Editing robotic library slot properties ......................................... 399
Removing or reconfiguring robotic library partitions ...................... 400
Managing tapes ......................................................................... 402
Default media sets ................................................................ 402
Overwrite protection periods and append periods in media sets
.................................................................................... 406
Creating media sets for tapes .................................................. 410
Changing the overwrite protection period or the append period for
a media set ................................................................... 413
Changing the name and description of a media set ...................... 415
Changing the media vault or vaulting periods for a media set
.................................................................................... 415
Deleting a media set .............................................................. 416
Renaming a media set ........................................................... 416
Media overwrite protection levels for tape media ......................... 416
Overwriting allocated or imported tape media ............................. 417
How Backup Exec searches for overwritable media in tape drives
.................................................................................... 417
Viewing tapes that are used by a job ......................................... 420
 Contents 15

Labeling tape media .................................................................... 420

About labeling imported tape media ......................................... 422
How barcode labels become media labels for tapes ..................... 422
Renaming a tape media label ................................................. 423
How WORM media is used in Backup Exec ..................................... 423
Default media vaults .................................................................... 424
Changing the name or description of a media vault ...................... 425
Creating media vault rules to move tape media to and from media
vaults ........................................................................... 426
Updating the tape media location in media vaults ........................ 427
Deleting a media vault ........................................................... 427
Moving tape media to a vault ................................................... 428
Retiring damaged tape media ....................................................... 428
Deleting tape media .................................................................... 429
Erasing tape or disk cartridge media ............................................... 429
About cataloging tape or disk cartridge media that contains encrypted
backup sets ......................................................................... 431
Associating tape media with a media set ......................................... 431
Editing tape media properties ........................................................ 432
Tape media rotation strategies ....................................................... 434

Chapter 12 Storage device pools ...................................................... 438

Creating storage device pools ....................................................... 438

Specifying a default selection method for a device in a storage device
pool ................................................................................... 441
Viewing jobs, job histories, and active alerts for a storage device pool
.......................................................................................... 441
Adding or removing devices in a storage device pool ......................... 442

Chapter 13 Storage operations .......................................................... 443

About storage operation jobs ......................................................... 444

Storage tab overview in Backup Exec ............................................. 445
Using the Configure Storage wizard ................................................ 448
Viewing details for multiple storage devices ...................................... 450
Sending a notification when a scheduled storage operation job
completes ........................................................................... 451
Scheduling a storage operation job ................................................ 451
Editing global settings for storage ................................................... 458
Sharing storage devices ............................................................... 467
Deleting a storage device ............................................................. 468
Changing the state of a storage device to online ............................... 469
Renaming a storage device .......................................................... 469
 Contents 16

Viewing jobs, job histories, backup sets, and active alerts for storage
devices ............................................................................... 470
Cataloging a storage device .......................................................... 470
Scanning a storage device ........................................................... 471
Inventorying a storage device ........................................................ 472
Inventorying and cataloging a storage device ................................... 473
Pausing and unpausing a storage device ......................................... 473
Disabling and enabling a storage device .......................................... 474
Initializing a robotic library ............................................................ 474
Formatting a tape as a WORM tape ................................................ 475
Retensioning a tape .................................................................... 475
Formatting a tape in a tape drive .................................................... 475
Ejecting media from a disk cartridge or tape drive .............................. 476
Cleaning a robotic library drive ...................................................... 477
Importing media to Backup Exec ................................................... 478
Exporting media and expired media ................................................ 485
Locking and unlocking the robotic library’s front portal ........................ 488
Backup Exec server and storage device states ................................. 494
Viewing the disk storage lockdown status ........................................ 497

Chapter 14 Conversion to virtual machines ................................... 499

How conversion of physical computers to virtual machines works in

Backup Exec ....................................................................... 499
Requirements for conversion to virtual machine jobs .......................... 507
Converting to a virtual machine simultaneously with a backup job ......... 508
Converting to a virtual machine after a backup job ............................. 515
Adding a conversion to virtual machine stage to a backup job .............. 523
Converting to a virtual machine from a point in time ........................... 530
Creating a one-time conversion to a virtual machine .......................... 532
Setting default options for conversion to virtual machine jobs ............... 539

Chapter 15 Configuration and settings ............................................ 543

Changing default backup job settings .............................................. 545

Configuring schedules for backup jobs ............................................ 549
Configuring storage options for backup jobs ..................................... 556
Configuring automatic test run jobs for backup jobs ........................... 562
Configuring automatic verify operations for backup jobs ...................... 563
Configuring Instant GRT and full catalog options to improve backup
performance for GRT-enabled jobs ........................................... 565
Configuring Advanced Open File options for backup jobs .................... 572
Configuring checkpoint restart ....................................................... 574
Configuring pre/post commands for backup jobs ............................... 577
 Contents 17

Configuring file and folder options for backup jobs ............................. 581
Setting default schedule options for rule-based jobs and run now jobs
.......................................................................................... 589
Excluding dates from the backup schedule for all backups .................. 592
Removing dates from the list of excluded dates ................................. 594
Exporting a list of dates that are excluded from all backups to another
server ................................................................................. 595
Changing the default preferences .................................................. 595
Configuring the default setting for backing up multiple servers or
applications ......................................................................... 597
Configuring database maintenance and security ............................... 597
Exporting the Backup Exec Database encryption key ......................... 601
Refreshing Backup Exec Database encryption keys ........................... 603
Configuring encryption for the connection to the Backup Exec Database
.......................................................................................... 604
Scheduling Backup Exec to check logon accounts ............................. 608
Configuring Backup Exec to discover data to back up ......................... 609
Adding discovered servers to the list of servers in Backup Exec ........... 611
Backup networks ........................................................................ 612
Changing network and security options for Backup Exec ..................... 614
Disabling disk storage lockdown .............................................. 619
Using Backup Exec with firewalls ................................................... 620
Backup Exec ports ................................................................ 621
Backup Exec listening ports .................................................... 623
About enabling a SQL instance behind a firewall ......................... 624
Using encryption with Backup Exec ................................................ 624
Encryption key management ......................................................... 627
Creating encryption keys .............................................................. 628
Replacing an encryption key ......................................................... 629
Deleting encryption keys .............................................................. 631
Granular Recovery Technology ...................................................... 632
Setting default Granular Recovery Technology (GRT) options .............. 639
DBA-initiated job templates ........................................................... 640
Creating DBA-initiated job templates ............................................... 641
Editing DBA-inititated job templates ................................................ 642
Deleting DBA-initiated job templates ............................................... 642
Storage options for DBA-initiated jobs ....................................... 643
General options for DBA-initiated jobs ....................................... 647
Network options for DBA-initiated jobs ...................................... 647
Duplicate job settings for DBA-initiated jobs ............................... 648
Configuring settings for Veritas™ Information Map ............................. 652
Backup Exec logon accounts ........................................................ 655
Creating a Backup Exec logon account ..................................... 658
 Contents 18

Editing a Backup Exec logon account ....................................... 659

Changing the password for a Backup Exec logon account ............. 661
Replacing a Backup Exec logon account ................................... 662
Deleting a Backup Exec logon account ...................................... 662
Changing your default Backup Exec logon account ...................... 664
Creating a new Backup Exec System Logon Account ................... 664
Copying logon account information to another Backup Exec server
.................................................................................... 665
Testing logon accounts .......................................................... 666
Starting and stopping Backup Exec services .................................... 667
Changing the credentials for a service account ................................. 667
Changing startup options for Backup Exec services ........................... 669
Configuring audit logs .................................................................. 670
Viewing the audit log ................................................................... 671
Removing entries from the audit log ................................................ 672
Saving an audit log to a text file ..................................................... 672
Copying configuration settings to another Backup Exec server ............. 672
Viewing server properties ............................................................. 673
Configuring default backup settings ................................................ 674

Chapter 16 Reports ............................................................................... 680

Reports in Backup Exec ............................................................... 680

Running a report now .................................................................. 682
Scheduling a report ..................................................................... 682
Creating a custom report .............................................................. 684
Adding or removing fields on a custom report ............................. 689
Changing filters for a custom report .......................................... 689
Changing the way data is grouped or sorted in a custom report
.................................................................................... 691
Changing graph options in custom reports ................................. 692
Previewing custom reports ...................................................... 693
Copying a custom report ........................................................ 693
Saving a report ........................................................................... 693
Printing a report from the Backup Exec Report Viewer ........................ 694
Viewing completed reports ............................................................ 695
Editing a report ........................................................................... 695
Re-running a completed report ...................................................... 695
Deleting a report ........................................................................ 696
Setting defaults for standard and custom reports ............................... 696
Viewing report properties .............................................................. 697
List of Backup Exec standard reports .............................................. 698
Alert History report ................................................................ 702
 Contents 19

Alert History By Backup Exec Server report ................................ 703

Audit Log report .................................................................... 704
Backup Job Success Rate report ............................................. 704
Backup Recommendations report ............................................ 705
Backup Resource Success Rate report ..................................... 705
Backup Sets by Media Set report ............................................. 706
Backup Size By Resource report .............................................. 706
Cloud Storage Summary report ............................................... 707
Daily Device Utilization report .................................................. 708
Deduplication Device Summary report ...................................... 708
Deduplication Summary report ................................................ 709
Device Summary report ......................................................... 710
Disk Storage Summary report ................................................. 711
Error-Handling Rules report .................................................... 712
Event Recipients report .......................................................... 713
Failed Backup Jobs report ...................................................... 713
Jobs Summary report ............................................................ 714
Managed Backup Exec Servers report ...................................... 716
Media Audit report ................................................................ 717
Media Errors report ............................................................... 718
Media Required for Recovery report ......................................... 718
Media Summary report .......................................................... 719
Media Vault Contents report .................................................... 720
Move Media to Vault report ..................................................... 720
Operations Overview report .................................................... 721
Overnight Summary report ...................................................... 723
Problem Files report .............................................................. 724
Recently Written Media report ................................................. 725
Recovery Ready Validation Summary ....................................... 725
Resource Protected Recently report ......................................... 726
Resource Risk Assessment report ............................................ 727
Restore Set Details by Resource report ..................................... 728
Retrieve Media from Vault report .............................................. 729
Robotic Library Inventory report ............................................... 729
Scheduled Server Workload report ........................................... 730
Scratch Media Availability report .............................................. 731
Test Run Results report .......................................................... 732

Chapter 17 Instant Cloud Recovery ................................................. 733

About Instant Cloud Recovery ....................................................... 734

Instant Cloud Recovery tab overview in Backup Exec ......................... 735
 Contents 20

Requirements to configure Instant cloud recovery in Backup Exec

.......................................................................................... 737
Preconfigurations to be completed in the Azure portal ....................... 738
Prepare VMware or Hyper-V infrastructure ................................. 738
How to configure Azure resources .................................................. 738
How to view error details .............................................................. 741
How to view configuration details ................................................... 742
How to view virtual machine details ................................................ 742
How to manually refresh the view of virtual machines ......................... 743
How to enable replication for virtual machines .................................. 743
How to manage replication for virtual machines ................................. 745
How to manage failover for a virtual machine .................................... 746
How to change the Subscription or Recovery Services Vault ................ 746
How to prepare a new infrastructure ............................................... 747
How to remove a configured Azure resource from Backup Exec ........... 747
How to renew the Backup Exec certificate ........................................ 748

Chapter 18 GDPR Guard ..................................................................... 750

About GDPR Guard .................................................................... 750
Backup Exec Management Command Line (BEMCLI) commands for
import and export .................................................................. 752
Supported types of backed up data ................................................ 754
How to block access to backed up items .......................................... 755
Restoring blocked items ............................................................... 756
Best practices for blocking access to backed up items with GDPR
Guard ................................................................................. 757

Chapter 19 Troubleshooting Backup Exec ..................................... 759

Troubleshooting hardware-related issues in Backup Exec ................... 760

Troubleshooting robotic libraries and tape drives ............................... 762
How to get more information about alerts and error messages ............. 767
Troubleshooting backup issues in Backup Exec ................................ 767
Troubleshooting failed components in the SAN ................................ 770
Troubleshooting offline storage devices in a SAN ....................... 770
Finding hardware errors in a SAN ............................................ 772
Resetting the SAN ................................................................ 773
Bringing storage devices online after an unsafe device removal
event in a SAN ............................................................... 774
Troubleshooting installation issues in Backup Exec ............................ 774
Troubleshooting blocked access to backed up items with GDPR Guard
.......................................................................................... 775
Troubleshooting Instant Cloud Recovery issues in Backup Exec ........... 777
 Contents 21

How to improve Backup Exec's performance .................................... 777

Accessing Veritas Online .............................................................. 778
Searching the Veritas Knowledge Base ........................................... 778
Contacting Backup Exec Technical Support ..................................... 779
Using Remote Assistance ............................................................. 779
Managing your Backup Exec support cases ..................................... 780
About Backup Exec diagnostic tools ............................................... 780
Running the Veritas QuickAssist Help Tool ...................................... 781
Generating a diagnostic file for troubleshooting Backup Exec ............... 781
Command line switches for a diagnostic file ............................... 782
Running the begather utility to troubleshoot Backup Exec components
on Linux servers ................................................................... 785
Using the Backup Exec Debug Monitor for troubleshooting .................. 786
About the Backup Exec debug tool ................................................. 786

Chapter 20 Using Backup Exec in cluster environments ........... 787

About Backup Exec and clusters .................................................... 788
Requirements for clustering Backup Exec in a Microsoft Cluster Server
environment ........................................................................ 788
How Backup Exec works in a Microsoft Cluster Server environment
.......................................................................................... 789
Requirements for installing Backup Exec on a Microsoft Cluster Server
.......................................................................................... 790
Installing Backup Exec on a Microsoft Cluster Server ........................ 791
Upgrading Backup Exec on a Microsoft cluster ................................. 792
Installing additional Backup Exec features on a Microsoft cluster ......... 793
Uninstalling Backup Exec from a Microsoft cluster ............................. 794
Creating storage device pools for Microsoft Cluster Servers ................ 794
Specifying a different failover node ................................................. 795
Designating a new central administration server in a Microsoft Cluster
Server ................................................................................ 796
Configurations for Backup Exec and Microsoft Cluster Servers ............. 797
Two-node cluster with locally attached storage devices ................. 798
Two-node cluster with tape devices on a shared SCSI bus ............ 799
Configuring a shared SCSI bus for tape devices .......................... 800
Multi-node clusters on a fibre channel SAN with the Central Admin
Server feature ................................................................ 802
Using the Central Admin Server feature with Microsoft clusters and a
storage area network ............................................................. 804
About backing up Microsoft Cluster Servers ..................................... 805
About restoring data to a Microsoft cluster ....................................... 805
Disaster recovery of a cluster ........................................................ 806
 Contents 22

Using Simplified Disaster Recovery to prepare for disaster recovery

of a cluster .................................................................... 807
Recovering nodes on the cluster using Simplified Disaster
Recovery ...................................................................... 807
Recovering Backup Exec on a Microsoft cluster using Simplified
Disaster Recovery .......................................................... 808
Recovering the entire cluster using a manual disaster recovery
procedure ..................................................................... 808
Restoring the Microsoft Cluster Server data files ............................... 809
Recovering Backup Exec in a Microsoft cluster ................................. 810
Manually joining two cluster disk groups and resynchronizing volumes
.......................................................................................... 810
Troubleshooting clusters .............................................................. 811

Chapter 21 Simplified Disaster Recovery ....................................... 812

About Simplified Disaster Recovery ................................................ 812

Requirements for using Simplified Disaster Recovery ........................ 813
Preparing computers for use with Simplified Disaster Recovery ............ 816
How to ensure that backups are enabled for Simplified Disaster
Recovery ............................................................................ 820
How Simplified Disaster Recovery uses disaster recovery information
files .................................................................................... 822
Setting or changing the alternate location for the disaster recovery
information file ..................................................................... 824
Changing the default path for the disaster recovery information
files .............................................................................. 825
Disaster recovery information file data paths .............................. 825
Creating a Simplified Disaster Recovery disk image ........................... 827
Contents of the Simplified Disaster Recovery disk image .............. 846
User scenarios when a user starts the Create Recovery Disk
Wizard .......................................................................... 848
Preparing to recover from a disaster by using Simplified Disaster
Recovery ............................................................................ 850
Hardware replacement during disaster recovery .......................... 851
Prepare to recover IBM computers with Simplified Disaster
Recovery ...................................................................... 852
Recovering a computer with Simplified Disaster Recovery ................... 853
Recovery notes for using Simplified Disaster Recovery with storage
pools and storage spaces ................................................. 859
Recovery notes for using Simplified Disaster Recovery with
Exchange, SQL, SharePoint, CAS, Hyper-V hosts, and the
Deduplication feature ...................................................... 863
 Contents 23

Advanced Disk Configuration on the Recover This Computer Wizard

.......................................................................................... 864
Performing manual disaster recovery .............................................. 867
Performing manual disaster recovery of a local Backup Exec server
on a Windows computer ................................................... 868
Performing manual disaster recovery of a remote Backup Exec
server or remote agent on a Windows computer .................... 873

Chapter 22 Integration with Veritas™ Information Map .............. 878

About Veritas™ Information Map .................................................... 878
How Backup Exec works with Veritas™ Information Map .................... 879
Requirements for integration with Veritas™ Information Map ............... 879
How Backup Exec integrates with Veritas™ Information Map ............... 880
Supported data sources for integration with Veritas™ Information Map
.......................................................................................... 883
Best practices for integration with Veritas™ Information Map ............... 883
Troubleshooting tips for integration with Veritas™ Information Map
.......................................................................................... 884
Limitation for integration with Veritas™ Information Map ..................... 887

Chapter 23 Integration with Veritas SaaS Backup ....................... 888

About integration with Veritas SaaS Backup ..................................... 888

Connecting to Veritas SaaS Backup ............................................... 889
Preconfigurations in Veritas SaaS Backup ....................................... 890
Managing Veritas SaaS Backup accounts ........................................ 890
Adding a new Veritas SaaS Backup account .................................... 891
Editing a Veritas SaaS Backup account ........................................... 891
Deleting a Veritas SaaS Backup account ......................................... 892
Generating a report to view Veritas SaaS Backup data ....................... 892

Chapter 24 Forever Incremental Backup ........................................ 894

About Forever Incremental Backup ................................................. 894

Differences between the traditional and the forever incremental backups
of virtual machines ................................................................ 895
How do forever incremental backups work ....................................... 896
Backing up virtual machines using forever incremental backups ........... 900
CAS-MBES scenarios in forever incremental backups ........................ 901
Notes for forever incremental backups ............................................ 901
Recommendations for forever incremental backups ........................... 901
Limitation of forever incremental backups ........................................ 902
 Contents 24

Appendix A Backup Exec Agent for Windows ................................ 903

About the Agent for Windows ........................................................ 903
Requirements for the Agent for Windows ......................................... 904
Stopping and starting the Agent for Windows .................................... 905
Establishing a trust between the Backup Exec server and a remote
computer ............................................................................ 905
About the Backup Exec Agent Utility for Windows .............................. 906
Starting the Backup Exec Agent Utility ...................................... 907
Viewing the activity status of the remote computer in the Backup
Exec Agent Utility ........................................................... 907
Viewing the activity status of the remote computer from the system
tray .............................................................................. 908
Starting the Backup Exec Agent Utility automatically on the remote
computer ...................................................................... 909
Setting the refresh interval on the remote computer ..................... 909
About publishing the Agent for Windows to Backup Exec servers
.................................................................................... 910
Adding Backup Exec servers that the Agent for Windows can
publish to ...................................................................... 910
Editing Backup Exec server information that the Agent for Windows
publishes to ................................................................... 911
Removing Backup Exec servers that the Agent for Windows can
publish to ...................................................................... 912
Configuring database access for Oracle operations ..................... 912
Removing a security certificate for a Backup Exec server that has
a trust with the Agent for Windows ..................................... 915
Using the Backup Exec Agent Utility Command Line Applet ................. 915
Backup Exec Agent Utility Command Line Applet switches .................. 916

Appendix B Backup Exec Deduplication Feature .......................... 920

About the Deduplication feature ..................................................... 921
Deduplication methods for Backup Exec agents ................................ 923
Requirements for the Deduplication feature ...................................... 924
Installing the Deduplication feature ................................................. 929
Converting an older version of Deduplication Storage to a newer version
.......................................................................................... 930
Configuring an OpenStorage device ............................................... 932
Editing the properties of an OpenStorage device ............................... 934
Specifying a Backup Exec server that has proximity to a shared
OpenStorage device ............................................................. 936
Creating or importing deduplication disk storage ............................... 937
Editing the properties of a deduplication disk storage device .......... 939
 Contents 25

Changing the password for the logon account for deduplication

disk storage ................................................................... 944
Selecting storage devices for direct access sharing ........................... 945
Editing server properties for direct access .................................. 946
Changing the location of a deduplication disk storage device ............... 947
Sharing a deduplication device between multiple Backup Exec servers
.......................................................................................... 949
How to use client-side deduplication ............................................... 949
How to set up backup jobs for deduplication ..................................... 950
Using optimized duplication to copy deduplicated data between
OpenStorage devices or deduplication disk storage devices .......... 951
Copying deduplicated data to tapes ................................................ 954
Using deduplication with encryption ................................................ 954
Restoring a deduplication disk storage device or deduplicated data
.......................................................................................... 955
Disaster recovery of deduplication disk storage devices ..................... 955
Disaster recovery of OpenStorage devices ....................................... 956

Appendix C Backup Exec Agent for VMware ................................. 958

About the Agent for VMware ......................................................... 959

Requirements for using the Agent for VMware .................................. 959
Using the Agent for VMware with Windows Server 2016 or later ........... 961
About installing the Agent for VMware ............................................. 961
Adding VMware vCenter Servers and ESX/ESXi hosts to the list of
servers on the Backup and Restore tab ..................................... 962
Viewing details about VMware resources ......................................... 963
Installing the Agent for Windows on VMware virtual machines .............. 964
Push-installing the Agent for Windows to VMware virtual machines
.......................................................................................... 965
About establishing trust for a vCenter/ESX(i) server ........................... 966
Establishing trust for a vCenter/ESX(i) server ............................. 966
Recommendations for when to use virtual-based backup and
agent-based backup .............................................................. 967
Backing up VMware virtual machines .............................................. 968
Setting default backup options for virtual machines ...................... 975
How Backup Exec automatically backs up new VMware virtual
machines during a backup job .......................................... 979
Using Granular Recovery Technology (GRT) with the Agent for
VMware ........................................................................ 979
How cataloging works with VMware virtual machine backups
.................................................................................... 983
Restoring VMware virtual machines and vmdk files ............................ 984
 Contents 26

About instant recovery of a VMware virtual machine .......................... 992

Requirements for instant recovery of a VMware virtual machine
.................................................................................... 995
Notes about instant recovery of a VMware virtual machine ............ 995
Best Practices for instant recovery of a VMware virtual machine
.................................................................................... 996
Creating an instant recovery job for a VMware virtual machine
.................................................................................... 997
Removing an instantly recovered VMware virtual machine ............ 999
Troubleshooting the Agent for VMware .......................................... 1000
About Recovery Ready for VMware virtual machines ........................ 1001
Requirements for validating a VMware virtual machine for recovery
.................................................................................. 1005
Notes about validating a VMware virtual machine for recovery
.................................................................................. 1005
Best Practices for validating VMware virtual machine for recovery
.................................................................................. 1006
Creating a validate virtual machine for recovery job .................... 1006

Appendix D Backup Exec Agent for Microsoft Hyper-V ............. 1010

About the Agent for Microsoft Hyper-V ........................................... 1011
Requirements for using the Agent for Microsoft Hyper-V ................... 1013
About installing the Agent for Microsoft Hyper-V .............................. 1015
Notes about using the Agent for Hyper-V ...................................... 1016
Disk space optimization with the Agent for Hyper-V .......................... 1018
Adding a Hyper-V host to the list of servers on the Backup and Restore
tab ................................................................................... 1018
Viewing details about Hyper-V resources ....................................... 1019
Installing the Agent for Windows on Hyper-V virtual machines ............ 1020
Push-installing the Agent for Windows to Hyper-V virtual machines
........................................................................................ 1021
Backing up Microsoft Hyper-V virtual machines ............................... 1022
Setting default backup options for Hyper-V ............................... 1030
How Backup Exec automatically protects new virtual machines
during a backup job ....................................................... 1032
Using Granular Recovery Technology (GRT) with the Agent for
Hyper-V ...................................................................... 1033
About backing up and restoring highly available Hyper-V virtual
machines .................................................................... 1036
About backing up VMs hosted on SMB/Scale out File Server ....... 1037
How cataloging works with Hyper-V virtual machine backups
.................................................................................. 1037
 Contents 27

Restoring Microsoft Hyper-V virtual machines ................................. 1039

About instant recovery of a Hyper-V virtual machine ......................... 1043
Requirements for instant recovery of a Hyper-V virtual machine
.................................................................................. 1047
Notes about instant recovery of a Hyper-V virtual machine .......... 1048
Creating an instant recovery job for a Hyper-V virtual machine
.................................................................................. 1049
Post-instant recovery tasks .................................................. 1051
About removing an instantly recovered Hyper-V virtual machine
.................................................................................. 1052
Removing an instantly recovered Hyper-V virtual machine ........... 1053
Best practices for instant recovery of a Hyper-V virtual machine
.................................................................................. 1054
About Recovery Ready for Hyper-V virtual machines ........................ 1055
Requirements for validating a Hyper-V virtual machine for recovery
.................................................................................. 1059
Notes about validating a Hyper-V virtual machine for recovery
.................................................................................. 1059
Best practices about validating a Hyper-V virtual machine for
recovery ...................................................................... 1060
Creating a validate virtual machine for recovery ........................ 1060
Troubleshooting issues with Backup Exec Agent for Microsoft Hyper-V
........................................................................................ 1062

Appendix E Backup Exec Agent for Microsoft SQL Server

........................................................................................ 1064

About the Agent for Microsoft SQL Server ...................................... 1064

Requirements for using the SQL Agent .......................................... 1066
About installing the SQL Agent .................................................... 1067
Backup strategies for SQL .......................................................... 1067
Adding SQL Servers to the list of servers on the Backup and Restore
tab ................................................................................... 1069
Configuring Backup Exec to run a consistency check before every SQL
backup ............................................................................. 1069
Using snapshot technology with the SQL Agent ............................... 1070
Using database snapshots for SQL Server ..................................... 1071
Backing up SQL databases and transaction logs ............................. 1073
Setting default backup options for SQL Server .......................... 1085
Restoring SQL databases and transaction logs ............................... 1095
Restoring the SQL master database ....................................... 1097
Restarting SQL using database copies .................................... 1098
Disaster recovery of a SQL Server ................................................ 1100
 Contents 28

Manual recovery of a SQL Server .......................................... 1102

Appendix F Backup Exec Agent for Microsoft Exchange

Server .......................................................................... 1103
About the Backup Exec Exchange Agent ....................................... 1104
Requirements for using the Exchange Agent .................................. 1104
Granting permissions on the Exchange Server to enable database
backups and restores, and Granular Recovery Technology
operations ......................................................................... 1108
About installing the Exchange Agent ............................................. 1113
Adding Exchange Servers and database availability groups to the list
of servers on the Backup and Restore tab ................................ 1113
Managing preferred server configurations for Microsoft Exchange
Database Availability Groups ................................................. 1114
Recommended configurations for Exchange .................................. 1117
Requirements for accessing Exchange mailboxes ........................... 1118
Backup strategies for Exchange ................................................... 1119
How Granular Recovery Technology works with the Exchange
Information Store ............................................................... 1121
Snapshot and offhost backups with the Exchange Agent ................... 1122
Backing up Exchange data ......................................................... 1124
Setting default backup options for Exchange Server ................... 1132
Restoring Exchange data ........................................................... 1138
Disaster recovery of an Exchange Server ....................................... 1144

Appendix G Backup Exec Agent for Microsoft SharePoint ....... 1146

About the Agent for Microsoft SharePoint ....................................... 1146

About installing the Agent for Microsoft SharePoint .......................... 1147
Requirements for the Agent for Microsoft SharePoint ........................ 1147
Using the Agent for Microsoft SharePoint with SharePoint Server
2010/2013/2016 and SharePoint Foundation 2010/2013/2016
........................................................................................ 1148
Adding a Microsoft SharePoint server farm to the list of servers on the
Backup and Restore tab ....................................................... 1149
Backing up Microsoft SharePoint data ........................................... 1149
Setting default backup options for SharePoint ........................... 1153
Restoring Microsoft SharePoint data ............................................. 1156
Disabling or enabling communication between a Microsoft SharePoint
web server and Backup Exec ................................................ 1158
Viewing or changing SharePoint farm properties .............................. 1159
Disaster recovery of Microsoft SharePoint 2010/2013/2016 data ......... 1160
 Contents 29

Appendix H Backup Exec Agent for Oracle on Windows or

Linux Servers ............................................................ 1165
About the Backup Exec Oracle Agent ............................................ 1165
About installing the Oracle Agent .................................................. 1167
Configuring the Oracle Agent on Windows computers and Linux servers
........................................................................................ 1167
Configuring an Oracle instance on Windows computers .............. 1168
Viewing an Oracle instance on Windows computers ................... 1172
Editing an Oracle instance on Windows computers .................... 1173
Deleting an Oracle instance on Windows computers .................. 1174
Enabling database access for Oracle operations on Windows
computers ................................................................... 1174
Configuring an Oracle instance on Linux servers ....................... 1177
Viewing an Oracle instance on Linux servers ............................ 1179
Editing an Oracle instance on Linux servers ............................. 1180
Deleting an Oracle instance on Linux servers ............................ 1180
Enabling database access for Oracle operations on Linux servers
.................................................................................. 1181
About authentication credentials on the Backup Exec server .............. 1182
Setting authentication credentials on the Backup Exec server for
Oracle operations ......................................................... 1183
Deleting an Oracle server from the Backup Exec server’s list of
authentication credentials ............................................... 1184
About Oracle instance information changes .................................... 1185
About backing up Oracle databases .............................................. 1185
About backing up Oracle RAC databases ................................. 1187
About performing a DBA-initiated backup job for Oracle .............. 1188
Oracle backup options ......................................................... 1189
About restoring Oracle resources ................................................. 1190
About DBA-initiated restore for Oracle ..................................... 1193
Oracle restore options ......................................................... 1193
About redirecting a restore of Oracle data ................................ 1194
Oracle advanced restore options ........................................... 1194
Performing a redirect restore of an Oracle 12c database using
Backup Exec ................................................................ 1196
Requirements for recovering the complete Oracle instance and
database using the original Oracle server ........................... 1199
Recovering the complete Oracle instance and database using the
original Oracle server ..................................................... 1200
Requirements for recovering the complete Oracle instance or
database to a computer other than the original Oracle server
.................................................................................. 1201
 Contents 30

Recovering the complete Oracle instance or database to a

computer other than the original Oracle server .................... 1202
Best practices for Backup Exec Agent for Oracle on Windows and
Linux Servers ..................................................................... 1203

Appendix I Backup Exec Agent for Enterprise Vault ................. 1207

About the Agent for Enterprise Vault ............................................. 1207
Requirements for the Enterprise Vault Agent ................................... 1211
About installing the Enterprise Vault Agent ..................................... 1212
About backup methods for Enterprise Vault backup jobs ................... 1212
Enterprise Vault backup options ............................................. 1215
About backing up Enterprise Vault components ............................... 1216
About consistency checks for Enterprise Vault databases and
Compliance and Discovery Accelerator databases ..................... 1219
Restoring Enterprise Vault .......................................................... 1219
Enterprise Vault restore options ............................................. 1221
About restoring individual files and folders with the Enterprise
Vault Agent .................................................................. 1224
About automatic redirection of Enterprise Vault components under
an Enterprise Vault server ............................................... 1224
Redirecting a restore for an Enterprise Vault component ............. 1225
Configuring Enterprise Vault to use the name of the new SQL Server
that holds the Directory database ........................................... 1227
Best practices for the Enterprise Vault Agent .................................. 1229
About the Backup Exec Migrator for Enterprise Vault ........................ 1229
Backup Exec Migrator for Enterprise Vault requirements ............. 1230
How the Backup Exec Migrator works ..................................... 1230
About using staged migrations with Backup Exec and the Backup
Exec Migrator ............................................................... 1234
About Backup Exec Migrator events ........................................ 1235
About Backup Exec Migrator logs ........................................... 1235
How to enable Backup Exec Migrator logging ........................... 1236
About deleting files migrated by Backup Exec Migrator ............... 1238
Configuring the Backup Exec Migrator ..................................... 1239
About viewing migrated Enterprise Vault data ........................... 1246
About retrieving migrated Enterprise Vault data ......................... 1247
About the Partition Recovery Utility ......................................... 1248
Enterprise Vault logon account ..................................................... 1252
Enterprise Vault options .............................................................. 1252
 Contents 31

Appendix J Backup Exec Agent for Microsoft Active Directory

........................................................................................ 1253

About the Agent for Microsoft Active Directory ................................. 1253

Requirements for the Agent for Microsoft Active Directory ................. 1254
About backing up Active Directory and ADAM/AD LDS ..................... 1255
Editing options for Active Directory and ADAM/AD LDS backup
jobs ............................................................................ 1256
Microsoft Active Directory backup job options ........................... 1258
About restoring individual Active Directory and ADAM/AD LDS objects
........................................................................................ 1259

Appendix K Backup Exec Central Admin Server Feature ......... 1262

About the Central Admin Server feature ......................................... 1263
Requirements for installing CAS ................................................... 1265
How to choose the location for CAS storage and media data ............. 1266
About installing the Central Admin Server feature ............................ 1268
Push-installing a managed Backup Exec server from the central
administration server ..................................................... 1269
Managed Backup Exec Server Configuration options .................. 1273
Installing a managed Backup Exec server across a firewall ......... 1275
Upgrading an existing CAS installation .......................................... 1277
Changing a Backup Exec server to a central administration server
........................................................................................ 1279
Changing a Backup Exec server to a managed Backup Exec server
........................................................................................ 1280
Deleting a managed Backup Exec server from a CAS environment
........................................................................................ 1281
Renaming a central administration server ....................................... 1283
Renaming a managed Backup Exec server .................................... 1284
How to reduce network traffic in CAS ............................................ 1285
CAS distributed, centralized, and replicated catalog locations ............. 1285
Changing the settings for a managed Backup Exec server ................. 1287
What happens when CAS communication thresholds are reached
........................................................................................ 1298
Enabling or disabling communications between the managed
Backup Exec server and the central administration server
.................................................................................. 1299
Alerts and notifications in CAS ..................................................... 1299
Enabling managed Backup Exec servers to use any available network
interface card .................................................................... 1301
About job delegation in CAS ........................................................ 1301
About copying jobs instead of delegating jobs in CAS ................. 1302
 Contents 32

About adding storage devices in a CAS environment ........................ 1302

How data lifecycle management (DLM) works in a CAS environment
........................................................................................ 1302
Obtaining media audit information for a managed Backup Exec server
........................................................................................ 1303
How to use Backup Exec server pools in CAS ................................ 1304
Selecting a Backup Exec server pool for backups ...................... 1305
Creating a Backup Exec server pool ....................................... 1305
Adding managed Backup Exec servers to a Backup Exec server
pool ........................................................................... 1306
Deleting a Backup Exec server pool ........................................ 1306
Removing a managed Backup Exec server from a Backup Exec
server pool .................................................................. 1307
How centralized restore works in CAS ........................................... 1307
How CAS restores data that resides on multiple storage devices
.................................................................................. 1308
About recovering failed jobs in CAS .............................................. 1310
Pausing or resuming a managed Backup Exec server ...................... 1311
Stopping or starting Backup Exec services for a managed Backup
Exec server ....................................................................... 1312
Viewing managed Backup Exec server properties ............................ 1313
Viewing the settings for a central administration server ..................... 1316
Disaster recovery in CAS ............................................................ 1318
Troubleshooting CAS ................................................................. 1319
Running the Backup Exec Utility for CAS operations ........................ 1321
Uninstalling Backup Exec from the central administration server ........ 1321
Uninstalling Backup Exec from a managed Backup Exec server ......... 1322

Appendix L Backup Exec Advanced Disk-based Backup

Feature ........................................................................ 1323
About the Advanced Disk-based Backup feature ............................. 1323
How to use synthetic backups in place of recurring full backups .......... 1324
Setting default backup options for the Advanced Disk-based Backup
feature .............................................................................. 1326
About true image restore for synthetic backups ............................... 1327
How to use off-host backup to process remote computer backups on
the Backup Exec server ........................................................ 1329
Configuring off-host backup options for a backup job ........................ 1332
Best practices for off-host backup ................................................. 1334
Troubleshooting off-host backups ................................................. 1335
Off-host backup issues with hardware providers .............................. 1338
 Contents 33

Appendix M Backup Exec NDMP Feature ..................................... 1339

Features of the NDMP feature ..................................................... 1339

Requirements for using the NDMP feature ..................................... 1340
About installing the NDMP feature ................................................ 1341
Adding NDMP servers to Backup Exec .......................................... 1341
Sharing the tape drives on NDMP servers between multiple Backup
Exec servers ...................................................................... 1343
NDMP backup options for NDMP servers ....................................... 1343
NDMP server backup selections .................................................. 1346
How to use patterns to exclude files and directories from an NDMP
server backup .................................................................... 1347
Supported configurations for duplicating data from NDMP servers
........................................................................................ 1349
About restoring and redirecting restore data for NDMP servers ........... 1349
NDMP server restore options ................................................. 1350
Setting the default backup options for the NDMP feature ................... 1353
Viewing the properties of an NDMP server ..................................... 1354
NDMP server properties ....................................................... 1354
Viewing storage properties for an NDMP server .............................. 1355
Storage properties for an NDMP server ................................... 1355

Appendix N Backup Exec Agent for Linux ..................................... 1357

About the Agent for Linux ........................................................... 1358

About open files and the Agent for Linux ........................................ 1358
Requirements for the Agent for Linux ............................................ 1358
About installing the Agent for Linux ............................................... 1359
Installing the Agent for Linux ................................................. 1360
About the Backup Exec operators (beoper) group for the Agent
for Linux ...................................................................... 1362
About establishing trust for a remote Linux computer in the Backup
Exec list of servers ............................................................. 1363
Establishing trust and adding a remote Linux computer to the
Backup Exec list of servers ............................................. 1364
Adding additional Backup Exec servers to which the Agent for Linux
can publish information ........................................................ 1364
About configuring the Agent for Linux ............................................ 1365
Excluding files and directories from all backup jobs for Linux computers
........................................................................................ 1366
Editing configuration options for Linux computers ............................ 1366
Configuration options for Linux computers ................................ 1367
About backing up a Linux computer by using the Agent for Linux ........ 1374
Linux backup options ........................................................... 1375
 Contents 34

About backing up and restoring Novell Open Enterprise Server

(OES) components ....................................................... 1376
About restoring data to Linux computers ........................................ 1377
About restoring Novell OES components ................................. 1378
Restore job options for Linux computers .................................. 1378
Editing the default backup job options for Linux computers ................ 1379
Default backup job options for Linux computers ......................... 1379
Uninstalling the Agent for Linux .................................................... 1381
Manually uninstalling the Agent for Linux ................................. 1382
Run-time scripts to remove when manually uninstalling the Agent
for Linux ...................................................................... 1383
Starting the Agent for Linux daemon ............................................. 1384
Stopping the Agent for Linux daemon ............................................ 1385
Troubleshooting the Agent for Linux .............................................. 1385

Appendix O Backup Exec Remote Media Agent for Linux ........ 1391
About the Remote Media Agent for Linux ...................................... 1392
How the Remote Media Agent for Linux works ................................ 1393
Requirements for the Remote Media Agent for Linux ........................ 1394
About open files and the Remote Media Agent for Linux .................... 1395
About installing the Remote Media Agent for Linux ........................... 1395
Installing the Remote Media Agent for Linux ............................. 1396
Uninstalling the Remote Media Agent for Linux ............................... 1399
Starting the Remote Media Agent for Linux daemon ......................... 1400
Stopping the Remote Media Agent for Linux daemon ....................... 1400
About establishing trust for a Remote Media Agent for Linux computer
in the Backup Exec list of servers .......................................... 1401
Establishing trust and adding a Remote Media Agent for Linux
computer to the Backup Exec list of servers ........................ 1401
Adding additional Backup Exec servers to which Remote Media Agent
for Linux can publish ............................................................ 1401
Finding simulated tape library files ................................................ 1402
About the Backup Exec operators (beoper) group for the Remote Media
Agent for Linux ................................................................... 1403
Creating the Backup Exec operators (beoper) group manually for
the Remote Media Agent for Linux .................................... 1403
About adding a Linux server as a Remote Media Agent for Linux ....... 1404
Adding a Linux server as a Remote Media Agent for Linux .......... 1404
Remote Media Agent for Linux options .................................... 1405
Changing the port for communications between the Backup Exec server
and the Remote Media Agent for Linux .................................... 1407
 Contents 35

About creating storage device pools for devices attached to the Remote
Media Agent for Linux ......................................................... 1407
Editing properties for the Remote Media Agent for Linux .................. 1408
Remote Media Agent for Linux properties ................................. 1408
Deleting a Remote Media Agent for Linux from the Backup Exec list
of servers .......................................................................... 1409
Sharing a Remote Media Agent for Linux between multiple Backup
Exec servers ...................................................................... 1409
About backing up data by using the Remote Media Agent for Linux
........................................................................................ 1410
About restoring data by using the Remote Media Agent for Linux ........ 1410
About the Tape Library Simulator Utility ......................................... 1411
Creating a simulated tape library .................................................. 1412
Simulated Tape Library options .............................................. 1413
Viewing simulated tape libraries properties ..................................... 1413
Simulated tape library properties ............................................ 1414
Deleting a simulated tape library .................................................. 1414
Managing simulated tape libraries from the command line ................. 1415
Command line switches for the Tape Library Simulator Utility ............. 1416
Troubleshooting the Remote Media Agent for Linux ......................... 1417

Appendix P Accessibility and Backup Exec .................................. 1420

About accessibility and Backup Exec ............................................ 1420

About keyboard shortcuts in Backup Exec ...................................... 1421
Home tab keyboard shortcuts ................................................ 1422
Backup and Restore tab keyboard shortcuts ............................. 1422
Job Monitor tab keyboard shortcuts ........................................ 1430
Storage tab keyboard shortcuts .............................................. 1433
Reports tab keyboard shortcuts .............................................. 1441
General keyboard navigation within the Backup Exec user interface
.................................................................................. 1442
Keyboard navigation within dialog boxes in Backup Exec ............ 1442
List box navigation in Backup Exec ............................................... 1443
Tabbed dialog box navigation in Backup Exec ................................. 1443
About setting accessibility options ................................................ 1444

Glossary .......................................................................................................... 1445

Index ................................................................................................................ 1451
 Chapter 1
Introducing Backup Exec
This chapter includes the following topics:

■ About Backup Exec

■ How Backup Exec works

About Backup Exec

Backup Exec 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 features offers solutions
for scaling your Backup Exec environment and extending platform and feature
support.
See “How Backup Exec works” on page 36.

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
 Introducing Backup Exec 37
How Backup Exec works

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 and cloud storage
Backup Exec uses data lifecycle management to automatically delete expired
backup sets on disk storage, disk cartridge media, deduplication storage, storage
arrays, cloud storage, 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 335.
■ 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.
 Chapter 2
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 Express Edition components installed with Backup Exec

■ System requirements for Backup Exec

■ Installing Backup Exec by using the Installation Wizard

■ Installing additional agents and features 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)

■ About the installation log

■ Viewing the Installation Summary Report

■ Repairing Backup Exec

■ Updating Backup Exec with Veritas Update

■ Viewing installed updates

■ Uninstalling Backup Exec updates

■ Viewing license information

 Installation 39
About the Backup Exec installation process and licensing options

■ Backup Exec license contract information

■ About upgrading to Backup Exec

■ Post-installation tasks

■ Uninstalling Backup Exec

■ Uninstalling Backup Exec using the command line

■ Uninstalling Backup Exec features 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 features. Using the installation wizard, you can
install Backup Exec and its agents and features 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 data deduplication in Windows, on an ReFS volume, or on
Cluster Shared Volumes.

When you install Backup Exec, you can input a license in two ways:
 Installation 40
About the Backup Exec installation process and licensing options

Table 2-1 Licensing options

Item Description

Enter entitlement IDs manually You can enter the entitlement IDs that are
listed on your license certificate. Entitlement
IDs contain one letter and 10 numbers, such
as A0123456789. After you add your
entitlement IDs, enter the Veritas User
Account credentials to connect to the Veritas
Entitlement Management System. Backup
Exec connects to the Veritas Entitlement
Management System and downloads the
license files. An Internet connection is
required to enter entitlement IDs manually.
Note: Licenses from previous versions of
Backup Exec cannot activate the current
version of Backup Exec.

Import licenses from the License File You can import your License Files (.slf) from
a network share or from a local drive.

You must go to the Veritas Entitlement

Management System to obtain them. From
the Veritas Entitlement Management System,
you receive one file with all of the entitlement
IDs that you registered.

After installation, the .slf files can be found in

the following location:

Windows 2008 and later:

C:\Programdata\Veritas Shared\Licenses

Install a 60-day trial version A 60-day trial version is available for Backup
Exec. If you do not enter any entitlement IDs
or license files during the installation process,
a trial version is installed.

After Backup Exec has been installed, you can install additional agents and features
if you have valid licenses for them. For more information about how to add agents
and features, refer to the Backup Exec Price and Licensing Guide. You can also
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.
 Installation 41
Backup Exec preinstallation checklist

Backup Exec may install the following additional products during the installation
process:
■ Microsoft Report Viewer 2010 SP1
■ Microsoft.NET Framework 4.8
■ 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 Visual C++ 2015 Redistributable Package
■ Microsoft SQL Server 2014 Express with SP3
For information about the best practices to install Backup Exec, refer to Backup
Exec Best Practices.
See “Installing Backup Exec by using the Installation Wizard” on page 48.
See “Installing additional agents and features to the local Backup Exec server”
on page 58.
See “Push-installing Backup Exec to remote computers” on page 60.
See “Push-installing the Agent for Windows to remote computers” on page 68.
See “Installing Backup Exec using the command line (silent mode)” on page 89.
See “Backup Exec preinstallation checklist” on page 41.

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 42.
■ Check the Backup Exec Hardware Compatibility List to confirm that your storage
device hardware is supported in this version of Backup Exec.
 Installation 42
Running the Environment Check before installing or upgrading Backup Exec

■ 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.
■ 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 667.
■ Ensure that port 50104 is 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 2014 Express with SP3 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 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 46.
■ If the third-party software that uses Backup Exec ports is configured correctly.
 Installation 43
Running the Environment Check before installing or upgrading Backup Exec

■ If required components are installed, and if they are compatible with Backup
Exec.
■ If previous versions of Backup Exec and Backup Exec features are installed.
■ If storage device hardware and associated drivers are properly installed and
recognized by the Windows operating system.
■ If the volume that has the deduplication storage does not have more than 12%
free space available.
■ If the deduplication services are not started.
■ If the Windows Hotfix (Windows update) is not installed.
One of the following results is reported for each item:

Table 2-2 Environment Check results

Result Description

Passed There are no incompatibilities to prevent the Backup Exec installation.

For hardware, this result indicates that the hardware configuration is
recognized by Backup Exec.

Warning 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.

Failed An incompatibility with Backup Exec exists, and it will cause the
installation to fail. Action is required before you can successfully install
Backup Exec.

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.
 Installation 44
Running the Environment Check before installing or upgrading Backup Exec

3 Do any of the following:

To check the configuration of the local Check Local Environment Check.

computer

To check the configuration of a remote Check Remote Environment Check.

computer

4 Click Next.
5 If you checked Remote Environment Check in step 3, do one of the following,
and then click Next:

To select the name of a computer from a Do the following:

list
■ Click Add Server From List.
■ Select the computer from the list, and
then click Next.

To add the name of a computer manually 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 remove the name of a computer from Do the following:

the list of computers on which the
■ Select the computer from the list.
Environment Check runs
■ Click Remove.

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.
 Installation 45
Microsoft SQL Server Express Edition components installed with Backup Exec

Microsoft SQL Server Express Edition

components installed with Backup Exec
The Backup Exec installation program installs Microsoft SQL Server 2014 Express
with SP3 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.

■ Select a Microsoft SQL Server 2008 R2 SP2 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 2008 R2 SP2
instance, ensure that the instance is installed before you continue with the
installation.

Caution: Backup Exec may not function properly if you install it into an existing
SQL Server instance that uses case-sensitive collation. It is recommended 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.
 Installation 46
System requirements for Backup Exec

Note: If you are installing a managed Backup Exec server, it is recommended that
you select a local Microsoft SQL Server 2008 R2 SP2 or later 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 46.

System requirements for Backup Exec

The following are the minimum system requirements to run this version of Backup
Exec:

Table 2-3 Minimum system requirements

Item Requirements

Operating system You can find a list of compatible operating systems, platforms, and
applications in the Backup Exec Software Compatibility List.
Note: Backup Exec 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 and
later. You can only install the Backup Exec Agent for Windows on Server
Core computers.

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 has been
enabled for data deduplication in Windows, on an ReFS volume, or on
Cluster Shared Volumes.

Internet browser Internet Explorer 7.0 or later

Processor Intel Pentium, Xeon, AMD, or compatible

Screen resolution 1024 x 768

SQL Server or SQL Server 2014 Express with SP3

SQL Express
 Installation 47
System requirements for Backup Exec

Table 2-3 Minimum system requirements (continued)

Item Requirements

Memory 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 features installed, and the specific computer
configuration.

For the Central Admin Server feature: 1 GB RAM is required; 2 GB

RAM is recommended.

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.

User interface The Backup Exec user interface displays in the format that is configured
language 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-4, you must install the English language
pack in Windows.

Installation disk 1.26 GB (Typical installation)

space
1.91 GB (Includes all features)
Note: Disk space requirements may vary depending on the operations
performed, the features 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.

Other Hardware The following hardware is recommended:

■ Network interface card or a virtual network adapter card

■ CD/DVD drive
■ A mouse
 Installation 48
Installing Backup Exec by using the Installation Wizard

Table 2-3 Minimum system requirements (continued)

Item Requirements

Storage 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 in the Backup Exec Hardware Compatibility
List.

For more information about support for additional drives within a robotic
or virtual tape library, refer to the Backup Exec Price and Licensing
Guide.

Table 2-4 Supported languages for the Backup Exec user interface

Language Language code

Chinese (Simplified) ZH

Chinese (Traditional) CH

English EN

French FR

German DE

Italian IT

Japanese JP

Korean KO

Spanish ES

Russian RU

Portuguese (Brazilian ) PT

See “Installing Backup Exec by using the Installation Wizard” on page 48.

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 simpler than a custom installation and will install
all agents and features included with your license. A typical installation may be
appropriate for small, simple environments. A custom installation is designed for
 Installation 49
Installing Backup Exec by using the Installation Wizard

large or complex environments, such as a remote Backup Exec server or an

environment which uses the Enterprise Server feature. In a custom installation, you
can choose which features and agents included with your license will be installed.
This makes it ideal for a user who wants to view and control which agents and
features will be installed.
In 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.
■ All agents and features included with your license are installed.
■ Veritas Update runs automatically.

Note: Before you install, make sure that your licenses for the Backup Exec editions
that you want to install are available. You must enter a license in order to install
any edition of Backup Exec, but you can install the trial edition without a license.

Choose either the typical installation or the custom installation:

How to perform a typical installation
How to perform a custom installation

How to perform a typical installation

Follow these steps to perform a typical installation of Backup Exec. A typical
installation of Backup Exec installs all of the features included with your license.
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.8. However, not all versions of Windows support .NET Framework
4.8. 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 and click Next.
3 On the Installation Type panel, click Typical installation, and then click Next.
 Installation 50
Installing Backup Exec by using the Installation Wizard

4 The Backup Exec Environment Check will run automatically.

5 Review the results of the Environment Check. 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.

6 On the Add Licenses panel, use one of the following methods to add licenses.

To enter entitlement IDs manually Do the following in the order listed:

Note: If you do not have an Internet ■ In the Enter an Entitlement ID field,
connection, import the license files type the appropriate entitlement ID from
manually to the Backup Exec server. To your license certificate.
download the license file go to the Veritas ■ Click Add to List.
Entitlement Management System portal ■ Repeat for each entitlement ID.
and then import to the Backup Exec server.
■ When you are finished entering the
entitlement IDs, click Next.
■ Enter the Veritas User Account
credentials and then click Download
to connect to the Veritas Entitlement
Management System and download
the license files.

To import licenses from the License File Do the following in the order listed:

■ Click Import License File.

■ Browse to the location of your license
files, and then select the appropriate
file.

■ Click Next.

To install a trial version Do not enter an entitlement ID or import a

license file. Go to the next step.

7 If you entered entitlement IDs, do one of the following on the Review Licenses
panel.
To install a licensed version of Backup Exec, perform the following in order:
■ 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 features you want to install.
 Installation 51
Installing Backup Exec by using the Installation Wizard

■ Click the drop-down menu, and then select the number of licenses that you
want to install.
To install a trial edition of Backup Exec, in the Select a Backup Exec edition
license to install on the computer field, select Trial. This option is only
available when you have installed a license. If you have not installed a license,
a trial version will automatically be installed when you click Next.
When you are finished on the Review Licenses panel, click Next.
8 On the Service Account panel, 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.
9 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.
If, during Backup Exec installation, the installer detects Backup Exec database
(BEDB) files from an earlier installation, the installer provides you the option
to use either the new database files or the existing database files. If you choose
to use the new database files, the old database files are copied to a different
location.
However, if you choose to use the existing database files, the installer warns
you that the installation might fail if the existing database files are of a different
version than the Backup Exec version you are trying to install.
Click Next.
10 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.
 Installation 52
Installing Backup Exec by using the Installation Wizard

11 On the Remote Computers panel, do one of the following.

To install the Agent for Windows on one remote computer, perform the following
in order:
■ 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 multiple computers using the same settings,
perform the following in order:
■ 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.
 Installation 53
Installing Backup Exec by using the Installation Wizard

To proceed without push-installing the Agent for Windows, click Next.

12 On the Data Backup panel, select a location to store a copy of the existing
Backup Exec database.
You can use this copy if the upgrade to Backup Exec fails.
After the upgrade to Backup Exec is complete, the deduplication storage is
converted to a newer version. The deduplication storage folder remains offline
till the conversion is complete. After the conversion is complete, and services
are restarted, the deduplication storage comes online.
Jobs that are targeted to deduplication storage fail during the conversion
process. Jobs that are scheduled on other storage continue to run during the
deduplication storage conversion. The estimated time for the conversion is
displayed in months, days, and hours. It is recommended that you keep a
secondary copy of the deduplication data before the upgrade starts, which can
be used if the conversion process fails.

Note: This panel is displayed only when you upgrade Backup Exec.

13 Select the I have read and understood the information check box, and then
click Next.
14 Review the Backup Exec installation summary, and then click Install.
15 If you installed the Agent for Windows on remote computers, on the Remote
Installation dialog box, click Next.
16 When the installation is complete, you can choose to restart the system, view
the readme, or remove the Backup Exec shortcut from the desktop.
17 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 BKUPINST21.htm in the
following directory on the computer where Backup Exec is installed.
For Windows 2008 and later: %programdata%\Veritas\Backup Exec\Logs
See “About the installation log” on page 98.

How to perform a custom installation

Follow these steps to install a custom installation of Backup Exec. A custom
installation allows you to choose which agents and features will be installed, based
on the licenses which you enter. Note that you cannot use a custom installation to
install more agents and features than are included with your license.
 Installation 54
Installing Backup Exec by using the Installation Wizard

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 wizard uses the Microsoft .NET Framework
version 4.8. However, not all versions of Windows support .NET Framework
4.8. 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 and click Next.
3 On the Installation Type panel, select Custom installation, and then click
Next.
4 On the Menu panel, select Local Installation, and then select Install Backup
Exec software and features. Click Next.
5 The Backup Exec Environment Check will run automatically.
6 Review the results of the Environment Check. 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 On the Add Licenses panel, use one of the following methods to enter licenses:
 Installation 55
Installing Backup Exec by using the Installation Wizard

To enter entitlement IDs manually Do the following in the order listed:

Note: If you do not have an Internet ■ In the Enter an Entitlement ID field,
connection, import the license files type the appropriate entitlement ID from
manually to the Backup Exec server. To your license certificate.
download the license file go to the Veritas ■ Click Add to List.
Entitlement Management System portal ■ Repeat for each entitlement ID.
and then import to the Backup Exec server.
■ When you are finished entering the
entitlement IDs, click Next.
■ Enter the Veritas User Account
credentials and then click Download
to connect to the Veritas Entitlement
Management System and download
the license files.

To import licenses from the License File Do the following in the order listed:

■ Click Import License File.

■ Browse to the location of your license
files, and then select the appropriate
file.
■ Click Next.

To install a trial version Do not enter an entitlement ID or import a

license file. Go to the next step.

8 If you entered entitlement IDs, do one of the following on the Review Licenses
panel:
To install a licensed version of Backup Exec, perform the following in order:
■ 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 features you want to install.
■ Click the drop-down menu, and then select the number of licenses that you
want to install.
■ If you do not make a selection, Backup Exec will select the license with the
largest feature set by default.
To install a trial version of Backup Exec, select Trial in the Select a Backup
Exec edition license to install on the computer field. This option is only
available when you have installed a license. If you have not installed a license,
a trial version will automatically be installed when you click Next.
The Review Licenses panel also allows you to view and customize the capacity
for each entitlement ID.
 Installation 56
Installing Backup Exec by using the Installation Wizard

When you are finished on the Review Licenses panel, click Next.
9 On the Configure Features panel, the Select features to install panel displays
all of the features and agents included with the licenses for which you entered
entitlement IDs. Select the check box next to any feature or agent that you
want to install. You can deselect agents and features to prevent them from
being installed now. Features and agents are organized by edition, based on
the licenses that you have entered. Note that a Trial Edition will display features
for Backup Exec Bronze, Silver, and Gold editions on this screen.
Agents and features for which you have not entered a license will be displayed,
but will be unavailable. If you install a trial license, then install a license with
fewer agents or features than are included with the trial, those agents and
features will be removed.
When you are finished configuring agents and features, click Next.
10 If you want to install Backup Exec for any additional languages, select the
language on the Choose Languages panel, and then click Next.
11 On the Destination panel, 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. It is recommended that you do not select a mount point as the
destination directory because if you delete the mount point, Backup Exec will
be uninstalled.
If the installer detects Backup Exec database (BEDB) files from an earlier
installation, the installer provides you the option to use either the new database
files or the existing database files. If you choose to use the new database files,
the old database files are copied to a different location.
However, if you choose to use the existing database files, the installer warns
you that the installation might fail if the existing database files are of a different
version than the Backup Exec version you are trying to install.
Click Next when you are finished reviewing the destination information.
 Installation 57
Installing Backup Exec by using the Installation Wizard

12 On the Service Account panel, 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.
13 On the Choose SQL Server panel, do one of the following to select a location
to store the Backup Exec Database.

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.

To create a local Backup Exec SQL Express instance, 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 use an existing SQL Server 2008 R2 SP2 instance, do the following in the
order listed:
■ Click Use an existing instance of SQL Server 2008 R2 with Service
Pack 2 or a later SQL Server version.
■ Select the instance.
■ Note that 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. For more information, See “Microsoft SQL Server Express
Edition components installed with Backup Exec” on page 45.
Click Next when you are finished.
 Installation 58
Installing additional agents and features to the local Backup Exec server

14 Backup Exec will now attempt to connect to the instance.

15 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.

16 If you are prompted, select how the Device Driver Installer should install
device drivers for the tape storage devices that are connected to the server,
and then click Next.
It is recommended that you select Use device drivers for all tape devices.
17 If you are prompted, enter information or choose settings for the additional
features that you want to install, and then click Next after each selection.
18 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.
19 When the installation is complete, you can choose to restart the system, view
the readme, or remove the Backup Exec shortcut from the desktop.
20 Click Next, and then click Finish to exit the wizard.
If you chose to restart the system, the computer will restart automatically.

Installing additional agents and features to the

local Backup Exec server
You can install agents and features when you install Backup Exec. However, if you
have already installed Backup Exec and want to install additional agents or features,
review the documentation for these features to ensure that your system meets all
of its minimum requirements. In addition, you must have a valid license for any
agents or features that you want to install. The Backup Exec services may be
stopped while the additional features are installed. If any active jobs are running,
you are prompted to stop them, or to wait for the jobs to finish.
 Installation 59
Installing additional agents and features to the local Backup Exec server

Note: If the Central Admin Server feature is installed, and you want to install
additional features 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 1311.

To install additional Backup Exec features to the local Backup Exec server
1 Click the Backup Exec button, select Installation and Licensing, and then
select Install Features and Licenses on this Backup Exec Server.
You may be prompted to insert the installation media.
2 Do one of the following:

To enter serial numbers Do the following in the order listed:

manually
■ In the Enter a Serial number field, type the
Note: If you do not have an appropriate serial number from your license
Internet connection, import certificate.
the license files manually to ■ Click Add to List.
the Backup Exec server. To ■ Repeat for each serial number.
download the license file go
■ Click Next.
to the Veritas Entitlement
■ Enter the Veritas User Account credentials and then
Management System portal
click Download to connect to the Veritas Entitlement
and then import to the Backup
Management System and download the license files.
Exec server.

To import licenses from the Do the following in the order listed:

license file
■ Click Import License File.
■ Browse to the location of your license files, and then
select the appropriate file.
■ Click Next.

To install a trial version Do not type a serial number or import a license file. Go
to step 5.
 Installation 60
Push-installing Backup Exec to remote computers

3 If you entered product activation serial numbers, on the Review Licenses

panel, the editions for which you have entered licenses will be shown. You can
also edit the Allocated Capacity field for each edition to specify how much of
your available capacity each will be able to use.
To install a trial edition of Backup Exec, select Trial in the Select a Backup
Exec edition license to install on the computer field. This option is only
available when you have installed a license. If you have not installed a license,
a trial version will automatically be installed when you click Next.
4 Click Next.
5 Do the following:
■ Check the check boxes for the additional features that you want to install.
■ Uncheck the check boxes for the features that you want to remove.

6 Click Next.
7 If you are prompted, enter information or choose settings for the additional
features that you want to install. Click Next after each selection.
8 Review the Backup Exec installation summary, and then click Install.
The Backup Exec services are stopped while the additional features 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.
9 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.
 Installation 61
Push-installing Backup Exec to remote computers

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.8. However, not all versions of Windows support .NET Framework 4.8. 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-5 Special considerations for installing Backup Exec to remote

computers

Item Consideration

Windows Server 2008 and later To push-install Backup Exec to a computer

that runs Windows Server 2008 and 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 data deduplication
in Windows, on an ReFS volume, or on
Cluster Shared Volumes.

Symantec Endpoint Protection (SEP) 11.0 or To push-install Backup Exec to a computer

later 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.

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.
 Installation 62
Push-installing Backup Exec to remote computers

The installation process creates an installation log named BKPINST20.htm in the

following directory on the computer where Backup Exec is installed.
For Windows 2008 and later: %programdata%\Veritas\Backup Exec\Logs
To push-install Backup Exec to remote computers
1 Do one of the following:

To push-install Backup Exec to remote Do the following steps in the order listed:
computers from the installation media
■ 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 Click the Backup Exec button, select
computers from the Backup Exec server Installation and Licensing, and then
select Install Agents and Backup Exec
Servers on Other Servers.

2 On the Remote Computers panel, do one of the following:

To install Backup Exec on one remote Do the following in the order listed:
computer
■ Click Add.
■ Select Add a Single Computer.
■ Select 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.
 Installation 63
Push-installing Backup Exec to remote computers

To install Backup Exec on multiple Do the following in the order listed:

computers using the same settings
■ Click Add.
■ Select Add Multiple Computers with
the Same Settings.
■ Select 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 features.

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:

To enter serial Do the following in the order listed:

numbers from your
■ In the Enter a Serial number field, type the appropriate serial
license certificate
number from your license certificate.
Note: If you do not ■ Click Add to List.
have an Internet ■ Repeat for each license for each feature or agent that you
connection, import want to install.
the license files ■ Click Next.
manually to the
■ Enter the Veritas User Account credentials and then click
Backup Exec
Download to connect to the Veritas Entitlement Management
server. To
System and download the license files.
download the
license file go to the
Veritas Entitlement
Management
System portal and
then import to the
Backup Exec
server.
 Installation 64
Push-installing Backup Exec to remote computers

To import licenses Do the following in the order listed:

from a License File
■ Click Import License File.
■ Browse to the location of your license files, and then select
the appropriate file.
■ Click Next.

To install a trial Do not type a serial number or import a license file. Go to step 8.
version

6 If you entered product activation serial numbers, on the Review Licenses

panel, do one of the following:

To install a licensed version of Backup Do the following in the order listed:

Exec
■ 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 features you want to install.
■ Click the drop-down menu, and then
select the number of licenses that you
want to install.

To install a trial version In the Select a Backup Exec edition

license to install on the computer field,
select Trial.

7 Click Next.
8 On the Configure Features panel, select any additional features that you want
to install.
For example, you can select additional standard features, or you can select
the agents or the features that are available for a trial installation.

Note: When push installing Backup Exec from one server to another, the feature
mapping in the Configure Feature Window will display the server from which
the push install is being initiated, not the server to which the product is being
push installed.

9 In the Destination Folder field, enter the location where you want to install
Backup Exec.
 Installation 65
Push-installing Backup Exec to remote computers

10 Click Next.
11 Complete the service account credentials options as follows:

User Name 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.

Password Type the password for an administrator account that the Backup
Exec services can use.

Domain 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.

12 Click Next.
13 Do one of the following to select a location on which to store the Backup Exec
Database, and then click Next.

To create a local Backup Exec Do the following in the order listed:

SQL Express instance
■ 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.
 Installation 66
Push-installing Backup Exec to remote computers

To use an existing SQL Server Do the following in the order listed:

2008 R2 SP2 instance
■ Click Use an existing instance of SQL Server
2008 R2 with Service Pack 2 or a later SQL
Server version.
■ 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 Express Edition

components installed with Backup Exec”
on page 45.

Backup Exec attempts to connect to the instance.

This step is skipped during upgrades.
14 Click Next.
15 Make a selection for tape device drivers, and then click Next.

Note: You do not need to install tape device drivers if Backup Exec runs on
Windows Server 2012 and later. Kernel-mode drivers and tapeinst.exe are no
longer installed if Backup Exec runs on Windows Server 2012 and later.
See “Installing tape device drivers ” on page 382.

16 Click Next.
17 If you are prompted, enter information or choose settings for additional features
that are being installed, and then click Next or OK after each selection.
18 After Backup Exec validates the remote computers, you can change the list in
any of the following ways:

To manually add one remote computer Click Add, and then click Add a Single
Computer.

To manually add multiple remote Click Add, and then click Add Multiple
computers Computers with the Same Settings.
 Installation 67
Push-installing Backup Exec to remote computers

To add multiple remote computers by Click Import and Export, and then select
importing an existing list of computers 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 change the product that you selected Select the remote computer that you want
to install or to change other properties you to change, and then click Edit.
selected for this installation

To delete a remote computer from the list Select the remote computer that you want
to delete, and then click Delete.

To save this list of remote computers and Verify that Save the server list for future
the associated remote computer logon remote install sessions is checked.
credentials
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 features to
these remote computers.

To save the list of remote computers to an Click Import and Export, and then click
XML file 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 fix the errors that were located during Right-click the name of the computer, and
the validation then click Fix Error.

To enable Backup Exec to attempt to Right-click the name of the computer, and
re-validate an invalid remote computer then click Retry Validation.

19 After all of the computers in the list are validated and the list is complete, click
Next.
 Installation 68
Methods for installing the Agent for Windows

20 Review the Backup Exec installation summary, and then click Install.
See “About the installation log” on page 98.
21 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 68.
■ 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 147.
■ 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 75.
■ Use a command prompt.
See “Using a command prompt to install the Agent for Windows on a remote
computer” on page 79.
■ Use command script files.
See “Using a command script to install the Agent for Windows” on page 82.

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.
 Installation 69
Methods for installing the Agent for Windows

Table 2-6 Special considerations for installing the Agent for Windows

Item Consideration

ForceGuest configuration 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 89.

Server core option of Windows Server Backup Exec installs a command-line version
2008/2012 and later of the Agent for Windows on the computers
that run the Server Core installation option of
Windows Server 2008/2012 and later. 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 916.

Windows data deduplication, ReFS volumes, You cannot install the Agent for Windows on
and Cluster Shared Volumes a volume that has been enabled for data
deduplication in Windows, on an ReFS
volume, or on Cluster Shared Volumes.
 Installation 70
Methods for installing the Agent for Windows

Table 2-6 Special considerations for installing the Agent for Windows
(continued)

Item Consideration

Windows Vista/2008 or later To push-install Backup Exec features to a

computer that runs Windows Vista/2008 or
later, 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.

Symantec Endpoint Protection 11.0 or later To push-install features 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.

Trust the Backup Exec server and remote When you connect to a remote computer from
computer 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 146.

The installation process creates an installation log named BKPINST20.htm on the

computer where Backup Exec is installed, and also creates an installation log named
RAWSinst20.htm on the remote computer.
See “About the installation log” on page 98.
 Installation 71
Methods for installing the Agent for Windows

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 79.
To push-install the Agent for Windows to remote computers
1 Do one of the following:

To push-install the Agent for Windows to Do the following steps in the order listed:
remote computers from the installation
■ From the installation media browser,
media
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 Click the Backup Exec button, select
remote computers from the Backup Exec Installation and Licensing, and then
server select Install Agents and Backup Exec
Servers on Other Servers.

2 Do one of the following

To install the Agent for Windows on one Do the following steps in the order listed:
remote computer
■ 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.
 Installation 72
Methods for installing the Agent for Windows

To install the Agent for Windows on Do the following steps in the order listed:
multiple computers using the same settings
■ 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 features.

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:

To manually add one remote computer Click Add, and then click Add a Single
Computer.

To manually add multiple remote Click Add, and then click Add Multiple
computers Computers with the Same Settings.
 Installation 73
Methods for installing the Agent for Windows

To add multiple remote computers by Click Import and Export, and then select
importing an existing list of computers 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 change the product that you selected Select the remote computer that you want
to install or to change other properties you to change, and then click Edit.
selected for this installation

To delete a remote computer from the list Select the remote computer that you want
to delete, and then click Delete.

To save this list of remote computers and Verify that Save the server list for future
the associated remote computer logon remote install sessions is checked.
credentials
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 features to
these remote computers

To save the list of remote computers to an Click Import and Export, and then click
XML file 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 fix the errors that were located during Right-click the name of the computer, and
the validation then click Fix Errors.

To enable Backup Exec to attempt to Right-click the name of the computer, and
re-validate an invalid remote computer then click Retry Validation.

8 After all of the computers in the list are validated and the list is complete, click
Next.
 Installation 74
Methods for installing the Agent for Windows

9 Review the Backup Exec installation summary, and then click Install.
See “About the installation log” on page 98.
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 Veritas Update” on page 100.
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.
 Installation 75
Methods for installing the Agent for Windows

3 On the Install Updates dialog box, select the option for when you want to
install the updates.

Recurrence Select this option to create a recurring

schedule for the job.

Recurrence Pattern 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.

Starting on Enter the date on which you want the

schedule to take effect.

Calendar View all the scheduled jobs on the calendar

to check for scheduling conflicts.

Keep the job scheduled for x hours Specify the maximum amount of time after
before it is rescheduled the scheduled start time at which you want
Backup Exec to consider the job to be
missed and reschedule it.

Cancel the job if it is still running x Specify the amount of time after the job's
hours after its scheduled start time scheduled start time at which you want
Backup Exec to cancel the job if it is still
running.

Run now with no recurring schedule Select this option to run the job
immediately without scheduling any more
instances of it for the future.

Run on Select a specific date on which to run the

job without scheduling any more instances
of it for the future.

Restart the computer automatically after Select this option to enable Backup Exec
installing the updates to the Backup to automatically restart the remote
Exec Agent for Windows when a restart computer, if required.
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
 Installation 76
Methods for installing the Agent for Windows

Organizational Unit. The features 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-7 How to install the Agent for Windows in an Active Directory
Network

Action Description

Create a transform for the Agent for Windows. A transform contains the changes that you
want to make to the Windows Installer
See the section called “Creating a transform”
package for the Agent for Windows when a
on page 77.
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 2008 or later.
■ Any Windows Server 2008 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.
 Installation 77
Methods for installing the Agent for Windows

Table 2-7 How to install the Agent for Windows in an Active Directory
Network (continued)

Action Description

Create a distribution point (share) that You must copy the transform that you create,
contains the source file of the Agent for and the Backup Exec RAWS32 or RAWSX64
Windows that you want to install. directory, to the distribution point.

See the section called “Creating a software

distribution point (share)” on page 78.

Configure a Group Policy Object to assign The software is installed automatically when
the transform and the RAWS32 or RAWSX64 the computers in the Organizational Unit are
directory in the distribution point to computers started.
in an Active Directory Organizational Unit.

See the section called “Configuring a Group

Policy Object” on page 78.

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
<Backup Exec install path>\Backup Exec\Agents\RAWS32 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 features 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.
 Installation 78
Methods for installing the Agent for Windows

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-8 How to create a software distribution point (share)

Step Description

Step 1 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 2 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

<Backup Exec install path>\Backup
Exec\Agents.

Step 3 Copy the transform from the path where it

was created to the RAWS32 or RAWSX64
directory on the shared folder.

Step 4 Configure a Group Policy Object to deploy

the source files.

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.
 Installation 79
Methods for installing the Agent for Windows

4 On the File Open dialog box, browse to the software distribution point by using
the Universal Naming Convention (UNC) name, for example, \\server
name\share name, select the package file, and then click Open.
5 Select the package file Veritas 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 features 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 features 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 RAWSinst20.htm.
See “About the installation log” on page 98.
 Installation 80
Methods for installing the Agent for Windows

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:
<Backup Exec install path>\Backup Exec\Agents
or you can copy the following folders to the same local directory:

To install to a 32-bit computer: RAWS32, MSXML, VCRedist, and

DotNetFx folders

To install to a 64-bit computer: RAWSX64, MSXML, VCRedist, and

DotNetFx folders

2 Open a command prompt and type the drive letter that you mapped in step 1
and the following path:

To install to a 32-bit computer: \RAWS32

To install to a 64-bit computer: \RAWSX64

 Installation 81
Methods for installing the Agent for Windows

3 Do one of the following:

To install the Agent for Windows to a 32-bit Run the following command:
computer without publishing enabled
setup.exe /RANT32: /S:
/DISADVRT:

To install the Agent for Windows to a 32-bit Run the following command:
computer with publishing enabled
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 Run the following command:
computer and restart the computer
setup.exe/RANT32: /S: /BOOT:
automatically

To install the Agent for Windows to a 64-bit Run the following command:
computer without publishing enabled
setup.exe /RAWSX64: /S:
/DISADVRT:

To install the Agent for Windows to a 64-bit Run the following command:
computer with publishing enabled
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 Run the following command:
computer and restart the computer
setup.exe /RAWSX64 /S: /BOOT:
automatically

The Agent for Windows is installed on the remote computer in the following
directory:

If you installed the Agent for Windows to <Backup Exec install

a 32-bit computer: path>\Backup Exec\RAWS32

If you installed the Agent for Windows to <Backup Exec install

a 64-bit computer: path>\Backup Exec\RAWSx64

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.
 Installation 82
Methods for installing the Agent for Windows

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:

To uninstall the Agent for Windows from a <Backup Exec install

32-bit computer: path>\Backup Exec\Agents\RAWS32

To uninstall the Agent for Windows from a <Backup Exec install

64-bit computer: path>\Backup Exec\Agents\RAWSX64

2 Open a command prompt, and then type the drive letter that you mapped in
step 1.
3 Run the following command:

To uninstall the Agent for Windows from a setup.exe /RANT32: /S: /U:
32-bit computer:
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 setup.exe /RAWSX64: /S: /U:
64-bit computer:

See “Using a command prompt to install the Agent for Windows on a remote
computer” on page 79.

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 RAWSinst20.htm.
See “About the installation log” on page 98.
 Installation 83
Installing the Remote Administrator

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:
<Backup Exec install path>\Backup Exec\Agents
2 Do one of the following:

To install the Agent for Windows on a In the RAWS32 directory, double-click

32-bit computer setupaa.

To install the Agent for Windows on a In the RAWSX64 directory, double-click

64-bit computer setupaax64.

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
<Backup Exec install path>\Backup Exec\Agents
2 Do one of the following:

To uninstall the Agent for Windows from a In the RAWS32 directory, double-click
32-bit computer Uninstallaaofo.

To uninstall the Agent for Windows from a In the RAWSX64 directory, double-click
64-bit computer Uninstallaaofox64.

3 Restart the remote computer.

See “Using a command script to install the Agent for Windows” on page 82.

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.
 Installation 84
Installing the Remote Administrator

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 Select the Use the logged on user's credentials as default authentication
(also applicable for smart card users) check box if you want to use the
logged on Windows user's credentials as default authentication for the Remote
Administration Console to log on to the Backup Exec server.
By default, this check box is not selected and you must enter the credentials
to log on to the Backup Exec Server.
This authentication can also be used if you log on to Windows using different
forms of authentication such as smart cards.
7 Click Next.
8 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.

9 Click Next.
10 Review the Backup Exec installation summary, and then click Install.
11 Click Next, and then click Finish to exit the wizard.
See “Running the Remote Administrator” on page 87.
 Installation 85
Installing the Remote Administrator

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.

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:
\be\winnt\install\bex64

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 "<Backup
Exec install path>\Backup Exec".

Table 2-9 Command line switches for Remote Administrator silent mode
installation

Switch Additional Switches Description

/RA: Installs Remote

Administrator using
the options that are
specified with the
additional switches.
 Installation 86
Installing the Remote Administrator

Table 2-9 Command line switches for Remote Administrator silent mode
installation (continued)

Switch Additional Switches Description

/DEST:"drive:\path" Specifies the local

path where Remote
Administrator will be
installed. Otherwise,
the default path
<Backup Exec
install
path>\Backup
Exec is used.

/DOCS: Installs the online

documentation.

/NOINSTALL: Lets you select all

install features
without actually
installing the Backup
Exec software. This
option can be used
with the /CPF: switch.

/CPF:"path\filename.cpf" Creates a file

containing all of the
installation
parameters provided.
Note that the file is
not encrypted, which
exposes parameters
such as the
password.

-? Provides help on all

command-line
operations, usage,
and special switches.

See “Installing Backup Exec using the command line (silent mode)” on page 89.
 Installation 87
Installing the Remote Administrator

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.
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, domain1\howard).
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 83.

To run the Remote Administrator
1 Click Start.
2 Point to Programs, and then click 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.
 Installation 88
Installing the Remote Administrator

3 Select the appropriate options.

Manage services 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.

Server name 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.

User name Enter an administrator user name for the

server to which you want to connect. Enter
the user name using the
Domain\Username format.

You cannot log on to the Remote

Administration Console with a user name
that has a blank password on Windows
Server 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.

Password Enter the password for the user.

Domain Enter the domain to which the user

belongs. Enter the name of the domain that
was used in the User name option.

Connect with the logged on user's Select this check box to connect to the
credentials (also applicable for smart Remote Administration Console using the
card users) logged on Windows user's credentials.
This authentication can also be used if you
log on to Windows using different forms of
authentication, such as smart cards.

The default behavior of this check box

depends on whether you selected this
option during the Remote Administrator
installation.
 Installation 89
Installing Backup Exec using the command line (silent mode)

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.
If you have used the Lock Console feature to lock the Backup Exec console you
need to enter credentials to connect to the Backup Exec server.
See “Locking and unlocking the Backup Exec Console” on page 118.

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 BKPINST20.htm on the
computer where Backup Exec is installed.
See “About the installation log” on page 98.
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:
\be\winnt\install\bex64
 Installation 90
Installing Backup Exec using the command line (silent mode)

4 Type setup /TS: and the appropriate switches. For example:

setup /TS: /USER:<user> /DOM:domain /PASS:password
/SLF:C:\path\slf.slf,C:\path\slf2.slf /S:

See “Command line switches for silent mode installation of Backup Exec”
on page 90.
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:
■ 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 89.

Table 2-10 Command line switches for silent mode installation of Backup
Exec

Switch Additional Switches Description

/TS: Installs Backup Exec using the options

that are specified with the additional
switches. The /USER:user, /DOM:dm,
/PASS:pw switches are required.
 Installation 91
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/USER:user Required. Specifies an existing user,

domain, and password for the Backup
/DOM:dm
Exec system service account. Silent
/PASS:pw 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.

/DEST:drive:\path Specifies the local path where Backup

Exec is installed. Otherwise, the default
path <Backup Exec install
path>\Backup Exec is used.

/DOCS: Installs the online documentation.

 Installation 92
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/BELANG:language 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"

/NOINSTALL: Lets you select all install options without

installing the Backup Exec software.
This option can be used with the /CPF:
switch.

/CPF:path\filename.cpf Creates a file containing all of the

installation parameters provided. Note
that the file is not encrypted, which
exposes parameters.
 Installation 93
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/SLF:slf file Specifies one or more licenses to use

for installing Backup Exec and additional
features. 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:\path\slf1.slf

/SLF:C:\path\slf1.slf,C:\path\ slf2.slf,
C:\path\ slf3.slf
Note: If you install a license for an
feature or agent, you must also type a
switch that specifies the feature or
agent. The switches that specify an
feature or agent are included in this
table.

/DISABLETELEMETRY: Disables the option to send Backup

Exec usage data over the web.

/BOOT: Automatically initiates a restart of the

computer during a silent install or
uninstall.
 Installation 94
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/TD:NEW, ALL, or NONE

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 tape drivers in
Windows 2008 R2, the Windows driver
signing policy must be set to Ignore.
However, for Windows 2008 the driver
installation fails when the signing policy
is set to Ignore. You can install the
drivers using Device Driver Installer
(tapeinst.exe) instead. See your
Microsoft Windows documentation for
more information about the signing
policy.

/DBSERVER:server\instance Installs the Backup Exec Database to

the specified SQL server.

/BACKUPDATA: Specifies if a copy of your current

Backup Exec Database should be stored
during an upgrade of Backup Exec.

/BACKUPDIR: 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.
 Installation 95
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/DBINSTPATH: SQL Express Installs the default instance of SQL

destination folder Express in the specified folder.

/ADVRT:Backup Exec server name Installs the Agent for Windows and
enables publishing.

/DISADVRT: Installs the Agent for Windows without

publishing it.

/SQLXSETUP:SQL Express Install Specifies the location of the

Package language-specific install package for
Microsoft SQL Server 2014 Express with
SP3.

/LOADER: Installs the Library Expansion feature.

This feature is not supported for
Windows Server 2012 or later.

/NFR: Installs the Not For Resale Edition. You

must enter a Not For Resale license to
install this edition.

/TRIAL: Installs the Trial Edition.

/APPLICATIONS: Installs the Agent for Databases and

Applications.

/VRAY Installs the V-Ray Edition. You must

enter a V-Ray license to install this
edition.

/CAPACITY Installs the Capacity Edition. You must

enter a Capacity license to install this
edition.

/CAPACITYLITE Installs the Capacity Edition Lite. You

must enter a Capacity Edition Lite
license to install this edition

/VIRT: Installs the Agent for VMware and

Hyper-V.
 Installation 96
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/ENTSERVER: Installs the Enterprise Server feature.

You must use one or both of the

following switches with the Enterprise
Server feature switch to indicate which
features you want to install.

■ /CASO:
Installs the Central Admin Server
feature.
■ /ADBO:
Installs the Advanced Disk-based
Backup feature.

/ADBO: Installs the Advanced Disk-based

Backup feature.

You must use /ENTSERVER: with this

switch.

/CASO: Installs the Central Admin Server

feature.

You must use /ENTSERVER: with this

switch.

/MMS:CAS server name Creates a managed Backup Exec server

for use with the Central Admin Server
feature.

/CASOPVLLOCAL: <1 or 0> /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:.

/ACCESSCATALOGSANDRESTORE: 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.
 Installation 97
Installing Backup Exec using the command line (silent mode)

Table 2-10 Command line switches for silent mode installation of Backup
Exec (continued)

Switch Additional Switches Description

/NTA: Installs the Agent for Windows.

/NDMP: Installs the NDMP feature.

/RALS: Installs the Agent for Linux.

/DEDUPE: Installs the Deduplication feature.

/VTL: Installs the Virtual Tape Library

Unlimited Drive feature.

/RMAL: Installs the Remote Media Agent for

Linux.

/COPYCONFIG: Installs the Copy Server Configuration

feature.

-? Provides help on all command-line

operations, usage, and special switches.

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
name\slf1.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.
 Installation 98
About the installation log

3 Change to the following directory:

BE\WINNT\INSTALL\Bex64

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
name\slf1.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:
BE\WINNT\INSTALL\Bex64

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:

About the installation log

Backup Exec creates an installation log file, named BKPINST20.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
RAWSinst20.htm is also created.
In addition, the text in the log file uses the following colors so you can identify
warnings and errors:

Table 2-11 Installation log colors

This color Indicates

Black Normal operations

Orange Warning messages

Red Error messages

 Installation 99
Viewing the Installation Summary Report

The BKPINST20.htm file is located in the following location:

For Windows 2008 and later: %ProgramData%\Veritas\Backup Exec\Logs

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 entitlement IDs when you install
additional agents or features. It is also updated when you remove agents or features
from Backup Exec.
The Installation Summary Report is stored in the following location:
For Windows 2008 and later: %programdata%\Veritas\Backup
Exec\Logs\InstallSummary\<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:

To view the Installation Summary Report from Click the Backup Exec button, select
the Administration Console Installation and Licensing, and then select
Installation Summary Report.

To view the Installation Summary Report from On the Home tab, in the Installation and
the Home tab Upgrades group, click Installation
Summary Report.

Repairing Backup Exec

If you have missing or corrupted Backup Exec files or registry keys on the local
Backup Exec server, run the Repair feature. 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.
 Installation 100
Updating Backup Exec with Veritas Update

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 Backup Exec, 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 Veritas Update

Veritas Update provides updates to Backup Exec, and is installed automatically
with Backup Exec.
Veritas Update can be run manually, or can be configured to run automatically every
day at a specific time. It can also be configured to download updates automatically
and raise an alert after the download is complete, or to detect updates and raise
an alert instead of proceeding to download them. Veritas Update is integrated with
Backup Exec, and can only be accessed from within the Backup Exec interface. If
you enable the automatic update feature, you can configure Veritas Update to poll
the main Veritas web server on a scheduled interval. If Veritas Update installs any
files, the BKPINST20.htm installation log file is updated with information about those
files.
If you run Veritas Update through the Remote Administration Console (RAC), please
note the following behaviors:
■ Veritas Update will only download and install updates for the local server on
which RAC is installed, not the remote media server to which the RAC is pointed.
■ Any Veritas Update alerts apply to the remote media server.
■ If you navigate to “Installed Updates” through the RAC interface, you will only
see the updates which have been installed on the remote media server, not the
updates which have been installed on the local RAC server.
 Installation 101
Updating Backup Exec with Veritas Update

■ To view updates which have been installed on the local RAC server, navigate
to the Windows “Programs and Features” control panel.
■ If you change the Veritas Update settings while using the Remote Administration
Console, those settings will be changed on the remote server.
For information about the best practices to use Veritas Update, refer to the Backup
Exec Best Practices.

Note: During the installation and update process, the Backup Exec services are
stopped and started one time during a Veritas Update session, regardless of the
number of updates that are being installed. All selected patches are installed in
order.

Scheduling automatic Backup Exec updates using Veritas

Update
You can schedule Veritas Update to check for updates automatically at a specific
time every day. By default, Veritas Update will check for updates at 10:00 PM.
At the scheduled time, Veritas Update automatically connects to the appropriate
website, and then determines if your files need to be updated. You can configure
Veritas Update to either download updates automatically and raise an alert when
the download is complete, or to detect available downloads, raise an alert notifying
you, and wait for your confirmation to download them.
Backup Exec sends the following Veritas Update alerts:

Table 2-12 Veritas Update alerts

Backup Exec sends this alert When

Veritas Update Informational Alert An update is installed successfully.

Veritas Update Warning Alert An update is installed successfully. However,

you must restart the computer.

Veritas Update Error Alert An update fails to install.

To schedule automatic update downloads using Veritas Update

1 Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2 In the left pane, select Veritas Update.
3 Select Check for updates daily.
 Installation 102
Updating Backup Exec with Veritas Update

4 Enter a new time in the At: field to set the time of day at which Veritas Update
will run. By default, this field is set to 10:00 PM.
5 Select one of the following options to determine what Veritas Update should
do when it detects available updates:
■ If you select Send an alert notification when updates are available, but
do not download or install the update, Veritas Update will send you an
alert when it detects available updates, but will not download or install them.
■ If you select Download updates first, and then send an alert notification,
Veritas Update will download any available updates, then send you an alert
notifying you that updates are ready to be installed.

6 Click OK to close the settings window, or Click here to run Veritas Update
to launch Veritas Update.

Running Veritas Update manually

When you launch Veritas Update, it will automatically search for and display any
available updates.
To download and install updates using Veritas Update, do the following:
1 Click the Backup Exec button, select Installation and Licensing, and then
select Veritas Update. Veritas Update will check for available updates and
display them.
2 Select the check boxes next to the updates that you want to install.
3 Click Install.
4 In the Start Patch Process dialog box, click Yes to continue with the installation
process, or No to cancel.
5 If you clicked Yes in the Start Patch Process dialog box, Veritas Update will
download the update and launch the update installer. Follow the installation
instructions included with the update to complete the installation process.
See “Viewing installed updates” on page 103.
See “Installing updates to the Agent for Windows on remote computers” on page 74.

Application settings for Veritas Update

You can schedule Veritas Update to check for updates for Backup Exec.
See “Updating Backup Exec with Veritas Update” on page 100.
 Installation 103
Viewing installed updates

Table 2-13 Application settings for Veritas Update

Item Description

Check for updates Lets you schedule automatic updates, and then choose the
automatically according to frequency of the updates.
a schedule

Daily Enables Backup Exec to check for new updates every day.
In the At field, enter the time to check for new updates.

Weekly Enables Backup Exec to check for new updates once a week.
In the Every field, select the day of the week on which to
check for updates. In the At field, enter the time to check for
new updates.

Monthly Enables Backup Exec to check for new updates once a

month. In the Every field, select the day of the month on
which to check for updates. In the At field, enter the time to
check for new updates.

Interval Lets you set the date and time that you want Backup Exec
to check for new updates.

Download and install all Enables Backup Exec to download and install all updates
available updates that are available without prompting you first.
automatically

Send an alert when updates Enables Backup Exec to alert you when updates are
are available; do not available. Updates are not downloaded or installed. This
download or install updates option is the default.

If you select this option, you need to run Veritas Update

manually to download and install the available updates.

Viewing installed updates

You can view the updates that are installed on a Backup Exec server. To do this,
you must be logged on with administrator privileges. Click the Backup Exec button,
select Installation and Licensing, and then select Installed Updates.
If a feature pack is installed before another feature pack, the earlier feature pack
is no longer displayed because it is included with the later feature pack.
A hotfix that is offered after the feature pack is released is displayed with the previous
feature pack.
 Installation 104
Uninstalling Backup Exec updates

Table 2-14 Installed Updates options

Item Description

Installed Updates Lists the hot fixes and the service packs that
are installed on the Backup Exec server.

Click here to run Veritas Update Lets you run Veritas Update to install hot fixes
and service packs.

Click here to view available updates Lets you view the hot fixes and service packs
that are available for download.

Uninstalling Backup Exec updates

To uninstall hotfixes or feature packs which you have already installed, you must
use the Windows Programs and Features control panel.
Follow the steps below to uninstall hotfixes or feature packs:
1 Open the Windows Start Menu.
2 Type "Programs and Features" to search for the Programs and Features
control panel. Select the control panel when it appears in the search results.
3 In the left pane of the Programs and Features control panel, click View
installed updates.
4 Scroll to the Backup Exec (TM) entry. Any hotfixes and feature packs which
you have already installed will be listed here.
5 Select a hotfix or feature pack and click Uninstall to begin the uninstallation
process.

Viewing license information

You can view information about the agents and features that are licensed and
installed on a Backup Exec Server.
You can also track your capacity usage and entitlement with Veritas Smart Meter.
Go to the Veritas Smart Meter site to see total amount of data that is backed up.
Ensure that the telemetry is enabled in Backup Exec to see the capacity usage in
Veritas Smart Meter. Backup Exec sends telemetry data periodically. The data that
you see in Smart Meter may not display the current data as Backup Exec refreshes
telemetry periodically.
https://taas.veritas.com/
 Installation 105
Backup Exec license contract information

To view license information

◆ Click the Backup Exec button, select Installation and Licensing, and then
select License Information.

Backup Exec license contract information

After you purchase or import license contracts for Backup Exec, the Veritas
Entitlement Management System will be updated with your license contract
information.
The entitlement associated with the ID contains the following information:
■ Licensing information for the product purchased.
■ Activation information.
■ License information, if it was purchased.
Backup Exec uses the contract expiration information to automatically set Backup
Exec alerts that remind you to renew the license contracts before they expire.
Reminder alerts are set at 30-day, 60-day, and 90-day intervals, based on the
expiration date of the license contract. If you do not renew the license contract, an
alert is sent when the license contract expires.
Based on the expiration date of the license, Backup Exec checks for a license
update in the Veritas Entitlement Management System. If the license expiry period
is greater than 60 days, Backup Exec checks for a license update every 30 days.
If the license expiry period is less than 60 days, Backup Exec checks for a license
update every 7 days. If you want to run a check for a license update in addition to
this check from Backup Exec, go to the Home tab > Support group > and click
Synchronize Entitlements with Veritas Entitlement Management System.
The Licensing Information panel on the Backup Exec console displays the number
of days until the currently installed license contract expires.
To view Backup Exec license contract information
◆ Click the Backup Exec button, select Installation and Licensing, and then
select License Contract Information.
See “Updating expired license contracts” on page 105.

Updating expired license contracts

When your license contracts expire, follow these steps to update them.
 Installation 106
Backup Exec license contract information

Note: You cannot use the Remote Administrator on a remote Windows server or
workstation to update license contracts.

Table 2-15 How to update expired license contracts

Step Additional information

Purchase new license contracts. Contact the reseller.

Get an updated license file. Update your current entitlements with a new
date and a new service contract number.

Launch the installation wizard from the Use the option Install Features and
Backup Exec Administration Console. Licenses on this Backup Exec Server on
the Installation and Licensing menu, which
is accessed from the Backup Exec button.

Use the installation wizard to add the new After you select the expired entitlement IDs
entitlement IDs, and then remove the expired from the list, use the Remove option.
entitlement IDs.

See “Backup Exec license contract information” on page 105.

Managing license contract customer numbers

Backup Exec provides a place where you can store all of your license contract
customer numbers.
You need to provide these numbers when you call technical support.
To manage license contract customer numbers
1 Click the Backup Exec button, select Installation and Licensing, and then
select License 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.
You can find your customer number in the Entitlement Owner box on the
certificate.
■ To remove a customer number, select the number from the list, and then
click Delete.

3 Click Close.
 Installation 107
About upgrading to Backup Exec

About upgrading to Backup Exec

In order to upgrade from older versions of Backup Exec to Backup Exec Update 1
(20.1) or later, you must provide a valid license at the time of the upgrade. Existing
licenses cannot be used to upgrade to the current version, even with a valid
maintenance agreement. You do not need to uninstall the previous version of Backup
Exec before upgrading. The current version will be installed over the previous
version. Different versions of Backup Exec cannot coexist on the same computer.

Note: Backup Exec 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 end-of-life decisions have been made.
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.
See “Using the Migration Report to determine how existing jobs changed after an
upgrade from a previous version of Backup Exec” on page 110.
Backup Exec provides backward compatibility as follows:
■ Backup Exec can communicate with Backup Exec 2014 Remote Agent for
Windows Systems and later.
■ Backup Exec supports side-by-side installations of the Remote Administration
Console for Backup Exec 15 and later. For example, you can have a Remote
Administration Console for Backup Exec 15, Backup Exec 16, and the current
version.
The version of the Backup Exec server being remotely administered must be
same as the version of the Remote Administration Console. For example, for a
Backup Exec 16 server, the Remote Administration Console version must be
16 or its Feature Pack versions.
■ Backup Exec Central Admin Server feature server can communicate with Backup
Exec 16 Feature Pack 2 for the purpose of rolling upgrades.
Before you upgrade Backup Exec, do the following:
 Installation 108
About upgrading to Backup Exec

■ 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 when you upgrade.
When you upgrade, on the Add Licenses panel, the existing licenses are listed.
You can also add new entitlement IDs. Click Next and enter the credentials of
the Veritas User Account that has permissions to the entitlements. Backup Exec
automatically downloads the new license files from the Veritas Entitlement
Management System. If you already have the license file, use the Import
License File button to import the license files.
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 2014 Express
with SP3 setup file for that language from the Microsoft website.

See “Installing Backup Exec by using the Installation Wizard” on page 48.

Transport Layer Security (TLS) 1.2 protocol

Backup Exec only uses the Transport Layer Security (TLS) 1.2 protocol for secure
communications with Backup Exec remote agents because TLS 1.0 has reached
End-of-Life.
If Backup Exec detects remote agents of a version earlier than Backup Exec 15
FP1 that do not support TLS 1.2 in your environment, based on the settings that
you select during patch or upgrades, the backup and restore of such servers may
fail.
It is recommended that you upgrade the remote agents immediately after the Backup
Exec server upgrade for secure communication.
■ Scenario 1: If you are upgrading to the Backup Exec from a version earlier than
Backup Exec 15 FP1:
When you are upgrading Backup Exec, the TLS Protocol pane is displayed.
Select the Allow fallback to TLS v1.0 check box if you cannot upgrade the
 Installation 109
About upgrading to Backup Exec

remote agents immediately. This setting allows Backup Exec to continue using
TLS 1.0 when communicating with older remote agents, so that backups and
restore for these agents work. If you do not select this check box, jobs for the
servers fail until you upgrade the remote agents.
■ Scenario 2: If you are installing a patch for the Backup Exec when you have a
remote agent with a version earlier than Backup Exec 15 FP1:
When you are installing a patch for the Backup Exec, a dialog box is displayed.
Click No, if you cannot upgrade the remote agents immediately. Backup Exec
continues to use TLS 1.0 for communicating with older remote agents so that
backups and restore continue to work. Click Yes to use TLS 1.2. Jobs for the
servers fail until you upgrade the remote agents.
In both upgrade and patch install scenarios, if you do not fallback to TLS 1.0
communicating with older remote agents, the backup and restore jobs will fail until
the remote agents are upgraded.
During the patch or upgrade installation, the following registry value is set to 1 if
you allow fallback to TLS 1.0.
Registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Backup Exec For
Windows\Backup Exec\Engine\Backup

ValueName: AllowTLSFallback

Value type: DWORD (32-bit)

After upgrading the Backup Exec remote agents, you can change the registry value
to always use TLS 1.2.
To use TLS 1.2, change the ValueName: AllowTLSFallback to 0.
If you continue to use TLS 1.0, the Backup Exec media server displays an alert
message every week. If you do not want Backup Exec to display the alert message,
upgrade the older agents to the latest version of Backup Exec. You can also disable
the alert message by editing the following registry key:
Registry Location: HKEY_LOCAL_MACHINE\Software\Veritas\Backup Exec For
Windows\Backup Exec\Server

ValueName = SupressTLSAlert

Value type: DWORD (32-bit)

When you set the value as 1, the weekly alerts are disabled.

Upgrade checklist for Backup Exec

Before you upgrade from a previous version of Backup Exec to the current version,
do the following:
 Installation 110
About upgrading to Backup Exec

■ Ensure that your backups are up to date. It is recommended that you always
run full backups before and after you upgrade the applications or operating
systems on any backup sources.
■ 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.
■ 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 entitlement IDs or License Files are available. You must enter
new Backup Exec license information during the upgrade.
For details on updated licensing, see the Backup Exec Licensing Guide
■ Review the following topics in the Backup Exec Administrator's Guide:
■ System requirements for Backup Exec
See “System requirements for Backup Exec” on page 46.
■ 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 335.
■ About upgrading from previous versions of Backup Exec
See “About upgrading to Backup Exec” on page 107.

■ Review the document Best practices for installing Backup Exec on the Backup
Exec knowledge base.

Using the Migration Report to determine how existing jobs changed

after an upgrade from a previous version of Backup Exec
When you upgrade to Backup Exec, 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.
It is recommended 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.
 Installation 111
Post-installation tasks

The Migration Report is stored in the following path:

<Backup Exec install path>\Backup
Exec\Data\MigrationReportFiles\Data-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.

To view the Migration Report

◆ Do one of the following:

To view the Migration Report from the Click the Backup Exec button, select
Administration Console Installation and Licensing, and then
select Migration Report.

To view the Migration Report from the On the Home tab, in the Installation and
Home tab Upgrades group, click Migration Report.

See “Configuring the Home tab” on page 122.

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 317.
■ 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 416.
■ Understand the default media set for tape media and its four-week overwrite
protection period.
See “Default media sets” on page 402.
■ Understand Data Lifecycle Management.
 Installation 112
Uninstalling Backup Exec

See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 335.
■ Learn about creating new media sets with different retention periods.
See “Creating media sets for tapes” on page 410.
■ 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 655.
■ Configure a secure connection to the Backup Exec Database
See “Configuring encryption for the connection to the Backup Exec Database”
on page 604.

Uninstalling Backup Exec

Use Microsoft’s Add or Remove Programs feature 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 tape class drivers. If you reinstall Backup
Exec and want to use 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 Backup Exec™, 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 features from the local Backup Exec server”
on page 113.
 Installation 113
Uninstalling Backup Exec using the command line

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.
3 Change to the following directory:
\be\winnt\install\bex64

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 89.

Uninstalling Backup Exec features from the local

Backup Exec server
The Installation Wizard removes Backup Exec features from the local Backup Exec
server. All corresponding files, registry keys, and configurations are removed.

Note: License files remain on the server after features are uninstalled. Do not delete
the license files while Backup Exec is installed. Deleting the license files causes
the trial version to go into effect.

To uninstall Backup Exec features from the local Backup Exec server
1 Click the Backup Exec button, select Installation and Licensing, and then
select Install Features and licenses on this Backup Exec Server.
2 On the Add Licenses panel, click Next.
3 On the Configure Features panel, deselect the agents or features that you
want to uninstall, then click Next.
 Installation 114
Uninstalling Backup Exec features from the local Backup Exec server

4 Uncheck the check box for the language that you want to remove.
5 On the Choose Languages panel, click Next.
6 If you are prompted to enter credentials for the Backup Exec service account,
type the correct credentials, and then click Next.
7 Read the installation summary, and then click Install to start the process.
8 When the Installation Wizard has completed, click Finish.
See “Uninstalling Backup Exec” on page 112.
 Chapter 3
Getting Started
This chapter includes the following topics:

■ About the Backup Exec Administration Console

■ Displaying the version information for Backup Exec

■ Locking and unlocking the Backup Exec Console

■ 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 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.
 Getting Started 116
About the Backup Exec Administration Console

Figure 3-1 Backup Exec Administration Console

The administration console screen includes the following components:

Table 3-1 Administration console components

Item Description

Backup Exec The Backup Exec button displays on the upper left side of the
button 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.
 Getting Started 117
About the Backup Exec Administration Console

Table 3-1 Administration console components (continued)

Item Description

Tabs 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
■ Instant Cloud Recovery. Manage disaster recovery with Azure
Site Recovery. You can monitor the replication health of virtual
machines and enable replication of VMware and Hyper-V virtual
machines, whose hosts are configured with Azure Site Recovery.

Groups 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.

Columns 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.

Selection pane Select items to work with, such as servers to back up or restore.
 Getting Started 118
Displaying the version information for Backup Exec

Table 3-1 Administration console components (continued)

Item Description

Details pane 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.

Status bar 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.

Refresh Click F5 to refresh the user interface on the administration console.

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.

Locking and unlocking the Backup Exec Console

To lock the Backup Exec session that you are working on and secure the Backup
Exec console from unauthorized access, you can use the Lock Console feature.
You can only enable this feature, when you select the Secure the Backup Exec
console check box in the Network and Security settings. The Lock Console
feature is now enabled.
If you do not select the Secure the Backup Exec console check box, the Lock
Console feature is grayed out.
 Getting Started 119
How to sort, filter, and copy information on the Backup Exec Administration Console

See “Changing network and security options for Backup Exec” on page 614.
After you lock the Backup Exec user interface, you must enter the password to
connect to the Backup Exec console, Unless you unlock the Backup Exec console,
you cannot perform any tasks in the Backup Exec user interface.
Backup Exec has other utilities that can be launched from the console and have
separate user interfaces. If any of these utilities are open when you lock the console,
you can continue to use them. For example, Quick Assist, Install Options and
Licenses, Help, Backup Exec Services, Install Agents, create Disaster Recovery
Disk, and so on.
In case of rolling upgrade, if you have an earlier version of MMS and an updated
version of CAS, and you connect to MMS from CAS, this feature is available but in
disabled state (grayed out).
To lock and unlock the Backup Exec console
1 Click the Backup Exec button and select Configuration and Settings > Backup
Exec Settings > Network and Security.
2 Select the Secure the Backup Exec console check box.

Note: By default, this check box is not selected.

3 Click the Backup Exec button, and then select Lock Console.
The Connect to Backup Exec server dialog box is displayed. The server
name and user name is disabled.
4 Enter the password for the user name that you used to log on to the Backup
Exec console.
5 Click Connect.
The state of the tasks before you locked the Backup Exec console resumes.
You can now continue using Backup Exec.

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.
 Getting Started 120
How to sort, filter, and copy information on the Backup Exec Administration Console

■ Specify a sort order for the columns that appear in the views.
■ 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:

To customize a view of the computers in On the Backup and Restore tab, in the
the list of servers Views group, click Sort and Filter.

To customize a view of the storage devices On the Storage tab, in the Views Group,
click List, and then click Sort and Filter.

2 Do any of the following:

To select a default configuration, such as Click Configurations and select a

Servers with Failed Backups, or to select configuration.
a configuration that you created and saved
previously

To specify an ascending or descending Click Sort, choose the options as

sort order for the columns appropriate, and then click OK.

To specify one or more columns to filter for Click Filter, choose the options as
specific values appropriate, and then click OK.

To specify the columns that you want to Click Columns, choose the options as
display and the order in which they should appropriate, and then click OK.
appear

To create and save a configuration Click Save, choose the options as

appropriate, and then click OK.
 Getting Started 121
Customizing views on the Backup Exec Administration Console

To edit a configured view

1 Do one of the following:

To edit a configuration from the Backup On the Backup and Restore tab, in the
and Restore tab Views group, click Sort and Filter.

To edit a configuration from the Storage On the Storage tab, in the Views group,
tab click Sort and Filter.

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:

To delete a configuration from the Backup On the Backup and Restore tab, in the
and Restore tab Views group, click Sort and Filter.

To delete a configuration from the Storage On the Storage tab, in the Views group,
tab click Sort and Filter.

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.

Table 3-2 Views on the Backup Exec Administration Console

View Description

Standard Displays the information in a view that provides descriptive text.

 Getting Started 122
Configuring the Home tab

Table 3-2 Views on the Backup Exec Administration Console (continued)

View Description

Compact Displays the information in a view that conserves space.

Tree Displays the items in a hierarchical view. This view is disabled for
the list of servers on the Backup and Restore tab.

List 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.

To customize views on the Backup Exec Administration Console

◆ On the Backup and Restore tab, the Job Monitor tab, the Storage tab, or
the Instant Cloud Recovery 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 In the Instant Cloud Recovery group, view the DR (Disaster Recovery) and
Failover readiness status for a configured Azure Recovery Services Vault.
4 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.

Restoring the Home tab's default layout

You can quickly restore the Home tab to its default configuration at any time.
 Getting Started 123
Configuring the Home tab

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

Item Description

One Column Displays the Home tab items in one column.

Two Columns Displays the Home tab items in two columns.

Narrow/Wide Displays the Home tab items in two columns with a narrow
panel and a wide panel.

Three Columns Displays the Home tab items in three columns.

Reset Home Tab Restores the contents of the Home tab to the default
configuration.

System Health group

The items in the System Health group provide overviews of alerts, backup jobs,
backup size data, storage status, and Simplified Disaster Recovery. You can select
the following items to display on the Backup Exec Home tab.

Table 3-4 System Health group items

Item Description

Active Alerts 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
 Getting Started 124
Configuring the Home tab

Table 3-4 System Health group items (continued)

Item Description

Alert History Lets you view the property and response

information for alerts.

Backup Status Provides a summary view of the backup job

status for the servers that are backed up or
available for backup.

Backup Size 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.

Storage Status 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.

Simplified Disaster Recovery 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 812.

Database Encryption Key Provides a status for whether the database

encryption key has been exported.

If you have not exported the database

encryption key, you should do so to ensure
that you can access the Backup Exec
Database later. You are required to provide
the database encryption key for disaster
recovery and migration scenarios, for
example.

See “Exporting the Backup Exec Database

encryption key” on page 601.
 Getting Started 125
Configuring the Home tab

Table 3-4 System Health group items (continued)

Item Description

Virtual Machine Backups Lists the number of virtual machines that are
being backed up with the virtual-based
backup method and with the agent-based
backup method.

The information is updated when a backup

job is created, deleted, or edited. It is also
updated when the user interface is refreshed
or relaunched.
 Getting Started 126
Configuring the Home tab

Table 3-4 System Health group items (continued)

Item Description

Instant Cloud Recovery Status

 Getting Started 127
Configuring the Home tab

Table 3-4 System Health group items (continued)

Item Description

Provides Azure Protection, Failover

Readiness, and DR (Disaster Recovery)
Health status.

■ Protection
The pie graph displays the protection
status of the configured virtual machines
in the Azure Recovery Services Vault. You
can view the number of protected and
unprotected virtual machines. For
protected virtual machines, the status can
be one of the following:
■ Protected
■ Unprotected
■ Failover Readiness
The pie graph displays whether virtual
machines are ready for failover.
Failover readiness is displayed only for
virtual machines of an Azure Recovery
Services Vault that are protected. For
protected virtual machines, the status can
be one of the following:
■ Test Recommended: No successful
test failover of the virtual machine after
it was protected. Test failover
recommended.
■ Performed Successfully: One or
more successful test failovers.
■ Not Applicable: Virtual machine is not
eligible for a test failover.
■ Disaster Recovery Health (DR Health)
The pie graph displays the disaster
recovery status of virtual machines.
DR Health is displayed only for virtual
machines of an Azure Recovery Services
Vault that are protected. For protected
virtual machines, the status can be one
of the following:
■ Critical: One or more critical
replication errors are detected. These
errors indicate that replication is either
stuck, or not progressing as fast as the
 Getting Started 128
Configuring the Home tab

Table 3-4 System Health group items (continued)

Item Description

data change rate for these virtual

machines.
■ Warning: One or more warnings are
detected that may impact replication
or indicate that replication progress is
slow for these virtual machines.
■ Healthy: Replication is in progress for
these virtual machines and no error or
warnings are detected.
■ Not Applicable: Virtual machines are
not in replication mode. For example,
virtual machines that are failed over.

See “About Instant Cloud Recovery”

on page 734.

Licensed Status Provides a summary of the licensed usage

status on the Backup Exec server.

For more information, refer to the Licensing

guide.

Support group
The items in the Support group provide technical support, documentation, licensing
contracts, and the RSS Reader resources. You can select the following items to
display on the Backup Exec Home tab.

Table 3-5 Support group items

Item Description

Technical Support 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
■ Remote Assistance
■ Register to receive notifications
■ Get Backup Exec updates
 Getting Started 129
Configuring the Home tab

Table 3-5 Support group items (continued)

Item Description

Documentation 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)

Licensing Information Provides the following licensing options to

help you manage license contracts and
licenses:

■ Synchronize Entitlements with Veritas

Entitlement Management System
■ View license information
■ View license contract information
■ Purchase or renew licenses
■ Verify that Entitlements are updated
to reflect the license renewal on
Veritas Entitlement Management
System.
■ Update the installed license keys.
■ View licensing process information

RSS Reader Lets you view and add Backup Exec and RSS
feeds.

Installation and Upgrades 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
from a previous version of Backup Exec”
on page 110.

See “Viewing the Installation Summary

Report” on page 99.
 Getting Started 130
Configuring the RSS Reader

Configuring the RSS Reader

You can customize the RSS Reader and select the default Backup Exec feeds that
display in the reader. You can add additional Backup Exec RSS feeds or remove
RSS feeds.
The 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 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 RSS Reader
1 On the Home tab, in the Support group, select the RSS Reader check box.
2 In the RSS Reader, click the arrow next to the RSS feed that contains the
article.
3 Click the hyperlink for the article that you want to open.
The 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 RSS feeds to the RSS Reader
1 On the Home tab, in the Support group, select the RSS Reader check box.
2 In the RSS Reader, click the pencil icon to add an RSS feed.
3 Enter any of the following:

URL Indicates the location of the RSS feed that

you want to add to the RSS Reader.

Name Indicates the name of the RSS feed that

you want to display in the RSS Reader.

Click here to see more RSS feeds Shows a list of RSS feeds that you can add
to the RSS Reader.

4 Click OK.
 Getting Started 131
Creating a disaster preparation plan (DPP)

To remove an RSS feed from the RSS Reader

1 On the tab, in the Support group, select the RSS Reader check box.
2 Do one of the following:

To remove a default Backup Exec RSS Clear the check box of the Backup Exec
feed RSS feed.

To remove an RSS feed that you added to Click the red X next to the name of the
the RSS Reader RSS feed.

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:
■ Automated recovery. Backup Exec’s Simplified Disaster Recovery (SDR) feature
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, refer to the
following sections:
See “Performing manual disaster recovery of a local Backup Exec server on a
Windows computer” on page 868.
See “Performing manual disaster recovery of a remote Backup Exec server or
remote agent on a Windows computer” on page 873.
While environments vary in different organizations, consider the following elements
when creating a comprehensive DPP.
 Getting Started 132
Creating a disaster preparation plan (DPP)

Table 3-6 Key elements of a DPP

Element Description

Hardware protection 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.

The ability to maintain Make sure that proper precautions are taken by everyone to
business operations during a implement plans for network interruptions. For example, the
disaster period 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.

A sound backup strategy. A well-designed backup strategy that includes a strong media
rotation scheme plays a key role in quickly restoring your file
server.

Off-site and duplicate stage It is imperative that you regularly move the backed-up data
backups. 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.

Effective DPP management 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.

See “Getting started with backups” on page 133.

 Getting Started 133
Getting started with backups

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

Step Description

1. Configure storage 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 448.

2. Configure Backup You can use the default Backup Exec logon account, which is the
Exec logon system logon account for the Backup Exec server.
accounts
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 655.

 Getting Started 134
Getting started with backups

Table 3-7 Getting started with backups (continued)

Step Description

3. Run a backup job You can back up any of the computers on which you installed the
appropriate Backup Exec agent, such the Agent for Windows.

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 153.

4. Create the By default, Backup Exec selects all the data on a computer for backup,
Simplified Disaster including the critical system components that you need to perform a
Recovery disk full system restore by using SDR. SDR-enabled backups are those
image 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 820.

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 827.

 Chapter 4
Backups
This chapter includes the following topics:

■ How to prepare for your first backup with Backup Exec

■ Improving backup performance in Backup Exec

■ Troubleshooting backup performance

■ 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

 Backups 136

■ Excluding files from backups

■ Including specific files with a backup job's backup selections

■ 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
 Backups 137
How to prepare for your first backup with Backup Exec

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?
If you encounter degraded performance in your backup or restore jobs, follow the
troubleshooting steps in the following sections to identify and resolve the issues.
See “Improving backup performance in Backup Exec” on page 138.
See “Troubleshooting backup performance” on page 141.
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 145.
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 317.
■ Set up storage device pools to load-balance jobs.
See “Creating storage device pools” on page 438.
■ Create media sets to manage data retention for tape cartridge media.
See “Default media sets” on page 402.
■ Configure deduplication disk storage to optimize storage and network bandwidth.
See “About the Deduplication feature” on page 921.
 Backups 138
Improving backup performance in Backup Exec

Improving backup performance in Backup Exec

Backup operations run in a group of systems. These systems can be compared to
pipelines of various sizes, from the disk containing the data all the way to the backup
destination. If any of these pipelines are constricted, they can become bottlenecks
that cause the entire backup process to slow down. The troubleshooting steps in
this section can help you identify bottlenecks in your backup or restore operations.
Some variables which can affect backup or restore performance include:

Item Description

Hardware Some hardware-related variables which can affect performance

include:

■ Speed of the disk controller

■ Improper cabling or termination
■ Hardware errors that are caused by the disk drive, tape drive,
disk controller, or SCSI bus

Confirm that the controller is rated for the tape backup hardware.
If it is not, you may experience unexpected performance
limitations.
Confirm that the SCSI BIOS Settings are set as follows:

■ Initiate Wide Negotiation is set to Yes when the tape device

is connected to a 68-pin wide SCSI Cable Connector
■ Tape drives are not connected to a SCSI Raid Controller

System The capacity and speed of the media server performing the
backup, or the remote system being backed up, significantly affect
performance. System activity during the backup also affects
performance. Fragmented disks take a longer time to back up.
Heavily fragmented hard disks not only affect the rate at which
data is written to tape, but also affect overall system performance.
Fragmented files take longer to back up because each segment
of data is located at a different location on the disk. This
fragmentation increases the time that is required to access the
data. Make sure to defragment disks on a regular basis.

Memory The amount of available memory affects backup speed. Insufficient

memory, improper page file settings, or a lack of available free
disk space can all cause excessive paging and slow performance.
Make sure that every program and every process release the
memory that it allocates when it starts. If a program or process
does not release as much memory as it originally allocated, a
memory leak occurs.
 Backups 139
Improving backup performance in Backup Exec

Item Description

File types An average file compresses at a 2:1 ratio when it is compressed

using hardware compression. Higher and lower compression
ratios occur depending on the type of files being backed up. If no
compression is used, the tape device performs at its rated speed.
Average compression ratios can double the backup speed. Image
and picture files are fully compressed on disk. Hardware
compression is performed by the tape device and not the backup
software.

Compression Successful compression can increase the tape drive's data transfer
rate up to twice the native rate. Compression can be highly
variable depending on the input data. Image files from a graphical
program might compress at 4.5:1 or more, while binary files might
compress at only 1.5:1. Data that has already been compressed
or encrypted may expand by about five percent if you attempt to
compress it further. This data expansion can reduce drive
throughput.

Files The total number of files on a disk and the relative size of each
file affects backup performance. Disks containing fewer files, but
where each file is large, run backups quickly. Backups run slower
if a disk contains many small files. A large number of files which
reside in the same directory path can be backed up more
efficiently than files in multiple directory locations.

Block size Larger block sizes can improve the compression ratio, which helps
the drive achieve better throughput and more tape capacity. Make
sure that the block sizes and buffer sizes are set properly.
Throughput increases in proportion to the compression achieved,
until you reach the drive's maximum throughput. Do not increase
the block size beyond the default settings.
 Backups 140
Improving backup performance in Backup Exec

Item Description

Network The physical connection to a remote disk limits that disk's backup
speed. The rate at which a remote server's hard disks can be
backed up depends on the following factors:

■ The make and model of network cards.

■ The mode and frame type configuration for the adapter.
■ The connectivity equipment.
■ Windows Settings.
■ Location of the drives. Local disk drives on the media server
can usually be backed up faster than remote servers across
a network.

A common cause of slow network backups is networking

configuration. Features such as "full-duplex" and "auto-detect"
may not be fully supported in every environment. To improve
throughput, manually set the speed to 100 MB and the duplex to
half/full for the server side. Find out which Ethernet port the server
is connected to on the switch, and set the SWITCH PORT setting
to 100 MB and half/full duplex. Do this for the backup server
switch port, and any switch ports for computers being backed up.
Note: When a hub is in place instead of a switch, full duplex may
not be supported. See the Original Equipment Manufacturer for
details on device features.

Note: Both the switch and the network card must have matching
settings. For instance, if the switch port is set to 100 half, the NIC
for the server should also be set to 100 half.

If a full duplex backup is slower than a half duplex backup, full

duplex may not be supported for your combination of NIC, driver,
and switch. Contact the NIC and switch manufacturer for updated
drivers, firmware, or other support documentation.

The NIC driver can be a common cause of slow throughput. The

NIC driver can be easily overwritten by an operating system
service pack. If a service pack has been applied and the driver
has been overwritten, reinstall the Original Equipment
Manufacturer driver.
 Backups 141
Troubleshooting backup performance

Item Description

Debugging Debugging that is enabled for troubleshooting purposes can also

affect system performance. Debugging that occurs through the
Services applet is temporary. Cycle the services or restart the
computer to stop the debugging. Debugging configured through
the Windows Registry allows for continuous debugging. Leaving
the services in debugging mode causes the logs to accumulate.
To improve performance, either take the services out of debugging
mode when the problem is resolved, delete the older debug files,
or compress the logs directory.

Backup Exec Database Installing the Backup Exec Database (BEDB) to an existing SQL
instance that other applications use can also degrade
performance. This is particularly relevant in a Central
Administration Server (CAS) environment. Other applications may
cause resource issues and use all the available resources within
the instance.

Troubleshooting backup performance

You can perform several steps to identify the causes of any Backup Exec job
performance issues that you encounter. This section examines performance
troubleshooting for the following job types:
■ Local backup to disk
■ Remote Backup to disk
■ Local backup to tape
■ Remote Backup to tape

Local backup to disk

1. Get a baseline. Review previous jobs in the Job History window of the Job
Monitor tab. Note both the speed of previous jobs and the overall duration of
these backups. Observe the total time that jobs take to complete, rather than
the actual byte count rates. If current jobs take longer to complete than previous
jobs, or do not meet speed expectations, continue troubleshooting.
2. Narrow down the problem. If the backup job includes multiple drives or agents,
split the job up into separate jobs for each of those drives and agents. You can
then review the performance of each drive or agent separately. To split up a
backup job, click on the Backup Exec button, select the C$ drive, schedule the
job, and click Submit. If performance is slow only for a particular job, continue
troubleshooting that job.
 Backups 142
Troubleshooting backup performance

3. If a particular job still shows slow performance, split the job again to further
determine which part of the data most affects the job's performance.
A section of data with many small files and directories will negatively impact
performance. This performance impact is normal behavior.
Check whether the data is redirected somewhere else. Some file systems allow
a directory to remotely mount data. The files in these directories can be located
on remote servers, which may degrade performance for the entire backup.
4. Test backup-to-disk (B2D) throughput. Use Windows to copy at least 2 GB of
data in the backup job to the B2D disk. Compare the performance of the
Windows copy to the performance of the backup. If the performances of both
are comparable, the performance bottleneck is likely in the disk subsystem in
which the B2D folders reside. Move the B2D folders to a faster disk subsystem,
or continue troubleshooting.
5. Test system throughput. If your job is file-based, instead of based on an
Exchange, SQL, or other type of database backup, create a similar backup in
NTBackup (Windows Backup) and perform a backup to disk. Compare the
performance of the NTBackup job to the performance of the Backup Exec job.
If you need to back up an Exchange, SQL, or other database, create a
backup-to-disk job in Backup Exec that backs up 2 GB of data to wherever that
database agent resides. Perform the same test with NTBackup. Compare the
performance of both backups. If performance rates are similar, then Backup
Exec is performing at the capacity of the system.

Remote backup to disk

1. Get a baseline. Review previous jobs in the Job History window of the Job
Monitor tab. Note both the speed of previous jobs and the overall time that is
required for these backups. Observe the total time that jobs take to complete,
rather than the actual byte count rates. If current jobs take longer to complete
than previous jobs, or do not meet speed expectations, continue
troubleshooting.
2. Narrow down the problem. If your job includes multiple drives or agents, split
the job up into separate jobs for each of those drives and agents. You can then
review the performance of each drive or agent separately. To split up a backup
job, click on the Backup Exec button, select the C$ drive, schedule the job,
and click Submit. If performance is slow only for a particular job, continue
troubleshooting that job.
3. If a particular job still shows slow performance, split the job again to further
determine if any particular part of the data affects performance. A section of
data with many small files and directories negatively affects performance. This
performance impact is normal behavior.
 Backups 143
Troubleshooting backup performance

Check whether the data is redirected somewhere else. Some file systems allow
a directory to remotely mount data. The files in these directories can be located
on remote servers, which may degrade performance for the entire backup.
4. Test network throughput. Copy between 500 MB and 1 GB of data from the
backup server to the remote server. Note how long the copy operation takes
to complete. You can perform this copy by creating a path to another server.
In the Windows command line, type <\\remote servername\c$>. When the
drive is displayed, copy the data.
Follow this same procedure to copy data from the remote server to the backup
server, and note how long the operation takes to complete.
Compare the speed of both of these network tests with Backup Exec's
performance. If Backup Exec performance is slower than the file copy tests,
the network is likely not the bottleneck.
If the network is not the bottleneck, consider performing the same test to a
different remote server, or between two different servers. This can help
determine if the performance issue is associated with the network in general,
or a particular server on the network. If you do not find any network performance
issues, continue to the next step.
5. Test system throughput. Try to back up the remote server with NTBackup
(Windows backup). If the remote server is not visible in NTBackup, create a
mapped drive to the server's drive and try to back up at least 2 GB of data.
Compare the NTBackup logs to the Backup Exec logs and identify any
performance differences.

Local backup to tape

1. Get a baseline. Review previous jobs in the Job History window of the Job
Monitor tab. Note both the speed of previous jobs and the overall duration of
these backups. Observe the total time that jobs take to complete, rather than
the actual byte count rates. If current jobs take longer to complete than previous
jobs, or do not meet speed expectations, continue troubleshooting.
2. Clear any temporary hardware glitches. Turn off the power to the server, tape
drive, or tape library, then turn it on again. Turn off the backup server first, then
the tape drive or library. Wait a few seconds, then turn on the tape drive or
tape library. When the tape drive or tape library is ready, turn on the server.
Run the backup job again and examine its performance. If the performance
issue persists, continue troubleshooting.
3. Check the SCSI subsystem. Slow performance can be caused by the disk
drive, the tape drive, the disk controller, the SCSI bus, or improper cabling or
termination. Ensure that the following are true:
 Backups 144
Troubleshooting backup performance

■ The controller is rated for the tape backup hardware.

■ The SCSI BIOS Settings are set properly.
■ Initiate Wide Negotiation is set to Yes when the tape device is connected
to a 68-pin-wide SCSI Cable Connector.
■ Tape drives are not connected to a SCSI Raid Controller.
The performance of the verify operation shows the health of the SCSI
subsystem. Because the verify operation only reads data and performs
in-memory operations on the media server, the speed of the SCSI subsystem
limits the verify operation's performance. You can examine the performance
of the verify operation by examining the job logs of any jobs which include a
verify operation. If the verify speeds are slow, the SCSI subsystem is likely the
performance bottleneck.
4. Split the job up into smaller jobs to identify which agents or features might
affect performance. If any of the smaller jobs show performance issues, continue
troubleshooting that job.
5. If a particular job still shows slow performance, split the job again to further
determine if any particular part of the data negatively affects performance. A
section of data with many small files and directories negatively affects
performance. This performance impact is normal behavior.
Determine whether the data is redirected somewhere else. Some file systems
allow a directory to remotely mount data. The files in these directories can be
located on remote servers, which may degrade performance for the entire
backup.
6. Test system throughput. Try to back up the remote server with NTBackup
(Windows backup). If the remote server is not visible in NTBackup, create a
mapped drive to the server's drive and try to back up at least 2 GB of data.
Compare the NTBackup logs to the Backup Exec logs and identify any
performance differences.
7. Successful compression can increase the tape drive's data transfer rate to
twice the native rate. Compression performance can be highly variable
depending on the input data. Image files can compress at a ratio of 4.5:1 or
more. Binary files may compress at only a 1.5:1 ratio. Data that has already
been compressed or encrypted may expand by about five percent if you attempt
to compress it further. This expansion can reduce drive throughput.
If hardware or software compression does not perform as expected, switch to
the other type of compression. You can switch compression types by editing
the backup job properties, clicking on General under Settings, then selecting
a different type of compression under the Compression Type menu.
 Backups 145
Required user rights for backup jobs

Remote backup to tape

1. Perform any of the troubleshooting steps for Local backup to tape given
above. You can also perform the following steps.
2. Test network throughput. Copy between 500 MB and 1 GB of data from the
backup server to the remote server and note the duration of the copy operation.
To do this, create a path to another server. In the Windows command line, type
<\\remote servername\c$>. When the drive is displayed, copy the data.

Follow this same procedure to copy data from the remote server to the backup
server, and note how long the operation takes to complete.
Compare the speed of both of these network tests with Backup Exec's
performance. If Backup Exec performance is slower than the file copy tests,
the network is likely not the bottleneck.
If the network is not the bottleneck, you can perform the same test to a different
remote server, or between two different servers. This may help you determine
if the performance issue is associated with the network in general, or with a
particular server on the network. If you do not find any network performance
issues, continue to the next step.
3. Test system throughput. Try to back up the remote server with NTBackup
(Windows backup). If the remote server is not visible in NTBackup, create a
mapped drive to the server's drive and try to back up at least 2 GB of data.
Compare the NTBackup logs to the Backup Exec logs and identify any
performance differences.

Note: If remote backups are not possible with NTBackup, open NTBackup
locally on the remote server and run a local backup job there. Use Backup
Exec to back up the same data to disk, and compare the performance of both
backups. In most cases, Backup Exec jobs which back up to disk run faster
than those that back up to tape.

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.
■ Back up files and directories.
■ Restore files and directories.
 Backups 146
About the list of servers on the Backup and Restore tab

■ 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 667.
See “Backup Exec logon accounts” on page 655.

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
■ Backup selections
■ Active alerts
■ Status
■ Last seven days of backup jobs
■ Last backup
■ Next backup
■ Percent complete
 Backups 147
Adding servers that you want to back up to the list of servers on the Backup and Restore tab

■ 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 147.
See “Removing servers from the list of servers on the Backup and Restore tab”
on page 148.

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.
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 611.

See “About the list of servers on the Backup and Restore tab” on page 146.
 Backups 148
Removing servers from the list of servers on the Backup and Restore tab

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 CAS 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 1307.

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 146.

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 153.
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.
 Backups 149
Hiding or viewing server groups on the Backup and Restore tab

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:

To filter servers by type In the Server type field, select the type of server for
which you want to search.

To filter servers by data 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 name In the Name contains field, type all or part of the server
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 149.
See “Adding servers to a server group” on page 150.
See “Removing servers from a server group” on page 150.
See “Editing a server group” on page 151.
See “Moving servers to the Retired Servers server group” on page 151.
See “Removing server groups from Backup Exec” on page 153.

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.
 Backups 150
Adding servers to a server group

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 148.

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.
See “Creating a server group” on page 148.

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.
 Backups 151
Editing a 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 148.

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:

To change the server group's In the Group name field, type the new name for the
name server group.

To change the server group's In the Description field, type the new description for
description the server group.

4 Click OK.
See “Creating a server group” on page 148.

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.
 Backups 152
Moving retired servers back to the All Servers server group

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:

To filter servers by type In the Server type field, select the type of server for
which you want to search.

To filter servers by data 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 name In the Name contains field, type all or part of the server
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 148.

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 151.
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.
 Backups 153
Removing server groups from Backup Exec

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 148.

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 148.

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.

Table 4-1 Backup definition contents

Item Description

Backup selections Backup selections include any servers, volumes, or data that
you have selected to back up.
 Backups 154
Backing up data

Table 4-1 Backup definition contents (continued)

Item Description

Job templates 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 183.

Stages 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 or create virtual
machines with your backup data.

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:
 Backups 155
Backing up data

■ 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 597.

Note: You cannot back up multiple servers with a synthetic backup job or a
conversion to virtual job.

■ 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 management 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 335.

■ 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.
 Backups 156
Backing up data

■ 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.
For information about the best practices to use backup jobs, refer to the Backup
Exec Best Practices.
See “Methods for installing the Agent for Windows” on page 68.
To back up data
1 Select one of the following methods to back up data:

To create recurring backup Complete the following steps:

jobs
■ 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 one-time backups 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.
 Backups 157
Backing up data

To create a new backup Complete the following steps:

definition using the settings
■ On the Backup and Restore tab, right-click the
from an existing backup
server or servers that you want to back up.
definition
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 backup definition Complete the following steps:

for a server group
■ 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.

2 In the Name field, type a name for the backup definition.

3 In the Description field, type a description for the backup definition.
 Backups 158
Backing up data

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.
 Backups 159
Backing up data

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 179.

7 (Optional) To prioritize the backup of specific volumes or virtual machines,

select the item, and then click Tag as business-critical.
See “About selecting data to back up ” on page 165.
8 Click OK.
 Backups 160
Backing up data

9 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

10 In the left pane, click Schedule, and then select when you want the backup
job or jobs to run.
11 In the left pane, click Storage, and then select the storage device that you
want to use for the backup job or jobs.
 Backups 161
Backing up data

12 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.

Network Select this option to specify the network interface that

Backup Exec uses to access remote computers.

See “Configuring network options for backup jobs”

on page 198.

Notification Select this option to configure Backup Exec to notify

specified recipients when the backup job is completed.

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 305.

Test Run Select this option to configure a test job that

automatically tests storage capacity, credentials, and
media integrity.

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 562.

Verify Select this option to create a job that automatically

verifies whether all of the data was successfully backed
up when the job is completed.

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 563.
 Backups 162
Backing up data

Instant GRT Select this option to configure the Instant GRT or the
full catalog operation for any GRT-enabled jobs. You
can choose to run a full catalog operation immediately
after the backup job finishes, schedule the full catalog
operation for another time, or run an Instant GRT
operation as part of the backup job.

See “Configuring Instant GRT and full catalog options

to improve backup performance for GRT-enabled jobs”
on page 565.

Advanced Open File 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 572.

See “Configuring checkpoint restart” on page 574.

Advanced Disk-based Select this option to configure off-host backup

Backup processing for the backup job.

See “Configuring off-host backup options for a backup

job” on page 1332.

Pre/Post Commands 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 577.

Files and Folders 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 581.

Enterprise Vault Select this option to configure Enterprise Vault options.

See “Enterprise Vault backup options” on page 1215.

Linux and Macintosh Select this option to configure options for any Linux or
Machintosh computers that are included in the backup
job.

See “Linux backup options” on page 1375.

 Backups 163
Backing up data

Microsoft Active Directory 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 1258.

Microsoft Exchange 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 1124.

Virtual Machines 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 1022.

See “Backing up VMware virtual machines” on page 968.

Microsoft SharePoint 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 1149.

Microsoft SQL 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 1073.

NDMP 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 1343.

Oracle Select this option to configure options for any Oracle

data that is included in the backup job.

See “Oracle backup options” on page 1189.

Exclusions Select this option to exclude specific files or specific

types of files from backups.

See “Excluding files from backups” on page 174.

13 When you are finished selecting all applicable options for the backup definition,
click OK.
 Backups 164
Backing up data

14 (Optional) You can add stages to this backup definition to duplicate your data
or create virtual machines with your backup data.

Note: You cannot add a stage to one-time backups.

See “Adding a stage to a backup definition” on page 214.

15 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 148.
See “Editing backup definitions” on page 200.
See “About selecting data to back up ” on page 165.
See “Changing the order in which backup sources are backed up” on page 171.

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.
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.
 Backups 165
About selecting data to back up

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 153.
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 “Notes about using the Agent for Hyper-V ” on page 1016.

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.
 Backups 166
About selecting data to back up

Figure 4-2 Selections box on the Backup Definition Properties dialog box

See “Backing up data” on page 153.

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.
Windows server provides the ability to encrypt volumes using the Bit locker
functionality. Backup Exec supports the backup and restore of Bitlocker enabled
volumes either by manually unlocking the destination volumes or by using the
 Backups 167
About selecting data to back up

Microsoft auto-unlock functionality. For more information, refer to the Microsoft

documentation.
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
logon account. You can also create a new logon account that can access the
selection.
See “Testing credentials for backup sources” on page 206.
See “Replacing the credentials for a backup source” on page 207.
See “Creating new credentials for a backup source” on page 208.
To include data in the backup, select the check box next to the drive or directory
that you want to back up.
This topic includes the following information:
Tagging resources as business-critical
Including and excluding specific files or subdirectories
Selecting multiple servers or applications
Selecting critical system components
Using fully qualified domain names in backup selections

Tagging resources as business-critical

The Tag as Business-Critical option lets you select which resources are most
important to you. When an item is tagged as a business-critical resource, Backup
Exec prioritizes the backup of that resource within the backup window before any
resources that are not tagged as business-critical. If you tag a resource as
business-critical, all of its children are also tagged as critical. When you tag an item
as a business-critical resource, Backup Exec changes the icon for that resource in
the backup set view and in the restore wizard.
The Tag as Business-Critical option is enabled for the following resources:
■ Windows volumes and UNIX root volumes
■ Exchange databases
■ SQL instances
■ Virtual machine folders
■ Virtual machines
■ SharePoint resources
■ Oracle instances
 Backups 168
About selecting data to back up

Note that the Tag as business-critical option is disabled on partial selections. In

addition, the option is not applicable to Enterprise Vault resources, such as
Compliance Accelerator or Discovery Accelerator.
When an item is tagged as a business-critical resource, it applies only to that job.
It is not a global setting. When you tag a server's resource as business-critical and
also select other resources from the same server, then the backup priority for the
business-critical resource is evaluated in relation to the other resources for that
server only. For multi-server jobs, business-critical resources are backed up by the
order in which the servers are prioritized, with the business-critical resources for
servers at the top of the list being backed up before business-critical resources for
the servers that are lower on the list.
Critical system resources can be tagged as business-critical as well. If critical system
resources are not selected, then the resources that are tagged as business-critical
are backed up before critical system resources if they are in the same backup job.
However, the best practice for critical system resources is to back them up in a
separate backup job. If you include both business-critical resources and critical
system resources in the same backup job, note that system state is always backed
up last regardless of whether it was tagged as a business-critical resource or not.
After you tag items as business-critical resources you can use the arrow buttons
on the Selection Details tab to change the order in which the items are backed
up. However, an item that is not tagged as a business-critical resource cannot be
moved ahead of an item that is tagged as a business-critical resource. For example,
if you tagged your C drive as a business-critical resource, but did not tag your E
drive as a business-critical resource, you cannot move the E drive ahead of the C
drive.
See “Changing the order in which backup sources are backed up” on page 171.

Note: During a rolling upgrade, the tag as business-critical feature is not applied
to jobs that are delegated to managed Backup Exec servers until the managed
servers are upgraded to the most recent version of Backup Exec.

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:
■ 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.
 Backups 169
About selecting data to back up

■ 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.
See “Excluding files from backups” on page 174.
See “Including specific files with a backup job's backup selections” on page 177.

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 597.

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.
 Backups 170
About selecting data to back up

Figure 4-3 Simplified Disaster Recovery indicator is ON in the Backup

Definition Properties dialog box

See “About backing up critical system components” on page 179.

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:
 Backups 171
Changing the order in which backup sources are backed up

■ 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 \\
■ The name cannot include the following characters: * | < > ?
It is not recommended using both fully qualified domain names and non-qualified
domain names. It is recommended that you use 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 171.

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.
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.
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
 Backups 172
Changing the order in which backup sources are backed up

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.
 Backups 173
Changing the order in which backup sources are backed up

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:

To reorder the servers in a In the left pane of the Backup Selections dialog box,
backup definition with multiple use the up and down arrows to configure the order of
servers the servers or applications.

Backup Exec backs up the servers or applications at

the top first.
 Backups 174
Excluding files from backups

To reorder the backup Do the following:

sources within a server
■ 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.

4 Click OK.
See “Backing up data” on page 153.
See “About selecting data to back up ” on page 165.

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
 Backups 175
Excluding files from backups

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:

To exclude files from a Complete the following steps:

backup job
■ 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 Complete the following steps:

backup definition
■ 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.
 Backups 176
Excluding files from backups

To globally exclude files from Complete the following steps:

all backups
■ Click the Backup Exec button.
■ Select Configuration and Settings, and then select
Job Defaults.
■ Click Exclude Selections.
■ Click Insert.

2 Complete any of the following fields to identify the files that you want to exclude:

Resource name Enter the name of the volume or drive that you want to
exclude from backups.

Path 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.

Name 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".
 Backups 177
Including specific files with a backup job's backup selections

3 Complete any of the following options, as necessary:

Apply to subdirectories Select this option to exclude the contents of all of the
subfolders when you select a directory.

Only modified files Select this option to exclude only the files that have
been modified in the directory that you specified.

Only read-only files Select this option to exclude only read-only files in the
directory that you specified.

Files dated 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 not accessed in X Select this option to exclude any files that have not been
days accessed in a specific number of days. You must enter
the number of days.

4 Click OK.
See “About selecting data to back up ” on page 165.
See “Including specific files with a backup job's backup selections” on page 177.

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.
 Backups 178
Including specific files with a backup job's backup selections

4 Complete any of the following fields to identify the files that you want to include:

Resource name Enter the name of the volume or drive that you want to
include in the backup.

Path 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.

Name 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".

5 Complete any of the following options as necessary:

Apply to subdirectories Select this option to include the contents of all of the
subfolders when you select a directory.

Only modified files Select this option to include only the files that have been
modified in the directory that you specified.

Only read-only files Select this option to include only read-only files in the
directory that you specified.

Files dated 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 not accessed in X Select this option to include any files that have not been
days accessed in a specific number of days. You must enter
the number of days.

Tag as business-critical Select this option to prioritize the backup of the selected
resource above other resources that are not tagged as
business-critical.

6 Click OK.
See “About selecting data to back up ” on page 165.
 Backups 179
About backing up critical system components

See “Excluding files from backups” on page 174.

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-4 Simplified Disaster Recovery indicator is ON in the Backup

Definition Properties dialog box

Simplified Disaster Recovery

indicator

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 812.
■ Conversion to virtual machines
See “How conversion of physical computers to virtual machines works in Backup
Exec” on page 499.
■ Complete online restore of a Microsoft Windows computer
See “Performing a complete online restore of a Microsoft Windows computer”
on page 234.
 Backups 180
About backing up critical system components

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.

Table 4-2 Restore scenarios by data type

File System Operating Complete Physical- Backup- Simplified

or Agent System Online to-Virtual to-Virtual Disaster
Name and Restore Conversion Conversion Recovery
Applications Can Be Can Be Can Be Can Be
Are Performed Performed Performed Performed
Installed
and
Functional

Active Yes Yes Yes Yes Yes

Directory

Active Yes No No No No
Directory
Lightweight

CSV Yes Yes No No Yes

EFI Yes Yes No No Yes

Enterprise Yes No No No No
Vault

Exchange Yes No Yes, any Yes, any No

Agent incremental incremental
or differential or differential
backups must backups must
use the use the
block-level block-level
backup backup
method method

FAT Yes Yes Yes Yes Yes

Hyper-V Yes No No No No
Agent

NTFS Yes Yes Yes Yes Yes

Oracle RMAN Yes No No No No

Windows
Agent
 Backups 181
About backing up critical system components

Table 4-2 Restore scenarios by data type (continued)

File System Operating Complete Physical- Backup- Simplified

or Agent System Online to-Virtual to-Virtual Disaster
Name and Restore Conversion Conversion Recovery
Applications Can Be Can Be Can Be Can Be
Are Performed Performed Performed Performed
Installed
and
Functional

ReFS Yes Yes No No Yes

Shadow Copy Yes Yes Yes Yes Yes

Components

SharePoint Yes No No No No
Agent

SQL Agent Yes No Yes, any Yes, any No

incremental incremental
or differential or differential
backups must backups must
use the use the
block-level block-level
backup backup
method method

System State Yes Yes Yes Yes Yes

Utility Yes Yes No No Yes

Partition

VMware Yes No No No No
Agent

Windows Yes Yes No No Yes

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
 Backups 182
Backup Exec Shadow Copy Components file system

can exclude Microsoft Exchange data from your backup, for example, and still use
the backup sets to perform a disaster recovery.
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
For information about the best practices to use Backup Exec to protect critical
system components, refer to Backup Exec Best Practices.

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 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
 Backups 183
Backup methods in Backup Exec

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 2008, in the absence of a SQL Agent 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 SQL Agent must be used
to protect the SQL SHAREPOINT instance.

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.
 Backups 184
Backup methods in Backup Exec

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.
It is recommended 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

Backup source Scenarios for which a full backup is recommended

Operating system 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.

Applications You should run a full backup when you:

■ Install new applications.
■ Upgrade applications to new versions.
■ Update the existing version of applications.

Backup Exec 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 Veritas
Update.
■ Make configuration changes.

Running full backups before and after each of these scenarios helps to ensure that
you can restore back to the previous configuration, if necessary.
 Backups 185
Backup methods in Backup Exec

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 581.
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 581.
 Backups 186
Backup methods in Backup Exec

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

Method Advantages Disadvantages

Full ■ Files are easy to find ■ Redundant backups

Full backups include all the Most of the files on your file
data that you selected to back server do not change. Each full
up. Therefore, you don’t have backup that follows the first is
to search through several merely a copy of what has
backup sets to find a file that already been backed up. Full
you need to restore. backups require more storage.
■ A current backup of your entire ■ Full backups take longer to
system is available on one perform
backup set Full backups can be time
If you run a full backup of your consuming, especially when
entire system and then need you have other servers on the
to restore it, all of the most network that need to be backed
current information is located up (for example, agent
in one place. workstations, remote servers).
 Backups 187
Backup methods in Backup Exec

Table 4-4 Backup method Advantages and Disadvantages (continued)

Method Advantages Disadvantages

Differential ■ Files are easy to find ■ Redundant backups

Restoring a system that is All of the files that were created
backed up with a differential or modified since the last full
method requires fewer backup are included; thus
backups. Differentials require creating redundant backups.
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.

Incremental ■ Better use of storage ■ Backups are spread across

Only the files that have multiple backup sets
changed since the last backup Since multiple backup sets are
are included, so much less required in a disaster situation,
data storage space is required. recovering a server can take
■ Less time is required for longer. In addition, the backup
backup sets must be restored in the
Incremental backups take correct order to effectively
much less time than full and bring the system up to date.
differential backups to
complete.

Consider the following backup strategy scenario:

 Backups 188
Backup methods in Backup Exec

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 features 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 191.
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.
 Backups 189
Backup methods in Backup Exec

Table 4-5 Available Backup Methods By Data Type

Data type Job type and backup method

Files and Folders 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

Enterprise Vault 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

Microsoft Initial full:

Exchange
■ 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)

Virtual Machines 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
 Backups 190
Backup methods in Backup Exec

Table 4-5 Available Backup Methods By Data Type (continued)

Data type Job type and backup method

Microsoft Initial full:

SharePoint
■ 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 SQL 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
 Backups 191
Configuring backup methods for backup jobs

Table 4-5 Available Backup Methods By Data Type (continued)

Data type Job type and backup method

NDMP (all) 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)

Oracle 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

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 183.
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.
 Backups 192
Configuring backup methods for backup jobs

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.

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:
 Backups 193
How Backup Exec determines if a file has been backed up

■ 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.

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.
 Backups 194
How Backup Exec determines if a file has been backed up

This topic includes the following information:

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
 Backups 195
How Backup Exec determines if a file has been backed up

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.
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 feature
(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 581.

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

Volume size Defaults

128 GB or larger ■ Change Journal Max Size: 32 MB

■ Allocation Delta: 4 MB
 Backups 196
How Backup Exec determines if a file has been backed up

Table 4-6 Change journal defaults set by Backup Exec (continued)

Volume size Defaults

Over 64 GB - 127 ■ Change Journal Max Size: 16 MB

GB ■ Allocation Delta: 2 MB

Over 4 GB - 63 GB ■ Change Journal Max Size: 8 MB

■ Allocation Delta: 1 MB

4 GB or less ■ Change Journal Max Size: 1 MB

■ Allocation Delta: 256 KB

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.
 Backups 197
Configuring Backup Exec to automatically delete files after a backup

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
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 581.
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.
To configure Backup Exec to automatically delete files after a backup
1 Do one of the following:

To configure Backup Exec to Complete the following steps:

automatically delete files after
■ Click the Backup Exec button, and then select
all backup jobs
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 Complete the following steps:

automatically delete files for
■ Create a new backup definition or edit an existing
specific backup jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Files and Folders.

 Backups 198
Configuring network options for backup jobs

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.

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 614.
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 CAS 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:

Network interface 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.

Protocol Select the protocol you want to use for this backup job.
The options are as follows:

■ Use any available protocol

■ IPv4
■ IPv6

Subnet Select the 32-bit number that determines the subnet to

which the network interface card belongs.
 Backups 199
Running the next scheduled backup job before its scheduled time

Allow use of any available Select this option to let Backup Exec use any available
network interface, subnet, network if the remote system that you selected for
or protocol for Backup Exec backup or restore is not part of the specified backup
agents not bound to the network.
above network interface,
If you do not select this option and the remote system
subnet, or protocol
is not part of the specified backup network, the job fails.
Backup Exec cannot access the data from the remote
system.

Interface Details 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.

Allow managed Backup Select this option to let a job use any network interface
Exec server to use any to access Backup Exec agents if the selected network
network interface to access interface is unavailable. Enabling this option lets the
Backup Exec agents 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

feature (CAS) is installed.

See “About the Central Admin Server feature”

on page 1263.

5 Click OK.
See “Backup networks” on page 612.

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.
 Backups 200
Editing backup definitions

■ 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 153.

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 or create virtual machines with your backup data.
See “Adding a stage to a backup definition” on page 214.
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:
 Backups 201
Editing backup definitions

To edit backups from the Complete the following steps:

Backup and Restore tab
■ 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 Job Complete the following steps:

Monitor tab
■ 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.
 Backups 202
Editing backup definitions

To edit backups from the Complete the following steps:

Storage tab
■ 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.

2 In the Selections box, click Edit.

 Backups 203
Editing backup definitions

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.
■ 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 179.

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:

To edit backups from the Complete the following steps:

Backup and Restore tab
■ 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.
 Backups 204
Editing backup definitions

To edit backups from the Job Complete the following steps:

Monitor tab
■ 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.
 Backups 205
Editing backup definitions

To edit backups from the Complete the following steps:

Storage tab
■ 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.

2 In the Backup box, click Edit.

 Backups 206
Testing credentials for backup sources

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.
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 153.

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.
It is recommended 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.
 Backups 207
Replacing the credentials for a backup source

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.
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 207.
See “Creating new credentials for a backup source” on page 208.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 210.

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.
It is recommended 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.
 Backups 208
Creating new credentials for a backup source

To replace the credentials for a backup source

◆ Do one of the following:

To replace the logon account Complete the following steps:

that is associated with a
■ On the Backup and Restore tab, double-click the
backup source on the
server whose credentials you want to view.
Credentials pane
■ 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.

To replace the logon account Complete the following steps:

that is associated with a
■ Create a new backup or edit an existing backup.
backup source in a backup
■ In the Selections box, click Test/Edit Credentials.
definition
■ In the Logon Account field, select the logon account
that you want to use for the backup source.
■ Click OK.

See “Testing credentials for backup sources” on page 206.

See “Creating new credentials for a backup source” on page 208.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 210.

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:
 Backups 209
Creating new credentials for a backup source

To create new credentials for Complete the following steps:

a backup source on the
■ On the Backup and Restore tab, double-click the
Credentials pane
server for which you want to create new credentials.
■ In the left pane, click Credentials.

To create new credentials for Complete the following steps:

a backup source in a backup
■ Create a new backup or edit an existing backup.
definition
■ In the Selections box, click Test/Edit Credentials.

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 206.
See “Replacing the credentials for a backup source” on page 207.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 210.
 Backups 210
Deleting retired or unused backup sources from the Credentials pane

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
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 206.

See “Replacing the credentials for a backup source” on page 207.
See “Creating new credentials for a backup source” on page 208.

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.
 Backups 211
How job scheduling works in Backup Exec

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
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 549.

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 213.
See “Including a specific date in the schedule for a backup job” on page 212.
 Backups 212
Including a specific date in the schedule for a backup job

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
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 213.

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:

To manually enter the date 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.
 Backups 213
Preventing backup jobs from running on a specific date

To select the date from the Click the date that you want to include with the backup
calendar 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.

7 Click OK.
See “How job scheduling works in Backup Exec” on page 210.

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 212.

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:
 Backups 214
Viewing all scheduled backup jobs on a calendar

To manually enter the date 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 select the date from the Click the date that you want to exclude.
calendar
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.

7 Click OK.
See “How job scheduling works in Backup Exec” on page 210.

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 210.

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 and duplication
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
 Backups 215
Adding a stage to a backup definition

storage when the backup job is complete. Then you can take the tape off-site to
ensure that your data is safe.

Table 4-7 Types of stages

Stage Description

Duplicate to Disk Creates a duplicate copy of your backup and sends it to disk
storage.

Duplicate to Tape Creates a duplicate copy of your backup and sends it to tape
storage.

Duplicate to Cloud Creates a duplicate copy of your backup and sends it to the
cloud storage.

Convert to Virtual Machine Creates a virtual machine from your backup sets after the
After Backup backup job is complete.

See “How conversion of physical computers to virtual

machines works in Backup Exec” on page 499.

Convert to Virtual Machine Creates a virtual machine from your backup sets while the
Simultaneously with Backups backup job is running.

See “How conversion of physical computers to virtual

machines works in Backup Exec” on page 499.

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.
 Backups 216
Editing a stage

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 153.
See “Editing a stage” on page 216.

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:

To edit a stage from the Complete the following steps:

Backup and Restore tab
■ 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 Job Complete the following steps:

Monitor tab
■ On the Job Monitor tab, right-click the job that
contains the stage that you want to edit.
■ Click Edit.

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 214.

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.
 Backups 217
Duplicating backup sets or a job history manually

See “Adding a stage to a backup definition” on page 214.

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 224.
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.
 Backups 218
Duplicating backup sets or a job history manually

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:

To run the duplicate job Select Run now.

immediately

To schedule the job for a later Select Run on, and then enter the date and time.
time

To schedule the job to run Select Create without a schedule.

later using an external
You can schedule the job to run later using an external
scheduling tool
scheduling tool.

To submit the job on hold 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.

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:

To enable compression for In the Compression field, select the type of

the duplicate backup sets compression.
 Backups 219
Duplicating backup sets or a job history manually

To enable encryption for the Complete the following steps:

duplicate backup sets
■ 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 run a verify operation on Select Verify at the end of the job.

the duplicate backup sets

9 On the Duplicate Job dialog box, click OK.

To duplicate job history
1 Do one of the following:

To duplicate job history from Complete the following steps:

the Backup and Restore tab
■ On the Backup and Restore tab or the Storage
or the Storage tab
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 Complete the following steps:

the Job Monitor tab
■ 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.

2 Click Duplicate.
 Backups 220
Duplicating backup sets or a job history manually

3 In the Schedule group box, select when you want Backup Exec to run the
duplicate job:

To run the duplicate job Select Run now.

immediately

To schedule the job for a later Select Run on, and then enter the date and time.
time

To schedule the job to run Select Create without a schedule.

later using an external
You can schedule the job to run later using an external
scheduling tool
scheduling tool.

To submit the job on hold 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.

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:

To enable compression for In the Compression field, select the type of

the duplicate job history compression.

To enable encryption for the Complete the following steps:

duplicate job history
■ 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 run a verify operation on Select Verify at the end of the job.

the duplicate job history

7 On the Duplicate Job dialog box, click OK for each duplicate job that you
create.
 Backups 221
Running a test run job manually

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 732.
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, it is recommended 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:

To run a test job from the Complete the following steps:

Backup and Restore tab
■ On the Backup and Restore tab, double-click the
server that contains the job you want to test.
■ In the left pane, click Jobs.
 Backups 222
Verifying backed up data manually

To run a test job from the Job Select the Job Monitor tab.
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 562.

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. It is recommended 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 563.
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.
 Backups 223
Verifying backed up data manually

■ 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:

To run the verify operation Select Run now.

immediately

To schedule the operation for Select Run on, and then enter the date and time.
a later time

To schedule the job to run Select Create without a schedule.

later using an external
You can schedule the verify operation to run later using
scheduling tool
an external scheduling tool.

6 Click OK.
To verify a job history
1 Do one of the following:

To verify a job history from Complete the following steps:

the Backup and Restore tab
■ On the Backup and Restore tab or the Storage
or the Storage tab
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 On the Job Monitor tab, do one of the following:
the Job Monitor tab
■ 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.

2 Click Verify.
 Backups 224
Copying data from a virtual tape library to a physical tape device using DirectCopy to tape

3 In the Schedule group box, select when you want Backup Exec to run the
verify operation:

To run the verify operation Select Run now.

immediately

To schedule the operation for Select Run on, and then enter the date and time.
a later time

To schedule the job to run Select Create without a schedule.

later using an external
You can schedule the verify operation to run later using
scheduling tool
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.
 Backups 225
Copying data from a virtual tape library to a physical tape device using DirectCopy to tape

Table 4-8 How to use DirectCopy to tape to copy data from a virtual tape
library to a physical device

Step Notes For more information

Create a regular backup Select a virtual tape library as See “Backing up data”
job. the storage destination. on page 153.

See “Configuring storage

options for backup jobs”
on page 556.

Create a duplicate In the DBA-initiated job settings: See “DBA-initiated job

backup job. templates” on page 640.
■ Select a physical tape
device as the destination. See “Storage options for
■ Select Enable DirectCopy DBA-initiated jobs” on page 643.
to tape. See “Duplicate job settings for
DBA-initiated jobs” on page 648.
 Chapter 5
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

 Restores 227
Methods for restoring data in Backup Exec

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.
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

Method Description

Search 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 229.

 Restores 228
Methods for restoring data in Backup Exec

Table 5-1 Guided methods to search for and restore data (continued)

Method Description

Restore 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 229.

See “Performing a complete online restore of a Microsoft

Windows computer” on page 234.

Simplified Disaster Lets you recover Windows computers after a hard drive
Recovery 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 812.

See “Restoring file system data” on page 233.

See “Restoring System State ” on page 235.
See “Restoring Backup Exec Shadow Copy Components” on page 240.
See “Restoring utility partitions or Unified Extensible Firmware Interface system
partitions” on page 240.
See “Restoring Exchange data” on page 1138.
See “Restoring SQL databases and transaction logs” on page 1095.
See “About restoring Oracle resources” on page 1190.
See “Restoring VMware virtual machines and vmdk files” on page 984.
See “Restoring a deduplication disk storage device or deduplicated data”
on page 955.
See “Restoring Microsoft SharePoint data” on page 1156.
See “Restoring Enterprise Vault” on page 1219.
 Restores 229
Searching for data to restore

See “About restoring data to Linux computers” on page 1377.

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

Note: You can search the backup sets for any data that was backed up from a
virtual machine if you have selected one of the full catalog options on the Instant
GRT and Full Catalog Options page and the full catalog job is complete. However,
the search option is available in the Restore Wizard only when you select an
application installed on the virtual machine for restore.
Search is not available if you have selected the Enable Instant GRT option on the
Instant GRT and Full Catalog Options page.

For files and folders, if you have blocked access to backed up files using the
Import-BEItemsToBlock BEMCLI command, the blocked files are not available
when you are browsing for files to be restored.
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.
 Restores 230
Restoring data from a server, a backup set, a backup job, or a storage device

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.
For the file and folders, if you have blocked access to backed up files using the
Import-BEItemsToBlock BEMCLI command, the blocked files are not displayed
in the search results.
See “Performing a complete online restore of a Microsoft Windows computer”
on page 234.

Table 5-2 Restore methods

Restore method More information

To restore from a server Restoring data from a server

To restore from a backup set To restore data from a backup set

To restore from a completed backup job Restoring data from a completed backup job

To restore from storage device media Restoring data 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.
 Restores 231
Restoring data from a server, a backup set, a backup job, or a storage device

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:

To restore data from the ■ On the Backup and Restore tab, in the list of
Backup and Restore tab 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 Job ■ On the Job Monitor tab, in the Jobs pane, right-click
Monitor tab a server that has been backed up.
■ Select Restore backup sets created by this job.

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.
 Restores 232
Restoring data from a server, a backup set, a backup job, or a storage device

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:

To restore from a disk storage Do the following in the order listed:

device
■ 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 tape drive Do the following in the order listed:

media or a disk cartridge
■ On the Storage tab, in the All Storage view, expand
media
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 media within Do the following in the order listed:

a robotic library
■ 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.

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.
 Restores 233
Restoring file system data

■ 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.
■ 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 229.
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.
3 Do one of the following:

To restore the data to a point-in-time at Select File and folder backups to a

which the backup set was created point-in-time.
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.
 Restores 234
Performing a complete online restore of a Microsoft Windows computer

To restore file and folder backups from a Select File and folder backups from a
backup set 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.

To search for files and folders Select Files and folders located through
Search.

To restore blocked files Do the following in the order listed:

Blocked items contain personally 1 Select the Allow restore of blocked

identifiable information. By default, the items check box.
blocked items are not available for restore.
2 On the Restore Blocked Items
Only the owner of a System Logon Account dialog box, enter the reason for
has the privileges to restore these blocked restoring blocked files and then click
items and reason for restore is recorded OK.
in the audit log.
See “About GDPR Guard” on page 750.

4 Click Next.
If you have blocked access to backed up files using the
Import-BEItemsToBlock BEMCLI command, the blocked files are not available
when you are searching for files to be restored.
5 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.
 Restores 235
Restoring System State

Note: Online restore using the Agent for Windows does not restore the
WindowsApps folders on operating systems that run Windows 8 or later. However,
the restore job is successful. Microsoft recommends to restore the WindowsApps
folders using Device Reset on the Settings panel.
The WindowsApps folders that are ignored during restore could be the following:
The folder pointed by
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\PackageRoot

The folder pointed by

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\PackageRepositoryRoot

%SystemRoot%\InfusedApps

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.
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.
If you have specified any blocked files, they are not restored.
See “About backing up critical system components” on page 179.
See “Methods for restoring data in Backup Exec” on page 227.

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
 Restores 236
Restoring System State

■ 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.

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 1253.
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 229.
 Restores 237
Restoring System State

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 179.
See “Performing a complete online restore of a Microsoft Windows computer”
on page 234.

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.
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.
 Restores 238
Installing a new Windows Server domain controller into an existing domain by using a redirected restore

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 227.
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
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 1253.
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

Step Description

Step 1 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 153.

 Restores 239
Installing a new Windows Server domain controller into an existing domain by using a redirected restore

Table 5-3 How to install a new Windows Server domain controller into an
existing domain by using a redirected restore (continued)

Step Description

Step 2 Attach the storage that contains the System State data to the computer
that you want to install into the destination domain.
Note: It is recommended that you encrypt the storage. Use caution
when transporting it to the location of the destination domain.

Step 3 Inventory and catalog the storage.

See “Inventorying and cataloging a storage device” on page 473.

Step 4 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 235.

Step 5 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 6 Complete the domain controller installation.

Step 7 Restart the computer that has the new domain controller.

Step 8 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 344.
 Restores 240
Restoring Backup Exec Shadow Copy Components

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 229.
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.
See “Methods for restoring data in Backup Exec” on page 227.
See “Restoring System State ” on page 235.

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
 Restores 241
About restoring encrypted data

that the operating system creates. The UEFI system partitions contain the critical
system files, such as bootmgr and BOOT\BCD 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 229.
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 227.

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.
 Restores 242
About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec

See “Using encryption with Backup Exec” on page 624.

See “Encryption key management” on page 627.

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 in
the Backup Exec Software Compatibility List.

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.
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 253.

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:
 Restores 243
How Backup Exec catalogs work

■ View information on all the directories and files that are contained in each backup
set.
■ Search for files to restore.
Backup Exec 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 immediately after the backup
operation by default.
For Exchange and SharePoint agent-based backups, the full 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 full catalog operation runs immediately after
all full, incremental, and differential backups by default. You can also schedule a
full catalog operation.
For information about the best practices to manage catalogs in Backup Exec, refer
to Backup Exec Best Practices.
See “Configuring default options for catalogs” on page 243.
See “Cataloging a storage device” on page 470.
See “About cataloging tape or disk cartridge media that contains encrypted backup
sets” on page 431.
See “Configuring Instant GRT and full catalog options to improve backup
performance for GRT-enabled jobs” on page 565.

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 242.
 Restores 244
How Backup Exec catalogs work

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:

Request all media in the Catalogs the media in tape drives and disk cartridges
sequence for catalog by starting with the lowest known tape number in the
operations 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.

 Restores 245
How Backup Exec catalogs work

Use storage-based catalogs Lets Backup Exec read the catalog information from the
storage device.

Storage-based catalogs allow fast 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: It is recommended 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 feature, 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 1349.
■ If you use the Advanced Disk-based Backup feature,
this option must be enabled to use the true image
restore capability.
See “About true image restore for synthetic backups”
on page 1327.
■ 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 816.
■ 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 632.
 Restores 246
How Backup Exec catalogs work

Truncate catalogs after 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 470.

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.

Catalog path 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:<Backup Exec install path>\Backup

Exec\Catalogs.
Note: It is recommended 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.

See “Moving the Backup Exec catalogs to a new

directory” on page 246.

4 Click OK.

Moving the Backup Exec catalogs to a new directory

It may be necessary to move the catalogs to a different location due to disk space
limitations or other issues. Backup Exec can be configured to use a different directory
for the catalog files.
The directory in which catalogs are stored from the Backup Exec server can also
be changed. When changing the catalog directory from the Backup Exec server,
all Backup Exec services must be stopped first and manually copy any existing
catalogs to the new catalog directory.
 Restores 247
Cataloging backup sets

To move the Backup Exec catalogs to a new directory

1 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, click Catalog.
3 In the Catalog path field, browse to or type the new path in which to store
catalogs.

Note: The directory must exist in Windows. Create the directory using Windows
Explorer before you type it in the Catalog path field.

4 Click OK.
5 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Services.
6 Click Stop all services.
7 Click OK.
After stopping all Backup Exec services, manually copy the catalog files from
the old folder to the new one.
8 Using Windows Explorer, navigate to the directory in which the catalogs are
currently stored.
9 Copy all of the items in the folder, including any subfolders and all files.
10 Using Windows Explorer, navigate to the directory to which you want to move
the catalogs.
11 Paste all of the items in the folder.
After any catalog files have been copied to the new directory, restart all Backup
Exec services.
12 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Services.
13 Click Start all services.
14 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
 Restores 248
Cataloging backup sets

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.
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 341.
See “How Backup Exec catalogs work” on page 242.
 Chapter 6
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.
 Job management and monitoring 250
How to monitor and manage jobs in Backup Exec

Table 6-1 Places where you can monitor jobs

Location where you can monitor jobs More information

The Job Monitor tab 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 Backup and Restore 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 Storage 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 Reports 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.

Job management
Backup Exec includes many features that enable you to manage backup jobs,
restore jobs, and storage operation jobs.
 Job management and monitoring 251
About the Job Monitor

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.
■ Retry only failed resources.
■ Run backup job with debugging enabled.
See “Editing backup definitions” on page 200.
See “Viewing job activity details for active jobs” on page 253.
See “Deleting scheduled jobs” on page 260.
See “Canceling an active job” on page 253.
See “Changing the priority for a scheduled job” on page 258.
See “Running a scheduled job immediately” on page 258.
See “Holding jobs” on page 254.
See “Holding the job queue” on page 256.
See “Running a test run job manually” on page 221.

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.
 Job management and monitoring 252
About the Job Monitor

Note: Report jobs do not appear on the Job Monitor. To monitor and manage
report jobs, go to the Reports tab.

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.
■ Retry only failed resources.
■ Run backup job with debugging enabled.
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.
■ Retry only failed resources.
■ Run backup job with debugging enabled.
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 249.
 Job management and monitoring 253
About the Job Monitor

See “Running a test run job manually” on page 221.

See “Duplicating backup sets or a job history manually” on page 216.
See “Verifying backed up data manually” on page 222.
See “Editing backup definitions” on page 200.

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:

To view job activity from the Job Monitor Select the Job Monitor tab.
tab

To view job activity from the Backup and Do the following:

Restore tab or the Storage tab
■ 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.

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
cancellation of a job, the Cancel Pending status appears in the Job Status column.
To cancel an active job
1 Do one of the following:

To cancel the job from the Job Monitor Select the Job Monitor tab.
tab
 Job management and monitoring 254
About the Job Monitor

To cancel the job from the Backup and Do the following:

Restore tab or the Storage tab
■ 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.

2 Right-click the active job that you want to cancel, and then click Cancel.
3 Click Yes to confirm the cancellation of the job.
See “List of job statuses in Backup Exec” on page 277.

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:

To place a job on hold from the Job Select the Job Monitor tab.
Monitor tab
 Job management and monitoring 255
About the Job Monitor

To place a job on hold from the Backup Do the following:

and Restore tab or the Storage tab
■ 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.

2 Do one of the following:

To hold a single job Select the job from the list of jobs, and then
in the Jobs group, click Hold. Then select
Hold Job.

To hold all active jobs 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 scheduled 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.

See “Removing the hold on jobs” on page 255.

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:

To remove the hold on jobs from the Job Select the Job Monitor tab.
Monitor tab
 Job management and monitoring 256
About the Job Monitor

To remove the hold from jobs from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job is on
hold.
■ In the left pane, click Jobs.

2 Do one of the following:

To remove the hold on a single job 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 all active jobs 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 scheduled 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.

See “Holding jobs” on page 254.

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
 Job management and monitoring 257
About the Job Monitor

To place the job queue on hold from the Select the Job Monitor tab.
Job Monitor tab

To place the job queue on hold from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
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.

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 257.

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

To remove the hold on the job queue from Select the Job Monitor tab.
the Job Monitor tab

To remove the hold on the job queue from Do the following:

the Backup and Restore tab or the
■ On the Backup and Restore tab or the
Storage tab
Storage tab, double-click the server or
the storage device where the job queue
is on hold.
■ In the left pane, click Jobs.

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 256.
 Job management and monitoring 258
About the Job Monitor

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:

To run the job from the Job Monitor tab Select the Job Monitor tab.

To run the job from the Backup and Do the following:

Restore tab or the Storage tab
■ 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.

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 258.

See “Deleting scheduled jobs” on page 260.

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:
 Job management and monitoring 259
About the Job Monitor

■ 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:

To change the job's priority from the Job Select the Job Monitor tab.
Monitor tab

To change the job's priority from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job is
scheduled to run.
■ In the left pane, click Jobs.

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.

 Job management and monitoring 260
About the Job Monitor

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:

To delete a scheduled job from the Job Select the Job Monitor tab.
Monitor tab

To delete a scheduled job from the Backup Do the following:

and Restore tab or the Storage tab
■ 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.

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 249.

Retrying only failed resources

You can retry a failed backup job to backup only the resources that failed during
the immediate previous run of that backup job. This option is available only for a
failed or cancelled backup job. If a backup job is successful, this option is grayed-out.
For example, if you have a VMware backup job that is backing up 5 virtual machines.
During backup, only 3 virtual machines are successfully backed up and for 2 virtual
machines the backup failed. You can refer to the job log to know the reason for the
failure, correct the issue, and then use the Retry Only Failed Resources option
 Job management and monitoring 261
About the Job Monitor

to run the job again. This time only the 2 virtual machines that failed during the
immediate previous run of that backup job are backed up. The 3 virtual machines
that were backed up successfully are not backed up again.
If a backup job is enabled for Simplified Disaster Recovery and failure occurs in
one or more of the critical resources, then when you retry the failed backup job, all
the critical resources are backed up again. Even the critical resources that may
have backed up successfully in the immediate previous run of that backup job.
In a CAS-MMS environment, for jobs delegated from the CAS server, the option to
run retry failed backup is only available from the CAS user interface. The option is
disabled for the delegated jobs on the MMS user interface.
To retry only failed resources
1 Do one of the following:

To retry the failed resource from the Job Select the Job Monitor tab.
Monitor tab

To retry the failed resource from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job is
running.
■ In the left pane, click Jobs.

2 Do one of the following:

■ Right-click the failed job that you want to retry, and then click Retry Only
Failed Resources.
■ On the Job Monitor tab, select the failed job that you want to retry, and
then click Retry Only Failed Resources.
A dialog box is displayed stating that the job will run immediately and also run
as per the defined schedule.
3 Click Yes.
The job starts and only the resource that failed during the immediate previous
run of the job is backed up.

Run backup job with debugging enabled

You can run a backup and restore job with automatic debugging enabled. When
you call technical support with an issue in your backup or restore job, technical
support asks you to gather the debug logs. With the help of the debug logs, support
 Job management and monitoring 262
About the Job History

can then make changes to the jobs that have an issue. After the job is complete,
you have all debug logs that you need to share with technical support.
To run a job with debugging enabled
1 Do one of the following:

To run the job with debugging enabled from Select the Job Monitor tab.
the Job Monitor tab

To run the job with debugging enabled from Do the following:

the Backup and Restore tab or the
■ On the Backup and Restore tab or the
Storage tab
Storage tab, double-click the server or
the storage device where the job is
running.
■ In the left pane, click Jobs.

2 Do one of the following:

■ Right-click the job , and then click Run with Debugging Enabled.
■ On the Job Monitor tab, select the job, and then click Run with Debugging
Enabled.
If the job does not have a schedule defined, a dialog box is displayed stating
that the job will run immediately.
If the job has a schedule defined, a dialog box is displayed and you must select
if you want the job to run immediately or as per the schedule. The debugging
enabled job runs only the first time that you enable the option. It does not run
on the subsequent schedules.
3 Click OK.
The job is completed and the debug logs are generated. If the backup or restore
job has an issue, you can send these debug logs to technical support.

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.
 Job management and monitoring 263
About the Job History

■ 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 264.
See “Viewing the job log ” on page 267.
See “Deleting a job from the Job History” on page 263.
See “Enabling an error-handling rule for a failed job” on page 275.
See “Duplicating backup sets or a job history manually” on page 216.
See “Verifying backed up data manually” on page 222.

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:

To view the history of a job from the Job On the Job Monitor tab, locate the job in
Monitor tab the Job Histories pane.

To view the history of a job from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job ran.
■ In the left pane, click Job History.

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:
 Job management and monitoring 264
About the Job History

To delete a job from the Job History on the On the Job Monitor tab, locate the job in
Job Monitor tab the Job Histories pane.

To delete a job from the Job History on the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job ran.
■ In the left pane, click Job History.

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 262.
See “Configuring database maintenance and security” on page 597.

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:

To run a job from the Job History on the On the Job Monitor tab, locate the job in
Job Monitor tab the Job Histories pane.

To run a job from the Job History on the ■ On the Backup and Restore tab or the
Backup and Restore tab or the Storage Storage tab, double-click the server or
tab the storage device where the job ran.
■ In the left pane, click Job History.

2 Right-click the job that you want to run, and then click Run Now.
See “About the Job History” on page 262.
 Job management and monitoring 265
About the Job History

Retrying only failed resources from the Job History

You can retry a job that failed from the job history for only the resources that failed
during the immediate previous run of that backup job. This option is available only
for a failed or cancelled backup job. If a backup job is successful, this option is
grayed-out.
For example, if you have a VMware backup job that is backing up 5 virtual machines.
During backup, only 3 virtual machines are successfully backed up and for 2 virtual
machines the backup failed. You can refer to the job log to know the reason for the
failure, correct the issue, and then use the Retry Only Failed Resources option
to run the job again. This time only the 2 virtual machines that failed during the
immediate previous run of that backup job are backed up.. The 3 virtual machines
that were backed up successfully are not backed up again.
If a backup job is enabled for Simplified Disaster Recovery and failure occurs in
one or more of the critical resources, then when you retry the failed backup job, all
the critical resources are backed up again. Even the critical resources that may
have backed up successfully in the immediate previous run of that backup job.
In a CAS-MMS environment, for jobs delegated from the CAS server, the option to
run retry failed backup is only available from the CAS user interface. The option is
disabled for the delegated jobs on the MMS user interface.
To retry only failed resources from the Job History
1 Do one of the following:

To retry the failed resource from the Job On the Job Monitor tab, locate the job in
Monitor tab the Job Histories pane.

To retry the failed resource from the Do the following:

Backup and Restore tab or the Storage
■ On the Backup and Restore tab or the
tab
Storage tab, double-click the server or
the storage device where the job ran.
■ In the left pane, click Job History.

2 Do one of the following:

■ Right-click the failed job that you want to retry, and then click Retry Only
Failed Resources.
■ On the Job Monitor tab, select the failed job that you want to retry, and
then click Retry Only Failed Resources.
 Job management and monitoring 266
About the Job History

A dialog box is displayed stating that the job will run immediately and also run
as per the defined schedule.
3 Click Yes.
The job starts and only the resource that failed during the immediate previous
run of the job is backed up.

Run backup job with debugging enabled from the Job History
You can run a backup and restore job with automatic debugging enabled. When
you call technical support with an issue in your backup or restore job, technical
support asks you to gather the debug logs. With the help of the debug logs, support
can then make changes to the jobs that have an issue. After the job is complete,
you have all debug logs that you need to share with technical support.
To run a job with debugging enabled
1 Do one of the following:

To run the job with debugging enabled from On the Job Monitor tab, locate the job in
the Job Monitor tab the Job Histories pane.

To run the job with debugging enabled from Do the following:

the Backup and Restore tab or the
■ On the Backup and Restore tab or the
Storage tab
Storage tab, double-click the server or
the storage device where the job is
running.
■ In the left pane, click Job History.

2 Do one of the following:

■ Right-click the job , and then click Run with Debugging Enabled.
■ On the Job Monitor tab, select the job, and then click Run with Debugging
Enabled.
If the job does not have a schedule defined, a dialog box is displayed stating
that the job will run immediately.
If the job has a schedule defined, a dialog box is displayed and you must select
if you want the job to run immediately or as per the schedule. The debugging
enabled job runs only the first time that you enable the option. It does not run
on the subsequent schedules.
3 Click OK.
The job is completed and the debug logs are generated. If the backup or restore
job has an issue, you can send these debug logs to technical support.
 Job management and monitoring 267
Viewing the job log

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:

To view the job log from the Job Monitor On the Job Monitor tab, locate the job in
tab the Job Histories pane.

To view the job log from the Backup and Do the following:
Restore tab or the Storage 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.

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:

To find text in the job log from the Job On the Job Monitor tab, in the Job
Monitor tab Histories pane, locate the job for which
you want to search the job log.
 Job management and monitoring 268
Viewing the job log

To find text in the job log from the Backup Do the following:
and Restore tab or the Storage 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.

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:

Match whole word only 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 case 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".

Highlight all matches Check this check box if you want Backup
Exec to highlight the text that matches the
search criteria. The option is selected by
default.

6 Click Next to find the next occurrence of the text.

See “Viewing the job log ” on page 267.
 Job management and monitoring 269
Viewing the job log

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:

To access the job log from the Job On the Job Monitor tab, locate the job in
Monitor tab the Job Histories pane.

To access the job log from the Backup Do the following:

and Restore tab or the Storage 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.

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 269.

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:

To access the job log from the Job On the Job Monitor tab, locate the job in
Monitor tab the Job Histories pane.

To access the job log from the Backup Do the following:

and Restore tab or the Storage 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.

2 Right-click the job, and then select View Job Log.

 Job management and monitoring 270
Viewing the job log

3 Click Save As.

4 Select the location where you want to save the job log.
See “Printing the job log” on page 269.

Linking from the job log to the Veritas 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
Veritas 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 Veritas 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 272.
To link from the job log to the Veritas Technical Support website
1 Do one of the following:

To link to the job log from the Job Monitor Select the Job Monitor tab.
tab

To link to the job log from the Backup and Do the following:
Restore tab or the Storage 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.

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:
 Job management and monitoring 271
Viewing the job log

Get-BEJobLog "pathname\job log filename"

For example, to display the job log C:<Backup Exec install path>\Backup
Exec\Data\bex00001.xml in text format to the command prompt, you would type:
Get-BEJobLog "C:<Backup Exec install path>\Backup Exec\Data\bex00001.xml"
To redirect the job log to a file, you would type one of the following:
Get-BEJobLog "C:<Backup Exec install path>\Backup Exec\Data\bex00001.xml"
> bex00001.txt
See “Viewing the job log ” on page 267.

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.

Summary information only 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.
 Job management and monitoring 272
Error-handling rules for failed or canceled jobs

Summary information and directories Select this option to include summary

processed information and a list of all processed
subdirectories in the job log.

Summary information, directories, and Select this option to include summary

files processed information, processed subdirectories, and
a list of all the file names that were
processed in the job log.

Summary information, directories, files, Select this option to include summary

and file details 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.

Prefix for the job log file name 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

Attach job logs as HTML Select this option to attach the job logs in
an HTML format when an email notification
is sent.

Attach job logs as text Select this option to attach the job logs in
a text format when an email notification is
sent.

Job log path Shows the current location of the job log.
To change the path you can use BE Utility.

See “Viewing the job log ” on page 267.

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.
 Job management and monitoring 273
Error-handling rules for failed or canceled jobs

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 273.
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 276.

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 272.
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.
 Job management and monitoring 274
Error-handling rules for failed or canceled jobs

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 275.
See “About the cluster failover error-handling rule” on page 276.

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 272.

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.
 Job management and monitoring 275
Error-handling rules for failed or canceled jobs

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 272.

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:

To enable an error-handling rule from the Select the Job Monitor tab.
Job Monitor tab

To enable an error-handling rule from the On the Backup and Restore tab or the
Backup and Restore tab or the Storage Storage tab, in the left pane, select Job
tab History.

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.
 Job management and monitoring 276
Error-handling rules for failed or canceled jobs

Table 6-2 Error codes for recovered jobs custom error-handling rule

Error code Description

0xE00081D9 E_JOB_ENGINE_DEAD The displayed error message is:

The Backup Exec job engine system
service is not responding.

0xE0008820 E_JOB_LOCAL The displayed error message is:

RECOVERNORMAL The local job has been recovered. No

user action is required.

0xE000881F E_JOB_REMOTE The displayed error message is:

RECOVERNORMAL The remote job has been recovered. No

user action is required.

0xE0008821 E_JOB_STARTUP The displayed error message is:

RECOVERY Job was recovered as a result of

Backup Exec RPC service starting. No
user action is required.

Note: If the Central Admin Server feature is installed, additional error codes are
selected.

See “Error-handling rules for failed or canceled jobs” on page 272.

See “About the cluster failover error-handling rule” on page 276.

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 272.
 Job management and monitoring 277
List of job statuses in Backup Exec

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 277.
See the section called “Completed job statuses” on page 278.
See the section called “Scheduled job statuses” on page 280.

Active job statuses

The following statuses may appear for the jobs that are active:

Table 6-3 Active job statuses

Status Description

Running The operation is underway.

Queued The job has been initiated, but Backup Exec is actively looking
for a suitable drive or media.

Cancel Pending 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.

Loading Media The media is being loaded and positioned on the target
device.

Pre-processing 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 595.
■ 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.

Snapshot processing Backup Exec is processing a snapshot operation.

Device Paused The device that the job was sent to is paused.

See “Pausing and unpausing a storage device” on page 473.

 Job management and monitoring 278
List of job statuses in Backup Exec

Table 6-3 Active job statuses (continued)

Status Description

Server Paused The Backup Exec server is paused.

See “Pausing or resuming a managed Backup Exec server”

on page 1311.

Stalled The Backup Exec services have become unresponsive.

See “Setting job status and recovery options” on page 282.

Media Request You must insert media for the job to continue.

Communication Stalled 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 1299.

No Communication 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 1299.

Consistency check Backup Exec is running a consistency check of the databases

before backup.

Updating Catalogs Backup Exec is updating the catalog information.

Completed job statuses

The following statuses may appear for the jobs that were completed:

Table 6-4 Job completion status

Status Description

Successful The job completed without errors.

Completed with The job completed, but some files were in use, skipped, or
exceptions corrupted.
 Job management and monitoring 279
List of job statuses in Backup Exec

Table 6-4 Job completion status (continued)

Status Description

Failed over 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.

Resumed The status is the same as the failed over status, however the
Enable checkpoint restart option was selected.

Canceled The administrator terminated the operation as it was running.

Canceled, timed out 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.

Failed 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 Veritas 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.

Recovered 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.
 Job management and monitoring 280
List of job statuses in Backup Exec

Table 6-4 Job completion status (continued)

Status Description

Missed The job did not run during the scheduled time window. The job is
rescheduled to run based on the time window that you configured.

Scheduled job statuses

The following statuses may appear for the jobs that are scheduled:

Table 6-5 Scheduled job statuses

Status Description

Invalid Schedule 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 589.

Not in time window 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 589.

On Hold The job has been placed on hold.

Queued 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 275.
 Job management and monitoring 281
List of job statuses in Backup Exec

Table 6-5 Scheduled job statuses (continued)

Status Description

Ready 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.
 Job management and monitoring 282
Setting job status and recovery options

Table 6-5 Scheduled job statuses (continued)

Status Description

Scheduled 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.

Server Paused 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 1311.

To Be Scheduled A state that the scheduled job transitions through as it is

being sent for processing.

Rule Blocked 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.

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.
 Job management and monitoring 283
Setting job status and recovery options

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.

Stalled Enter the amount of time you want to wait

before Backup Exec changes an
unresponsive job's status to Stalled.

Recovered 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.

4 Click OK.
 Job management and monitoring 284
Setting job status and recovery options

See “List of job statuses in Backup Exec” on page 277.

See “Custom error-handling rule for recovered jobs” on page 275.
 Chapter 7
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

 Alerts and notifications 286
Alerts and notifications in Backup Exec

■ 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

Item Description

Attention required Indicates the issues that require a response before

the job or operation can continue.

Error 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.

Warning Indicates the conditions that may or may not cause

jobs to fail. You should monitor the conditions and
take actions to resolve them.

Informational Provides status messages for the conditions that you

might want to know about.

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
 Alerts and notifications 287
Where to find alerts in Backup Exec

required alerts cannot be disabled. You can filter the alerts so that only specific
alerts appear.
See “Configuring alert categories” on page 302.
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 702.
See “Responding to active alerts” on page 293.
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 294.
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.
 Alerts and notifications 288
Where to find alerts in Backup Exec

Table 7-2 Where alerts appear on the Backup Exec Administration Console

Location of alerts Details

Home tab 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.

Backup and Restore 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.

Storage 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.
 Alerts and notifications 289
Enabling active alerts and alert history to display on the Home tab

Table 7-2 Where alerts appear on the Backup Exec Administration Console
(continued)

Location of alerts Details

Backup Exec status bar 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.

Windows 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.

Pop-up window 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.

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:
 Alerts and notifications 290
Enabling active alerts and alert history to display on the Home tab

■ 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 290.

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 289.

Table 7-3 Properties for active alerts

Item Description

Severity 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

Category Indicates the condition that caused the alert. Categories include
Database Maintenance, General Information, Device Error, or Job
Failed.

Message Indicates the text of the error message.

Date and Time Shows the date and time when the alert was received.

Job Name 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.

Storage Shows the name of the storage device on which the alert occurred.

Server Shows the name of the server on which the alert occurred.
 Alerts and notifications 291
Viewing the alert history for a server or a storage device

Table 7-3 Properties for active alerts (continued)

Item Description

Source Indicates the cause of the alert.

Alerts can originate from one of the following sources:

■ System
■ Job
■ Storage
■ Media

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.
 Alerts and notifications 292
Copying alert text to a document or email

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.
 Alerts and notifications 293
Viewing the job log from an alert

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 289.
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
 Alerts and notifications 294
Clearing all informational alerts manually

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 302.
Some alerts provide a Unique Message Identifier (UMI) code. This code is a
hyperlink to the Veritas 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 302.

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.
 Alerts and notifications 295
Configuring email or text message notification for alerts

Table 7-4 How to set up notification for alerts

Step Action

Step 1 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 295.

Step 2 Add the contact information for the people or groups that you want to
receive notifications.

See “Adding recipients for notification” on page 297.

See “Adding a recipient group for alert notifications” on page 299.

Step 3 Assign each recipient to the receive notifications for specific alert
categories.

See “Assigning recipients to receive notifications for specific alert

categories” on page 304.

See “Configuring alert categories” on page 302.

See “Sending a notification when a job completes” on page 304.

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

Notification type Description

Email notification Backup Exec uses SMTP for email

notifications and supports authentication and
Transport Layer Security (TLS). Notification
email messages can be sent to Microsoft
Outlook and web-based email applications,
such as Gmail or Yahoo mail.
 Alerts and notifications 296
Configuring email or text message notification for alerts

Table 7-5 Types of notification (continued)

Notification type Description

Text message notification 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>

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 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.
 Alerts and notifications 297
Adding recipients for notification

If you want to send alert notifications by Do the following:

email
■ 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 In Text message service provider

text message 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.

4 Click OK.
You can now add information about the recipients who need to receive alert
notifications.
See “Adding recipients for notification” on page 297.

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
 Alerts and notifications 298
Adding recipients for notification

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 295.
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:

To send emails to 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.
 Alerts and notifications 299
Adding a recipient group for alert notifications

To send text messages to this recipient 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.

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 304.

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.
 Alerts and notifications 300
Disabling email or text message alert notification for a recipient

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 297.

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.
 Alerts and notifications 301
Editing recipient notification properties

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 305.

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.
 Alerts and notifications 302
Configuring alert categories

See “Disabling notifications for a specific alert category” on page 305.

See “Disabling email or text message alert notification for a recipient” on page 300.
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.
 Alerts and notifications 303
Configuring alert categories

4 Under Category Properties, select the appropriate options.

Enable alerts for this category Enables or disables the alert. You cannot
disable error and attention required alerts.

Include the job log with email Sends the job log to the recipient that is
notifications configured for notification. If you select this
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.

Record event in the Windows Event Log Enters the alert into the Windows Event
Viewer. The Windows Event log displays
all the property information for the alert.

If a link does not appear in the Windows

Event log you can search the Technical
Support website for information about the
Event ID.

Send SNMP notifications Indicates whether SNMP notifications are

enabled or cleared for the alert. SNMP
must be installed to use this option.

Automatically clear after X Lets you enter the number of minutes,

hours/minutes hours, or days you want the alert to remain
active before it is cleared.
Note: Error alerts cannot be cleared
automatically, so this option is disabled for
error alerts.

Respond with Indicates the response that you want

Backup Exec to send automatically when
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.
 Alerts and notifications 304
Assigning recipients to receive notifications for specific alert categories

Send notification to the following Lets you select the name of a recipient to
recipients 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.

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.
 Alerts and notifications 305
Disabling notifications for a specific alert category

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 304.

Table 7-6 Notification options for jobs

Item Description

Recipient name Shows the names of the individual and group

recipients.

Recipient type Indicates Recipient for an individual recipient

or Group for a group recipient.

Include job log in email notifications 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:

HKLM\Software\Veritas\Backup Exec for

Windows\Backup Exec\Server\Max
Notification Attachment Size

The attachment size can also be determined

by the settings on your mail server.

Manage Recipients Lets you add, edit, or delete recipients.

Properties Lets you view or change the properties of a

selected recipient.

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.
 Alerts and notifications 306
Configuring default alert settings

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 300.

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 license contracts, check
Send an alert reminder to renew your license contracts on, and then enter
a date.
4 In the Capacity usage warning threshold for sending alert field, enter the
percentage of capacity usage that you want to use as a threshold to receive
an alert for renewal.
Based on the threshold that you enter, the Healthy or Warning icon is displayed
on the Home tab. This option is enabled when Subscription licenses or Capacity
licenses are installed.
 Alerts and notifications 307
Enabling or disabling pop-up alerts

5 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 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.

Error 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.

Warning 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.

Attention required 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.

6 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.
7 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.
 Alerts and notifications 308
SNMP traps for Backup Exec alerts

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 WINNT\SNMP\language directory on the Backup Exec
installation media that you can load into your SNMP console.
The Object Identifier prefix for Veritas 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

Trap Type Object ID String 1 String 2 String 3 String 4

Product Start 1302.3.1.1.9.1 Backup Exec: machine name product, version,

Application revision
initializing

Product Stop 1302.3.1.1.9.2 Backup Exec: machine name product, version,

Application revision
terminating

Job Canceled 1302.3.1.2.8.2 Backup Exec: Job machine name job name local or remote
canceled by Operator name
Operator

Job Failed 1302.3.1.2.8.1 Backup Exec: Job machine name job name detail message
failed

Storage device 1302.3.2.5.3.3 Backup Exec: machine name job name detail message
requires human Storage device
intervention requires attention
 Alerts and notifications 309
SNMP traps for Backup Exec alerts

Table 7-7 SNMP traps (continued)

Trap Type Object ID String 1 String 2 String 3 String 4

Robotic library 1302.3.2.4.3.3 Backup Exec: machine name job name detail message
requires human robotic library
intervention device requires
attention

Simplified Disaster 1302.3.1.4.2.1.2 SDR full backup machine name job name detail message
Recovery Message success

Backup Exec 1302.3.1.1.9.3 The application machine name job name detail message
system error has encountered
an error

Backup Exec 1302.3.1.1.9.4 Information on machine name job name detail message
general information normal events

Job Success 1302.3.1.2.8.3 The job machine name job name detail message
succeeded

Job Success with 1302.3.1.2.8.4 The job machine name job name detail message
exceptions succeeded, but
there was a
problem

Job Started 1302.3.1.2.8.5 The job has machine name job name detail message
started

Job Completed 1302.3.1.2.8.6 The job machine name job name detail message
with no data succeeded, but
there was no data

Job Warning 1302.3.1.2.8.7 The job has a machine name job name detail message
warning

PVL Device Error 1302.3.1.5.1.1.1 The device has machine name job name detail message
encountered an
error

PVL Device 1302.3.1.5.1.1.2 The device has machine name job name detail message
Warning encountered a
warning

PVL Device 1302.3.1.5.1.1.3 Normal device machine name job name detail message
Information information

PVL Device 1302.3.1.5.1.1.4 Device requires machine name job name detail message
Intervention attention
 Alerts and notifications 310
SNMP traps for Backup Exec alerts

Table 7-7 SNMP traps (continued)

Trap Type Object ID String 1 String 2 String 3 String 4

PVL Media Error 1302.3.1.5.2.1.1 There is an error machine name job name detail message
with the media

PVL Media 1302.3.1.5.2.1.2 There may be a machine name job name detail message
Warning problem with the
media

PVL Media 1302.3.1.5.2.1.3 Normal media machine name job name detail message
Information information

PVL Media 1302.3.1.5.2.1.4 Media requires machine name job name detail message
Intervention attention

Catalog Error 1302.3.1.5.3.1.1 There is an error machine name job name detail message
with the catalog

Tape Alert Error 1302.3.1.5.4.1.1 There is a machine name job name detail message
TapeAlert error

Tape Alert Warning 1302.3.1.5.4.1.2 There is a machine name job name detail message
TapeAlert warning

Tape Alert 1302.3.1.5.4.1.3 Normal TapeAlert machine name job name detail message
Information information

Database 1302.3.1.5.5.1.1 There is a machine name job name detail message

Maintenance Error database
maintenance error

Database 1302.3.1.5.5.1.2 Normal database machine name job name detail message
Maintenance maintenance
Information information

Install Update 1302.3.1.5.7.1.1 There is an install machine name job name detail message
Warning warning

Install Update 1302.3.1.5.7.1.2 Normal Install machine name job name detail message
Information information

See “Installing and configuring the SNMP system service” on page 310.

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.
 Alerts and notifications 311
SNMP traps for Backup Exec alerts

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>:\winnt\wmi\backupexecperfmon.mof

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.
 Alerts and notifications 312
SNMP traps for Backup Exec alerts

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>:\winnt\wmi\snmp\eng\bkupexecmib.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>:\winnt\wmi\deletebackupexecperfmon.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
 Chapter 8
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.
 Disk-based and network-based storage 314
Features and types of disk-based storage and network-based storage

■ 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

Types of disk-based storage Description

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.

See “Configuring disk storage” on page 317.

Disk cartridge devices 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 328.

Deduplication disk storage 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 Backup
Exec Deduplication feature to use this
data-reduction strategy that optimizes storage
and network bandwidth.

See “About the Deduplication feature”

on page 921.

Network-based storage includes NDMP servers, OpenStorage devices, cloud

storage devices, and the Remote Media Agent for Linux.
 Disk-based and network-based storage 315
Storage trending statuses for disk storage and virtual disks

Table 8-2 Types of network storage

Type of storage Description

NDMP servers 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 feature” on page 1339.

OpenStorage OpenStorage devices are network-attached storage that supports

devices Veritas's OpenStorage technology.

See “Configuring an OpenStorage device” on page 932.

Cloud storage Cloud storage devices are the storage devices that are configured on
devices the cloud hosted by the cloud storage service provider.

Remote Media The Remote Media Agent for Linux lets you back up data from remote
Agent for Linux 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 1392.

For information about the best practices to manage disk-based storage in Backup
Exec, refer to Backup Exec Best Practices.
See “Storage trending statuses for disk storage and virtual disks” on page 315.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 335.
See “Viewing jobs, job histories, backup sets, and active alerts for storage devices”
on page 470.
See “Backup sets ” on page 341.

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.
 Disk-based and network-based storage 316
Setting low disk space thresholds on disk-based storage

Table 8-3 Storage trending statuses

Storage trending status Description

Remaining storage: x days An estimate of the remaining number of days

of storage space, based on the current usage
of disk space.

History of used space is still being This status may appear for any of the
gathered 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.

Current storage is sufficient The environment contains enough disk space

to meet storage requirements for the next 30
days.

No estimate due to an inconclusive history A storage trend cannot be obtained. Unusual

of used space increases or decreases in the amount of free
disk space in the last 30 days can cause this
status.

Not enough statistical information is Backup Exec has not collected enough
available 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.

See “Configuring disk storage” on page 317.

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
 Disk-based and network-based storage 317
Configuring disk storage

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.
■ 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 335.

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
 Disk-based and network-based storage 318
Configuring disk storage

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.

For information about the best practices to use hot-pluggable devices in Backup
Exec, refer to Backup Exec Best Practices.
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.
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
 Disk-based and network-based storage 319
Configuring disk storage

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. It is recommended 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:

If the Central Admin Server feature is not Click Disk-based storage, and then click
installed Next.

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select the Backup Exec server on
which you want to configure storage,
and then click Next.
■ Click Disk-based storage, and then
click Next.

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:
 Disk-based and network-based storage 320
Configuring disk storage

To change the configuration 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 configure the disk storage device Click Finish.

See “Changing the location of a disk storage device” on page 320.

See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 335.

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.

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:

To change the configuration 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.
 Disk-based and network-based storage 321
Configuring disk storage

To configure the disk storage device Click Finish.

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 473.
See “Configuring disk storage” on page 317.

Editing disk storage properties

You can edit disk space management settings for the disk storage device.
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:

Name Displays the name of the disk storage. You

can edit this field.

Description Displays a description of the disk storage.

You can edit this field.
 Disk-based and network-based storage 322
Configuring disk storage

Limit Backup Exec to read-only Prevents Backup Exec from deleting

operations 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 335.

See “Backup sets ” on page 341.

See “How to restore data from a reattached

or reinserted disk-based storage device”
on page 327.

Maximum file size 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.
 Disk-based and network-based storage 323
Configuring disk storage

Preallocate disk space incrementally up Creates the file when the backup job starts
to the maximum file size 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.

Preallocation increment 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.

Auto detect block and buffer size 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.
 Disk-based and network-based storage 324
Configuring disk storage

Block size 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.

Buffer 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.
 Disk-based and network-based storage 325
Configuring disk storage

Low disk space - Critical 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 - Warning 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%.

 Disk-based and network-based storage 326
Configuring disk storage

Low disk space 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 335.

Disk space to reserve for non-Backup Displays the amount of disk space to set
Exec operations aside for applications other than Backup
Exec.
The default value is 10 MB.

Auto detect settings Indicates if Backup Exec automatically

detects the preferred settings for read and
write buffers for the disk storage.

Buffered read 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.
 Disk-based and network-based storage 327
How to restore data from a reattached or reinserted disk-based storage device

Buffered write 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.

Concurrent write sessions Displays the number of concurrent write

operations that you want to allow to this
disk storage device.

4 Click Apply.
See “Configuring disk storage” on page 317.

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 473.
See “Backup sets ” on page 341.
 Disk-based and network-based storage 328
Configuring disk cartridge storage

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:

If the Central Admin Server feature is not Click Disk-based storage, and then click
installed Next.

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select the Backup Exec server that you
want to configure storage for, and then
click Next.
■ Click Disk-based storage , and then
click Next.

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:
 Disk-based and network-based storage 329
Configuring disk cartridge storage

To change the configuration 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 configure the disk cartridge device Click Finish.

See “Editing disk cartridge properties” on page 329.

Editing disk cartridge properties

You can edit settings for the disk cartridge storage.
See “Configuring disk cartridge storage” on page 328.
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:

Name Displays the name of the disk cartridge.

Disk cartridge names cannot exceed 128
characters.

You can rename the disk cartridge.

Description Displays a description of the disk cartridge.

You can change the description.

Maximum file size 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.
 Disk-based and network-based storage 330
Configuring disk cartridge storage

Preallocate disk space incrementally up Creates the file when the job starts by
to the maximum file size 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.

Preallocation increment 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.

Auto detect block and buffer size 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.
 Disk-based and network-based storage 331
Configuring disk cartridge storage

Block size 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.

Buffer 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.
 Disk-based and network-based storage 332
Configuring disk cartridge storage

Low disk space - Critical 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 445.

Low disk space - Warning 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 445.

Low disk space 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 445.
 Disk-based and network-based storage 333
Configuring disk cartridge storage

Auto detect settings Indicates if Backup Exec automatically

detects the preferred settings for read and
write buffers for the disk cartridge.

The default value is Enabled.

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 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 write 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.

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 328.
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.
 Disk-based and network-based storage 334
Configuring disk cartridge storage

3 Edit any of the following options:

Media label Displays the media label that Backup Exec

assigns automatically or that the
administrator assigns.

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.

Media description Displays the original media label if the

media is imported media. You can edit the
media description to make it a more
descriptive label. The description is limited
to 128 characters.

Preserve 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 to No by default.
 Disk-based and network-based storage 335
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

Limit Backup Exec to read-only Prevents Backup Exec from deleting

operations 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 335.

See “Backup sets ” on page 341.

See “How to restore data from a reattached

or reinserted disk-based storage device”
on page 327.

4 Click Apply.

How data lifecycle management (DLM) deletes

expired 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, virtual disks, and cloud storage. 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
 Disk-based and network-based storage 336
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

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 345.
See “Changing the expiration date of backup sets on disk-based storage”
on page 344.
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.
 Disk-based and network-based storage 337
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

In a Central Admin Server feature (CAS) 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 670.
See “Audit Log report” on page 704.
Storage options that can affect how data lifecycle management deletes backup
sets are described in the following table:
 Disk-based and network-based storage 338
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

Table 8-4 Storage options in Backup Exec that affect data lifecycle
management

Storage option Description

Allow Backup Exec to delete all expired This global setting lets Backup Exec delete
backup sets 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 feature

(CAS) 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 CAS 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 458.
 Disk-based and network-based storage 339
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

Table 8-4 Storage options in Backup Exec that affect data lifecycle
management (continued)

Storage option Description

Limit Backup Exec to read-only operations This global setting prevents Backup Exec
on a disk-based storage device if it has from deleting expired backup sets on any
been detached for x number of days 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 345.

See “Changing the expiration date of backup

sets on disk-based storage” on page 344.

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 458.
 Disk-based and network-based storage 340
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage

Table 8-4 Storage options in Backup Exec that affect data lifecycle
management (continued)

Storage option Description

Limit Backup Exec to read-only operations This global setting prevents Backup Exec
on a disk cartridge if it has not been from deleting expired backup sets on any disk
inserted for x number of days 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 341.

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 458.

Limit Backup Exec to read-only operations 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 321.

See “Editing disk cartridge properties”

on page 329.

See “Editing the properties of a deduplication

disk storage device” on page 939.
 Disk-based and network-based storage 341
Backup sets

Table 8-4 Storage options in Backup Exec that affect data lifecycle
management (continued)

Storage option Description

Low disk space 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 316.

For information about the best practices of Backup Exec data lifecycle management
(DLM) feature, refer to Backup Exec Best Practices.

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.
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
 Disk-based and network-based storage 342
Backup sets

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

Type of storage Backup data retention

Disk storage, disk cartridge Backup Exec uses data lifecycle management to
devices, deduplication disk automatically delete expired backup sets from disk-based
storage, storage arrays, cloud storage. By default, Backup Exec keeps the most recent
storage, and virtual disks 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 335.

See “How to restore data from a reattached or reinserted

disk-based storage device” on page 327.
 Disk-based and network-based storage 343
Backup sets

Table 8-5 Storage types and backup set retention (continued)

Type of storage Backup data retention

Tape cartridge media 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 402.

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 344.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 345.
See “Releasing retained backup sets on disk-based storage” on page 346.
See “Cataloging backup sets” on page 247.
See “Viewing the contents or properties of backup sets” on page 347.
 Disk-based and network-based storage 344
Backup sets

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
feature (CAS) 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 335.
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:

 Disk-based and network-based storage 345
Backup sets

To expire backup sets ■ Click Expire.

immediately Backup Exec displays the backup set and any
dependent backup sets.
■ To expire the single backup you selected and any
dependent backup sets, click Expire.
If you selected multiple backup sets, click Expire or
Expire All. You can also click Skip to skip a backup
set and its dependents from deletion.

To change the expiration date ■ Click Expiration.

of backup sets ■ Enter the new expiration date in the Expiration field.
■ Click OK.

See “Backup sets ” on page 341.

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 335.
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.
 Disk-based and network-based storage 346
Backup sets

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:

Legal 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.

User defined Select this option if the reason for retaining the backup
sets is something other than a legal one.

System defined This option is used by Backup Exec when a backup set
needs to be retained for some future operations to run.
This option is grayed out and cannot be selected.

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 341.
See “Releasing retained backup sets on disk-based storage” on page 346.

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.
 Disk-based and network-based storage 347
Backup sets

■ 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.
5 Select Do not retain.
6 Click OK.
See “Backup sets ” on page 341.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 345.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 335.

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
 Disk-based and network-based storage 348
Backup sets

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.
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:

To view the contents of the In the left pane, click Contents.

backup sets
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 properties of the In the left pane, click Properties.

backup sets

See “Backup sets ” on page 341.

 Chapter 9
Cloud-based storage
devices
This chapter includes the following topics:

■ About cloud-based storage devices

■ Amazon S3 cloud-based storage

■ Google cloud-based storage

■ Microsoft Azure cloud-based storage

■ Private cloud-based storage

■ About S3-Compatible Cloud Storage

■ Notes for cloud-based storage devices

■ Editing the properties of a cloud-based storage device

■ Best practices for using cloud-based storage

■ Changing default cloud storage settings

■ About the Backup Exec™ CloudConnect Optimizer

About cloud-based storage devices

Backup Exec supports backups to cloud-based storage devices. You can use the
cloud connector to back up and restore data from cloud Storage as a Service
(STaaS) vendors. Cloud-based storage is unlike traditional tape or disk media,
which use persistent backup images. Usually, a public cloud storage vendor
calculates cloud-based storage costs per byte stored and per byte transferred.
 Cloud-based storage devices 350
Amazon S3 cloud-based storage

For the list of supported public and private cloud providers, refer to the Backup
Exec hardware compatibility list.

Note: A cloud storage device cannot belong to any storage pools.

For information about the best practices to manage Backup Exec Cloud Connector,
refer to Backup Exec Best Practices.
The following notes apply to cloud-based storage devices:
■ If you use Backup Exec Central Admin Server feature, you can share a public
cloud storage device between multiple managed Backup Exec servers. You can
enable the sharing when you add a public cloud storage device. You can select
new managed Backup Exec servers to share a public cloud storage device. You
can remove the sharing ability for any managed Backup Exec servers at any
time.
■ Data lifecycle management automatically expires the backup sets that are on
cloud storage.
■ Some cloud storage providers require encryption.
See “Using encryption with Backup Exec” on page 624.

Amazon S3 cloud-based storage

The following sections provide information about the requirements for configuring
an Amazon S3 cloud-based storage device and configure the storage for Amazon
S3 storage in Backup Exec.
See “Requirements for configuring an Amazon S3 cloud-based storage device”
on page 350.
See “Configuring storage for Amazon cloud storage” on page 351.

Requirements for configuring an Amazon S3 cloud-based storage

device
Backup Exec cloud connector enables Backup Exec to back up data to and restore
data from Amazon Simple Storage Service (S3).
Review the following requirements before configuring an Amazon S3 cloud-based
storage device:
■ You must obtain an Amazon Simple Storage Service (S3) account and the
associated user name and password. You also must obtain an Amazon access
key ID and secret access key.
 Cloud-based storage devices 351
Amazon S3 cloud-based storage

■ Ensure that you have already created the buckets. Buckets represent a logical
unit of storage on the cloud-based storage device.

Note: As a best practice, you should create specific buckets to use exclusively
with Backup Exec.
Each cloud storage device must use a different bucket. Do not use the same
bucket for multiple cloud storage devices even if these devices are configured
on different Backup Exec servers.

■ Ensure that the bucket names meet the following Backup Exec requirements:
■ Bucket names can contain lowercase letters, numbers, and dashes (or
hyphens)
■ Bucket names cannot begin with a dash (or a hyphen)
The buckets are not available for use in Backup Exec if the bucket name does
not comply with the bucket naming convention or if you have created a bucket
for a region that Backup Exec does not support.
To review the list of supported regions, refer to the Backup Exec hardware
compatibility list.
See “Configuring storage for Amazon cloud storage” on page 351.

Configuring storage for Amazon cloud storage

You can configure a cloud-based storage device for the Amazon cloud storage,
and then back up data to it.

Note: For cloud-based storage devices, by default, the Do not verify data for this
job option is now selected in the Backup Options. Cloud vendors charge for
operations that read data from and write data to the cloud. To avoid charges for
reading data during the verify operation of a backup or duplicate job, this option is
selected by default.
See “Configuring automatic verify operations for backup jobs” on page 563.

See “Adding a stage to a backup definition” on page 214.

See “Requirements for configuring an Amazon S3 cloud-based storage device”
on page 350.
 Cloud-based storage devices 352
Amazon S3 cloud-based storage

To configure storage for Amazon cloud storage in Backup Exec

1 On the Backup and Restore tab, click the Back Up > Backup to Cloud option
and then click OK.
Or, on the Storage tab, in the Configure Storage group, click Cloud Storage
and then click Next.
Or, on the Storage tab, click Configure Cloud Storage.
2 Enter a name and description for the cloud storage device, and then click Next.
3 From the list of cloud storage providers, select S3, and then click Next.
4 In the Cloud storage field, select the Amazon server name from the drop-down
list.
5 In the Storage tier field, select a tier from the drop-down list.
The options are Standard (for frequently accessed data), Standard_IA
(Infrequently accessed data), Glacier, Deep Archive, Intelligent_Tiering, or
One Zone_IA (Infrequently accessed data).

Note: To restore from Glacier and Deep Archive storage device is a time
consuming activity. Refer to the Amazon documentation for more information
about retrieval time delay.

6 In the Logon account field, select an account from the drop-down list or click
Add/Edit to add an account.
7 On the Logon account selection dialog box, click Add.
8 On the Add Logon Credentials dialog box, do the following:
■ In the User name field, type the Amazon account access key ID.
■ In the Password field, type the Amazon account secret access key.
■ In the Confirm password field, type the Amazon account secret access
key again.
■ In the Account name field, type a name for this logon account.
The Backup Exec user interface displays this name as the cloud storage
device name in all storage device options lists.

9 Click OK twice.
10 Select the Amazon logon account that you created in step 7, and then click
Next.
11 Select a bucket from the list of buckets that are associated with the server
name and then click Next.
 Cloud-based storage devices 353
Google cloud-based storage

12 Specify how many concurrent operations can run at the same time on this
cloud storage device, and then click Next.
This setting determines the number of jobs that can run at the same time on
this device. The suitable value for this setting may vary depending on your
environment and the bandwidth to the cloud storage. You may choose the
default value.
13 Review the configuration summary, and then click Finish.
Backup Exec creates a cloud storage device. You must restart Backup Exec
services to bring the new device online.
14 In the window that prompts you to restart the Backup Exec services, click Yes.
After services restart, Backup Exec displays the new cloud storage location in
the All Storage list.

Google cloud-based storage

The following sections provide information about the requirements to configure a
Google cloud-based storage device and configure the storage for Google storage
in Backup Exec.
See “Requirements for configuring a Google cloud-based storage device”
on page 353.
See “Configuring storage for Google cloud storage” on page 354.

Requirements for configuring a Google cloud-based storage device

Backup Exec cloud connector enables Backup Exec to back up data to and restore
data from Google cloud storage.
Review the following requirements before configuring a Google cloud-based storage
device:
■ You must obtain a Google cloud platform account and the associated user name
and password. You also must obtain a Google S3 interoperability access key
and a Google S3 interoperability secret key.
You can generate these keys in the Google Developers Console.
■
Note: As a best practice, you should create specific buckets to use exclusively
with Backup Exec.
Each cloud storage device must use a different bucket. Do not use the same
bucket for multiple cloud storage devices even if these devices are configured
on different Backup Exec servers.
 Cloud-based storage devices 354
Google cloud-based storage

Ensure that you have already created the buckets. Buckets represent a logical
unit of storage on the cloud-based storage device.
■ Ensure that the bucket names meet the following Backup Exec requirements:
■ Bucket names can contain lowercase letters, numbers, and dashes (or
hyphens)
■ Bucket names cannot begin with a dash (or a hyphen)
The buckets are not available for use in Backup Exec if the bucket name does
not comply with the bucket naming convention or if you have created a bucket
for a region that Backup Exec does not support.
To review the list of supported regions, refer to the Backup Exec hardware
compatibility list.
See “Configuring storage for Google cloud storage” on page 354.

Configuring storage for Google cloud storage

You can configure a cloud-based storage device for the Google cloud storage, and
then back up data to it.

Note: For cloud-based storage devices, by default, the Do not verify data for this
job option is now selected in the Backup Options. Cloud vendors charge for
operations that read data from and write data to the cloud. To avoid charges for
reading data during the verify operation of a backup or duplicate job, this option is
selected by default.

See “Configuring automatic verify operations for backup jobs” on page 563.
See “Adding a stage to a backup definition” on page 214.
See “Requirements for configuring a Google cloud-based storage device”
on page 353.
To configure storage for Google cloud storage in Backup Exec
1 On the Backup and Restore tab, click the Back Up > Backup to Cloud option
and then click OK.
Or, on the Storage tab, in the Configure Storage group, click Cloud Storage
and then click Next.
Or, on the Storage tab, click Configure Cloud Storage.
2 Enter a name and description for the cloud storage device, and then click Next.
3 From the list of cloud storage providers, select S3, and then click Next.
 Cloud-based storage devices 355
Google cloud-based storage

4 In the Cloud storage field, select the Google server name from the drop-down
list.
5 In the Logon account field, select an account from the drop-down list or click
Add/Edit to add an account.
6 On the Logon Account Selection dialog box, click Add.
7 On the Add Logon Credentials dialog box, do the following:
■ In the User name field, type the Google account access key ID.
■ In the Password field, type the Google account secret access key.
■ In the Confirm password field, type the Google account secret access key
again.
■ In the Account name field, type a name for this logon account.
The Backup Exec user interface displays this name as the cloud storage device
name in all storage device options lists.
8 Click OK twice.
9 Select the Google logon account that you created in step 7, and then click
Next.
10 Select a bucket from the list of buckets that are associated with the server
name and then click Next.
11 Specify how many concurrent operations can run at the same time on this
cloud storage device, and then click Next.
This setting determines the number of jobs that can run at the same time on
this device. The suitable value for this setting may vary depending on your
environment and the bandwidth to the cloud storage. You may choose the
default value.
12 Review the configuration summary, and then click Finish.
Backup Exec creates a cloud storage device. You must restart Backup Exec
services to bring the new device online.
13 In the window that prompts you to restart the Backup Exec services, click Yes.
After services restart, Backup Exec displays the new cloud storage location in
the All Storage list.
 Cloud-based storage devices 356
Microsoft Azure cloud-based storage

Microsoft Azure cloud-based storage

The following sections provide information about the requirements to configure a
Microsoft Azure cloud-based storage device and configure the storage for Microsoft
Azure storage in Backup Exec.
See “Configuring storage for Microsoft Azure cloud storage” on page 357.

Requirements for configuring a Microsoft Azure cloud-based storage

device
Backup Exec cloud connector enables Backup Exec to back up data to and restore
data from Microsoft Azure cloud-based storage device.
Review the following requirements before configuring a Microsoft Azure cloud-based
storage device:
■ You must obtain the Microsoft Azure storage account and at least one storage
access key (primary access key or secondary access key).
■ Ensure that you have already created the blob storage containers for the storage
account. Blob storage containers represent a logical unit of storage on the
cloud-based storage device.

Note: As a best practice, you should create specific containers to use exclusively
with Backup Exec.
Each cloud storage device must use a different container. Do not use the same
container for multiple cloud storage devices even if these devices are configured
on different Backup Exec servers.

■ Ensure that the container names meet the following Backup Exec requirements:
■ Container names can contain lowercase letters, numbers, and dashes (or
hyphens)
■ Containers names cannot begin with a dash (or a hyphen)
The containers are not available for use in Backup Exec if the container name
does not comply with the container naming convention.
To review the list of supported regions, refer to the Backup Exec hardware
compatibility list.
See “Configuring storage for Microsoft Azure cloud storage” on page 357.
 Cloud-based storage devices 357
Microsoft Azure cloud-based storage

Configuring storage for Microsoft Azure cloud storage

You can configure a cloud-based storage device for the Microsoft Azure cloud
storage, and then back up data to it.

Note: For cloud-based storage devices, by default, the Do not verify data for this
job option is now selected in the Backup Options. Cloud vendors charge for
operations that read data from and write data to the cloud. To avoid charges for
reading data during the verify operation of a backup or duplicate job, this option is
selected by default.

See “Configuring automatic verify operations for backup jobs” on page 563.
See “Requirements for configuring a Microsoft Azure cloud-based storage device”
on page 356.
To configure storage for Microsoft Azure cloud storage in Backup Exec
1 On the Backup and Restore tab, click the Back Up > Backup to Cloud option
and then click OK.
Or, on the Storage tab, in the Configure Storage group, click Cloud Storage
and then click Next.
Or, on the Storage tab, click Configure Cloud Storage.
2 Enter a name and description for the cloud storage device, and then click Next.
3 From the list of cloud storage providers, select Azure, and then click Next.
4 In the Cloud storage field, select the Microsoft Azure server name from the
drop-down list.
5 In the Logon account field, select an account from the drop-down list or click
Add/Edit to add an account.
6 On the Logon Account Selection dialog box, click Add.
7 On the Add Logon Credentials dialog box, do the following:
■ In the User name field, type the Microsoft Azure storage user name.
■ In the Password field, type the Microsoft Azure storage account access
key. You can enter the primary access key or the secondary access key.
■ In the Confirm password field, type the Microsoft Azure storage account
access key again.
■ In the Account name field, type a name for this logon account.
The Backup Exec user interface displays this name as the cloud storage
device name in all storage device options lists.
 Cloud-based storage devices 358
Private cloud-based storage

8 Click OK twice.
9 Select the Microsoft Azure logon account that you created in step 7, and then
click Next.
10 Select a container from the list of containers that are associated with the server
name and then click Next.
11 Specify how many concurrent operations can run at the same time on this
cloud storage device, and then click Next.
This setting determines the number of jobs that can run at the same time on
this device. The suitable value for this setting may vary depending on your
environment and the bandwidth to the cloud storage. You may choose the
default value.
12 Review the configuration summary, and then click Finish.
Backup Exec creates a cloud storage device. You must restart Backup Exec
services to bring the new device online.
13 In the window that prompts you to restart the Backup Exec services, click Yes.
After services restart, Backup Exec displays the new cloud storage location in
the All Storage list.

Private cloud-based storage

The following sections provide information about the requirements to configure a
private cloud-based storage device and configure the storage for private storage
in Backup Exec. There are also sections that provide information about how to
create, view, edit, and delete a cloud instance for a private cloud.
See “Requirements for configuring a private cloud-based storage device”
on page 358.
See “Configuring storage for a private cloud-based storage device” on page 360.
See “Creating a cloud instance for a private cloud” on page 360.
See “Viewing and editing existing cloud instances for a private cloud” on page 362.
See “Deleting a cloud instance for a private cloud” on page 362.

Requirements for configuring a private cloud-based storage device

Backup Exec cloud connector enables Backup Exec to back up data to and restore
data from a private cloud-based storage device.
Review the following requirements before configuring a private cloud-based storage
device:
 Cloud-based storage devices 359
Private cloud-based storage

■ Configure the private cloud-based storage server in your environment.

Create an account to access the private cloud-based storage server before you
configure a cloud storage device in Backup Exec. You must also obtain the
private cloud-based storage server's access key ID and secret access key.
■ Ensure that buckets are already created in the private cloud storage server.
Buckets represent a logical unit of storage on the cloud-based storage device.

Note: As a best practice, you should create specific buckets to use exclusively
with Backup Exec.
Each cloud storage device must use a different bucket. Do not use the same
bucket for multiple cloud storage devices even if these devices are configured
on different Backup Exec servers.

■ Ensure that the bucket names meet the following Backup Exec requirements:
■ Bucket names can contain lowercase letters, numbers, and dashes (or
hyphens)
■ Bucket names cannot begin with a dash (or a hyphen)

Note: The buckets are not available for use in Backup Exec if the bucket
name does not comply with the bucket naming convention.

■ Create a cloud instance for the private cloud storage server.

See “Creating a cloud instance for a private cloud” on page 360.
■ Ensure that the private cloud-based storage server has a Certificate Authority
(CA)-signed certificate. Backup Exec supports only CA-signed certificates while
it communicates with the private cloud storage in the SSL mode. If it does not
have the CA-signed certificate, data transfer between Backup Exec and the
private cloud provider may fail in the SSL mode.
While creating a cloud instance you can decide to use the SSL protocol. Backup
Exec supports backup to a private cloud storage even if you decide not to use
the SSL protocol when you create a cloud instance.
To review the list of supported regions, refer to the Backup Exec hardware
compatibility list.
See “Configuring storage for a private cloud-based storage device” on page 360.
 Cloud-based storage devices 360
Private cloud-based storage

Creating a cloud instance for a private cloud

Before configuring a cloud storage device for a private cloud provider, you must
create a custom cloud instance for the private cloud storage server.
Type the following command in BEMCLI to create a custom cloud instance:
New-BECloudInstance

Before you create a storage device for a private cloud, you must run this command.
Ensure that the cloud instance name meets the following Backup Exec requirements:
■ It can contain letters, numbers, and dashes (or hyphens).
■ It cannot begin with a dash (or a hyphen).

Note: You must create only one cloud instance on a Backup Exec server for a
private cloud storage server. You can create another cloud instance on a different
Backup Exec server for the same private cloud storage server.

For more 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:<Backup Exec install path>\Backup Exec
See “Configuring storage for a private cloud-based storage device” on page 360.
See “Requirements for configuring a private cloud-based storage device”
on page 358.

Configuring storage for a private cloud-based storage device

You can configure a private cloud-based storage device, and then back up data to
it. Before configuring a cloud storage device for a private cloud storage server, you
must create a custom cloud instance for the private cloud storage server.

Note: For cloud-based storage devices, by default, the Do not verify data for this
job option is now selected in the Backup Options. Cloud vendors charge for
operations that read data from and write data to the cloud. To avoid charges for
reading data during the verify operation of a backup or duplicate job, this option is
selected by default.

See “Configuring automatic verify operations for backup jobs” on page 563.
See “Creating a cloud instance for a private cloud” on page 360.
 Cloud-based storage devices 361
Private cloud-based storage

See “Adding a stage to a backup definition” on page 214.

See “Requirements for configuring a private cloud-based storage device”
on page 358.
To configure storage for a private cloud-based storage device
1 On the Backup and Restore tab, click the Back Up > Backup to Cloud option
and then click OK.
Or, on the Storage tab, in the Configure Storage group, click Cloud Storage
and then click Next.
Or, on the Storage tab, click Configure Cloud Storage.
2 Enter a name and description for the cloud storage device, and then click Next.
3 From the list of cloud storage providers, select S3, and then click Next.
4 In the Cloud storage field, select the private cloud-based storage server name
from the drop-down list.
5 In the Logon account field, select an account from the drop-down list or click
Add/Edit to add an account.
6 On the Logon Account Selection dialog box, click Add.
7 On the Add Logon Credentials dialog box, do the following:
■ In the User name field, type the private cloud-based storage account access
key ID.
■ In the Password field, type the private cloud-based storage device secret
access key.
■ In the Confirm password field, type the private cloud-based storage
account secret access key again.
■ In the Account name field, type a name for this logon account.
The Backup Exec user interface displays this name as the cloud storage device
name in all storage device options lists.
8 Click OK twice.
9 Select the private cloud-based storage logon account that you created in step
7, and then click Next.
10 Select a bucket from the list of buckets that are associated with the server
name and then click Next.
 Cloud-based storage devices 362
Private cloud-based storage

11 Specify how many concurrent operations can run at the same time on this
cloud storage device, and then click Next.
This setting determines the number of jobs that can run at the same time on
this device. The suitable value for this setting may vary depending on your
environment and the bandwidth to the cloud storage. You may choose the
default value.
12 Review the configuration summary, and then click Finish.
Backup Exec creates a cloud storage device. You must restart Backup Exec
services to bring the new device online.
13 In the window that prompts you to restart the Backup Exec services, click Yes.
After services restart, Backup Exec displays the new cloud storage location in
the All Storage list.

Viewing and editing existing cloud instances for a private cloud

Type the following command in BEMCLI to view a custom cloud instance:
Get-BECloudInstance

Type the following command in BEMCLI to edit a custom cloud instance:

Set-BECloudInstance

Note: You cannot edit the cloud instance name and cloud provider of a custom
cloud instance.
You must create only one cloud instance on a Backup Exec server for a private
cloud storage server. You can create another cloud instance on a different Backup
Exec server for the same private cloud storage server.

For more 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:<Backup Exec install path>\Backup Exec
See “Creating a cloud instance for a private cloud” on page 360.
See “Deleting a cloud instance for a private cloud” on page 362.

Deleting a cloud instance for a private cloud

Type the following command in BEMCLI to delete a custom cloud instance:
Remove-BECloudInstance
 Cloud-based storage devices 363
About S3-Compatible Cloud Storage

Note: Before deleting a cloud instance, delete the private cloud storage devices
that are attached to that cloud instance.
See “Deleting a storage device” on page 468.

For more 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:<Backup Exec install path>\Backup Exec
See “Creating a cloud instance for a private cloud” on page 360.

About S3-Compatible Cloud Storage

Backup Exec provides the S3-compatible cloud storage feature. You can use the
S3 provider to configure S3-compatible cloud storage devices with Backup Exec.
When the configuration process is complete, you can create a storage device within
the Backup Exec console that can access S3 compatible cloud environments. S3
compatible communications have not been tested in all cloud environments and
may not work in some cases.
S3 compatible environments that are not specifically listed in the Backup Exec
Hardware Compatibility List are considered alternative configurations. The Backup
Exec Hardware Compatibility List defines alternative configurations as:
Alternative Configurations: Our Licensed Software is designed to interoperate
with many types of systems, applications, and hardware. Sometimes a customer
may choose to use our Licensed Software in an "Alternative Configuration", namely,
an environment that has not been validated, approved or verified to operate with
our Licensed Software or which does not support such Licensed Software or only
supports limited functionality. In most cases, we do not support Alternative
Configurations, and we have no obligation to provide Support Services to Licensed
Software in an Alternative Configuration. We make no warranty with respect to use
of Licensed Software in an Alternative Configuration and any such use is at your
own risk. A "Supported Configuration" might be converted into an Alternative
Configuration where a vendor modifies one of its components that is part of the
original Supported Configuration. As a consequence, your Licensed Software would
then be operating in an Alternative Configuration. If you experience a problem with
the Licensed Software in an Alternative Configuration or if your issue deals with
script that was developed by an unauthorized consulting partner, then we may ask
you to reproduce the problem in a Supported Configuration environment. Please
note we have no obligation to attempt to resolve problems that cannot be replicated
in a Supported Configuration. However, if the problem can be replicated in a
 Cloud-based storage devices 364
About S3-Compatible Cloud Storage

Supported Configuration, we will investigate the problem in that Supported

Configuration and attempt to resolve it. If the problem cannot be replicated in a
Supported Configuration, then we may elect not to work on that problem.
See “Amazon S3 cloud-based storage” on page 350.
See “Google cloud-based storage” on page 353.
See “Private cloud-based storage” on page 358.
See “Configuring S3-Compatible Cloud Storage with Backup Exec” on page 364.

Configuring S3-Compatible Cloud Storage with Backup Exec

You can configure S3-compatible cloud storage that Backup Exec can access.
To configure S3-Compatible Cloud Storage with Backup Exec
1 Configure a cloud instance using the Backup Exec Command Line Interface
(BEMCLI) and provide the cloud location and configuration parameters to the
Backup Exec server.
To configure a cloud instance, you must pre-configure a user account and
buckets in the cloud environment.
For S3, following is an example command:
New-BECloudInstance -Name "CloudInstance0001" -Provider
"compatible-with-s3" - ServiceHost "s3.yourendpoint.com" -SslMode
"Disabled" -HttpPort 80 - HttpsPort 443

Where ServiceHost is replaced with your cloud server endpoint address.

In this example command, the SslMode is Disabled. Backup Exec supports
the SSL protocol. While creating a cloud instance you can decide to use the
SSL protocol. It is recommended that the SslMode be Enabled.
Ensure that the S3-compatible cloud-based storage server has a Certificate
Authority (CA)-signed certificate. Backup Exec supports only CA-signed
certificates while it communicates with the S3-compatible cloud storage in the
SSL mode. If it does not have the CA-signed certificate, data transfer between
Backup Exec and the S3-compatible cloud provider may fail in the SSL mode.
2 Create a cloud storage device in Backup Exec using the storage device
configuration wizard. Then select the newly created cloud instance and the S3
account credentials that can be used to access the S3-compatible cloud.
See “Amazon S3 cloud-based storage” on page 350.
See “Google cloud-based storage” on page 353.
See “Private cloud-based storage” on page 358.
 Cloud-based storage devices 365
Notes for cloud-based storage devices

See “About S3-Compatible Cloud Storage” on page 363.

Notes for cloud-based storage devices

Glacier and Glacier Deep Archive support
The following information applies to Glacier and Glacier Deep Archive support:
■ Backing up to a cloud storage device:
When the backup sets are deleted, the storage provider still incurs charges
based on their pricing model.
For example: Go to Backup Exec > Configuration and Settings > Job Defaults
> Storage
Set the Keep for value - 1 month
In Amazon set the time for which you want to keep the backup sets as 3 months
Even if you delete the data before 3 months, the cloud provider charges based
on what is set in Amazon, that is for complete 3 months.
■ Restoring from cloud:
Restore from Glacier and Deep Archive uses Standard retrieval that can take
from 3 to 12 hours depending on the storage device that you selected. The
restore operation is time consuming.
■ When you select Glacier or Deep Archive, the Inventory and Catalog now and
Catalog operations are disabled for Glacier and Glacier Deep Archive storage
at the device level. You can run the Inventory operation independently on this
storage device.
The Catalog operation is supported only for an individual media.
You can run the catalog of individual media by performing the following steps
in the order listed:
■ Set the registry value from the Backup Exec server to show hidden cloud
media.
HKLM:\SOFTWARE\Veritas\Backup Exec For Windows\BackupExec\User
Interface
DWORD value: ShowHiddenMedia set it to 1.
■ Catalog individual media by running the following command from BEMCLI:
Get-BEMedia OST00000170 | Submit-BECatalogMediaJob
OST00000170 is the example media name in this catalog command.
 Cloud-based storage devices 366
Editing the properties of a cloud-based storage device

Editing the properties of a cloud-based storage

device
You can view all of the properties of a cloud-based storage device and you can
change some of the properties.
To edit the properties of a cloud-based storage device
1 On the Storage tab, double-click the name of the cloud storage device.
2 In the left pane, click Properties.
 Cloud-based storage devices 367
Editing the properties of a cloud-based storage device

3 Change the following properties as needed:

Name Indicates the user-defined name for this

cloud storage device.

You can modify this field.

Description Indicates the user-defined description of

this cloud storage device.

You can modify this field.

State Indicates the current state of the device.

You cannot modify this field.

Cloud Storage Indicates the fully qualified name of the

server on which the device exists.

You cannot modify this field.

Storage location Indicates the name of the server on which

the device exists.

You cannot modify this field.

Storage type Indicates the type of cloud storage device.

You cannot modify this field.

Bucket/Storage container Indicates the name of the storage location

on the cloud storage device. These storage
units are called buckets.
You cannot modify this field.

Storage tier Indicates the name of the storage tier.

You cannot modify this field.

Note: This field displays N/A if the storage
tiers are not supported for a cloud storage
device.

Backup Exec server with device Indicates the Backup Exec server that has
proximity physical or logical proximity to the storage
device to run operations for that device.

Use this field in a CAS environment.

Logon account Indicates the name of the logon account

that is required to access the device.

You can modify this field.

 Cloud-based storage devices 368
Best practices for using cloud-based storage

Concurrent operations Indicates the maximum number of jobs that

you want to run at the same time on this
device.

You can modify this field.

Backup data written Shows only the amount of the space used
for the backed-up data.

Connection type Indicates the type of connection between

the Backup Exec server and the cloud
storage device. The connection type is
Network.

You cannot modify this field.

Backup Exec service restart needed Indicates if the Backup Exec services must
be restarted to apply any changes that are
made to this device.

You cannot modify this field.

4 Click Apply to save the changes.

Best practices for using cloud-based storage

Table 9-1 Best practices for using cloud-based storage

Item Best practice

Data encryption when Some public cloud storage providers require encryption to be
backing up data to a enabled when backup jobs or duplicate jobs are targeted to cloud
public cloud storage storage.
device
All data is secured using SSL during data transfer from Backup
Exec to a public cloud-based storage device. However, Backup
Exec jobs must have encryption enabled to encrypt the data
at-rest in the public cloud storage.

See “Using encryption with Backup Exec” on page 624.

Network usage and During data transfer, a cloud-based storage device consumes
backups to a cloud high bandwidth. This might affect the functioning of any other
storage device critical applications running at that time. Therefore, it is
recommended that you schedule the backup jobs or duplicate
backup jobs to a cloud storage device at a time when the
bandwidth consumption by other applications is relatively less.
 Cloud-based storage devices 369
Changing default cloud storage settings

Table 9-1 Best practices for using cloud-based storage (continued)

Item Best practice

Backup Exec Best practices for Backup Exec CloudConnect Optimizer

CloudConnect Optimizer
■ If you have multiple devices for the same cloud provider, you
can run the CloudConnect Optimizer job for any one of the
devices as the suggested write connection value is applicable
for all devices of that cloud server type.
■ Run the CloudConnect Optimizer job close to the backup
window so that the Backup Exec CloudConnect Optimizer
and backup to cloud jobs run in a similar network environment.
Ensure that you have enough time so that the CloudConnect
Optimizer job finishes and then the backup to cloud job starts.
■ When you run the CloudConnect Optimizer job, ensure that
no backups are running to cloud. This is to ensure that no
other backup jobs are sharing the network bandwidth with the
Backup Exec CloudConnect Optimizer.
■ It is recommended that you run the CloudConnect Optimizer
job, when you configure a cloud storage device, and after you
restart the backup exec services.

See “About the Backup Exec™ CloudConnect Optimizer”

on page 370.

See “Configuring the Backup Exec™ CloudConnect Optimizer”

on page 371.

See “Editing the CloudConnect Optimizer job” on page 372.

See “Deleting the CloudConnect Optimizer job” on page 373.

Changing default cloud storage settings

The default cloud storage settings are now enabled in Backup Exec to reduce the
storage read write errors that appear when the network is not able to handle the
number of connections from the Backup Exec media server to the cloud storage
provider.
These connections to cloud are for reading information from the cloud and writing
information to the cloud. These are the maximum number of connections that Backup
Exec can open.
Currently, the maximum in the connection range is set by default for the read and
write connections. It is recommended that you change the values only if there are
constant backup failures due to network or bandwidth issues with the set value. In
such a case, run the Backup Exec CloudConnect Optimizer in Backup Exec, which
 Cloud-based storage devices 370
About the Backup Exec™ CloudConnect Optimizer

suggests the number of write connections suitable for a backup job in your
environment.
The Backup Exec CloudConnect Optimizer displays a job log with the suggested
Write Connections value for the specific cloud server type. This value is updated
to the Backup Exec settings if you select the Use the suggested number of Write
Connections for the upcoming jobs check box in the Backup Exec CloudConnect
Optimizer.
See “Configuring the Backup Exec™ CloudConnect Optimizer” on page 371.
You can change the read and write connection values for each type of cloud storage
server that is supported by Backup Exec. For backup or restore jobs running on
cloud devices, it is recommended that you change the read and write connection
values only during network and bandwidth issues. For more information, refer to
the Backup Exec Best Practices document.
To change the default storage settings
1 Click the Backup Exec button, click Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, click Cloud Storage.
3 Edit any of the following options:

Cloud server type Displays the type of cloud server.

Connection range Displays the connection range for each type of cloud server.

Read connections Lets you select the number of read connections for each type
of cloud server. The default value for each cloud server is
already selected.

The default values are set as per the best practices suggested
by Backup Exec.

Write connections Lets you select the number of write connections for each type
of cloud server. The default value for each cloud server is
already selected.

The default values are set as per the best practices suggested
by Backup Exec.

About the Backup Exec™ CloudConnect Optimizer

Run the Backup Exec CloudConnect Optimizer to get a suggested Write Connections
value that utilizes the available bandwidth. After the CloudConnect Optimizer job
 Cloud-based storage devices 371
About the Backup Exec™ CloudConnect Optimizer

is completed, the log gives you the results of the job and the suggested write
connections value.
See “Changing default cloud storage settings” on page 369.
After you run the CloudConnect Optimizer job for any cloud storage device, the job
log displays the suggested Write Connections value for the specific cloud server
type. This value is updated to the Backup Exec settings if you select the Use the
suggested number of Write Connections for the upcoming jobs check box in
the CloudConnect Optimizer.
The Write Connections value is specific to a cloud server type. There can be multiple
cloud devices with the same cloud server type and the value suggested by the
CloudConnect Optimizer would be the same for all the cloud devices of that specific
cloud server type. If you select multiple devices that have different cloud providers,
you need to need to run the CloudConnect Optimizer job for each device.
It is recommended that you run the CloudConnect Optimizer job close to the backup
window and do not run any other backup jobs to the cloud at the same time.
See “Configuring the Backup Exec™ CloudConnect Optimizer” on page 371.
See “Editing the CloudConnect Optimizer job” on page 372.
See “Deleting the CloudConnect Optimizer job” on page 373.

Configuring the Backup Exec™ CloudConnect Optimizer

You can configure and run the CloudConnect Optimizer job to get a suggested
Write Connections value.
To configure the CloudConnect Optimizer job
1 On the Storage tab, right-click a cloud storage device and click CloudConnect
Optimizer.
2 On the Backup Exec CloudConnect Optimizer dialog box, in the General
tab, edit any of the following options.

Job name Displays a name for the CloudConnect Optimizer job.

You can edit the name of the job.

Cloud server type Displays the type of cloud server.

Use the suggested number of Select the check box to update the suggested value
Write Connections for the in the Backup Exec settings.
upcoming jobs

3 Click the Schedule tab.

 Cloud-based storage devices 372
About the Backup Exec™ CloudConnect Optimizer

4 In the Schedule options, edit any of the following options.

Run now Runs the job immediately.

Run on Schedules the job to run on a specific date and time.

5 Click OK.
The CloudConnect Optimizer job runs based on whether you have scheduled
for it to run immediately or scheduled for a later date.
In case of CAS-MMS scenario, from the Central Admin Server (CAS), you can
create a CloudConnect Optimizer job only for the devices that are local to the
CAS server or the one shared with the CAS server. For devices that are local
to the Managed Media Server (MMS), a CloudConnect Optimizer job can only
be created from that particular MMS. If a cloud storage device is shared
between CAS and MMS, and you want job to run on MMS, you must to create
job from MMS only. The CloudConnect Optimizer job runs on the media server
where the job is created.
The CloudConnect Optimizer job is displayed on the Job Monitor and Storage
tab. If the CloudConnect Optimizer job is scheduled for a later date, the job
status displays the Scheduled status. After the job completes successfully,
the Job Monitor > Job Histories section and Storage > Job History section
displays the job details and the job status.
After the CloudConnect Optimizer job completes, the job log displays the
suggested Write Connections value. If you have selected the check box to
update the suggested value in the Backup Exec settings, this value is updated
and used for the upcoming jobs. A confirmation message is displayed that the
value is successfully updated in the Backup Exec settings.
See “Changing default cloud storage settings” on page 369.
See “About the Backup Exec™ CloudConnect Optimizer” on page 370.
See “Editing the CloudConnect Optimizer job” on page 372.
See “Deleting the CloudConnect Optimizer job” on page 373.

Editing the CloudConnect Optimizer job

You can edit a scheduled CloudConnect Optimizer job.
 Cloud-based storage devices 373
About the Backup Exec™ CloudConnect Optimizer

To edit the CloudConnect Optimizer job

1 Do one of the following:

To edit a CloudConnect On the Job Monitor tab, right-click the scheduled

Optimizer job from the Job CloudConnect Optimizer job and then click Edit.
Monitor tab.

To edit a CloudConnect On the Storage tab, right-click the scheduled

Optimizer job from the CloudConnect Optimizer job and then click Edit.
Storage tab.

2 On the CloudConnect Optimizer dialog box, make any necessary changes.

3 Click OK.
See “About the Backup Exec™ CloudConnect Optimizer” on page 370.
See “Configuring the Backup Exec™ CloudConnect Optimizer” on page 371.
See “Deleting the CloudConnect Optimizer job” on page 373.

Deleting the CloudConnect Optimizer job

You can delete a scheduled CloudConnect Optimizer job.
To delete the CloudConnect Optimizer job
1 Do one of the following:

To delete a CloudConnect On the Job Monitor tab, locate the scheduled

Optimizer job from the Job CloudConnect Optimizer job that you want to delete.
Monitor tab.

To delete a CloudConnect On the Storage tab, locate the scheduled

Optimizer job from the Storage CloudConnect Optimizer job that you want to delete.
tab.

2 Right-click the scheduled job, and then click Delete.

3 Click Yes.
See “About the Backup Exec™ CloudConnect Optimizer” on page 370.
See “Configuring the Backup Exec™ CloudConnect Optimizer” on page 371.
See “Editing the CloudConnect Optimizer job” on page 372.
 Chapter 10
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.
 Legacy backup-to-disk folders 375
Legacy backup-to-disk folders

You cannot send backup data to a backup-to-disk folder. It is recommended 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 313.
See “Restoring data from a legacy backup-to-disk folder” on page 377.
See “Changing the location of a legacy backup-to-disk folder” on page 376.
See “Recreating a legacy backup-to-disk folder and its contents” on page 377.

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 374.
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:

Name Displays the name of the backup-to-disk

folder. Backup-to-disk folder names must
not exceed 128 characters.

Description Displays the description of the

backup-to-disk folder.

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:
 Legacy backup-to-disk folders 376
Legacy backup-to-disk folders

Auto detect buffers Indicates if Backup Exec automatically

detects the preferred settings for read
buffers for the backup-to-disk folder.

Buffered reads 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.

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 374.
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.
 Legacy backup-to-disk folders 377
Legacy backup-to-disk folders

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 377.
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 374.
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 377.
3 Right-click the backup-to-disk folder, and then click Inventory and Catalog.
See “Inventorying and cataloging a storage device” on page 473.

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 344.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 345.
 Legacy backup-to-disk folders 378
Legacy backup-to-disk folders

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:

If the Central Admin Server feature is not Select Disk-based Storage, and then click
installed Next.

If the Central Admin Server feature is Do the following in the order listed:
installed
■ 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.

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:

To change the configuration 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 import the legacy backup-to-disk folder Click Finish.

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.
 Legacy backup-to-disk folders 379
Legacy backup-to-disk folders

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.
 Chapter 11
Tape storage
This chapter includes the following topics:

■ Support for tape drives and robotic libraries

■ Adding or replacing devices with the Hot-swappable Device Wizard

■ Installing 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

■ Editing tape media properties

■ Tape media rotation strategies

 Tape storage 381
Support for tape drives and robotic libraries

Support for tape drives and robotic libraries

When you install Backup Exec, it automatically recognizes all tape storage devices
that are attached to the Backup Exec server.
Support for tape drives and libraries varies across Backup Exec editions. Please
refer to the licensing information specific to your edition for more information.
You can use the Configure Storage wizard to perform the following actions for
tape storage:
■ Partition robotic library slots.
■ Install tape device drivers.

Note: You do not need to install tape device drivers if Backup Exec runs on
Windows Server 2012 and later. Kernel-mode drivers and tapeinste.exe are no
longer installed if Backup Exec runs on Windows Server 2012 and later.
See “Installing tape device drivers ” on page 382.

■ 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 “Default media sets” on page 402.
See “Viewing jobs, job histories, backup sets, and active alerts for storage devices”
on page 470.

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.
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.
 Tape storage 382
Installing tape device drivers

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 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:

For iSCSI-attached storage: In the iSCSI control panel applet, add the
storage to the Persistent Targets list.

Continue with the next step.

For any other hot-swappable storage: Continue with the next step.

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.

Installing 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:
kernel-mode tape drivers and tapeinst.exe
Before you install tape device drivers, do the following:
■ Ensure that Backup Exec supports the tape device.
 Tape storage 383
Installing tape device drivers

You can find a list of compatible types of storage in the Backup Exec hardware
compatibility list.
■ 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 Device Driver Installation Wizard, in the following procedure.
To install 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 Device Driver Installation Wizard, follow the on-screen prompts.

kernel-mode tape drivers and tapeinst.exe

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 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.
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.
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.
 Tape storage 384
Editing tape drive properties

To install 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:<Backup Exec install path>\Backup Exec
2 On the 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 381.
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.
 Tape storage 385
Editing tape drive properties

3 Edit any of the following options:

Name Displays the name of the tape drive. You

can edit this field.

Description Displays the description of the tape drive.

You can edit this field.

Hardware compression Indicates if hardware compression is

enabled.

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.
 Tape storage 386
Editing tape drive properties

Block size 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.

Buffer 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.
 Tape storage 387
Editing tape drive properties

Buffer count 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.

High water 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.

Reset to default settings Returns all of the preferred configuration

settings to their defaults.

Read single block mode 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.

Write 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.

It is recommended that you select this

option if the tape drive is shared.

This option is enabled by default.

 Tape storage 388
Editing tape drive properties

Read SCSI pass-through mode 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.

Write 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.

It is recommended that you select this

option if the tape drive is shared.

This option is enabled by default.

Servers that share this device Displays the servers that can also use this
device.

See “Sharing storage devices” on page 467.

Media Type 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 391.

Can Read From Indicates if this tape drive can read from
the media type.
See “Configuring barcode rules for a
robotic library ” on page 391.
 Tape storage 389
Viewing tape drive statistics

Can Write To Indicates if this tape drive can write to this

media type.

See “Configuring barcode rules for a

robotic library ” on page 391.

4 Click Apply.

Viewing tape drive statistics

You can view statistics about tape drives.
See “Support for tape drives and robotic libraries” on page 381.
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
 Tape storage 390
Robotic libraries in Backup Exec

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 390.
See “Creating robotic library partitions” on page 397.

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 in the Backup Exec Hardware
Compatibility List.
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 11-1 Example configuration for a multi-drive robotic library

Data transfer element (storage devices ) SCSI ID Drive

element
address

Robotic arm 4 N/A

Storage device 0 5 00008000

 Tape storage 391
Robotic libraries in Backup Exec

Table 11-1 Example configuration for a multi-drive robotic library (continued)

Data transfer element (storage devices ) SCSI ID Drive

element
address

Storage device 1 6 00008001

See “Robotic libraries in Backup Exec” on page 389.

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. It is recommended 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 472.

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 392.
See the section called “Adding, editing, and deleting barcode rules by using the
Backup Exec global settings” on page 393.
 Tape storage 392
Robotic libraries in Backup Exec

See the section called “Enabling or disabling barcode rules by using robotic library
properties” on page 393.

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:

If the Central Admin Server feature is not Click Tape storage, and then click Next.
installed

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select the Backup Exec server on
which you want to configure storage,
and then click Next.
■ Click Tape storage, and then click
Next.

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:

To add a new barcode rule 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 edit an existing 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 delete a barcode rule Select a barcode rule, click Delete, and

then click Yes to confirm the deletion.

6 Click Next.
 Tape storage 393
Robotic libraries in Backup Exec

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:

To change the barcode configuration 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 complete the barcode configuration Click Finish.

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:

To enable all barcode rules for this robotic Click Enabled.

library

To disable all barcode rules for this robotic Click Disabled.

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.
 Tape storage 394
Robotic libraries in Backup Exec

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:

To add new barcode rule Click New, and then continue with the next
step.

To edit an existing barcode rule Select the barcode rule that you want to
edit, click Edit, and then continue with the
next step.

To delete 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.

 Tape storage 395
Robotic libraries in Backup Exec

4 Add or change any of the following information:

Media type Click the drop-down menu and select or

change the media type.

Vendor 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.

Barcode prefix 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 suffix 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.

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 474.
See “Robotic libraries in Backup Exec” on page 389.
 Tape storage 396
Robotic libraries in Backup Exec

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 477.

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 389.
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.
 Tape storage 397
Creating robotic library partitions

3 Edit the following options as appropriate:

Name Displays the name of the robotic library.

You can edit this field.

Description 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.

First slot number 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.

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 399.
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
 Tape storage 398
Creating robotic library partitions

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:

To view all of the robotic libraries that you Do the following in the order listed:
can configure partitions for
■ 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 configure partitions for a specific robotic Do the following in the order listed:
library
■ On the Storage tab, right-click the
robotic library for which you want to
create partitions.
■ Click Configure partitions.

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:

To change the configuration 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 configure the partitions Click Finish.

Adding or removing tape drives in a robotic library partition

You can add or remove tape drives in a robotic library partition.
 Tape storage 399
Creating robotic library partitions

See “Creating robotic library partitions” on page 397.

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:

To add a tape drive to the robotic library Do the following in the order listed:
partition
■ Click Add.
■ In the devices list that appears, select
the tape drive that you want to add, and
then click OK.

To remove a tape drive from the robotic Select the tape drive that you want to
library partition remove, and then click Remove.

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 389.
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 389.
 Tape storage 400
Creating robotic library partitions

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.
5 Edit any of the following options.

Cleaning slot 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 477.

Preserve description 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.

6 Click Apply.

Removing or reconfiguring robotic library partitions

You can remove or reconfigure robotic library partitions.
 Tape storage 401
Creating 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:

To change the configuration 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 remove the partitions Click Finish.

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:

To change the configuration 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 configure the partitions Click Finish.

See “Reassigning a slot base number for robotic libraries” on page 399.
 Tape storage 402
Managing tapes

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.
■ 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.
For information about the best practices to manage tapes in Backup Exec, refer to
Backup Exec Best Practices.
See “Default media sets” on page 402.
See “Tape media rotation strategies” on page 434.
See “Creating media sets for tapes” on page 410.

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.
 Tape storage 403
Managing tapes

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 478.

You cannot modify the properties of system media sets. System media sets are
described in the following table:

Table 11-2 Default system media sets

Name Description

Backup Exec and Windows NT Displays all media that is imported from another
Backup Media installation of Backup Exec.

See “Cataloging a storage device” on page 470.

Cleaning Media Displays all cleaning media.

See “Cleaning a robotic library drive” on page 477.

Foreign 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 242.

See “Cataloging a storage device” on page 470.

 Tape storage 404
Managing tapes

Table 11-2 Default system media sets (continued)

Name Description

Retired 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 429.

See “Retiring damaged tape media” on page 428.

Scratch Media 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 406.

Backup Exec creates the following default user media sets:

 Tape storage 405
Managing tapes

Table 11-3 Default user media sets

Name Description

Keep Data for 4 Weeks 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 Infinitely - Do Displays all tape media that you associate with this media
Not Allow Overwrite 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.

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.
 Tape storage 406
Managing tapes

Note: It is recommended 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 406.
See “Creating media sets for tapes” on page 410.
See “Creating media vault rules to move tape media to and from media vaults”
on page 426.
See “Duplicating backup sets or a job history manually” on page 216.
See “Associating tape media with a media set” on page 431.

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 11-4 Overwrite protection and append periods

Rule Description

Append period 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.
 Tape storage 407
Managing tapes

Table 11-4 Overwrite protection and append periods (continued)

Rule Description

Overwrite protection period 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 416.

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 317.
The following graphic shows the relationship between the append period and the
overwrite protection period.
 Tape storage 408
Managing tapes

Figure 11-1 Append periods and overwrite protection periods

The append period begins when the media is allocated to a

media set.
A PPE N D PERI OD

The overwrite protection period is

TIME

measured from the time of the last

OVER

write to the media.

During the append period, data

can be added to the media. Any
R I T E P R OWT E C T I O N

data already on the media is The media

protected against loss. cannot be
Overwritten
by another
The append period ends.
job during
this interval.
After the append (However,
period expires, and you could
while the overwrite erase the
protection period is media or
still active, data associate it
cannot be added to with scratch
P ERIO D

the media. Any data media.)

TIME

already on the
media is protected
against loss.

The overwrite protection period

expires.

New
data
After the overwrite protection
period expires, the media
becomes recyclable. This
means that new data can be
TIME

written to the beginning of the

media by a new backup job
(causing loss of the original
data).
Old
data

The append and overwrite protection periods that you specify apply to all the data
on the media.
 Tape storage 409
Managing tapes

Each time data is written to a media, the time remaining in the overwrite protection
period is reset, and the countdown is restarted.

Figure 11-2 How overwrite protection periods are reset

Time in Append period = 5 Time in Append period = 5 Time in Append period = 5

days days days days days days

1 Normal Bkup 1 Normal Bkup 1 Normal Bkup

2 2 Normal Bkup 1 2 Normal Bkup 1
3 3 3 Normal Bkup 1 2
4 4 4 Normal Bkup 1 2 3
Normal Bkup 1 2 3 4
5 5 5
6 6 6
7 7 7
Protection Protection Protection
8 8 period 14 8
period 14 period 14
9 9 days 9 days
days
10 10 10
11 11 11
12 12 12
13 13 13
14 14 14
15 15 15
16 The media can be 16 16
17 overwritten at this time 17 The media can be 17 Fifth Day
18 18 overwritten at this time 18
19 First Day 19 Second Day 19
The media can be
20 20 20 overwritten at this time

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.
 Tape storage 410
Managing tapes

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 402.

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:

To change the configuration 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 create the media set Click Finish.

Editing media set properties

You can edit the following properties for media sets:
 Tape storage 411
Managing tapes

■ 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 402.
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:

Name Displays the name of the media set.

Description Displays the description of the media set.

 Tape storage 412
Managing tapes

Overwrite protection period 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 406.

Append 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.
 Tape storage 413
Managing tapes

Media vault to use with this media set Displays the media vault that stores the
media that is associated with this media
set.

See “Default media vaults” on page 424.

Move media to this vault after Displays the time period after which this
media is reported as ready to be moved to
this vault.

Return media from this vault after Displays the time period after which this
media is reported as ready to be returned
from this vault.

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 406.
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:
 Tape storage 414
Managing tapes

Overwrite protection period 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.

Append 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.

6 Click Apply.
 Tape storage 415
Managing tapes

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 424.
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:

Media vault to use with this media set Displays the media vault that stores the
media that is associated with this media
set.

Move media to this vault after Displays the time period after which this
media is reported as ready to be moved to
this vault.

Return media from this vault after Displays the time period after which this
media is reported as ready to be returned
from this vault.

6 Click Apply.
 Tape storage 416
Managing tapes

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 402.

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 402.
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.
 Tape storage 417
Managing tapes

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 406.

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 402.
See “Deleting tape media” on page 429.
See “Editing global settings for storage” on page 458.

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.
 Tape storage 418
Managing tapes

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: It is recommended 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 11-5 How Backup Exec searches for overwritable media in tape drives

Overwrite protection level and Media is overwritten in tape drives in this

overwrite option: order:

Full + Overwrite scratch media first 1 Scratch media

Note: This combination provides 2 Recyclable media in the destination media set
the most protection against
3 Recyclable media in any media set
overwriting media.

Full + Overwrite recyclable media 1 Recyclable media in the destination media set
first
2 Scratch media

3 Recyclable media in any media set

Partial + Overwrite scratch media 1 Scratch media

first
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
 Tape storage 419
Managing tapes

Table 11-5 How Backup Exec searches for overwritable media in tape drives
(continued)

Overwrite protection level and Media is overwritten in tape drives in this

overwrite option: order:

Partial + Overwrite recyclable media 1 Recyclable media in the destination media set
first
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

None - No overwrite protection + 1 Scratch media

overwrite scratch media first
2 Recyclable media in the destination media set
Warning: This options is not
3 Recyclable media in any media set
recommended because it does not
protect data from being overwritten. 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 + 1 Recyclable media in the destination media set

overwrite recyclable media first
2 Scratch media
Warning: This options is not
3 Recyclable media in any media set
recommended because it does not
protect data from being overwritten. 4 Media that is imported from another installation
of Backup Exec, or from another product

5 Allocated media in any media set

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 458.
See “Default media vaults” on page 424.
 Tape storage 420
Labeling tape media

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 402.
To view the tapes that are used by a job
1 Do any of the following:

To view the job log from the Job Monitor Select the Job Monitor tab.
tab

To view the job log from the Backup and Do the following in the order listed:
Restore tab or the Storage 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.

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.
 Tape storage 421
Labeling tape media

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 470.
 Tape storage 422
Labeling tape media

See “Renaming a tape media label ” on page 423.

See “How barcode labels become media labels for tapes” on page 422.

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 429.

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 420.
See “Scanning a storage device” on page 471.
 Tape storage 423
How WORM media is used in Backup Exec

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 420.

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.
 Tape storage 424
Default media vaults

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 475.
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 556.

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 11-6 Default media vaults

Default media vault Description

Online Tape Media 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.
 Tape storage 425
Default media vaults

Table 11-6 Default media vaults (continued)

Default media vault Description

Offline Tape Media 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.

Vaulted 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.

All Media Vaults 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 426.

See “Changing the name or description of a media vault” on page 425.

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 424.
To change media vaults and media vault rules, edit the properties of the media set
that is associated with the media vault.
 Tape storage 426
Default media vaults

See “Editing media set properties” on page 410.

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 425.

Table 11-7 Properties for media vaults

Item Description

Name Displays the name of the media vault.

Description Displays a description of the media vault.

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 424.
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 427.
 Tape storage 427
Default media vaults

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 424.
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 424.
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.
 Tape storage 428
Retiring damaged tape media

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 424.
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 429.
See “Media Errors report” on page 718.
 Tape storage 429
Deleting tape media

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 428.

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.
 Tape storage 430
Erasing tape or disk cartridge media

Table 11-8 Erase operations

Erase operation Description

Erase media now 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.

Long 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.

Schedule Let you schedule either an Erase or Long

erase operation, and lets you choose
notification options.

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:

To run an erase operation immediately Click Erase media now.

To run a long erase operation immediately Click Long erase media now.

3 Click Yes when you are prompted to erase the media.

 Tape storage 431
About cataloging tape or disk cartridge media that contains encrypted backup sets

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:

To schedule an erase operation Click Schedule erase.

To schedule a long erase operation Click Schedule long erase.

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 451.
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 627.

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:
 Tape storage 432
Editing tape media properties

■ 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 410.

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 402.

Editing tape media properties

You can view tape media properties and edit some properties.
See “Managing tapes” on page 402.
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.
 Tape storage 433
Editing tape media properties

3 Change any of the following options:

Media label 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 description 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.

Preserve 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.

4 Click Apply.
 Tape storage 434
Tape media rotation strategies

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 11-9 Son media rotation strategy

Item Description

Number of media required 1 (minimum)

Overwrite protection period Last backup

The Son strategy involves performing a full backup every day.

Figure 11-3 Son backup strategy

Mon Tue Wed Thu Fri

Media 1 Media 1 Media 1 Media 1 Media 1

Week 1

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.
 Tape storage 435
Tape media rotation strategies

Father/Son media rotation strategy

The Father/Son media rotation strategy requires the following:

Table 11-10 Father/Son media rotation strategy

Item Description

Number of media required 6 (minimum)

Overwrite protection period Two weeks

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 11-4 Father/Son backup strategy

Mon Tue Wed Thu Fri

Media 1 Media 2 Media 3 Media 4 Media 5

Week 1

Media 1 Media 2 Media 3 Media 4 Media 6

Week 2

Full Backup Incremental or Differential

Backup

Grandfather media rotation strategy

The Grandfather media rotation strategy requires the following:
 Tape storage 436
Tape media rotation strategies

Table 11-11 Grandfather media rotation strategy

Item Description

Number of media required 19 (minimum)

Overwrite protection period One year

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.
 Tape storage 437
Tape media rotation strategies

Figure 11-5 Grandfather backup strategy

Mon Tue Wed Thu Fri

Mon 1 Tue 2 Wed 3 Thu 4 Fri 5

Week 1

Mon 1 Tue 2 Wed 3 Thu 4 Fri 6

Week 2

Mon 1 Tue 2 Wed 3 Thu 4 Fri 7

Week 3

Mon 1 Tue 2 Wed 3 Thu 4 Monthly

Week 4

Full Backup Incremental or

Differential
Backup

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.
 Chapter 12
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.
 Storage device pools 439
Creating storage device pools

■ 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 441.

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 feature installed, you can create managed
Backup Exec server pools.

Table 12-1 System-defined storage device pools maintained by Backup Exec

System-defined storage device pools Description

that are maintained by Backup Exec

Any disk storage Contains the fixed-disk storage.

Any tape drive 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 disk cartridge 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.

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.
 Storage device pools 440
Creating 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:

If the Central Admin Server feature is not Select Storage pools, and then click Next.
installed

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select the Backup Exec server that you
want to configure storage for, and then
click Next.
■ Select Storage pools, and then click
Next.

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:

To change the configuration 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 configure the storage device pool Click Finish.

See “Adding or removing devices in a storage device pool ” on page 442.

See “How to use Backup Exec server pools in CAS ” on page 1304.
See “Adding or removing devices in a storage device pool ” on page 442.
See “Error-handling rules for failed or canceled jobs” on page 272.
 Storage device pools 441
Specifying a default selection method for a device in a storage device pool

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:<Backup Exec install path>\Backup Exec
See “Creating storage device pools” on page 438.

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 249.
See “Alerts and notifications in Backup Exec” on page 286.
 Storage device pools 442
Adding or removing devices in a storage device pool

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 438.

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 441.

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:

To add a storage device to the pool Do the following in the order listed:
■ Click Add.
■ Select the devices that you want to add,
and then click OK.

To remove a storage device from a pool Select the device that you want to remove,
and then click Remove.

5 Click Apply.
 Chapter 13
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

 Storage operations 444
About storage operation jobs

■ 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

■ Viewing the disk storage lockdown status

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 451.
See “Sending a notification when a scheduled storage operation job completes”
on page 451.
 Storage operations 445
Storage tab overview in Backup Exec

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 450.
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 119.

Table 13-1 All Storage overview

Item Description

Name 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 469.

State 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 494.

Parent Device 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.

Backup Exec Server 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.
 Storage operations 446
Storage tab overview in Backup Exec

Table 13-1 All Storage overview (continued)

Item Description

Storage Type 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, cloud storage, and
so on.

This column only appears if you select the List view from the
Views group at the top of the window.

Active Alerts 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 286.

Storage Trending 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 315.
 Storage operations 447
Storage tab overview in Backup Exec

Table 13-1 All Storage overview (continued)

Item Description

Capacity 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 321.

See “Editing disk cartridge properties” on page 329.

See “How Backup Exec catalogs work” on page 242.

See “Inventorying a storage device” on page 472.

Total 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.

Used Space Displays the amount of space that is used as storage, after
any compression or deduplication operations have occurred.
 Storage operations 448
Using the Configure Storage wizard

Table 13-1 All Storage overview (continued)

Item Description

Backup Data Written 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.

Available Space Displays the difference between Total Capacity and Used
Space.

% of Available Space Displays the difference as a percentage between Total

Capacity and Used Space.

Active and Scheduled Jobs 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.

Compression Ratio Displays the ratio of the uncompressed size of a file over its
compressed size.

Average job rate Disiplays the average speed of the jobs that run on this
device.

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 the Backup Exec
Hardware Compatibility List.
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.
 Storage operations 449
Using the Configure Storage wizard

Table 13-2 Storage that you can configure in the Configure Storage wizard

Type of Description
storage

Disk-based Storage that remains attached to the server.

storage 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 317.
■ 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 328.
■ 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 937.

Network Network storage includes the following:

storage
■ 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 feature” on page 1339.
■ OpenStorage devices
Network-attached storage that supports Veritas's OpenStorage
technology.
See “Configuring an OpenStorage device” on page 932.
■ Cloud storage devices
Cloud storage devices are the storage devices that are configured on
the cloud hosted by the cloud storage service provider
For the list of supported cloud providers, refer to the Backup Exec
Hardware Compatibility List.
■ 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 1392.
 Storage operations 450
Viewing details for multiple storage devices

Table 13-2 Storage that you can configure in the Configure Storage wizard
(continued)

Type of Description
storage

Tape 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 381.
■ Robotic libraries
Storage that contains tape drives, slots, and an automated method for
loading tapes.
See “Robotic libraries in Backup Exec” on page 389.
■ Barcode rules
See “Configuring barcode rules for a robotic library ” on page 391.

Storage pools Storage pools include the following:

■ Storage device pools

■ Managed Backup Exec server pools

See “Creating storage device pools” on page 438.

Media sets Media sets and vaults are for tape media only, and include the following:
and vaults
■ Append period
■ Overwrite protection period
■ Vaulting rules

You can also run wizards to update media vaults.

See “Managing tapes” on page 402.

See “About storage operation jobs” on page 444.

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 445.
 Storage operations 451
Sending a notification when a scheduled storage operation job completes

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 444.
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 444.
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 451.

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 444.
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.
 Storage operations 452
Scheduling a storage operation job

4 Select any of the following options:

Recurrence Specify a recurrence schedule for the job.

Hours 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.

Days 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.
 Storage operations 453
Scheduling a storage operation job

Weeks 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.
 Storage operations 454
Scheduling a storage operation job

Months
 Storage operations 455
Scheduling a storage operation job

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.
 Storage operations 456
Scheduling a storage operation job

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.

Years 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.

at Designate the starting time for the first job

in the recurrence pattern.
 Storage operations 457
Scheduling a storage operation job

Calendar View all scheduled jobs on a calendar to

check for scheduling conflicts.

Reschedule the job if it does not start x Specify the amount of time past the job's
hours after its scheduled start 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.

Cancel the job if it is still running x Specify the amount of time after the job's
hours after it scheduled start time 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.

Include dates with the schedule of this Specify dates to include with the job
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.

Exclude dates from the schedule for Specify dates to exclude from the job
this 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.

Run now with no recurring schedule Run the job immediately without scheduling
any more instances of it for the future.

Run on Run the job at the time and date that you
specify.
 Storage operations 458
Editing global settings for storage

Create without a schedule 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.

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.

Inventory robotic libraries when Backup Enable Backup Exec to inventory all of the
Exec services start 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.

 Storage operations 459
Editing global settings for storage

Full - protect allocated and imported Select this option to prevent Backup Exec
media 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 406.
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.

Partial - protect only allocated 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.

It is recommended this option if you want

to use media from another installation of
Backup Exec or from another product

This option is enabled by default.

Prompt before overwriting imported Select this option to be prompted before

media 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.
 Storage operations 460
Editing global settings for storage

None 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.

Prompt before overwriting allocated or Select this option to be prompted before

imported media Backup Exec overwrites allocated or
imported media in tape drives. If you
selected None, it is 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.
 Storage operations 461
Editing global settings for storage

Overwrite scratch media before Select this option to let Backup Exec
overwriting recyclable media contained overwrite scratch media first in a tape drive
in the targeted media set when an overwrite job occurs.

See “How Backup Exec searches for

overwritable media in tape drives ”
on page 417.

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.

 Storage operations 462
Editing global settings for storage

Overwrite recyclable media contained Select this option to let Backup Exec
in the targeted media set before overwrite recyclable media in a tape drive
overwriting scratch media 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 417.

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.
 Storage operations 463
Editing global settings for storage

Limit Backup Exec to read-only Select this option to prevent Backup Exec
operations on a disk-based storage from reclaiming disk space from expired
device if it has been detached for 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 321.

See “Backup sets ” on page 341.

See “How to restore data from a reattached

or reinserted disk-based storage device”
on page 327.

See “How data lifecycle management

(DLM) deletes expired backup sets on
disk-based storage” on page 335.

Number of days 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.

 Storage operations 464
Editing global settings for storage

Limit Backup Exec to read-only Prevents Backup Exec from reclaiming disk
operations on a disk cartridge if it has space from expired backup sets on any
not been inserted for 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 329.

See “Backup sets ” on page 341.

See “How to restore data from a reattached

or reinserted disk-based storage device”
on page 327.

See “How data lifecycle management

(DLM) deletes expired backup sets on
disk-based storage” on page 335.

Number of days 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.

 Storage operations 465
Editing global settings for storage

Allow Backup Exec to delete all expired

backup sets
 Storage operations 466
Editing global settings for storage

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 feature
(CAS) 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 CAS
environment.
 Storage operations 467
Sharing storage devices

See “Backup sets ” on page 341.

See “How data lifecycle management

(DLM) deletes expired backup sets on
disk-based storage” on page 335.

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 CAS
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 feature 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
■ Cloud storage 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
 Storage operations 468
Deleting a storage device

server can use the storage device. However, if your environment does not allow
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, or a cloud-based 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 Right-click the device again, and then click Delete.
3 When you are prompted to delete the storage device, click Yes.
 Storage operations 469
Changing the state of a storage device to online

See “Disabling and enabling a storage device” on page 474.

See “Recreating a legacy backup-to-disk folder and its contents” on page 377.
See “Backup sets ” on page 341.

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.
The alert may include a link to the 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 760.
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 444.
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.
 Storage operations 470
Viewing jobs, job histories, backup sets, and active alerts for storage devices

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 444.
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 262.
See “How to monitor and manage jobs in Backup Exec” on page 249.
See “About the Job Monitor” on page 251.
See “Alerts and notifications in Backup Exec” on page 286.
See “Backup sets ” on page 341.

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. It is
recommended that you encrypt data instead.
See “Using encryption with Backup Exec” on page 624.

See “Inventorying and cataloging a storage device” on page 473.

See “How Backup Exec catalogs work” on page 242.
 Storage operations 471
Scanning a storage device

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 470.

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 444.
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.
 Storage operations 472
Inventorying a storage device

4 To schedule the job, in the left pane, click Schedule and select the appropriate
options.
See “Scheduling a storage operation job” on page 451.
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 470.

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.
 Storage operations 473
Inventorying and cataloging a storage device

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 451.
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 470.
See “Inventorying robotic libraries when Backup Exec services start” on page 391.

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 444.
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 470.

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 444.
 Storage operations 474
Disabling and enabling a storage device

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 470.
 Storage operations 475
Formatting a tape as a WORM tape

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 423.

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 444.
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 470.

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.
 Storage operations 476
Ejecting media from a disk cartridge or tape drive

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 444.

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 470.

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 444.
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.
 Storage operations 477
Cleaning a robotic library drive

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 451.
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 470.

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 444.
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 396.
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.
 Storage operations 478
Importing media to Backup Exec

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 451.
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 470.

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 402.

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.
 Storage operations 479
Importing media to Backup Exec

See “Scanning a storage device” on page 471.

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:

Import Updates the Backup Exec database with

information about the media.

Inventory after 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.

4 To send a notification when the job completes, in the left pane, click Notification
and select the appropriate options:

Recipient name Show the names of the individual and group

recipients.

Recipient type Indicate Recipient for an individual recipient or

Group for a group recipient.

Manage Recipients Add, edit, or delete recipients.

Properties View or change the properties of a selected

recipient.
 Storage operations 480
Importing media to Backup Exec

5 To schedule the job, in the left pane, click Schedule and select the appropriate
options.

Recurrence Specify a recurrence schedule for the job.

Hours 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.

Days 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.
 Storage operations 481
Importing media to Backup Exec

Weeks 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.
 Storage operations 482
Importing media to Backup Exec

Months
 Storage operations 483
Importing media to Backup Exec

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.
 Storage operations 484
Importing media to Backup Exec

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.

Years 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.

at Designate the starting time for the first job in the

recurrence pattern.

Calendar View all scheduled jobs on a calendar to check

for scheduling conflicts.

Reschedule the job if it does not Specify the amount of time past the job's
start x hours after its scheduled scheduled start time at which Backup Exec
start changes the job completion status to Missed. The
job is rescheduled to run based on the time
window that you configured.
 Storage operations 485
Exporting media and expired media

Cancel the job if it is still running Specify the amount of time after the job's
x hours after it scheduled start scheduled start time at which you want to cancel
time the job if it is still running. Backup Exec changes
the job completion status to Canceled, timed out.

Include dates with the schedule Specify dates to include with the job schedule.
of this job 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.

Exclude dates from the schedule Specify dates to exclude from the job schedule.
for this job 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.

Run now with no recurring Run the job immediately without scheduling any
schedule more instances of it for the future.

Run on Run the job at the time and date that you specify.

Create without a schedule 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.

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 470.

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
 Storage operations 486
Exporting media and expired media

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 478.

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.
 Storage operations 487
Exporting media and expired media

■ Right-click the robotic library, and then click Export.

2 Do one of the following:

To immediately export only the media that Click Export expired media now.
Backup Exec cannot write to and place it
The operation runs. You can view the job
in the portal
history for details about the job.

To immediately export the media to the Click Export media now.

portal
The operation runs. You can view the job
history for details about the job.

To immediately import media after the Click Import after export.

export
The operation runs. You can view the job
history for details about the job.

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 470.
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.
 Storage operations 488
Locking and unlocking the robotic library’s front portal

4 Click the drop-down menu and select one of the following storage operations
that you want to schedule:

Export 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.

Import media after export Adds the scratch media to the robotic
library to prepare for the next backup.

Export expired media 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.

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. Backup Exec Media Servers will not lock robotic libraries when running
backup jobs or when a Lock job is run.
 Storage operations 489
Locking and unlocking the robotic library’s front portal

If you want to unlock the robotic libraries, contact technical support.

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:

Recipient name Show the names of the individual and group

recipients.

Recipient type Indicate Recipient for an individual recipient or

Group for a group recipient.

Manage Recipients Add, edit, or delete recipients.

Properties View or change the properties of a selected

recipient.

5 To schedule the job, in the left pane, click Schedule and select the appropriate
options.

Recurrence Specify a recurrence schedule for the job.

 Storage operations 490
Locking and unlocking the robotic library’s front portal

Hours 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.

Days 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.

Weeks 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.
 Storage operations 491
Locking and unlocking the robotic library’s front portal

Months
 Storage operations 492
Locking and unlocking the robotic library’s front portal

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.
 Storage operations 493
Locking and unlocking the robotic library’s front portal

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.

Years 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.

at Designate the starting time for the first job in the

recurrence pattern.

Calendar View all scheduled jobs on a calendar to check

for scheduling conflicts.

Reschedule the job if it does not Specify the amount of time past the job's
start x hours after its scheduled scheduled start time at which Backup Exec
start changes the job completion status to Missed. The
job is rescheduled to run based on the time
window that you configured.
 Storage operations 494
Backup Exec server and storage device states

Cancel the job if it is still running Specify the amount of time after the job's
x hours after it scheduled start scheduled start time at which you want to cancel
time the job if it is still running. Backup Exec changes
the job completion status to Canceled, timed out.

Include dates with the schedule Specify dates to include with the job schedule.
of this job 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.

Exclude dates from the schedule Specify dates to exclude from the job schedule.
for this job 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.

Run now with no recurring Run the job immediately without scheduling any
schedule more instances of it for the future.

Run on Run the job at the time and date that you specify.

Create without a schedule 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.

6 Click OK.
See “Viewing jobs, job histories, backup sets, and active alerts for storage devices”
on page 470.

Backup Exec server and storage device states

Backup Exec servers and storage devices display a state that indicates their current
condition.
 Storage operations 495
Backup Exec server and storage device states

Table 13-3 Possible states for Backup Exec servers and storage devices

State Description

All the Backup Exec services need to be The Backup Exec services and the Backup
restarted on <Backup Exec server> Exec deduplication services must be
restarted.

See “Starting and stopping Backup Exec

services” on page 667.

An error occurred while discovering this The Backup Exec services must be restarted.
device. Cycle the services on <Backup Exec
See “Starting and stopping Backup Exec
server> to retry device discovery.
services” on page 667.

Active The storage device is in use by a job.

Configuration failed Configuration has failed for a local disk

storage device or virtual disk.

Configuring A local disk storage device or virtual disk is

in the process of configuration.

Disabled The storage device is disabled and Backup

Exec cannot use it. The device is available
for other applications.

Disabled; Active The storage device'a status was changed to

Disabled while a job was running to the
device.

Low disk space; Active The storage device is in a low disk space
condition, but is currently in use by a job.

Low disk space The storage device has low disk space.

No communication Communications have stopped between a

managed Backup Exec server and a central
administration server in a Central Admin
Server feature environment.

See “What happens when CAS

communication thresholds are reached”
on page 1298.

Not configurable The disk cannot be configured because it is

in a bad state, or it has failed.

Not configured The disk is available for configuration but has

not yet been configured.
 Storage operations 496
Backup Exec server and storage device states

Table 13-3 Possible states for Backup Exec servers and storage devices
(continued)

State Description

Offline 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.

The alert may include a link to the 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 469.

Online The storage device is online.

Paused The storage device is paused.

See “Pausing and unpausing a storage

device” on page 473.

Paused; Active The storage device is paused, but is currently

in use by a job.
 Storage operations 497
Viewing the disk storage lockdown status

Table 13-3 Possible states for Backup Exec servers and storage devices
(continued)

State Description

Stalled Communications have stalled during

communications between a managed Backup
Exec server and a central administration
server in a Central Admin Server feature
environment.

See “What happens when CAS

communication thresholds are reached”
on page 1298.

The Backup Exec deduplication services need The Backup Exec deduplication services
to be restarted on <Backup Exec server> 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 667.

The Backup Exec services on <Backup Exec The Backup Exec services must be restarted.
server> need to be restarted
See “Starting and stopping Backup Exec
services” on page 667.

This device has not been discovered A state that can occur after you add a new
correctly. Cycle the services on <Backup storage device to Backup Exec. You must
Exec server> to retry device discovery. restart the Backup Exec services so that the
device discovery process can run again.

Uninitialized The device has not been initialized.

Viewing the disk storage lockdown status

The disk storage lockdown setting protects the disk-based backup storage configured
with Backup Exec. Access to disk storage is limited only to authorized processes
like Backup Exec services. Only Backup Exec is allowed to write to the disk storage.
In addition, external processes are not allowed to modify backup data by injecting
code into Backup Exec processes. The disk storage lockdown status displays the
status of disk-based backup storage configured with Backup Exec.
This setting is enabled by default and is the recommended setting to protect your
backup data. You can disable the setting by providing the System Logon Account
credentials. To disable the lockdown, click Backup Exec Settings > Network And
 Storage operations 498
Viewing the disk storage lockdown status

Security > Disk storage lockdown settings > Disable and enter the System
Logon Account credentials.
To view the disk storage lockdown status
1 In the Backup Exec status bar, double-click Disk storage lockdown status.
The Disk storage lockdown status details dialog box is displayed. The Disk
storage lockdown status displays the status of the disk storage lockdown
setting. There can be four states of the disk lockdown.

Enabled The disk storage lockdown setting is enabled and the

disk-based backup storage is protected by Backup Exec.

Disabled The disk storage lockdown setting is disabled.

Enabled with exception The disk storage setting is enabled but there are some disk
storage for which the lockdown cannot be enabled.

Unavailable Backup Exec cannot retrieve the status of the disk storage
lockdown setting.

2 Click OK.
See “Changing network and security options for Backup Exec” on page 614.
 Chapter 14
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.
 Conversion to virtual machines 500
How conversion of physical computers to virtual machines works in Backup Exec

■ 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
or later 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:
 Conversion to virtual machines 501
How conversion of physical computers to virtual machines works in Backup Exec

Table 14-1 Conversion to virtual machine options

Name of option Description

Back up to Disk and Simultaneously These options run the conversion

Convert to Virtual Machine simultaneously with the backup job. Because
two operations are performed at the same
Back up to Deduplication Disk Storage
time, this job may take longer to run than a
and Simultaneously Convert to Virtual
regular backup job. A large backup window
Machine
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 508.
 Conversion to virtual machines 502
How conversion of physical computers to virtual machines works in Backup Exec

Table 14-1 Conversion to virtual machine options (continued)

Name of option Description

Back Up to Disk and then Convert to These options let you schedule the
Virtual Machine conversion to run after the backup job. These
options require a smaller backup window than
Back Up to Deduplication Disk Storage
the simultaneous conversion options.
and then Convert to Virtual Machine
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 515.

Convert to Virtual Machine from A conversion to a virtual machine from a point

Point-in-Time 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 530.
 Conversion to virtual machines 503
How conversion of physical computers to virtual machines works in Backup Exec

Table 14-1 Conversion to virtual machine options (continued)

Name of option Description

One-Time Convert to Virtual Machine 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 532.

Add Stage 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 523.

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.
 Conversion to virtual machines 504
How conversion of physical computers to virtual machines works in Backup Exec

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 file\folder 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.
 Conversion to virtual machines 505
How conversion of physical computers to virtual machines works in Backup Exec

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 or later 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 or later Hyper-V host
Before you create a job to convert a physical computer to a Windows Server 2012
and later 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 and later 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.
 Conversion to virtual machines 506
How conversion of physical computers to virtual machines works in Backup Exec

■ 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.
■ Conversion to any previous versions of a Windows Hyper-V host is not supported,
so those jobs fail. For example, if the physical computer runs Windows Server
2012 with an ReFS volume, conversion to a Windows Server 2012 Hyper-V
host is supported.
■ If the physical computer runs Windows Server 2012 or later 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
 Conversion to virtual machines 507
Requirements for conversion to virtual machine jobs

■ MSExchangeServiceHost
■ MSExchangeThrottling
■ MSExchangeTransport
■ MSExchangeTransportLogSearch
■ MSExchangeUM
■ MSExchangeUMCR
See “Requirements for conversion to virtual machine jobs” on page 507.

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.

■ Conversion from a duplicate backup set is not 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 or later.
■ Only basic disks are supported. Dynamic disks are not supported for Hyper-V
conversions.
 Conversion to virtual machines 508
Converting to a virtual machine simultaneously with a backup job

■ 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.

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.
See “How conversion of physical computers to virtual machines works in Backup
Exec” on page 499.

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:
 Conversion to virtual machines 509
Converting to a virtual machine simultaneously with a backup job

To change the backup selections 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 options Do the following:

■ In the Backup box, click Edit, and then

change the backup options as needed.
■ Click OK.

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:
 Conversion to virtual machines 510
Converting to a virtual machine simultaneously with a backup job

If you selected Hyper-V in step 5

 Conversion to virtual machines 511
Converting to a virtual machine simultaneously with a backup job

Do the following to configure the

conversion options:

■ Click the arrow in the Hyper-V server

name field, select the name of the
server where you want to create the
virtual machine, and then click Add.
■ In the Destination drive or path field,
enter the location on the physical
computer where the virtual disks should
be created. Enter a drive letter and
path.
■ If you want to change the default virtual
machine name, type the new name in
the Virtual machine name field.
■ If you want to enable Backup Exec to
overwrite a virtual machine if a virtual
machine with the same name already
exists, verify that the Overwrite the
virtual machine if it already exists
option is selected. If this option is not
selected and the virtual machine name
already exists, then the job fails.
■ In the Full path of Hyper-V Integration
Components ISO image field, enter
the location of your Hyper-V Integration
Components ISO image. The ISO
image is needed to make the virtual
machine bootable.
Note: This option is not available for
Hyper-V servers that run on Windows
2016 or later. Such Hyper-V servers
install integration services directly on
the virtual machine either through a
Windows update or a user-initiated
download.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
 Conversion to virtual machines 512
Converting to a virtual machine simultaneously with a backup job

configuration, and then enter the new

information.
 Conversion to virtual machines 513
Converting to a virtual machine simultaneously with a backup job

If you selected VMware ESX/vCenter

server in step 5
 Conversion to virtual machines 514
Converting to a virtual machine simultaneously with a backup job

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.
 Conversion to virtual machines 515
Converting to a virtual machine after a backup job

Note: In a CAS environment, this path

should be local to the managed Backup
Exec server to which the job is targeted.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
configuration, and then enter the new
information.

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 499.

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:
 Conversion to virtual machines 516
Converting to a virtual machine after a backup job

To change the backup selections 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 options Do the following:

■ In the Backup box, click Edit, and then

change the backup options as needed.
■ Click OK.

4 In the Conversion to Virtual box, click Edit.

5 In the left pane, select Schedule, and then select one of the following options:

To schedule the conversion to run at a Do the following:

specific time
■ 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 create the conversion job without Do the following:

scheduling it
■ 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 run the conversion immediately after Select Convert to virtual immediately

the backup job completes after source task completes.
 Conversion to virtual machines 517
Converting to a virtual machine after a backup job

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:
 Conversion to virtual machines 518
Converting to a virtual machine after a backup job

If you selected Hyper-V in step 8

 Conversion to virtual machines 519
Converting to a virtual machine after a backup job

Do the following to configure the

conversion options:

■ Click the arrow in the Hyper-V server

name field, select the name of the
server where you want to create the
virtual machine, and then click Add.
■ In the Destination drive or path field,
enter the location on the physical
computer where the virtual disks should
be created. Enter a drive letter and
path.
■ If you want to change the default virtual
machine name, type the new name in
the Virtual machine name field.
■ If you want to enable Backup Exec to
overwrite a virtual machine if a virtual
machine with the same name already
exists, verify that the Overwrite the
virtual machine if it already exists
option is selected. If this option is not
selected and the virtual machine name
already exists, then the job fails.
■ In the Full path of Hyper-V Integration
Components ISO image field, enter
the location of your Hyper-V Integration
Components ISO image. The ISO
image is needed to make the virtual
machine bootable.
Note: This option is not available for
Hyper-V servers that run on Windows
2016 or later. Such Hyper-V servers
install integration services directly on
the virtual machine either through a
Windows update or a user-initiated
download.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
 Conversion to virtual machines 520
Converting to a virtual machine after a backup job

configuration, and then enter the new

information.
 Conversion to virtual machines 521
Converting to a virtual machine after a backup job

If you selected VMware ESX/vCenter

server in step 8
 Conversion to virtual machines 522
Converting to a virtual machine after a backup job

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.
 Conversion to virtual machines 523
Adding a conversion to virtual machine stage to a backup job

Note: In a CAS environment, this path

should be local to the managed Backup
Exec server to which the job is targeted.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
configuration, and then enter the new
information.

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 499.

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.
 Conversion to virtual machines 524
Adding a conversion to virtual machine stage to a backup job

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:
 Conversion to virtual machines 525
Adding a conversion to virtual machine stage to a backup job

If you selected Hyper-V in step 7

 Conversion to virtual machines 526
Adding a conversion to virtual machine stage to a backup job

Do the following to configure the

conversion options:

■ Click the arrow in the Hyper-V server

name field, select the name of the
server where you want to create the
virtual machine, and then click Add.
■ In the Destination drive or path field,
enter the location on the physical
computer where the virtual disks should
be created. Enter a drive letter and
path.
■ If you want to change the default virtual
machine name, type the new name in
the Virtual machine name field.
■ If you want to enable Backup Exec to
overwrite a virtual machine if a virtual
machine with the same name already
exists, verify that the Overwrite the
virtual machine if it already exists
option is selected. If this option is not
selected and the virtual machine name
already exists, then the job fails.
■ In the Full path of Hyper-V Integration
Components ISO image field, enter
the location of your Hyper-V Integration
Components ISO image. The ISO
image is needed to make the virtual
machine bootable.
Note: This option is not available for
Hyper-V servers that run on Windows
2016 or later. Such Hyper-V servers
install integration services directly on
the virtual machine either through a
Windows update or a user-initiated
download.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
 Conversion to virtual machines 527
Adding a conversion to virtual machine stage to a backup job

configuration, and then enter the new

information.
 Conversion to virtual machines 528
Adding a conversion to virtual machine stage to a backup job

If you selected VMware ESX/vCenter

server in step 7
 Conversion to virtual machines 529
Adding a conversion to virtual machine stage to a backup job

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.
 Conversion to virtual machines 530
Converting to a virtual machine from a point in time

Note: In a CAS environment, this path

should be local to the managed Backup
Exec server to which the job is targeted.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
configuration, and then enter the new
information.

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 499.

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.
 Conversion to virtual machines 531
Converting to a virtual machine from a point in time

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:

To run the job immediately Click Run now.

To schedule the conversion to run at a Click Run on, and then enter the date and
specific time time to run the job.

To create the conversion job without Select Create without a schedule. When
scheduling it 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.

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.
 Conversion to virtual machines 532
Creating a one-time conversion to a virtual machine

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:

To run the job immediately Click Run now.

To schedule the conversion to run at a Click Run on, and then enter the date and
specific time time to run the job.

To create the conversion job without Select Create without a schedule. When
scheduling it 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.

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.
 Conversion to virtual machines 533
Creating a one-time conversion to a virtual machine

8 Configure the conversion options:

 Conversion to virtual machines 534
Creating a one-time conversion to a virtual machine

If you selected Hyper-V in step 7

 Conversion to virtual machines 535
Creating a one-time conversion to a virtual machine

Do the following to configure the

conversion options:

■ Click the arrow in the Hyper-V server

name field, select the name of the
server where you want to create the
virtual machine, and then click Add.
■ In the Destination drive or path field,
enter the location on the physical
computer where the virtual disks should
be created. Enter a drive letter and
path.
■ If you want to change the default virtual
machine name, type the new name in
the Virtual machine name field.
■ If you want to enable Backup Exec to
overwrite a virtual machine if a virtual
machine with the same name already
exists, verify that the Overwrite the
virtual machine if it already exists
option is selected. If this option is not
selected and the virtual machine name
already exists, then the job fails.
■ In the Full path of Hyper-V Integration
Components ISO image field, enter
the location of your Hyper-V Integration
Components ISO image. The ISO
image is needed to make the virtual
machine bootable.
Note: This option is not available for
Hyper-V servers that run on Windows
2016 or later. Such Hyper-V servers
install integration services directly on
the virtual machine either through a
Windows update or a user-initiated
download.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
 Conversion to virtual machines 536
Creating a one-time conversion to a virtual machine

configuration, and then enter the new

information.
 Conversion to virtual machines 537
Creating a one-time conversion to a virtual machine

If you selected VMware ESX/vCenter

server in step 7
 Conversion to virtual machines 538
Creating a one-time conversion to a virtual machine

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.
 Conversion to virtual machines 539
Setting default options for conversion to virtual machine jobs

Note: In a CAS environment, this path

should be local to the managed Backup
Exec server to which the job is targeted.
■ If you want to change the CPU count
or amount of physical RAM for the
destination virtual machine, on the
Server configuration tab, enter the
new amounts in the Desintation virtual
machine fields.
■ If you want to change the disk type, the
controller, or the virtual disk location for
one of the disks, on the Disk
configuration tab, click Edit disk
configuration, and then enter the new
information.

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 499.

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:
 Conversion to virtual machines 540
Setting default options for conversion to virtual machine jobs

To schedule conversion to virtual jobs to Do the following:

run at a specific time
■ 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 create conversion to virtual jobs without Do the following:

scheduling them
■ 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 run the conversion immediately after Select Convert to virtual immediately

the backup job completes after source task 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:
 Conversion to virtual machines 541
Setting default options for conversion to virtual machine jobs

If you selected Hyper-V in step 6 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.
Note: This option is not available for
Hyper-V servers that run on Windows
2016 or later. Such Hyper-V servers
install integration services directly on
the virtual machine either through a
Windows update or a user-initiated
download.
 Conversion to virtual machines 542
Setting default options for conversion to virtual machine jobs

If you selected VMware ESX/vCenter Do the following to configure the

server in step 6 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 CAS environment, this path
should be local to the managed Backup
Exec server to which the job is targeted.

8 Click OK
 Chapter 15
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 Instant GRT and full catalog options to improve backup performance
for GRT-enabled jobs

■ Configuring Advanced Open File options for backup jobs

■ Configuring checkpoint restart

■ 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

■ Exporting the Backup Exec Database encryption key

 Configuration and settings 544

■ 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

■ Configuring settings for Veritas™ Information Map

■ 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

 Configuration and settings 545
Changing default backup job settings

■ Saving an audit log to a text file

■ Copying configuration settings to another Backup Exec server

■ Viewing server properties

■ Configuring default backup settings

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
■ Duplicate to Cloud
■ Convert to Virtual
■ Forever Incremental Backup

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.
 Configuration and settings 546
Changing default backup job settings

3 In the left pane, select the setting for which you want to configure default
options.

Schedule Select this option to configure default settings for the

time and frequency with which you want to run backup
jobs.

See “Configuring schedules for backup jobs”

on page 549.

Storage Select this option to configure default settings for the

storage device that you want to use for backup jobs.

See “Configuring storage options for backup jobs”

on page 556.

Notification Select this option to configure Backup Exec to notify

specified recipients when backup jobs are completed.

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 305.

Test Run Select this option to configure a test job that

automatically tests storage capacity, credentials, and
media integrity.

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 562.

Verify Select this option to create a job that automatically

verifies whether all of the data was successfully backed
up when jobs are completed.

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 563.
 Configuration and settings 547
Changing default backup job settings

Instant GRT Select this option to configure Instant GRT or full catalog
operations for any GRT-enabled jobs. You can choose
to run a full catalog operation immediately after the
backup job finishes, schedule the full catalog operation
for another time, or run an Instant GRT operation as
part of the backup job.

See “Configuring Instant GRT and full catalog options

to improve backup performance for GRT-enabled jobs”
on page 565.

Advanced Open File 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 572.

See “Configuring checkpoint restart” on page 574.

Advanced Disk-based Select this option to configure off-host backup

Backup processing for backup jobs.

See “Setting default backup options for the Advanced

Disk-based Backup feature” on page 1326.

Pre/Post Commands 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 577.

Files and Folders 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 581.

Enterprise Vault Select this option to configure Enterprise Vault options

for backup jobs.

See “Enterprise Vault backup options” on page 1215.

Linux and Macintosh Select this option to configure options for any Linux or
Macintosh computers that are included in backup jobs.

See “Linux backup options” on page 1375.

 Configuration and settings 548
Changing default backup job settings

Microsoft Active Directory 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 1256.

Microsoft Exchange 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 1132.

Virtual Machines 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 975.

See “Setting default backup options for Hyper-V”

on page 1030.

Microsoft SharePoint 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 1153.

Microsoft SQL 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 1085.

NDMP 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 1343.

Oracle Select this option to configure options for any Oracle

data that is included in backup jobs.

See “Oracle backup options” on page 1189.

Exclusions Select this option to exclude specific files or specific

types of files from backup jobs.

See “Excluding files from backups” on page 174.

4 Select the appropriate options.

5 When you are finished configuring default options, click OK.
 Configuration and settings 549
Configuring schedules for backup jobs

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 210.
For information about configuring a schedule for a Forever Incremental backup,
refer to the following chapter.
See “Forever Incremental Backup” on page 894.
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:

To configure default schedule ■ Click the Backup Exec button, and then select
settings for all backup jobs Configuration and Settings.
■ Select Job Defaults, and then select the type of
backup for which you want to configure schedule
settings.

To configure a schedule for ■ Create a new backup definition or edit an existing

specific backup jobs backup definition.
■ In the Backup box, click Edit.

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.
 Configuration and settings 550
Configuring schedules for backup jobs

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:

To configure recurring jobs Complete the following steps:

■ Select Recurrence.
■ Proceed to step 6 to configure the recurrence
pattern.

To configure jobs to run Complete the following steps:

immediately without any
■ Select Run now with no recurring schedule.
recurrences
■ Proceed to step 9.

Note: This option is only available for full backup jobs.

To configure a job without a Complete the following steps:

schedule
■ 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.

6 To configure the recurrence pattern, complete the following options:

 Configuration and settings 551
Configuring schedules for backup jobs

Hours 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.

Days 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.

Weeks 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.
 Configuration and settings 552
Configuring schedules for backup jobs

Months
 Configuration and settings 553
Configuring schedules for backup jobs

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.
 Configuration and settings 554
Configuring schedules for backup jobs

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.

Years 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.

at Enter the starting time for the first job in the recurrence
pattern.

Starting on 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.

Calendar Click this option to view all scheduled backup jobs on

a calendar to check for scheduling conflicts.
 Configuration and settings 555
Configuring schedules for backup jobs

Run initial full backup now Select this option to run the initial full backup as soon
in addition to the selected as the job is created without affecting the schedule of
schedule future jobs.

Reschedule the job if it Specify the amount of time past the job's scheduled
does not start X hours after start time at which you want Backup Exec to change
its scheduled start time 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 277.

Cancel the job if it is Specify the amount of time after the job's scheduled
running X hours after its start time at which you want to cancel the job if it is still
scheduled start time running. Backup Exec changes the job completion status
to Canceled, timed out.

See “List of job statuses in Backup Exec” on page 277.

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 212.
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 213.
 Configuration and settings 556
Configuring storage options for backup jobs

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 545.
See “Backing up data” on page 153.

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:

To configure default storage Complete the following steps:

options for all backup jobs
■ 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 storage options Complete the following steps:

for specific backup jobs
■ Create a new backup definition or edit an existing
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Storage.

 Configuration and settings 557
Configuring storage options for backup jobs

3 Complete the following options as necessary:

Note: Some of these options display only in Central Admin Server feature
(CAS) environments.

Priority 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 258.

Backup Exec server or Select whether you want a job to run on devices on a
Backup Exec server pool 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 feature 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.

Storage Select the storage device to which you want to send

backup data.
See “Creating storage device pools” on page 438.

See “About the Remote Media Agent for Linux ”

on page 1392.

See “Features and types of disk-based storage and

network-based storage” on page 313.
 Configuration and settings 558
Configuring storage options for backup jobs

4 If you selected to configure an OpenStorage device or a deduplication disk

storage device in the Storage field, select from the following options:

Enable the remote Select this option to enable a remote computer to send
computer to directly access data directly to an OpenStorage device or a
the storage device and to deduplication disk storage device, and to perform
perform client-side client-side deduplication if the device supports it. The
deduplication, if it is Backup Exec server is bypassed, which leaves the
supported 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 feature 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 949.

Enable the remote Select this option to enable a remote computer to send
computer to access the data through the Backup Exec server to an OpenStorage
storage device through the device or a deduplication disk storage device, and to
Backup Exec server and to perform Backup Exec server-side deduplication if it it
perform Backup Exec supported. If the Backup Exec server does not support
server-side deduplication, deduplication, the data is deduplicated on an intelligent
if it is supported disk device, such as PureDisk or a device from a
third-party vendor.

This option appears if the Deduplication feature is

installed and an OpenStorage device or a deduplication
disk storage device is selected in the Storage field.

See “About the Deduplication feature” on page 921.

5 In the Keep for field, enter the amount of time for which you want to keep the
backup sets or job history.
If you have selected Glacier or Deep Archive cloud storage devices in the
Storage field, when the backup sets are deleted, the storage provider still
incurs charges based on their pricing model.
See “Notes for cloud-based storage devices” on page 365.
6 If you selected to configure a tape device in the Storage field, complete the
following options as necessary:
 Configuration and settings 559
Configuring storage options for backup jobs

Media set 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 402.

Overwrite media 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 402.

See “Media overwrite protection levels for tape media”

on page 416.

See “How Backup Exec searches for overwritable media

in tape drives ” on page 417.
 Configuration and settings 560
Configuring storage options for backup jobs

Append to media, overwrite Select this option to append the backed up data to the
if no appendable media is specified media set if an appendable media is available.
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, terminate Select this option to append the backed up data to the
job if no appendable media specified media set if an appendable media is available.
is available Otherwise, Backup Exec terminates the job.

This option is available only if you selected a tape device

in the Storage field.

Eject the media after job Select this option to eject the media from the drive or
completes 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 476.

Retension media before Select this option to run the tape in the drive from
backup 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.

Use Write once, read many Select this option to use WORM (write once, read many)
(WORM) media 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 423.
 Configuration and settings 561
Configuring storage options for backup jobs

Export media to vault after Select this option to logically move the media from the
job completes 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 424.

7 In the Compression field, select from the following options:

None 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.

Software Select this option to use STAC software data

compression, which compresses the data before it is
sent to the storage device.

Hardware (if available, Select this option to use hardware data compression if
otherwise none) the storage device supports it. If the drive does not
feature data compression, the data is backed up
uncompressed.

Hardware (if available, Select this option to use hardware data compression if
otherwise software) the storage device supports it. If the drive does not
feature hardware data compression, STAC software
compression is used.
 Configuration and settings 562
Configuring automatic test run jobs for backup jobs

8 To configure encryption, complete the following options:

Encryption type Select the type of encryption that you want to use, if
any.

See “Using encryption with Backup Exec” on page 624.

Encryption key Select the encryption key that you want to use, if you
selected to use encryption.

Manage Keys 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 627.

9 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.

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.
 Configuration and settings 563
Configuring automatic verify operations for backup jobs

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 732.
You can manually run a test run job at any time.
See “Running a test run job manually” on page 221.
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:

To enable test run jobs as a Complete the following steps:

default for all backup jobs
■ 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 a test run job for Complete the following steps:

specific backup jobs
■ Create a new backup definition or edit an existing
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Test Run.

3 Select Enable test run.
4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.

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. It is recommended that you verify all
 Configuration and settings 564
Configuring automatic verify operations for backup jobs

backed up data to ensure the integrity of the collection of data and the media on
which it resides.
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 222.
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:

To configure automatic verify Complete the following steps:

operations for all backup jobs
■ 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 Complete the following steps:

operations for specific backup
■ Create a new backup definition or edit an existing
jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Verify.

 Configuration and settings 565
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

3 Complete the following options:

At the end of the job Select this option to run a verify operation automatically
when the backup job is completed.

After job finishes, as a Select this option to create a verify operation and
separate job 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.

As a separate scheduled Select this option to create a verify operation and

job 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.

Do not verify data for this Select this option to disable the verify operation for the
job backup job.
Note: This option is selected by default for the
cloud-based storage devices.

4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.

Configuring Instant GRT and full catalog options

to improve backup performance for GRT-enabled
jobs
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 242.
The catalog operation can be time consuming. It requires access to the storage
device that is used for the backup. 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.
On the Instant GRT and Full Catalog Options dialog box, you can either choose
the Instant GRT option or one of the full catalog options.
 Configuration and settings 566
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

Note: The Instant GRT and Full Catalog Options are 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 the section called “Full catalog” on page 566.

See the section called “Instant GRT” on page 567.
See the section called “Differences between Instant GRT and full catalog”
on page 568.
See “To configure an Instant GRT or a full catalog operation” on page 569.

Full catalog
For GRT-enabled backup jobs, you can delay the catalog operation and run it as
a separate operation to have less 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.
See “Granular Recovery Technology” on page 632.
When you enable GRT for Microsoft Exchange, Microsoft SharePoint, Microsoft
Hyper-V, or VMware backups, the full catalog operation runs immediately after the
backup job by default.
For Exchange and SharePoint agent-based backups, the full 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 full catalog operation runs immediately after
all full, incremental, and differential backups by default.
You can also configure the full catalog operation to run on a schedule if you do not
want it to run immediately after the backup job.
You may want to schedule the full catalog operation to run outside of your backup
window so that it does not interfere with your system resources. If you schedule
the full 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 full catalog operation to run at midnight, you would have the following
backup sets:
■ Full (11:00 A.M.)
 Configuration and settings 567
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

■ 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.
■ Incremental 6 (5:00 A.M.) This backup is not cataloged.
In the example, the full catalog operation runs only for Incremental 5, Incremental
3, and Incremental 1. For such jobs, you can use the Search wizard to search the
data or you can quickly browse for individual items that you want to restore. You
can perform a granular recovery using Incremental 2, Incremental 4, and Incremental
6 as well; however, it takes slightly longer to browse items because they are not
fully cataloged. Backup Exec dynamically displays the granular data by mounting
the backup set.

Instant GRT
An Instant GRT operation runs as part of the backup job and collects only the
minimum required catalog information. You cannot use the Search wizard to search
the backup sets for individual items. When you browse the backup sets for individual
items, Backup Exec reads and displays the granular information in the backup sets
as you browse for items that you want to restore. Depending on the backup set you
are browsing, full, incremental, or differential, it takes a few minutes or longer to
browse individual items.
Before you run an Instant GRT operation, review the following requirements:
■ In a CAS environment, ensure that the logon accounts used for backups are
added to the list of logon accounts on the central administration server and the
managed Backup Exec servers.
■ The storage that hosts the backup sets must be online when you browse for
individual items that you want to restore because Backup Exec mounts the
backup sets dynamically. For incremental and differential backup sets, all such
related backup sets should also be accessible during restore.
 Configuration and settings 568
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

■ If a CAS environment, if a Backup Exec server tries to browse the backup sets
of another Backup Exec server and if a firewall is configured between them, you
must open ports on the servers.
It is recommended that you browse backup sets either from the managed Backup
Exec server on which the backup jobs were run or from the central administrative
server.
See “Backup Exec ports” on page 621.
See “Backup Exec listening ports” on page 623.

Differences between Instant GRT and full catalog

Table 15-1 Differences between Instant GRT and full catalog

Item Instant GRT Full catalog

Granular item search using Not available. You can search the backup
the Search wizard sets for granular data.

Backup sets browse You can dynamically browse You can search as well as
the backup sets to select the browse the backup sets to
individual items that you want select the individual items that
to restore. you want to restore.

Delay in catalog job No delay in the catalog job. It You can configure the catalog
runs as part of the backup job to run immediately after
job. the backup job or at a
scheduled time.

Catalog time No separate catalog time The catalog operation runs as

because the cataloging a separate job. It consumes
happens as part of the time because Backup Exec
backup job. Backup Exec collects detailed cataloging
collects only the minimum information for the backup
required catalog information. job.

Catalog file size Smaller file size because only Large file size because the
the minimum required data is complete backup set is
cataloged. cataloged.
 Configuration and settings 569
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

Table 15-1 Differences between Instant GRT and full catalog (continued)

Item Instant GRT Full catalog

Time to browse granular data Slightly longer than the time Less than the time taken for
for granular restore taken for browsing data when browsing data when you do
you do a full catalog because an Instant GRT because the
Backup Exec dynamically GRT information is already
browses the backup set for available in the detailed
reading the GRT data when catalog collected during the
you expand backup sets to full catalog job.
restore granular items.

The restore time is the same

as for a full-cataloged backup
set.

Device busy time The device is not busy for a The device is busy for a long
long time because the catalog time. First when the backup
is not detailed and it also runs happens, and then when the
as part of the backup job. full catalog operation runs as
a separate job.

You can configure these 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 Instant
GRT or full catalog options, however. If you want to configure these options only
for specific jobs, you can configure the settings when you create those jobs.
To configure an Instant GRT or a full catalog operation
1 Do one of the following:

To configure Instant GRT or Complete the following steps:

full catalog options for all
■ Click the Backup Exec button, and then select
backup jobs
Configuration and Settings.
■ Select Job Defaults, and then select the type of
backup for which you want to configure the Instant
GRT or full catalog settings.

To configure Instant GRT or Complete the following steps:

full catalog options for specific
■ Create a new backup definition or edit an existing
backup jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Instant GRT.

 Configuration and settings 570
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

3 Select one of the following options:

Enable Instant GRT Select this option if you want to run an Instant GRT
operation for GRT-enabled backup jobs.

This option is the default setting for all new GRT-enabled

backup jobs configured on a new Backup Exec
installation. If you upgrade from Backup Exec 15 Feature
Pack 5 and earlier to Backup Exec, the default
cataloging option might change depending on your
Backup Exec server environment and the version from
which you are upgrading. After upgrade if this option is
not set as the default, you can set this option as the
default option to take advantage of faster backups.

For existing GRT-enabled backup jobs that protect

Exchange, SharePoint, or virtual machines using the
virtual-based backup, the default option for existing jobs
does not change. The existing jobs retain the default
option that was set before the upgrade. If a new device
added after the upgrade, the default option is set to
Enable Instant GRT.

If you select this option, the catalog operation runs as

part of the backup job and collects only the minimum
required catalog information.

You cannot use the Search wizard to search the backup

sets for granular data. However, you can browse the
backup sets. If you want to restore granular data from
the backup sets, Backup Exec browses the backup sets
for granular data as you browse for items that you want
to restore. If you select this option, the time to browse
granular data at the time of restore is slightly longer.
 Configuration and settings 571
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs

Run a full catalog operation Select this option to run the full catalog operation
as a separate job immediately after a backup job finishes. The catalog
immediately after the operation runs as a separate job.
backup job finishes
For Exchange and SharePoint agent-based backups,
the full 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 full catalog

operation runs immediately after all full, incremental,
and differential backups.
Note: Before the full catalog operation completes,
instead of using the Search wizard, you must browse
the backup sets to select the individual items that you
want to restore. The Search wizard is available after the
full catalog job is complete.

Schedule a full catalog Select this option to run the full catalog operation as a
operation as a separate job separate, scheduled job. Then select the start time and
after the backup finishes the days of the week on which you want the full catalog
operation to run.

If you schedule the full 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: Before the full catalog operation completes,
instead of using the Search wizard, you must browse
the backup sets to select the individual items that you
want to restore. The Search wizard is available after the
full catalog job is complete.

4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.
See “How cataloging works with Hyper-V virtual machine backups” on page 1037.
See “How cataloging works with VMware virtual machine backups” on page 983.
 Configuration and settings 572
Configuring Advanced Open File options for backup jobs

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:

To configure default Complete the following steps:

Advanced Open File options
■ Click the Backup Exec button, and then select
for all backup jobs
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 Advanced Open Complete the following steps:

File options for specific
■ Create a new backup definition or edit an existing
backup jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Advanced Open File.

3 Complete the following options:

Use snapshot technology Select this option to enable the use of snapshot
technology for backup jobs.
 Configuration and settings 573
Configuring Advanced Open File options for backup jobs

Snapshot provider 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.
■ 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.

Process logical volumes for Select this option to enable the backup of multiple
backup one at a time 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.
 Configuration and settings 574
Configuring checkpoint restart

Enable checkpoint restart 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 574.

4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.

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.
 Configuration and settings 575
Configuring checkpoint restart

Note: If you use the Central Admin Server feature (CAS), 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 572.
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.
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 193.

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.
 Configuration and settings 576
Configuring checkpoint restart

■ 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.
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:

Maximum retries Enter the maximum number of times that you want
Backup Exec to retry a job that fails.

Retry interval Enter the interval of time in minutes that you want
Backup Exec to wait before it attempts to restart a job.

6 In the Final job disposition group box, select one of the following options:

Place job on hold until error Select this option to have Backup Exec place the job
condition has been on hold if the job cannot be completed successfully after
manually cleared the maximum number of retries. The job remains on
hold until the error condition has been manually cleared.

Reschedule job for its next Select this option to have Backup Exec reschedule the
scheduled service job for its next scheduled occurrence if the job cannot
be completed successfully after the maximum number
of retries.
 Configuration and settings 577
Configuring pre/post commands for backup jobs

7 (Optional) In the Notes field, type any additional notes about the error-handling
rule.
8 Click OK.

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
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.
 Configuration and settings 578
Configuring pre/post commands for backup jobs

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:

To configure default pre/post Complete the following steps:

commands for all backup jobs
■ 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 pre/post Complete the following steps:

commands for specific
■ Create a new backup definition or edit an existing
backup jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Pre/Post Commands.

 Configuration and settings 579
Configuring pre/post commands for backup jobs

3 Complete the following options:

Type a command to run Runs a command on the specified server before the
before the backup runs backup job runs. Use local paths, and make sure that
the paths exist on each server and are correct.

Commands that require user interaction, such as

prompts, are not supported.

Run job only if Runs the backup job only if the pre-command is
pre-command is successful successful. If the pre-command fails, the job does not
run, and is marked as failed.

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.

Type a command to run Runs a command on the specified server after the
after the backup runs backup job runs. Use local paths, and make sure that
the paths exist on each server and are correct.

Commands that require user interaction, such as

prompts, are not supported.

Run post-command after Runs the post-command after the verification completes,
job verification completes if you configured a verify operation for the job.
See “Configuring automatic verify operations for backup
jobs” on page 563.

Run post-command only if Runs the post-command only if the pre-command is

pre-command is successful 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.
 Configuration and settings 580
Configuring pre/post commands for backup jobs

Run post-command even if Runs the post-command regardless of whether the job
job fails 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.

Let Backup Exec check the Lets Backup Exec check the return codes of the pre-
exit codes of the and post-commands to determine if they completed
commands to determine if successfully.
the commands completed
Backup Exec interprets an exit code of zero from either
successfully
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.

On this Backup Exec server Runs the pre- and post-commands on this Backup Exec
server only.

On each server backed up 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.

Cancel command if not Designates the number of minutes Backup Exec should
completed within x minutes wait before it cancels a pre- or post-command that did
not complete. The default timeout is 30 minutes.

4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.
 Configuration and settings 581
Configuring file and folder options for backup jobs

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:

To configure default file and Complete the following steps:

folder options for all backup
■ Click the Backup Exec button, and then select
jobs
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 file and folder Complete the following steps:

settings for specific backup
■ Create a new backup definition or edit an existing
jobs
backup definition.
■ In the Backup box, click Edit.

2 In the left pane, click Files and Folders.

3 Complete the following options:
 Configuration and settings 582
Configuring file and folder options for backup jobs

Backup method for files

 Configuration and settings 583
Configuring file and folder options for backup jobs

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
 Configuration and settings 584
Configuring file and folder options for backup jobs

before the next backup job, the bit is turned on again.

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 feature (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 193.
 Configuration and settings 585
Configuring file and folder options for backup jobs

Enable single instance Select this option if you want Backup Exec to check the
backup for NTFS volumes 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.

This option is not applicable if the data targeted for

backup is on a Windows Server 2016 and later because
Microsoft no longer supports the 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.
 Configuration and settings 586
Configuring file and folder options for backup jobs

Back up files and Select this option to back up the information for the
directories by following junction points and the files and directories to which
junction points and mount they are linked. If this check box is not selected, then
points 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.

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 Select this option to back up the information for any
directories by following symbolic links and the files and directories to which they
symbolic links 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.
 Configuration and settings 587
Configuring file and folder options for backup jobs

Back up data in Remote Select this option to back up any data that has been
Storage 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.
 Configuration and settings 588
Configuring file and folder options for backup jobs

Back up open files 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.

Backup method 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 183.

 Configuration and settings 589
Setting default schedule options for rule-based jobs and run now jobs

Delete selected files and Select this option if you want Backup Exec to delete the
folders after successful data you selected to back up after the backup job
backup 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 197.

Preserve tree on back up Select this option to retain the file system's directory
and delete 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.

4 Click OK.
See “Changing default backup job settings” on page 545.
See “Backing up data” on page 153.

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.
 Configuration and settings 590
Setting default schedule options for rule-based jobs and run now jobs

3 In the Recurrence Pattern group box, select the default frequency for backup
jobs:

To run jobs every X hours or Click Hours, and then enter the frequency in the Every
minutes 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 days 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 weeks 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.

 Configuration and settings 591
Setting default schedule options for rule-based jobs and run now jobs

To run jobs every X months 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.
 Configuration and settings 592
Excluding dates from the backup schedule for all backups

To run jobs every X years 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.

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 210.
See “List of job statuses in Backup Exec” on page 277.

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.
 Configuration and settings 593
Excluding dates from the backup schedule for all backups

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 595.
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:

To manually enter the date 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 select the date from the Click the date that you want to exclude.
calendar
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 import a list of dates Complete the following steps:

■ Click Browse.
■ Select the text file that contains the exclude dates.
■ Click Open.
■ Click Import.
 Configuration and settings 594
Removing dates from the list of excluded dates

To delete a date from the list Complete the following steps:

of dates to exclude
■ Select the date or dates that you want to remove
from the list.
■ Click Delete.

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 592.
 Configuration and settings 595
Exporting a list of dates that are excluded from all backups to another server

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 592.
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.
 Configuration and settings 596
Changing the default preferences

3 Configure any of the following preferences:

Show splash screen at Clear this option to show the Backup Exec
startup Administration Console instead of the splash screen
when you start Backup Exec.

Display progress indicators Select this option to display the percentage complete
for backup jobs. This number while a backup job runs. These indicators
requires additional time to appear in the Job Activity dialog box, and they let you
pre-scan resource. 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.

Enable auto Enables you to use this option to auto synchronize the
synchronization of the licenses with Veritas Entitlement Management System.
licenses with Veritas Backup Exec periodically checks for a license update
Entitlement Management in Veritas Entitlement Management System. If an update
System. is available, Backup Exec downloads the updated
license file. This option is enabled by default.

Allow Backup Exec to Select this option to participate in the Backup Exec
report anonymous usage product improvement program.
information (No personally
General Backup Exec usage and statistical information
identifiable information will
is periodically collected and sent anonymously to help
be sent).
improve the Backup Exec customer experience.
Note: Although usage and statistical information is
collected, Backup Exec never collects specific user
information.

Use alternating row colors 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.

Re-enable Select this option to enable any messages that you have
disabled.

4 Click OK.
 Configuration and settings 597
Configuring the default setting for backing up multiple servers or applications

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
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 153.

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.
 Configuration and settings 598
Configuring database maintenance and security

■ 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.
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.
 Configuration and settings 599
Configuring database maintenance and security

4 Configure any of the following options:

Perform database Select the time that you want to perform database
maintenance daily at maintenance.

All the maintenance occurs once a day at the time you

specify.

Delete aged data Select this option to delete expired job history, job logs,
alert history, and reports from the Backup Exec
Database after the specified number of days have
passed.

Keep job history for data on Select this option to keep all job history data for any
media that have current media to which an overwrite protection period is
overwrite protection currently assigned.
periods
After a media’s overwrite protection period expires, the
media’s job history data can be deleted.

Keep job history for Select this option to indicate the number of days to keep
specified number of days job history data in the database before it is deleted.

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.

Job logs Indicate the number of days to keep job logs in the
database before they are deleted.

Job logs include detailed information about the job.

Alert history Indicate the number of days to keep alert history data
in the database before it is deleted.

Alert history data includes property and response

information for the alert.

Reports Indicate the number of days to keep report data in the

database before it is deleted.

Report data includes property information about any

report jobs that were generated. The report itself is not
deleted.

Audit logs Indicate the number of days to keep audit log data in
the database before it is deleted.

The audit log includes information about any operations

that are performed in Backup Exec.

See “Configuring audit logs” on page 670.

 Configuration and settings 600
Configuring database maintenance and security

Perform database Select this option to check the logical consistency and
consistency check physical consistency of the data in the database.

The option is not checked by default. It is recommended

that you run a consistency check periodically at a time
when there is minimal activity from Backup Exec.

Save contents of database Select this option to save the data that is contained in
to the Backup Exec data the database to the Backup Exec data directory so that
directory 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.

Optimize database size Select this option to organize fragmented pages and
decrease the size of the physical database to 10 percent
above what is actually used.
 Configuration and settings 601
Exporting the Backup Exec Database encryption key

5 To export the database encryption key, complete the following fields:

Note: 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 601.

Path Type the path of a secure location to which you want to

export the Backup Exec Database encryption key.

Remember the export path. Select this option to let Backup Exec remember the path
By clicking this check box, to which you exported the database encryption key.
you consent to let Backup
If you select this option, Backup Exec can attempt to
Exec retain and display the
automatically recover the database encryption key in
export path during import
the event that the key fails. If you do not select this
operations.
option, you must manually import the database
encryption key if it ever fails.

Export Click this option to export the Backup Exec Database

encryption key to the location that you specified in the
Path field.

6 Click OK.
See “Configuring encryption for the connection to the Backup Exec Database”
on page 604.

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.
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
 Configuration and settings 602
Exporting the Backup Exec Database encryption key

■ 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
It is recommended 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 feature (CAS) deployments.
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.
4 If you want Backup Exec to remember the path to which you exported the
database encryption key, select Remember the export path. By clicking this
check box, you consent to let Backup Exec retain and display the export
path during import operations.
If you select this option, Backup Exec can attempt to automatically recover the
database encryption key in the event that the key fails. If you do not select this
option, you must manually import the database encryption key if it ever fails.
5 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 through 5.
6 Click OK.
 Configuration and settings 603
Refreshing Backup Exec Database encryption keys

See “Configuring database maintenance and security” on page 597.

See “Refreshing Backup Exec Database encryption keys” on page 603.
See “Configuring encryption for the connection to the Backup Exec Database”
on page 604.

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. It is recommended that you make a complete backup of the registry
and computer before making any registry changes.

3 Locate and right-click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Backup Exec For
Windows\Backup Exec\Server\DatabaseEncryptionAction
 Configuration and settings 604
Configuring encryption for the connection to the Backup Exec Database

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. It is
recommended 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 601.

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 CAS 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, It is recommended that you create and use your
own certificates for additional security.
 Configuration and settings 605
Configuring encryption for the connection to the Backup Exec Database

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.
For information about the best practices to manage the database encryption, refer
to the Backup Exec Best Practices.

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. It is recommended 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.
 Configuration and settings 606
Configuring encryption for the connection to the Backup Exec Database

■ 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.
 Configuration and settings 607
Configuring encryption for the connection to the Backup Exec Database

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:
 Configuration and settings 608
Scheduling Backup Exec to check logon accounts

For clustered Backup Exec You must configure a secure SQL connection on each node
environments 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 Central Admin Server You must configure a secure SQL connection on each
feature (CAS) environments computer in the CAS environment, including the central
administration server and any managed Backup Exec servers.

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 2:00
pm.

Note: The default time is set to 2.00 pm only for fresh installations of Backup Exec
15 Feature Pack 3 and later. For earlier installations and servers upgraded to Backup
Exec 15 Feature Pack 3 and later, the default time will still be set to 1.00 am.
 Configuration and settings 609
Configuring Backup Exec to discover data to back up

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.
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:

Check that the backup Select this option to test whether Backup Exec can
sources in jobs can be access the backup sources in your backup jobs with the
accessed with the logon logon accounts that you selected.
accounts you selected

Perform check every X days Enter the interval for Backup Exec to test logon
at X 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.

Check logon accounts only Select this option to limit the logon account test to the
at the server level 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.

4 Click OK.
See “Backup Exec logon accounts” on page 655.

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.
 Configuration and settings 610
Configuring Backup Exec to discover data to back up

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
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 611.
■ 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.
 Configuration and settings 611
Adding discovered servers to the list of servers in Backup Exec

3 Configure any of the following options:

Discover servers that have Select this option to allow Backup Exec to discover any
data that has not been data that needs to be backed up.
backed up
When this option is selected, Backup Exec automatically
checks your network for any data that has not been
backed up.

Frequency 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.

Interval 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.

Cancel data discovery if not Lets you select the number of hours after which the data
completed within discovery process is canceled if it is not finished.

Canceling the data discovery process can help prevent

it from affecting your system resources.

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.
 Configuration and settings 612
Backup networks

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.

Upgrade the Backup Exec Agent for Upgrades the Agent for Windows on the
Windows to the current version server that you are adding to the list of
automatically servers, if necessary.

Restart the remote computer Restarts the remote computer after the
automatically after installing the Backup Agent for Windows is installed.
Exec Agent for Windows when a restart
is required

10 Click Install.
See “Configuring Backup Exec to discover data to back up” on page 609.

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.
 Configuration and settings 613
Backup networks

Figure 15-1 Example of backup network

backup network
network ID: 128.10.0.0
subnet mask: 255.255.0.0

IP address
IP address: IP address: 128.10.0.3
128.10.0.1 128.10.0.2
IP address: router A
IP address: IP address:
10.67.0.3
10.67.0.1 10.67.0.2

Database router B
Backup Exec server server Exchange server

corporate network
network ID: 128.20.0.0
subnet mask: 255.255.0.0

database user email user database and email user

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
 Configuration and settings 614
Changing network and security options for Backup Exec

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 614.
See “Configuring network options for backup jobs” on page 198.
See “Using Backup Exec with firewalls” on page 620.

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 198.
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:
 Configuration and settings 615
Changing network and security options for Backup Exec

Network interface 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.

Protocol Select the default protocol you want to use for backup
jobs.
The options are as follows:

■ Use any available protocol

■ IPv4
■ IPv6

Subnet Select the 32-bit number that determines the subnet to

which the network interface card belongs.

Allow use of any available Select this option to let Backup Exec use any available
network interface, subnet, network if the remote system that you selected for
or protocol for Backup Exec backup or restore is not part of the specified backup
agents not bound to the network.
above network interface,
If you do not select this option and the remote system
subnet, or protocol
is not part of the specified backup network, the job fails.
Backup Exec cannot access the data from the remote
system.

Interface Details 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.

Enable selection of user Select this option to include user-defined shares in jobs.
shares
If you do not select this option, you cannot select
user-defined shares when you create jobs.

Enable TCP dynamic port Lets Backup Exec agents use a range of ports for
range 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. It is recommended that you use 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 620.

 Configuration and settings 616
Changing network and security options for Backup Exec

Use a custom port to Lets you specify the port that Backup Exec uses for
receive operation requests communication between the Backup Exec server and
from the Oracle server 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 1185.

Use FIPS 140-2 compliant Lets you enable software encryption that complies with
software encryption 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.

Manage Keys Lets you create a new encryption key or manage

existing encryption keys.

Allow only Kerberos Allows Backup Exec to restrict clients, such as Remote
authentication from the Administration Console to use Kerberos only
Remote Administration authentication.
Console
If you select this check box to use only Kerberos
authentication, the Backup Exec Management Service
must be restarted. Any connections from Remote
Administration Console that fall back to use NTLM
authentication are disabled.

By default, this option is not selected.

This option is disabled when a Backup Exec server is

in a workgroup. Only the owner of a System Logon
Account, who is logged on to the Backup Exec console
has the privileges to change the option.
Note: The System Logon Account must be a member
of Domain Admins group.
 Configuration and settings 617
Changing network and security options for Backup Exec

Secure the Backup Exec Lets you secure the Backup Exec console by providing
console the following features when you select the Secure the
Backup Exec Console check box:

■ Authentication
After you select the Secure the Backup Exec
Console check box, the authentication setting is
enabled and the next time that you launch Backup
Exec, you need to enter Backup Exec login
credentials to connect to the console.
If you do not enter the credentials you cannot
connect to the Backup Exec console.
■ Lock Console option
After you select the Secure the Backup Exec
Console check box, this feature is enabled. You can
lock the Backup Exec session that you are working
on and secure the Backup Exec console from
unauthorized access. Unless you unlock the Backup
Exec console, you cannot perform any tasks in the
Backup Exec user interface.

Note: By default, this check box is not selected.

This option is not applicable for Remote Administration

Console (RAC) as you must always provide credentials
to connect to the Backup Exec console.

Only the owner of a System Logon Account, who is

logged on to the Backup Exec console has the privileges
to change the user access settings. If you want to know
the owner of the System Logon Account, click the
Backup Exec button, and then select Configuration
and Settings > Select Logon Accounts > Manage
Logon Accounts. On the Logon Account
Management dialog box, the Owner column displays
the owner of the System Logon Account.

In case of rolling upgrade, if you have an earlier version

of MMS and an updated version of CAS, and you
connect to MMS from CAS, this check box is available
and you can select it. However, this setting is not
enabled for MMS.

See “Locking and unlocking the Backup Exec Console”

on page 118.
 Configuration and settings 618
Changing network and security options for Backup Exec

Disk storage lockdown The Ransomware Resilience feature lets you enable or
setting disable the lockdown setting on the disk storage.

The disk storage lockdown setting protects the

disk-based backup storage configured with Backup
Exec. Access to disk storage is limited only to authorized
processes like Backup Exec services. Only Backup Exec
is allowed to write to the disk storage (Backup Exec
data folders where the backup jobs are targeted). No
other process can write to the disk storage. In addition,
external processes are not allowed to modify backup
data by injecting code into Backup Exec processes.

While the lockdown is enabled, backups and restores

continue to work without a change.

If the disk storage is created on a network share hosted

on a remote server, Backup Exec can only monitor the
write operations originating from the media server. If
the network share is accessed from any other server,
which does not have Backup Exec installed, write
access is allowed.

This setting is enabled by default and is the

recommended setting to protect your backup data. You
can disable the setting by providing the System Logon
Account credentials.

See “Disabling disk storage lockdown” on page 619.

When the lockdown is in effect, the status displays

Enabled.

The setting is disabled and the lockdown status displays

Disabled. It is strongly recommended that you enable
this setting to protect your disk-based storage. Any
changes to the disk-based storage can only be done by
Backup Exec.

If you disable the lockdown setting, the Send periodic

alerts if the disk storage lockdown setting is
disabled check box is selected so that you can receive
periodic alerts. An alert is generated at 11 am every day
until the lockdown setting is enabled again. By default,
this check box is selected. You can clear the check box
to stop the periodic alerts.

To enable the lockdown setting again, click Enable.

See “Viewing the disk storage lockdown status”

on page 497.
 Configuration and settings 619
Changing network and security options for Backup Exec

4 Click OK.
If you selected the Allow only Kerberos authentication from the Remote
Administration Console check box, a confirmation message is displayed.
5 If you want to restart the Management Service, click Yes.
See “Backup networks” on page 612.

Disabling disk storage lockdown

The disk storage lockdown setting is enabled by default and is the recommended
setting to protect your backup data. You can disable the setting by providing the
System Logon Account credentials.
To disable the disk storage lockdown
1 Click Disable.
The Disable disk storage lockdown dialog box is displayed. The disk storage
lockdown setting protects the disk-based storage against unauthorised access.
You must enter the Service Logon Account credentials to disable the setting.
2 Do the following:

User name Displays the user name of the System Logon

Account.

You cannot edit the user name.

Password Specify the password of the System Logon Account.

Reason to disable lockdown Specify the reason to disable the lockdown.

3 Click OK.
If the setting is successfully disabled, a confirmation message is displayed. If
the setting is not disabled, a message is displayed.
4 Click OK.
After the setting is disabled, the lockdown status displays Disabled on the
Network and Security pane. It is strongly recommended that you enable this
setting to protect your disk-based storage. Any changes to the disk-based
storage can only be done by Backup Exec.
See “Changing network and security options for Backup Exec” on page 614.
 Configuration and settings 620
Using Backup Exec with firewalls

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.

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.
It is recommended 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%\System32\drivers\etc\services 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.
 Configuration and settings 621
Using Backup Exec with firewalls

When you set up TCP dynamic port ranges, It is recommended 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.
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 621.
See “Backup Exec listening ports” on page 623.
See “About enabling a SQL instance behind a firewall” on page 624.

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 620.
The following table provides more information about which ports Backup Exec and
its agents and options use:

Table 15-2 Backup Exec ports

Service or Process Port Port Type

Backup Exec Agent Browser 6101 TCP

(process=benetns.exe)
 Configuration and settings 622
Using Backup Exec with firewalls

Table 15-2 Backup Exec ports (continued)

Service or Process Port Port Type

Backup Exec Agent for Windows 10000 TCP

(process=beremote.exe)

Backup Exec server 3527, 6106 TCP

(process=beserver.exe)

MSSQL$BKUPEXEC A port number between TCP

(process=sqlservr.exe) 49152 and 65535
UDP
(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.

Agent for Oracle on Windows or Linux Random port unless

Servers configured otherwise

Agent for Linux Default NDMP port, TCP

typically

10000

Backup Exec deduplication engine 10082 TCP

(process=spoold.exe)

Backup Exec deduplication manager 10102 TCP

(process=spad.exe)

Backup Exec Management Service 50104 TCP

(process=
BackupExecManagementService.exe)

Kerberos 88 UDP

NETBIOS 135 TCP, UDP

NETBIOS Name Service 137 UDP

NETBIOS Datagram Service 138 UDP

NETBIOS Session Service 139 TCP

NETBIOS 445 TCP

 Configuration and settings 623
Using Backup Exec with firewalls

Table 15-2 Backup Exec ports (continued)

Service or Process Port Port Type

DCOM/RPC 3106 TCP

Agent for Windows 6103 TCP

Push Install - Check for conflicts in 103x TCP

message queue for CAS, which is part
of beserver.exe

Push Install 441 TCP

SMTP email notification 25 outbound from TCP

Backup Exec server

SNMP 162 outbound from TCP

Backup Exec server

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 620.
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 15-3 Backup Exec listening ports

Service Port Port Type

Backup Exec Agent Browser 6101 TCP

(benetns.exe)

Backup Exec Agent for Windows 10000 TCP

(beremote.exe)

Backup Exec server (beserver.exe) 3527, 6106 TCP

Backup Exec Management Service 50104 TCP

(process=
BackupExecManagementService.exe)
 Configuration and settings 624
Using encryption with Backup Exec

Table 15-3 Backup Exec listening ports (continued)

Service Port Port Type

MSSQL$BKUPEXEC (sqlsevr.exe) 1125 TCP

1434 UDP

Agent for Linux (RALUS) 10000 TCP

DBA-initiated backups for Oracle 5633 TCP

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 1275.
See “Using Backup Exec with firewalls” on page 620.

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.
 Configuration and settings 625
Using encryption with Backup Exec

When you run a duplicate backup job, any backup sets that are already encrypted,
will remain encrypted, regardless of the encryption option that you select. However,
you can encrypt any unencrypted backup sets.
For information about the best practices of Backup Exec software encryption, refer
to Backup Exec Best Practices.
This topic includes the following information:
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.
It is recommended 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.
 Configuration and settings 626
Using encryption with Backup Exec

Backup Exec manages the encryption keys that are used to access the encrypted
data.
Backup Exec only supports approved devices for T10 encryption.

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 627.

Restricted keys and common keys

Backup Exec has the following types of encryption keys:

Table 15-4 Types of encryption keys

Key type Description

Common Anyone can use the key to encrypt data during a backup job
and to restore encrypted data.
 Configuration and settings 627
Encryption key management

Table 15-4 Types of encryption keys (continued)

Key type Description

Restricted 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.

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. It is recommended 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 627.

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 624.
 Configuration and settings 628
Creating encryption keys

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, it is recommended that you do 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.

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 628.
See “Replacing an encryption key” on page 629.
See “Deleting encryption keys” on page 631.

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.
3 Click Manage Keys.
 Configuration and settings 629
Replacing an encryption key

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.
It is recommended 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 627.
See “Using encryption with Backup Exec” on page 624.

Replacing an encryption key

You can replace one encryption key with another for all backup jobs and duplicate
backup set jobs.
 Configuration and settings 630
Replacing an encryption key

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:

To use an existing Select the key from the list.

key
 Configuration and settings 631
Deleting encryption keys

To create a new Complete the following steps:

key
■ 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. It is recommended 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.

7 Click OK.
See “Encryption key management” on page 627.
See “Using encryption with Backup Exec” on page 624.

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:
 Configuration and settings 632
Granular Recovery Technology

■ 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 627.

See “Using encryption with Backup Exec” on page 624.

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
 Configuration and settings 633
Granular Recovery Technology

■ 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, 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,
by default the catalog operation is delayed and runs as a separate operation to
have less 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 full catalog operation runs immediately after the
backup job by default.
For Exchange and SharePoint agent-based backups, the full 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 full catalog operation runs immediately after
all full, incremental, and differential backups by default.
You can configure the full catalog operation to run on a schedule if you do not want
it to run immediately after the backup job. You can also run an Instant GRT operation
that runs as part of the backup job.
See “Configuring Instant GRT and full catalog options to improve backup
performance for GRT-enabled jobs” on page 565.
For information about the best practices to use Backup Exec and Granular Recovery
Technology (GRT), refer to Backup Exec Best Practices.
The following table lists the individual items you can restore for each agent.
 Configuration and settings 634
Granular Recovery Technology

Table 15-5 Individual items that can be recovered for each agent

Agent Individual items

Agent for Microsoft Active You can restore the following individual items:
Directory
■ Active Directory objects and attributes
■ Active Directory Application Mode (ADAM) and Active
Directory Lightweight Directory Services (AD LDS) objects
and attributes

Agent for Microsoft Exchange You can restore the following individual items:
Server
■ Mailboxes
■ Mail messages and their attachments
■ Public folders
■ Calendar items
■ Contacts
■ Notes
■ Tasks

Agent for Microsoft The following are examples of the individual items that can
SharePoint 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 VMware and You can restore drives, folders, and files from virtual
Hyper-V 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 979.

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.
 Configuration and settings 635
Granular Recovery Technology

Note: It is recommended 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.

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
It is recommended 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.

Note: Backup Exec does not store the granular backup sets on disk in encrypted
form when you enable encryption for the GRT-enabled backup jobs that are sent
to disk, deduplication, and disk cartridge devices. Only the backup sets for the
backup sources that do not support GRT are stored in encrypted form. All the backup
sets for the backup jobs that are sent to cloud, OpenStorage, and tape devices are
stored in encrypted form.

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, to avoid disk space problems, it should meet these requirements:
■ It should not be a system volume
■ It should have at least 1 GB of available space
 Configuration and settings 636
Granular Recovery Technology

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:

Table 15-6 Staging processes

Location of data to be Staging process

restored

Tape 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.

Cloud Backup Exec uses a staging location to restore GRT-enabled

data from the Cloud Storage Device.

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 Cloud Storage 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.

Disk storage device that is on Backup Exec must copy a small amount of metadata that is
a volume with file size associated with the backup set to the staging area to
limitations (such as FAT or complete the restore.
FAT32)
Backup Exec deletes the data from the staging area when
the restore job is complete.

The staging location's default path is C:\temp. You can change the default backup
and restore staging locations in the Backup Exec settings.
 Configuration and settings 637
Granular Recovery Technology

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 15-7 Granular Recovery Technology requirements

Agent Restrictions

Agent for Microsoft Active You must use a Backup Exec server that is running Windows
Directory Server 2012 R2 to back up an Active Directory server that is
running Windows Server 2012 R2.

In a CAS 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.
 Configuration and settings 638
Granular Recovery Technology

Table 15-7 Granular Recovery Technology requirements (continued)

Agent Restrictions

Agent for Microsoft Exchange Backup Exec must have access to a uniquely named mailbox
Server within the Exchange organization for backup and restore of
the Information Store.

See “Requirements for accessing Exchange mailboxes ”

on page 1118.

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 You must have a current version of the Agent for Windows
SharePoint installed on all of the servers that participate in the SharePoint
farm.
 Configuration and settings 639
Setting default Granular Recovery Technology (GRT) options

Table 15-7 Granular Recovery Technology requirements (continued)

Agent Restrictions

Agent for VMware and You can recover only individual items to virtual machines that
Hyper-V 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 243.

See “Setting default Granular Recovery Technology (GRT) options” on page 639.

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 632.
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:
 Configuration and settings 640
DBA-initiated job templates

If Granular Recovery Lets you designate a location where Backup Exec can
Technology (GRT) is stage temporary data during GRT-enabled backup jobs.
enabled for backups, enter
Ensure that the location is an NTFS volume and that it
the path to an NTFS volume
is not a system volume. If the default path of C:\TEMP
of the local Backup Exec
does not meet these requirements, type a different path
server where Backup Exec
on the Backup Exec server where Backup Exec can
can stage temporary data
stage temporary data.

Backup Exec deletes the data when the backup job is

completed.

At least 1 GB of disk space is required.

Enter the path to an NTFS Lets you designate a location where Backup Exec can
volume of the local Backup stage temporary data during GRT restore jobs.
Exec server where Backup This option is applicable only when you restore individual
Exec can store temporary items under the following conditions:
data (Microsoft Hyper-V,
Microsoft Exchange, ■ The backup of Microsoft Hyper-V, Microsoft
Microsoft SharePoint, Exchange, Microsoft SharePoint, Microsoft Active
Microsoft Active Directory, Directory, or VMware Virtual Infrastructure was
and VMware) 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.

It is recommended that you avoid using system volumes

for temporary staging locations.

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.
 Configuration and settings 641
Creating DBA-initiated job templates

See “Configuring the Oracle Agent on Windows computers and Linux servers”
on page 1167.
See “About performing a DBA-initiated backup job for Oracle” on page 1188.
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 641.
See “Editing DBA-inititated job templates” on page 642.
See “Deleting DBA-initiated job templates” on page 642.

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 640.
See “Storage options for DBA-initiated jobs” on page 643.
See “General options for DBA-initiated jobs” on page 647.
See “Network options for DBA-initiated jobs” on page 647.
See “Migrator for Enterprise Vault options” on page 1243.
See “Notification options for jobs” on page 305.
See “Duplicate job settings for DBA-initiated jobs” on page 648.
 Configuration and settings 642
Editing DBA-inititated job templates

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 640.
See “Storage options for DBA-initiated jobs” on page 643.
See “General options for DBA-initiated jobs” on page 647.
See “Network options for DBA-initiated jobs” on page 647.
See “Migrator for Enterprise Vault options” on page 1243.
See “Notification options for jobs” on page 305.
See “Duplicate job settings for DBA-initiated jobs” on page 648.

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 640.
 Configuration and settings 643
Deleting DBA-initiated job templates

Storage options for DBA-initiated jobs

You can configure storage settings for DBA-initiated jobs.
See “DBA-initiated job templates” on page 640.

Table 15-8 Storage options for DBA-initiated jobs

Item Description

Storage Specifies the storage device to which you want to send

backup data for the DBA-initiated jobs.

See “Creating storage device pools” on page 438.

See “About the Remote Media Agent for Linux ” on page 1392.

See “Features and types of disk-based storage and

network-based storage” on page 313.

Enable the remote Enables a remote computer to send data directly to an

computer to directly access OpenStorage device or a deduplication disk storage device,
the storage device and to and to perform client-side deduplication if the device supports
perform client-side it. The Backup Exec server is bypassed, which leaves the
deduplication, if it is Backup Exec server free to perform other operations. If
supported client-side deduplication cannot be performed, then either
Backup Exec server deduplication or Appliance deduplication
is performed.

This option appears if the Deduplication feature 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 949.

Enable the remote Enables a remote computer to send data through the Backup
computer to access the Exec server to an OpenStorage device or a deduplication
storage device through the disk storage device, and to perform Backup Exec server-side
Backup Exec server and to deduplication if it it supported. If the Backup Exec server does
perform Backup Exec not support deduplication, the data is deduplicated on an
server-side deduplication, intelligent disk device, such as PureDisk or a device from a
if it is supported third-party vendor.

This option appears if the Deduplication feature is installed

and an OpenStorage device or a deduplication disk storage
device is selected in the Storage field.

See “About the Deduplication feature” on page 921.

Keep for Designates the amount of time for which you want to keep
the backup sets or job history from the DBA-initiated jobs.
 Configuration and settings 644
Deleting DBA-initiated job templates

Table 15-8 Storage options for DBA-initiated jobs (continued)

Item Description

Media set 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 402.

Overwrite media 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 402.

See “Media overwrite protection levels for tape media”

on page 416.

See “How Backup Exec searches for overwritable media in

tape drives ” on page 417.
 Configuration and settings 645
Deleting DBA-initiated job templates

Table 15-8 Storage options for DBA-initiated jobs (continued)

Item Description

Append to media, overwrite Appends this backup job to the specified media set if an
if no appendable media is appendable media is available. Otherwise, Backup Exec
available 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, terminate Appends this backup job to the specified media set if an
job if no appendable media appendable media is available. Otherwise, Backup Exec
is available terminates the job.

This option is available only if you selected a tape device in

the Storage field.

Eject media after job Ejects the media from the drive or slot when the operation
completes 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 476.

Retension media before Runs the tape in the drive from beginning to end at a fast
backup 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.

Use Write once, read many Specifies the use of WORM (write once, read many) media
(WORM) 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 423.

 Configuration and settings 646
Deleting DBA-initiated job templates

Table 15-8 Storage options for DBA-initiated jobs (continued)

Item Description

Compression 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.

Encryption type Specifies the type of encryption that you want to use, if any.

See “Using encryption with Backup Exec” on page 624.

Encryption key Specifies the encryption key that you want to use, if you
selected to use encryption.

See “Using encryption with Backup Exec” on page 624.

Manage Keys 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 627.

 Configuration and settings 647
Deleting DBA-initiated job templates

General options for DBA-initiated jobs

You can configure general options for DBA-initiated jobs.
See “DBA-initiated job templates” on page 640.

Table 15-9 General options for DBA-initiated jobs

Item Description

Job name Specifies the name for this backup template. You can accept
the default name that appears or enter a name. The name
must be unique.

Backup set description Describes the information in the backup set for future
reference.

Verify after backup Performs a verify operation automatically to make sure that
completes the media can be read after the backup has been completed.
Verifying all backups is recommended.

Network options for DBA-initiated jobs

You can configure network options for DBA-initiated jobs.
See “DBA-initiated job templates” on page 640.

Note: Some of these options may not display in a CAS environment.

Table 15-10 Network options for DBA-initiated jobs

Item Description

Network interface 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.

Protocol Specifies the protocol you want to use for this backup job.
The options are as follows:

■ Use any available protocol

■ Use IPv4
■ Use IPv6

Subnet Displays the 32-bit number that determines the subnet to

which the network interface card belongs.
 Configuration and settings 648
Deleting DBA-initiated job templates

Table 15-10 Network options for DBA-initiated jobs (continued)

Item Description

Allow use of any available Lets Backup Exec use any available network if the remote
network interface, subnet, system that you selected for backup or restore is not part of
or protocol for Backup the specified backup network.
Exec agents not bound to
If you do not select this option and the remote system is not
the above network
part of the specified backup network, the job fails. Backup
interface, subnet, or
Exec cannot access the data from the remote system.
protocol

Interface Details 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.

Allow managed Backup Lets a job use any network interface to access Backup Exec
Exec server to use any agents if the selected network interface is unavailable.
network interface to access Enabling this option lets the managed Backup Exec server
Backup Exec agents 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

feature (CAS) is installed.

See “About the Central Admin Server feature” on page 1263.

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 640.

Table 15-11 Duplicate job settings for DBA-initiated jobs

Item Description

Enable settings to duplicate Enables the settings for a duplicate backup set template.
backup sets for this job

Storage Specifies the storage device to which you want to send

backup data for the duplicate DBA-initiated job.

Keep for Designates the amount of time for which you want to keep
the backup sets or job history from the duplicate DBA-initiated
job.
 Configuration and settings 649
Deleting DBA-initiated job templates

Table 15-11 Duplicate job settings for DBA-initiated jobs (continued)

Item Description

Media set 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 402.

Overwrite media 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 402.

See “Media overwrite protection levels for tape media”

on page 416.

See “How Backup Exec searches for overwritable media in

tape drives ” on page 417.

Append to media, overwrite Appends this backup job to the specified media set if an
if no appendable media is appendable media is available. Otherwise, Backup Exec
available 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, terminate Appends this backup job to the specified media set if an
job if no appendable media appendable media is available. Otherwise, Backup Exec
is available terminates the job.
 Configuration and settings 650
Deleting DBA-initiated job templates

Table 15-11 Duplicate job settings for DBA-initiated jobs (continued)

Item Description

Eject media after job Ejects the media from the drive or slot when the operation
completes completes. You can also schedule a job to eject media.

See “Ejecting media from a disk cartridge or tape drive”

on page 476.

Retension media before Runs the tape in the drive from beginning to end at a fast
backup 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.

Use Write once, read many Specifies the use of WORM (write once, read many) media
(WORM) 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 423.

Enable DirectCopy to tape 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 224.
 Configuration and settings 651
Deleting DBA-initiated job templates

Table 15-11 Duplicate job settings for DBA-initiated jobs (continued)

Item Description

Compression 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.

Encryption type Specifies the encryption key that you want to use, if any.

See “Using encryption with Backup Exec” on page 624.

Encryption key Specifies the encryption key that you want to use, if you
selected to use encryption.

See “Using encryption with Backup Exec” on page 624.

Manage Keys 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 627.

 Configuration and settings 652
Configuring settings for Veritas™ Information Map

Table 15-11 Duplicate job settings for DBA-initiated jobs (continued)

Item Description

Preferred source device Specifies the preferred source device that you want to use
as the storage for the duplicate job.

Verify after backup Performs a verify operation automatically to make sure that
completes the data can be read after the backup has been completed.
Verifying all backups is recommended.

Configuring settings for Veritas™ Information

Map
You can configure the settings to register Backup Exec with Veritas™ Information
Map.
To configure settings for Veritas™ Information Map
1 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, select Veritas Information Map.
3 Configure the following settings:

Send Select this check box to send metadata about items in the backup sets
metadata to Veritas Information Map from Backup Exec to Veritas Information
about items Map.
in the
If you clear this check box, Backup Exec immediately stops sending
backup sets
metadata about items in the backup sets to Veritas Information Map. If
to Veritas
you want to start sending metadata to Information Map, select the check
Information
box again.
Map

Server Name Enter the server name where the Information Map Agent is installed.
 Configuration and settings 653
Configuring settings for Veritas™ Information Map

Port Enter the port number for connecting to the Information Map Agent.

Specify the port that is used by the Information Map Connector service
(ConnectorService.exe). By default, the 8286 port number is used.

If you have changed the port number during installation of the

Information Map Agent, use the changed port number.

To know the port number that is used do the following in the order listed.

■ Go to the path where the Information Map Agent is installed. By

default, this path is:
C:<Backup Exec install path>\InformationMapAgent
\connectorFramework\connectorService
■ Open the webService file in notepad, and find app.hostPort= .
Use the port number that is listed in this field.

Logon Select the logon account of the server where the Information Map Agent
Account is installed.

If the logon account for the server is not in the list, click Add/Edit to
add it to the list.
Note: The logon account must be part of the local administrator's group
on the server where the agent is installed.

Agent Status Displays the registration status of Backup Exec with the Information
Map Agent.

4 Click Register.

Note: Information Map setup details are saved only after the connection is
registered successfully.

5 The Establish Trust dialog box is displayed.

You must verify the security certificate to establish trust with the Information
Map server.
6 Click View Certificate and compare the public key with in the certificate with
the public key available on the Information Map Agent server.
To determine the public key of the certificate on the server where the Information
Map Agent is installed, do the following in the order listed:
■ Open the command prompt on the server where the Information Map Agent
is installed.
 Configuration and settings 654
Configuring settings for Veritas™ Information Map

■ Switch the directory path to C:<Backup Exec install

path>\InformationMapAgent\bin

Note: This is the default path where the Information Map Agent is installed.

■ Run the connector_config.exe generate_webserver_crt command.

A .cert file is generated. Open that file and retrieve the public key. Match
this key with the certificate key that is displayed when you click View
Certificate.

7 If the certificate is valid, click Yes.

Backup Exec registers with the Information Map Agent and after the registration
is successful, a confirmation message is displayed.
8 Select the number of days within which the backup sets were created for their
information to be used. Backup Exec sends most recent metadata of files and
folders of the protected servers to the Information Map Agent, using the
information available in the backup sets.
By default, 45 is selected.

Note: Metadata is sent to Information Map for a specific resource at least once,
and subsequently Backup Exec finds no backups of that resource that is created
within the number of days configured with this setting. Backup Exec considers
the resource as not part of the live actively protected resources any longer,
and the metadata is deleted from Information Map.

9 Select the check box to send metadata about items in the backup sets that are
encrypted with a common encryption key to Information Map.

Note: The metadata about items in the backup sets that are encrypted with a
restricted key is not sent to Information Map.

10 (Optional) To update the Information Map Agent details, edit the required
settings and then click Update.

Metadata about the protected data of a virtual agent

To send metadata about protected data of a virtual agent, ensure that the backup
jobs are configured with the appropriate option in the Instant GRT tab. Go to
Configuration and Settings > Job Defaults > Backup to Disk > Instant GRT.
In this tab, select any of the following options:
 Configuration and settings 655
Backup Exec logon accounts

■ Run a full catalog operation as a separate job immediately after the backup
job finishes
■ Schedule a full catalog operation as a separate job after the backup finishes
See “Integration with Veritas™ Information Map” on page 878.

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
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.
 Configuration and settings 656
Backup Exec logon accounts

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: DOMAIN\Administrator
Description: BACKUPSERVER\Administrator Default Account
Owner: BACKUPSERVER\Administrator
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 664.
■ 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 1066.
See “Requirements for accessing Exchange mailboxes ” on page 1118.
■ 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 664.
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
 Configuration and settings 657
Backup Exec logon accounts

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.
Some features available in the Backup Exec global settings let you set up a Logon
Account. For example, Simplified Disaster Recovery or Veritas Information Map
where a Logon Account must be specified. To access global settings, click the
Backup Exec button > Configuration and Settings > Backup Exec Settings.
By default, the Backup Exec System Logon Account is assigned for a feature. Since
these settings are global to Backup Exec, the assigned Logon Account is accessible
to all logged in users of Backup Exec. As a security best practice, review the Logon
Accounts in the global settings that are assigned to the features. It is recommended
that you create and assign Logon Accounts with only minimal privileges required
for that feature and select Common as the type of account that can be shared
across all users of Backup Exec.
See “Creating a Backup Exec logon account” on page 658.
See “Editing a Backup Exec logon account” on page 659.
See “Changing the password for a Backup Exec logon account” on page 661.
See “Replacing a Backup Exec logon account” on page 662.
 Configuration and settings 658
Backup Exec logon accounts

See “Deleting a Backup Exec logon account” on page 662.

See “Copying logon account information to another Backup Exec server” on page 665.

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
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.
 Configuration and settings 659
Backup Exec logon accounts

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.
4 In the User name field, type the fully qualified user name for the Backup Exec
logon account.
For example, type "DOMAIN\Administrator".
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 655.

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)
 Configuration and settings 660
Backup Exec logon accounts

■ Account name
■ Password
■ User name
■ Notes
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.
 Configuration and settings 661
Backup Exec logon accounts

4 Edit any of the following properties:

User name Type the fully qualified user name for the Backup Exec
logon account. For example, DOMAIN\Administrator.

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.

Change Password Click this option to change the password for the account.
The password you enter is encrypted for security.

Account name 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.

Notes Type any optional notes indicating how the Backup Exec
logon account is used.

This is a restricted logon Select this option to make this Backup Exec logon
account 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 my default 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.

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 655.

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.
 Configuration and settings 662
Backup Exec 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 655.

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.
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 655.

Deleting a Backup Exec logon account

If you no longer need a Backup Exec logon account, you can delete it.
 Configuration and settings 663
Backup Exec logon accounts

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:

If the logon account is not Click Yes to confirm the deletion.

referenced by any backup
jobs

If the logon account is Complete the following steps to replace the logon
referenced by backup jobs 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.

5 Click OK.
See “Backup Exec logon accounts” on page 655.
See “Replacing a Backup Exec logon account” on page 662.
 Configuration and settings 664
Backup Exec logon accounts

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 655.

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.
 Configuration and settings 665
Backup Exec logon accounts

4 Complete the following options:

User name Type the fully qualified user name for the Backup Exec
logon account. For example, DOMAIN\Administrator.

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.

Change Password Click this option to change the password for the account.
The password you enter is encrypted for security.

Account name 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.

Notes Type any optional notes indicating how the Backup Exec
logon account is used.

This is a restricted logon Select this option to make this Backup Exec logon
account 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 my default 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.

5 Click OK to create the system logon account.

See “Backup Exec logon accounts” on page 655.

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.
 Configuration and settings 666
Backup Exec logon accounts

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 655.

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.
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 655.
 Configuration and settings 667
Starting and stopping Backup Exec services

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:

To start all services for the Click Start all services.

selected server

To stop all services for the Click Stop all services.

selected server

To restart all services for the Click Restart all services.

selected server

4 Cick OK.
See “Changing the credentials for a service account” on page 667.
See “Changing startup options for Backup Exec services” on page 669.

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.

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.
 Configuration and settings 668
Changing the credentials for a service account

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 145.
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.
 Configuration and settings 669
Changing startup options for Backup Exec services

5 Complete the following fields:

Old user name Type the current user name for the service account that
you want to change.

Old password Type the current password for the service account that
you want to change.

New user name Type the new user name for the service account that
you want to change.

New password Type the new password for the service account that you
want to change.

Confirm password Type the new password again to confirm it.

Grant required rights to the Select this option to grant the service account the proper
service account system service rights.

6 Click OK.
7 Click Close.
See “Starting and stopping Backup Exec services” on page 667.
See “Changing startup options for Backup Exec services” on page 669.

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.
 Configuration and settings 670
Configuring audit logs

3 Click Edit credentials.

4 Check the Change startup options check box.
5 Select from the following options:

Automatic Select this option to automatically start the service

account at system startup.

Manual 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.

Disabled Select this option to disable the service account at

system startup.

6 Click OK.
7 Click Close.
See “Starting and stopping Backup Exec services” on page 667.
See “Changing the credentials for a service account” on page 667.

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
■ Audit logs
■ Backup set retention
■ Devices and media
■ Encryption keys
■ Error-handling rules
■ Install
■ Jobs
■ Logon accounts
 Configuration and settings 671
Viewing the audit log

■ Server configuration
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 671.
See “Removing entries from the audit log” on page 672.
See “Saving an audit log to a text file” on page 672.

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 670.
 Configuration and settings 672
Removing entries from the audit log

Removing entries from the audit log

You can remove the entries for all categories or for a selected category.
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 670.

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 670.

Copying configuration settings to another Backup

Exec server
If you have the Central Admin Server feature (CAS), 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 agents and features to the local Backup Exec server”
on page 58.
 Configuration and settings 673
Viewing server properties

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:

Default schedule Select this option to copy the default schedule settings
from this Backup Exec server to another Backup Exec
server.

Error-handling rules Select this option to copy error-handling rules from this
Backup Exec server to another Backup Exec server.

Alert configuration Select this option to copy the alert configuration from
this Backup Exec server to another Backup Exec server.

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 feature” on page 1263.

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
 Configuration and settings 674
Configuring default backup settings

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 feature (CAS), 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 1316.
To view server properties
◆ Complete either of the following as necessary:

To view the local Backup ■ Click the Backup Exec button, select Configuration
Exec server's properties and Settings, and then click Local server
properties.
■ When you are finished viewing the local server
properties, click OK.

To view any other server's ■ On the Backup and Restore tab, double-click the
properties server whose properties you want to view.
■ In the left pane, click Properties.

Configuring default backup settings

You can choose the processing method to use for Hyper-V backups. You set this
option for the Backup Exec server, so the method that you choose is applied to all
backups of Hyper-V virtual machines that the Backup Exec server protects.
Three processing options are available:
■ The Resilient Change Tracking (RCT) method. This method tracks the changes
for virtual machines that should be backed up. The RCT method provides better
resiliency than the Standard and Faster processing methods. Backups are faster
for larger virtual machines compared to other 2 methods. RCT does not make
use of VSS infrastructure on the Hyper-V host.
This method is available only for Hyper-V servers that run Windows 2016 and
later.
 Configuration and settings 675
Configuring default backup settings

■ The standard processing method. This method reads the whole virtual disk and
identifies the changes that should be backed up. The changed blocks that are
identified are then backed up.
■ The faster processing method. This method is faster than the standard processing
method because it writes all changes to a new differencing disk and then backs
up only the differencing disk. This method saves time because the entire disk
does not have to be read.

Table 15-12 Difference between the Resilient Change Tracking, standard

processing, and the faster processing methods

Processing Supported Backup type Disk storage Impacts on

method Hyper-V space system
servers performance

Resilient Change Windows 2016 ■ Differential No extra space Does not impact
Tracking (RCT) and later. ■ incremental is required. performance
method

Standard Windows 2008 ■ Differential No extra space Does not impact

processing and later. ■ Differential is required. performance
method with
incremental
 Configuration and settings 676
Configuring default backup settings

Table 15-12 Difference between the Resilient Change Tracking, standard

processing, and the faster processing methods (continued)

Processing Supported Backup type Disk storage Impacts on

method Hyper-V space system
servers performance

Faster Windows 2012 ■ Incremental Requires extra May slow down

processing and later. ■ Full space on the system
method ■ Differential Hyper-V host performance
backups run even after the because a
as backup job is checkpoint is
incremental complete. The always present
backups and extra space for each virtual
the job required machine backed
completes depends on how up using this
with a status long the method.
of "Success checkpoint is not
with merged back into
exceptions". the parent disk
and the number
of writes that
have happened
before the
merge. The
space consumed
for each virtual
machine might
not be significant
but if there are
many virtual
machines in your
environment, the
checkpoints
consumes a
significant
amount of space.

However, you
can use this
method if you
take frequent
backups and
disk space is not
a constraint.
 Configuration and settings 677
Configuring default backup settings

How upgrades affect Hyper-V backup settings

The following notes provide information for upgrades:
■ When you upgrade from Backup Exec 15 Feature Pack 3 and later, the existing
Hyper-V backup setting does not change. Existing and new backup jobs use
the setting that was configured in Feature Pack 3, unless you change it.
■ When you upgrade from Backup Exec 15 Feature Pack 2 or earlier, the default
Hyper-V backup setting for existing jobs is Use the standard processing
method. Existing and new backup jobs use this setting unless you change it.
In this scenario, the Resilient Change Tracking (RCT) method is disabled.
■ On the Backup Exec server, it is always recommended that you select the
Resilient Change Tracking (RCT) method. If RCT is selected then it is used
wherever applicable. If RCT is not supported by a virtual machine, then one of
the two methods, standard processing or faster processing is used.
To configure Hyper-V incremental or differential backup settings
1 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, select Virtual Machines.
 Configuration and settings 678
Configuring default backup settings

3 Select the processing method that you want to use for all Hyper-V incremental
or differential backup jobs.

Use Resilient Change Tracking Select this option if you want to run both
wherever applicable incremental backups and differential backups. If
RCT is selected then it is used wherever applicable
and is the recommended method. If a virtual
machine does not support RCT, the standard or
faster processing method is used, based on your
selection.
Note: This option is available only for Hyper-V
servers that run Windows Server 2016 and later.

If you do not select the RCT method and if a

Windows Server 2016 or later host is found,
Backup Exec sends periodic alerts for you to
enable the RCT method. If you do not want Backup
Exec to display the alert messages, you can
disable the alerts by editing the following registry
key:

Registry Location:
HKEY_LOCAL_MACHINE\Software\Veritas\Backup
Exec For Windows\Backup Exec\Server

ValueName = SupressRCTAlert

When you set the value as 1, the alerts are

disabled.

Use the faster processing Select this method if you want incremental backups
method jobs to be processed as quickly as possible, and
do not want to perform any differential backups.
This option does not support differential backups.
If you select this option, all Hyper-V differential
backups are processed as incremental backups.
Note: This option is available only for Hyper-V
servers that run Windows 2012 and later. For all
supported previous versions of Windows, the
standard processing method must be used.

Use the standard processing Select this option if you want to run both
method incremental backups and differential backups.

Note: When you change to a different backup processing method, the next job
runs as a full backup instead of an incremental or a differential backup.
 Configuration and settings 679
Configuring default backup settings

Note: In a CAS environment, if the processing method is not the same on the
central administration server and the managed Backup Exec server, the method
that is set for the managed Backup Exec server is used when a job is delegated
from the central administration server.

4 Click OK.

Changing virtual machine validation settings for VMware

and Hyper-V
In the Virtual Machine Validation Settings, you can change the timeout settings
of a virtual machine for VMware and Hyper-V. After you create the validation job
for a virtual machine, before the job runs, you can change the maximum time that
it takes for a virtual machine to boot. This is a global setting that is applicable to all
validation jobs. If the virtual machine does not boot within the selected time, the
validation job fails.
To change virtual machine validation settings for VMware and Hyper-V
1 Click the Backup Exec button, select Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, select Virtual Machines.
3 In the Select the maximum boot time for a virtual machine option, select
the time in minutes.
By default, 5 minutes is selected. You can select from 1 to 60 minutes.
 Chapter 16
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
 Reports 681
Reports in Backup Exec

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.

For information about the best practices to use Backup Exec reports, refer to the
Backup Exec Best Practices.

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 feature, 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 682
Running a report now

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.
See “Running a report now” on page 682.
See “List of Backup Exec standard reports” on page 698.

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 682.
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.
 Reports 683
Scheduling a 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.
■ Validation Status
■ 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.
 Reports 684
Creating a custom report

6 In the left pane, click Schedule, and then select one of the following scheduling
options:

Recurrence Lets you schedule the job to run multiple

times. You can set the recurrence pattern
so that the job runs

Run now with no recurring schedule Lets you run the job immediately.

Run on Lets you set the date and time to run the
report.

Create without a schedule 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.

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 695.

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:
 Reports 685
Creating a custom report

Table 16-1 Filter expression for finding alerts for errors

Filter type Data

Field name Alert Type

Operator = (Equal)

Value Errors

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 16-2 Filter expression for finding alerts on a specific day

Filter type Data

Field name Date Entered

Operator =(Equal)

Value 06/03/2014 | <time>

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
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 696.
 Reports 686
Creating a custom report

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.
■ 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:
 Reports 687
Creating a custom report

To combine two Click AND.

filter expressions For example, to find all backup jobs that failed, add the following
so that both expressions:
expressions must
be true for the ■ Status = Failed
result to be true ■ 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 Click OR.

filter expressions For example, to find jobs that either failed or were canceled, add
so that one of the the following expressions:
expressions must
be true for the ■ Status = Failed
result to be true ■ 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 Click ( ) +

filter expressions For example, to find backup jobs and restore jobs that failed, add
into a single
the following expressions:
expression
■ 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)

 Reports 688
Creating a custom report

To separate two Click ( ) -

filter expressions
For example, if you used ( ) + to combine Type = Backup with
that were
Type = Restore, it is displayed on the Filters dialog box as follows:
combined into a
single expression (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.

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.
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.
 Reports 689
Creating a custom report

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:

To add new fields to the report ■ Select a category.

■ Under Available fields, select the fields
you want to add, and then click the right
arrow (>>) button.

To remove fields from the report Under Fields selected for the report, click
the field you want to remove, and then click
the left arrow (<<) button.

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.
 Reports 690
Creating a custom report

4 Create a filter by defining one or more filter expressions.

To add a new filter expression Select a field name and operator, and then
enter a value. Click Add.

To edit an existing 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 delete a filter expression Under Filter criteria, select the filter

expression that you want to delete, and
then click Remove.

5 To combine sets of filter expressions, do any of the following:

To combine two Click AND.

filter expressions For example, to find all backup jobs that failed, add the following
so that both expressions:
expressions must
be true for the ■ Status = Failed
result to be true ■ 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 Click OR.

filter expressions For example, to find jobs that either failed or were canceled, add
so that one of the the following expressions:
expressions must
be true for the ■ Status = Failed
result to be true ■ 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

 Reports 691
Creating a custom report

To combine two Click ( ) +

filter expressions For example, to find backup jobs and restore jobs that failed, add
into a single the following expressions:
expression
■ 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 separate two Click ( ) -

filter expressions
For example, if you used ( ) + to combine Type = Backup with
that were
Type = Restore, it is displayed on the Filters dialog box as follows:
combined into a
single expression (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.

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.
 Reports 692
Creating a custom report

3 Do any of the following:

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 field you want to
change, click the down arrow, and then
select the new field to use as a group.

To remove 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 change the order in which data is Click Ascending or Descending.

grouped

To change the field that is used to sort the ■ In the left pane, click Sorting.
data ■ 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 disable sorting ■ 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 change the order in which data is sorted Click Ascending or Descending.

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.
 Reports 693
Saving a report

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.

Note: You cannot preview custom reports from the Backup Exec Remote
Administration Console.

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.

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)
 Reports 694
Printing a report from the Backup Exec Report Viewer

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.

To save a report that is currently displayed On the report, in the Report Viewer, click
on the screen Save As.

To save a report that is in the See ■ On the Reports tab, under Report
Completed report group Groups, click See Completed.
■ Click Save As.
■ Double-click a completed report that
you want to save to a new location.

2 Enter the file name and location where you want to save the report.
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.
 Reports 695
Viewing completed reports

To print a report from the Backup Exec Report Viewer

1 Run a report.
See “Running a report now” on page 682.
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.

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. It is recommended 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.

To edit a scheduled standard report On the Reports tab, under Report

Groups, click See Upcoming.

To edit a custom report On the Reports tab, under Report

Groups, click Custom.

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.
 Reports 696
Deleting a report

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.

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 Click Yes to confirm that you want to delete the report.

Setting defaults for standard and custom reports

You can set Backup Exec to display all reports in either HTML or Adobe Portable
Document Format (PDF). The default setting is HTML. The format that you select
does not affect the format of the reports that are sent to users with the notification
feature.
For custom reports, you can do the following:
■ Include a logo in the header.
■ Choose a color for the banner in the header.
When you choose a color for the banner, you can type the numbers that
correspond to the colors (RGB values), or you can select the color from a chart.
■ Include text in the footer.
■ Include the time in the footer.
 Reports 697
Viewing report properties

To set defaults for standard and custom reports

1 Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2 In the left pane, click Reports.
3 Complete the appropriate options.

To select a default report format for Under Report format, select either HTML
standard and custom reports or PDF.

To limit the number of rows that can be Under Report content, in Maximum
included in standard and custom reports number of rows to include in a report,
type the appropriate number.

To enable standard and custom reports to Under Report content, click Show all
show all data that is generated, even if rows.
some of the data is duplicated

To enable standard and custom reports to Under Report content, click Show
show only unique data distinct rows.

To add a logo to the header section of Under Header, check Use custom image
custom reports file, and then enter the path to the image
that you want to use in the Image file path
field.

To customize the colors in the header Under Banner color, either enter the
section of custom reports numbers that correspond to the colors you
want to use, or click Colors to select a
color from a chart.

To include default text or the time in the Under Footer, in the Text field, type the
footer of custom reports default text that you want to appear on
every custom report. If you want the time
of the report to be included in the footer,
verify that Include time is checked.

4 Click OK.

Viewing report properties

Report properties provide detailed information about each report, such as the file
name, file size, and report creation date. The properties can be viewed, but not
edited.
 Reports 698
List of Backup Exec standard reports

To view report properties

1 On the Reports tab, under Report Groups, select a report group.
2 Right-click a report for which you want to view properties, and then click
Properties.
3 Click OK after you have finished viewing the properties.

List of Backup Exec standard reports

This section provides detailed information about each standard report that is
available in Backup Exec. The data that appears on each report varies depending
on the criteria you selected to include in the report.
The following standard reports are included in Backup Exec:

Table 16-3 Backup Exec standard reports

Report Name Description

Alert History Lists all alerts in the alert history chronologically,

displaying the most recent alerts first

See “Alert History report” on page 702.

Alert History by Backup Exec Lists all alerts in the alert history, grouped and filtered
server by Backup Exec server, displaying the most recent
alerts first.

See “Alert History By Backup Exec Server report”

on page 703.

Audit Log Lists the contents of the audit logs for selected servers
for the specified time period.

See “Audit Log report” on page 704.

Backup Job Success Rate Lists the success rate for backup jobs run to back up
selected servers.

See “Backup Job Success Rate report” on page 704.

Backup Recommendations Lists any recommendations that can help you to better
manage your backups.

See “Backup Recommendations report” on page 705.

 Reports 699
List of Backup Exec standard reports

Table 16-3 Backup Exec standard reports (continued)

Report Name Description

Backup Resource Success Rate Lists the success rate for backup jobs for specified
past number of days for resources on selected servers.

See “Backup Resource Success Rate report”

on page 705.

Backup Sets by Media Set Lists all backup sets by media set.

See “Backup Sets by Media Set report” on page 706.

Backup Size by Resource Lists the backup size for each resource job for up to
seven previous runs and then computes the trailing
average for up to seven previous runs for each job
run.

See “Backup Size By Resource report” on page 706.

Cloud Storage Summary Displays the summary of the size of cloud storage that
the backed up data uses on the Backup Exec server.

See “Cloud Storage Summary report” on page 707.

Daily Device Utilization Lists the percentage of the storage devices’ capacity
that the Backup Exec server uses.

See “Daily Device Utilization report” on page 708.

Deduplication device summary Displays a summary of the deduplication operations

for local deduplication disk storage and shared
deduplication disk storage.

See “Deduplication Device Summary report”

on page 708.

Deduplication summary Displays a deduplication summary for all of the

deduplication jobs that run on the Backup Exec server.

See “Deduplication Summary report” on page 709.

Device Summary Lists the device usage and error summary for each
selected Backup Exec server.

See “Device Summary report” on page 710.

Disk Storage Summary Displays disk-based usage statistics for Backup Exec
server disk storage.

See “Disk Storage Summary report” on page 711.

 Reports 700
List of Backup Exec standard reports

Table 16-3 Backup Exec standard reports (continued)

Report Name Description

Error-Handling Rules Lists all the defined error-handling rules.

See “Error-Handling Rules report” on page 712.

Event Recipients Lists all events that were received by each notification
recipient.

See “Event Recipients report” on page 713.

Failed Backup Jobs Lists all the failed backup jobs, sorted by the resource
server and time frame.

See “Failed Backup Jobs report” on page 713.

Jobs Summary Lists all the jobs that ran within the last 72 hours in
chronological order.

Lists the jobs that ran in Veritas SaaS Backup.

See “Jobs Summary report” on page 714.

Managed Backup Exec Servers Lists the status and configuration for all Backup Exec
servers that are managed by a central administration
server.

See “Managed Backup Exec Servers report”

on page 716.

Media Audit Lists the recent media configuration changes.

See “Media Audit report” on page 717.

Media Errors Lists the number of errors that occur on all media.

See “Media Errors report” on page 718.

Media Required for Recovery Lists the media that contain the backup sets for each
system that is backed up on selected servers for the
specified time period. This report can be inaccurate if
media overwrite settings allow the media to be
overwritten.

See “Media Required for Recovery report” on page 718.

Media Summary Lists all the media sets and media that are used by
Backup Exec servers. The current location is given for
each media. Also lists usage statistics for media and
the location of media within Backup Exec media sets.

See “Media Summary report” on page 719.

 Reports 701
List of Backup Exec standard reports

Table 16-3 Backup Exec standard reports (continued)

Report Name Description

Media Vault Contents Lists the media that are located in each media vault.

See “Media Vault Contents report” on page 720.

Move Media to Vault Lists all media that can be moved to a media vault.
The listed media are not currently in a media vault and
the media’s append period has expired.

See “Move Media to Vault report” on page 720.

Operations Overview Lists past and future operations data for user-set
period.

See “Operations Overview report” on page 721.

Overnight Summary Lists the results of backup jobs for each resource
during the last 24 hours. This report includes backup
jobs that were scheduled to run but did not run. Jobs
are given a grace period of 24 hours before they are
marked as past due.

See “Overnight Summary report” on page 723.

Problem Files Lists all the problem files that are reported for jobs.
The files are grouped by day and resource.

See “Problem Files report” on page 724.

Recently Written Media Lists all media that have been modified in the last 24
hours.

See “Recently Written Media report” on page 725.

Recovery Ready Validation Lists the backup sets for which the Validate Virtual
Summary Machine for Recovery jobs are run.

See “Recovery Ready Validation Summary”

on page 725.

Resource Protected Recently Lists all job detail statistics and exceptions that
occurred on a Backup Exec server for which you run
this report.

See “Resource Protected Recently report” on page 726.

Resource Risk Assessment Lists job information for resources on which the last
backup job run on the resource failed. The data is
filtered by resource server.

See “Resource Risk Assessment report” on page 727.

 Reports 702
List of Backup Exec standard reports

Table 16-3 Backup Exec standard reports (continued)

Report Name Description

Restore Set Details by Resource Lists all restore sets that ran within the last 72 hours.
The sets are grouped by the server and resource.

See “Restore Set Details by Resource report”

on page 728.

Retrieve Media from Vault Lists all reusable media currently in the specified vault.

See “Retrieve Media from Vault report” on page 729.

Robotic Library Inventory Lists the contents of slots in robotic libraries that are
attached to Backup Exec servers. Usage statistics are
provided for each piece of media.

See “Robotic Library Inventory report” on page 729.

Scheduled Server Workload Lists the estimated scheduled workload for the next
24-hour period by server.

See “Scheduled Server Workload report” on page 730.

Scratch Media Availability Lists the aging distribution of media. Shows how many
media are available for overwrite and when other
media will become available for overwrite.

See “Scratch Media Availability report” on page 731.

Test Run Results Lists the results for the test run jobs that are set for
the selected time period and Backup Exec servers.

See “Test Run Results report” on page 732.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Alert History report

The Alert History report lists all the alerts in the Alert History chronologically,
displaying the most recent alerts first.

Table 16-4 Alert History report

Item Description

Time Date and time the alert occurred.

Received Time the alert occurred.

 Reports 703
List of Backup Exec standard reports

Table 16-4 Alert History report (continued)

Item Description

Responded Time when the user responded to the alert.

Responding User User that responded to the alert.

Job Name The name of the job that is associated with the alert.

Backup Exec server Name of the Backup Exec server on which the alert
occurred.

Category Title of the alert, such as Service Start or Job Failed.

Message A description of the event that caused the alert.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Alert History By Backup Exec Server report

The Alert History by Backup Exec server report lists all alerts in the alert history,
grouped and filtered by Backup Exec server, displaying the most recent alerts first.

Table 16-5 Alert History by Backup Exec Server report

Item Description

Backup Exec Name of the Backup Exec server on which the alert occurred.
server

Time Date and time the alert occurred.

Received Time the alert occurred.

Responded Time when the user responded to the alert.

Responding User User that responded to the alert.

Job Name Name of the job that is associated with the alert.

Category Title of the alert, such as Service Start or Job Failed.

Message Describes the event that caused the alert.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 704
List of Backup Exec standard reports

Audit Log report

The Audit Log report lists the contents of the audit logs for the selected servers for
the selected time period.

Table 16-6 Audit Log report

Item Description

Category Category in which the change occurred, such as Logon Account, Alerts,
or Job.

Date Entered Time and date the change occurred.

Message Description of the change that was made in Backup Exec.

User Name User that made the change.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Backup Job Success Rate report

The Backup Job Success Rate report lists the success rate for backup jobs.

Table 16-7 Backup Success Rate report

Item Description

Server Name of the server being backed up.

Date Date the backup job was processed.

Total Jobs Total number of jobs that were processed by the Backup Exec server.

Successful Total number of jobs successfully performed by the Backup Exec server.

Success Rate Percentage of successful jobs that were processed by the Backup Exec
server.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 705
List of Backup Exec standard reports

Backup Recommendations report

The Backup Recommendations report lists any recommendations that can help
you to better manage your backups. The recommendations may include better
ways to back up specific types of data or suggestions for how to use other products.

Table 16-8 Backup Recommendations report

Item Description

Backup Exec server Name of the Backup Exec server for which
the recommendation applies.

Job Name Name of the job that is associated with the

recommendation.

Start Time Date and time when the job that is associated
with the recommendation ran.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Backup Resource Success Rate report

The Backup Resource Success Rate report lists the success rate for backup jobs
for a specific number of days for resources on selected servers.

Table 16-9 Backup Resource Success Rate report

Item Description

Resource Name of the system being backed up.

Date Date the backup job was processed.

Total Jobs Total number of jobs that were processed by the Backup Exec server.

Successful Total number of jobs successfully performed by the Backup Exec server.

Success Rate Percentage of successful jobs that were processed by the Backup Exec
server.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 706
List of Backup Exec standard reports

Backup Sets by Media Set report

The Backup Sets by Media Set report lists all the backup sets by media set.

Table 16-10 Backup Sets by Media Sets report

Item Description

Media Set Name of the media set on which the job ran.

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Method Specific type of backup.

Business-Critical Indicates whether the backup set includes an item that was tagged as
a business-critical resource.

Date / Time Date and time the data was backed up.

Backup Set Describes the data that was backed up and the location of the data.
Description /
Source

Directories Number of directories that were backed up.

Files Number of files that were backed up.

Size Amount of data that was backed up.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Backup Size By Resource report

The Backup Size By Resource report lists the backup size for each resource job
for up to seven previous jobs. It also computes the trailing average, which is the
average of the amount of data that was backed up in the seven previous jobs.

Table 16-11 Backup Size by Resource Job report

Item Description

Server Name of the Backup Exec server where the data for the backup job
was located.

Resource Name of the resource that was backed up.

Job Name of the backup job.

 Reports 707
List of Backup Exec standard reports

Table 16-11 Backup Size by Resource Job report (continued)

Item Description

Job Date and Date and time the backup job was processed.
Time Run

Backup Size Amount of data that was backed up.

Trailing Avg Average amount of data that was backed up during the seven previous
runs.

Difference % Amount by which the data that was backed up in the current job differs
from the data that was backed up in the previous backup jobs.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Cloud Storage Summary report

The Cloud Storage Summary report displays a summary of the size of cloud storage
that the backed up data uses on the Backup Exec server.

Table 16-12 Cloud Storage Summary report

Item Description

Device Name The name of the cloud storage device.

Cloud The fully qualified name of the server on which the device exists.
Storage
Server

Cloud The name of the storage location on the cloud storage device. These storage
Bucket units are called buckets..

Bytes The amount of data written to the cloud storage device.

Written

Bytes Read The amount of data read from the cloud storage device.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 708
List of Backup Exec standard reports

Daily Device Utilization report

The Daily Device Utilization report lists the percentage of the storage devices’
capacity that the Backup Exec server uses.

Table 16-13 Daily Device Utilization report

Item Description

Drive Name Name of the storage device and the Backup Exec server where the
device is located.

Status Status of the storage device

Statuses for storage devices are as follows:

■ Pause
The storage device is temporarily stopped.
■ Enable
The storage device is available for use with Backup Exec. If the
storage device is disabled, it is available for use with other
applications.
■ Online
The storage device is available for use.
■ Offline
Backup Exec cannot access the storage device.

Date Date the storage device was used.

Jobs Number of jobs that were processed by the Backup Exec server’s
storage device.

Size The amount of data that was processed by the Backup Exec server’s
storage device.

Utilization (%) Percentage of device utilization.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Deduplication Device Summary report

The Deduplication device summary report displays a summary of the deduplication
operations for local deduplication disk storage and shared deduplication disk storage.
 Reports 709
List of Backup Exec standard reports

Table 16-14 Deduplication device summary report

Item Description

State Device state, such as online and enabled.

Created Date media was created.

Total Capacity Total capacity of the deduplication disk

storage.

Used Capacity Capacity presently used by the deduplication

disk storage.

Available Capacity Remaining capacity of the deduplication disk

storage.

Percent Full Percentage of storage space that is available

in the deduplication disk storage.

Protected Bytes Total amount of data that is selected for

backup in all jobs using the device before
deduplication occurs.

Deduplication Ratio Ratio of the amount of data before

deduplication to the amount of data after
deduplication.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Deduplication Summary report

The Deduplication Summary report displays a deduplication summary for all of the
deduplication jobs that run on the Backup Exec server.

Table 16-15 Deduplication Summary report

Item Description

Job Name Name of the job.

Start Time Time of day that Backup Exec attempted to

start the job.

Duration Length of time the operation took to process.

Size The amount of data processed.

 Reports 710
List of Backup Exec standard reports

Table 16-15 Deduplication Summary report (continued)

Item Description

Size/Minute Number of kilobytes, megabytes, or gigabytes

processed per minute.

Scanned Byte Count Total amount of data that is selected for

backup before deduplication occurs.

Stored Byte Count The amount of unique data is stored after

deduplication occurs.

Deduplication Ratio Ratio of the amount of data before

deduplication to the amount of data after
deduplication.

Status Status of the operation, such as Completed

(Success), Failed, or Canceled.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Device Summary report

The Device Summary report lists all the devices for each selected Backup Exec
server.

Table 16-16 Device Summary report

Item Description

Server Name of the server where the device is located.

Drive Name Name of the drive in the robotic library.

Target Address of the storage device that is connected to the Backup Exec
server.

State Device state, such as online.

Created Date on which the media was created.

Cleaned Date on which the last cleaning job was run on the drive.

Hours Hours the device has been in use since the last cleaning job.

Errors Number of errors occurring since the last cleaning job.

 Reports 711
List of Backup Exec standard reports

Table 16-16 Device Summary report (continued)

Item Description

Size Amount of data that was read and written since the last cleaning job.

Mounts Number of mounts occurring since the last cleaning job.

Hours Total number of hours the device has been in use.

Errors Total number of errors occurring on the device.

Size Amount of data that was read and written to the device.

Mounts Total number of mounts occurring to the device.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Disk Storage Summary report

The Disk Storage Summary report displays disk usage statistics for Backup Exec
server disk storage.

Table 16-17 Disk storage summary report

Item Description

Device Name Name of the disk storage device.

State State of the device.

Device states include the following:

■ Online
■ Enabled
■ Offline
■ Paused
■ Disabled

Local Access Path Path on the disk where backup data is stored.

Total Capacity Total capacity of the disk.

Used Space Amount of disk space being used as storage.

Free Space Amount of disk space remaining.

See “Running a report now” on page 682.

 Reports 712
List of Backup Exec standard reports

See “Creating a custom report” on page 684.

Error-Handling Rules report

The Error-Handling Rules report lists all error-handling rules and provides details
about each rule.

Table 16-18 Error Handling Rules report

Item Description

Rule Name Name of the Error-Handling rule.

Notes Information that was entered in the Notes section when the
error-handling rule was created.

Job Status Final job status that activates the rule.

Possible statuses are as follows:

■ Error
■ Canceled

Error Category Category of error for which the rule will be applied.
Available error categories include the following:

■ Device
■ Job
■ Media
■ Network
■ Other
■ Resource
■ Security
■ Server
■ System

Enabled Displays if the rule is enabled or disabled.

Cancel Job Displays an X if this option is selected for the error-handling rule. The
option cancels all jobs after the maximum number of retries have been
attempted.

Pause Job Displays an X if this option is selected for the error-handling rule. The
option enables Backup Exec to pause the job until you can manually
clear the error.

Retry Job Displays an X if this option is selected for the error-handling rule. The
option enables Backup Exec to retry the job.
 Reports 713
List of Backup Exec standard reports

Table 16-18 Error Handling Rules report (continued)

Item Description

Maximum Retries Number of times the job is to be retried.

Retry Interval Number of minutes Backup Exec waits before trying to run the job again.
(minutes)

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Event Recipients report

The Event Recipient report lists events that were registered for each notification
recipient.

Table 16-19 Event Recipients report

Item Description

Recipient Name Name of the recipient.

Recipient type Designates to whom the Event Recipients report is sent, such as an
individual recipient or a group of recipients.

Event Type Alert category or ad hoc job.

Event Name Detail for the alert category or ad hoc job.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Failed Backup Jobs report

The Failed Backup Jobs report lists all the failed backup jobs. The jobs are sorted
by the server and specified time frame.

Table 16-20 Failed Jobs report

Item Description

Resource Name of the system being backed up.

Start Time Date and time the backup job started.

Duration Length of time the operation took to process.

 Reports 714
List of Backup Exec standard reports

Table 16-20 Failed Jobs report (continued)

Item Description

Job Name Name of job that failed.

Business-Critical Indicates whether the job included items that were tagged as
business-critical resources.

Category Category for the failed job that may be generated by a system, job,
media, or device error.

Error Code Displays the error code that corresponds to the failure.

Description Describes the event that caused the error.

Status Status of the operation, such as Error.

Device Name Name of the device on which the job ran.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Jobs Summary report

The Jobs Summary report lists all jobs that have run within the specified time range.
The jobs are listed in chronological order.

Table 16-21 Jobs Summary report

Item Description

Start Time Date and time the operation started.

Job Name Name of the completed job.

Duration Length of time that the operation processed.

Size The amount of data processed.

Files Number of files processed.

Directories Number of directories processed.

Size/Minute Number of kilobytes, megabytes, or gigabytes processed per minute.

Skipped Number of files that were skipped during the operation.

Corrupt Files Number of corrupt files that were encountered during the operation.
 Reports 715
List of Backup Exec standard reports

Table 16-21 Jobs Summary report (continued)

Item Description

Files in Use Number of files in use during the operation.

Status Status of the operation, such as Completed (Success), Failed, or

Canceled.

Type Lists the type of job that Backup Exec ran within the specified time
range.

Table 16-22 Veritas SaaS Backup data in the Jobs Summary report

Item Description

Connector Name of the connector from Veritas SaaS Backup, such

as G Suite, Office365, and Salesforce.

Job Displays details about the operation processed.

Statistics

Type Lists the type of job that Veritas SaaS Backup ran within
the specified time range, such as Backup, Restore, or
Item Restore.

Status Status of the operation, if it has Succeeded or Failed.

Start Time Date and time the operation started.

Duration Length of time that the operation processed.

Files Number of files processed during the operation.

Size The amount of data processed.

File Displays details about the files that were removed or

Exceptions failed during the operation.

Removed Number of files removed during the operation.

Removed Size Size of the removed files during this operation.

Failed Number of files failed during the operation.

Failed Size Size of the failed files during this operation.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 716
List of Backup Exec standard reports

Managed Backup Exec Servers report

The Managed Backup Exec Servers report lists status and configuration information
for the managed Backup Exec servers in a Central Admin Server feature
environment.

Table 16-23 Managed Backup Exec Servers report

Item Description

CAS Servers Names of the central administration servers.

Managed Backup Names of the managed Backup Exec servers.

Exec server

Status Status of the server.

Possible statuses include the following:

■ Online - available for use.

■ Stalled - not responding immediately to messages
■ No Comm - communications to the server have been lost for some
period of time.

Stalled Time limit that was used for determining Stalled communications status.

No Comm Time limit that was used for determining No Comm communications
status.

Catalog Location Location of the catalog information.

Possible locations are as follows:

■ Local - the catalog information is located on the managed Backup

Exec server.
■ CAS - the catalog information is located on the central administration
server.

Logs When job logs are uploaded from the managed server to the CAS
database.
Possible upload times are as follows:

■ Timed basis in seconds

■ Scheduled time
■ Completion of job
■ Never
 Reports 717
List of Backup Exec standard reports

Table 16-23 Managed Backup Exec Servers report (continued)

Item Description

History When job history is uploaded from the managed server to the CAS
database.
Possible upload times are as follows:

■ Timed basis in seconds

■ Scheduled time
■ Completion of job
■ Never

Status When status is uploaded from the managed server to the CAS database.
Possible upload times are as follows:

■ Timed basis in seconds

■ Scheduled time
■ Completion of job
■ Never

Display Alert Displays Yes if you have configured an alert to be set if the time
difference between the central administration server's clock and a
managed Backup Exec server's clock exceeds a preset value (maximum
time difference tolerance).

Sec Maximum time difference tolerance in seconds that is set for server.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Media Audit report

The Media Audit report lists the recent configuration changes that you made to your
media.
In a Central Admin Server feature (CAS) environment, if you run this report from
the central administration server the report provides data only for the media for the
central administration server; it does not provide any data for any of the managed
Backup Exec servers. To obtain the media audit data for a managed Backup Exec
server, you can do one of the following:
■ Log on locally to the managed Backup Exec server and run the report from it.
■ Use the Remote Administrator feature to log on to the managed Backup Exec
server from a remote Windows server or workstation, and then run the report.
 Reports 718
List of Backup Exec standard reports

Table 16-24 Media Audit report

Item Description

Date Entered Time and date the change occurred.

Message Description of the change that was made to the media.

User Name User that made the change.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Media Errors report

The Media Errors report lists the number of errors that occur on all media.

Table 16-25 Media Errors report

Item Description

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Business-Critical Indicates whether the media contains a backup set that has a
business-critical resource.

Total Mounts Total number of times this media has been mounted.

Total In Use Total number of hours that this media has been in use.
Hours

Total Errors Total number of error alerts for the system, jobs, media, and devices.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Media Required for Recovery report

The Media Required for Recovery report lists the media that contain the backup
sets for each system that was backed during the specified time period. However,
this report may be inaccurate if media overwrite settings allow the media to be
overwritten.
 Reports 719
List of Backup Exec standard reports

Table 16-26 Media Required for Recovery report

Item Description

Date Date and time the backup job set was created.

Media Location Name of the storage device where the media that was used for the
Name backup job is stored.

Media Label Media label that is assigned to the media.

Business-Critical Indicates whether the media includes a backup set that has a
business-critical resource.

Recycle Time Displays the date and the time after which the media can be overwritten.

Backup Method Specific type of backup.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Media Summary report

The Media Summary report lists all media sets and media that are used by Backup
Exec servers. Usage statistics are given for each piece of media.

Table 16-27 Media Summary report

Item Description

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Media Type Type of media cartridge, such as 4mm.

Allocated Date media was allocated to a media set as a result of an overwrite

operation.

Modified Date data was last written to the media.

Business-Critical Indicates whether the media includes a backup set that has a
business-critical resource.

Hours Total number of hours that the media has been in use.

Mounts Total number of times the media has been mounted.

Soft Errors Number of recoverable read errors encountered.

 Reports 720
List of Backup Exec standard reports

Table 16-27 Media Summary report (continued)

Item Description

Hard Errors Number of unrecoverable read errors encountered.

Write Size Amount of data that has been written to the media.

Current Size Estimate of the amount of data currently on the media.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Media Vault Contents report

The Media Vault Contents report lists all the media in a specified media vault.

Table 16-28 Media Vault Contents report

Item Description

Vault Name Location of the media.

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Overwrite Date that data on the media may be overwritten.

Protection End
Date

Vault Media Rule Date media can be moved to vault.

Move Date

Media Set Name of media set to which the media belongs.

Vault Media Rule Name of vault media rule.

Name

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Move Media to Vault report

Lists all media that you can move to a media vault.
The media listed are not currently in a media vault and meet one of the following
criteria:
 Reports 721
List of Backup Exec standard reports

■ The media has met or exceeded the vault move date that was specified for the
media containing the media.
■ The append period `has expired, but the overwrite protection period is still current
(allocated).

Table 16-29 Move Media to Vault report

Item Description

Backup Exec Name of the Backup Exec server where the data for the backup job
server was located.

Media Set Name of the media set.

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Location Location of the media.

Append Period Last date that data may be added to the media.
End Date

Overwrite Date that data on the media may be overwritten.

Protection End
Date

Vault Media Rule Date media can be moved to vault.

Move Date

Vault Name Name of vault to which media is to be moved.

Vault Media Rule Name of vault media rule.

Name

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Operations Overview report

The Operations Overview report lists details for past and future Backup Exec
operations.
 Reports 722
List of Backup Exec standard reports

Table 16-30 Operations Overview report

Item Description

Job summary for Details Backup Exec job activity for the specified time period.
jobs completed in
the past x Hours

Errors Total number of error alerts for the system, jobs, media, and devices.

Warnings Total number of warning alerts for of jobs, media, and devices.

Information Total number of informational alerts for the system, jobs, media, and
devices.

Attention Total number of alerts that require a response from the user.
Required

Completed Total number of jobs that failed.

(Failed)

Completed Total number of canceled jobs.

(Canceled)

Completed Total number of jobs that completed successfully.

(Success)

Exceptions Total number of jobs that completed successfully, but may contain one
or more skipped files, corrupt files, virus infected files or files in use.

Total Data Total amount of data that was backed up in kilobytes, megabytes, or
Backed Up gigabytes.

Total Media Used Total number of media that were used to back up the completed jobs.

Missed Total number of missed jobs.

Recovered Total number of recovered jobs.

Active Jobs Total number of active jobs.

Scheduled Jobs Displays those jobs whose scheduled start times begin within 72 hours
of the job being created. Jobs with recurring schedules also appear if
their start times begin within 72 hours of the job's last start time.

Jobs On Hold Total number of jobs on hold.

Job Status The status of the jobs.

Scratch Media Total number of scratch media available.

Recyclable Total number of recyclable media available.

 Reports 723
List of Backup Exec standard reports

Table 16-30 Operations Overview report (continued)

Item Description

Imported Number of imported media. Imported media is media that was created
by a product other than this installation of Backup Exec.

Allocated Number of allocated media (media belonging to a user media set).

Total Total number of overwritable media available.

Overwritable
Media

Total Appendable Total number of appendable media available.

Media

Media Overwrite Displays the level of overwrite protection (Full, Partial, None) that is
Protection Level assigned to the media.

Online Devices Total number of online devices.

Offline Devices Total number of offline devices.

Disabled Devices Total number of disabled devices.

Paused Devices Total number of paused devices.

Disabled Lists the name of the devices that are disabled.

Paused Name of the paused devices.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Overnight Summary report

The Overnight Summary report lists the results of backup jobs for each resource
during the last 24 hours. This report includes backup jobs that were due to run but
did not run. Jobs are given a grace period of 24 hours before being marked as past
due.

Table 16-31 Overnight Summary report

Item Description

Resource System being backed up.

 Reports 724
List of Backup Exec standard reports

Table 16-31 Overnight Summary report (continued)

Item Description

Type Displays the type of job that Backup Exec runs to produce the Overnight
Summary report.

Because the Overnight Summary report lists the results of backup jobs
for each resource during the past 24 hours, Backup is always the type
of job that appears

Start time Date and time the operation started.

Business-Critical Indicates if the item was tagged as a business-critical resource.

Status Status of the operation.

Error Category Category for the job that may be generated by a system, job, media,
or device error.

Backup Exec Name of the Backup Exec server on which the job ran.
server

Device Name Name of the device on which the job ran.

Total Tasks Total number of jobs that ran within the last 24 hours.

Uncorrected Number of the jobs that fail and were not run again with successful
Exceptions completion.

Service Level Percentage of jobs that ran successfully.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Problem Files report

The Problem Files report lists all the problem files that were reported for jobs. The
files are grouped by day and resource.

Table 16-32 Problem Files report

Item Description

Date Date the problem file was encountered.

Resource System on which the problem file is located.

Time Time the problem file was encountered.

 Reports 725
List of Backup Exec standard reports

Table 16-32 Problem Files report (continued)

Item Description

Reason Error code that is listed in the job log summary.

File Name Name of the problem file.

Type Lists the type of job that Backup Exec ran when problematic files were
detected.

Backup Exec Name of the Backup Exec server on which the file is located.
Server

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Recently Written Media report

The Recently Written Media report lists all the media that has been modified within
the specified period.

Table 16-33 Recently Written Media report

Item Description

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

Location Location of the media, such as the storage vault name or drive name.

Set Name of backup set.

Date and Time Date and time media was last modified.
Modified

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Recovery Ready Validation Summary

The Recovery Ready Validation Summary report shows the summary of the virtual
machines that you validated.
 Reports 726
List of Backup Exec standard reports

Table 16-34 Recovery Ready Validation Summary report

Item Description

Backup Set Displays the details of the backup set. name of the backup set, size of the
Details backup set, and name of the device

■ Backup set: Name of the backup set.

■ Size: Size of the backup set.
■ Device Name: Name of the device.

Job Displays details about the validation job.

Statistics
■ Job Name: Name of the validation job.
■ Start Time: Time when the validation job started.

Backup Set Displays the status of the tests and checks run on the backup set.
Validation
■ Register VM: Status of the Register VM test.
■ Power ON: Status of the Power ON test.
■ Heartbeat Check: Status of the Heartbeat check.

Validation Displays the final validation status of the backup set.

Status
■ Validation passed
■ Validation failed
■ Unable to validate

The validation status and the range of the report that you selected are displayed in
the Recovery Ready Validation Summary report.
If you do not select the range, the report is displayed for last 30 days. If you run the
same validation job multiple times for the same backup set, the report displays
information for the latest run of the validation job.

Resource Protected Recently report

The Resource Protected Recently report lists all job detail statistics and exceptions
that occurred on a Backup Exec server for which you run this report.

Table 16-35 Resource Protected Recently report

Item Description

Start Time Date and time the backup job started.

Business-Critical Indicates whether the item was tagged as a

business-critical resource.
 Reports 727
List of Backup Exec standard reports

Table 16-35 Resource Protected Recently report (continued)

Item Description

Duration Amount of time that was required for the job

to complete.

Size Amount of data that was backed up.

Files Number of files that were backed up.

Directories Number of directories that were backed up.

Size per Min Amount of data that was backed up per

minute.

Skipped Number of files that were skipped during the

backup.

Corrupt Files Number of corrupt files that were detected

during the backup.

Files in Use Number of files that were in use during the

backup.

Status Status of the backup job.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Resource Risk Assessment report

The Resource Risk Assessment report shows job information for resources on
which the last backup job that was run on the resource failed.

Table 16-36 Resource Risk Assessment report

Item Description

Resource System on which the job ran.

Error Text Describes the event that caused the job to fail.

Start Time Time the operation started.

Job Name of the job that failed.

Business-Critical Indicates whether the item was tagged as a business-critical resource.

 Reports 728
List of Backup Exec standard reports

Table 16-36 Resource Risk Assessment report (continued)

Item Description

Error Category The category for the failed job that may be generated by a system, job,
media, or device error.

Backup Exec Name of the Backup Exec server on which the job ran.
Server

Device Name Name of the device on which the job ran.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Restore Set Details by Resource report

The Restore Set Details by Resource report lists all restore jobs that ran within the
specified time range on a selected server. The jobs are grouped by the server and
resource.

Table 16-37 Resource Set Details by Resource report

Item Description

Resource Name of the system being backed up.

Start Time Date and time the operation started.

Duration Length of time the operation took to process.

Size The amount of data processed.

Files Number of files processed.

Directories Number of directories processed.

Data/Minute Amount of data that was processed per minute.

Skipped Number of files that were skipped during the operation.

Corrupt Files Number of corrupt files that were encountered during the operation.

Files in Use Number of files in use during the operation.

Status Status of the operation, such as Completed.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 729
List of Backup Exec standard reports

Retrieve Media from Vault report

The Retrieve Media from Vault report lists all reusable media currently in a specified
media vault.

Table 16-38 Retrieve Media from Vault report

Item Description

Cartridge Label Displays the name of the disk cartridge. Disk cartridge names cannot
exceed 128 characters.

You can rename the disk cartridge.

See “Editing disk cartridge properties” on page 329.

Vault Name Displays the name of the vault where the media is located.

Media Set Name Displays the name of the media set.

Offsite Return Displays the date that the media was returned to the off-site vault.
Date

Recycle Date Displays the date after which the media can be overwritten.

No Append Date Displays the date on which Backup Exec can no longer append data
to the media.

Rule Name Displays the name of vault media rule that is applied to the media.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Robotic Library Inventory report

The Robotic Library Inventory report lists the contents of slots in robotic libraries
that are attached to Backup Exec servers. Usage statistics are provided for each
piece of media.

Table 16-39 Robotic Library Inventory report

Item Description

Server Name of the server where the robotic library is located.

Device Name Name of the robotic library.

Slot Sequential number of the slot in the robotic library.

 Reports 730
List of Backup Exec standard reports

Table 16-39 Robotic Library Inventory report (continued)

Item Description

Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned barcode label.

State State of operation of the slot: paused, disabled, enabled, offline, or

online.

Modified Date the media in the slot was last accessed.

Business-Critical Indicates whether the media includes a backup set that has a
business-critical resource.

Write Number of bytes that have been written to this media.

Full Space available on a media; "1" indicates that media is full and "0"
indicates that there is space available on the media.

Hours Total number of hours this media has been in use.

Mounts Total number of times this media has been mounted.

Append The time remaining in the media’s append period.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Scheduled Server Workload report

The Scheduled Server Workload report displays the estimated scheduled workload
for a server during the next 24-hour period or a user-defined time period. The report
only displays recurring jobs that have already run at least one time, not jobs
scheduled to run once.

Table 16-40 Scheduled Server Workload report

Item Description

Backup Exec Name of the Backup Exec server that will process the scheduled jobs.
server

Job Name of the job that is scheduled to run.

Next Due Date Time and day the next job is scheduled to run.

Backup Size Estimated amount of data to be processed during the next 24 hours.
 Reports 731
List of Backup Exec standard reports

Table 16-40 Scheduled Server Workload report (continued)

Item Description

Total Size Total amount of data to be processed on the server during the next 24
hours.

Total Size Total amount of data to be processed on all Backup Exec servers.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.

Scratch Media Availability report

The Scratch Media Availability report shows the aging distribution of media, how
many media are available for overwrite, and when other media will become available
for overwrite.

Table 16-41 Scratch Media Availability report

Item Description

Cartridge Label Cartridge label that was assigned by Backup Exec, assigned by the
administrator, or contained on a pre-assigned barcode label

You can rename the cartridge.

See “Editing disk cartridge properties” on page 329.

Media Location Name of the storage device that contains the actual media.
Name

Total Capacity Total native capacity of the scratch media without using compression.

Append Hours Capacity of scratch media available for append.

Remaining

Remaining Total amount of remaining native capacity of the scratch media without
Capacity compression.

Retention Hours The amount of time remaining to retain and protect the media from
Remaining being overwritten.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Reports 732
List of Backup Exec standard reports

Test Run Results report

The Test Run Results report displays the results for the test run jobs that are set
for the selected period.

Table 16-42 Test Run Results report

Item Description

Backup Exec Name of the Backup Exec server on which the job ran.
server

Job Date and Date and time the backup job was processed.
Time Run

Job Name Name of the test run job.

Backup Sets Name of the backup set.

Credential Check Indicates if the Backup Exec logon account was verified as correct for
the resources being backed up.

Backup Size Size in kilobytes, megabytes, or gigabytes of the backup.

Media Type Type of media used, such as 4mm.

Device Name Name of the device, such as the name of the robotic library.

Max Needed Amount of space that is needed on the media to run the job.

Online Capacity of media available in the device to which data can be

appended.

Media Total Total amount of appendable media available to the system.

Online Capacity of media available in the device to which data can be written.

Media Total Total amount of overwritable media available to the system.

See “Running a report now” on page 682.

See “Creating a custom report” on page 684.
 Chapter 17
Instant Cloud Recovery
This chapter includes the following topics:

■ About Instant Cloud Recovery

■ Instant Cloud Recovery tab overview in Backup Exec

■ Requirements to configure Instant cloud recovery in Backup Exec

■ Preconfigurations to be completed in the Azure portal

■ How to configure Azure resources

■ How to view error details

■ How to view configuration details

■ How to view virtual machine details

■ How to manually refresh the view of virtual machines

■ How to enable replication for virtual machines

■ How to manage replication for virtual machines

■ How to manage failover for a virtual machine

■ How to change the Subscription or Recovery Services Vault

■ How to prepare a new infrastructure

■ How to remove a configured Azure resource from Backup Exec

■ How to renew the Backup Exec certificate

 Instant Cloud Recovery 734
About Instant Cloud Recovery

About Instant Cloud Recovery

Backup Exec users get Disaster Recovery powered by Azure Site Recovery. You
can set up the Microsoft Azure infrastructure in Backup Exec that helps you save
time and additional costs.
You can monitor the health of virtual machines that are managed from Azure Site
Recovery. You can independently day-to-day monitoring of virtual machines from
the Backup Exec console.
Instant Cloud Recovery helps you enable replication for your on-premises virtual
machines (VMware and Hyper-V), whose hosts are configured with Azure Site
Recovery. If an outage or failure occurs, you can failover the replicated virtual
machines to Azure to ensure that they are available for business operations.

See “Instant Cloud Recovery tab overview in Backup Exec” on page 735.
See “Requirements to configure Instant cloud recovery in Backup Exec” on page 737.
See “Preconfigurations to be completed in the Azure portal ” on page 738.
See “How to configure Azure resources” on page 738.
See “How to enable replication for virtual machines” on page 743.
See “How to manage failover for a virtual machine” on page 746.
See “How to manage replication for virtual machines” on page 745.
See “How to change the Subscription or Recovery Services Vault” on page 746.
See “How to view configuration details” on page 742.
 Instant Cloud Recovery 735
Instant Cloud Recovery tab overview in Backup Exec

See “How to renew the Backup Exec certificate” on page 748.

See “How to prepare a new infrastructure” on page 747.
See “How to manually refresh the view of virtual machines” on page 743.
See “How to remove a configured Azure resource from Backup Exec” on page 747.
See “How to view virtual machine details” on page 742.

Instant Cloud Recovery tab overview in Backup

Exec
On the Instant Cloud Recovery tab, you can manage disaster recovery with Azure
Site Recovery. You can monitor the replication health of virtual machines and enable
replication of on-premises virtual machines, whose hosts are configured with Azure
Site Recovery.
With the Instant Cloud Recovery tab you can also refresh the view of virtual
machines in Backup Exec, change the Subscription and Recovery Services Vault,
view error details, renew certificate, view virtual machine details from the Azure
portal, manage failover from the Azure portal, create new infrastructure from the
Azure portal, and delete the Azure resource configuration from Backup Exec.
You can view the protection status, replication health, and validation errors for a
virtual machine.
See “About Instant Cloud Recovery” on page 734.
 Instant Cloud Recovery 736
Instant Cloud Recovery tab overview in Backup Exec

Table 17-1 Disaster Recovery to Cloud tab

Group Item Description

Manage Manage Failover Lets you manage failover only for a virtual machine that
is replicated or protected.

This option takes you to the Azure portal to manage the

failover.

See “How to manage failover for a virtual machine”

on page 746.

Manage Replication Lets you manage replication for virtual machines of a

configured Recovery Services Vault from the Azure
portal.

This option takes you to the Azure portal to manage the

replication.

See “How to manage replication for virtual machines”

on page 745.

View Error Details Lets you view errors for a virtual machine. Before you
protect a virtual machine, you must resolve any validation
errors that are identified.

See “How to view error details” on page 741.

Update Change Lets you change the Azure Subscription or Recovery

Operations Subscription or Services Vault for Backup Exec to monitor and manage
Vault Azure Site Recovery resources.
See “How to change the Subscription or Recovery
Services Vault” on page 746.

Refresh View Lets you manually refresh the view of the virtual
machines based on the Subscription and Recovery
Services Vault that you selected.

See “How to manually refresh the view of virtual

machines” on page 743.

Renew Certificate Lets you renew the Backup Exec certificate that connects
you to the Azure portal.

See “How to renew the Backup Exec certificate”

on page 748.
 Instant Cloud Recovery 737
Requirements to configure Instant cloud recovery in Backup Exec

Table 17-1 Disaster Recovery to Cloud tab (continued)

Group Item Description

Configure Configure Azure Lets you configure Azure resources by selecting a

Resources Subscription and an existing Azure Recovery Services
Vault or create a new Azure Recovery Services Vault.
Based on your selection, you can see a list of virtual
machines that are available in the configured Azure
Recovery Services Vault.

See “How to configure Azure resources” on page 738.

View Configuration Lets you view the configured Azure resource details.
Details
See “How to view configuration details” on page 742.

Prepare New Lets you prepare new infrastructure for the configured
Infrastructure Recovery Services Vault on the Azure portal.

This option takes you to the Azure portal to prepare the

new infrastructure.

See “How to prepare a new infrastructure” on page 747.

Remove Lets you delete the configured Azure resources and the
Configuration view of the virtual machines from Backup Exec.

See “How to remove a configured Azure resource from

Backup Exec” on page 747.

Virtual Machine Lets you view details only for a protected virtual machine
Details in Backup Exec on the Azure portal.

This option takes you to the Azure portal to view the

virtual machine details.

See “How to view virtual machine details” on page 742.

Requirements to configure Instant cloud recovery

in Backup Exec
To monitor the health and enable replication of virtual machines using Instant Cloud
Recovery, following are the requirements from Backup Exec:
■ Ensure that you have created a Subscription in the Azure portal.
■ Ensure that you log on to Microsoft Azure as a user who satisfies the given
criteria.
 Instant Cloud Recovery 738
Preconfigurations to be completed in the Azure portal

■ Global administrator for the Active Directory tenant of the Azure subscription
or has the permissions to create apps in the tenant.
■ Owner or User Access Administrator for the Azure subscription.
Refer to the Required permissions section in the Microsoft documentation
for more information.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/
resource-group-create-service-principal-portal

■ Ensure that you prepare the infrastructure in the Azure portal if you create a
Recovery Services Vault in Backup Exec.
See “Preconfigurations to be completed in the Azure portal ” on page 738.

Preconfigurations to be completed in the Azure

portal
To monitor the health and enable replication of virtual machines in Backup Exec,
you must complete certain configurations In the Azure portal.
See “Prepare VMware or Hyper-V infrastructure” on page 738.
See “About Instant Cloud Recovery” on page 734.
See “Requirements to configure Instant cloud recovery in Backup Exec” on page 737.

Prepare VMware or Hyper-V infrastructure

To replicate VMware or Hyper-V virtual machines to Azure, prepare your on-premises
VMware or Hyper-V infrastructure.
For more information about preparing infrastructure for your VMware or Hyper-V
machines, refer to the Microsoft Azure documentation.
https://docs.microsoft.com/en-us/azure/site-recovery/
vmware-azure-tutorial-prepare-on-premises
https://docs.microsoft.com/en-us/azure/site-recovery/
hyper-v-prepare-on-premises-tutorial

How to configure Azure resources

You can configure Azure resources by selecting a Subscription and an existing
Recovery Services Vault or create a new Recovery Services Vault. Based on your
selection, you can view a list of virtual machines. You can monitor the replication
 Instant Cloud Recovery 739
How to configure Azure resources

health of virtual machines and enable replication of on-premises virtual machines,

whose hosts are configured with Azure Site Recovery.
If you configure disaster recovery to Azure Site Recovery for the first time, no virtual
machines are available for replication when you go to the Instant Cloud Recovery
tab.
To configure Azure resources
1 On the Instant Cloud Recovery tab, click Configure Azure resources.
You can go to the Azure portal for more information about Azure Site Recovery.
2 On the Configure Azure Resources wizard, select the cloud environment that
you want to use for the configuration.
The cloud environments are displayed. For example, Azure, Azure China,
Azure Germany, Azure US Government Cloud.
3 Click Next.
The Microsoft logon dialog box appears.
Ensure that you log on to Microsoft Azure as a user who satisfies the given
criteria:
Refer to the Required permissions section in the Microsoft documentation for
more information:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/
resource-group-create-service-principal-portal
■ Global administrator for the Active Directory tenant of the Azure subscription
or has the permissions to create apps in the tenant.
■ Owner or User Access Administrator for the Azure subscription.
After the logon is complete, you are redirected to the Configure Azure
Resources wizard.
Based on your Azure account, the list of your Subscriptions is retrieved from
the Azure portal.
 Instant Cloud Recovery 740
How to configure Azure resources

4 Select the Azure Subscription that you want to use for the configuration.

Note: Ensure that you only select a valid Subscription.

If there are no Subscriptions created for the Azure account, a message is

displayed. You must go to the Azure portal and create the Subscription. After
the Subscription is created, start the configuration again from Step 1.
For more information about how to create an Azure Subscription, refer to the
following link:
https://azure.microsoft.com/en-in/free/
5 Click Next.
Based on the Subscription that you select, a list of Recovery Services Vaults
is retrieved from Azure.
6 Do one of the following:

To use an existing Do the following in the order listed:

Recovery Services
1 Select the Recovery Services Vault from the drop-down list.
Vault
Based on the Recovery Services Vault, the region is
displayed. You cannot change the region.

2 Click Finish.

To create a new Do the following in the order listed:

Recovery Services
1 Select Create a new vault from the drop-down list.
Vault
2 Specify a name for the new Recovery Services Vault.

3 Select the region of the vault from the drop-down list.

4 Click Finish.

A message appears that you will be directed to the Azure

portal.

5 Click OK.

You are redirected to the Azure portal. On the Azure portal,

prepare the infrastructure for the new vault.

Backup Exec retrieves information about the vault, the list of virtual machines based
on the infrastructure of the Recovery Services Vault, and displays the information
on the Backup Exec console.
The following information is displayed:
 Instant Cloud Recovery 741
How to view error details

Name Displays the name of the virtual machine as displayed on the Azure
portal. For ESX or Hyper-V this is display name of the virtual machine.

Replication Displays the replication health; whether the virtual machine is replicated
Health successfully or if there are any errors or warnings. The most common
statuses for replication health are:

■ Warning
■ Healthy
■ Critical
■ Not replicated

Protection Status Displays the protection status; whether the virtual machine is protected.
The most common values for protection status are Protected and
Unprotected.

Configuration Displays if there are any configuration issues identified for a virtual
Issues machine by Azure and the number of issues.

To view the configuration issues, select the virtual machine, and click
View Error Details.

Last Successful Displays the date and time when the last successful failover was
Failover completed.

RPO Recovery Point Objective (RPO)

Displays the date and time when the last successful replication was
completed.

Validation Errors Displays if there are any validation errors identified for a virtual machine
and the number of such errors. To view the validation errors, select the
virtual machine, and click View Error Details.

If a virtual machine has validation errors, you cannot protect the

machine. You must first resolve the validation errors and then protect
the machine.

See “About Instant Cloud Recovery” on page 734.

How to view error details

You can view the errors for a virtual machine. You must resolve the validation errors
and then protect a virtual machine. You cannot enable replication for a virtual
machine that has validation errors.
On the Instant Cloud Recovery tab, select the virtual machine and in the Manage
group, click View Error Details.
 Instant Cloud Recovery 742
How to view configuration details

The View Error Details dialog box is displayed giving information about the type
of errors for the virtual machine. There are three types of errors:
■ Validation Errors
■ Configuration Issues
■ Replication Health Issues
For any type of error, the error message is displayed along with the possible cause
of the error and recommended solution.

How to view configuration details

You can view configured Azure resource details in the Backup Exec console.
On the Instant Cloud Recovery tab, in the Configure group, click View
Configuration Details.
The Azure Resource Configuration Details dialog box is displayed.

Table 17-2 Azure Configuration Details

Item Description

Subscription ID Subscription ID from the Azure portal.

Subscription Name of the configured Subscription.

Name

Recovery Name of the configured Recovery Services Vault.

Services Vault

See “About Instant Cloud Recovery” on page 734.

How to view virtual machine details

You can view details of a virtual machine on the Azure portal. You cannot view
details of a virtual machine that is not protected.
On the Instant Cloud Recovery tab, do one of the following:
■ Select the virtual machine for which you want to view details and in the Configure
group, click Virtual Machine Details.
■ Right-click the virtual machine for which you want to view details and click Virtual
Machine Details.
 Instant Cloud Recovery 743
How to manually refresh the view of virtual machines

You are redirected to the Azure portal, the Properties page for the selected virtual
machine.
See “About Instant Cloud Recovery” on page 734.

How to manually refresh the view of virtual

machines
You can manually refresh the view of the virtual machines based on the Subscription
and Recovery Services Vault that you selected during configuration. There is a
frequency at which the virtual machines view is automatically refreshed and the
virtual machines view does not display the most updated status. By default, this
frequency is 10 minutes. If you want to manually refresh the view between the
automatic refresh, you can use this option.
On the Instant Cloud Recovery tab, in the Update Operations group, click Refresh
View.
The virtual machines view is refreshed with the most updated information.
See “About Instant Cloud Recovery” on page 734.

How to enable replication for virtual machines

You can enable replication for virtual machines from the Backup Exec console.
Replication is a continuous backup of your virtual machine in Azure cloud. When
disaster occurs, you can failover to the target virtual machine.
If you have logged on to Microsoft Azure as a Global Administrator, an Owner, or
a User Access Administrator, you can enable replication in Backup Exec.
Refer to the Required permissions section in the Microsoft documentation for more
information:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/
resource-group-create-service-principal-portal
To enable replication in Backup Exec, you must first create replication policies in
the Azure portal. When you prepare the infrastructure for your Recovery Services
Vault, create the replication policies for your virtual machines.
You can enable replication for VMware and Hyper-V virtual machines.
See “About Instant Cloud Recovery” on page 734.
 Instant Cloud Recovery 744
How to enable replication for virtual machines

To enable replication for virtual machines

1 On the Instant Cloud Recovery tab, right-click the virtual machine for which
you want to enable replication and click Enable Replication.
The Enable Replication dialog box is displayed.

Note: You cannot enable replication for a virtual machine that has validation
errors.

2 Select the VMware or Hyper-V parameters.

Virtual VMware and Displays the name of the VMware or Hyper-V virtual
Machine Name Hyper-V machine for which you want to enable replication.

Target VMware and Type the name of the target VMware or Hyper-V virtual
Machine Name Hyper-V machine.

The target machine name must meet the following

requirements:

■ The target machine name cannot be empty.

■ The target machine name length cannot exceed
63 characters.
■ The target machine name must start with a letter
and can contain only letters, numbers, and
hyphens.

Operating Hyper-V Select the operating system of the Hyper-V virtual

System machine. The target virtual machine in Azure cloud is
created with the same operating system.

Process VMware Select the configuration server that does the

Server processing for the target virtual machine during
replication.

Configuration VMware Select the configuration server that manages

Server replication for the target virtual machine.

Run As VMware Select the account that target virtual machine uses.
Account

Replication VMware and Select the replication policy that you want to use for
Policy Hyper-V the VMware or Hyper-V virtual machine.
 Instant Cloud Recovery 745
How to manage replication for virtual machines

Storage VMware and Select the storage account that the target machine will
Account Hyper-V use.

There are two types of storage accounts, Standard

and Premium.

Storage VMware and Select the storage account for replication logs that the
account for Hyper-V target machine will use.
replication
If you select a Premium storage account, you must
logs
select a Standard storage account for replication logs.

This option is grayed out if you select a Standard

storage account. The Standard storage account is
used as the storage account for replication logs.

Virtual VMware and Select the virtual network that the target machine
Network Hyper-V belongs to.

Resource VMware and Select the resource group that the target machine
Group Hyper-V belongs to.

For more information about advanced properties to enable replication for a

virtual machine, go to the Azure portal.
3 Click OK.
The replication parameters or settings that you selected are sent to Azure and
if the parameters are set correctly, a message is displayed. Replication status
for the virtual machine refreshes every 10 minutes. To view more details, select
a virtual machine and click Virtual Machine Details or view the status of the
replication operation in the Protection Status column. After the replication is
complete, the Protection Status displays Protected.
If an incorrect parameter is set, a pop-up message is displayed. You can click
Enable Replication and select the parameters again.
If the replication task fails, Backup Exec displays replication errors for the
specific virtual machine. To view the errors, click View Error Details.
Alternatively, select the virtual machine, click Virtual Machine Details, which
takes you to the Azure portal to view the replication errors.
See “About Instant Cloud Recovery” on page 734.

How to manage replication for virtual machines

You can manage replication for virtual machines of a configured Recovery Services
Vault from the Azure portal.
 Instant Cloud Recovery 746
How to manage failover for a virtual machine

On the Instant Cloud Recovery tab, select the virtual machine and in the Manage
group, click Manage Replication.
You are redirected to the Azure portal, the Replicated items page of the Recovery
Services Vault that you selected in Backup Exec.
You can now manage replication for the virtual machines in this Recovery Services
Vault from the Azure portal.
See “About Instant Cloud Recovery” on page 734.

How to manage failover for a virtual machine

You can only manage failover for a virtual machine that is protected from the Azure
portal.
On the Instant Cloud Recovery tab, do one of the following:
■ Select the virtual machine for which you want to manage failover and in the
Manage group, click Manage Failover.
■ Right-click the virtual machine for which you want to manage failover and click
Manage Failover.
You are redirected to the Azure portal from where you can manage the failover.
See “About Instant Cloud Recovery” on page 734.

How to change the Subscription or Recovery

Services Vault
You can change the Subscription or Recovery Services Vault that you selected
when the Azure resources were configured.
To change the Subscription or Recovery Services Vault
1 On the Instant Cloud Recovery tab, in the Update Operations group, click
Change Subscription Or Vault.
The Configure Azure Resources wizard is displayed.
2 Select any of the following resources that you want to change:
■ Subscription
■ Recovery Services Vault

3 Click Next.
 Instant Cloud Recovery 747
How to prepare a new infrastructure

4 If you selected Subscription, the Azure environment page is displayed. Select

the environment, logon to the Azure portal, and then select the Azure
Subscription that you want to use for the configuration or create a new
Subscription in the Azure portal.
For more information about how to create an Azure Subscription, refer to the
following link:
https://azure.microsoft.com/en-in/free/
If you selected Recovery Services Vault, select the Azure vault that you want
to use for the configuration or create a new vault in Backup Exec and prepare
the infrastructure from the Azure portal.
See “How to configure Azure resources” on page 738.
5 Click Finish.
Backup Exec retrieves information about the vault, the list of virtual machines
based on the subscription and vault, and displays the information on the Backup
Exec console.
See “About Instant Cloud Recovery” on page 734.

How to prepare a new infrastructure

You can prepare new infrastructure in the Azure portal for the Recovery Services
Vault that is created in Backup Exec.
On the Instant Cloud Recovery tab, in the Configure group, click Prepare New
Infrastructure.
You are redirected to the Azure portal, the Site Recovery page. You can now
prepare new infrastructure for the Recovery Services Vault that is created in Backup
Exec or select a different vault.
See “About Instant Cloud Recovery” on page 734.

How to remove a configured Azure resource from

Backup Exec
You can remove the configured Azure resources view from Backup Exec. This
removes the configured Subscription and Recovery Services Vault information from
Backup Exec.
 Instant Cloud Recovery 748
How to renew the Backup Exec certificate

To remove a configured Azure resource

1 On the Instant Cloud Recovery tab, in the Configure group, click Remove
Configuration.
The Microsoft logon dialog box appears. You must log on to the Azure portal
using your credentials.
Ensure that you logon to Microsoft Azure as a user who satisfies the following
criteria:
■ Global administrator for the Active Directory tenant of the Azure subscription
or has the permissions to create apps in the tenant.
■ Owner or User Access Administrator for the Azure subscription.
Refer to the Required permissions section in the Microsoft documentation
for more information:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/
resource-group-create-service-principal-portal
A confirmation message is displayed.
2 Click Yes.
The configured Azure resources are removed from Backup Exec.
See “About Instant Cloud Recovery” on page 734.

How to renew the Backup Exec certificate

The certificate that is generated when Backup Exec is installed is used when you
establish a connection to the Azure portal. The certificate is valid for one year. A
new certificate is automatically generated 6 months after the start date. The older
certificate is still valid for one year.
For example, you installed Backup Exec on 1st January 2018. The validity of the
certificate is up to 31st December 2018. On 1st July 2018, a new certificate is
automatically generated. The new certificate starts from 1st January 2019 to 31st
December 2019. The older certificate is still valid up to 31st December 2018.
When there are 15 days remaining for the certificate to expire, an alert is displayed
on each day for you to renew the certificate.
 Instant Cloud Recovery 749
How to renew the Backup Exec certificate

To renew the certificate

1 On the Instant Cloud Recovery tab, in the Update Operations group, click
Renew Certificate.

Note: Renew Certificate is enabled only 6 months before the certificate expires.

The Microsoft logon dialog box appears.

2 Log on to the Azure portal using your credentials.
The certificate is automatically renewed.
If you do not renew the certificate and the certificate expires after one year, Backup
Exec cannot perform operations in the Azure portal. All options except Renew
Certificate on the Instant Cloud Recovery tab are disabled.
After you renew the certificate, the connection between Backup Exec and Azure is
established and the options on the Instant Cloud Recovery tab are enabled.
See “About Instant Cloud Recovery” on page 734.
 Chapter 18
GDPR Guard
This chapter includes the following topics:

■ About GDPR Guard

■ Backup Exec Management Command Line (BEMCLI) commands for import and
export

■ Supported types of backed up data

■ How to block access to backed up items

■ Restoring blocked items

■ Best practices for blocking access to backed up items with GDPR Guard

About GDPR Guard

An organization may require to block some of the backed-up items for privacy and
compliance reasons, such as General Data Protection Regulation (GDPR). These
items should not be viewed or restored.
Backup Exec provides a way to import the list of items to block. You can use the
GDPR Guard feature to specify the list of backed-up items whose access needs to
be blocked.
An organization can use any tool to create a list of the blocked items. Backup Exec
take this list in the form of a CSV file. The format of the CSV file used for specifying
blocked items information during import is generic and can accommodate any CSV
file generated by different tools.
To import the CSV file containing blocked items into Backup Exec, you must use
the Import-BEItemsToBlock BEMCLI command. You can import CSV files multiple
times into Backup Exec and each CSV can contain blocked items from multiple
servers.
 GDPR Guard 751
About GDPR Guard

You can export the content of all imported files into one CSV file using the
Export-BEItemsBlocked BEMCLI command.

After the blocked items are imported, the restore browse and search view do not
display the blocked items. When you run a restore job, the blocked items are not
available for restore. The blocked items continue to be part of backups and are not
deleted from the backup media.
Backup Exec ensures that information about blocked items is protected using
encryption and all operations that are related to blocked items are recorded in the
audit log for compliance requirements.
When you run a restore job, you can use the Allow restore of blocked items
option to restore blocked items. When you select this option, you must provide a
reason to restore the blocked items and that is recorded in the audit log. Backup
Exec allows only an SLA owner to restore the blocked items.
Following are the key features of GDPR Guard:
■ Blocked items cannot be viewed or restored from the Backup Exec console.
■ Backup Exec ensures integrity and protection of the blocked items data.
■ The file format that is used for blocked files operations (import and export) is
CSV, which is an accepted and easy to use format. A CSV file supports all types
of character encoding.
■ All operations that are related to blocked items are recorded in audit logs and
Windows event log, which can be used for compliance requirements.
■ The imported blocked items on Central Administration Server (CAS) are
auto-synced across all Managed Backup Exec Server (MBES)s that support
blocking of items, ensuring blocking in the CAS-MBES environment without
actually importing blocked items in each MBES.

Note: The import command cannot be run on MBES. The export command can
be run on CAS and MBES.
 GDPR Guard 752
Backup Exec Management Command Line (BEMCLI) commands for import and export

Figure 18-1 Workflow for blocking access to backed up items with GDPR
Guard

See “ Backup Exec Management Command Line (BEMCLI) commands for import
and export” on page 752.
See “Supported types of backed up data” on page 754.
See “How to block access to backed up items” on page 755.
See “Restoring blocked items” on page 756.
See “Best practices for blocking access to backed up items with GDPR Guard”
on page 757.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.

Backup Exec Management Command Line

(BEMCLI) commands for import and export
Blocked items can be specified and viewed using the following BEMCLI commands.
■ Import-BEItemsToBlock

■ Export-BEItemsBlocked
 GDPR Guard 753
Backup Exec Management Command Line (BEMCLI) commands for import and export

For more 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:<Backup Exec install path>\Backup Exec

Import blocked items

The Import-BEItemsToBlock BEMCLI command is used to provide list of blocked
items to Backup Exec. This command requires full path of the CSV file as one of
its parameters.
The CSV file contains information about the items to be blocked, specifically the
server name and the full path. You can use the import command to add new entries
to the existing list of blocked items used by Backup Exec.
The column names in the CSV file are not required to be in a specific order and the
import command can accept a CSV file, which can contain extra columns. This
makes the format of the CSV file generic to accommodate any CSV file generated
by different tools.
In the same operation you can import the blocked items that belong to different
servers and are part of the same CSV.
Every time the import command is run, an entry is logged into the audit log under
the Compliance category and the Windows Event Viewer.

Export blocked items

You can use the Export-BEItemsBlocked BEMCLI command to export information
about all the blocked items that are imported.
Information about the blocked items is exported to a CSV file at a specified location.
This export command requires the location to create the CSV file, as a parameter.
The export command creates a CSV file in the same format as the input CSV file.
Every time the export command is run, an entry is logged into the audit log under
the Compliance category and the Windows Event Viewer.
It is recommended to regularly back up the imported blocked items by running the
export BEMCLI command.

CAS-MBES behavior for import and export commands

Import command behavior:
■ Import command can be run only on CAS and is blocked on MBES.
■ After the import operation on CAS is complete, the blocked items information
along with the encryption key is sent to MBES.
 GDPR Guard 754
Supported types of backed up data

■ If an MBES is offline during the import operation, the blocked items' information
is shared with that MBES after it is online.
■ In case of a rolling upgrade, older MBES does not receive the blocked items.
After MBES is upgraded to the current version of Backup Exec, the blocked
items information is synced with MBES.
■ If a new MBES is added, the encryption key and blocked items information is
synced with the MBES.
■ If there is an update to the blocked items or reset operations, all information
including CSV data is synced with MBES.
The export command runs on both CAS and MBES.
See “About GDPR Guard” on page 750.
See “Supported types of backed up data” on page 754.
See “How to block access to backed up items” on page 755.
See “Restoring blocked items” on page 756.
See “Best practices for blocking access to backed up items with GDPR Guard”
on page 757.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.

Supported types of backed up data

Backup Exec supports the following types of backed up data:
■ File systems that Backup Exec supports. For example, NTFS, Linux.

Note: NDMP file servers are not supported.

■ Windows shares
■ File and folder data of virtual machine backups; both VMware and Hyper-V.
See “About GDPR Guard” on page 750.
See “ Backup Exec Management Command Line (BEMCLI) commands for import
and export” on page 752.
See “How to block access to backed up items” on page 755.
See “Restoring blocked items” on page 756.
 GDPR Guard 755
How to block access to backed up items

See “Best practices for blocking access to backed up items with GDPR Guard”
on page 757.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.

How to block access to backed up items

You can block access to backed-up items from Backup Exec. Backup Exec takes
as input the list of items that need to be blocked from restore. Backup Exec honors
the blocked items during restore and ensures integrity and protection of the blocked
items' information.
Ensure that you have a list of the items that need to be blocked from restore. You
can use any tool to create a list of the blocked items. The list must be in a CSV file
format and contain the item path and server information for every blocked item.
All import and export command-related operations and restore job executions are
recorded in the audit log and Windows Event Log.
The restore job log contains the information that the blocked items are not restored.
The actual file names are not listed.
To block access to backed up items
1 Import the CSV file containing the list of blocked items in Backup Exec using
the Import-BEItemsToBlock BEMCLI command.
You can export this imported list of blocked items to a different location by
using the Export-BEItemsBlocked BEMCLI command. The exported CSV file
is your backup of blocked items.
See “ Backup Exec Management Command Line (BEMCLI) commands for
import and export” on page 752.
2 On the Backup and Restore tab, right-click the server for which you want to
restore data, and then click Restore.
3 Select Files, folders, or volumes, and then click Next.
 GDPR Guard 756
Restoring blocked items

4 Select File and folder backups to a point-in-time, File and folder backups
from a backup set, or Files and folders located through Search.
The list of blocked items that were imported are not available when you select
files and folders. When the blocked items have to be restored, Backup Exec
allows only the SLA owner to restore these items and reason for restore is
recorded in the audit log.
5 Follow the Restore Wizard prompts to restore the data.
See “Restoring file system data” on page 233.
See “About GDPR Guard” on page 750.
See “ Backup Exec Management Command Line (BEMCLI) commands for import
and export” on page 752.
See “Supported types of backed up data” on page 754.
See “Restoring blocked items” on page 756.
See “Best practices for blocking access to backed up items with GDPR Guard”
on page 757.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.

Restoring blocked items

Blocked items, by default are not displayed in restore and search view and cannot
be restored.
In scenarios, when the blocked items have to be restored, Backup Exec permits
only the SLA owner to restore these items and reason for restore is recorded in the
audit log. The audit log records the reason for which the blocked files are restored.
If you want to know the owner of the system logon account, click the Backup Exec
button, and then select Configuration and Settings > Select Logon Accounts
> Manage Logon Accounts. On the Logon Account Management dialog box,
the Owner column displays the owner of the system logon account.
To restore the blocked files
1 Log on as an SLA owner.
2 In the Restore Wizard, select Files, folders, or volumes, and then click Next.
3 Select the Allow restore of blocked items check box.
4 In Restore Blocked Items dialog box, type the reason for restore.
 GDPR Guard 757
Best practices for blocking access to backed up items with GDPR Guard

5 In the Restore Wizard, click Next to view the blocked files in the Restore view.
The restore view lists the blocked items that can be selected for restore.
6 Follow the Restore Wizard prompts to restore the data.
See “About GDPR Guard” on page 750.
See “ Backup Exec Management Command Line (BEMCLI) commands for import
and export” on page 752.
See “How to block access to backed up items” on page 755.
See “Supported types of backed up data” on page 754.
See “Best practices for blocking access to backed up items with GDPR Guard”
on page 757.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.

Best practices for blocking access to backed up

items with GDPR Guard
Review the following best practices before you block access to backed up items:
■ While specifying the blocked item in the CSV file for import, ensure that you use
'*' related wildcards to specify a set of items within a folder. For example,
H:\Folder1\*.txt and E:\*.* can be used for blocked items path in the CSV file to
block all text files under H:\Folder1 or to block all files in the E: directory.
■ For the blocked items that belong to a non-Windows computer, the file path is
case-sensitive. Ensure that you provide a file path with the correct case.
■ Ensure that the server names mentioned for blocked item entry in the CSV file
match with the server name appearing in the Servers list on the Media server
(Backup and restore Tab > Servers Column). If the fully qualified domain
(FQDN) server name is used for a blocked item entry in the CSV file and the
server appears with a different name in the Servers list, ensure that the remote
agent of that server publishes itself on the media server. If the server name
does not match, entries are skipped.
■ Run the export BEMCLI command after the import operation is complete. The
exported file is your backup for all the blocked items that are imported.
■ Enter the reason for restoring blocked items when you create a restore job with
the Allow restore of blocked items option. The reason is recorded in the audit
logs and appears in the audit reports. The reports can be referred for compliance
and audit purposes.
 GDPR Guard 758
Best practices for blocking access to backed up items with GDPR Guard

■ Run the import command again when a media is moved to a new media server
and this media has backup sets that contain blocked items. If you do not run
the import command again, the blocked items will be available for restore.
■ In a CASO environment, run CAS and all MBES with Backup Exec 20.3 or later
version for items to be blocked across all media servers. When you run the
import command on the CAS server, the information is automatically synced on
the MBES server.
■ Run the audit log report regularly to keep a record of all the operations related
to blocked items.
■ Ensure that the CSV used for specifying blocked items during import operation
is with one of the following character encodings:
■ Locale encoding which corresponds to the ANSI and the OEM code pages.
■ UTF-8 with Byte-Order-Mark (BOM).
■ UTF-16 Little-Endian with BOM.
■ UTF-16 Big-Endian with BOM.
The import command does not function properly if the input CSV file contains
strings from multiple locales.
■ If you are restoring a virtual machine or doing a local restore of your computer
using Simplified Disaster Recovery, ensure that you delete the blocked items
manually or using a post-processing script once the restore is complete.
Otherwise, blocked items are restored in such cases.
See “About GDPR Guard” on page 750.
See “ Backup Exec Management Command Line (BEMCLI) commands for import
and export” on page 752.
See “Supported types of backed up data” on page 754.
See “How to block access to backed up items” on page 755.
See “Restoring blocked items” on page 756.
See “Troubleshooting blocked access to backed up items with GDPR Guard”
on page 775.
 Chapter 19
Troubleshooting Backup
Exec
This chapter includes the following topics:

■ Troubleshooting hardware-related issues in Backup Exec

■ Troubleshooting robotic libraries and tape drives

■ How to get more information about alerts and error messages

■ Troubleshooting backup issues in Backup Exec

■ Troubleshooting failed components in the SAN

■ Troubleshooting installation issues in Backup Exec

■ Troubleshooting blocked access to backed up items with GDPR Guard

■ Troubleshooting Instant Cloud Recovery issues in Backup Exec

■ How to improve Backup Exec's performance

■ Accessing Veritas Online

■ Searching the Veritas Knowledge Base

■ Contacting Backup Exec Technical Support

■ Using Remote Assistance

■ Managing your Backup Exec support cases

■ About Backup Exec diagnostic tools

■ Running the Veritas QuickAssist Help Tool

 Troubleshooting Backup Exec 760
Troubleshooting hardware-related issues in Backup Exec

■ Generating a diagnostic file for troubleshooting Backup Exec

■ Running the begather utility to troubleshoot Backup Exec components on Linux

servers

■ Using the Backup Exec Debug Monitor for troubleshooting

■ About the Backup Exec debug tool

Troubleshooting hardware-related issues in

Backup Exec
For common hardware-related issues, review the following frequently asked
questions:

Table 19-1 Hardware-related questions

Question Answer

How do I know if You can find a list of compatible devices at the Backup Exec Hardware
my storage Compatibility List.
device is
If your drive is listed on the hardware compatibility list, run the Configure
supported?
Storage wizard and install device drivers.

See “Installing tape device drivers ” on page 382.

From the Configure Storage wizard, the Device Driver Installation Wizard
finds and installs the most suitable driver for your tape drive.

How can I The following sections provide tips for troubleshooting and configuring
troubleshoot tape device and robotic library hardware:
issues with a
See “Troubleshooting robotic libraries and tape drives” on page 762.
robotic library or
tape drive? See “Starting and stopping Backup Exec services” on page 667.

See “Deleting a storage device” on page 468.

 Troubleshooting Backup Exec 761
Troubleshooting hardware-related issues in Backup Exec

Table 19-1 Hardware-related questions (continued)

Question Answer

I’m getting an Many factors can cause the cyclic redundancy check (CRC) error.
error "Storage The following list contains the most common reasons for this error and
device [device] potential ways to resolve the problem:
reported an error
on a request to ■ Contaminated read and write heads of the tape device.
read or write data Check with the hardware manufacturer for proper cleaning techniques.
to or from media. ■ Bad media.
Error reported: Replace the media. Try a new tape that the hardware manufacturer
Data error (cyclic has certified.
redundancy ■ Tape driver.
check)." What Load the appropriate Backup Exec tape driver.
should I do? You can find a list of compatible devices in the Backup Exec Hardware
Compatibility List.
■ Wide negotiation for the SCSI controller is not configured properly.
If the device is a wide (68 pin) SCSI device, then wide negotiation
may and should be used. If the device is a narrow (50 pin) SCSI
device, disable wide negotiation. Use the manufacturer's SCSI
installation program to disable wide negotiation on the SCSI controller
card.
■ SCSI controller transfer rate is too fast.
Use the manufacturer's SCSI installation program to lower the SCSI
transfer rate. Check with the manufacturer of the controller and the
device for the proper configuration for the SCSI transfer rate.
■ SCSI controller synchronous negotiation enabled.
Use the manufacturer's SCSI installation program to disable
synchronous negotiation on the SCSI controller card. Check with the
manufacturer of the controller and the device for the proper
configuration for SCSI synchronous negotiation.
■ Incorrect termination or bad cables.
Verify that the SCSI cable is good and that it is configured to provide
proper SCSI termination. Do not mix passive and active termination.
■ Confirm that the tape drive functions properly.
Check with the tape drive manufacturer for diagnostic software to test
the condition of the tape drive hardware.
■ General SCSI problems.
Isolate the tape drive on its own controller card or try a different SCSI
card.
 Troubleshooting Backup Exec 762
Troubleshooting robotic libraries and tape drives

Table 19-1 Hardware-related questions (continued)

Question Answer

Why does my The DLT tape drive maintains internal information about the tape on a
DLT tape drive tape directory track. The directory track is updated before the tape is
pause when it ejected from the drive. If the drive is turned off without ejecting the tape
catalogs some first, this information is lost.
tapes?
Re-generating the tape directory information takes several hours to
complete, which makes it seem like the drive is hung. Allow sufficient
time for the operation to complete and then eject the tape. Normal
operation resumes after the directory track is updated.

A backup to my The backup most likely fails to complete because the storage option
DLT tape drive is Eject the media after job completes is selected, and the tape drive
stuck at 99% does not support the operation. Some tape drives require you to manually
complete. What remove the tape, such as Digital Linear Tape (DLT), Linear Tape-Open
should I do? (LTO), Travon, and Onstream drives.

To remedy this situation, either uncheck the storage option Eject the
media after job completes, or configure an automatic response to the
active alert.

See “Configuring network options for backup jobs” on page 198.

Troubleshooting robotic libraries and tape drives

This section contains troubleshooting strategies that can help resolve issues with
robotic libraries and tape drives. For best results, perform these in order.
Several of these troubleshooting strategies use the Veritas QuickAssist (VQA) tool.
First, verify that the operating system detects the device. Repeat this process
whenever Backup Exec loses the ability to manage external tape hardware. If your
tape hardware is in a storage area network (SAN), you may need to cycle the SAN
power switch to recognize the device. We recommend plugging the tape hardware
into a backup power supply that provides surge protection.
Ensure that you have installed the latest firmware for the tape device, robotic library,
and host bus adapter. Contact the hardware manufacturer for the latest firmware
for the tape drive or robotic library, and for the latest firmware and device drivers
for the host bus adapter.
Verify that your license and your installed features support the number of drives
you need to use. Depending on your Backup Exec edition and license, you may
need to purchase support for additional tape drives in robotic libraries, or upgrade
to another edition. See the Backup Exec licensing documentation for more
information.
 Troubleshooting Backup Exec 763
Troubleshooting robotic libraries and tape drives

Refer to the Backup Exec hardware compatibility list

1. The hardware compatibility list (HCL) can help you verify that Backup Exec
supports your devices, inquiry strings, and connection methods. Refer to the
HCL to confirm that the device is officially supported by Backup Exec.
2. Refer to the HCL to confirm that the inquiry string for the device matches the
string in the HCL.
3. Refer to the HCL to confirm that the connection method that is used to connect
the device to the server is supported. Many devices support multiple connection
methods. These devices are listed more than once in the HCL. Some connection
methods may work for a particular device, but might not be listed in the HCL.
If a method is not listed in the HCL, it is not officially supported.

Verify admin rights for the Backup Exec service account

1. Verify that the Backup Exec service account is a Domain administrator account
or a built-in administrator account.
You can use the VQA tool for this procedure.
■ For Backup Exec 2012 and later, click on the Backup Exec button, then on
Configuration and Settings, then Backup Exec Services.
■ For Backup Exec 2010, on the Backup Exec Tools menu, click Backup
Exec Services, then on Services Credentials.

2. Verify that the account has the following basic rights and permissions:
■ Act as part of the operating system
■ Backup files and directories
■ Create a token object
■ Log on as a batch job
■ Log on as a service
■ Manage auditing and security log
■ Restore files and directories
■ Take ownership of files and other objects

Stop and disable the Removal Storage service

1. This procedure only applies to Windows Server 2003/XP. In Windows, click
Start, then Control Panel, then Administrative Tools, and double-click on
Services.
You can use the VQA tool for this procedure.
 Troubleshooting Backup Exec 764
Troubleshooting robotic libraries and tape drives

2. Click Removal Storage Service, then click on Stop and Disable. If a Removal
Storage service error appears, disregard it. The error should not occur again
after you restart the server.
3. Restart the server.

Review system event logs for hardware errors

1. In Windows, right-click on My Computer, then on Manage.
2. Expand Computer Management > System Tools > Event Viewer, then click
on System. On some versions of Windows, the path is Computer Management
> System Tools > Event Viewer > Windows Logs > System.
3. Look for any hardware errors in the logs.

Ensure that you have installed the latest device drivers for the tape device
1. Note: Backup Exec has only been tested for performance and compatibility
with the drivers that are listed on the hardware compatibility list.

If you have installed the latest version of Backup Exec, you should already
have the latest drivers. If your drivers are out of date, click Backup Exec tape
device drivers > Drivers for a list of tape device drivers available for download.
2. Use Tapeinst.exe to install the tape device driver. This program is copied to
your hard disk when you install Backup Exec.
3. Navigate to the Windows Device Manager to verify that the tape device drives
were installed for the tape drive.
■ For Windows 2008: Right-click on Computer > Manage, expand Server
Manager > Diagnostics, then select Device Manager.
■ For Windows 2003: Right-click on My Computer > Manager, expand
Computer Management, then select Device Manager.

4. In the Device Manager, locate the tape driver, and right-click on Properties.
5. Click the Driver tab and verify that the driver provider is Veritas.

Uninstall any third-party applications that control the tape device

1. Backup Exec may not be able to communicate properly with tape devices if
another vendor's backup application is installed. This can happen even if the
services for that application are disabled. Click Start > Control Panel >
Add/Remove Programs.
 Troubleshooting Backup Exec 765
Troubleshooting robotic libraries and tape drives

Note: Do not uninstall tape diagnostic tools when Backup Exec services are
running. Remove tape diagnostic tools after the diagnostic tests are complete.

2. Select the third-party application or tool, and click Uninstall.

3. Repeat the uninstallation process for all third-party applications or tools which
prevent Backup Exec from communicating properly.

Ensure that Microsoft default drivers are installed for a medium changer
1. This procedure pertains to robotic library devices only. Navigate to the Windows
Device Manager using one of the following methods:
■ In Windows 2008: Right-click on Computer, then click Manage. Expand
Server Manager > Diagnostics, then select Device Manager.
■ In Windows 2003: Right-click on My Computer, then click Manager. Expand
Computer Management, then select Device Manager.

2. Expand Medium Changer, and ensure that Unknown Medium Changer is

listed. If Unknown Medium Changer is listed, the default Microsoft drivers
are installed.
3. If OEM drivers are installed, right-click the OEM driver, then click on Properties
> Update driver. Updating the driver installs the Microsoft driver and causes
Unknown Medium Changer to be displayed.

Use the Discover tool to troubleshoot hardware errors or reservation conflicts

1. The Discover tool displays detailed attributes of any backup devices that are
attached to the server. To begin, stop the Backup Exec services.
2. Navigate to the Backup Exec installation directory.
3. To run the tool and create a text output, run the following command at a
command prompt: Discover.exe > C:\discover.txt

Use tracer.exe to troubleshoot SCSI issues

1. Begin by verifying that the SCSI changer service is running. Click Start. In the
search box, type msinfo32 and press Enter.
You can use the VQA tool for this procedure.
2. In the System Information dialog, expand Software Environment, and then
click System Drivers.
3. Locate the SCSIChanger device, and verify that its Status is set to Running.
4. After you have verified that the SCSI changer service is running, stop the
Backup Exec services.
 Troubleshooting Backup Exec 766
Troubleshooting robotic libraries and tape drives

5. Navigate to your Backup Exec directory, and launch tracer.exe. The tracer
program begins capturing SCSI information.
6. Restart the Backup Exec Services. To restart the services, launch
Servicesmgr.exe from the Backup Exec directory.

7. After the services start, review the tracer log for any hardware errors or
reservation conflicts.

Detect and uninstall any orphaned devices

1. Orphaned devices may be present in Device Manager after you replace
hardware, or perform firmware and driver updates. To begin, open the Windows
Device Manager using a command prompt by running the following commands
at the command line:
C:\cd WINDOWS

C:\WINDOWS>cd system32

C:\WINDOWS\system32>devmgmt.msc

C:\WINDOWS\system32>

2. In the Device Manager, click the View menu, then select Show Hidden
Devices. This option shows all device drivers, including those that are not
currently installed and running on the computer.
3. Expand the following devices. For any of these devices that are not shown in
bold, right-click them and click Uninstall:
■ Medium changer
■ Tape drives
■ SCSI cards
Devices that are not bold are not loaded and can be uninstalled.

Warning: Removing devices and drivers that are still required by the system
may result in the system becoming unstable and unable to start.

Disable, delete, and turn on the device in Backup Exec

1. In the Backup Exec console, go to Devices/Storage tab.
2. Right-click the device, and then select Disable.
For Backup Exec 2010 and earlier, deselect Enable. When the check box for
this option is clear, the device is disabled.
 Troubleshooting Backup Exec 767
How to get more information about alerts and error messages

3. Right-click the device, and then select Delete. A prompt to move the backup
jobs to other devices or device pools may appear. For Backup Exec 2012, this
prompt appears as Retarget Jobs.
4. Note the jobs that are affected and move the jobs back to the original device
after resolving the issue with the device.
5. Stop the Backup Exec services.
6. Navigate to the Backup Exec directory and run Tapeinst.exe.
7. In the Backup Exec Device Driver Installed dialog, select the following
options:
■ Use tape drivers for all supported tape devices
■ Delete entries for tape devices that are unavailable, removed, or turned
off
■ Use Plug-and-Play drivers for Windows 2000 and later

8. Restart the Backup Exec services.

How to get more information about alerts and

error messages
Backup Exec generates an error message when a condition occurs that is important
enough to warrant your attention, or requires that you submit a response. Most
alerts and error messages are self explanatory, but there may be times when you
need to get more information to resolve a condition.
You can get more information on Backup Exec alert and error messages in the
following ways:
■ On the alert message, click the link for more information, or look in the job log
and click the UMI link. This code is a hyperlink to the Veritas Technical Support
website. You can access the technical notes that are related to the alert.
See “Linking from the job log to the Veritas Technical Support website”
on page 270.
■ Search the Veritas Technical Support knowledge base for the error.
See “Searching the Veritas Knowledge Base” on page 778.

Troubleshooting backup issues in Backup Exec

If you have problems with backing up data, review the following questions.
 Troubleshooting Backup Exec 768
Troubleshooting backup issues in Backup Exec

Table 19-2 Backup questions

Question Answer

I am unable to back up For non-snapshot backups, when Backup Exec encounters a

certain files on my system file that is in use by another process, it either skips the file or
that are in use by other waits for the file to become available. These actions depend
processes. Why is that? on the options for no-snapshot backups that you configure
when you create the backup.

See “Configuring file and folder options for backup jobs”

on page 581.

If you configure Backup Exec to back up open files with a lock,

it attempts to open the files in a different mode. It locks these
files during backup to prevent other processes from writing to
them. It is recommended that you close the applications that
leave files open so that the files are backed up in a consistent
state.

To back up open files on Windows computers, use the

Advanced Open File options to configure the backups that use
snapshot technology.

See “Configuring Advanced Open File options for backup jobs”

on page 572.

Why does the Backup Exec Backup Exec is a client/server application that must always be
Administration Console available to process the jobs that are submitted from both local
continue to own a storage and remote administrative consoles.
device even when it's not
The Backup Exec services claim all of the storage devices that
running?
are attached to the Backup Exec server whenever the services
are running. Backup Exec requires constant control of the
storage devices to collect statistics on media and storage
device usage, and to provide media overwrite protection when
necessary.
 Troubleshooting Backup Exec 769
Troubleshooting backup issues in Backup Exec

Table 19-2 Backup questions (continued)

Question Answer

When I run a local backup, The type of partition for which the system is formatted may
the total number of bytes cause this problem.
backed up by Backup Exec
If you have a Windows NTFS compressed partition, Backup
does not match the number
Exec displays the uncompressed byte count of the files that
of bytes displayed by
are backed up. Meanwhile, Windows Explorer displays the
Windows. Why?
compressed byte count of the files on the hard drive. For
example, Windows compresses an NTFS partition that contains
1 GB of data to 500 MB. Backup Exec reports that 1 GB of
data was backed up, even though Windows Explorer displays
that only 500 MB of compressed data exists on the hard drive

If you have a FAT partition, Backup Exec reports the actual

number of bytes of the files being backed up while File Manager
reports an inflated amount of disk space. For example, a 2 GB
FAT partition has a 32-K cluster size and File Manager displays
1.9 GB of used space. Backup Exec reports that 1.4 GB of
data was backed up. Assuming that a 50-MB pagefile.sys is
excluded from the backup, there is a 450-MB difference in the
number of bytes.

Converting to NTFS regains disk space since it is more efficient

and the default cluster size (automatically set by Windows) in
NTFS is less than FAT. Windows lets you specify a cluster
size other than the default; however system performance may
decrease. For more information, see the Windows
documentation.

How can I change my You can refresh a database encryption key at any time. Refer
existing database to the following topic for more information about refreshing
encryption key if I feel it has database encryption keys.
been compromised or to
See “Refreshing Backup Exec Database encryption keys”
comply with company
on page 603.
policies?
 Troubleshooting Backup Exec 770
Troubleshooting failed components in the SAN

Table 19-2 Backup questions (continued)

Question Answer

Why do I experience slow Local disk drives on the Backup Exec server can usually be
throughput when I back up backed up at a faster speed than backing up remote servers
remote disks? across a network.
The backup speed for a remote disk is limited by the speed of
the physical connection. The rate at which a remote server's
hard disks are able to be backed up depends on the following
items:

■ The make/model of network cards.

■ The mode/frame type configuration for the adapter.
■ The connectivity equipment (hubs, switches, routers, and
so on).
■ The Windows settings.

Troubleshooting failed components in the SAN

Various problems can occur at any location in a SAN.
For Backup Exec to work properly, a storage device has to be recognized in the
following locations:
■ The bridge or router must recognize it as a SCSI device
■ The operating system must recognize it as a device
■ Backup Exec must recognize it as a supported device
In some cases, hardware issues may require you to contact your hardware vendor
for technical support.
You may need to replace a component of your SAN, such as a bridge or a switch.
For specific steps for replacing your equipment, refer to your hardware vendor’s
documentation.
See “Troubleshooting offline storage devices in a SAN ” on page 770.

Troubleshooting offline storage devices in a SAN

If a device in your SAN has gone offline, follow these steps to determine the source
of the problem.
Before you begin troubleshooting, verify that your storage devices are on the Backup
Exec supported device list.
 Troubleshooting Backup Exec 771
Troubleshooting failed components in the SAN

You can find a list of compatible operating systems, platforms, and applications in
the Backup Exec Software Compatibility List.
Also, verify that all hardware drivers are up to date and are started. If you find errors
with your hardware, contact your hardware vendor for specific instructions.

Table 19-3 Troubleshooting offline storage devices in a SAN

Step Action

Step 1 Use the Windows Device Manager to verify

that the operating system recognizes the
device.

If the device is not recognized, you may need

to troubleshoot the device.

See “Finding hardware errors in a SAN”

on page 772.

Step 2 For robotic libraries, verify that robotic library

support is installed.

Step 3 Check the system event log for the following

errors, which indicate SAN communication
errors: SCSI errors 9, 11, and 15, or timeout
errors relating to storage. Check the
application event log for multiple events
33152. These events indicate SAN
communication errors.

See “Finding hardware errors in a SAN”

on page 772.

You may need to contact your hardware

vendor.

Step 4 If the library is online, but some or all of the

drives are offline, use Backup Exec to
initialize the library.

See “Initializing a robotic library” on page 474.

Step 5 If initializing the library does not bring the

storage devices online, check the library for
an error display on the front panel,
mechanical problems, or tapes inappropriately
in the drives. Correct any errors that you find.
 Troubleshooting Backup Exec 772
Troubleshooting failed components in the SAN

Table 19-3 Troubleshooting offline storage devices in a SAN (continued)

Step Action

Step 6 If no errors exist on the library or if you

corrected the errors and the storage devices
are still offline, stop Backup Exec services
and then restart.

See “Starting and stopping Backup Exec

services” on page 667.

Step 7 If restarting the services does not bring the

storage devices online, restart the operating
system. Be sure that no Backup Exec jobs
are running when you restart.

Step 8 If restarting the operating system does not

bring the storage devices online, reset the
SAN to help identify problem tape storage.
Recycling the SAN may also resolve Fibre
Channel problems.

See “Resetting the SAN” on page 773.

Finding hardware errors in a SAN

Use the following steps to find the common hardware errors that occur in a SAN.
If you find errors with your hardware, contact your hardware vendor for specific
instructions.

Table 19-4 Finding hardware errors in a SAN

Step Action

Step 1 Verify that the proper device drivers are

installed.

Step 2 Verify that the fibre cable is securely

connected to the HBA and to the fibre switch.

Step 3 Verify that the fibre connection is properly

connected to the robotic library from the fibre
switch.
 Troubleshooting Backup Exec 773
Troubleshooting failed components in the SAN

Table 19-4 Finding hardware errors in a SAN (continued)

Step Action

Step 4 Check for a failed hardware component

between the server and the fibre switch.
Sometimes some of the servers in the SAN
recognize the storage device, but other
servers do not. If none of the servers in the
SAN recognize the storage device, check for
a failed hardware component between the
fibre switch and the storage device.

Step 5 Reset the SAN, which may identify problem

hardware components and may resolve fibre
problems.

See “Resetting the SAN” on page 773.

Resetting the SAN

Resetting the SAN involves turning off the components of the SAN, and then
powering them on in a specific order.

Table 19-5 Resetting the SAN

Step Action

Step 1 Turn off all servers, robotic libraries, and fibre

bridges in the SAN.

In rare cases, you may need to turn off the

fibre switch also. If you need to turn off the
switch, you should power it on before any
other components. Wait for all checks to
complete before you turn on the other
components.

Step 2 Turn on the robotic library.

See “Initializing a robotic library” on page 474.

Step 3 Verify that the fibre switch recognizes the

robotic library.

Step 4 Turn on the central administration server.

Step 5 Verify that the operating system recognizes

the robotic library and its drives.
 Troubleshooting Backup Exec 774
Troubleshooting installation issues in Backup Exec

Table 19-5 Resetting the SAN (continued)

Step Action

Step 6 Turn on one of the managed Backup Exec

servers. Wait for the managed Backup Exec
server to start before you turn on the other
managed Backup Exec servers.

Bringing storage devices online after an unsafe device removal event

in a SAN
If a storage device is in use by Backup Exec at the time of an unsafe device removal
event, the device appears as offline in Backup Exec.

Table 19-6 How to bring a device online after an unsafe device removal event

Step Action

Step 1 Verify that no Backup Exec jobs are running

in the SAN.

Step 2 Use Backup Exec to initialize the robotic

library if the library is online but the drives are
offline.

See “Initializing a robotic library” on page 474.

Step 3 Stop all Backup Exec services and then

restart them if the library is offline or if the
drives are offline after initialization.

If the device is not online, you may need to

troubleshoot the device.

See “Finding hardware errors in a SAN”

on page 772.

Troubleshooting installation issues in Backup

Exec
If you have problems with .NET installation review the following points.
■ If the .NET 4.8 installation fails, try to install it manually before you retry
installation of Backup Exec. This helps to isolate any issues from Backup Exec
such as, issues with Microsoft's .NET installer or any environmental issues.
 Troubleshooting Backup Exec 775
Troubleshooting blocked access to backed up items with GDPR Guard

■ The BKUPINST21.htm file logs any errors that occur during the .NET installation.
However, detailed logs are available in .Net 4.8 setup logs, which are available
at %temp% folder and the file name are Microsoft .NET Framework 4.8
Setup_*.html, Microsoft .NET Framework 4.8 Setup_*.txt, and
dd_ndp48-x86-x64-allos-enu_decompression_log.txt.

Troubleshooting blocked access to backed up

items with GDPR Guard
If you have problems with blocking access to backed up items with GDPR Guard,
review the following points.
■ If the import command is successful but the restore and search view continue
to display and restore the blocked items, check the following:
■ Check if the full path of any blocked item entry in the CSV file that was
specified during import contains a comma (,). If the file name or any of the
folders in the path contain a comma, the entry is not imported properly. For
example: E:\Folder,Delimited\file.txt and E:\F1\ab,a.txt are unsupported
entries for blocked items.
■ Some entries may get blocked if the full path of a blocked item's entry
contains a wildcard within a folder that is also applicable to the items of that
folder and its subfolders. For example: E:\F1\a*.txt blocks all text files starting
with letter 'a' inside the E:\F1 folder and inside the E:\F1\F2 folder. To ensure
that the item within a subfolder is not blocked, you must add each entry
separately and not use wildcards in this scenario.
■ If the same server is added in Backup Exec using multiple names, such as
by the NetBIOS name, FQDN, or IP address, the items are blocked only for
the server name that is specified in the blocked item entry in the CSV. To
resolve this issue, add the blocked item entries via each of the server names
separately in the input CSV for the import operation.

■ If some blocked items are skipped during the import operation with the reason
displayed as invalid item path, check the following:
■ The full path for the skipped item does not start with the volume or share
name and starts with server name. For example: E:\folder1\a.txt and
TestShare\F1\b.txt are acceptable entries in the full path.
■ Only the file name in the item path contains '*' related wildcards. If the folder
path contains the wildcard, the entry is skipped. For example:
G:\Test2\*\CatTrans.xsl and G:\*\results.txt are invalid entries.
 Troubleshooting Backup Exec 776
Troubleshooting blocked access to backed up items with GDPR Guard

■ If Import operations terminate with the following error: “An error occurred while
processing a blocked item. The internal list of blocked items does not exist”.
Check whether the input CSV file path is correct and does not point to an invalid
drive or network location.
■ If the export operation terminates with the following error: “An error occurred
while opening the internal list of blocked items”.
Ensure that the specified output folder path is valid and does not point to an
invalid drive or network location..
■ If some of the blocked items are displayed in the restore or search view that
may be due to the following reasons:
■ An import operation is running for the CSV file containing some blocked
items of the same resource.
■ The integrity check failed for the internal list of blocked items for that resource
or some problem occurred while reading from the internal list of blocked files
for the restore or search view.
If you run the restore job, the restore job log displays the exact reason of the
failure in reading from the internal list of blocked files.
■ If a soft or hard link path is specified in the CSV, only the link is blocked. To
block the folder that the link is pointing to, specify the actual path of the folder
in the CSV.
■ If you want to remove a blocked file entry from an already imported CSV file,
do the following in the order listed:
■ Run the export command.
■ Remove the entry from the generated CSV.
■ Delete the internal file containing the list of blocked items for the resource
whose entry is removed. Remove the internal file from te following location:
"data\BLFileInfo" folder under the Backup Exec installation directory.
■ Run the import command again with the ResetifCorrupted parameter.
Import-BEItemsToBlock - RESETifCorrupted - CsvFilePath <CVS
file path> - ColumnNameForServerName <Name of 1st column> -
ColumnNameForBlockedItemPath <Name of 2nd column>

■ If the restore and search view does not display results for a long time it can be
because a large number of blocked items are added for that resource. In such
a scenario, restore job can still be run at the folder or volume level to view the
items that are restored and viewed.
■ If a standalone media server that has blocked items needs to be converted into
an MBES server, perform the following steps in the order listed:
 Troubleshooting Backup Exec 777
Troubleshooting Instant Cloud Recovery issues in Backup Exec

■ Export the blocked items file.

■ Delete the bin files from the Data\BLFileInfo folder under the Backup Exec
installation folder.
■ Convert the standalone server to an MBES server.
■ Import the blocked items on CAS using the exported file that you created.

See “About GDPR Guard” on page 750.

Troubleshooting Instant Cloud Recovery issues

in Backup Exec
If you have problems with Instant Cloud Recovery feature in Backup Exec, review
the following points.
■ If there is failure when you connect to Azure Site Recovery (Azure portal) for
the first time, ensure that the basic requirements for Internet explorer are met.
Refer to the following link to see a list of supported browsers:
https://docs.microsoft.com/en-us/azure/azure-preview-portal-supported-browsers-devices
Ensure that the portal is accessible from the browser before working on any
connectivity issues.
■ Ensure that the system clock is in sync with the internet time. Any difference
causes Certificate Errors when connecting to Azure Site Recovery.

How to improve Backup Exec's performance

To get the best performance from Backup Exec, you should review several factors:
■ Data transfer path
■ Backup Exec agent performance
■ Network performance
■ Backup Exec server performance
■ Storage device performance
For more information on how to measure and tune the performance of these items,
see the following sections:
See “Improving backup performance in Backup Exec” on page 138.
See “Troubleshooting backup performance” on page 141.
 Troubleshooting Backup Exec 778
Accessing Veritas Online

Accessing Veritas Online

You can access Veritas community forums, learn about training courses, and view
Veritas websites

Table 19-7 Veritas Online menu items

Item Description

Share Your Ideas Connects you to the Veritas Connect forum

where you can post your ideas for improving
Backup Exec.

Education Services Provides the links to all Veritas Education

training and custom learning services.

Backup Exec Tech Center Provides the links to Backup Exec self-paced
training modules.

Backup Exec Page Provides the links to resources for Backup

Exec.

Veritas Home Page Connects you to the Veritas website.

To access Veritas Online

◆ Click the Backup Exec button, select Veritas Online, and then select the
appropriate menu item.
See “Searching the Veritas Knowledge Base” on page 778.

Searching the Veritas Knowledge Base

The Veritas Knowledge Base is a centralized location where you can find more
information about Veritas products. The knowledge base contains information about
how to install, upgrade, configure, and use Veritas products. It also contains
information about requirements, best practices, and how to troubleshoot problems.
The Veritas Knowledge Base is accessible from within Backup Exec.

Note: You must have an active Internet connection to access the Veritas Knowledge
Base.

The knowledge base uses a keyword-based search technology. It focuses on the

important keywords in a search and compares them to other search phrases to
provide the best possible results. You can use Boolean search features and
 Troubleshooting Backup Exec 779
Contacting Backup Exec Technical Support

expression queries to provide search parameters. For best results, focus on a few
keywords that best represent your question.
When you search the knowledge base, a new browser window launches and displays
the search results.
To search the Veritas Knowledge Base
1 Do either of the following:
■ Click the Backup Exec button, select Technical Support, and then select
Search Knowledge Base.
■ On the Home tab, in the Support group, ensure that Technical Support
is checked. Then, in the Technical Support panel, click Veritas Technical
Support.

2 Enter a keyword or phrase, and then click the search icon.

Contacting Backup Exec Technical Support

If you have tried to solve a problem, but still need a resolution, you can contact
Veritas Technical Support for Backup Exec over the Internet or by phone.
To expedite the Technical Support process, do the following:
■ Know your Backup Exec version and revision number.
■ Use one of the diagnostic utilities that are included with Backup Exec to collect
the information that technical support can use to diagnose your issue.
To contact Backup Exec Technical Support
◆ Click the Backup Exec button, select Technical Support, and then select
Backup Exec Technical Support.
See “Displaying the version information for Backup Exec” on page 118.
See “About Backup Exec diagnostic tools” on page 780.
See “Accessing Veritas Online” on page 778.

Using Remote Assistance

Remote Assistance launches a WebEx session on the Internet, which lets you join
a support session or start a support session.
To use Remote Assistance
◆ Click the Backup Exec button, select Technical Support, and then select
Remote Assistance.
 Troubleshooting Backup Exec 780
Managing your Backup Exec support cases

Managing your Backup Exec support cases

From Backup Exec, you can launch the MyVeritas website, where you can create,
review, and manage cases related to technical product support.
To manage your Backup Exec support cases
◆ Click the Backup Exec button, select Technical Support, and then select
Manage Support Cases.

About Backup Exec diagnostic tools

The following diagnostic tools help to troubleshoot issues in Backup Exec:

Table 19-8 Backup Exec diagnostic tools

Item Description

Veritas QuickAssist (VQA) Help Tool Scans the local computer and generates a
report about common issues in your Backup
Exec environment.

See “Running the Veritas QuickAssist Help

Tool ” on page 781.

Backup Exec diagnostic application Gathers the pertinent information about a

Windows computer for troubleshooting.

See “Generating a diagnostic file for

troubleshooting Backup Exec” on page 781.

Gather utility for Linux servers Creates and compiles a Packet file. The file
contains detailed information about
installation, diagnostics, and error reports.

See “Running the begather utility to

troubleshoot Backup Exec components on
Linux servers” on page 785.

Backup Exec Debug Monitor Captures the debug output from Backup Exec
and saves it into debug logs.
See “Using the Backup Exec Debug Monitor
for troubleshooting” on page 786.
 Troubleshooting Backup Exec 781
Running the Veritas QuickAssist Help Tool

Running the Veritas QuickAssist Help Tool

The Veritas QuickAssist help tool is a multi-product diagnostic utility that identifies
common issues, gathers data for support-assisted troubleshooting, and provides
links to other customer self-help and support resources. To perform checks on the
local computer, Veritas QuickAssist gathers information from the local computer
and then analyzes it. Veritas QuickAssist does not permanently alter any files on
the computer unless you select the option when you run the tool. Veritas QuickAssist
does not permanently install anything on your computer when it runs.
To run the Veritas QuickAssist Help Tool
1 Click the Backup Exec button, select Technical Support, and then select
Quick Assist.
2 Follow the on-screen prompts.

Generating a diagnostic file for troubleshooting

Backup Exec
Backup Exec includes a diagnostic application (Bediag.exe) that gathers information
about a Windows computer for troubleshooting purposes. This application can be
run from within Backup Exec or it can be run from a command line. This application
can be run for a local server or a remote server. You can run diagnostics on a
remote Backup Exec server if Backup Exec is installed on the remote server and
the Backup Exec services are running.
The Bediag application collects the following types of information:
■ Account groups, account privileges, and environment settings.
■ Backup Exec software version and registry information, Backup Exec agent
listing, Windows version information, SCSI hardware configuration, SQL Server
information, Driver services information, and Windows Services information.
■ Server information, supported shared directories, and Windows sockets
information.
To generate a diagnostic file from within Backup Exec
1 Click the Backup Exec button, select Technical Support, and then select
Backup Exec Diagnostics.
2 Select the server from the drop-down list.
If the server that you want to select is not in the drop-down list, click Browse
to select it from a list of available servers.
3 Enter the logon information for the server that you selected.
 Troubleshooting Backup Exec 782
Generating a diagnostic file for troubleshooting Backup Exec

4 Click Run Diagnostics.

5 Click Close.
6 Open the "Bediag.txt"from the directory that contains Bediag.exe (by default
<Backup Exec install path>\Backup Exec).

To generate a diagnostic file from a command line

1 Launch the command prompt.
2 Do one of the following:

To generate a diagnostic file for a Backup From the directory <Backup Exec
Exec server install path>\Backup Exec\, type
bediag [switches] servername .

See “Command line switches for a

diagnostic file” on page 782.

To generate a diagnostic file for a remote From the directory <Backup Exec
computer install path>\Backup Exec\, type
bediag [switches] workstationname.

See “Command line switches for a

diagnostic file” on page 782.

3 Open the "Bediag.txt"from the directory that contains Bediag.exe (by default
<Backup Exec install path>\Backup Exec).

Command line switches for a diagnostic file

You can add the following switches to gather additional information when you
generate a diagnostic file for troubleshooting.
See “Generating a diagnostic file for troubleshooting Backup Exec” on page 781.

Table 19-9 Command line switches for a diagnostic file

Switch Description

/a Dumps the Agent List.

/ad Dumps Active Directory information.

/adamm Appends ADAMM file information.

/agents Dumps agent information for the favorite resources.

/all Dumps everything.

 Troubleshooting Backup Exec 783
Generating a diagnostic file for troubleshooting Backup Exec

Table 19-9 Command line switches for a diagnostic file (continued)

Switch Description

/app Dumps the Application Event log.

/b2d Dumps Backup Exec backup-to-disk information.

/basicscsi Dumps basic SCSI hardware subkey from the registry.

/beallfiles Dumps all Backup Exec files and directories.

/bedb Dumps Backup Exec Database information.

/befiles Dumps Backup Exec file information.

/bereg Dumps Backup Exec software configuration from the registry.

/beupdate Dumps Backup Exec update information.

/bex Dumps only the Backup Exec entries that are in the Application Event
log.

/c Dumps the Backup Exec software configuration from the registry.

/caso Dumps information about the central administration server and managed
Backup Exec servers.

/cluster Dumps cluster information

/cps Dumps CPS registry information.

/detailnic Dumps the server's detailed network card information.

/detailscsi Dumps the server's detailed SCSI adapter information.

/dirsvc Dumps the directory service event log.

/dlo Dumps DLO ini file.

/dns Dumps the DNS event log.

/err Dumps only the error events from any event log.

/evdb Dumps Veritas Enterprise Vault database information.

/evevents Dumps the Veritas Enterprise Vault event logs.

/evreg Dumps Veritas Enterprise Vault registry information.

/frs Dumps the file replication service event log.

 Troubleshooting Backup Exec 784
Generating a diagnostic file for troubleshooting Backup Exec

Table 19-9 Command line switches for a diagnostic file (continued)

Switch Description

/o:[file] Specifies the output job log for append.

Omitting [file] sends output to the screen.

/h Dumps the SCSI hardware subkey from registry.

/instapp Dumps information about installed applications.

/lic Dumps Backup Exec server license information.

/liveupdate Dumps Veritas Update Information

/n Dump Windows Socket Network Protocols.

/networkinformation Dumps TCP/IP settings, Winsock information, and Windows firewall

information.

/oracle Dumps Oracle information.

/p Dumps the user privileges.

/power Dumps the PowerShell event log.

/recs:n Dumps only the newest records from given event logs.

The bex, err, and recs switches must be used with the app switch and
the sys switches.

/s Dumps the information on Services.

/sec Dumps the security event log.

/server Dumps server information, such as CPU, memory, disk information,

and more.

/services Dumps information about services.

/sql Dumps the Microsoft SQL Server information.

/bereginfo Dumps the Backup Exec registry information.

/sys Dumps the system event log.

/sys32info Dumps driver information from the system32\drivers folder.

/svcacct Dumps user names used for Backup Exec services.

/u Dumps Microsoft update information.

/userinfo Dumps user privileges and group information.

 Troubleshooting Backup Exec 785
Running the begather utility to troubleshoot Backup Exec components on Linux servers

Table 19-9 Command line switches for a diagnostic file (continued)

Switch Description

/v Dumps Server Information.

/w Dumps Windows version information.

/winpower Dumps the Windows PowerShell event log.

/winupdate Dumps Microsoft update information.

/x Dumps Microsoft Exchange Server Information.

/? Displays usage information.

Running the begather utility to troubleshoot

Backup Exec components on Linux servers
The begather utility brings together the files that help you diagnose issues with
Backup Exec components on Linux servers. After you run it, the begather utility
displays the name of the Packet file that it creates. The files that are gathered
contain detailed information regarding installation, diagnostics, and error reporting.
Reviewing these files before contacting technical support can reveal the source of
the issue. If the solution is not evident based on the gathered files, have the Packet
file available when contacting support. The support technician may request an email
that contains the Packet file.
Run the begather utility to troubleshoot Backup Exec components on Linux
servers
1 Log on as root to the Linux server on which the Backup Exec components are
installed.
2 Navigate to the following directory:
/opt/VRTSralus/bin
For example:
cd /opt/VRTSralus/bin

3 Start the begather utility.

For example:
./begather

4 Note the location of the Packet file that is displayed on the screen.
 Troubleshooting Backup Exec 786
Using the Backup Exec Debug Monitor for troubleshooting

Using the Backup Exec Debug Monitor for

troubleshooting
The Backup Exec Debug Monitor, or SGMon, is a diagnostic tool that captures
debug output from Backup Exec and saves it in debug logs. SGMon debug logs
can help you troubleshoot backup issues. Furthermore, debug logs can help
Technical Support diagnose and repair problems.
When you open SGMon, it automatically captures debug data from Backup Exec's
services. To collect debug information while SGMon is closed, enable debug log
creation outside of SGMon and specify a directory in which to save the logs.
For more information about how to configure the Debug Monitor and read log files,
refer to the help within the Debug Monitor.
To use the Backup Exec Debug Monitor for troubleshooting
◆ Click the Backup Exec button, select Technical Support, and then select
Collect debug output.

About the Backup Exec debug tool

Backup Exec includes a debug tool (BEDBG) that generates diagnostic information
about the Backup Exec processes that shut down unexpectedly. The diagnostic
information helps Technical Support diagnose and repair the problem. The Backup
Exec debug tool runs by default in Backup Exec. The data that the tool gathers is
copied into the BEDBG folder which is located in <Backup Exec install path>\Backup
Exec.
 Chapter 20
Using Backup Exec in
cluster environments
This chapter includes the following topics:

■ About Backup Exec and clusters

■ Requirements for clustering Backup Exec in a Microsoft Cluster Server

environment

■ How Backup Exec works in a Microsoft Cluster Server environment

■ Requirements for installing Backup Exec on a Microsoft Cluster Server

■ Installing Backup Exec on a Microsoft Cluster Server

■ Upgrading Backup Exec on a Microsoft cluster

■ Installing additional Backup Exec features on a Microsoft cluster

■ Uninstalling Backup Exec from a Microsoft cluster

■ Creating storage device pools for Microsoft Cluster Servers

■ Specifying a different failover node

■ Designating a new central administration server in a Microsoft Cluster Server

■ Configurations for Backup Exec and Microsoft Cluster Servers

■ Using the Central Admin Server feature with Microsoft clusters and a storage
area network

■ About backing up Microsoft Cluster Servers

■ About restoring data to a Microsoft cluster

 Using Backup Exec in cluster environments 788
About Backup Exec and clusters

■ Disaster recovery of a cluster

■ Restoring the Microsoft Cluster Server data files

■ Recovering Backup Exec in a Microsoft cluster

■ Manually joining two cluster disk groups and resynchronizing volumes

■ Troubleshooting clusters

About Backup Exec and clusters

In a server cluster, Backup Exec can protect data on local disks and shared disks,
as well as protect Microsoft SQL and Exchange databases that are configured as
virtual server applications; that is, they contain an IP address resource, a Network
Name resource, and are displayed on the network with a unique server name (the
virtual server name). Clustered servers provide high availability of applications and
data to users. In a clustered server, several servers (called nodes) are linked in a
network, and run cluster software that allows each node access to the shared disks.
If a node becomes unavailable, cluster resources migrate to an available node
(called failover). The shared disks and the virtual server are kept available. During
failover, users experience only a short interruption in service.
For information about the best practices to use Backup Exec in clustered
environments, refer to Backup Exec Best Practices.
See “Installing Backup Exec on a Microsoft Cluster Server ” on page 791.
See “Configurations for Backup Exec and Microsoft Cluster Servers” on page 797.
See “About backing up Microsoft Cluster Servers” on page 805.
See “About restoring data to a Microsoft cluster” on page 805.
See “ Requirements for clustering Backup Exec in a Microsoft Cluster Server
environment” on page 788.
See “Disaster recovery of a cluster” on page 806.

Requirements for clustering Backup Exec in a

Microsoft Cluster Server environment
The following are requirements for clustering Backup Exec:
■ It is strongly recommended that if you plan to cluster Backup Exec, use the
default database instance (MSDE) that Backup Exec installs.
■ You can use a remote SQL Server instance to host the Backup Exec Database.
 Using Backup Exec in cluster environments 789
How Backup Exec works in a Microsoft Cluster Server environment

Only one installed instance of Backup Exec can be installed into the remote
SQL Server instance on a clustered node. All other installed instances of Backup
Exec in the cluster must use the default Backup Exec MSDE database instance.

Note: You must run the Backup Exec cluster wizard on the cluster node that
uses the remote SQL Server instance.

■ For off-host backups that use the hardware provider in a Microsoft cluster (MSCS)
environment, the Backup Exec server and the remote computer must be in
different cluster groups. The cluster applications cannot support device logical
unit numbers (LUNs) that have duplicate signatures and partition layouts.
Therefore, the snapshots containing the LUNs must be transported to a host or
remote computer that is outside the cluster.
■ For Windows Server 2008 and later, you must use the same level of operating
system on the Backup Exec server and on the computer that hosts the remote
SQL Server instance in the following scenarios:
■ To use a remote clustered SQL Server instance to host the Backup Exec
Database
■ To use the Backup Exec Utility to reconfigure the clustered Backup Exec
installation or the remote clustered SQL Server instance

For Windows Server 2012 and later, Backup Exec supports parallel backups across
Cluster Shared Volumes (CSV) and cluster nodes.
Backup Exec does not support virtual machines that store data on both CSVFS
and NTFS volumes.
For specific operating system requirements, refer to the Backup Exec Software
Compatibility List.
See “Installing Backup Exec on a Microsoft Cluster Server ” on page 791.
See “About backing up Microsoft Cluster Servers” on page 805.

How Backup Exec works in a Microsoft Cluster

Server environment
When you install Backup Exec into a Microsoft cluster, you install it as a virtual
server application. You assign an IP address resource, a Network Name resource
(the virtual server name), and a disk resource to Backup Exec.
When a failover occurs, backup jobs that were running are rescheduled. The Backup
Exec services are restarted on a designated failover node, and the backup jobs are
 Using Backup Exec in cluster environments 790
Requirements for installing Backup Exec on a Microsoft Cluster Server

restarted by default. Backup Exec provides an additional rule for cluster failover
restart called checkpoint restart. A checkpoint restart option allows backup jobs to
continue from the point at which the jobs were interrupted rather than starting the
backup again. If you enable the rule to retry jobs on a cluster failover, then you can
specify an additional option to do a checkpoint restart when retrying the job.
Checkpoint restart is the only property available for the Cluster Failover Rule. You
can change the default so that jobs are not restarted.
When the failed server comes back online, the Microsoft cluster can automatically
rebalance the workload in a cluster, called failback, by moving cluster groups back
to the server that has rejoined the cluster. However, by design, Backup Exec does
not failback. The backup jobs will continue to run on the designated failover node.
By continuing to run backup jobs on the designated failover node, any further risk
of having to restart the jobs again when the failed server rejoins the cluster is
avoided. Then, when it is convenient, you can move the Backup Exec cluster group
back to the controlling node.
Specific details of how Backup Exec runs in a cluster vary depending on the
configuration you use in the cluster.
See “Configuring checkpoint restart” on page 574.
See “Configurations for Backup Exec and Microsoft Cluster Servers” on page 797.
See “Installing Backup Exec on a Microsoft Cluster Server ” on page 791.

Requirements for installing Backup Exec on a

Microsoft Cluster Server
For specific operating system requirements, refer to the Backup Exec Software
Compatibility List.
The following items are required to install Backup Exec on a Microsoft cluster:
■ Backup Exec clusters can be installed on Windows Server 2008 R2 SP1 majority
node configurations. However, there must be a shared disk in the configuration
in order for Backup Exec to share its database files between nodes. In this type
of configuration, if the majority of the cluster nodes fail, then the entire cluster
will fail. This configuration normally uses more than two nodes in the cluster
configuration.
■ The controlling node and designated failover nodes must be online during
installation of Backup Exec into the cluster.
■ A unique IP address and a unique network name for the Backup Exec virtual
server is required during installation.
 Using Backup Exec in cluster environments 791
Installing Backup Exec on a Microsoft Cluster Server

■ During installation of a Backup Exec cluster, the node that runs the installation
should own the shared disk. If you use a physical disk resource that belongs to
another application, the Backup Exec Cluster Wizard will move all the resources
that belong to the other application into the Backup Exec group. It is
recommended that Backup Exec not be installed on the cluster quorum.
■ An individually licensed copy of Backup Exec, as well as any applicable agents
and options, is required for each active node in the cluster as defined in the End
User License Agreement. When installing a trial version of Backup Exec, a
cluster environment is automatically detected and licenses are not required.
■ When you install Backup Exec clusters in a Central Admin Server feature (CAS)
configuration, all Backup Exec installations must have the same server
configuration. Either all nodes should be database servers or all nodes should
be managed Backup Exec servers that connect to the central administration
server.
■ All Backup Exec installations into a cluster must either be part of a single cluster
group, or be locally installed on each node. If cluster-aware Backup Exec is
installed in a cluster as well as a locally installed version of Backup Exec (not
cluster-aware), then you cannot log on to the locally installed Backup Exec
server. You can only log on using the Backup Exec virtual server name. To be
able to log on to the locally installed Backup Exec server, you must first use the
Cluster Configuration Wizard to uninstall cluster-aware Backup Exec from all
the nodes in the cluster.
■ Use the same account for Backup Exec services on all nodes in the cluster. If
nodes in a cluster use Backup Exec and have different accounts, change the
services to use the same account.
See “Installing Backup Exec on a Microsoft Cluster Server ” on page 791.
See “Configurations for Backup Exec and Microsoft Cluster Servers” on page 797.

Installing Backup Exec on a Microsoft Cluster

Server
Installing Backup Exec on the same disk that the cluster quorum is installed on is
not recommended. If you have to specify a new drive letter for the quorum disk
during a recovery process, Backup Exec will not recognize the new drive and will
not run.
 Using Backup Exec in cluster environments 792
Upgrading Backup Exec on a Microsoft cluster

Note: By default, failover from the controlling node to a designated node occurs in
alphabetical order according to the machine name of each node. To change the
order in which failover will occur on the designated nodes, rename the machines.

The Backup Exec Agent for Windows is automatically installed on all the nodes in
the cluster. If this installation of Backup Exec is to be used to back up remote servers
outside the cluster, install the Agent for Windows on those remote servers as well.
To install Backup Exec on a Microsoft Cluster Server
1 Install Backup Exec on all the nodes that you want in the cluster. Use the same
installation path for each node.
2 From the node that you want to be the active node, start Backup Exec.
3 Click the Backup Exec button, select Configuration and Settings, and then
select Cluster Configuration Wizard.
4 Follow the instructions on the screen.
On the Virtual Server Information screen, Backup Exec automatically displays
a default name called BKUPEXECVRS for the virtual server. Type a new default
name if you do not want to use the default.
5 When the Cluster Configuration Wizard completes, create a storage device
pool that contains all the locally attached storage devices on each node to be
used when failover occurs. This ensures that jobs can be run on the storage
devices that are attached to the failover nodes.
See “Creating storage device pools for Microsoft Cluster Servers” on page 794.
6 Repeat step 5 for all nodes.
See “Configurations for Backup Exec and Microsoft Cluster Servers”
on page 797.
See “Specifying a different failover node” on page 795.

Upgrading Backup Exec on a Microsoft cluster

You can upgrade Backup Exec on the nodes in a cluster without taking the nodes
out of the cluster.

Table 20-1 Upgrading Backup Exec on a Microsoft cluster

Step Action

Step 1 Select a node to upgrade and make that node

the active Backup Exec cluster node.
 Using Backup Exec in cluster environments 793
Installing additional Backup Exec features on a Microsoft cluster

Table 20-1 Upgrading Backup Exec on a Microsoft cluster (continued)

Step Action

Step 2 Run the Backup Exec installation program on

the active node.

Step 3 Move the cluster group to the next node you

want to upgrade, and then run the Backup
Exec installation program on that node. All of
the resources except for the disk should be
offline when moved over to each node for
upgrade.

Step 4 Repeat step 3 for each node in the cluster.

See “Installing additional agents and features to the local Backup Exec server”
on page 58.

Installing additional Backup Exec features on a

Microsoft cluster
Install additional Backup Exec features on each node of the cluster. For details on
installing each feature, see the appropriate section in this guide, or in online Help.
To install additional Backup Exec features
1 On the controlling node, make sure the Backup Exec group is online before
you start installing additional features.
2 Install the additional features.
See “Installing additional agents and features to the local Backup Exec server”
on page 58.
3 After the installation is complete on the controlling node, use the cluster
administrator to move the Backup Exec group to the next appropriate node,
and repeat step 2.
Be sure to install the same features with the same settings for each node in
the cluster.
4 To install the Agent for Oracle on Windows or Linux Servers on other nodes,
map a drive to the shared disks where Backup Exec is installed on the cluster,
and run SETUP.
See “Uninstalling Backup Exec from a Microsoft cluster” on page 794.
 Using Backup Exec in cluster environments 794
Uninstalling Backup Exec from a Microsoft cluster

Uninstalling Backup Exec from a Microsoft cluster

You use the Cluster Configuration Wizard to remove Backup Exec.
To uninstall Backup Exec from a cluster
1 Click the Backup Exec button, select Configuration and Settings, and then
select Cluster Configuration Wizard.
2 Use the wizard to remove cluster-aware Backup Exec from all selected servers.
When unclustering the active node, you can either leave the Backup Exec data
on the shared drive or delete it. If you delete the data, you can make the data
available on the active node.
3 Uninstall Backup Exec from all the nodes.
4 After Backup Exec has been uninstalled, move any resource disks from the
Backup Exec cluster group to another group, and then delete the Backup Exec
cluster group.
5 On any node, click Start, point to Settings, and then click Control Panel to
uninstall Backup Exec.
6 Double-click Add/Remove Programs, and then in the list of currently installed
programs, select Backup Exec and click Change/Remove.
7 Repeat step 5 for all nodes.
See “Creating storage device pools for Microsoft Cluster Servers” on page 794.

Creating storage device pools for Microsoft

Cluster Servers
When Backup Exec is installed on a cluster, it creates a set of default storage pools
for each node in the cluster. If a node has storage devices, those storage devices
are automatically assigned to an appropriate device pool, which is also the default
destination device on that node when you create backup or restore jobs. However,
to allow jobs to run on the storage devices attached to a failover node after a failover
occurs, you must create a storage pool that includes the storage devices from all
of the nodes. If the cluster is also configured with tape devices on a shared SCSI
bus, then add the tape device name used by each node to the storage pool. You
must also select this storage pool as the destination device for all jobs that you
want to be restarted.
You can create either a single storage pool, or you can create storage pools for
device or media types so that when jobs fail over they can be restarted on "like"
devices and media.
 Using Backup Exec in cluster environments 795
Specifying a different failover node

To create a storage pool for a cluster

1 From the controlling node, open Backup Exec.
2 Create a new storage device pool and add storage devices.
See “Creating storage device pools” on page 438.
3 Exit Backup Exec. If there are tape devices on a shared SCSI bus, then add
the tape device name used by each node.
4 Using the cluster administrator, move the Backup Exec resource group to the
next appropriate node.
5 Open Backup Exec, add storage devices for this node to the previous storage
pool and then exit Backup Exec. If there are tape devices on a shared SCSI
bus, then add the tape device name used by each node.
6 Repeat step 4 and step 5 for each node in the cluster.

Specifying a different failover node

You can do the following:
■ Change the order in which the nodes fail over.
■ Add a failover node to the cluster.
■ Remove a failover node from the cluster.

Note: By default, in a MSCS cluster, failover from the controlling node to a

designated node occurs in alphabetical order according to the machine name of
each node. To change the order in which failover will occur on the designated nodes,
rename the machines in the order in which they should fail over.

Before you add a node to the Backup Exec cluster configuration, you must install
Backup Exec on it. Cluster services for a node should be online before you add or
remove it from the cluster.
If you are removing a node, do not run the cluster configuration wizard from the
node you want to remove.
 Using Backup Exec in cluster environments 796
Designating a new central administration server in a Microsoft Cluster Server

To add or remove a failover node

1 On the controlling node, click the Backup Exec button, select Configuration
and Settings, and then select Cluster Configuration Wizard.
2 Follow the instructions on the screen to add or remove a node.
3 If you have added a failover node, also add any locally attached storage devices
that are to be used when failover occurs to the cluster storage pool. This
ensures that jobs can be run on the storage devices that are attached to the
failover nodes.
If you remove some but not all nodes in a cluster, an uninstall of Backup Exec
results in a password being requested for the virtual server and the services
continuing to run. You must remove Backup Exec from all nodes on the cluster.
See “Uninstalling Backup Exec from a Microsoft cluster” on page 794.
See “Specifying a different failover node” on page 795.
See “Configurations for Backup Exec and Microsoft Cluster Servers”
on page 797.

Designating a new central administration server

in a Microsoft Cluster Server
To designate a new central administration server for a cluster environment, use
BEUtility.exe. BEUtility enables you to do various types of configuration and
maintenance operations on your Backup Exec servers.

Note: In a cluster environment, do not use Change Service Account in

BEUtility.exe.

To change a Backup Exec cluster from a Database Server to a Member Server

1 Install the new server as a managed Backup Exec server with the Library
Expansion feature installed.
Make sure connections to the Backup Exec cluster and other member servers
are working properly.
2 Using the cluster administrator, shut down the Backup Exec cluster services.
Be sure to keep the Disk resource online.
3 Move the catalog files from the Backup Exec cluster installation path to the
respective installation paths on the new database server.
 Using Backup Exec in cluster environments 797
Configurations for Backup Exec and Microsoft Cluster Servers

4 Use BEUtility.exe to connect all Backup Exec servers to the new database
server and to start all Backup Exec services.
5 Stop and restart the Backup Exec Services on the new database server.
6 Using the Cluster Administrator, move the Backup Exec resource group to the
failover node and make sure services start on that node.
7 Use BEUtility.exe to stop and restart the Backup Exec Services on all the
member servers of the SAN in order for them to connect to the new database
server.
To change a Backup Exec cluster from a central administration server to a
managed Backup Exec server
1 Install the new server as a managed Backup Exec server.
Make sure connections to the Backup Exec cluster and other managed Backup
Exec servers are working properly.
2 Using the cluster administrator, shut down the Backup Exec cluster services.
Be sure to keep the Disk resource online.
3 Move the catalog files from the Backup Exec cluster installation path to the
respective installation paths on the new central administration server.
4 Use BEUtility.exe to connect all Backup Exec servers to the new central
administration server and to start all Backup Exec services.
5 Stop and restart the Backup Exec Services on the central administration server.
6 Using the Cluster Administrator, move the Backup Exec resource group to the
failover node and make sure services start on that node.
7 Use BEUtility.exe to stop and restart the Backup Exec Services on all the
managed Backup Exec servers in order for them to connect to the new central
administration server.
See “Multi-node clusters on a fibre channel SAN with the Central Admin Server
feature” on page 802.

Configurations for Backup Exec and Microsoft

Cluster Servers
Backup Exec supports various cluster configurations of between two and eight
nodes on a fibre channel SAN, with locally attached storage devices, or with storage
devices on a shared SCSI bus. You can use any combination of these configurations.
 Using Backup Exec in cluster environments 798
Configurations for Backup Exec and Microsoft Cluster Servers

Note: If you install the cluster on a private network, use the Cluster Administrator
to enable public communication if necessary.

If you are using a cluster on a fibre channel SAN or with storage devices on a shared
SCSI bus and failover occurs, depending on the capability of your various SAN
components, media might be orphaned in the tape drive until the failed node
becomes active again.
If end-of-job markers were not written to the media before the failover occurred,
the media may be marked as unappendable by the Backup Exec engine when the
next append backup job is run. The media remains unappendable until it is
overwritten (or erased, or the retention period expires, etc.).
If the storage device is a robotic library, you can review the Robotic Library Inventory
report to discover if the media was marked unappendable by the Backup Exec
engine. If the Full column reports a 3, the Backup Exec engine has marked the
media as unappendable.
To add or remove hot-swappable devices in a cluster, run the Hot-swap Device
Wizard on all Backup Exec Cluster nodes. If a server is not updated to recognize
a new device, any job that is targeted to that device may fail.
See “Adding or replacing devices with the Hot-swappable Device Wizard”
on page 381.
The following examples illustrate various cluster configurations:
■ See “Two-node cluster with locally attached storage devices” on page 798.
■ See “Two-node cluster with tape devices on a shared SCSI bus” on page 799.
■ See “Configuring a shared SCSI bus for tape devices” on page 800.
■ See “Multi-node clusters on a fibre channel SAN with the Central Admin Server
feature” on page 802.

Two-node cluster with locally attached storage devices

In this configuration, cluster-aware Backup Exec is installed on the controlling node,
failover occurs to designated nodes in the cluster, and storage devices are locally
attached to each node.
Depending on the type of storage device, each node’s locally attached storage
devices are automatically assigned to an appropriate storage device pool that
Backup Exec creates. These storage device pools also act as default destination
devices on that node when you create backup or restore jobs. You must create a
storage pool that includes storage devices on the controlling node and on each
failover node in order for jobs to run when failover occurs.
 Using Backup Exec in cluster environments 799
Configurations for Backup Exec and Microsoft Cluster Servers

See “Creating storage device pools for Microsoft Cluster Servers” on page 794.
To restore data in this configuration, move media to the failover node’s locally
attached storage device and reinventory the device before starting a restore
operation.

Figure 20-1 Two-node Cluster with Locally Attached Storage Devices

Backup Exec Virtual Server

Controlling Failover
node node
Shared SCSI Bus
for disks

Locally attached Locally Attached

Heartbeat
storage devices storage devices
LAN

See “Multi-node clusters on a fibre channel SAN with the Central Admin Server
feature” on page 802.

Two-node cluster with tape devices on a shared SCSI bus

In this configuration, cluster-aware Backup Exec is installed on the controlling node,
failover occurs to designated nodes in the cluster, and tape devices are attached
to a shared SCSI bus that is separate from any shared SCSI bus for disks.
Because each node creates a unique tape device name for the same device, if the
drive is not serialized, this configuration requires you to create a storage pool that
includes the tape device name used by each node in order for jobs to run when
failover occurs.
See “Creating storage device pools for Microsoft Cluster Servers” on page 794.
When failover occurs, a SCSI bus reset is issued. Therefore, tape devices and
shared drives should not be connected to the same SCSI bus; each should be
connected to separate SCSI buses.
See “Configuring a shared SCSI bus for tape devices” on page 800.
 Using Backup Exec in cluster environments 800
Configurations for Backup Exec and Microsoft Cluster Servers

Note: If you are using a serialized tape device in a shared SCSI cluster configuration,
media that is orphaned in a device because of a failover will be ejected from the
tape device. If you are using a tape device that is not serialized, you need to
manually eject the media from the device or reboot the device.

Figure 20-2 Two-node cluster with tape devices on a shared SCSI bus

Backup Exec Virtual Server

Controlling Failover node
node

Shared SCSI
Bus for Disks

Shared SCSI
Bus for Tape
Devices

Heartbeat

LAN

See “Multi-node clusters on a fibre channel SAN with the Central Admin Server
feature” on page 802.

Configuring a shared SCSI bus for tape devices

To configure tape devices on a shared SCSI bus, you must have SCSI cables,
SCSI terminators, a SCSI adapter in each cluster node to provide a shared external
bus between the nodes, and at least one tape device on the shared bus.
The tape devices must be connected to a bus that uses the same method of
transmission that the device does (single-ended or differential). Only one
transmission method can be used on a single SCSI bus, however, if the devices
use different transmission methods, you can install a signal converter between the
devices. A signal converter converts single-ended SCSI signals to differential SCSI
signals.

Note: You must use a signal converter to connect single-ended and differential
devices in order to avoid hardware damage.

You must terminate the SCSI bus at both ends so that commands and data can be
transmitted to and from all devices on the bus. Each SCSI bus must have two
terminators and they must be at each end of the segment.
 Using Backup Exec in cluster environments 801
Configurations for Backup Exec and Microsoft Cluster Servers

If a tape device is in the middle of the bus, remove any internal termination in that
device.
If the tape device is at the end of the bus, and the tape device has internal
termination, you can use the device’s internal termination to terminate the bus.

Figure 20-3 Example of a shared bus with tape devices at the end of the bus

Backup Exec Virtual Server

Controlling
Failover node
node

Shared SCSI
bus for disks

Shared SCSI
bus for tape devices

Heartbeat

LAN

Following are methods you can use to terminate a bus:

■ SCSI adapters. This method is not recommended because if the server is
disconnected from the shared bus, or if there is a power supply failure, the bus
may not be properly terminated and may be inoperable.
■ Pass-through (or feed-through) SCSI terminators. These can be used with SCSI
adapters and with some tape devices. If the tape device is at the end of the bus,
you can attach a pass-through SCSI terminator to terminate the bus. The internal
terminators in the tape device must be disabled. This is a recommended method.

Note: To ensure termination if a power supply failure occurs, turn off the on-board
terminators on the SCSI controller (using the host adapter manufacturer’s
recommended method) and physically terminate the controller with a terminator.

■ Y cables. These can be used with some tape devices. If the tape device is at
the end of the bus, you can attach a terminator to one branch of a Y cable to
terminate the bus. The internal terminators in the tape device must be disabled.
This is a recommended method.
■ Trilink connectors. These can be used with some tape devices. If the tape device
is at the end of the bus, you can attach a terminator to one of the trilink
 Using Backup Exec in cluster environments 802
Configurations for Backup Exec and Microsoft Cluster Servers

connectors to terminate the bus. The internal terminators in the tape device
must be disabled. This is a recommended method.
Besides terminating the bus, Y-cables and trilink connectors also allow you to isolate
the devices from the shared bus without affecting the bus termination. You can
maintain or remove that device without affecting the other devices on the shared
SCSI bus.
To configure a shared SCSI bus for tape devices
1 Install the SCSI controllers for the shared SCSI bus.
Make sure that the SCSI controllers for the shared SCSI bus are using different
SCSI IDs. For example, on the controlling node, set the SCSI controller ID to
6 and on the failover node, set the SCSI controller ID to 7.
2 Prepare the SCSI controllers for the shared SCSI bus. Refer to your SCSI host
adapter manufacturer’s documentation for details.
Do not have power on to both nodes while configuring the computers, or if both
nodes have power on, do not connect the shared SCSI buses to both nodes.
3 Connect the shared SCSI tape devices to the cable, connect the cable to both
nodes, and then terminate the bus segment using one of the methods discussed
in the previous section.
See “Two-node cluster with tape devices on a shared SCSI bus” on page 799.

Multi-node clusters on a fibre channel SAN with the Central Admin

Server feature
In this configuration, one or more clusters are attached to a fibre channel storage
area network (SAN), with cluster-aware Backup Exec and the Central Admin Server
feature (CAS) installed on the controlling node in each cluster. Shared secondary
storage devices are attached to the fibre channel, although a single storage device
can be shared between one or more clusters. Failover occurs (in alphabetical order
of the machine name) to other designated nodes in the cluster.

Note: When using multiple clusters in a CAS environment, it is strongly

recommended that the cluster nodes be connected to the storage devices using a
fibre switch. If you use a hub rather than a fibre switch, the hub will receive a reset
command during a failover event that causes all other components attached to the
hub to be disconnected. You can designate any server on the fibre channel SAN
as the central administration server.

You should create a failover storage pool for the cluster.

 Using Backup Exec in cluster environments 803
Configurations for Backup Exec and Microsoft Cluster Servers

See “Creating storage device pools for Microsoft Cluster Servers” on page 794.
This configuration offers increased performance since backups are performed locally
instead of over a network. Additionally, centralized media catalogs are available.
Because CAS uses a shared catalog database, a tape that has already been
cataloged can be physically moved from one device to another and not have to be
recataloged.

Note: The CAS feature must be installed on each failover node, with the same
settings that were used on the primary node. Either all nodes should be database
servers or all nodes should be managed Backup Exec servers.

The following are examples of multi-node clusters:

Figure 20-4 Two 2-node Clusters on a Fibre Channel SAN with the Central
Admin Server feature

Fibre
Channel
SAN Secondary
Secondary server
Storage
Devices

Backup Exec Backup Exec

Virtual Server Virtual Server
A B

Controlling Failover
node node
Shared Shared
SCSI Bus for disks
Failover SCSI Bus for disks
node
Heartbeat Controlling
node
Heartbeat

LAN

You can have a four-node cluster.

See “Using the Central Admin Server feature with Microsoft clusters and a storage
area network” on page 804.
 Using Backup Exec in cluster environments 804
Using the Central Admin Server feature with Microsoft clusters and a storage area network

Using the Central Admin Server feature with

Microsoft clusters and a storage area network
Managed Backup Exec servers can be clustered. However, this configuration is
not recommended because the central administration server recovers all failed jobs
in a distributed job environment.
The following configurations can be used when installing Backup Exec clusters with
the Central Admin Server feature (CAS).
■ Backup Exec cluster with CAS
■ Backup Exec cluster with the managed Backup Exec server configuration
To install Backup Exec in a Microsoft cluster with CAS
1 Install Backup Exec with CAS and any additional features onto your Microsoft
cluster nodes.
2 From the node that you want to designate as the active node, start Backup
Exec.
3 Click the Backup Exec button, select Configuration and Settings, and then
select Cluster Configuration Wizard..
4 Follow the instructions on the screen.
5 When the Cluster Configuration Wizard completes, install the managed Backup
Exec server. Use the virtual Backup Exec cluster name when prompted for the
central administration server.
To install Backup Exec in a Microsoft cluster with the managed Backup Exec
server configuration
1 Install Backup Exec with the managed Backup Exec server feature and any
additional features onto your Microsoft cluster nodes.
All nodes that run Backup Exec in the Microsoft cluster configuration must
access the same central administration server. If the nodes do not access the
same central administration server, failovers do not occur properly.
2 From the node that you want to designate as the active node, start Backup
Exec.
3 Click the Backup Exec button, select Configuration and Settings, and then
select Cluster Configuration Wizard.
4 Follow the instructions on the screen.
See “About backing up Microsoft Cluster Servers” on page 805.
 Using Backup Exec in cluster environments 805
About backing up Microsoft Cluster Servers

About backing up Microsoft Cluster Servers

To protect all data in the cluster, which includes file shares, databases, and the
cluster quorum, back up the following:
■ Local disks, Shadow Copy Components, and System State on each node. The
cluster quorum, which contains recovery information for the cluster and
information about changes to the cluster configuration, is included in the System
State backup.
■ All shared disks, including the data in the Microsoft Cluster Server folder on the
Quorum disk.
■ Virtual servers, which may contain data or contain applications such as Microsoft
SQL Server or Exchange Server. Use Backup Exec database agents to back
up databases.

Note: For offhost backup jobs that use the hardware provider, the Backup Exec
server and the remote computer must be in different cluster groups. The cluster
applications cannot support device logical unit numbers (LUNs) that have duplicate
signatures and partition layouts, therefore, the snapshots containing the LUNs must
be transported to a host, or remote computer, that is outside the cluster.

The Backup Exec Management Command Line Interface (BEMCLI) can be used
with Backup Exec when Backup Exec is installed in a cluster. The only limitation is
that you cannot use the BEMCLI to specify a device for backup. You can use the
BEMCLI to target a storage pool, but not a specific device in that pool.
See “Backing up data” on page 153.
See “Editing backup definitions” on page 200.
See “Adding a stage to a backup definition” on page 214.

About restoring data to a Microsoft cluster

For all file restore operations, including redirecting restores, use the normal restore
procedures.
When restoring files to shared drives, direct those files to the virtual server or the
controlling node of the resource. When restoring individual database files, such as
Microsoft SQL Server or Exchange Server, direct those files to the virtual server
name of a specific installation of the SQL or Exchange database.
See “Methods for restoring data in Backup Exec” on page 227.
 Using Backup Exec in cluster environments 806
Disaster recovery of a cluster

Disaster recovery of a cluster

Prepare for recovery by creating a disaster preparation plan.
Prepare to restore SQL and Exchange databases in a cluster after a disaster by
reading the sections on preparing for disaster recovery in the appropriate chapters.
In addition to the initial preparation instructions, further action is required to
completely protect the Microsoft clusters.
If a disaster occurs, the following information is required to successfully recover
the cluster:
■ General Cluster Information
■ Cluster name
■ Cluster IP address and subnet mask
■ Cluster node names
■ Node IP addresses
■ Local and shared drive letters and partition scheme
■ Disk signatures

■ Cluster Groups
■ Group name
■ Preferred nodes
■ Failover/failback policies

■ Cluster Resources
■ Resource name
■ Resource type
■ Group membership
■ Possible owners
■ Resource dependencies
■ Restart and Looks Alive/Is Alive properties
■ Resource-related parameters
■ Application-specific configuration (SQL Database Character Set)

See “Creating a disaster preparation plan (DPP)” on page 131.

See “Disaster recovery of an Exchange Server” on page 1144.
 Using Backup Exec in cluster environments 807
Disaster recovery of a cluster

Using Simplified Disaster Recovery to prepare for disaster recovery

of a cluster
Backup Exec provides a fully-automated disaster recovery solution called Simplified
Disaster Recovery, which allows you to quickly and efficiently recover the nodes
that comprise the server cluster after a disaster. Oracle servers cannot be restored
using Simplified Disaster Recovery. For more information about disaster recovery
for these options, see the appropriate chapters.
See “Preparing computers for use with Simplified Disaster Recovery” on page 816.

Note: To change the setup, use hardware, or a hardware configuration that is

different from the original configuration, you must perform a manual recovery.

Recovering nodes on the cluster using Simplified Disaster Recovery

If you used Backup Exec’s Simplified Disaster Recovery to prepare for a disaster,
you can use Simplified Disaster Recovery to recover the nodes to their pre-disaster
state.
When recovering both nodes in a cluster, make sure that the drive letters match
the original cluster configuration. The scaled-back version of Windows that runs
the recovery wizard may detect the hard drives in a different order than what was
originally configured under the original version of Windows.
If the original configuration does not match, then to a certain extent, you can control
the hard drive numbering scheme that Windows devises.
If you cannot get the SDR Recover This Computer Wizard to properly detect the
hard drive order, you can still manually set up hard drive partitions using the
Advanced Disk Configuration option within the Recover This Computer Wizard.
After this is done, you can continue with automated restore of your backup media
afterward.

Note: After Windows has been installed, you cannot change the system drive’s
letter. You must restore the system to the same drive letter from which it was backed
up.
 Using Backup Exec in cluster environments 808
Disaster recovery of a cluster

To recover nodes on the cluster using Simplified Disaster Recovery

1 If you are recovering more than one node, disconnect the shared disks. If you
are recovering only one node, the shared disks do not need to be disconnected.
If all nodes in the cluster are unavailable and must be recovered, the cluster
cannot fail over. Disconnect the shared disks before recovery begins.
2 Restore the nodes.
See “Methods for restoring data in Backup Exec” on page 227.
3 Reconnect the shared drives and bring the nodes online.
4 To restore a database to the shared drives, use the appropriate Backup Exec
agent.
See “About Simplified Disaster Recovery” on page 812.

Recovering Backup Exec on a Microsoft cluster using Simplified

Disaster Recovery
To fully restore a cluster on which Backup Exec is installed, you can use Simplified
Disaster Recovery to restore the cluster node and all shared disks or you can rebuild
the cluster. To remotely restore the cluster catalog the media that contains the
backup sets of the cluster nodes and the shared disk.
To recover Backup Exec on a Microsoft Cluster with Simplified Disaster
Recovery:
1 Replace all shared disks, if necessary.
2 Run the SDR Recover This Computer Wizard on one of the nodes. During
this process, use Advanced Disk Configuration to repartition all shared disks
to their original configuration. Restore the local disk, system state, and the data
files to the shared disk.
3 Restart the server.
The cluster service and all other cluster applications should come online.
4 Run the Recover This Computer wizard on all other nodes. Restore only the
local disk and system state.
See “About Simplified Disaster Recovery” on page 812.

Recovering the entire cluster using a manual disaster recovery

procedure
As part of the manual recovery process, you must reinstall Windows, including the
last service pack applied before the failure.
 Using Backup Exec in cluster environments 809
Restoring the Microsoft Cluster Server data files

See “About restoring Oracle resources” on page 1190.

To recover the entire cluster manually
1 On the first node you want to recover, reinstall Windows, including the last
service pack applied before the failure.
2 On the other nodes you want to recover, reinstall Windows, including the last
service pack applied before the failure.
3 Reinstall the cluster services and bring the cluster online.
Do the following:
■ If you are recovering a Microsoft Cluster Server, after booting the nodes in
a cluster, make sure that the drive letters match the original cluster
configuration. If the original configuration does not match, then to a certain
extent, you can control the hard drive numbering scheme that Windows
devises by using the Disk Administrator.
■ If you are recovering a Microsoft Cluster Server, use the Cluster Wizard to
reinstall Backup Exec on the cluster. You must use the same settings used
during the initial installation.
See “Installing Backup Exec on a Microsoft Cluster Server ” on page 791.

4 Catalog the media in the cluster.

5 On the Backup and Restore tab on the active node, click Restore.
6 Restore last full backup sets made of the active node, and then restore the
System State.
7 If you are recovering a Microsoft Cluster Server, select the Restore cluster
quorum option in the Restore Wizard.
8 Start the restore operation.
9 When the restore has completed, reboot the active node.
10 For each node that you need to recover, repeat step 5 through step 9.
11 After all nodes are recovered, restore the Backup Exec data files, and all other
data files, to the shared disks.
12 To restore a database to the shared disks, use the appropriate Backup Exec
agent.

Restoring the Microsoft Cluster Server data files

To fully recover the cluster, the cluster files in the MSCS folder may need to be
restored. If the Quorum disk is still available and has not changed, then you do not
have to restore the data files.
 Using Backup Exec in cluster environments 810
Recovering Backup Exec in a Microsoft cluster

For versions of Windows prior to Windows Server 2008, if the Quorum disk is new,
you must restore the data files to the new Quorum disk. You should disable the
cluster disk driver before restoring the data files.
See “Methods for restoring data in Backup Exec” on page 227.

Recovering Backup Exec in a Microsoft cluster

If you used Simplified Disaster Recovery's Create Simplified Disaster Recovery
Disk Wizard to prepare disaster recovery media for the shared disks, you must
use a manual process to recover Backup Exec on a shared disk.
To use a manual process to recover Backup Exec on a shared disk
1 Replace the shared disk if necessary, and add that disk to the cluster as a disk
resource.
2 Reinstall the cluster-aware version of Backup Exec on the cluster using the
same information used in the original installation.
3 Use Backup Exec to restore any data from the catalogs.
See “Methods for restoring data in Backup Exec” on page 227.

Manually joining two cluster disk groups and

resynchronizing volumes
If an Advanced Disk-based backup failed due to the application virtual server failover,
you may need to re-join the cluster disk groups.
To manually re-join the two cluster disk groups and resynchronize the volumes
1 Import the cluster disk group into the node, if the original cluster disk group is
not already imported into the node where the production virtual server is
currently online.
2 Rejoin the new cluster disk group with the original cluster disk group.
3 Snap back the snapped volumes with their original volumes. Ensure that the
option to synchronize using the original volume is selected.
If you are not able to import the new cluster disk group into the node where
the original cluster disk group is currently located, failover the application virtual
server back to its original node before rejoining the two cluster disk groups.
See “Troubleshooting clusters” on page 811.
 Using Backup Exec in cluster environments 811
Troubleshooting clusters

Troubleshooting clusters
If you experience problems with using Backup Exec in a cluster environment, review
the questions and answers in this section.

Table 20-2 Cluster troubleshooting questions and answers

Question Answer

I used the checkpoint You received this error because failover occurred in the middle
restart option for my of backing up the resource, therefore the backup set was not
backups. During one of closed on the media. However, the objects that were partially
my backups, a Microsoft backed up in the first backup set were completely backed up
cluster failover occurred. again during restart, ensuring data integrity. Therefore, all of the
Multiple backup sets objects on the media for the given backup set should still be
were created. When I try restored and verified.
to verify or restore using
these backup sets, an
"Unexpected End of
Data" error occurs on the
set that contains the data
that was backed up prior
to the failover. Why does
this occur? Is my data
safe?

I clustered a central This occurs when the managed Backup Exec server becomes
administration server with the active node and attempts to connect to the Backup Exec
a managed Backup Exec database on the central administration server, which is no longer
server. Now the device available. To correct this, you must use the Backup Exec Utility
and media service on the (BEUTILITY.EXE) or reinstall the managed Backup Exec server
managed Backup Exec to become a central administration server.
server fails. Why?

See “About Backup Exec and clusters” on page 788.

 Chapter 21
Simplified Disaster
Recovery
This chapter includes the following topics:

■ About Simplified Disaster Recovery

■ Requirements for using Simplified Disaster Recovery

■ Preparing computers for use with Simplified Disaster Recovery

■ How to ensure that backups are enabled for Simplified Disaster Recovery

■ How Simplified Disaster Recovery uses disaster recovery information files

■ Setting or changing the alternate location for the disaster recovery information
file

■ Creating a Simplified Disaster Recovery disk image

■ Preparing to recover from a disaster by using Simplified Disaster Recovery

■ Recovering a computer with Simplified Disaster Recovery

■ Advanced Disk Configuration on the Recover This Computer Wizard

■ Performing manual disaster recovery

About Simplified Disaster Recovery

Simplified Disaster Recovery (SDR) is automatically installed with Backup Exec so
that you can perform disaster recovery on Windows computers on which the Agent
for Windows is installed. By default, Backup Exec is configured to back up all of
the critical system components that you need to perform a disaster recovery.
 Simplified Disaster Recovery 813
Requirements for using Simplified Disaster Recovery

After a computer's critical system components are backed up, use the Create
Simplified Disaster Recovery Disk Wizard to create a Simplified Disaster Recovery
disk image. Use the recovery disk to perform disaster recovery of the computers
that are backed up.
When you use SDR to perform a recovery, Backup Exec uses the system-level
information from the SDR backup to rebuild the server and restore it to a functional
state. Recovery includes a bare metal or dissimilar hardware restore operation.
Through integration with the Microsoft Volume Shadow Copy Service (VSS), the
SDR backups include all selected elements, even if they are components of the
active operating system or are in an open state. VSS integration ensures that the
backups are in a consistent state and have been properly placed into a quiescent
state when the backup occurs.
Simplified Disaster Recovery is available only for servers on which the Agent for
Windows is installed and that are backed up through the Agent for Windows. You
must purchase the Agent for Windows separately, and then install it on the remote
computers that you want to protect.
The Simplified Disaster Recovery feature now requires the Microsoft Assessment
and Deployment Kit (ADK) to create a Simplified Disaster Recovery disk image
(.iso).

Note: After the Backup Exec upgrade, customers must customize the existing SDR
ISOs to make the ISO compatible with the Backup Exec release to which they have
upgraded.

For information about the best practices to use Backup Exec Simplified Disaster
Recovery (SDR), refer to Backup Exec Best Practices.
See “Preparing computers for use with Simplified Disaster Recovery” on page 816.
See “How to ensure that backups are enabled for Simplified Disaster Recovery”
on page 820.
See “Requirements for using Simplified Disaster Recovery ” on page 813.
See “Creating a Simplified Disaster Recovery disk image” on page 827.
See “Recovering a computer with Simplified Disaster Recovery” on page 853.

Requirements for using Simplified Disaster

Recovery
The following items are required for Simplified Disaster Recovery (SDR):
 Simplified Disaster Recovery 814
Requirements for using Simplified Disaster Recovery

■ Backup Exec or the Backup Exec Agent for Windows must be installed on any
computers that you want to protect with SDR.

Note: The Create Simplified Disaster Recovery Wizard is not supported on any
32-bit operating system.

■ Encryption key files must exist for all volumes that you encrypt with Windows
BitLocker Drive Encryption.
■ A third-party ISO 9660-compliant CD or DVD burning application must be
available to burn the SDR-created bootable image to a CD or DVD.
■ A writable or rewritable CD or DVD device must be available.
■ An Internet connection so that you can download the Microsoft Assessment and
Deployment Kit.
■ The option Use storage-based catalogs must be enabled. If you disable this
option, the backup sets that you create for use with SDR cannot be restored
during an SDR recovery operation. As a result, SDR cannot recover the failed
computer. To ensure that this option is enabled, click the Backup Exec button,
click Configuration and Settings > Backup Settings > Catalog.

Note: If you use deduplication disk storage devices, be aware that there are
limitations in their use with SDR.
See “Recovery notes for using Simplified Disaster Recovery with Exchange, SQL,
SharePoint, CAS, Hyper-V hosts, and the Deduplication feature” on page 863.

Additional requirements exist when you create a Simplified Disaster Recovery disk
image and when you run the Recover This Computer Wizard, as described in the
following sections.

Requirements for creating a Simplified Disaster Recovery

disk image
The following items are required to create the Simplified Disaster Recovery disk
image:
■ The Simplified Disaster Recovery disk image must be the same version of
Backup Exec as the Backup Exec server. You cannot use SDR to restore the
backups that were created with previous versions of Backup Exec.
■ The Microsoft Windows Assessment and Deployment Kit (ADK) 8.1, and ADK
8.1 Update 1 is supported only on Windows Server 2008 SP2. From Windows
Server 2008 R2 to Windows Server 2016, you can create an SDR disk only
 Simplified Disaster Recovery 815
Requirements for using Simplified Disaster Recovery

using ADK 10. For Windows Server 2019, you must use Windows ADK 1809
to create an SDR disk. If the Backup Exec server does not run on Windows
Server 2008 SP2 or later, or if the server does not have an Internet connection,
methods are provided to let you create the Simplified Recovery Disk.

Note: The recovery disk created with Windows ADK 8.1 does not detect the
Backup Exec storage folder (\BEData) if this folder is configured on the storage
pools and storage spaces on the Backup Exec Server. This problem happens
only when the Backup Exec server installed on Windows Server 2016 operating
system is not available and you want to perform an SDR local recovery from
the BEData folder.
The recovery disk created with Windows ADK 10 and ADK 8.1 does not detect
the Backup Exec Storage folder (\BEData) if this folder is configured on the
storage pools and storage spaces on the Backup Exec Server. This problem
happens only when the Backup Exec server installed on Windows Server 2019
operating system is not available and you want to perform an SDR Local recovery
from the BEData folder.
If you create the storage pools and spaces using the recovery disk created with
Windows ADK 10, then after system restore, the Windows Server 2012 and
Windows Server 2012 R2 operating systems does not detect the storage pools
and spaces.
If you create the storage pools and spaces using the recovery disk created with
Windows ADK 1809, then after system restore, all Windows 2016 and earlier
operating systems do not detect the storage pools and spaces.

■ 5 GB of disk space to download and install ADK.

■ 1 GB of disk space to store the required files and folders to create the ISO image.

Requirements for running the Recover This Computer

Wizard
The following items are required to run the Recover This Computer Wizard:
■ The Simplified Disaster Recovery disk image must be the same version of
Backup Exec as the Backup Exec server.
■ If the computer that you want to recover was backed up to a tape device,
deduplication storage, or to a virtual disk, then SDR cannot store the disaster
recovery information file with the backup sets. Instead, you must provide the
path to the default location or to the alternate location when the Recover This
Computer Wizard prompts you. The default location is C:<Backup Exec
 Simplified Disaster Recovery 816
Preparing computers for use with Simplified Disaster Recovery

install path>\Backup Exec\sdr\Data. If the file is unavailable, you cannot

recover the computer with SDR.
■ The backup set that contains all of the critical system components for the
computer that you want to restore.
■ The boot drive on the computer that you want to recover must have from 3-GB
to 5-GB of free space depending on the operating system and configuration.
If a blank screen appears and the computer does not restart after you use the
SDR disk, ensure that the boot drive has the necessary amount of free space.
Then, restart the computer again.
■ The target computer that you want to recover to must have an amount of RAM
that is equal to or greater than the minimum that the restored operating system
requires.
■ The target computer that you want to recover to must have disks with enough
free space to contain the data that you restore from the backup of critical
volumes. A volume is considered critical if it is required for the computer to start
successfully.
■ If you recover a Windows computer that has BitLocker encryption enabled, you
must turn on BitLocker encryption after the restore. See your Microsoft
documentation for more information on BitLocker drive encryption.
■ If the computer you recover contains a RAID setup, you may be required to
configure the RAID before you start it with the SDR disk. Use the computer
manufacturer's RAID software to configure the RAID system.
■ If you restore Windows with storage spaces and storage pools, you should be
aware of the possible restore scenarios.
See “Recovery notes for using Simplified Disaster Recovery with storage pools
and storage spaces” on page 859.
See “Creating a Simplified Disaster Recovery disk image” on page 827.
See “Recovering a computer with Simplified Disaster Recovery” on page 853.

Preparing computers for use with Simplified

Disaster Recovery
Prepare computers for use with Simplified Disaster Recovery (SDR) by performing
the following steps:
 Simplified Disaster Recovery 817
Preparing computers for use with Simplified Disaster Recovery

Table 21-1 Preparing computers for use with Simplified Disaster Recovery

Step Description More information

Step 1 Specify an alternate location where Backup Exec creates the disaster recovery
copies of the disaster recovery information file after a backup job that
information files are stored. includes all critical system components
completes successfully. Backup Exec then
stores the disaster recovery information file
in the default storage location with the
backup set on a disk storage or disk
cartridge device, and in the alternate
storage locations. Catalog entries from
subsequent backups are automatically
added to the disaster recovery information
file.
Warning: If you back up a computer to a
tape device, deduplication storage, or a
virtual disk, Backup Exec cannot store a
disaster recovery information file with the
backup set. You must have a disaster
recovery information file in an alternate
location to ensure that you can use SDR to
recover the computer.

See “Setting or changing the alternate

location for the disaster recovery information
file” on page 824.
 Simplified Disaster Recovery 818
Preparing computers for use with Simplified Disaster Recovery

Table 21-1 Preparing computers for use with Simplified Disaster Recovery
(continued)

Step Description More information

Step 2 Run the backup jobs that include By default, Backup Exec selects all critical
all critical system components system components when you select a
(SDR-enabled backups) for the computer for backup. When all critical
computers that you want to protect. system components are included in the
These are the backups for which backup job selections, the Simplified
the Simplified Disaster Recovery Disaster Recovery indicator on the backup
indicator is ON. selections appears as ON.
Note: For environments running If you deselect one or more critical system
the Central Admin Server feature, component files, the indicator appears as
run a database maintenance job OFF. It is recommended that you select the
before you run SDR-enabled entire computer for backup; otherwise,
backups. Otherwise, the central Backup Exec cannot create the
administration server denies system-specific disaster recovery
communication attempts from the information file.
managed Backup Exec servers.
Critical system components include the
See “Configuring database following:
maintenance and security”
■ System volume (including EFI and utility
on page 597.
partitions)
■ Boot volume (executing operating
system)
■ Services application volumes (boot,
system, and automatic startup)
■ System State devices and volumes
(including Active Directory, system files,
and so on)

See “How to ensure that backups are

enabled for Simplified Disaster Recovery”
on page 820.
 Simplified Disaster Recovery 819
Preparing computers for use with Simplified Disaster Recovery

Table 21-1 Preparing computers for use with Simplified Disaster Recovery
(continued)

Step Description More information

Step 3 Create additional copies of the Backup Exec stores the important disaster
disaster recovery information files recovery information files in the default path,
and store them in a safe place. the alternate location, and with the backup
set if disk storage or disk cartridge devices
are used as the destination storage. It is
recommended that you also make additional
copies of the files and store them in a safe
place. Without the disaster recovery
information files, you cannot recover Backup
Exec servers by using Simplified Disaster
Recovery (SDR). Having multiple copies of
the disaster recovery information files
ensures that you can successfully recover
Backup Exec servers with SDR.

By default, the disaster recovery information

files reside in the <Backup Exec
install path>\Backup
Exec\SDR\Data directory on the Backup
Exec server. Use Windows Explorer or
another Copy utility to copy the disaster
recovery information files from the default
location to another storage location of your
choice. Backup Exec does not automatically
update these copies, but they do let you
restore a computer to an older point-in-time
if the other disaster recovery files are not
available

Step 4 Use the Create Simplified Backup Exec generates alerts after each
Disaster Recovery Disk Wizard backup job until you create the Simplified
to create a disk image, and then a Disaster Recovery disk image. You can
bootable CD or DVD recovery disk. disable these alerts, but it is recommended
that you create the Simplified Disaster
Recovery disk image.

See “Creating a Simplified Disaster

Recovery disk image” on page 827.

If you install the Create Simplified Disaster

Recovery Wizard on a standalone server,
you cannot use the wizard to run Veritas
Update.
 Simplified Disaster Recovery 820
How to ensure that backups are enabled for Simplified Disaster Recovery

How to ensure that backups are enabled for

Simplified Disaster Recovery
By default, Backup Exec is configured to back up all of the critical system
components that you need to use Simplified Disaster Recovery to recover a
computer.
When the Simplified Disaster Recovery indicator for the backup selections is green,
or ON, it indicates that the critical system components are selected for backup. The
backup is SDR-enabled. If the indicator is gray, or OFF, then the backup is not
enabled for SDR. You can click the icon to select all of the necessary components
for disaster recovery, or to disable disaster recovery for backups created by this
job.
To ensure that a backup is enabled for Simplified Disaster Recovery, you can view
the backup selections that appear when you create or edit a backup job.
To ensure that backups are enabled for Simplified Disaster Recovery
1 On the Backup and Restore tab, create a new backup job or edit an existing
one.
2 On the Backup Definition Properties dialog box, on the selections pane, do
one of the following:
■ Ensure that the icon to the left of the computer name is green.
■ Click Edit, and ensure that the icon on the right is green, and that the text
indicates that Simplified Disaster Recovery is on.

Note: If you hover the mouse over the icon, the text indicates whether the
Simplified Disaster Recovery is on or off.

3 If the icon is not green, or if the text indicates that Simplified Disaster Recovery
is off, click the icon and then select the option Select all necessary
components for disaster recovery.
 Simplified Disaster Recovery 821
How to ensure that backups are enabled for Simplified Disaster Recovery

Figure 21-1 Simplified Disaster Recovery indicator is ON in the Backup

Definition Properties dialog box
 Simplified Disaster Recovery 822
How Simplified Disaster Recovery uses disaster recovery information files

Figure 21-2 Simplified Disaster Recovery indicator is ON in the Backup

Selections dialog box

See “Preparing computers for use with Simplified Disaster Recovery” on page 816.

How Simplified Disaster Recovery uses disaster

recovery information files
For each computer that you back up and for which the Simplified Disaster Recovery
indicator is ON, Backup Exec creates a disaster recovery information file. A disaster
recovery information file contains computer-specific information for the computer
that is backed up. Each time that a backup of all critical system components runs,
the disaster recovery information files are automatically updated. Each disaster
information recovery file uses the file name <computer_name>.DR. SDR uses the
computer-specific information that is contained in the file when you run the Recover
This Computer wizard. Without a disaster recovery information file, a recovery of
the computer is not possible with SDR.

Note: Backup Exec by default supports the latest three full SDR backup chains
required for system recovery using SDR. Each backup chain includes one full
backup set, its dependent incremental and differential backups, and their duplicate
backup sets.
 Simplified Disaster Recovery 823
How Simplified Disaster Recovery uses disaster recovery information files

A disaster recovery information file contains the following information for the
computer that is backed up:
■ Hardware-specific information, such as hard disk partition information, mass
storage controller information, and network interface card information.
■ A list of catalog entries that identify the backup sets and storage media that are
needed to recover the computer.
■ The Windows Automated System Recovery configuration information file (asr.xml)
required during the recovery process.
Backup Exec stores the disaster recovery information file in the following locations:
■ With the backup sets if the backup storage is disk storage or a disk cartridge
device.
■ On the Backup Exec server’s hard drive in the following path:

C:<Backup Exec install path>\Backup Exec\sdr\Data\

■ In an alternate location that you specify, on a different computer than the Backup
Exec server.

Note: It is recommended that you specify an alternate storage location. If the

Backup Exec server crashes, you cannot retrieve the disaster recovery information
file from the default location. However, you can retrieve it from the alternate location.
You should also create additional copies of the disaster recovery information files
and store them in a safe place. Use Windows Explorer or another Copy utility to
copy the disaster recovery information files from the default location to another
storage location of your choice. Backup Exec does not automatically update these
copies, but they do let you restore a computer to an older point-in-time if the other
disaster recovery files are not available.

If the disaster recovery information file is stored with the backup sets, then SDR
automatically uses that file to perform the recovery. If the backup sets are stored
on a tape storage device, deduplication storage, or on a virtual disk, then SDR
cannot store the file with the backup sets. Instead, you must provide the path to
the default location or the alternate location of the disaster recovery file when the
Recover This Computer wizard prompts you.
See “Setting or changing the alternate location for the disaster recovery information
file” on page 824.
See “Changing the default path for the disaster recovery information files”
on page 825.
 Simplified Disaster Recovery 824
Setting or changing the alternate location for the disaster recovery information file

Setting or changing the alternate location for the

disaster recovery information file
It is recommended that you specify an alternate location where Backup Exec can
store the disaster recovery information files. The disaster recovery information files
contain computer-specific information for each computer that you back up with
Simplified Disaster Recovery (SDR). When you recover a Backup Exec server from
a disaster, you must have the Backup Exec server's disaster recovery information
file available. Without it, you cannot use SDR to recover the Backup Exec server.
It is recommended that the alternate location be on another computer or on a
different physical drive than the default location. If the Backup Exec server's hard
drive is damaged, you can access a copy of the disaster recovery information from
the alternate location.You can specify a drive letter that is mapped to a network
share as the alternate location.
To use a remote computer’s hard drive as the alternate path, establish a valid
connection to the remote computer. Specify a UNC path as the alternate path, and
then check the directory to ensure that the disaster recovery information files are
copied.
For a clustered Backup Exec server or remote Backup Exec servers, specify an
alternate location on a shared drive or on a drive that is outside the cluster.
You should also create additional copies of the disaster recovery information files
and store them in a safe place.
See “How Simplified Disaster Recovery uses disaster recovery information files”
on page 822.
To set or change the alternate location for the disaster recovery information
file
1 Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2 In the left pane, select Simplified Disaster Recovery.
3 In the Alternate path field, enter the path where you want to store a copy of
the disaster recovery information file, or click Browse to navigate to a path.
4 Specify the logon account to use to access the alternate path.
5 Click OK.
See “Changing the default path for the disaster recovery information files”
on page 825.
 Simplified Disaster Recovery 825
Setting or changing the alternate location for the disaster recovery information file

Changing the default path for the disaster recovery information files
You can change the default path for the disaster recovery information files. However,
it is recommended that you do not change the default path.
Copies of the disaster recovery information files are necessary to automate the
recovery of a Backup Exec server.
Backup Exec automatically creates the disaster recovery information file during a
backup and stores a copy of it in the following path:

C:<Backup Exec install path>\Backup Exec\sdr\Data\

If you change the disaster recovery data path, ensure that you copy the existing
disaster recovery information files to the new path. The copies let you recover a
computer with the previous SDR backups.
See “How Simplified Disaster Recovery uses disaster recovery information files”
on page 822.
To change the default path for the disaster recovery information files
1 Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2 In the left pane, select Simplified Disaster Recovery.
3 In the Path field, change the path to the location where you want to store the
disaster recovery information file, or click Browse to navigate to a location.
4 Click OK.
See “Setting or changing the alternate location for the disaster recovery information
file” on page 824.

Disaster recovery information file data paths

Simplified Disaster Recovery (SDR) creates the disaster recovery information files
that are required for recovery.
See “How Simplified Disaster Recovery uses disaster recovery information files”
on page 822.
 Simplified Disaster Recovery 826
Setting or changing the alternate location for the disaster recovery information file

Table 21-2 Storage locations for the disaster recovery information file

Item Description

Path Indicates a directory path where you want to

store the disaster recovery information files
for the computers that you back up. Backup
Exec automatically creates the files after a
backup job runs for which all critical system
components are selected. Backup Exec then
stores the disaster information recovery files
in the following default location:

C:<Backup Exec install path>\Backup

Exec\sdr\Data\<computer name>.dr.
Note: It is recommended that you do not
change the default path.

Alternate path Indicates an alternate path where you can

store copies of the disaster recovery
information files for the computers that you
back up. Backup Exec automatically creates
or updates the files after a backup job runs
for which all critical system components are
selected. Backup Exec then stores copies of
the disaster recovery information files in this
location.

It is recommended that you specify an

alternate path that is not on the Backup Exec
server, or that is on a different physical drive
than the default location. You can specify a
drive letter mapped to a network share as the
alternate location. If the Backup Exec server’s
hard drive is unavailable during a recovery,
you can copy the disaster recovery
information file from the alternate path to any
location to recover the failed computer.

To use a remote computer’s hard drive as the

alternate path, establish a valid connection
to the remote computer. Specify a UNC path
as the alternate path, and then check the
directory to ensure that the disaster recovery
information files are copied.
 Simplified Disaster Recovery 827
Creating a Simplified Disaster Recovery disk image

Creating a Simplified Disaster Recovery disk

image
The Create Simplified Disaster Recovery Disk Wizard guides you through the
process of creating a startup recovery disk image that you can use to recover backed
up computers.
The following items are required to create the Simplified Disaster Recovery disk
image:
■ 5 GB of disk space to download and install the ADK.
■ 1 GB of disk space to store the required files and folders to create the ISO image.

Warning: The ADK download may take few hours depending on your network
speed.

After you run Simplified Disaster Recovery-enabled backups of the computers that
you want to protect, run the Create Simplified Disaster Recovery Disk Wizard
to create the Simplified Disaster Recovery disk image. Simplified Disaster
Recovery-enabled backups are those backups that display the green indicator on
the backup properties pane that indicates the critical system components on the
computer are selected.
See “How to ensure that backups are enabled for Simplified Disaster Recovery”
on page 820.
For Windows Server 2008 SP2 to Windows Server 2016, the wizard installs the
ADK. For Windows Server 2019, you must manually download and install the ADK.
The wizard uses the required files and folders from the ADK to create a startup
recovery disk image in ISO format. You can then burn the image to a CD or DVD
by using a third-party image burning application. For disaster recovery of a computer,
you use the Simplified Disaster Recovery disk to start the computer, and then to
recover it.
When you create the recovery disk, you can add language and time zone selections.
You can also select the computers for which you want to add network and storage
drivers. You can further customize the recovery disk by adding new OEM drivers.
 Simplified Disaster Recovery 828
Creating a Simplified Disaster Recovery disk image

Note: If you create the Simplified Disaster Recovery disk image before you run
backups, the drivers for the backed-up computers are not included on the recovery
disk. You must create a new recovery disk if you want the drivers of the backed-up
computers to be included on the recovery disk. You can then specify the existing
recovery disk as the source, and then select the computers for which you want to
add the drivers to the recovery disk.

Depending on your environment, different methods are available for you to create
the Simplified Disaster Recovery disk image.

Table 21-3 Methods for creating the Simplified Disaster Recovery disk image

Environment Method

If the Backup Exec server runs on Windows See the section called “Creating a Simplified
Server 2019 Disaster Recovery disk image if the Backup
Exec server runs on Windows Server 2019”
on page 828.

If the Backup Exec server runs on Windows See the section called “Creating a Simplified
Server 2008 R2 to Windows Server 2016 Disaster Recovery disk image if the Backup
Exec server runs on Windows Server 2008
R2 to Windows Server 2016” on page 831.

If the Backup Exec server runs on Windows See the section called “Creating a Simplified
Server 2008 SP2 Disaster Recovery disk image if the Backup
Exec server runs on Windows Server 2008
SP2” on page 834.

If the Backup Exec server is not available See the section called “Creating a Simplified
Disaster Recovery disk image if the Backup
Exec server is not available” on page 838.

If the Backup Exec server on which you want See the section called “Creating a Simplified
to create the Simplified Disaster Recovery Disaster Recovery disk image on a Backup
disk image does not have an Internet Exec server that does not have an internet
connection and does not have ADK installed connection and does not have ADK or
Windows Preinstallation Environment
installed” on page 841.

Creating a Simplified Disaster Recovery disk image if the

Backup Exec server runs on Windows Server 2019
If the Microsoft Windows Assessment and Deployment Kit (ADK) is not already
installed on this server, you have to manually download and install Windows ADK
1809 using the following link:
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install?ocid=tia-235208000
 Simplified Disaster Recovery 829
Creating a Simplified Disaster Recovery disk image

It is recommended that you download and install Windows ADK 1809 before you
launch the Create Simplified Disaster Recovery Disk Wizard.
If Windows ADK 1809 is already installed, the Create Simplified Disaster Recovery
Disk Wizard detects the ADK installed and proceeds to create the recovery disk.
To create a Simplified Disaster Recovery disk image if the Backup Exec server
runs on Windows Server 2019
1 Do any of the following:
■ On the Backup and Restore tab, in the Restores group, click Create
Disaster Recovery Disk.
■ Click the Backup Exec button, click Configuration and Settings, and then
click Create Disaster Recovery Disk.
■ On the Home tab, in the Simplified Disaster Recovery panel, click Create
Disaster Recovery Disk.
■ Click the Start button, and then click Create Disaster Recovery Disk.

2 Review the Welcome panel of the Simplified Disaster Recovery Disk

Creation wizard, and then click Next.
3 Do one of the following:

To create a Simplified Click Create a new Simplified Disaster Recovery Disk

Disaster Recovery disk image image (.iso).
for the first time

To select network and Do the following in the order listed:

storage drivers from an
■ Click From a previous CD or DVD, or from a
existing Simplified Disaster
folder.
Recovery disk CD or DVD, or
■ Enter the location of the previous recovery disk, or
from a folder
type the path to a folder that contains the files that
are extracted from the recovery disk.

To select network and Do the following in the order listed:

storage drivers from an
■ Click From an image (.iso) file.
existing image (.iso) file
■ Enter the location of the recovery image file.

4 Click Next.
 Simplified Disaster Recovery 830
Creating a Simplified Disaster Recovery disk image

5 Do one of the following:

If the Windows The Simplified Disaster Recovery Disk Creation wizard detects the
ADK 1809 is installed version of ADK and the wizard continues with the recovery
already disk creation process.
installed on the
Note: If you have created an SDR using ADK 10.0, you can customize
computer
the SDR even if you have Windows ADK 1809 installed on a Windows
Server 2019 operating system.

If the Windows The Simplified Disaster Recovery Disk Creation wizard displays the
ADK 1809 is following link to manually download and install Windows ADK 1809.
not installed on
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install?ocid=tia-235208000
the computer
On the Windows ADK 1809 page, install the Windows ADK Insider
and Windows Preinstallation Environment components.

For the Windows ADK Insider component, on the Windows

Assessment and Deployment Kit wizard, follow the prompts to install
the ADK. On the Select the features you want to install page, select
only the Deployment Tools check box.

After the ADK is installed, install the Windows Preinstallation

Environment component by accepting the recommended defaults in
the wizard.

After both components are installed, launch the Simplified Disaster

Recovery Disk Creation wizard again.

If the ADK 10.0 The Simplified Disaster Recovery Disk Creation wizard detects that
is installed on ADK 10.0 version is installed and the ADK update screen is displayed.
the computer
The wizard informs you that this is not the latest available version of
ADK but you can proceed with the SDR disk creation. Confirm that
you want to continue using ADK 10. If you continue, it may not support
all the features of Windows Server 2019.

After you select the check box and click Next, the wizard continues
with the recovery disk creation process.

6 Specify the startup options that you want when you recover a computer, and
then click Next.
7 Do one of the following:

To add network drivers and Select the computers for which you want to add the
storage drivers for the drivers to the recovery disk, and then click Next.
computers for which you ran
SDR backups
 Simplified Disaster Recovery 831
Creating a Simplified Disaster Recovery disk image

To add network drivers and Do the following in the order listed:

storage drivers that were
■ On the Select computers to use the drivers from
found on the computers for
panel, click Next.
which you ran SDR backups
■ On the Drivers to Include panel, select the drivers
that are not already included
that you want to include in the custom recovery disk,
in the source image
and then click Next.

To add network drivers and Do the following in the order listed:

storage drivers from OEM
■ On the Select computers to use the drivers from
media
panel, click Next.
■ On the Drivers to Include panel, click Add Driver,
navigate to the location of the media, select it, and
then click Open.
■ When the drivers display on the Select computers
to use the drivers from panel, click Next.

8 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: If you use any non-English characters in the volume label, then those
characters are not properly displayed when you mount the .iso image.

Note: It is recommended that you store the image that you want to burn on
the computer where the CD image or DVD image burning application is installed.
By default, the location is as follows:C:<Backup Exec install path>\Backup
Exec\sdr\CustomSDRImage.iso

9 Review the summary panel, and then click Create Image.

10 After the Simplified Disaster Recovery disk CD or DVD image is created,
clickNext, and then click Finish.
11 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.

Creating a Simplified Disaster Recovery disk image if the

Backup Exec server runs on Windows Server 2008 R2 to
Windows Server 2016
If the Microsoft Windows Assessment and Deployment Kit (ADK) is not already
installed on this server, then the Create Simplified Disaster Recovery Disk Wizard
 Simplified Disaster Recovery 832
Creating a Simplified Disaster Recovery disk image

guides you through the download and installation of the ADK. The ADK installation
defaults are already selected. It is recommended that you use these defaults.

Note: Backup Exec supports only ADK 10 on Windows Server 2008 R2 to Windows
Server 2016. If Windows ADK is not installed on the system, the Create Simplified
Disaster Recovery wizard downloads and installs Windows ADK 10.

To create a Simplified Disaster Recovery disk image if the Backup Exec server
runs on Windows Server 2008 R2 or later
1 Do any of the following:
■ On the Backup and Restore tab, in the Restores group, click Create
Disaster Recovery Disk.
■ Click the Backup Exec button, click Configuration and Settings, and then
click Create Disaster Recovery Disk.
■ On the Home tab, in the Simplified Disaster Recovery panel, click Create
Disaster Recovery Disk.
■ Click the Start button, and then click Create Disaster Recovery Disk.

2 Review the Welcome panel of the Simplified Disaster Recovery Disk

Creation wizard, and then click Next.
3 Do one of the following:

To create a Simplified Disaster Recovery Click Create a new Simplified Disaster

disk image for the first time Recovery Disk image (.iso).

To select network and storage drivers from Do the following in the order listed:
an existing Simplified Disaster Recovery
■ Click From a previous CD or DVD, or
disk CD or DVD, or from a folder
from a folder.
■ Enter the location of the previous
recovery disk, or type the path to a
folder that contains the files that are
extracted from the recovery disk.

To select network and storage drivers from Do the following in the order listed:
an existing image (.iso) file
■ Click From an image (.iso) file.
■ Enter the location of the recovery image
file.

4 Click Next.
5 Do one of the following:
 Simplified Disaster Recovery 833
Creating a Simplified Disaster Recovery disk image

If the ADK is already installed on the If an ADK version other than ADK 10 is
computer installed on the operating system, the
Create Simplified Disaster Recovery wizard
detects the Windows ADK version and
informs the user that a new SDR disk
cannot be created using the installed ADK
version.

If ADK 10 is installed, the wizard informs

you that this is not the latest available
version of ADK but you can proceed with
the SDR disk creation. Confirm that you
want to continue using ADK 10.

After you select the check box and click

Next, the wizard continues with the
recovery disk creation process.

Continue with step 6

If the ADK is not installed on the computer If Windows ADK is not installed on the
system, the Create Simplified Disaster
Recovery wizard downloads and installs
Windows ADK 10.

Do the following in the order listed:

■ Click Next to continue to the ADK

download and installation wizard.
■ On the ADK wizard panels, click Next
to accept the recommended defaults.
Note: The ADK download may take
few hours, depending on the
bandwidth.
■ After the ADK is installed, click Close
to continue with the Create Simplified
Disaster Recovery Disk Wizard.

6 Specify the startup options that you want when you recover a computer, and
then click Next.
7 Do one of the following:

To add network drivers and storage drivers Select the computers for which you want
for the computers for which you ran SDR to add the drivers to the recovery disk, and
backups then click Next.
 Simplified Disaster Recovery 834
Creating a Simplified Disaster Recovery disk image

To add network drivers and storage drivers Do the following in the order listed:
that were found on the computers for which
■ On the Select computers to use the
you ran SDR backups that are not already
drivers from panel, click Next.
included in the source image
■ On the Drivers to Include panel, select
the drivers that you want to include in
the custom recovery disk, and then
click Next.

To add network drivers and storage drivers Do the following in the order listed:
from OEM media
■ On the Select computers to use the
drivers from panel, click Next.
■ On the Drivers to Include panel, click
Add Driver, navigate to the location of
the media, select it, and then click
Open.
■ When the drivers display on the Select
computers to use the drivers from
panel, click Next.

8 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: If you use any non-English characters in the volume label, then those
characters are not properly displayed when you mount the .iso image.

Note: It is recommended that you store the image that you want to burn on
the computer where the CD image or DVD image burning application is installed.
By default, the location is as follows:C:<Backup Exec install path>\Backup
Exec\sdr\CustomSDRImage.iso

9 Review the summary panel, and then click Create Image.

10 After the Simplified Disaster Recovery disk CD or DVD image is created,
clickNext, and then click Finish.
11 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.

Creating a Simplified Disaster Recovery disk image if the

Backup Exec server runs on Windows Server 2008 SP2
If the Microsoft Windows Assessment and Deployment Kit (ADK) is not already
installed on this server, then the Create Simplified Disaster Recovery Disk Wizard
 Simplified Disaster Recovery 835
Creating a Simplified Disaster Recovery disk image

guides you through the download and installation of the ADK. The ADK installation
defaults are already selected. It is recommended that you use these defaults.

Note: Backup Exec supports Windows ADK 8.1 on Windows 2008 SP2. If Windows
ADK is not installed on a Windows 2008 SP2 system, the Create Simplified
Disaster Recovery wizard downloads and installs Windows ADK 8.1.

To create a Simplified Disaster Recovery disk image if the Backup Exec server
runs on Windows Server 2008 SP2
1 Do any of the following:
■ On the Backup and Restore tab, in the Restores group, click Create
Disaster Recovery Disk.
■ Click the Backup Exec button, click Configuration and Settings, and then
click Create Disaster Recovery Disk.
■ On the Home tab, in the Simplified Disaster Recovery panel, click Create
Disaster Recovery Disk.
■ Click the Start button, and then click Create Disaster Recovery Disk.

2 Review the Welcome panel of the Simplified Disaster Recovery Disk

Creation wizard, and then click Next.
3 Do one of the following:

To create a Simplified Disaster Recovery Click Create a new Simplified Disaster

disk image for the first time Recovery Disk image (.iso).

To select network and storage drivers from Do the following in the order listed:
an existing Simplified Disaster Recovery
■ Click From a previous CD or DVD, or
disk CD or DVD, or from a folder
from a folder.
■ Enter the location of the previous
recovery disk, or type the path to a
folder that contains the files that are
extracted from the recovery disk.

To select network and storage drivers from Do the following in the order listed:
an existing image (.iso) file
■ Click From an image (.iso) file.
■ Enter the location of the recovery image
file.

4 Click Next.
5 Do one of the following:
 Simplified Disaster Recovery 836
Creating a Simplified Disaster Recovery disk image

If the ADK is already installed on the If Windows ADK 8.0 is already installed,
computer the recovery disk wizard warns the user
that user cannot create a new SDR using
this ADK version; however, user can
customize the recovery disk. User can
either exit from the wizard or user can
download ADK 8.1, and customize the disk.

If Windows ADK 8.1 is already installed,

the recovery disk wizard first warns the
user about the Windows ADK version; and
if user wants to continue, the wizard
continues with the recovery disk creation
process.

Continue with step 6

If the ADK is not installed on the computer If Windows ADK is not installed on the
system, the Create Simplified Disaster
Recovery wizard downloads and installs
Windows ADK 8.1.
Do the following in the order listed:

■ Click Next to continue to the ADK

download and installation wizard.
■ On the ADK wizard panels, click Next
to accept the recommended defaults.
Note: The ADK download may take
few hours, depending on the
bandwidth.
■ After the ADK is installed, click Close
to continue with the Create Simplified
Disaster Recovery Disk Wizard.

6 Specify the startup options that you want when you recover a computer, and
then click Next.
7 Do one of the following:

To add network drivers and storage drivers Select the computers for which you want
for the computers for which you ran SDR to add the drivers to the recovery disk, and
backups then click Next.
 Simplified Disaster Recovery 837
Creating a Simplified Disaster Recovery disk image

To add network drivers and storage drivers Do the following in the order listed:
that were found on the computers for which
■ On the Select computers to use the
you ran SDR backups that are not already
drivers from panel, click Next.
included in the source image
■ On the Drivers to Include panel, select
the drivers that you want to include in
the custom recovery disk, and then
click Next.

To add network drivers and storage drivers Do the following in the order listed:
from OEM media
■ On the Select computers to use the
drivers from panel, click Next.
■ On the Drivers to Include panel, click
Add Driver, navigate to the location of
the media, select it, and then click
Open.
■ When the drivers display on the Select
computers to use the drivers from
panel, click Next.

8 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: If you use any non-English characters in the volume label, then those
characters are not properly displayed when you mount the .iso image.

Note: It is recommended that you store the image that you want to burn on
the computer where the CD image or DVD image burning application is installed.
By default, the location is as follows:
C:<Backup Exec install path>\Backup Exec\sdr\CustomSDRImage.iso

9 Review the summary panel, and then click Create Image.

10 After the Simplified Disaster Recovery disk CD or DVD image is created, click
Next, and then click Finish.
11 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.
 Simplified Disaster Recovery 838
Creating a Simplified Disaster Recovery disk image

Creating a Simplified Disaster Recovery disk image if the

Backup Exec server is not available
The Microsoft Assessment and Deployment Kit (ADK) installation is supported only
on Windows Server 2008 SP2 and later. If the Backup Exec server does not run
on Windows Server 2008 SP2 or later, or if the server is not available, you can use
the Backup Exec installation media to install the Create Simplified Disaster
Recovery Disk Wizard and the Remote Administration Console on a standalone
server that runs Windows Server 2008 SP2 or later.
The Create Simplified Disaster Recovery Disk Wizard guides you through the
download and installation of the ADK. The ADK installation defaults are already
selected. It is recommended that you use these defaults. You can then create the
recovery disk by connecting to a remote Backup Exec server, as guided by the
wizard.
To create a Simplified Disaster Recovery disk image if the Backup Exec server
is not available
1 Insert the Backup Exec installation media into a server that runs Windows
Server 2008 SP2 or later.
2 From the installation media browser, click Installation.
3 Click Simplified Disaster Recovery Disk Creation Wizard, and then click
Install.

Note: The Simplified Disaster Recovery Disk Creation Wizard and the
Backup Exec Remote Administration Console are installed.

4 Accept the terms of the license agreement, and then click Next.
5 Accept the default installation location, or specify a new location, and then click
Next.
6 By default, after the computer is restarted, the Create Simplified Disaster
Recovery Disk Wizard starts; if you unchecked the default, to start the wizard,
click Start > All Programs > Veritas Backup Exec >Create Disaster
Recovery Disk.
7 On the Welcome panel of the Simplified Disaster Recovery Disk Creation
wizard, click Connect to a Backup Exec server.
8 Specify a Backup Exec server machine name or IP address, enter your
credentials and the domain, and then click Next.
9 Do one of the following:
 Simplified Disaster Recovery 839
Creating a Simplified Disaster Recovery disk image

To create a Simplified Disaster Recovery Click Create a new Simplified Disaster

disk image for the first time Recovery Disk Image (.iso).

To select network and storage drivers from Do the following in the order listed:
an existing Simplified Disaster Recovery
■ Click From a previous CD or DVD, or
disk CD or DVD, or from a folder
from a folder.
■ Enter the location of the previous
recovery disk, or type the path to a
folder that contains the files that are
extracted from the recovery disk.

To select network and storage drivers from Do the following in the order listed:
an existing image (.iso) file
■ Click From an image (.iso) file.
■ Enter the location of the recovery image
file.

10 Click Next.
11 Do one of the following:

If the ADK is already installed on this Continue with step 12

computer

If the ADK is not installed on this computer Do the following in the order listed:

■ Click Next to continue to the ADK

download and installation wizard.
■ On the ADK wizard panels, click Next
to accept the recommended defaults.
Note: The ADK download may take
few hours depending on your network
speed.
■ After the ADK is installed, click Close
to continue with the Create Simplified
Disaster Recovery Disk Wizard.

12 Specify the startup options that you want when you recover a computer, and
then click Next.
13 Do one of the following:.

To add network drivers and storage drivers Select the computers for which you want
from the computers for which you ran SDR to add the drivers to the recovery disk, and
backups then click Next
 Simplified Disaster Recovery 840
Creating a Simplified Disaster Recovery disk image

To add network drivers and storage drivers Do the following in the order listed:
that were found on the computers for which
■ On the Select computers to use the
you ran SDR backups that are not already
drivers from panel, click Next.
included in the source image
■ On the Drivers to Include panel, select
the drivers that you want to include on
the custom recovery disk, and then
click Next.

To add network drivers and storage drivers Do the following in the order listed:
from OEM media
■ On the Select computers to use the
drivers from panel, click Next.
■ On the Drivers to Include panel, click
Add Driver, navigate to the location of
the media, select it, and then click
Open.
■ When the drivers display on the Select
computers to use the drivers from
panel, click Next.

To add a computer to the list Do the following in the order listed:

■ Click Add DR file.

■ Navigate to the location of the DR file,
select it, and then click OK.
■ On the Select computers to use the
drivers from screen, select the
computer that you added, and then
click Next.

14 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: It is recommended that you store the image that you want to burn in a
location on the computer where the CD image or DVD image burning application
is installed. By default, the location is as follows:
C:<Backup Exec install path>\Backup Exec\sdr\CustomSDRImage.iso

15 Review the summary panel, and then click Create Image.

16 After the Simplified Disaster Recovery disk CD or DVD image is created, click
Next, and then click Finish.
17 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.
 Simplified Disaster Recovery 841
Creating a Simplified Disaster Recovery disk image

Creating a Simplified Disaster Recovery disk image on a

Backup Exec server that does not have an internet
connection and does not have ADK or Windows
Preinstallation Environment installed
For Windows ADK 10 and ADK 8.1, you can download the ADK executable file to
a computer that has Internet access, and then copy the downloaded files to the
computer on which you want to install ADK. Then, you can run the Simplified
Disaster Recovery Disk Creation wizard to create the recovery disk.
For Windows ADK 1809, you can download the ADK and Windows Preinstallation
Environment executable files to a computer that has Internet access, and then copy
the downloaded files to the computer on which you want to install the ADK and
Windows Preinstallation Environment. Then, you can run the Simplified Disaster
Recovery Disk Creation wizard to create the recovery disk.
To create a Simplified Disaster Recovery disk image on a Backup Exec server
with Windows Server 2019 installed that does not have an Internet connection
and does not have Windows ADK 1809 and Windows Preinstallation
Environment installed
1 On a computer that has an Internet connection, for Windows ADK 1809,
manually download and install Windows ADK 1809 using the following link.
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install?ocid=tia-235208000
2 After the download is complete, verify that the adksetup.exe file and the
Installers folder have been downloaded to the computer.
3 Copy the downloaded files and folder to the computer on which you want to
install ADK.
4 Start adksetup.exe from the copied folder.
5 On the ADK Specify Location panel, click Install the Assessment and
Deployment Kit to this computer, enter the path to which you want to install
the ADK, and then click Next.
6 Click Accept to accept the terms of the license agreement.
7 On the ADK Select the features you want to install panel, click Deployment
Tools, and then click Install.
Complete the ADK installation.
8 Verify that the adkwinpesetup.exe file and the Installers folder have been
downloaded to the computer.
9 Copy the downloaded files and folder to the computer on which you want to
install the preinstallation environment.
10 Start adkwinpesetup.exe from the copied folder.
 Simplified Disaster Recovery 842
Creating a Simplified Disaster Recovery disk image

11 On the ADK Specify Location panel, click Install the Assessment and
Deployment Kit Windows Preinstallation Environment Add-ons to this
computer, enter the path to which you want to install the preinstallation
environment, and then click Next.
12 Click Accept to accept the terms of the license agreement.
13 On the preinstallation environment Select the features you want to install
panel, select Windows Preinstallation Environment (Windows PE), and
then click Install.
14 After the installation is complete, on the Backup Exec server to which you
installed the ADK and preinstallation environment, do any of the following:
■ On the Backup and Restore tab, in the Restores group, click Create
Disaster Recovery Disk.
■ Click the Backup Exec button, click Configuration and Settings, and then
click Create Disaster Recovery Disk.
■ On the Home tab, in the Simplified Disaster Recovery panel, click Create
Disaster Recovery Disk.
■ Click the Start button, and then click Create Disaster Recovery Disk.

15 Review the Welcome panel of the Simplified Disaster Recovery Disk

Creation wizard, and then click Next.
16 Do any of the following:

To create a Simplified Disaster Click Create a new Simplified Disaster Recovery

Recovery disk image for the first Disk image (.iso).
time

To select network and storage Do the following in the order listed:

drivers from an existing Simplified
■ Click From a previous CD or DVD, or from
Disaster Recovery disk CD or DVD,
a folder.
or from a folder
■ Enter the location of the previous recovery disk,
or type the path to a folder that contains the
files that are extracted from the recovery disk.

To select network and storage Do the following in the order listed:

drivers from an existing image
■ Click From an image (.iso) file.
(.iso) file
■ Enter the location of the recovery image file.

17 Click Next.
18 Specify the startup options that you want when you recover a computer, and
then click Next.
 Simplified Disaster Recovery 843
Creating a Simplified Disaster Recovery disk image

19 Do one of the following:

To add network drivers and Select the computers for which you want to add
storage drivers for the computers the drivers to the recovery disk, and then click
for which you ran SDR backups Next.

To add network drivers and Do the following in the order listed:

storage drivers that were found on
■ On the Select computers to use the drivers
the computers for which you ran
from panel, click Next.
SDR backups that are not already
■ On the Drivers to Include panel, select the
included in the source image
drivers that you want to include in the custom
recovery disk, and then click Next.

To add network drivers and Do the following in the order listed:

storage drivers from OEM media
■ On the Select computers to use the drivers
from panel, click Next.
■ On the Drivers to Include panel, click Add
Driver, navigate to the location of the media,
select it, and then click Open.
■ When the drivers display on the panel, click
Next.

20 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: It is recommended that you store the image that you want to burn on
the computer where the CD image or DVD image burning application is installed.
By default, the location is as follows: C:<Backup Exec install path>\Backup
Exec\sdr\CustomSDRImage.iso.

21 Review the summary panel, and then click Create Image.

22 After the Simplified Disaster Recovery disk CD or DVD image is created, click
Next, and then click Finish.
23 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.
 Simplified Disaster Recovery 844
Creating a Simplified Disaster Recovery disk image

To create a Simplified Disaster Recovery disk image on a Backup Exec server

that does not have an Internet connection and does not have ADK 10 or ADK
8.1 installed
1 On a computer that has an Internet connection, click the following link to
download the adksetup.exe:
For Windows ADK 10 https://go.microsoft.com/fwlink/p/?LinkId=526740 (ADK
10.1.14393.0)
For Windows ADK 8.1 http://go.microsoft.com/fwlink/?LinkId=293840 (ADK
8.100.26866.0)
2 Run the adksetup.exe.
3 On the ADK Specify Location panel, click Download the Assessment and
Deployment Kit for installation on a separate computer, enter the path to
the Backup Exec server to which you want to install the ADK components, and
then click Next.
4 Click Yes or No to join the Microsoft Customer Experience Improvement
Program, and then click Next.
5 Click Accept to accept the terms of the license agreement and to start the
ADK download.
6 After the download is complete, verify that the adksetup.exe file and the
Installers folder have been downloaded to the computer.
7 Copy the downloaded files and folder to the computer on which you want to
install ADK.

Note: ADK installation is supported only on Windows Server 2008 SP2 and
later.

8 Start adksetup.exe from the copied folder.

9 On the ADK Specify Location panel, click Install the Assessment and
Deployment Kit to this computer, enter the path to which you want to install
the ADK, and then click Next.
10 Click Accept to accept the terms of the license agreement.
11 On the ADK Select the features you want to install panel, select Deployment
Tools and Windows Preinstallation Environment (Windows PE), and then
click Install.
12 After the installation is complete, on the Backup Exec server to which you
installed the ADK, do any of the following:
 Simplified Disaster Recovery 845
Creating a Simplified Disaster Recovery disk image

■ On the Backup and Restore tab, in the Restores group, click Create
Disaster Recovery Disk.
■ Click the Backup Exec button, click Configuration and Settings, and then
click Create Disaster Recovery Disk.
■ On the Home tab, in the Simplified Disaster Recovery panel, click Create
Disaster Recovery Disk.
■ Click the Start button, and then click Create Disaster Recovery Disk.

13 Review the Welcome panel of the Simplified Disaster Recovery Disk

Creation wizard, and then click Next.
14 Do any of the following:

To create a Simplified Disaster Recovery Click Create a new Simplified Disaster

disk image for the first time Recovery Disk image (.iso).

To select network and storage drivers from Do the following in the order listed:
an existing Simplified Disaster Recovery
■ Click From a previous CD or DVD, or
disk CD or DVD, or from a folder
from a folder.
■ Enter the location of the previous
recovery disk, or type the path to a
folder that contains the files that are
extracted from the recovery disk.

To select network and storage drivers from Do the following in the order listed:
an existing image (.iso) file
■ Click From an image (.iso) file.
■ Enter the location of the recovery image
file.

15 Click Next.
16 Specify the startup options that you want when you recover a computer, and
then click Next.
17 Do one of the following:

To add network drivers and storage drivers Select the computers for which you want
for the computers for which you ran SDR to add the drivers to the recovery disk, and
backups then click Next.
 Simplified Disaster Recovery 846
Creating a Simplified Disaster Recovery disk image

To add network drivers and storage drivers Do the following in the order listed:
that were found on the computers for which
■ On the Select computers to use the
you ran SDR backups that are not already
drivers from panel, click Next.
included in the source image
■ On the Drivers to Include panel, select
the drivers that you want to include in
the custom recovery disk, and then
click Next.

To add network drivers and storage drivers Do the following in the order listed:
from OEM media
■ On the Select computers to use the
drivers from panel, click Next.
■ On the Drivers to Include panel, click
Add Driver, navigate to the location of
the media, select it, and then click
Open.
■ When the drivers display on the panel,
click Next.

18 Type the volume label and the path for the image (.iso) file to specify the location
to store the startup image, and then click Next.

Note: It is recommended that you store the image that you want to burn on
the computer where the CD image or DVD image burning application is installed.
By default, the location is as follows: C:<Backup Exec install path>\Backup
Exec\sdr\CustomSDRImage.iso

19 Review the summary panel, and then click Create Image.

20 After the Simplified Disaster Recovery disk CD or DVD image is created, click
Next, and then click Finish.
21 Burn the startup ISO 9660 image to a CD or DVD by using a third-party image
burning application.

Contents of the Simplified Disaster Recovery disk image

The Simplified Disaster Recovery disk image provides the Recover This Computer
wizard that guides you through the steps to recover a computer.
The Simplified Disaster Recovery disk image also includes the tools that you can
use to manage the server's network configuration while in the recovery environment.
Other utilities are included on the disk that you can use for additional recovery
 Simplified Disaster Recovery 847
Creating a Simplified Disaster Recovery disk image

environment operations, such as dynamic loading of drivers, and accessing a

command prompt.
Network tools include the following menu items:
■ Start My Networking Services
■ Map a Network Drive
■ Configure Network Connection Settings
■ Run IP Config Utility
■ Ping a Remote Computer
Utility tools include the following menu items:
■ Gather Log Files for Technical Support
■ View Log File
■ Start PowerShell
■ Start Command Prompt
■ Edit the Windows boot.ini File
■ Load a Driver
■ Select Keyboard
Simplified Disaster Recovery also provides you with a hard disk configuration tool
called Advanced Disk Configuration. Advanced Disk Configuration lets you run
advanced hard disk operations on the computer that you want to recover.
For example, you can do tasks such as:
■ Create or delete volumes.
■ Resize a volume.
■ Convert a basic hard disk to a dynamic disk.
■ Change or assign drive letters.
■ Create spanned, striped, and mirrored volumes.
See “Advanced Disk Configuration on the Recover This Computer Wizard”
on page 864.
See “Requirements for using Simplified Disaster Recovery ” on page 813.
 Simplified Disaster Recovery 848
Creating a Simplified Disaster Recovery disk image

User scenarios when a user starts the Create Recovery Disk Wizard
When a user starts the Create Simplified Disaster Recovery Disk Wizard, the
wizard first internally checks whether Windows ADK is already installed on the
system. Refer the table for a high-level sequence of events.

Table 21-4 User scenarios when a user starts the Create Recovery Disk
Wizard

Windows If Windows ADK is not installed If Windows ADK is installed

server version

Windows Server If Windows ADK is not installed, the If Windows ADK is installed, the
2008 SP2 Simplified Disaster Recovery Disk Simplified Disaster Recovery Disk
Creation wizard downloads Windows Creation wizard verifies if the
ADK 8.1 from the Microsoft Web site. Windows ADK version is 8.1. If
After Windows ADK 8.1 download ADK 8.1 is installed, the wizard
and install, the wizard starts creating informs the user that this is not the
the SDR disk. latest ADK version but the user
can proceed with the SDR disk
creation.

If the Windows ADK version is

below 8.1, the wizard displays a
warning message to the user to
download Windows ADK 8.1 from
the Microsoft Web site, and then
proceed with the SDR disk
creation. Wizard does not support
creating a new SDR disk using
ADK 8.0.
 Simplified Disaster Recovery 849
Creating a Simplified Disaster Recovery disk image

Table 21-4 User scenarios when a user starts the Create Recovery Disk
Wizard (continued)

Windows If Windows ADK is not installed If Windows ADK is installed

server version

Windows Server If Windows ADK is not installed, the If Windows ADK is installed, the
2008 R2 Simplified Disaster Recovery Disk Simplified Disaster Recovery Disk
Creation wizard downloads Windows Creation wizard verifies if the
ADK 10 from the Microsoft Web site. Windows ADK version is 10. If
After Windows ADK 10 download and ADK 10 is installed, the wizard
install, the wizard starts creating the informs the user that this is not the
SDR disk. latest ADK version but the user
can proceed with SDR disk
creation.

If the Windows ADK version is

below 10, the wizard displays an
informational message to the user
to download Windows ADK 10
from the Microsoft Web site and
then proceed with the SDR disk
creation. Wizard does not support
creating a new disk using ADK 8.0
or ADK 8.1.

Windows Server Same as Windows 2008 R2 Same as Windows 2008 R2

2012

Windows Server Same as Windows 2008 R2 Same as Windows 2008 R2

2012 R2

Windows Server Same as Windows 2008 R2 Same as Windows 2008 R2

2016
 Simplified Disaster Recovery 850
Preparing to recover from a disaster by using Simplified Disaster Recovery

Table 21-4 User scenarios when a user starts the Create Recovery Disk
Wizard (continued)

Windows If Windows ADK is not installed If Windows ADK is installed

server version

Windows Server If Windows ADK 1809 is not installed, If Windows ADK 1809 is installed,
2019 the user must download and install the Simplified Disaster Recovery
Windows ADK 1809 manually. Disk Creation wizard detects the
installed version of ADK and the
When you install ADK 1809, the user
wizard continues with the recovery
must install the Windows ADK
disk creation process.
Insider and Windows
Preinstallation Environment If Windows ADK 10 is installed,
components. the Simplified Disaster Recovery
Disk Creation wizard detects that
After the components are installed,
ADK 10.0 version is installed and
launch the Simplified Disaster
the ADK update screen is
Recovery Disk Creation wizard again.
displayed. The wizard informs the
user that this is not the latest
available version of ADK but the
user can proceed with the SDR
disk creation. Confirm that the
user wants to continue using ADK
10. If the user continues, it may
not support all the features of
Windows Server 2019.

Preparing to recover from a disaster by using

Simplified Disaster Recovery
When a disaster occurs, you can use Simplified Disaster Recovery (SDR) to return
the computer to its pre-disaster state.
To prepare to recover a computer, use the following steps:

Table 21-5 Preparing to recover from a disaster by using Simplified Disaster

Recovery

Step Description

Step 1 Disconnect any storage area network or

cluster that is attached to the computer being
recovered. Otherwise, the hard drives on
those computers may also be repartitioned
and reformatted.
 Simplified Disaster Recovery 851
Preparing to recover from a disaster by using Simplified Disaster Recovery

Table 21-5 Preparing to recover from a disaster by using Simplified Disaster

Recovery (continued)

Step Description

Step 2 Plan any hardware changes to the computer

to be recovered.

See “Hardware replacement during disaster

recovery” on page 851.

Step 3 Review additional requirements for IBM

computers if the computer to be recovered is
an IBM computer.

See “Prepare to recover IBM computers with

Simplified Disaster Recovery” on page 852.

Step 4 Review recovery notes if you are recovering

a SQL server, Exchange server, SharePoint
server, or an environment in which the Central
Admin Server feature is installed.

See “Recovery notes for using Simplified

Disaster Recovery with Exchange, SQL,
SharePoint, CAS, Hyper-V hosts, and the
Deduplication feature” on page 863.

Review recovery notes if you are recovering

Windows operating systems with storage
pools and storage spaces.

See “Recovery notes for using Simplified

Disaster Recovery with storage pools and
storage spaces” on page 859.

When you complete these steps, you can start the recovery process.
See “Recovering a computer with Simplified Disaster Recovery” on page 853.

Hardware replacement during disaster recovery

You can use Simplified Disaster Recovery (SDR) to recover a computer that is no
longer functioning. For example, if the computer’s main system board fails, you can
restore the computer’s data after you replace the system board. You can also restore
the data even if the new board is a different model or if it contains multiple
processors.
If you plan to change the hardware in the computer being recovered, consider the
following information before you use SDR to recover the computer:
 Simplified Disaster Recovery 852
Preparing to recover from a disaster by using Simplified Disaster Recovery

Table 21-6 Hardware considerations when recovering failed computers

Item Description

Hard drives Any hard drives that you replace should be

the same size or larger than the original
drives.

System boards After you replace a faulty system board and

after you use SDR to recover the computer,
you must use the system board
manufacturer’s driver CD to re-install
additional functionality such as onboard
sound and video.

Network interface cards If you change the network interface card in

the computer that you want to recover, you
must install the necessary network drivers.
Without the network drivers, you cannot
access the network if you want to use a
remote Backup Exec server or remote legacy
backup-to-disk folders to recover the
computer. After you complete the recovery,
you must install new network interface card
drivers that match the network card that is
currently in the computer.

In most instances, it is not necessary to install

the drivers manually. Most drivers are
available on the Simplified Disaster Recovery
disk image. When you create the Simplified
Disaster Recovery disk image, you can
customize it to include any drivers that you
may need.

See “Recovering a computer with Simplified Disaster Recovery” on page 853.

Prepare to recover IBM computers with Simplified Disaster Recovery

To prepare to recover an IBM computer that has an IBM ServeRAID card by using
Simplified Disaster Recovery, use the following steps:
 Simplified Disaster Recovery 853
Recovering a computer with Simplified Disaster Recovery

Table 21-7 Prepare to recover an IBM computer

Step Description

Step 1 Install and configure the IBM ServeRAID

controller card and ServeRAID software so
that a boot volume is recognizable by the
Windows operating system.

Step 2 Before you use the SDR startup media, start

the server by using the IBM server’s
ServeRAID Configuration and Management
CD in the CD-ROM drive. This starts the IBM
ServeRAID utilities configuration and
installation process to view and update the
current BIOS and firmware levels.

Refer to the IBM ServeRAID documentation for complete installation instructions

for installing Windows on an IBM Server with the ServeRAID controller. Create and
initialize the ServeRAID disks so that volumes are recognizable by the Windows
operating system.
See “Recovering a computer with Simplified Disaster Recovery” on page 853.

Recovering a computer with Simplified Disaster

Recovery
You can use the Simplified Disaster Recovery Recover This Computer Wizard
to run a local recovery or a remote recovery of a Backup Exec server or a Windows
computer.
You can perform a local recovery if all of the following conditions are met:
■ You want to restore a Backup Exec server or a Windows computer.
■ The backup data for the computer is located on the devices that you can locally
attach to the computer on which you run the Recover This Computer Wizard.
■ You can provide the disaster recovery information file for the Backup Exec server
or the Windows computer that you want to recover.
 Simplified Disaster Recovery 854
Recovering a computer with Simplified Disaster Recovery

Note: If the computer that you want to recover was backed up to a tape device,
to a deduplication storage, or to a virtual disk, then SDR was unable to store
the disaster recovery information file with the backup sets. You must provide
the path to the default location or to the alternate location for the disaster recovery
information file when the Recover This Computer Wizard prompts you. If you
cannot provide a disaster recovery information file, then you must perform a
manual disaster recovery. Refer to the following sections for more information
about how to perform manual disaster recovery:
See “Performing manual disaster recovery of a local Backup Exec server on a
Windows computer” on page 868.
See “Performing manual disaster recovery of a remote Backup Exec server or
remote agent on a Windows computer” on page 873.

Note: If you are restoring data on the same computer and if you do not select
the Erase hard disks and recreate the volume layout shown above option,
the recovery process does not restore the WindowsApps folders on operating
systems that run Windows 8 or later. However, the restore job is successful.
Microsoft recommends to restore the WindowsApps folders using Device Reset
on the Settings panel.
The WindowsApps folders that are ignored during restore could be the following:
The folder pointed by
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\PackageRoot

The folder pointed by

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\PackageRepositoryRoot

%SystemRoot%\InfusedApps

You can perform a remote recovery if all of the following conditions are met:
■ You want to restore a Backup Exec server or a Windows computer.
■ The backup data for the computer is located on the devices that are attached
to a remote Backup Exec server
■ You have network access to the remote Backup Exec server.
Before you start, review the steps for preparing to recover.
See “Preparing to recover from a disaster by using Simplified Disaster Recovery”
on page 850.
During recovery operations, you can recover the computer from the most recent
backup. Or, you can recover to a previous point-in-time backup.
 Simplified Disaster Recovery 855
Recovering a computer with Simplified Disaster Recovery

The Recover This Computer Wizard supports the recovery of computers with
encrypted backup sets. If the Simplified Disaster Recovery (SDR) backups are
encrypted during backup, the 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 627.
To restore data by using the Recover This Computer Wizard, the following items
are required:
■ The Simplified Disaster Recovery disk image, which must be the same version
of Backup Exec as the Backup Exec server.
■ If the computer that you want to recover was backed up to a tape device,
deduplication storage, or to a virtual disk, then the disaster recovery information
file is not stored with the backup sets. Instead, you must provide the path to the
default location or to the alternate location when the Recover This Computer
Wizard prompts you. The default location is: C:<Backup Exec install
path>\Backup Exec\sdr\Data. If the file is unavailable, you cannot recover the
computer with SDR.
■ The backup set that contains all of the critical system components for the
computer that you want to restore.
■ The boot drive on the computer that you want to recover must have from 3 GB
to 5 GB of free space, depending on the operating system and configuration.

Note: If a blank screen appears and the computer does not restart after you run
SDR, ensure that the boot drive has the necessary amount of free space. Then,
restart the computer again.

■ The computer that you want to recover must have an amount of RAM that is
equal to or greater than the minimum that the restored operating system requires.
■ The computer that you want to recover must have disks with enough free space
to contain the data that you restore from the backup of critical volumes. A volume
is considered critical if it is required for the computer to start successfully.
■ If you recover a Windows computer that has BitLocker encryption enabled, you
must turn on BitLocker encryption after the restore. See your Microsoft
documentation for more information on BitLocker drive encryption.
■ If the computer that you want to recover contains a RAID setup, you may be
required to configure the RAID before you start it with the SDR disk. Use the
computer manufacturer's RAID software to configure the RAID system.
■ If appropriate, review the following recovery notes:
 Simplified Disaster Recovery 856
Recovering a computer with Simplified Disaster Recovery

■ See “Recovery notes for using Simplified Disaster Recovery with storage
pools and storage spaces” on page 859.
■ See “Recovery notes for using Simplified Disaster Recovery with Exchange,
SQL, SharePoint, CAS, Hyper-V hosts, and the Deduplication feature”
on page 863.

Note: Boot managers, such as System Commander or the OS/2 Boot Manager,
cannot be restored with SDR. Boot managers are usually installed at a very low
level that Backup Exec cannot protect. For example, the OS/2 Boot Manager resides
in its own hard drive volume that Backup Exec cannot access. Because of the many
different boot managers available, you may not be able to restart the computer after
an SDR recovery, even though the operating system was restored. You can reinstall
the boot manager to resolve this issue.

To recover a computer by using the Recover This Computer Wizard

1 Place the startup Simplified Disaster Recovery Disk in the CD drive or DVD
drive of the computer that you want to recover, and then start the computer.
2 On the End User License Agreement screen, click Accept.
3 On the Simplified Disaster Recovery Welcome screen, click Recover This
Computer.
4 In the left pane, click Network, and then click Configure Network Connection
Settings.
5 Select the appropriate network adapter configuration, and then click OK.
6 Do one of the following:
 Simplified Disaster Recovery 857
Recovering a computer with Simplified Disaster Recovery

If the backup data for this computer is Do the following in the order listed:
located on the devices that are attached
■ Click The data is located on devices
to a remote Backup Exec server (remote
attached to a remote Backup Exec
recovery)
server.
■ Enter the name and domain of the
remote Backup Exec server where the
backup data is located, and the
appropriate administrator or
administrator-equivalent credentials.
■ (Optional) To configure network adapter
settings, click Configure network
adapter settings, and then do one of
the following:
■ To assign a static IP address for
each detected network adapter,
select the appropriate options, and
then click OK.
■ To configure an IPv6 network
controller, click Configure IPv6,
select the appropriate options, and
then click OK.
■ (Optional) To load network adapter
drivers, click Load network adapter
drivers. Then, click Install Driver for
any inactive network controller that the
wizard detects. Navigate to the device
that contains the network controller
driver, and then click Open. Select the
driver, and then click Open again.
■ Click Next.

If the computer that you want to recover Do the following in the order listed:
was backed up to locally attached devices
■ Click The data is located on devices
such as tape drives, robotic libraries, disk
locally attached to this computer.
storage devices, or disk cartridge devices
■ Enter the appropriate administrator or
(local recovery)
administrator-equivalent credentials
when prompted, and then click Next.
 Simplified Disaster Recovery 858
Recovering a computer with Simplified Disaster Recovery

7 Select the disaster recovery information file that you want to use, and then
click Next.

Note: Backup Exec by default supports the latest three full SDR backup chains
that are required for system recovery using SDR. Each backup chain includes
one full backup set, its dependent incremental and differential backups, and
their duplicate backup sets.

8 Select the backup sets that you want to use to recover the computer, and then
click Next.
9 Select the storage device that contains the backup data for the computer, and
then click Next.
10 Do any of the following:

To use the volume layout as shown Click Next.

To view the disk geometry as it presently Click Preview.

exists, or to view a graphical representation
of proposed changes

To install required SCSI or RAID controller Do the following in the order listed:
drivers
■ Click Load Storage controller drivers.
■ Click Install Driver for any inactive
network controller that the wizard
detects.
■ Navigate to the device that contains the
network controller driver, and then click
Open.
■ Select the driver, and then click Open
again.

To automatically create a volume layout Select Erase hard disks and recreate the
on the available hard disks if mismatched volume layout shown above. Existing
volumes appear in the simplified volume data on these disks will be lost.
layout view

To change volume sizes or other Click Advanced Disk Configuration.

disk-related operations
See “Advanced Disk Configuration on the
Recover This Computer Wizard”
on page 864.

11 Review the Recovery Summary and click Back to make any changes, or click
Recovery to start the recovery process.
 Simplified Disaster Recovery 859
Recovering a computer with Simplified Disaster Recovery

12 If you recover a Backup Exec server that runs Backup Exec 15 or later, select
the appropriate database encryption key and then click Next.

Note: Backup Exec 15 and later requires a database encryption key to access
the Backup Exec Database. If you proceed without entering the database
encryption key on this screen, you are prompted to enter the key when you
restart Backup Exec.

13 When the recovery is complete, do any or all of the following:

To troubleshoot any issues that occurred Click View Hardware Discovery log.
during the hardware discovery phase

To troubleshoot any issues that occurred Click View Recover This Computer log.
during the recovery process

To restart this computer after you click Select Restart this computer.
Finish

To complete the recovery process and Click Finish.

close the wizard

Note: If the recovered computer contains multiple hard disks, ensure that the
computer's BIOS is configured to start the computer from the hard disk that
contains the Windows operating system. On many computers, the BIOS menu
can be accessed by pressing F2 or DEL on the computer keyboard.

Recovery notes for using Simplified Disaster Recovery with storage

pools and storage spaces
You can perform Simplified Disaster Recovery (SDR) for Windows operating systems
with storage pools and storage spaces using either of the scenarios that are
described in the following table:
 Simplified Disaster Recovery 860
Recovering a computer with Simplified Disaster Recovery

Table 21-8 Scenarios for SDR for storage pools and storage spaces

Scenario Description

Restore Windows operating systems with

storage pools and storage spaces to the
same computer
 Simplified Disaster Recovery 861
Recovering a computer with Simplified Disaster Recovery

Table 21-8 Scenarios for SDR for storage pools and storage spaces
(continued)

Scenario Description

In this scenario, the Recover This Computer

Wizard prompts you to reconfigure storage
pools and storage spaces, or remove them,
or to restore them as they are.

To reconfigure or remove the storage pools

and storage spaces, click the PowerShell
button on the displayed message dialog box
to open a PowerShell window.
Note: The recovery disk created with
Windows ADK 8.1 does not detect the Backup
Exec storage folder (\BEData) if this folder is
configured on the storage pools and storage
spaces on the Backup Exec Server. This
problem happens only when the Backup Exec
server installed on Windows Server 2016
operating system is not available and you
want to perform an SDR local recovery from
the BEData folder.

The recovery disk created with Windows ADK

10 and ADK 8.1 does not detect the Backup
Exec Storage folder (\BEData) if this folder is
configured on the storage pools and storage
spaces on the Backup Exec Server. This
problem happens only when the Backup Exec
server installed on Windows Server 2019
operating system is not available and you
want to perform an SDR Local recovery from
the BEData folder.

If you create the storage pools and spaces

using the recovery disk created with Windows
ADK 10, then after system restore, the
Windows Server 2012/2012 R2 operating
system does not detect the storage pools and
spaces.

If you create the storage pools and spaces

using the recovery disk created with Windows
ADK 1809, then after system restore, all
Windows 2016 and earlier operating systems
do not detect the storage pools and spaces.
 Simplified Disaster Recovery 862
Recovering a computer with Simplified Disaster Recovery

Table 21-8 Scenarios for SDR for storage pools and storage spaces
(continued)

Scenario Description

For more information about storage

commands in PowerShell, see the following
URL:

http://technet.microsoft.com/library/hh848705.aspx

Restore a version of Windows that is before In this scenario, you restore to a computer
Windows 8/Windows Server 2012 to a that contains configured storage pools and
computer on which storage pools and storage storage spaces. However, the operating
spaces or virtual disks are already configured. system that you restore does not recognize
storage pools and storage spaces.
The Recover This Computer Wizard
prompts you to do either of the following:

■ To remove the storage pools and storage

spaces, click the PowerShell button on
the displayed message dialog box to open
a PowerShell window.
For more information about storage
commands in PowerShell, see the
following URL:
http://technet.microsoft.com/library/hh848705.aspx
■ To continue to restore the storage pools
and storage spaces, click Next on the
displayed message dialog box. The
Recover This Computer Wizard blocks
any volume operations on the virtual disk,
such as creating a volume, deleting a
volume, assigning a drive letter, and so
on.

Limitations for restoring storage pools and storage spaces

The Recover This Computer Wizard automatically maps volumes to their original
virtual disks or storage spaces if you restore to the same computer. If you do not
restore to the same computer, then you must use PowerShell and the SDR
Advanced Disk Configuration utility to manually map the volumes to the virtual disks
or storage spaces.
The Recover This Computer Wizard does not allow Boot, System, and Recovery
volumes to be mapped to virtual disks.
 Simplified Disaster Recovery 863
Recovering a computer with Simplified Disaster Recovery

See “Advanced Disk Configuration on the Recover This Computer Wizard”

on page 864.

Recovery notes for using Simplified Disaster Recovery with

Exchange, SQL, SharePoint, CAS, Hyper-V hosts, and the
Deduplication feature
Review the following recovery notes if you recover a SQL Server, Exchange Server,
SharePoint server, or an environment in which the Central Admin Server feature
is installed.

Microsoft SQL Server recovery notes

After you use Simplified Disaster Recovery (SDR) to recover the Windows server,
SDR automatically replaces the damaged master and model databases with copies
of the master database and the model database. After SQL is restarted and the
latest master database backup and all other system databases are restored, you
must still restore all user databases. Use the Backup Exec Restore wizard to restore
the latest backups.

Microsoft Exchange recovery notes

After you use SDR to recover the Windows server, use the Backup Exec Restore
wizard to restore the Exchange Server databases from the most recent Exchange
Server database backups.

SharePoint Portal Server recovery notes

You can use SDR to recover a Windows server that has SharePoint Portal Server
installed. After you restore the Windows computer, you must restart it. After the
computer restarts, although, the SharePoint Portal Server software is installed, it
is not functional. You must remove the SharePoint Portal Server and reinstall it
before the SharePoint data can be restored.

Central Admin Server feature (CAS) recovery notes

When you use SDR to recover a computer in a CAS environment, you can submit
the remote restore job to either of the following:
■ The central administration server.
■ The managed Backup Exec server that performed the original backup job.

Microsoft Hyper-V hosts

After you use SDR to recover the Windows server, use the Backup Exec Restore
wizard to restore the Microsoft Hyper-V guest virtual machines from the most recent
Microsoft Hyper-V backups.
 Simplified Disaster Recovery 864
Advanced Disk Configuration on the Recover This Computer Wizard

Backup Exec Deduplication feature recovery notes

If the Backup Exec Deduplication feature is installed and you use deduplication
disk storage devices, consider the following:
■ If you back up the local Backup Exec server, do not select a deduplication disk
storage device on the server as the destination storage device. The Recover
This Computer wizard cannot restore data from a local deduplication disk
storage device.
■ Simplified Disaster Recovery (SDR) cannot recover a deduplication disk storage
device.
■ Before you can use SDR to restore a remote computer that was backed up with
client-side deduplication, you must first delete the direct access device.
See “Selecting storage devices for direct access sharing” on page 945.
If you use SDR to recover a Backup Exec server that contains a deduplication disk
storage device, consider the following:
■ Any existing backup sets that were sent to the deduplication disk storage device
after it was backed up cannot be restored.
■ The deduplication disk storage device may not be in an operational state after
the recovery.
You can also use manual disaster recovery to recover deduplication disk storage
devices and OpenStorage devices.
See “Methods for restoring data in Backup Exec” on page 227.
See “Disaster recovery of deduplication disk storage devices ” on page 955.
See “Disaster recovery information file data paths” on page 825.
See “Setting or changing the alternate location for the disaster recovery information
file” on page 824.
See “About the Central Admin Server feature” on page 1263.

Advanced Disk Configuration on the Recover This

Computer Wizard
The Recover This Computer Wizard restores the hard drive volumes to the same
sizes they were before the disaster. If the hard drive in the failed computer is larger
than the hard drive that was in place before the disaster, it may result in unused
and unallocated space. You can run Advanced Disk Configuration to alter the volume
sizes to reflect the larger hard drive size.
The following is an example of why the hard drive volumes should be resized:
 Simplified Disaster Recovery 865
Advanced Disk Configuration on the Recover This Computer Wizard

The pre-disaster computer hardware contains a 40 GB hard drive with two 20-GB
volumes. You replace it with a 90-GB model. SDR then uses the disaster recovery
information file to rebuild the hard disk partition table by using the partition
information that is found on the original 40-GB hard drive. As a result, only 40 GB
of space is allocated on the new 90 GB hard drive, with a partition map that consists
of two 20-GB partitions.
You can access Advanced Disk Configuration from within the Recover This
Computer Wizard.

Note: You should be familiar with Microsoft Disk Management concepts before you
run Advanced Disk Configuration.

The following table provides details about the additional disk-related operations
that you can do with Advanced Disk Configuration.

Table 21-9 Advanced Disk Configuration tasks

Task Description

Create a simple volume A simple volume is a partition on a disk that

contains a file system.

Format a volume Disk volumes must be formatted before data

can be stored on them.

Extend the size of a volume If a disk contains some unallocated disk

space that is adjacent to a functional volume,
you can extend the volume to include the free
space. To extend the volume, it must be
either raw or formatted with the Windows
NTFS file system.

Shrink the size of a volume You can decrease the size of a volume by
shrinking the volume into the contiguous,
unallocated disk space that is on the same
disk.

When you shrink a volume, there is no need

to reformat the volume. Ordinary files are
automatically relocated on the disk to create
the new, unallocated disk space.
 Simplified Disaster Recovery 866
Advanced Disk Configuration on the Recover This Computer Wizard

Table 21-9 Advanced Disk Configuration tasks (continued)

Task Description

Create a spanned volume A spanned volume spans more than one

physical disk. You can create a spanned
volume by spanning it across multiple
physical disks, or by spanning the volume
into unallocated disk space.

To create a spanned volume, you must have

a startup volume and at least two dynamic
volumes.
Note: Spanned volumes are not
fault-tolerant.

Create a striped volume Striped volumes store data in stripes across

two or more physical disks. Although striped
volumes do not provide fault-tolerance
protection, they do offer the best performance
of all the volumes in Windows.

Create a mirrored volume A mirrored volume provides a copy of the data

that is written to a selected volume. Because
all data is written to both the mirrored volume
and the selected volume, mirroring reduces
the capacity of both volumes by 50%.

View volume properties You can view properties for each volume in
the Current Disk Layout view or in the Original
Disk Layout view.

Change an assigned drive letter You can change assigned drive letters for all
volumes if you want to organize your drive
letters in a certain way.

Delete a volume Deleting a volume erases all data from the

volume; therefore, it is recommended that
you use caution when considering the use of
this option.

Convert a basic disk to a dynamic disk Converting basic disks to dynamic disks lets
you create the volumes that span multiple
disks. Dynamic disks also let you create
fault-tolerant volumes, such as mirrored
volumes and RAID-5 volumes. All volumes
on dynamic disks are referred to as dynamic
volumes.
 Simplified Disaster Recovery 867
Performing manual disaster recovery

Table 21-9 Advanced Disk Configuration tasks (continued)

Task Description

Convert a Master Boot Record (MBR) disk MBR disks use the standard BIOS interface.
to a Guid Partition Table (GPT) disk GPT disks use extensible firmware interface
(EFI).

You can convert MBR disks to GPT disks if

the disk does not contain partitions or
volumes.

Convert a Guid Partition Table (GPT) disk GPT disks use extensible firmware interface
to a Master Boot Record (MBR) disk (EFI). Master boot record (MBR) disks use
the standard BIOS interface.

GPT disks can be converted to MBR disks if

the disk does not contain partitions or
volumes.

View the original disk layout geometry The original disk layout shows the actual hard
disk layout that existed during the backup job.
Within the simplified layout view, you can
accept the disk geometry as it originally
existed before the disaster, or you can alter
the geometry by changing the volume sizes.
Depending on the size of the existing disks,
you can alter volume sizes in megabytes,
gigabytes, or terabytes.

The simplified layout view has a Preview tab

that lets you view the disk geometry as it
presently exists. If you change the disk
geometry and change volume sizes, click the
Preview tab to see a graphical representation
of your proposed changes.

If mismatched volumes appear in the

simplified volume layout view, you can use
the option Erase hard disks and recreate
the volume layout shown above to
automatically create a volume layout on the
available hard disks. You can also manually
create a volume layout by using the
Advanced Disk Configuration option.

Performing manual disaster recovery

You should perform manual disaster recovery in the following situations:
 Simplified Disaster Recovery 868
Performing manual disaster recovery

■ Simplified Disaster Recovery is not available or has failed.

■ The Windows operating system has become corrupted and cannot be restored
using the Emergency Repair Disks.
■ The hard drive containing the Windows operating system has encountered an
unrecoverable error that requires reformatting the disk.
■ The hard drive that contains the Windows operating system needs to be replaced.
For information about how to perform manual disaster recovery of a local Backup
Exec server on a Windows computer, see the following section:
See “Performing manual disaster recovery of a local Backup Exec server on a
Windows computer” on page 868.
For information about how to perform manual disaster recovery of a remote Backup
Exec server or remote agent on a Windows computer, see the following section:
See “Performing manual disaster recovery of a remote Backup Exec server or
remote agent on a Windows computer” on page 873.

Performing manual disaster recovery of a local Backup Exec server

on a Windows computer
This procedure restores the computer's operating system to a pre-disaster state.
It also restores the data files, except for those that a Backup Exec agent protects,
such as the Agent for Microsoft Exchange Server. If Backup Exec agents protect
any of the data, refer to the section in the Backup Exec Administrator's Guide on
how to restore the data that is protected by the agent before beginning disaster
recovery. The agent-protected data should be restored after the system recovery
is complete. This procedure includes non-authoritative and authoritative restore of
Active Directory for a domain controller.
These steps are intended for manual disaster recovery only. If Simplified Disaster
Recovery (SDR) is enabled for the computer, you should use SDR for disaster
recovery.
The following items are required for manual disaster recovery of a local system:
■ A current full backup of the computer to be recovered and any subsequent
incremental and differential backups.
■ The Windows installation media.
■ The Backup Exec installation media.
■ The database encryption key that was used to encrypt the Backup Exec
Database. You should have exported the key to a secure location. You must
retrieve it from that location to complete the recovery process.
 Simplified Disaster Recovery 869
Performing manual disaster recovery

■ A storage device such as a tape drive, disk storage device, or a robotic library
must be attached to the computer that you want to recover.
■ If you want to perform an authoritative restore on a domain controller, you must
provide DSRM credentials.

Note: If you recover a Windows computer that has BitLocker encryption enabled,
you must enable BitLocker encryption again after the restore. See Microsoft's
documentation for more information on BitLocker drive encryption.

Always log on to Windows using the Administrator account or its equivalent during
this procedure.

To run a manual disaster recovery of a local Backup Exec server on a Windows

computer
1. Install the original version of Windows. The same Service Pack and patches
need to be applied after Windows is installed.
Note the following scenarios:
■ If you recover from an entire hard disk failure, use Windows setup to partition
and format the new disk during installation. This Windows installation is
necessary to provide Backup Exec with a target to which it can restore the
system. The computer name, Windows directory, and the file system (such
as NTFS) must be the same as the previous Windows installation. This
basic installation is overwritten by the backed-up version, which restores
your system configuration, application settings, and security settings.
■ If the system was a domain controller, in a specific domain or workgroup,
do not join the domain or workgroup. Use the More... option on the
Computer Name Change dialog box to manually add a domain suffix to
the computer name that matches the system's original domain or workgroup
suffix.
Change the new system name to match the original system name by
performing the following steps in the order listed:
■ From System Properties, on the Computer Name tab, click Change.

Note: If the domain or workgroup is joined, you must reestablish the

domain or the workgroup trust relationship after the restore and restart
are complete.

■ On the Computer Name/Domain Changes dialog box, click More.

 Simplified Disaster Recovery 870
Performing manual disaster recovery

■ If necessary, select Change primary DNS suffix when domain

membership changes, and then click OK.
■ Restart the system.

2. Install Backup Exec to a directory other than where it was originally installed
(a temporary installation). Always log on to Windows using the Administrator
account or its equivalent during this procedure.

Note: After recovery is complete, this installation of Backup Exec can be

removed.

3. Start Backup Exec, and then add the required Storage device by selecting the
Storage tab and then Configure Storage.
This storage device is the tape where your backup set resides or the disk path
where your disk storage device backup files are located.

Note: If you use a disk storage device to recover the local Backup Exec server,
do not include the original disk storage device. If you cannot avoid restoring it,
you need to ensure that the disk storage device being used for the recovery
does not conflict with the original disk storage device location.

4. On the Storage tab, click Inventory and Catalog to both inventory and catalog
the media that contains the latest full, incremental, and differential backups of
the computer that you want to recover.
5. Select the Backup and Restore tab, and then click Restore.
6. Do one of the following:
■ If the restore method Complete online restore of a computer, or restore
system component is available, do the following in the order listed:
■ Click Complete online restore of a computer, or restore system
component, and then click Next.
■ Click A Microsoft Windows computer that was fully selected for
backup, and then click Next.
■ Select the backup sets that you want to restore, and then click Next.
■ Make sure that you deselect the location for restore where your disk
storage device backup files were located, or else the restore operation
will overwrite them. Applications and data drives can be restored later
once the server recovery is completed.
 Simplified Disaster Recovery 871
Performing manual disaster recovery

■ Ensure that the option, Restore over existing files is selected, and
then accept the default selections on the How do you want to maintain
file integrity, hierarchy, and security for restore data panel.
■ Click Next.
■ On the How do you want to restore operating system features panel,
click Next.
■ For an authoritative restore of a domain controller, select the Mark this
server as the primary arbitrator for replication when restoring
SYSVOL in the System State option on the How do you want to
restore System State data? panel.
■ On the What additional tasks do you want to perform before and/or
after a restore panel, select any additional tasks that you want to run
before or after a restore, and then click Next.
■ Schedule the job to run, and then click Next.
■ On the Restore summary panel, click Finish.
■ Do not restart the computer after the restore job finishes.

■ If the restore method Complete online restore of a computer, or restore

system component is not available, create a restore job and manually
select individual system components for recovery. Do not restart the
computer after the restore job finishes.

7. Your computer's operating system is now restored to a pre-disaster state, but

you should not restart your system yet. Your data files have been restored if
they were included in a restore job, except those protected by Backup Exec
database agents.
Continue with one of the following:
■ For an authoritative restore of a domain controller, skip to step 8.
■ If you want to restore a standalone server or a non-authoritative restore of
a domain controller, the recovery is complete. Restart the computer after
the restore job successfully completes. If you have copied disk storage
device files to another location for the purpose of a restore, you can remove
them. Skip to step 9 to complete this procedure.

8. For an authoritative restore of a domain controller, do the following:

 Simplified Disaster Recovery 872
Performing manual disaster recovery

Note: Make sure that the system is started into Directory Services Restore
Mode for the first restart after the restore. Failing to do so may replicate the
Active Directory once the Active Directory services are online. To prevent this
replication, you can isolate the system from the network temporarily.

■ Press F8 during startup. A menu appears that lets you diagnose and fix
system startup problems.
■ Select Directory Services Restore Mode.
■ Log on using your DSRM credentials.
■ Open a command prompt.
■ Type NTDSUTIL, and then press Enter. For more information about running
NTDSUTIL for Windows Server, see Microsoft's documentation.
■ Type Activate Instance NTDS, and then press Enter.
■ Type Authoritative Restore, and then press Enter.
■ Type the following command, and then press Enter:
restore subtree ou=OU_Name,dc=Domain_Name,dc=xxx
In this command, <ou_name> is the name of the organizational unit that you
want to restore, <domain_name> is the domain name that the OU resides
in, and <xxx> is the top-level domain name of the domain controller, such
as com, org, or net.
■ Repeat these steps as many times as necessary for the specific objects
that you need to restore.
■ After you have finished restoring Active Directory information, exit
NTDSUITIL.
■ Restart the computer.

Note: If you have copied disk storage device files to some other location
to restore them, they can be removed.

9. When you launch Backup Exec, the program prompts you for the database
encryption key file. Complete the following steps to import the database
encryption key file:
■ Locate the database encryption key from the secure location to which you
backed it up. Backup Exec indicates the name of the key that needs to be
restored.
 Simplified Disaster Recovery 873
Performing manual disaster recovery

■ Copy the file and then paste it in the Data folder in the directory in which
you installed Backup Exec.
■ Log on to Backup Exec.

Performing manual disaster recovery of a remote Backup Exec server

or remote agent on a Windows computer
This procedure restores the computer's operating system to a pre-disaster state.
It also restores the data files, except for those that a Backup Exec agent protects,
such as the Agent for Microsoft Exchange Server. If Backup Exec agents protect
any of the data, refer to the section in the Backup Exec Administrator's Guide on
how to restore the data that is protected by the agent before beginning disaster
recovery. The agent-protected data should be restored after the system recovery
is complete. This procedure includes non-authoritative and authoritative restore of
Active Directory for a domain controller.
These steps are intended for manual disaster recovery only. If Simplified Disaster
Recovery (SDR) is enabled for the computer, you should use SDR for disaster
recovery.
The following items are required for manual disaster recovery of a remote system:
■ A current full backup of the computer to be recovered and any subsequent
incremental and differential backups.
■ The Windows installation media.
■ The database encryption key that was used to encrypt the Backup Exec
Database. You should have exported the key to a secure location. You must
retrieve it from that location to complete the recovery process.
■ If you want to perform an authoritative restore on a domain controller, DSRM
credentials are needed.

Note: If you recover a Windows computer that has BitLocker encryption enabled,
you must enable BitLocker encryption again following the restore. See Microsoft's
documentation for more information on BitLocker drive encryption.

Always log on to Window using the Administrator account or its equivalent during
this procedure.
 Simplified Disaster Recovery 874
Performing manual disaster recovery

To run a manual disaster recovery of a remote Backup Exec server or remote agent
on a Windows computer
1. At the remote computer, install the original version of Windows. The same
Service Pack and patches need to be applied after Windows is installed. Note
the following scenarios:
■ If you recover from an entire hard disk failure, use Windows setup to partition
and format the new disk during installation. This Windows installation is
necessary to provide Backup Exec with a target to which it can restore the
system. The computer name, Windows directory, and the file system (such
as NTFS) must be the same as the previous Windows installation. This
basic installation is overwritten by the backed-up version, which restores
your system configuration, application settings, and security settings.
■ If the system was a domain controller, in a specific domain or workgroup,
do not join the domain or workgroup. Use the More... option on the
Computer Name Change dialog box to manually add a domain suffix to
the computer name that matches the system's original domain or workgroup
suffix.
Change the new system name to match the original system name by
performing the following steps in the order listed:
■ From System Properties, on the Computer Name tab, click Change.

Note: If the domain or workgroup is joined, you must reestablish the

domain or the workgroup trust relationship after the restore and the
restart are complete.

■ On the Computer Name/Domain Changes dialog box, click More.

■ If necessary, select Change primary DNS suffix when domain
membership changes, and then click OK.
■ Restart the system.

2. At the Backup Exec server, install the Backup Exec Agent for Windows on the
remote computer.

Note: After recovery, the Backup Exec logon account needs to be updated
and the Backup Exec trust needs to be reestablished for the recovered remote
server.

3. On the Backup and Restore tab, select the computer name, and then click
Restore.
 Simplified Disaster Recovery 875
Performing manual disaster recovery

4. Do one of the following:

If the restore method Complete online restore of a computer, or restore
system component is available, do the following in the order listed:
■ Click Complete online restore of a computer, or restore system
component, and then click Next.
■ Click A Microsoft Windows computer that was fully selected for a
backup, and then click Next.
■ Select the point in time, ensuring that only the critical set is selected, and
then click Next.
■ Select To the original location, and then click Next.
■ Ensure that the option, Restore over existing files is selected, and then
accept the default selections on the How do you want to maintain file
integrity, hierarchy, and security for restore data panel.
■ Click Next.
■ For an authoritative restore of a domain controller, select Mark this server
as the primary arbitrator for replication when restoring SYSVOL in the
System State option on the How do you want to restore System State
data? panel.
■ On the What additional tasks do you want to perform before and/or
after a restore? panel, select any additional tasks that you want to run
before or after a restore, and then click Next.
■ Schedule the job to run and then click Next.
■ On the Restore summary panel, click Finish.
■ Do not restart the computer.
If the restore method Complete online restore of a computer, or restore
system component is not available, create a restore job and manually
select individual system components for recovery. Do not restart the
computer.

5. Your computer's operating system is now restored to a pre-disaster state, but

you should not restart your system yet. Your data files have been restored if
they were included in a restore job, except those protected by Backup Exec
database agents.
Continue with one of the following:
■ For an authoritative restore of a domain controller, proceed to step 6.
■ If you want to perform a standalone server restore or a non-authoritative
restore of a domain controller, the recovery is complete. Restart the
 Simplified Disaster Recovery 876
Performing manual disaster recovery

computer after the restore job successfully completes. Proceed to step 7

to complete this procedure.

6. For an authoritative restore of a domain controller, do the following:

Note: Make sure that the system is started into Directory Services Restore
Mode for the first restart after the restore. Failing to do so may replicate the
Active Directory once the Active Directory services are online. To prevent this
replication, you can isolate the system from the network temporarily.

■ Press F8 during startup. A menu appears that lets you diagnose and fix
system startup problems.
■ Select Directory Services Restore Mode.
■ Log on using your DSRM credentials.
■ Open a command prompt.
■ Type NTDSUTIL, and then press Enter. For more information about running
NTDSUTIL for Windows Server, see Microsoft's documentation.
■ Type Activate Instance NTDS, and then press Enter.
■ Type Authoritative Restore, and then press Enter.
■ Type the following command, and then press Enter:
restore subtree ou=OU_Name,dc=Domain_Name,dc=xxx
In this command, <ou_name> is the name of the organizational unit that you
want to restore, <domain_name> is the domain name that the OU resides
in, and <xxx> is the top-level domain name of the domain controller, such
as com, org, or net.
■ Repeat these steps as many times as necessary for the specific objects
that you need to restore.
■ After you have finished restoring Active Directory information, exit
NTDSUITIL.
■ Restart the computer.

7. When you launch Backup Exec, the program prompts you for the database
encryption key file.
Complete the following steps to import the database encryption key file:
■ Locate the database encryption key from the secure location to which you
backed it up. Backup Exec indicates the name of the key that needs to be
restored.
 Simplified Disaster Recovery 877
Performing manual disaster recovery

■ Copy the file and then paste it in the Data folder in the directory in which
you installed Backup Exec.

8. Log on to Backup Exec.

 Chapter 22
Integration with Veritas™
Information Map
This chapter includes the following topics:

■ About Veritas™ Information Map

■ How Backup Exec works with Veritas™ Information Map

■ Requirements for integration with Veritas™ Information Map

■ How Backup Exec integrates with Veritas™ Information Map

■ Supported data sources for integration with Veritas™ Information Map

■ Best practices for integration with Veritas™ Information Map

■ Troubleshooting tips for integration with Veritas™ Information Map

■ Limitation for integration with Veritas™ Information Map

About Veritas™ Information Map

The Veritas™ Information Map renders your unstructured data in visual context
and guides users towards unbiased, information-governance decision making.
Using the dynamic navigation in Information Map, customers can identify areas of
risk, areas of value, and areas of waste across their environment and make decisions
which reduce information risk and optimize information storage.
For more information, refer to the Veritas™ Information Map documentation.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
 Integration with Veritas™ Information Map 879
How Backup Exec works with Veritas™ Information Map

How Backup Exec works with Veritas™

Information Map
Backup Exec sends metadata about the items in the backup sets of the protected
servers to the Information Map Agent. The Agent evaluates the metadata sent by
Backup Exec and sends changed metadata to the Information Map services hosted
in the cloud.

Requirements for integration with Veritas™

Information Map
The following requirements are for integrating Backup Exec with Veritas™
Information Map.
■ Information Map displays metadata only for the servers that are configured in
a domain.
 Integration with Veritas™ Information Map 880
How Backup Exec integrates with Veritas™ Information Map

■ For servers that are protected using CIFS backups (no remote agent is
installed on the server); for example, NAS box, ensure that the server is
added in Backup Exec using its FQDN name.
■ For servers that have the remote agent installed, Backup Exec can determine
its FQDN name irrespective of how the server is added in Backup Exec.

■ For CAS-MMS deployment, if the CAS server is registered with the Information
Map Agent, the encryption key for backup sets of MMS must to be available on
the CAS server to send metadata about such backup sets.
■ For information about operating system requirements when you install Information
Map, refer to the Information Map documentation.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
■ For CAS-MMS deployment, you must register with the Information Map Agent
from the CAS server. Backup Exec sends item-level metadata from all servers
in the CAS-MMS deployment. There is no requirement to register with the
Information Map Agent from the MMS servers.
■ In CAS-MMS environment configured in distributed catalog mode, when the
backup set is on MMS and such backup set is being scanned from CAS then a
temporary file gets created on CAS server having scan task information.
Ensure that there is sufficient space on C: of CAS server. The required size is
dependent on number of items in the backup set. For example, for 6 million
items in backup set it needs ~100GB free space on CAS server’s C:

How Backup Exec integrates with Veritas™

Information Map
To integrate with Backup Exec, you need to perform the following steps:
 Integration with Veritas™ Information Map 881
How Backup Exec integrates with Veritas™ Information Map

To integrate with Information Map

1 Prepare Information Map deployment with a tenant. Contact Veritas to provision
a tenant in Information Map. Refer to the Information Map documentation for
more information.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
2 Install and configure the Information Map Agent.
Refer to the system requirements for installing the Information Map agent.
When you install the Information Map Agent ensure that you note the port
number. The same port number can be used when you configure the Information
Map settings in Backup Exec.
When you install the Information Map Agent, ensure that in the Shared Data
Location option, a network share is specified. If the Information Map Agent is
uninstalled or reinstalled, the cache information used that is in the previous
installation is not lost and can be reused.
The Information Map Agent is installed on-premises and is responsible for
sending data to Information Map. Backup Exec communicates with the
Information Map Agent.
Refer to the Information Map documentation for detailed information.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
3 Configure Backup Exec to integrate it with Information Map.
Do the following in the order listed:
■ Install and configure Backup Exec.
■ Click the Backup Exec button, and select Configuration and Settings >
Backup Exec Settings > Veritas Information Map.
■ Configure the settings for Information Map in the Backup Exec console.
See “Configuring settings for Veritas™ Information Map” on page 652.
After you perform these steps, Backup Exec is registered successfully with
the Information Map Agent.
 Integration with Veritas™ Information Map 882
How Backup Exec integrates with Veritas™ Information Map

4 Manage Information Map settings in the Veritas™ Information Map.

The servers that are protected by Backup Exec are available in the Information
Map console. Enable the servers whose item-level metadata you want to view
in Information Map. It may take some time for the item-level information for
enabled servers to be displayed in the Information Map console.
If you have a large number of servers for which you want to send item-level
metadata to Information Map, it is recommended that you not enable all servers
at the same time, and instead enable them in phases. Enable the servers after
taking a full backup. For example, if you have 10 servers, you can enable 3
servers first, then enable 3 more, and so on.
In the Veritas Connection Center (VCC), configure the settings for the Backup
Exec server under the Connections tab. Update the schedule in Information
Map to specify how frequently you want Backup Exec to send metadata about
items in the backup sets to Information Map.
It is recommended that you configure the scan schedule in the Veritas
Connection Center to be outside your backup window.
Backup Exec sends metadata about the items in the backup sets of the
protected servers to Information Map. You can use Information Map and
fine-tune the settings as per your requirements. Go to Information Map >
Administration > Global settings and select the age to define stale data,
item types, extensions, and so on. Refer to the Information Map documentation
for detailed information.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
5 Based on the schedule configured in VCC, Backup Exec obtains discovery
and scan tasks regularly from the Information Map Agent.
The default frequency is 30 minutes for polling discovery and scan tasks.
■ As part of a discovery task, Backup Exec sends information about how
many servers and resources it protects.
■ As part of a scan task, Backup Exec sends metadata about the items in
the backup sets of the protected servers that are enabled on Information
Map.
In the scenario that there is a chain of backup sets (a full backup set and
one or more incremental/differential backup sets) available for a protected
server, Backup Exec sends item-level metadata about items in the full
backup set first. The incremental or differential backup sets are processed
together during the next scan task.
Backup Exec displays informational and failure alerts on the console for the
discovery tasks and scan tasks. In the Backup Exec console, to get more
 Integration with Veritas™ Information Map 883
Supported data sources for integration with Veritas™ Information Map

information about Information Map discovery or scan tasks, you can refer to
the Information Map alerts in the console. The alerts also give information
about how many servers were discovered and which backup sets were scanned
by Backup Exec.
For more information, refer to the Information Map documentation.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0

Supported data sources for integration with

Veritas™ Information Map
The following data sources are supported when integrating with Veritas™ Information
Map
■ File systems that are supported by Backup Exec. For example, NTFS, ext2,
ext3.
■ NDMP file servers
■ Windows shares

Best practices for integration with Veritas™

Information Map
Best practices include tips and recommendations to help you use Backup Exec
with Information Map.
■ When you install the Information Map Agent, ensure that in the Shared Data
Location option, a remote share is specified. If the Information Map Agent is
uninstalled or reinstalled, the cache information that is used in the previous
installation is not lost and can be reused.
For more information about how to install and configure the Information Map
Agent, refer to the Veritas™ Information Map documentation.
http://veritashelpsupport.com/Welcome?locale=EN_US&context=INFOMAP1.0
■ To limit the load on the Backup Exec server and to be able to use the Information
Map Agent for different Information Map datastores, it is recommended that you
install Information Map Agent on a different computer.
■ If you want to send metadata about protected data of a virtual agent, ensure
that the backup jobs are configured with the appropriate option in the Instant
GRT tab. Go to Configuration and Settings > Job Defaults > Backup to Disk
> Instant GRT. In this tab, select any of the following options:
 Integration with Veritas™ Information Map 884
Troubleshooting tips for integration with Veritas™ Information Map

■ Run a full catalog operation as a separate job immediately after the

backup job finishes
■ Schedule a full catalog operation as a separate job after the backup
finishes

■ Ensure that the time duration that is selected in the Catalog panel is more than
the duration that you set for sending item-level metadata created within the
specified number of days to Information Map. To change the catalog setting, go
to Configuration and Settings > Backup Exec Settings > Catalog > Truncate
catalogs after.
For example, if 60 days is selected in the Truncate catalogs after option, in
the Send metadata about items in the backup sets created within the
specified number of days option, you need to select duration of less than 60
days.
■ It is recommended that you configure the scan schedule in the Veritas Connection
Center to be outside your backup window.
■ If you have a large number of servers for which you want to send item-level
metadata to Information Map, it is recommended that you not enable all servers
at the same time, and instead enable them in phases. Enable the servers after
taking a full backup. For example, if you have 10 servers, you can enable 3
servers first, then enable 3 more, and so on.

Troubleshooting tips for integration with Veritas™

Information Map
If you have problems with Veritas™ Information Map in Backup Exec, review the
following points.
■ If you uninstall Backup Exec, a prompt appears for you to retain information or
remove information from Backup Exec. If you choose to retain information, the
Information Map Agent server name, port, and logon account information are
retained. The Agent certificate is also retained in the Windows certificate store.
If you choose to remove information, the Information Map Agent details are
removed, and the Agent certificate is also removed from the Windows certificate
store.
■ If the Information Map Agent certificate is renewed or changed, Backup Exec
must register with the Information Map Agent and establish trust by verifying
the certificate again. An alert is displayed that the certificate has changed. On
Configuration and Settings > Backup Exec Settings > Veritas Information
Map panel, click Update and establish trust by verifying the certificate.
 Integration with Veritas™ Information Map 885
Troubleshooting tips for integration with Veritas™ Information Map

■ If Backup Exec is installed on a Windows 2008 server, you may see the following
error during registration with the Information Map Agent server:
Could not create SSL/TLS secure channel.
To resolve this error, enable TLS 1.2. Perform the steps given in the following
article.
https://support.microsoft.com/kb/4019276
■ Backup Exec is unable to communicate with Information Map Agent’s connector
service.
If a log, similar to the one given in the following example, is seen in the
Management service logs, it is because Backup Exec is unable to communicate
with Information Map Agents connector service. Ensure that the service is up
and running.
Error while sending HeartBeat:
MANAGEMENT: [10/26/17 23:07:02] [0029] 10/26
23:07:01.882[InfoMapConne] Sending HeartBeat to InfoMap agent on
10.217.193.169
MANAGEMENT: [10/26/17 23:07:02] [0029] 10/26
23:07:01.978[InfoMapConne] ERROR:Using password to authenticate
during first request
MANAGEMENT: [10/26/17 23:07:03] [0029] 10/26
23:07:03.109[InfoMapConne] ERROR:Exception during sending request.
MANAGEMENT: [10/26/17 23:07:03] [0029] 10/26
23:07:03.109[InfoMapConne] ERROR: Exception Message: Unable to
connect to the remote server
MANAGEMENT: [10/26/17 23:07:03] [0029] 10/26
23:07:03.109[InfoMapConne] ERROR: Exception Status: ConnectFailure
MANAGEMENT: [10/26/17 23:07:03] [0029] 10/26
23:07:03.109[InfoMapConne] ERROR:Retrying after 20000 ms.
MANAGEMENT: [10/26/17 23:07:23] [0029] 10/26
23:07:23.122[InfoMapConne] ERROR:Using password to authenticate
during retry
MANAGEMENT: [10/26/17 23:07:24] [0029] 10/26
23:07:24.134[InfoMapConne] ERROR:Exception during sending request.
MANAGEMENT: [10/26/17 23:07:24] [0029] 10/26
23:07:24.134[InfoMapConne] ERROR: Exception Message: Unable to
connect to the remote server
MANAGEMENT: [10/26/17 23:07:24] [0029] 10/26
23:07:24.134[InfoMapConne] ERROR: Exception Status: ConnectFailure
MANAGEMENT: [10/26/17 23:07:24] [0029] 10/26
23:07:24.134[InfoMapConne] ERROR:Retrying after 20000 ms.
 Integration with Veritas™ Information Map 886
Troubleshooting tips for integration with Veritas™ Information Map

MANAGEMENT: [10/26/17 23:07:44] [0029] 10/26

23:07:44.149[InfoMapConne] ERROR:Using password to authenticate
during retry
MANAGEMENT: [10/26/17 23:07:45] [0029] 10/26
23:07:45.152[InfoMapConne] ERROR:Exception during sending request.
MANAGEMENT: [10/26/17 23:07:45] [0029] 10/26
23:07:45.152[InfoMapConne] ERROR: Exception Message: Unable to
connect to the remote server
MANAGEMENT: [10/26/17 23:07:45] [0029] 10/26
23:07:45.152[InfoMapConne] ERROR: Exception Status: ConnectFailure
MANAGEMENT: [10/26/17 23:07:45] [0029] 10/26
23:07:45.152[InfoMapConne] ERROR:Retrying after 20000 ms.
MANAGEMENT: [10/26/17 23:08:05] [0029] 10/26
23:08:05.165[InfoMapConne] ERROR:Using password to authenticate
during retry
MANAGEMENT: [10/26/17 23:08:06] [0029] 10/26
23:08:06.185[InfoMapConne] ERROR:Exception during sending request.
MANAGEMENT: [10/26/17 23:08:06] [0029] 10/26
23:08:06.185[InfoMapConne] ERROR: Exception Message: Unable to
connect to the remote server
MANAGEMENT: [10/26/17 23:08:06] [0029] 10/26
23:08:06.185[InfoMapConne] ERROR: Exception Status: ConnectFailure
MANAGEMENT: [10/26/17 23:08:06] [0029] 10/26
23:08:06.189[InfoMapConne] Web Exception in
ConnectorManagerHeartBeatTask: Message: Unable to connect to the
remote server
Error while polling for Tasks:
MANAGEMENT: [10/26/17 22:58:26] [0020] 10/26
22:58:26.828[InfoMapConne] Next Polling Time = 10/8/2018 5:18:27
AM, Poll Now = True, Polling Interval = 30, Task Concurrency Level
= 1, Session Time = 720, Retry Count = 3, Retry Wait = 20000,
HeartBeat Interval = 60, Conn Timeout Secs = 100, Read Write
Timeout Secs = 630
MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26
22:58:31.109[InfoMapConne] Polling for InfoMap jobs, ConnectorId:
8ba84bda-1876-4ca6-92b6-1d6b25a9fc4e
MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26
22:58:31.109[InfoMapConne] GetFileNameForAlert: Current Alert File
Count: 57
 Integration with Veritas™ Information Map 887
Limitation for integration with Veritas™ Information Map

MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26

22:58:31.109[InfoMapConne] GetFileNameForAlert: Alert File Name:
C:\Program Files\Veritas\Backup
Exec\Data\BE-WIN2012R2_InfoMap_00058.txt
MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26
22:58:31.109[InfoMapConne] ERROR:The connection time out is 100000
ms.
MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26
22:58:31.109[InfoMapConne] ERROR:The read write time out is 630000
ms.
MANAGEMENT: [10/26/17 22:58:31] [0021] 10/26
22:58:31.125[InfoMapConne] ERROR:Using password to authenticate
during first request
MANAGEMENT: [10/26/17 22:58:32] [0021] 10/26
22:58:32.156[InfoMapConne] ERROR:Exception during sending request.
MANAGEMENT: [10/26/17 22:58:32] [0021] 10/26
22:58:32.156[InfoMapConne] ERROR: Exception Message: Unable to
connect to the remote server
MANAGEMENT: [10/26/17 22:58:32] [0021] 10/26
22:58:32.156[InfoMapConne] ERROR: Exception Status: ConnectFailure
MANAGEMENT: [10/26/17 22:58:32] [0021] 10/26
22:58:32.156[InfoMapConne] ERROR:Retrying after 20000 ms.
An alert will always get generated with detailed error message when there is a
failure while executing a Task. Alternatively, you can also check Management
service logs with verbose logging on InfoMapConnector component as mentioned
above and also check connector service logs on the Information Map Agent
server.
Connector service log gets created at default location - C:<Backup Exec install
path>\InformationMapAgent\connectorFramework\connectorService\cfConnectorService.log

Limitation for integration with Veritas™

Information Map
Backup Exec does not send metadata to Information Map about the backup sets,
which are encrypted with a restricted key.
 Chapter 23
Integration with Veritas
SaaS Backup
This chapter includes the following topics:

■ About integration with Veritas SaaS Backup

■ Connecting to Veritas SaaS Backup

■ Preconfigurations in Veritas SaaS Backup

■ Managing Veritas SaaS Backup accounts

■ Adding a new Veritas SaaS Backup account

■ Editing a Veritas SaaS Backup account

■ Deleting a Veritas SaaS Backup account

■ Generating a report to view Veritas SaaS Backup data

About integration with Veritas SaaS Backup

Veritas SaaS Backup is a backup and a recovery solution that lets you backup
cloud workloads, such as Office 365 Admin, G Suite, and Salesforce. Backup
Exec is a solution for backing up and restoring on-premise workloads. Backup Exec
integrates with Veritas SaaS Backup to provide unified reporting across Backup
Exec and Veritas SaaS Backup.
You must complete the preconfigurations in Veritas SaaS Backup and then add a
new logon account in Backup Exec. In the Backup Exec console, you can use the
reporting feature to run the Jobs Summary report to view Veritas SaaS Backup
data along with Backup Exec data.
 Integration with Veritas SaaS Backup 889
Connecting to Veritas SaaS Backup

See “Preconfigurations in Veritas SaaS Backup” on page 890.

See “Managing Veritas SaaS Backup accounts” on page 890.
See “Adding a new Veritas SaaS Backup account” on page 891.
See “Editing a Veritas SaaS Backup account” on page 891.
See “Deleting a Veritas SaaS Backup account” on page 892.
See “Generating a report to view Veritas SaaS Backup data” on page 892.

Connecting to Veritas SaaS Backup

Veritas SaaS Backup is a hosted cloud-to-cloud backup solution that provides data
protection across Office 365 and other SaaS workloads.
A free trial of Veritas SaaS Backup is available for Backup Exec users.
https://www.veritas.com/form/trialware/saas-backup
To connect to Veritas SaaS Backup
◆ Click the Backup Exec button, select Veritas SaaS Backup, and then select
Veritas SaaS Backup Website.
The Veritas SaaS Backup page is displayed.
https://www.veritas.com/product/backup-and-recovery/
saas-backup?om_camp_id=us_vrc_be_web_saas-backup_customers
 Integration with Veritas SaaS Backup 890
Preconfigurations in Veritas SaaS Backup

Preconfigurations in Veritas SaaS Backup

You must complete the following preconfigurations in Veritas SaaS Backup. After
completing the preconfigurations, you can use Backup Exec to add logon accounts
or view the SaaS Backup data in the Jobs Summary report.
■ Create an account to connect to Veritas SaaS Backup.
■ Set up a connector in Veritas SaaS Backup.
For more information about Veritas SaaS Backup, refer to the following link:
https://www.veritas.com/content/support/en_US/dpp.SaaSBackup.html

Managing Veritas SaaS Backup accounts

You can add, edit, or delete a Veritas SaaS Backup logon account. After you add
a logon account, the logon account details are displayed.
To manage Veritas SaaS Backup accounts
1 Click the Backup Exec button, select Veritas SaaS Backup, and then select
Manage Veritas SaaS Backup Accounts.
The Veritas SaaS Backup Logon Account Management dialog box is
displayed.
If you have added any Veritas SaaS Backup logon accounts, the details are
displayed.
2 View or select any of the following options:

Account Identifier Displays the account identifier for the Veritas SaaS Backup
logon account that you added.

Region Displays the region for the Veritas SaaS Backup logon
account that you added.

Add Click Add to add a new Veritas SaaS Backup logon

account.

Delete Click Delete to remove a Veritas SaaS Backup logon

account.

Edit Click Edit to update a Veritas SaaS Backup logon account.

3 Click OK.
 Integration with Veritas SaaS Backup 891
Adding a new Veritas SaaS Backup account

Adding a new Veritas SaaS Backup account

You can add a new Veritas SaaS Backup account.
To add a new Veritas SaaS Backup account
1 Click the Backup Exec button, select Veritas SaaS Backup, and then select
Manage Veritas SaaS Backup Accounts.
The Veritas SaaS Backup Logon Account Management dialog box is
displayed.
2 Click Add.
3 In the Account Credentials, complete the following fields.

User name Enter a user name for the logon account.

Password Enter a password for the logon account.

Region Select the region to associate the account. Backup Exec

supports three regions.

■ US region
https://us.saasbackup.veritas.com/v-signin.html
■ Australia region
https://ap.saasbackup.veritas.com/v-signin.html
■ Europe region
https://eu.saasbackup.veritas.com/v-signin.html

Account identifier Enter a name you can use to identify the logon account in
Backup Exec.

4 Click OK.
Backup Exec adds a new account. The account information is sent to Veritas
SaaS Backup. Veritas SaaS Backup creates a token that is sent to Backup
Exec and stored in the Backup Exec database.

Editing a Veritas SaaS Backup account

You can only edit the account identifier in the Veritas SaaS Backup account that
you created. To make changes to any other fields, you must delete the account
and create a new account.
 Integration with Veritas SaaS Backup 892
Deleting a Veritas SaaS Backup account

To edit a Veritas SaaS Backup account

1 Click the Backup Exec button, select Veritas SaaS Backup, and then select
Manage Veritas SaaS Backup Accounts.
The Veritas SaaS Backup Logon Account Management dialog box is
displayed.
2 Select the logon account that you want to update and click Edit.
3 Update the Account identifier and click OK.

Deleting a Veritas SaaS Backup account

You can delete the Veritas SaaS Backup account that you created. When the
account is deleted, the login information and SaaS Backup job history is removed
from Backup Exec.
To delete a Veritas SaaS Backup account
1 Click the Backup Exec button, select Veritas SaaS Backup, and then select
Manage Veritas SaaS Backup Accounts.
The Veritas SaaS Backup Logon Account Management dialog box is
displayed.
2 Select the logon account that you want to update and click Delete.
A confirmation message is displayed.
3 Click Yes.

Generating a report to view Veritas SaaS Backup

data
After the new logon account is added using Backup Exec, run the Jobs Summary
report from the Reports tab to view Veritas SaaS Backup data.
To generate the Jobs Summary report
1 Select the Reports tab.
2 From Report Groups, click Jobs > Jobs Summary.
 Integration with Veritas SaaS Backup 893
Generating a report to view Veritas SaaS Backup data

3 Right-click and run the Jobs Summary Report.

4 If the Run Report Now - Jobs Summary properties page appears, you can
only select the Job Status as Completed (Success) or Failed, and then click
OK.
If you do not select any status, Veritas SaaS Backup data for both Completed
(Success) and Failed status is displayed. If you select any other status, no
data is displayed for Veritas SaaS Backup.
Refer to the following topic for more information about the Jobs Summary
report with the Veritas SaaS Backup data.
See “Jobs Summary report” on page 714.
 Chapter 24
Forever Incremental
Backup
This chapter includes the following topics:

■ About Forever Incremental Backup

■ Differences between the traditional and the forever incremental backups of

virtual machines

■ How do forever incremental backups work

■ Backing up virtual machines using forever incremental backups

■ CAS-MBES scenarios in forever incremental backups

■ Notes for forever incremental backups

■ Recommendations for forever incremental backups

■ Limitation of forever incremental backups

About Forever Incremental Backup

Customers normally take weekly full backup and daily incremental backups from
the source virtual machines. Frequent full backups of virtual machines can cause
the backups to run past the backup window. This not only affects the SLA, but also
affects the virtual machines and the network bandwidth.
Backup Exec introduces Forever Incremental Backup, also known as Backup Exec
Accelerator. When you create a forever incremental backup policy, a full backup is
taken from the source virtual machine that is followed by incremental backups. A
consolidate backup is run by consolidating the previous set of full and incremental
backups. Subsequent incremental backups use the consolidate full backup as a
 Forever Incremental Backup 895
Differences between the traditional and the forever incremental backups of virtual machines

baseline to determine changes in the source virtual machine. A consolidate full

backup is equivalent to a full backup from the source virtual machine. It can be
used for all types of restores, such as Virtual machine restore, GRT restore,
application GRT restore, Instant Recovery, and Recovery Ready.

Benefits of Forever Incremental backups

■ Frees up the backup window.
■ Meets the backup policy requirements and recovery time objectives by running
weekly consolidated backups without running a full backup from the source
virtual machine.
■ Reduces the load on virtual machines and the network bandwidth by avoiding
frequent full backups from the source virtual machine.
Forever incremental backups are supported for both VMware and Hyper-V virtual
machines.

Differences between the traditional and the forever

incremental backups of virtual machines
The following table describes the differences between the traditional and the forever
incremental backups of virtual machines.

Table 24-1 Differences between the traditional and the forever incremental
backups of virtual machines

Item Traditional backup Forever Incremental backup

Supported backup Supports full, incremental, and Supports full, consolidate full, and
types differential backups. incremental backups.

Connection to the All backups from the source Only incremental backups from the
source virtual virtual machine. Connection source virtual machine. No
machine required. connection to the source virtual
machine is required for Consolidate
Full backups.

Load on the source Increases load as all backups Reduces the load as only
virtual machine are from the source virtual incremental backups are from the
machine. source virtual machine.

Backup method Standard processing, Faster Standard processing and Resilient

processing, and Resilient Change Tracking (RCT) methods
Only applicable for
Change Tracking (RCT) only.
Hyper-V virtual
methods.
machines
 Forever Incremental Backup 896
How do forever incremental backups work

How do forever incremental backups work

Two job templates are added by default for a forever incremental backup definition.
You can also add a third job template. You can navigate to the templates from
Backup Options > Schedule tab.
■ Forever Incremental
Use this template to get data from the source virtual machine with the VMware
or Hyper-V backup methods. If it is the first job that runs as a part of the forever
incremental solution, it backs up the full data from the source virtual machine.
■ Consolidate Full
Use this template to consolidate all backup sets available since the last full
backup and create a new full backup set on the Backup Exec server. The
consolidate backup runs locally on the Backup Exec server and does not connect
to the virtualization host or the virtual machine that is backed up. Subsequent
incremental backups refer to this consolidate full backup as the baseline.
■ Full
Add this job template to run a full backup from the source virtual machine (protect
the virtual machine directly from the source) as per the defined schedule.
As part of the Verify operation in a consolidate full backup, Backup Exec mounts
the backup set from the consolidate full backup and compares the GRT volume
level information with the last backup set.
For example, you created a forever incremental backup definition for a VMware
virtual machine. The incremental is scheduled daily starting from Saturday, 7th
September and consolidate full is scheduled weekly starting Friday, 13th September.
On the first Saturday, 7th September at 11:00 P.M., full data of the virtual machine
is backed up from the source virtual machine (F1).
 Forever Incremental Backup 897
How do forever incremental backups work

Table 24-2
Date Backup Date Backup

Week Saturday, 7th Full (F1) Week Saturday, 14th Incremental

1 September - 11:00 2 September - 11:00 (F2-I2)
P.M. P.M.

Sunday, 8th Incremental Sunday, 15th Incremental

September - 11:00 (F1-I1) September - 11:00 (F2-I3)
P.M. P.M.

Monday, 9th Incremental Monday, 16th Incremental

September - 11:00 (F1-I2) September - 11:00 (F2-I4)
P.M. P.M.

Tuesday, 10th Incremental Tuesday, 17th Incremental

September - 11:00 (F1-I3) September - 11:00 (F2-I5)
P.M. P.M.

Wednesday, 11th Incremental Wednesday, 18th Incremental

September - 11:00 (F1-I4) September - 11:00 (F2-I6)
P.M. P.M.

Thursday, 12th Incremental Thursday, 19th Incremental

September - 11:00 (F1-I5) September - 11:00 (F2-I7)
P.M. P.M.

Friday, 13th Full (F2) Friday, 20th Full (F3)

September - 11:00 September - 11:00
A.M. A.M.

Friday, 13th Incremental Friday, 20th Incremental

September - 11:00 (F2-I1) September - 11:00 (F3-I1)
P.M. P.M.

The backup chain then continues.

 Forever Incremental Backup 898
How do forever incremental backups work

Supported storage
A forever incremental backup definition is supported on the following devices:
■ Disk storage
 Forever Incremental Backup 899
How do forever incremental backups work

■ Deduplication disk storage

■ Disk storage that is hosted on a network share

Note: The Duplicate stage can be targeted to all devices that are supported by
Backup Exec.

Default schedule
You can set a schedule for each job template.
■ Forever Incremental
The default schedule is set for 11:00 P.M. every day. An incremental backup is
taken from source virtual machine every day at 11 P.M.
■ Consolidate Full
The default schedule is set for every week on Friday at 11:00 A.M. The
consolidate operation runs on the Backup Exec server every Friday at 11:00
A.M.
■ Full
The default schedule is set for the fourth Friday of each month at 11:00 P.M. A
full backup runs on the source virtual machine on the fourth Friday of each month
at 11:00 P.M. You can change the schedule as per your requirements.

Data lifecycle management (DLM)

You need to specify the backup set retention for forever incremental backups and
consolidate full backup sets. The backup sets are not expired and deleted until the
retention period has expired.

Prevent backup sets from getting deleted

Backup sets that are created by forever incremental backup jobs are retained
(consolidate full, full, and forever incremental backups). When the consolidate full
or full backup from the source virtual machine runs and is successful, the previous
backup chain containing the earlier full and the incremental backup sets are no
longer retained.
The latest full backup set created by the consolidate full or full backup from the
source virtual machine is retained along with the next set of incremental backups.
The backup set is retained until the subsequent consolidate full or full backup runs.
Even if a backup set has expired, it is not deleted as it is part of the backup chain
that is retained.
 Forever Incremental Backup 900
Backing up virtual machines using forever incremental backups

After the consolidate full or full backup from the source virtual machine is successfully
completed, the sets in the previous chain are no longer retained. Those sets can
be deleted depending on the retention period.
Considering the previous example, Backup Exec retains F1 to F1-I5. After F2 runs
and is successful, F2 is retained and Backup Exec no longer retains F1 to F1-I5.
In this backup chain, F2 to F2-I7 are retained till F3 runs and is successful. At any
point, only latest backup chain is retained.
In the Backup Exec user interface, all backup sets have the retention option set as
System defined and retain reason as Retained for Consolidate Full job.

Cataloging and Granular Recovery Technology (GRT)

The consolidate full backup does not run a catalog operation to collect GRT
information. The GRT information is instead copied from the latest incremental
backup available before the consolidate full backup is run. For the incremental or
the full backup from the source virtual machine, the catalog operation is run to
collect GRT information.

Backing up virtual machines using forever

incremental backups
You can create a backup for VMware and Hyper-V virtual machine using the forever
incremental backup definition.
To back up virtual machines using forever incremental backups
1 On the Backup and Restore tab, select a VMware or Hyper-V virtual machine,
an ESXi host, or a vCenter server, or a Hyper-V host from the list of servers.
2 Do one of the following:
■ In the Backups group, select Backup > Create a Forever Incremental
Backup for Virtual Machines.
■ Right-click and select Backup > Create a Forever Incremental Backup
for Virtual Machines.

3 On the Backup Definition Properties dialog box, in the Selections box, click
Edit to add or remove resources from the backup selection list.
Depending on whether you select a VMware ESX host or a Hyper-V host, the
virtual machines for the selected host are displayed.
4 On the Backup Definition Properties dialog box, in the Backup box, click
Edit, and select the backup options.
5 On the Backup Definition Properties dialog box, click OK.
 Forever Incremental Backup 901
CAS-MBES scenarios in forever incremental backups

CAS-MBES scenarios in forever incremental

backups
Review the following information that is related to CAS-MBES.
■ In a CASO environment, it is recommended that forever incremental, consolidate
full, and full jobs are targeted to storage devices from the same host. This helps
to avoid an impact of network bandwidth on the performance of the consolidate
full backup job.
■ In a CASO environment, for Backup to disk, you can select multiple disk storage
across various servers.
■ In a CASO environment, there is a restriction for the deduplication device to
ensure that no performance impact is observed. Forever incremental backups
allow selection of only one deduplication device for the jobs in the Backup stage.
You can only select the host server of the deduplication disk storage as a Backup
Exec server.
■ In a rolling upgrade scenario, forever incremental backup definition jobs can
only run on Backup Exec 20.6 or later.

Notes for forever incremental backups

The following notes are for forever incremental backups.
■ If the configuration for a VMware or Hyper-V virtual machine changes, the next
incremental backup is promoted to a full backup. For example, a new disk is
added to a virtual machine and if the next backup is an incremental backup, it
gets promoted to a full backup.
■ To create a forever incremental backup definition, create a new job. Traditional
backup definitions cannot be converted into forever incremental backup definition.
■ The Run a SQL Log backup after backing up the virtual machine setting for
SQL Application GRT virtual machine backup is not applicable to the consolidate
full job. The setting is applicable to the full or the forever incremental backup
from the source virtual machine.

Recommendations for forever incremental

backups
Recommendations to help you use forever incremental backups.
 Forever Incremental Backup 902
Limitation of forever incremental backups

■ Consolidate backup is an I/O intensive operation. Ensure that you select the
proper backup storage for Forever Incremental backup definition.
■ It is recommended that a Consolidate Full backup runs after a maximum of 30
consecutive incremental backups. This ensures that restore operations complete
in a reasonable time.
■ It is recommended that you run a periodic full backup from the source virtual
machine. Compared to traditional backups, in a forever incremental backup
definition, a full backup from the source virtual machine can be run at a lesser
frequency. This is applicable when a virtual machine has significant configuration
changes.
For example, full backup from the source virtual machine - monthly, incremental
- daily, and consolidate full - weekly.
■ It is recommended that you schedule a consolidate full backup, outside the
regular backup window.
■ Keep the Verify option enabled for forever incremental backup definition.
■ If a consolidate full job fails, it is recommended that you run a full backup from
the source virtual machine.
■ Run the Validate VM job after a consolidate full set. You can run this job when
backup sets are hosted on a disk.

Limitation of forever incremental backups

Limitation when you use forever incremental backups.
■ Forever incremental backups for Hyper-V are supported only using the Standard
processing and Resilient Change Tracking (RCT) method. You cannot run a
forever incremental backup using the Faster processing method.
 Appendix A
Backup Exec Agent for
Windows
This appendix includes the following topics:

■ About the Agent for Windows

■ Requirements for the Agent for Windows

■ Stopping and starting the Agent for Windows

■ Establishing a trust between the Backup Exec server and a remote computer

■ About the Backup Exec Agent Utility for Windows

■ Using the Backup Exec Agent Utility Command Line Applet

■ Backup Exec Agent Utility Command Line Applet switches

About the Agent for Windows

The Agent for Windows enables Windows Servers network administrators to perform
backup and restore operations on Backup Exec agents that are connected to the
network.
The Agent for Windows is a system service that runs on remote Windows servers
and workstations. The Agent for Windows provides faster backup processing by
locally performing the tasks that require extensive network interaction in typical
backup technologies. The Agent for Windows processes backup data into a
continuous stream that the Backup Exec server then processes as a single task.
This method provides better data transfer rates over traditional technologies, which
require multiple requests and acknowledgments between the Backup Exec server
and the remote server.
 Backup Exec Agent for Windows 904
Requirements for the Agent for Windows

The Agent for Windows enables you to do the following:

■ Back up and restore in firewall environments.
■ Back up and restore using a specified local network if the Backup Exec server
and the remote computer are on the same subnet.
■ Attain significant performance increases when running modified backups (for
example, differential and incremental). This occurs because file selection is
performed locally by the Agent for Windows instead of across the network as
performed by traditional network backup applications.

Note: Network hardware has a major effect on performance. Performance is directly

related to the capabilities of the networking hardware in the Backup Exec server
and the remote device. Higher network bandwidth ratings also contribute to faster
operation processing.

See “Requirements for the Agent for Windows” on page 904.

See “Methods for installing the Agent for Windows” on page 68.
See “Changing network and security options for Backup Exec” on page 614.
See “Using Backup Exec with firewalls” on page 620.
See “Backup Exec Shadow Copy Components file system” on page 182.
See “About the Backup Exec Agent Utility for Windows” on page 906.

Requirements for the Agent for Windows

Because an Agent for Windows is also a Client Access License (CAL), you must
install the Agent for Windows on any remote Windows computer that you want to
back up. You cannot fully protect resources on a remote server until an Agent for
Windows has been installed.
At the Backup Exec server, you must enter Agent for Windows licenses for each
remote Windows computer that you want to protect. To back up a remote Windows
computer from more than one Backup Exec server, you must enter the same Agent
for Windows licenses on each Backup Exec server.
Backup Exec Agent for Applications and Databases also includes an Agent for
Windows that lets you protect one remote Windows computer. The Agent for
Windows license is enabled when you install the database agents on the Backup
Exec server.
To protect the Workstation versions of the supported Windows platforms, you must
install the Agent for Windows on each platform.
 Backup Exec Agent for Windows 905
Stopping and starting the Agent for Windows

You can find a list of compatible operating systems, platforms, and applications in
the Backup Exec Software Compatibility List.

Note: If a previous version of the Agent for Windows is installed, it is automatically

upgraded when you initiate a new Agent for Windows installation. Previous versions
of the Agent for Windows are automatically detected on the remote computers and
replaced with the new version during installation of the new Agent for Windows.
The name of the system service may have changed when the upgrade is complete.

You can install the Agent for Windows using many methods, depending on your
environment.
See “Methods for installing the Agent for Windows” on page 68.

Stopping and starting the Agent for Windows

The Agent for Windows is automatically started as a service when Windows is
started on the remote computer.
To stop or start the Agent for Windows
1 Open Windows Services.
2 In the Results pane, right-click Backup Exec Remote Agent for Windows.
3 Do one of the following:

To stop the Agent for Windows Click Stop.

To start the Agent for Windows Click Start.

See “About the Agent for Windows” on page 903.

Establishing a trust between the Backup Exec

server and a remote computer
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. You must also establish this trust if you want to
configure a remote computer to perform client-side deduplication. You should
manually verify the identity of the remote computer to ensure that the remote
computer is a trusted source before you establish the trust. After you verify that the
 Backup Exec Agent for Windows 906
About the Backup Exec Agent Utility for Windows

remote computer is a trusted resource, you can establish the trust with the Backup
Exec server.
Backup Exec issues a security certificate for both the Backup Exec server and the
remote computer. The security certificate is valid for approximately one year and
is automatically renewed during normal operations. However, if the certificate expires
you must re-establish the trust.
You can establish a trust between the Backup Exec server and the remote computer
by adding the remote computer to the list of servers on the Backup and Restore
tab.
To establish a trust for a remote computer
1 On the Backup and Restore tab, in the Servers and Virtual Hosts group,
click Add.
2 Click Microsoft Windows computers and servers.
3 Follow the on-screen prompts.

About the Backup Exec Agent Utility for Windows

The Backup Exec Agent Utility is installed when the Agent for Windows is installed
on a remote Windows computer.
You can perform the following tasks with the Backup Exec Agent Utility:
■ Start the Backup Exec Agent Utility each time you log on.
See “Starting the Backup Exec Agent Utility” on page 907.
■ View current activity on the remote Windows computer.
See “Viewing the activity status of the remote computer from the system tray”
on page 908.
■ Configure the Agent for Windows to send information such as the version and
the IP address to a Backup Exec server.
See “About publishing the Agent for Windows to Backup Exec servers”
on page 910.
■ Configure the Backup Exec Agent Utility for backup and restore operations of
Oracle instances.
See “Configuring an Oracle instance on Linux servers” on page 1177.
■ Configure the Backup Exec Agent Utility for Backup Exec server database
access for Oracle operations.
See “Configuring database access for Oracle operations” on page 912.
■ Remove the security certificate for a Backup Exec server.
 Backup Exec Agent for Windows 907
About the Backup Exec Agent Utility for Windows

See “Removing Backup Exec servers that the Agent for Windows can publish
to” on page 912.

Starting the Backup Exec Agent Utility

You access the Backup Exec Agent Utility from the Windows taskbar.
See “Viewing the activity status of the remote computer in the Backup Exec Agent
Utility” on page 907.
See “About publishing the Agent for Windows to Backup Exec servers” on page 910.
To start the Backup Exec Agent Utility
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
When the Backup Exec Agent Utility is running, an icon appears in the system
tray. You can double-click the icon to view the utility.
2 To open the registry editor, the Services window, and the Event Viewer on the
remote Windows computer, right-click the Backup Exec Agent Utility icon in
the system tray, and then click Tools.

Viewing the activity status of the remote computer in the Backup

Exec Agent Utility
You can use the Backup Exec Agent Utility to view the activity status of the remote
Windows computer.
 Backup Exec Agent for Windows 908
About the Backup Exec Agent Utility for Windows

To view the activity status of the remote computer in the Backup Exec Agent
Utility
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
If the Backup Exec Agent Utility is already running, you can double-click its
icon in the system tray.
2 Click the Status tab.
You can view any of the following information about the remote Windows
computer:

Backup Exec server Displays the name of the Backup Exec server that is
processing the current operation.

Source Displays the media or share that is being processed.

Current folder Displays the name of the current directory, folder, or

database (depending on the specific agent) that is being
processed.

Current file Displays the name of the current file that is being
processed.

3 Click OK.
See “About the Backup Exec Agent Utility for Windows” on page 906.

Viewing the activity status of the remote computer from the system
tray
You can view the activity status for a remote computer.
Possible statuses are as follows:
■ A backup job is running.
■ A restore job is running.
■ A backup and a restore job are running.
■ Snapshot in progress.
■ The Backup Exec client service named Beremote.exe is not running on the
computer.
■ Idle.
 Backup Exec Agent for Windows 909
About the Backup Exec Agent Utility for Windows

To view the activity status of a remote computer

◆ Position the cursor over the Agent for Windows icon in the system tray.
See “About the Backup Exec Agent Utility for Windows” on page 906.

Starting the Backup Exec Agent Utility automatically on the remote

computer
You can start the Backup Exec Agent Utility automatically each time you log on to
the remote computer.
To start the Backup Exec Agent Utility automatically on the remote computer
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
If the Backup Exec Agent Utility is already running, you can double-click its
icon in the system tray.
2 Click the Status tab.
3 Check the Start the Backup Exec Agent Utility every time you log on check
box.
4 Click OK.
See “About the Backup Exec Agent Utility for Windows” on page 906.

Setting the refresh interval on the remote computer

You can display the number of seconds for the Backup Exec Agent Utility to wait
before refreshing the status of the computer.
To set the refresh interval on the remote computer
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
If the Backup Exec Agent Utility is already running, you can double-click its
icon in the system tray.
2 Click the Status tab.
3 In the Refresh interval box, type the number of seconds to refresh the status.
4 Click OK.
See “About the Backup Exec Agent Utility for Windows” on page 906.
 Backup Exec Agent for Windows 910
About the Backup Exec Agent Utility for Windows

About publishing the Agent for Windows to Backup Exec servers

Use the Backup Exec Agent Utility to add, change, or delete the Backup Exec server
names or IP addresses that this remote Windows computer publishes to. Each
Backup Exec server that you add to the list on the Publishing tab displays the
remote computer in the list of servers on the Backup and Restore tab. After the
remote computer is added to the list of servers, you can right-click the remote
computer and click Establish Trust to verify that the remote computer is a trusted
resource.
This information that the Agent for Windows publishes includes the version of the
Agent for Windows and the remote computer’s IP addresses. Because the remote
computer’s IP address is published to the Backup Exec server, the Backup Exec
server can connect to and display the remote computer even if it is in an unknown
domain.
For each Backup Exec server that is published to, you can specify a local backup
network for operations between the Backup Exec server and the remote computer.
Directing jobs to a specified local network rather than to a corporate network isolates
the backup data traffic so that other connected networks are not affected when
operations are performed between the Backup Exec server and the remote
computer.
See “About the Backup Exec Agent Utility for Windows” on page 906.
See “Backup networks” on page 612.
See “About the list of servers on the Backup and Restore tab” on page 146.
See “Adding Backup Exec servers that the Agent for Windows can publish to”
on page 910.
See “Editing Backup Exec server information that the Agent for Windows publishes
to” on page 911.
See “Removing Backup Exec servers that the Agent for Windows can publish to”
on page 912.

Adding Backup Exec servers that the Agent for Windows can publish
to
You can use the Backup Exec Agent Utility to add a Backup Exec server that the
Agent for Windows can publish information.
See “About publishing the Agent for Windows to Backup Exec servers” on page 910.
See “Viewing the activity status of the remote computer from the system tray”
on page 908.
 Backup Exec Agent for Windows 911
About the Backup Exec Agent Utility for Windows

To add Backup Exec servers that the Agent for Windows can publish to
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > VeritasBackup Exec > Backup Exec Agent
Utility.
When the Backup Exec Agent Utility is running, an icon appears in the system
tray. You can double-click this icon to view the utility.
2 Click the Publishing tab.
3 (Optional) The first time that you start the Backup Exec Agent Utility, click
Change Settings to enable the options.
4 Click Add.
5 Enter the following information:

Backup Exec server name Type the Backup Exec server name or the IP address
or IP address of the Backup Exec server to which you want to publish
information.

User Name Type the user name for an account that has
administrative rights on the Backup Exec server.

Password Type the password for an account that has

administrative rights on the Backup Exec server.

6 Click OK.

Editing Backup Exec server information that the Agent for Windows
publishes to
You can use the Backup Exec Agent Utility to edit a Backup Exec server name or
IP address to which the Agent for Windows can publish information.
See “About publishing the Agent for Windows to Backup Exec servers” on page 910.
To edit Backup Exec server information
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
When the Backup Exec Agent Utility is running, an icon appears in the system
tray. You can double-click this icon to view the utility.
2 Click the Publishing tab.
 Backup Exec Agent for Windows 912
About the Backup Exec Agent Utility for Windows

3 (Optional) The first time that you are start the Backup Exec Agent Utility, click
Change Settings to enable the options.
4 Select the Backup Exec server that you want to edit from the list.
5 Click Edit.
6 Edit the Backup Exec server name or IP address.
7 Click OK.

Removing Backup Exec servers that the Agent for Windows can
publish to
You can use the Backup Exec Agent Utility to remove a Backup Exec server so
that the Agent for Windows no longer publishes information to it.
See “About publishing the Agent for Windows to Backup Exec servers” on page 910.
To remove Backup Exec servers that the Agent for Windows can publish to
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
When the Backup Exec Agent Utility is running, an icon appears in the system
tray. You can double-click this icon to view the utility.
2 Click the Publishing tab.
3 (Optional) The first time that you are start the Backup Exec Agent Utility, click
Change Settings to enable the options.
4 Select the Backup Exec server that you want to remove from the list.
5 Click Remove.
6 Click OK.

Configuring database access for Oracle operations

You can configure database access to enable the Backup Exec server to
authenticate Oracle operations.
See “Setting authentication credentials on the Backup Exec server for Oracle
operations” on page 1183.
 Backup Exec Agent for Windows 913
About the Backup Exec Agent Utility for Windows

To configure database access for Oracle operations

1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
2 Click the Database Access tab.
3 (Optional) The first time that you start the Backup Exec Agent Utility, click
Change Settings to enable the options.
 Backup Exec Agent for Windows 914
About the Backup Exec Agent Utility for Windows

4 Complete the appropriate options to configure database access:

Enable the Backup Exec Select this option to enable Oracle operations between
server to authenticate the Backup Exec server and this computer.
Oracle operations

User name Specify a user name that has administrative rights to

this computer. This logon account is what the Backup
Exec server uses when it connects to this computer.

If you specify an IP address or a fully qualified computer

name as part of the user name, the Backup Exec Agent
Utility may not be able to verify the user account. If the
credentials entered are incorrect, the error “cannot
attach to a resource” may be displayed when you run
a backup or restore job.

You must add this computer name and logon account

to the Backup Exec server's list of authentication
credentials for Oracle servers. If the authentication fails
when the Oracle resources are backed up, the backup
job fails. If the authentication fails when you are
browsing the backup sets for a restore job, then the
backup sets become unavailable, and you must run a
DBA-initiated restore job to restore data.

Password Specify the password for this logon account.

Note: For security reasons, the logon credentials are
not stored on the remote computer.

Confirm Password Type the password again to confirm it.

Use a custom port to Select this option to change the port that is used for
connect to the Backup Exec communications between this computer and the Backup
server during Oracle Exec server during Oracle operations. By default, port
operations 5633 is used.

If you change the port number on this computer, you

must also change it on the Backup Exec server, and
then restart the Backup Exec Job Engine Service on
the Backup Exec server.

Port number Type the port number that you want to use for
communications between this computer and the Backup
Exec server.
 Backup Exec Agent for Windows 915
Using the Backup Exec Agent Utility Command Line Applet

5 Click OK.
6 On the Backup Exec server, add the name of the Oracle server and the user
name that you entered on the Database Access tab to the Backup Exec
server's list of authentication credentials.
See “About the Backup Exec Agent Utility for Windows” on page 906.

Removing a security certificate for a Backup Exec server that has a

trust with the Agent for Windows
You can remove the security certificate for a Backup Exec server that has
established a trust with the Agent for Windows.
To remove a security certificate for a Backup Exec server
1 On the computer on which the Agent for Windows is installed, on the taskbar,
click Start > All Programs > Veritas Backup Exec > Backup Exec Agent
Utility.
2 Click the Security tab.
3 (Optional) The first time that you start the Backup Exec Agent Utility, click
Change Settings to enable the options.
4 Select the Backup Exec server that you want to remove the security certificate
for, and then click Remove.
5 Click OK.
See “Establishing a trust between the Backup Exec server and a remote computer”
on page 905.

Using the Backup Exec Agent Utility Command

Line Applet
You can use the Backup Exec Agent Utility Command Line Applet from any Windows
operating system command prompt to access the Backup Exec Agent Utility. The
Backup Exec Agent Utility Command Line Applet is installed when you install the
Agent for Windows.
If you run the command line utility on a Windows computer, you must run it in
elevated command prompt.

Note: To run the Backup Exec Agent Utility Command Line Applet on a Microsoft
Windows computer, you must use Server Core.
 Backup Exec Agent for Windows 916
Backup Exec Agent Utility Command Line Applet switches

You can run the following Backup Exec Agent Utility functions with the Backup Exec
Agent Utility Command Line Applet:
■ Set the publishing interval (in minutes).
■ List the published name for the agent.
■ List the Backup Exec server names to which the agent is publishing.
■ Add a Backup Exec server to the publishing list.
■ Remove a Backup Exec server from the publishing list.
■ View the following status information:
■ Activity status
■ Current source
■ Current folder
■ Current file
■ Currently attached Backup Exec server

To use the Backup Exec Agent Utility Command Line Applet

1 Open a command prompt.
2 From the Backup Exec installation directory, type ramcmd.exe followed by a
series of command switches.
The default installation location is c:<Backup Exec install path>\Backup
Exec\RAWS
See “Backup Exec Agent Utility Command Line Applet switches” on page 916.

Backup Exec Agent Utility Command Line Applet

switches
The following table describes the switches that you can use with the Backup Exec
Agent Utility Command Line Applet.
See “Using the Backup Exec Agent Utility Command Line Applet” on page 915.
 Backup Exec Agent for Windows 917
Backup Exec Agent Utility Command Line Applet switches

Table A-1 Backup Exec Agent Utility Command Line Applet switches

Switch Description

status:[n] Status output is repeated every <n> seconds, with a range

of 1 - 86400. Press Q to stop the output from running.

ramcmd /status:[n]

When you use the /status switch without a time value, the
Agent for Windows status appears in the command window
and then the applet exits.

/publish:[on | off | add | remove Use the following parameters with the /publish switch:
| interval][/ms:<Backup Exec
■ No parameter specified- Displays the publishing status
server>] [/t:<x>]
and then exits.
■ [on] - Turns publishing on. Lets the Agent for Windows
send information about itself, such as its version and
IP address.
■ [off] - Turns publishing off.
■ [add], [remove] - Used with /ms. You can use this
parameter to add or remove Backup Exec servers from
the Agent for Windows publish list.
■ [interval] - Used with /t. Specifies the time interval that
the Agent for Windows sends information about itself
to the Backup Exec server.
You can set the time interval in minutes using the
/t:[<x>] parameter.

Note: The [interval] switch must be used with the /t: switch.
Using [interval] alone on the command line is not supported.

ramcmd /publish:[on|off|add|remove|interval]
[/ms<Backup Exec server>][/t:<x>]
 Backup Exec Agent for Windows 918
Backup Exec Agent Utility Command Line Applet switches

Table A-1 Backup Exec Agent Utility Command Line Applet switches
(continued)

Switch Description

/oracle: [new | edit | delete] Use the following parameters with the /oracle switch:

/in:[<instance name>] ■ No parameter specified- Displays the existing Oracle

instances and then exits.
/ms:[<Backup Exec server |
■ [new], [edit], [delete] - Used with switch /in.
address>]
■ /in:[<instance name>] - Used to add, edit, and delete
/jt:[<job template>] Oracle instance names from the Oracle instance list.
/user:[<username>] ■ /ms:[<Backup Exec server name | address>] - Sets the
Backup Exec server name or its IP address.
/password:[<password> | * ]
■ /jt:[<job template>] - Sets a Backup Exec job template.
/rc: [yes | no] ■ /user:[<username>] - Sets a username.
/tns:[<TNS name>] ■ /password:[<password> | *] - Sets a password to be
used with /user:[<username>]. If you omit the password,
or you use an asterisk [*], you do not need to enter the
password on the command line. After the command
runs, a prompt appears asking you for a password.
■ /rc:[yes | no] - Turns the Use recover catalog setting
on or off. If /rc appears without a parameter, then the
current status for that instance is displayed.
■ /tns:[TNS name] - Sets the TNS name alias of an
available Oracle database and the server it resides on
in the Oracle TNSNAMES file.
ramcmd.exe /oracle:edit /in:<instance
name> /rc:[yes|no][/tns:<TNS
name>][/user:<username>][/password:password|*]

/auth:[on | off] Enables or disables Backup Exec server authentication for

[/user:<username>] Oracle operations.
[/password:<password> | *]
■ /auth:on - Turns the state on. Requires /user parameter.
■ /auth:off - Turns the state off. Requires /user parameter.
■ /user:<username> - Sets a username.
■ /password:<password> - Sets a password to be used
with /user:<username>. If you enter an asterisk for the
password or omit the password, you are prompted for
the password.
 Backup Exec Agent for Windows 919
Backup Exec Agent Utility Command Line Applet switches

Table A-1 Backup Exec Agent Utility Command Line Applet switches
(continued)

Switch Description

/port:[<port>] Displays or sets a custom port that is used to connect to

the Backup Exec server during Oracle operations.

■ /port - Displays the current port number. If the port is

the default port, displays "(default)".
■ /port:<port> - Sets the port number to <port>. To change
the port to the default port number, type [/port:0].

/log_path:[<log path>] Displays or sets a custom path for debug logs.

■ /log_path - Displays the log directory path and then

exits.
■ /log_path:<"logs path"> - Creates the directory <"logs
path">. If the path has a space in the name, enclose
the path in quotes. For example, "C:\Program
files\LogsFolder".
 Appendix B
Backup Exec
Deduplication Feature
This appendix includes the following topics:

■ About the Deduplication feature

■ Deduplication methods for Backup Exec agents

■ Requirements for the Deduplication feature

■ Installing the Deduplication feature

■ Converting an older version of Deduplication Storage to a newer version

■ Configuring an OpenStorage device

■ Editing the properties of an OpenStorage device

■ Specifying a Backup Exec server that has proximity to a shared OpenStorage

device

■ Creating or importing deduplication disk storage

■ Selecting storage devices for direct access sharing

■ Changing the location of a deduplication disk storage device

■ Sharing a deduplication device between multiple Backup Exec servers

■ How to use client-side deduplication

■ How to set up backup jobs for deduplication

■ Using optimized duplication to copy deduplicated data between OpenStorage

devices or deduplication disk storage devices
 Backup Exec Deduplication Feature 921
About the Deduplication feature

■ Copying deduplicated data to tapes

■ Using deduplication with encryption

■ Restoring a deduplication disk storage device or deduplicated data

■ Disaster recovery of deduplication disk storage devices

■ Disaster recovery of OpenStorage devices

About the Deduplication feature

The Backup Exec Deduplication feature supports a data-reduction strategy by
optimizing storage and network bandwidth. The Deduplication feature supports
integrated deduplication at the Backup Exec server and on remote computers that
have the Agent for Windows or the Agent for Linux installed. It also allows data to
be deduplicated and stored on intelligent disk devices from other vendors.

Table B-1 Types of deduplication

Type of deduplication Where deduplication Benefits

occurs

Backup Exec server-side On the Backup Exec server. Reduces the size of backups,
deduplication which reduces storage
requirements.

Client-side deduplication On the remote computer Reduces network traffic

where the data is located. because only unique data is
sent across the network. It
Note: The Agent for
also reduces the backup
Windows is required on the
window.
remote Windows computer to
perform Windows client-side
deduplication. The Agent for
Linux is required on the Linux
computer to perform Linux
client-side deduplication.

Appliance deduplication On an intelligent disk device, Reduces the size of backups,

such as Veritas PureDisk, or which reduces storage
a device from a third-party requirements. It also reduces
vendor. the backup window.

With a single Deduplication feature license key, you can use two types of
deduplication devices.
 Backup Exec Deduplication Feature 922
About the Deduplication feature

Table B-2 Types of deduplication devices that work with the Deduplication
feature

Type of Description
device

OpenStorage Backup Exec uses Veritas's OpenStorage technology, which allows

device intelligent disk devices to integrate with Backup Exec. You can back up
data to the Veritas PureDisk device and to storage devices from other
vendors.

You can find a list of compatible types of storage in the Backup Exec
Hardware Compatibility List.

See “Configuring an OpenStorage device” on page 932.

Deduplication Deduplication disk storage provides integrated deduplication on the Backup

disk storage Exec server. Deduplication disk storage is a disk-based backup folder that
is located on the Backup Exec server.

See “Creating or importing deduplication disk storage” on page 937.

In addition to reducing storage requirements and network traffic, the Deduplication

feature lets you do the following:
■ Copy deduplicated data from an OpenStorage device or deduplication disk
storage to tape for long-term or off-site storage.
■ Use optimized duplication, which lets you copy deduplicated data between
OpenStorage devices from the same vendor and between deduplication disk
storage devices.
■ Use Granular Recovery Technology (GRT) with jobs that use deduplication
devices.
■ Share OpenStorage devices and deduplication storage devices among multiple
Backup Exec servers when you use the Central Admin Server feature.
For information about the best practices to use Backup Exec Deduplication and
Backup Exec Deduplication with the Central Admin Server Option (CASO), refer
to Backup Exec Best Practices.
See “Installing the Deduplication feature” on page 929.
See “Requirements for the Deduplication feature” on page 924.
See “Sharing a deduplication device between multiple Backup Exec servers”
on page 949.
See “Using optimized duplication to copy deduplicated data between OpenStorage
devices or deduplication disk storage devices” on page 951.
See “Copying deduplicated data to tapes” on page 954.
 Backup Exec Deduplication Feature 923
Deduplication methods for Backup Exec agents

Deduplication methods for Backup Exec agents

Backup Exec supports the following deduplication methods:
■ Client-side deduplication, either on an intelligent disk device or to a deduplication
disk storage device.
■ Backup Exec server-side deduplication with a deduplication disk storage device.
■ Appliance deduplication on an OpenStorage device.
The following table lists the deduplication methods that are available for the Backup
Exec agents.

Table B-3 Deduplication methods for Backup Exec agents

Agent Client-side Client-side Backup Backup Appliance

deduplication deduplication Exec Exec deduplication
(file system (with server-side server-side on an
backups or Granular deduplication deduplication OpenStorage
VSS-snapshot Recovery (file system (with device
enabled Technology backups or Granular
backups, enabled) VSS-snapshot Recovery
whichever enabled Technology
is backups, enabled)
supported) whichever
is
supported)

Agent for Yes Not Yes Not Yes

Windows applicable applicable

Agent for Yes (for Yes (for Yes Yes Yes

VMware and Hyper-V only) Hyper-V only)
Hyper-V
Note: The Note: The
Agent for Agent for
Windows Windows
must be must be
installed on installed on
the Hyper-V the Hyper-V
host. host.

Agent for Yes No Yes Not Yes

Linux applicable

Agent for No No Yes No No

Enterprise
Vault
 Backup Exec Deduplication Feature 924
Requirements for the Deduplication feature

Table B-3 Deduplication methods for Backup Exec agents (continued)

Agent Client-side Client-side Backup Backup Appliance

deduplication deduplication Exec Exec deduplication
(file system (with server-side server-side on an
backups or Granular deduplication deduplication OpenStorage
VSS-snapshot Recovery (file system (with device
enabled Technology backups or Granular
backups, enabled) VSS-snapshot Recovery
whichever enabled Technology
is backups, enabled)
supported) whichever
is
supported)

Exchange Yes Yes Yes Yes Yes

Agent

SQL Agent Yes Not Yes Not Yes

applicable applicable

SharePoint Yes Yes Yes Yes Yes

Agent

Active Yes Yes Yes Yes Yes

Directory
Agent

Agent for Linux: Yes No Yes No Yes

Oracle
Windows:
Yes

See “About the Deduplication feature” on page 921.

Requirements for the Deduplication feature

The requirements for the Deduplication feature vary depending on the type of
storage devices you want to use and the type of deduplication you want to use.
Before you use the Deduplication feature, you should determine what type of storage
devices you want to use with it and what type of deduplication you want to use.
Then, verify that your system meets the requirements for the storage devices you
want to use.
 Backup Exec Deduplication Feature 925
Requirements for the Deduplication feature

Warning: It is strongly recommended that you exclude the deduplication disk storage
device from all antivirus scans. If an antivirus scanner deletes or quarantines the
files from the deduplication disk storage device, access to the device may be
disabled.
 Backup Exec Deduplication Feature 926
Requirements for the Deduplication feature

Table B-4 Requirements and recommendations for the Deduplication feature

Item Requirements and Recommendations

Deduplication disk
storage devices
 Backup Exec Deduplication Feature 927
Requirements for the Deduplication feature

Table B-4 Requirements and recommendations for the Deduplication feature

(continued)

Item Requirements and Recommendations

The following items are required:

■ A 64-bit Backup Exec server.

■ A Backup Exec server with a minimum of 4 cores.
It is recommended that you have 8 cores.
■ For 64 TB of stored deduplicated data, 8 cores are required.
■ A dedicated volume to use as the location to store the deduplication
disk storage. The dedicated volume must have 20 percent free
space that totals no less than 5 gigabytes (GB) of free space.
■ The deduplication disk storage device must be excluded from
antivirus scans. If an antivirus scanner deletes or quarantines the
files from the deduplication disk storage device, access to the
deduplication disk storage device may be disabled.
■ Deduplication disk storage requires 4 GB physical memory for up
to 4 TB storage. After that 1 GB of physical memory is required for
each 1 TB of deduplication disk storage and up to 32 TB. For
example, 5 GB physical memory for 5 TB storage. For deduplication
disk storage more than 32 TB and up to 64 TB, 32 GB or more
physical memory is recommended.
■ It is recommended the following as minimum disk speeds per
individual read, write, or verify operation:
■ Up to 32 TBs of storage:
■ 130 MB per second
■ 200 MB per second for enterprise-level performance
■ 32 to 48 TBs of storage: 200 MB per second
■ 48 to 64 TBs of storage: 250 MB per second

The above recommendations are for the performance of a single

operation. You may need more capability depending on your objectives
for writing to and reading from disk.
Note: You should be aware of the effects that computer disk speeds
have on deduplication performance.

Computer disk speeds can have the following effects on deduplication

performance:
■ Computers with disk speeds greater than 200 MB per second have
optimal read and write performance for deduplication.
■ Computers with disk speeds between 150-200 MB per second have
sufficient read and write speed for deduplication.
■ Computers with disk speeds between 100-150 MB per second have
some operations with degraded performance.
 Backup Exec Deduplication Feature 928
Requirements for the Deduplication feature

Table B-4 Requirements and recommendations for the Deduplication feature

(continued)

Item Requirements and Recommendations

■ Computers with disk speeds less than 100 MB per second

experience poor performance. You should improve disk reads and
writes before you install and run deduplication.

Deduplication disk ■ Storage area network (Fibre Channel or iSCSI), direct-attached

storage connection storage (DAS), or internal disks are supported.
Removable disks including USB, eSATA, and FireWire devices are
not supported.
■ The Backup Exec server should have redundant connectivity to
the storage.
■ The storage network must be a dedicated, low latency network with
a maximum of 1-millisecond latency per round trip.
■ The storage network must have enough bandwidth to meet your
throughput objectives. The following storage network bandwidths
are supported:
■ iSCSI SANs with a bandwidth of at least 10 Gb per second.
■ Fibre Channel SANs with a bandwidth of at least 4 Gb per
second.
■ A minimum bandwidth of 130 MB per second is required for read
and write performance. Bandwidth that is less than 130 MB per
second may be used in smaller, less resource-intensive
environments. However, as usage increases, deduplication requires
more bandwidth to ensure adequate throughput for deduplication
processes and backups. Otherwise, performance and stability are
negatively affected.

Deduplication disk The following requirements are for the password credentials for a
storage credentials deduplication disk storage device:

■ The password cannot be blank

■ The password cannot contain the following characters: &, ", <, >,
%, ^
■ The password cannot start with the hyphen character: -
■ The password cannot end with the backslash character: \
 Backup Exec Deduplication Feature 929
Installing the Deduplication feature

Table B-4 Requirements and recommendations for the Deduplication feature

(continued)

Item Requirements and Recommendations

OpenStorage To use a Veritas PureDisk device or a storage device from another

devices vendor as an OpenStorage device, you must purchase the device and
the appropriate OpenStorage connector from the device's vendor.

You can use the Deduplication feature with OpenStorage devices on

a 64-bit Backup Exec server.

The standard system requirements for Backup Exec apply to the

Deduplication feature when you use OpenStorage devices.

Client-side On the server where the Agent for Windows is installed, 1.5 GB of
deduplication for memory is required.
Windows
Both 32-bit and 64-bit Windows operating systems are supported.

Client-side You can find a list of compatible operating systems for Linux client-side
deduplication for deduplication in the Backup Exec Software Compatibility List.
Linux
A 64-bit Linux operating system is required.

The following deduplication devices can be used:

■ Deduplication disk storage device

■ Veritas PureDisk OpenStorage device, which is the only type of
OpenStorage device that supports client-siide deduplication for
Linux.

The following Backup Exec options are required:

■ Agent for Linux

■ Deduplication feature

See “Installing the Deduplication feature” on page 929.

Installing the Deduplication feature

Before you attempt to install a Backup Exec edition which includes the Deduplication
feature, verify that your system meets the requirements.
See “Requirements for the Deduplication feature” on page 924.
See “Installing additional agents and features to the local Backup Exec server”
on page 58.
 Backup Exec Deduplication Feature 930
Converting an older version of Deduplication Storage to a newer version

Converting an older version of Deduplication

Storage to a newer version
Backup Exec improves speed and deduplication when backing up to Backup Exec
deduplication folder. The conversion from an older version of deduplication storage
to a newer version involves the conversion of the existing deduplication data to a
newer format. The conversion time depends on the size of the deduplication storage
and the number of backup sets.
To convert from an older version of Deduplication Storage to a newer version
1 It is recommended that you make a copy of the deduplication data before the
upgrade starts.
2 Ensure that the following are true:
■ You have at least 12% free space available on the volume on which the
deduplication storage folder exists.
■ Deduplication services are running.
■ Windows Hotfix is installed.
See “Running the Environment Check before installing or upgrading Backup
Exec” on page 42.
3 If you need to free up more space on the volume, you can use the tool
pdde_gc.exe to reclaim storage space. If you have enough free space available,
proceed to the next step.
To run pdde_gc.exe, follow these steps:
■ Mount the ISO from the Backup Exec media or upgrade an earlier version
of Backup Exec. On the media, the tool is located in
<mounted-path>\BE\WinNT\Install\PDDEMigration.

■ On the command line, run pdde_gc.exe without any parameters.

If you need more free space, you can try any of the following options:
■ Use the Backup Exec console to expire backup sets on the deduplication
storage.
■ Run CR queue processing twice.
■ Run the pdde_gc.exe tool again.
 Backup Exec Deduplication Feature 931
Converting an older version of Deduplication Storage to a newer version

4 Upgrade Backup Exec to the latest version.

See “Installing Backup Exec by using the Installation Wizard” on page 48.
After Backup Exec has been upgraded, the conversion from the older version
of deduplication storage to a newer version starts. The existing deduplication
data is converted to a new format. During the conversion process, the
deduplication storage remains offline. Any ongoing deduplication jobs fail and
jobs targeted to any other storage continue to run during the deduplication
storage conversion.
The Backup Exec console displays an alert that the conversion process has
started. Depending on the time required for the conversion, an alert is displayed
every 15 minutes showing the progress of the conversion. An alert is also
displayed if the conversion is successful, has resumed, or has failed.
5 If the conversion is successful, a prompt is displayed in the Backup Exec
console, asking you to restart the Backup Exec services.
If you click OK, the Backup Exec Services dialog box is displayed. Click Restart
all services.
Optionally, on the Backup Exec Administration Console, click the Backup Exec
button, select Configuration and Settings, select Backup Exec Services,
and then click Restart all services.
If the conversion fails, you can manually convert the data to the new
deduplication format. Refer to the following section for information on how to
manually convert the data.
If the conversion fails because of a server restart, the conversion resumes after
the service restart is complete.

Create or import an older deduplication folder

You can create or import a deduplication storage folder in Backup Exec. You have
an existing deduplication storage folder that was created when you had the older
deduplication version that Backup Exec no longer supports. When you try to import
the folder, an error is displayed and the import fails. You need to manually convert
the older version of the folder to the new supported deduplication version supported
by Backup Exec using the steps in the following section:
After the conversion is completed successfully, you can import the folder. There
can be only one deduplication storage configured with a single Backup Exec media
server.
 Backup Exec Deduplication Feature 932
Configuring an OpenStorage device

Restore an older deduplication storage backup using

Backup Exec
You can restore an existing deduplication backup set using Backup Exec. This
backup set was created and backed up using an older deduplication version that
Backup Exec no longer supports. When you try to restore the backup set, the restore
job fails with an exception regarding the older deduplication backup sets but the
data is restored. You need to manually convert the restored deduplication folder to
a newer supported version of deduplication using the steps in the following section:
After the conversion is complete, you can import the restored folder and add that
folder as a path to the deduplication storage for Backup Exec.

Configuring an OpenStorage device

OpenStorage is a Veritas technology that allows intelligent disk devices to integrate
with Backup Exec.
You can find a list of compatible types of storage in the Backup Exec Hardware
Compatibility List.
Some intelligent disk devices can include multiple logical storage units. However,
each logical storage unit is added as a single OpenStorage device. When you add
an OpenStorage device, Backup Exec can automatically locate the logical storage
units on that device.

Note: When you delete or erase the media from an OpenStorage device, it may
take up to 48 hours for more space to become available. Backup Exec cannot
always calculate the amount of space that will be made available.

If you use Backup Exec Central Admin Server feature, you can share an
OpenStorage device between multiple Backup Exec servers. You can enable sharing
when you add an OpenStorage device. You can select new Backup Exec servers
to share an OpenStorage device or remove the sharing ability for Backup Exec
servers at any time. You can specify a different Backup Exec server on which to
run backup operations when the OpenStorage device is the source of a job, such
as a duplicate job, or a verify job.
See “Sharing a deduplication device between multiple Backup Exec servers”
on page 949.
Before you configure an OpenStorage device, have the following information
available:
■ What you want to name the OpenStorage device.
 Backup Exec Deduplication Feature 933
Configuring an OpenStorage device

■ The name of the provider for the OpenStorage device.

■ The name of the server and the logon account to use to access the OpenStorage
device. You cannot use the System Logon Account. It is recommended that you
select or create a logon account that you use exclusively for the deduplication
disk storage device. You should not use this account for any other purpose.
This account should not contain credentials that are subject to password update
policies.
■ Whether you want to enable encryption while data is transmitted to the
OpenStorage device and while the data is stored on it.
■ The number of concurrent operations to run on the device. This setting
determines the number of jobs can run at the same time on this device. The
number of jobs varies depending on your hardware and environment, so you
may need to adjust this setting more than once. It is recommended that you set
it low enough to avoid overloading your system, but high enough to process
your jobs in a timely manner.
To prevent a deduplication job from being sent to a non-deduplication device in a
storage pool, you cannot add an OpenStorage device to any storage pools.
To configure an OpenStorage device
1 On the Storage tab, in the Configure group, click Configure Storage.
2 Do one of the following:

If the Central Admin Server feature is not Click Network storage, and then click
installed Next.

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select a Backup Exec server, and then
click Next.
■ Click Network storage, and then click
Next.

3 Click OpenStorage, and then click Next.

4 Enter a name and description for the OpenStorage device, and then click Next.
5 Do one of the following:

If the provider for the OpenStorage device Select the provider, and then click Next.
is listed
 Backup Exec Deduplication Feature 934
Editing the properties of an OpenStorage device

If the provider for the OpenStorage device Do the following in the order listed:
is not listed
■ Select My provider is not listed here,
and then click Next.
■ Enter the provider name, and then click
Next.

6 Enter the name of the server and the logon account to use to access the
OpenStorage device, and then click Next.
7 Specify the number of concurrent operations that can run on the OpenStorage
device, and then click Next.
8 Review the summary, and then do one of the following:

To change the configuration 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 create or import the OpenStorage Click Finish.

device

See “Specifying a Backup Exec server that has proximity to a shared OpenStorage
device” on page 936.

Editing the properties of an OpenStorage device

You can view all of the properties of an OpenStorage device and you can change
some of the properties.
To edit the properties for an OpenStorage device
1 On the Storage tab, double-click the name of the OpenStorage device.
2 In the left pane, select Properties.
 Backup Exec Deduplication Feature 935
Editing the properties of an OpenStorage device

3 Change the following properties as needed:

Name Indicates the user-defined name for this

OpenStorage device.

Description Indicates the user-defined description of

this OpenStorage device.

Backup Exec server with device Indicates the server that you want to run
proximity backup operations when the OpenStorage
device is shared between servers in a
Central Admin Server feature environment.
You can specify a Backup Exec server that
has physical or logical proximity to the
OpenStorage device. Proximity of the
Backup Exec server to the device is an
advantage when the device is the source
of a job, such as a duplicate job or a verify
job, and you want to avoid running the job
over a WAN.

By default, the Backup Exec server on

which you create the OpenStorage device
is the server that runs the backup
operations for the device.

Logon account Indicates the name of the logon account

that is required to access the device.

Concurrent operations Indicates the maximum number of jobs that

you want to run at the same time on this
device.

Split data stream every Indicates the size at which you want
Backup Exec to span to a new image. The
default size is 50 GB.

Data stream size Indicates the size of a single write

operation that Backup Exec issues. The
default size varies based on the type of
device that is being used.

Stream handler Indicates whether stream handler is used.

Backup Exec sets this option automatically
when you select a server type. For some
types of devices, this option does not
appear at all. If Backup Exec does not set
this option, contact the device's vendor for
the recommended setting.
 Backup Exec Deduplication Feature 936
Specifying a Backup Exec server that has proximity to a shared OpenStorage device

Client-side deduplication Indicates whether client-side deduplication

is enabled for this OpenStorage device.

Client-side deduplication enables a remote

computer to send data directly to an
OpenStorage device. By using client-side
deduplication, the Backup Exec server is
bypassed, which leaves the Backup Exec
server free to perform other operations.

Disk space to reserve for non-Backup Displays the amount of disk space to set
Exec operations aside for applications other than Backup
Exec. The default amount is 5%.

4 Click Apply to save the changes.

Specifying a Backup Exec server that has

proximity to a shared OpenStorage device
You can specify a Backup Exec server that has physical or logical proximity to an
OpenStorage device to run operations for that device. Proximity of the Backup Exec
server to the device is an advantage when the device is the source of a job, such
as a duplicate job or a verify job, and you want to avoid running the job over a WAN.
By default, the Backup Exec server on which you create the device is the server
that runs the backup operations for the device. You can specify a Backup Exec
server with proximity only if the device is shared between servers in a Central Admin
Server feature environment.
If you remove the specified Backup Exec server with device proximity, you are
prompted to specify another server.
To specify a Backup Exec server that has proximity to a shared OpenStorage
device
1 On the Storage tab, double-click the name of the device.
2 In the left pane, select Properties.
3 In the Backup Exec server with device proximity field, on the drop-down
menu, select the server that you want to run operations for the device.
4 Click Apply.
 Backup Exec Deduplication Feature 937
Creating or importing deduplication disk storage

Creating or importing deduplication disk storage

Deduplication disk storage provides a disk-based backup folder that you can use
as a destination for backup jobs. When you use deduplication disk storage, only
unique data is stored.
Before you create a deduplication disk storage device, review the requirements. It
is recommended that you use a dedicated volume and a large amount of RAM for
deduplication disk storage.
See “Requirements for the Deduplication feature” on page 924.
You can create only one deduplication disk storage device on a Backup Exec server.
You can create deduplication disk storage on a storage array. However, if a
deduplication disk storage device already exists on a Backup Exec server, then
you cannot add another device to a storage array that is connected to that Backup
Exec server.
When you use Backup Exec's Delete option on a deduplication disk storage device,
the folder is removed from the Backup Exec database. However, the folder and the
files in it remain on the disk. When you delete backup sets from a deduplication
disk storage device, it may take up to 48 hours for more space to become available.
Backup Exec cannot always calculate the amount of space that will be made
available.
If you use the Backup Exec Central Admin Server feature, you can share a
deduplication disk storage device between multiple Backup Exec servers. You can
enable sharing when you add a deduplication disk storage device. You can select
new Backup Exec servers to share deduplication disk storage or remove the sharing
ability for Backup Exec servers at any time.
You can create new deduplication disk storage, or you can import an existing
deduplication disk storage device from another Backup Exec server.
See “Sharing a deduplication device between multiple Backup Exec servers”
on page 949.
Before you create or import a deduplication disk storage device, have the following
information available:
■ What you want to name the deduplication disk storage device.
■ The volume on which you want to create the deduplication disk storage device.
■ The path of the existing deduplication disk storage device, if you import a
deduplication disk storage device.
■ The information for the user account that was used when the existing
deduplication disk storage device was originally created.
 Backup Exec Deduplication Feature 938
Creating or importing deduplication disk storage

■ The logon account to use to access the deduplication disk storage device. You
cannot use the System Logon Account. It is recommended that you select or
create a logon account that you use exclusively for the deduplication disk storage
device. You should not use this account for any other purpose. This account
should not contain credentials that are subject to password update policies.
The following requirements are for the password credentials for a deduplication
disk storage device:
■ The password cannot be blank
■ The password cannot contain the following characters: &, ", <, >, %, ^
■ The password cannot start with the hyphen character: -
■ The password cannot end with the backslash character: \

■ Whether you want to enable encryption while the data is transmitted to the
deduplication disk storage device and while the data is stored on it. You should
not use the Backup Exec encryption options for backup jobs that deduplicate
data.
■ The number of concurrent operations to run on the device. This setting
determines the number of jobs that can run at the same time on this device.
The number of jobs varies depending on your hardware and environment, so
you may need to adjust this setting more than once. It is recommended that you
set it low enough to avoid overloading your system, but high enough to process
your jobs in a timely manner.
To create or import deduplication disk storage
1 On the Storage tab, in the Configure group, click Configure Storage.
2 Do one of the following:

If the Central Admin Server feature is not Select Disk-based storage, and then click
installed Next.

If the Central Admin Server feature is Do the following in the order listed:
installed
■ Select the Backup Exec server that you
want to configure deduplication disk
storage for, and then click Next.
■ Select Disk-based storage, and then
click Next.

3 Click Deduplication disk storage, and then click Next.

4 Enter a name and description for the deduplication disk storage device, and
then click Next.
 Backup Exec Deduplication Feature 939
Creating or importing deduplication disk storage

5 Do one of the following:

To create a new deduplication disk storage Click Next to accept the default location
device that appears in the field.

To import an existing deduplication disk Enter the path of the existing deduplication
storage device disk storage device, and then click Next.

6 Click the drop-down arrow and select the logon acount to use to access the
deduplication disk storage device, or click Add/Edit to create a logon acount,
and then click Next.
7 Specify if you want to enable encryption during transmission of data to the
deduplication disk storage device and while the data is stored on it, and then
click Next.
8 Specify the number of concurrent operations that can run on the deduplication
disk storage device, and then click Next.
9 Review the storage configuration summary, and do either of the following:

To change any of the selections Do the following in the order listed:

■ Click a review heading and make the

appropriate changes.
■ Click Next through the wizard to return
to the summary screen.
■ Click Finish.

To start the configuration Click Finish.

Editing the properties of a deduplication disk storage device

You can edit some properties of a deduplication disk storage device.
To edit the properties of a deduplication disk storage device
1 On the Storage tab, double-click the name of the deduplication disk storage
device.
2 In the left pane, select Properties.
 Backup Exec Deduplication Feature 940
Creating or importing deduplication disk storage

3 Change the following properties as needed:

Name Indicates the name that was entered when

the deduplication disk storage was
configured. You can change the name at
any time.

Description Indicates the description that was entered

when the deduplication disk storage was
configured. You can change the description
at any time.

Logon account Indicates the logon account that is being

used to access the device.

If you change the logon account after you

configure the device, additional steps are
required to enable access to the data that
is already stored on the device.

See “Changing the password for the logon

account for deduplication disk storage”
on page 944.

Encryption Enables or disables encryption while the

data is transmitted to the device, and while
the data is stored on the device.

You should not use the Backup Exec

encryption options for backup jobs that
deduplicate data.

Concurrent operations Indicates the maximum number of jobs that

you want to run at the same time on this
device.

The number of jobs varies depending on

your hardware and environment, so you
may need to adjust this setting more than
once. It is recommended that you set it low
enough to avoid overloading your system,
but high enough to process your jobs in a
timely manner.

Data stream size Indicates the size of a single write

operation that Backup Exec issues. The
default size varies based on the type of
device being used.
 Backup Exec Deduplication Feature 941
Creating or importing deduplication disk storage

Client-side deduplication Indicates whether client-side deduplication

is enabled for this device.

Client-side deduplication enables a remote

computer that is configured to send data
directly to the deduplication disk storage.
After the data is deduplicated, then only
unique data is sent directly to the
deduplication disk storage. By using this
option, the Backup Exec server is
bypassed, which leaves the Backup Exec
server free to perform other operations.

Percentage of disk space to reserve for Displays the amount of disk space to set
non-Backup Exec operations aside for applications other than Backup
Exec. The default amount is 5%

Log level Indicates the type of information you want

to include in the diagnostic logs for this
device. The choices range from critical
errors only to all types of messages.

Log retention period Indicates the number of days to keep the

diagnostic logs for this device.
 Backup Exec Deduplication Feature 942
Creating or importing deduplication disk storage

Low disk space - Critical Displays the critically low disk space
threshold at which you want Backup Exec
to send an alert. 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,

and you can change the amount of disk
space to megabytes or gigabytes. This
threshold must be less than the warning
low disk space threshold.

You may want to set the threshold slightly

higher than the minimum amount that you
need to run jobs. By doing so, you allow
time to address the disk space issue before
the jobs fail.

The default is 5%.

This property appears only if the

deduplication disk storage is on a storage
array.
 Backup Exec Deduplication Feature 943
Creating or importing deduplication disk storage

Low disk space - Warning Displays the low disk space threshold at
which you want Backup Exec to send an
alert. 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,

and you can change the amount of disk
space to megabytes or gigabytes. This
threshold must be less than the low disk
space threshold.

You may want to set the threshold slightly

higher than the minimum amount that you
need to run jobs. By doing so, you allow
time to address the disk space issue before
the jobs fail.

The default is 15%.

This property appears only if the

deduplication disk storage is on a storage
array.
 Backup Exec Deduplication Feature 944
Creating or importing deduplication disk storage

Low disk space Displays the low disk space threshold at

which you want Backup Exec to send an
alert. 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,

and you can change the amount of disk
space to megabytes or gigabytes.

You may want to set the threshold slightly

higher than the minimum amount that you
need to run jobs. By doing so, you allow
time to address the disk space issue before
the jobs fail.

The default is 25%.

This property appears only if the

deduplication disk storage is on a storage
array.

4 Click Apply to save the changes

Changing the password for the logon account for deduplication disk
storage
When you specify a Backup Exec logon account for a deduplication disk storage
device, an additional user account is created for the deduplication components with
the same user name and password. However, if you change the credentials for the
Backup Exec logon account, the credentials for the additional user account are not
changed automatically. You must use the spauser.exe utility to update the password
for the additional user account. This account is known as the "User 1" account when
you use the spauser.exe utility to view a list of user names that are associated with
the deduplication disk storage.
To change the password for the logon account for deduplication disk storage
1 Click the Backup Exec button, and then select Configuration and Settings.
2 Select Logon Accounts, and then select Manage Logon Accounts.
3 Select the Backup Exec logon account that you want to change, and then click
Edit.
4 Type the current password for the logon account, and then click OK.
 Backup Exec Deduplication Feature 945
Selecting storage devices for direct access sharing

5 Click Change Password.

6 Type the new password in the Password field and in the Confirm field.
7 Click OK.
8 At a command prompt, switch to the Backup Exec program file directory, and
then type the following command:
spauser.exe -c -u <UserName>

The default Backup Exec program file directory is C:<Backup Exec install
path>\Backup Exec
The user name is case-sensitive. If you do not know the user name, type the
following command to find the user name that is associated with "User 1":
spauser.exe -l

You are prompted for the old password and a new password. Ensure that the
new password is the same as the password that you used in step 6.

Selecting storage devices for direct access

sharing
Direct access enables a remote computer to send data directly to storage devices
that are hosted by a Backup Exec server. When direct access sharing is enabled,
the Backup Exec server is bypassed.
If you use a deduplication disk storage device or an OpenStorage device that
supports client-side deduplication, then enabling direct access sharing enables
Backup Exec to perform client-side deduplication. Note that client-side deduplication
is CPU-intensive.
Direct access sharing becomes available after you create a backup job in which a
deduplication device is selected and the following option is selected: Enable the
remote computer to directly access the storage device and to perform
client-side deduplication, if it is supported.
After the correctly configured backup job is created, then the option Direct access
sharing appears in the following locations.
■ On the details screen for a server on the Backup and Restore tab.
■ On the details screen for a storage device on the Storage tab.
In addition, the option Direct access properties appears on the details screen for
a server on the Backup and Restore tab.
 Backup Exec Deduplication Feature 946
Selecting storage devices for direct access sharing

To select storage devices for direct access sharing

1 Do one of the following:
■ On the Backup and Restore tab, double-click the server that you want to
set up to share devices.
■ On the Storage tab, double-click the storage device that you want to share.

2 In the left pane, select Direct access sharing.

3 Select the check box for the items that you want to share.

Note: After you enable direct access sharing for a client, you must restart the Backup
Exec services on the Backup Exec server. Click the Backup Exec button, select
Configuration and Settings, and then select Backup Exec Services, and then
click Restart all services.

See “Editing server properties for direct access” on page 946.

Editing server properties for direct access

For servers that are enabled for direct access, you can do the following:
■ Add or change a description of the server.
■ Enable or disable ICMP ping operations to detect the server.
■ Add or edit a logon account that is used to access the remote computer.
To edit server properties for direct access
1 On the Backup and Restore tab, double-click the server that is enabled for
direct access.
2 In the left pane, select Direct access properties.
 Backup Exec Deduplication Feature 947
Changing the location of a deduplication disk storage device

3 Edit the following options as needed:

Server name Indicates the name of the remote computer

or managed Backup Exec server.

Description Lets you enter a description of the server.

Port Indicates the port that is used for

communications between the Backup Exec
server and the remote computer.

Use ICMP ping operations to detect the Lets the Backup Exec server use ICMP
server ping to locate the remote computer.

Logon account Indicates the logon account that is required

to access the remote computer. You can
add a new logon account or edit an existing
account.

4 To save changes, click Apply.

Changing the location of a deduplication disk

storage device
You can change the location of an existing deduplication disk storage device. You
can move the deduplication disk storage device to another volume on the same
Backup Exec server. If the Central Admin Server feature is installed, you can move
the deduplication disk storage device to another Backup Exec server. Only one
deduplication disk storage device is supported per Backup Exec server.
It is recommended that you use the same name for the deduplication disk storage
device when you change the location, but it is not required.
To change the location of a deduplication disk storage device
1 Ensure that no jobs are running or are scheduled to run until you have
completed the process of changing the location of a deduplication disk storage
device.
2 Document the current path of the deduplication disk storage device by viewing
the properties of the device.
3 On the Storage tab, right-click the deduplication disk storage device, and then
click Disable.
4 Right-click the deduplication disk storage device again, and then click Delete.
5 When you are prompted to delete the device, click Yes.
 Backup Exec Deduplication Feature 948
Changing the location of a deduplication disk storage device

6 Click the Backup Exec button, select Configuration and Settings, select
Backup Exec Services, and then click Stop all services.
7 In Windows Explorer, copy the deduplication disk storage device to the new
path or volume.

Note: This step can take a long time as all of the data within the device is
copied to the new location.

8 On the Backup Exec Administration Console, click the Backup Exec button,
select Configuration and Settings, select Backup Exec Services, and then
click Restart all services.
9 On the Storage tab, click Configure Storage, click Disk-based storage, and
then click Next.
10 Click Deduplication disk storage, and then click Next.
11 Enter a name and description for the deduplication disk storage device, and
then click Next.
12 Do one of the following:

If the deduplication disk storage device Click Create a new deduplication disk
was created in Backup Exec 2012 and later storage device.

If the deduplication disk storage device Click Import an existing deduplication

was created in a version prior to Backup disk storage device, and then enter the
Exec 2012 path to which you moved the deduplication
disk storage device.

13 Click Next.
14 Specify the logon account that was used for the original deduplication disk
storage device, and then click Next.
15 Specify if you want to enable encryption, and then click Next.
16 Specify the number of concurrent operations to run on the deduplication disk
storage device, and then click Next.
17 Review the summary, and then click Finish.
18 When the deduplication disk storage device comes online, you can delete the
original files.
 Backup Exec Deduplication Feature 949
Sharing a deduplication device between multiple Backup Exec servers

Sharing a deduplication device between multiple

Backup Exec servers
If you use the Backup Exec Central Admin Server feature, you can select which
Backup Exec servers can share a deduplication disk storage device or an
OpenStorage device. When you add a deduplication disk storage device or an
OpenStorage device, the Backup Exec server that you used to add the device is
automatically selected for sharing.

Note: To share a deduplication disk storage device, you must add it as an

OpenStorage device on all Backup Exec servers that you want to access the device,
except for the Backup Exec server that was used to create it.

This type of sharing is not the same as direct access sharing. With direct access
sharing, a remote computer bypasses the Backup Exec server to directly access
storage devices that are hosted by the Backup Exec server.
See “Sharing storage devices” on page 467.
See “Selecting storage devices for direct access sharing” on page 945.

How to use client-side deduplication

Client-side deduplication enables a remote computer to send data directly to an
OpenStorage device or a deduplication disk storage device. By using client-side
deduplication, the Backup Exec server is bypassed, which leaves the Backup Exec
server free to perform other operations. If your deduplication device supports
client-side deduplication, a remote computer deduplicates data and then sends
only the unique data directly to a deduplication disk storage device or an
OpenStorage device. Client-side deduplication is available for Windows computers
and Linux computers.

Note: Client-side deduplication may increase the CPU utilization on the remote
computer if your deduplication device supports client-side deduplication.

When you create a backup job with client-side deduplication, keep in mind the
following items:
■ The backup job can include resources from only one remote computer.
■ The Agent for Windows is required on the remote Windows computer to perform
Windows client-side deduplication. The Agent for Linux is required on the Linux
computer to perform Linux client-side deduplication.
 Backup Exec Deduplication Feature 950
How to set up backup jobs for deduplication

Note: A maximum of 64 remote agents with client-side deduplication enabled

are allowed per Backup Exec server.

■ The remote computer must be pingable.

■ The remote computer cannot be a Backup Exec server.
■ A deduplication disk storage device or an OpenStorage device must be used
for the backup job.
■ The option Client-side deduplication must be enabled on the properties for
the storage device.
■ The option Enable the remote computer to directly access the storage
device and to perform client-side deduplication, if it is supported must be
selected in the Storage options for the backup job. This option is selected by
default when you select a deduplication disk storage device or an OpenStorage
device as the storage for a backup job.
If you do not configure the remote computer to use client-side deduplication, then
the data from the remote computer is sent to the Backup Exec server to be
deduplicated. Then, the deduplicated data is backed up to the deduplication disk
storage or the OpenStorage device. This process increases the CPU utilization on
the Backup Exec server. However, this process is useful if you are backing up older
remote computers.
See “About the Deduplication feature” on page 921.
See “How to set up backup jobs for deduplication” on page 950.
See “Editing the properties of an OpenStorage device” on page 934.
See “Editing the properties of a deduplication disk storage device” on page 939.

How to set up backup jobs for deduplication

Set up a backup job for deduplication by selecting the option Back Up to
Deduplication Disk Storage. Then, on the Storage settings, select either an
OpenStorage device or a deduplication disk storage device as the destination
device, and then select the deduplication method to use.
The following deduplication methods are available:
■ If you want to enable client-side deduplication, select the option Enable the
remote computer to directly access the storage device and to perform
client-side deduplication, if it is supported. This is the default option. If the
storage device that you select for the job does not support client-side
 Backup Exec Deduplication Feature 951
Using optimized duplication to copy deduplicated data between OpenStorage devices or deduplication disk
storage devices

deduplication, then either Backup Exec server-side deduplication or appliance

deduplication is used.
■ If you want to enable Backup Exec server-side deduplication, select the option
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. If the storage device that you select for the job does not
support server-side deduplication, then appliance deduplication is used.
See “How to use client-side deduplication” on page 949.

Using optimized duplication to copy deduplicated

data between OpenStorage devices or
deduplication disk storage devices
Backup Exec supports optimized duplication, which enables deduplicated data to
be copied directly from one OpenStorage device to another OpenStorage device
from the same vendor. Both devices must be attached to a single Backup Exec
server. For example, you can copy data from one Veritas PureDisk device to another
Veritas PureDisk device. Because the data is deduplicated, only unique data is
copied between the devices.
To copy data between OpenStorage devices or deduplication disk storage devices,
you must create a job to duplicate backup sets. The destination device for the
duplicate job must be the same type of device from the same vendor as the device
that was used in the source backup job. No additional settings are required;
optimized duplication occurs automatically when you set up a duplicate backup job
between appropriate devices. You can restore data from either device.
Optimized duplication can be performed on backup sets that were enabled for
Granular Recovery Technology (GRT). However, only deduplication disk storage
devices and PureDisk devices support optimized duplication for GRT-enabled
backup sets.
You can find a list of compatible types of storage devices in the Backup Exec
Hardware Compatibility List.

Note: The OpenStorage devices must be from the same vendor. You cannot perform
optimized duplication between OpenStorage devices from different vendors. If you
attempt to copy deduplicated data between OpenStorage devices from different
vendors, regular duplication is performed instead of optimized duplication.
 Backup Exec Deduplication Feature 952
Using optimized duplication to copy deduplicated data between OpenStorage devices or deduplication disk
storage devices

Using optimized duplication with the Central Admin Server

feature
If you use the Central Admin Server feature (CAS), the functionality of optimized
duplication is expanded to let you do the following:
■ Copy data from a deduplication disk storage device on one Backup Exec server
to a deduplication disk storage device on another Backup Exec server.
■ Copy data from an OpenStorage device that is attached to a Backup Exec server
to another OpenStorage device that is attached to a different Backup Exec
server.
To use optimized duplication with CAS, the following requirements must be met:
■ You must have a license for the Enterprise Server feature. CAS is installed as
part of the Enterprise Server feature.
■ All Backup Exec servers that you use with CAS as either a central administration
server or as managed Backup Exec servers must use the 64-bit version of
Windows.
■ You must have a central administration server and at least one managed Backup
Exec server in your CAS environment.
■ For client-side deduplication and Backup Exec server-side deduplication, you
must configure one deduplication disk storage on the Backup Exec server from
which you want to copy the deduplicated data. You must also configure one
deduplication disk storage on the Backup Exec server to which you want to copy
the deduplicated data.
■ For appliance deduplication, the Backup Exec server from which you want to
copy deduplicated data must have the appropriate plug-in for the OpenStorage
device and a properly configured OpenStorage device. In addition, the Backup
Exec server to which you want to copy the deduplication data must have the
appropriate plug-in for the OpenStorage device and a properly configured
OpenStorage device.
■ You must share deduplication devices between the Backup Exec servers.
■ You must inventory and catalog the media on the destination server before you
recover any files from the duplicated backup set. You must do this regardless
of how the catalog sharing option is configured for CAS.

Using optimized duplication to transfer backup data to a

remote location
You can use optimized duplication to transfer backup data to a remote location over
a WAN connection. You should prepopulate the destination deduplication disk
storage device with a full backup of the servers. This prepopulation task is also
 Backup Exec Deduplication Feature 953
Using optimized duplication to copy deduplicated data between OpenStorage devices or deduplication disk
storage devices

known as seeding the destination deduplication disk storage device. Seeding helps
avoid the time-consuming and bandwidth-intensive process of transmitting large
amounts of backup data over the low bandwidth WAN connection.
To seed a device, you can store a full backup to an external storage device such
as a USB drive. You can then transport the USB drive to the remote location where
the Backup Exec server and the destination deduplication disk storage device are
kept, and duplicate the backup data to the deduplication disk storage device.

How to set up optimized duplication

Set up a duplicate backup job to perform optimized duplication.

Table B-5 How to set up optimized duplication

Step For more information

If you are using CAS, do the following: See “Configuring an OpenStorage device”
on page 932.
■ Verify that you have one central
administration server and at least one See “Creating or importing deduplication disk
managed Backup Exec server. storage” on page 937.
■ Verify that the Backup Exec server from
which you want to copy the deduplicated
data has a deduplication disk storage
device (for client-side or Backup Exec
server-side deduplication) or an
OpenStorage device (for appliance
deduplication). Also verify that the Backup
Exec server to which you want to copy the
deduplicated data has a deduplication disk
storage device (for client or Backup Exec
server-side deduplication) or an
OpenStorage device (for appliance
deduplication).
■ Verify that the Backup Exec servers are
enabled for sharing.

Note: This information applies only to CAS.

If you do not have CAS, skip this step.

Create a backup job that uses an See “Backing up data” on page 153.
OpenStorage device or a deduplication disk
storage device as the destination.
 Backup Exec Deduplication Feature 954
Copying deduplicated data to tapes

Table B-5 How to set up optimized duplication (continued)

Step For more information

Create a job to duplicate backup sets and See “Duplicating backup sets or a job history
select the appropriate OpenStorage device manually” on page 216.
or deduplication disk storage as the
destination.
Note: The destination device for the
duplicate job must be the same type of device
from the same vendor as the device that was
used in the source backup job.

See “Sharing a deduplication device between multiple Backup Exec servers”

on page 949.

Copying deduplicated data to tapes

Backup Exec lets you copy deduplicated data from an OpenStorage device to tape
for long-term or off-site storage. When data is copied to tape, it is rehydrated. In
other words, the files are reassembled into their original form and are not
deduplicated.
To copy deduplicated data to tapes, you must create a duplicate backup job that
copies the backup sets from the OpenStorage device to a tape device.
See “Duplicating backup sets or a job history manually” on page 216.

Using deduplication with encryption

You should not use the Backup Exec encryption options for backup jobs that
deduplicate data. Data cannot be deduplicated when the Backup Exec encryption
options are used.
If you want deduplicated data to be encrypted on a deduplication disk storage
device, you can enable the encryption property on the deduplication disk storage
device.
See “Encryption key management” on page 627.
 Backup Exec Deduplication Feature 955
Restoring a deduplication disk storage device or deduplicated data

Restoring a deduplication disk storage device or

deduplicated data
You can restore a deduplication disk storage by running the Restore Wizard. When
you restore a deduplication disk storage device, the original folder is deleted and
then replaced by the restored folder.

Note: You cannot redirect the restore of a deduplication disk storage device. You
must restore a deduplication disk storage device to its original location.

To restore deduplicated data, you can create a regular restore job. No additional
settings are required.
See “Restoring data from a server, a backup set, a backup job, or a storage device”
on page 229.
To restore a deduplication disk storage device
1 On the Backup and Restore tab, right-click the computer for which you want
to restore the deduplication disk storage de