Veritas Backup Exec Administrator'

Veritas Backup Exec
Administrator's Guide
Legal Notice
Copyright © 2017 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. Please see the Third Party Legal Notice Appendix to this Documentation
or TPIP ReadMe File accompanying this product for more information on the Third Party
Programs.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of 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
500 E Middlefield Road
Mountain View, CA 94043
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)
CustomerCare@veritas.com
Japan
CustomerCare_Japan@veritas.com
Contents
Technical Support
Chapter 1
............................................................................................ 4
Introducing Backup Exec
................................................ 35
About Backup Exec ...................................................................... 35
How Backup Exec works ................................................................ 35
Chapter 2
Installation
........................................................................... 37
About the Backup Exec installation process and licensing options
...........................................................................................
About Backup Exec editions and licenses ..........................................
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 .....................................
Push-installing the Agent for Windows to remote computers ............
Installing updates to the Agent for Windows on remote computers
.....................................................................................
Installing the Agent for Windows in an Active Directory network
.....................................................................................
Using a command prompt to install the Agent for Windows on a
remote computer ..............................................................
Using a command script to install the Agent for Windows ................
Installing the Remote Administrator .................................................
Installing the Remote Administrator using the command line ...........
Running the Remote Administrator .............................................
Installing Backup Exec using the command line (silent mode) ................
Command line switches for silent mode installation of Backup
Exec ..............................................................................
38
40
43
44
47
48
51
60
62
69
70
75
76
80
83
84
85
87
90
90
Contents
Creating and using installation parameter files .............................. 97
About the installation log ................................................................ 98
Viewing the Installation Summary Report .......................................... 99
Repairing Backup Exec ................................................................. 99
Updating Backup Exec with Veritas Update ...................................... 100
Viewing installed updates ............................................................. 102
Uninstalling Backup Exec updates .................................................. 103
Viewing license information ........................................................... 103
Backup Exec license contract information ........................................ 104
Updating expired license contracts ........................................... 104
Managing license contract customer numbers ............................ 105
About upgrading to Backup Exec ................................................... 105
Upgrade checklist for Backup Exec .......................................... 107
Using the Migration Report to determine how existing jobs changed
after an upgrade from a previous version of Backup Exec
.................................................................................... 108
Post-installation tasks .................................................................. 108
Uninstalling Backup Exec ............................................................. 109
Uninstalling Backup Exec using the command line ............................. 110
Uninstalling Backup Exec features from the local Backup Exec server
.......................................................................................... 110
Chapter 3
Getting Started
................................................................. 112
About the Backup Exec Administration Console ................................
Displaying the version information for Backup Exec ...........................
How to sort, filter, and copy information on the Backup Exec
Administration Console ..........................................................
Customizing views on the Backup Exec Administration Console ...........
Configuring the Home tab .............................................................
Configuring the Veritas RSS Reader ...............................................
Creating a disaster preparation plan (DPP) ......................................
Getting started with backups .........................................................
Chapter 4
Backups
112
115
115
117
118
123
124
126
.............................................................................. 129
How to prepare for your first backup with Backup Exec .......................
Required user rights for backup jobs ...............................................
About the list of servers on the Backup and Restore tab .....................
Adding servers that you want to back up to the list of servers on the
Backup and Restore tab .........................................................
Removing servers from the list of servers on the Backup and Restore
tab .....................................................................................
Creating a server group ...............................................................
131
131
132
133
134
134
8
Contents
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 .........................................................................
How Backup Exec backs up and restores volumes that are enabled
for deduplication in Windows .............................................
How Backup Exec backs up and restores Microsoft Virtual Hard
Disk (vhd) files ...............................................................
About selecting data to back up ....................................................
Changing the order in which backup sources are backed up ................
Excluding files from backups .........................................................
Including specific files with a backup job's backup selections ...............
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 ................................................................
135
136
136
137
137
138
139
139
149
149
150
156
158
161
163
166
167
175
177
181
182
183
184
190
191
192
194
194
196
197
198
198
200
200
205
206
208
9
Contents
Chapter 5
Restores
............................................................................. 210
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 ...................................................
Configuring default options for catalogs .....................................
Moving the Backup Exec catalogs to a new directory ...................
Cataloging backup sets ................................................................
Chapter 6
Job management and monitoring
211
213
213
217
218
219
222
224
224
225
226
226
226
227
230
231
............................... 233
How to monitor and manage jobs in Backup Exec .............................
About the Job Monitor ..................................................................
Viewing job activity details for active jobs ...................................
Canceling an active job ..........................................................
Holding jobs ........................................................................
Removing the hold on jobs .....................................................
Holding the job queue ............................................................
Removing the hold on the job queue .........................................
Running a scheduled job immediately .......................................
Changing the priority for a scheduled job ...................................
Deleting scheduled jobs .........................................................
About the Job History ..................................................................
Viewing the history of a job .....................................................
Deleting a job from the Job History ...........................................
Running a job from the Job History ...........................................
Viewing the job log .....................................................................
Finding text in the job log ........................................................
Printing the job log ................................................................
233
235
237
237
238
239
240
240
241
242
243
244
245
245
246
247
247
249
10
Contents
Saving the job log .................................................................
Linking from the job log to the Veritas Technical Support website
....................................................................................
How to use job logs with vertical applications ..............................
Configuring default job log options ............................................
Error-handling rules for failed or canceled jobs ..................................
Creating a custom error-handling rule .......................................
Enabling or disabling error-handling rules ..................................
Deleting a custom error-handling rule ........................................
Enabling an error-handling rule for a failed job ............................
Custom error-handling rule for recovered jobs ............................
About the cluster failover error-handling rule ...............................
List of job statuses in Backup Exec .................................................
Setting job status and recovery options ...........................................
Chapter 7
249
250
250
251
252
253
254
254
255
255
256
257
262
Alerts and notifications ................................................... 265
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
..........................................................................................
Active alerts properties ..........................................................
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 ...................................
Removing a recipient from a group ...........................................
Disabling email or text message alert notification for a recipient ............
Editing recipient notification properties ............................................
Deleting recipients ......................................................................
Configuring alert categories ..........................................................
Assigning recipients to receive notifications for specific alert categories
..........................................................................................
Sending a notification when a job completes ....................................
Notification options for jobs .....................................................
Disabling notifications for a specific alert category .............................
266
267
269
270
271
271
272
272
273
273
274
274
275
277
279
280
280
281
281
282
284
284
285
285
11
Contents
Configuring default alert settings ....................................................
Enabling or disabling pop-up alerts .................................................
SNMP traps for Backup Exec alerts ................................................
Installing and configuring the SNMP system service .....................
Installing the Windows Management Instrumentation performance
counter provider .............................................................
Installing the Windows Management Instrumentation provider for
SNMP ..........................................................................
Uninstalling the Windows Management Instrumentation
performance counter provider ...........................................
Uninstalling the Windows Management Instrumentation provider
for SNMP ......................................................................
Chapter 8
Disk-based and network-based storage
Cloud-based storage devices
291
292
292
292
................... 293
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 ...............................................................
Changing the location of a disk storage device ............................
Editing disk storage properties .................................................
How to restore data from a reattached or reinserted disk-based storage
device ................................................................................
Configuring disk cartridge storage ..................................................
Editing disk cartridge properties ...............................................
Editing disk cartridge media properties ......................................
How data lifecycle management (DLM) deletes expired backup sets
on disk-based storage ...........................................................
Backup sets ..............................................................................
Changing the expiration date of backup sets on disk-based storage
....................................................................................
Retaining backup sets on disk-based storage to prevent them
from expiring ..................................................................
Releasing retained backup sets on disk-based storage .................
Viewing the contents or properties of backup sets .......................
Chapter 9
286
287
288
291
293
295
296
297
300
301
307
308
309
313
315
321
324
325
326
327
...................................... 329
About cloud-based storage devices ................................................
Amazon S3 cloud-based storage ...................................................
Requirements for configuring an Amazon S3 cloud-based storage
device ..........................................................................
Configuring storage for Amazon cloud storage ............................
329
330
330
331
12
Contents
Google cloud-based storage .........................................................
Requirements for configuring a Google cloud-based storage device
....................................................................................
Configuring storage for Google cloud storage .............................
Microsoft Azure cloud-based storage ..............................................
Requirements for configuring a Microsoft Azure cloud-based
storage device ...............................................................
Configuring storage for Microsoft Azure cloud storage ..................
Private cloud-based storage .........................................................
Requirements for configuring a private cloud-based storage device
....................................................................................
Creating a cloud instance for a private cloud ..............................
Configuring storage for a private cloud-based storage device
....................................................................................
Viewing and editing existing cloud instances for a private cloud
....................................................................................
Deleting a cloud instance for a private cloud ...............................
About S3-Compatible Cloud Storage ..............................................
Configuring S3-Compatible Cloud Storage with Backup Exec
....................................................................................
Editing the properties of a cloud-based storage device .......................
Best practices for using cloud-based storage ....................................
Changing default cloud storage settings ..........................................
About the Veritas Backup Exec™ CloudConnect Optimizer .................
Configuring the Veritas Backup Exec™ CloudConnect Optimizer
....................................................................................
Chapter 10
333
334
336
336
337
338
338
340
340
342
342
343
344
345
347
348
350
350
Legacy backup-to-disk folders ..................................... 354
Legacy backup-to-disk folders ......................................................
Changing the name or description of a legacy backup-to-disk
folder ...........................................................................
Changing the buffered read setting for a legacy backup-to-disk
folder ...........................................................................
Changing the location of a legacy backup-to-disk folder ................
Recreating a legacy backup-to-disk folder and its contents ............
Restoring data from a legacy backup-to-disk folder ......................
Chapter 11
333
Tape storage
354
355
355
356
357
357
..................................................................... 360
Support for tape drives and robotic libraries ...................................... 361
Adding or replacing devices with the Hot-swappable Device Wizard
.......................................................................................... 361
Installing tape device drivers ........................................................ 362
13
Contents
Editing tape drive properties ..........................................................
Viewing tape drive statistics ..........................................................
Robotic libraries in Backup Exec ....................................................
Requirements for setting up robotic library hardware ....................
Inventorying robotic libraries when Backup Exec services start
....................................................................................
Configuring barcode rules for a robotic library ............................
Initializing a robotic library when the Backup Exec service starts
....................................................................................
Defining a cleaning slot .........................................................
Editing robotic library properties ...............................................
Creating robotic library partitions ....................................................
Adding or removing tape drives in a robotic library partition ...........
Reassigning a slot base number for robotic libraries .....................
Editing robotic library slot properties .........................................
Removing or reconfiguring robotic library partitions ......................
Managing tapes .........................................................................
Default media sets ................................................................
Overwrite protection periods and append periods in media sets
....................................................................................
Creating media sets for tapes ..................................................
Changing the overwrite protection period or the append period for
a media set ...................................................................
Changing the name and description of a media set ......................
Changing the media vault or vaulting periods for a media set
....................................................................................
Deleting a media set ..............................................................
Renaming a media set ...........................................................
Media overwrite protection levels for tape media .........................
Overwriting allocated or imported tape media .............................
How Backup Exec searches for overwritable media in tape drives
....................................................................................
Viewing tapes that are used by a job .........................................
Labeling tape media ....................................................................
About labeling imported tape media .........................................
How barcode labels become media labels for tapes .....................
Renaming a tape media label .................................................
How WORM media is used in Backup Exec .....................................
Default media vaults ....................................................................
Changing the name or description of a media vault ......................
Creating media vault rules to move tape media to and from media
vaults ...........................................................................
Updating the tape media location in media vaults ........................
364
369
369
370
371
371
375
376
376
377
378
379
379
380
382
382
386
390
393
395
395
396
396
396
397
397
400
400
402
402
403
403
404
405
406
407
14
Contents
Deleting a media vault ...........................................................
Moving tape media to a vault ...................................................
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 .......................................................
Chapter 12
Storage device pools
Storage operations
411
411
412
414
...................................................... 418
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 .........................
Chapter 13
407
408
408
409
409
418
421
421
422
.......................................................... 423
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 ..........................................
Initializing a robotic library ............................................................
Formatting a tape as a WORM tape ................................................
424
425
428
430
431
431
438
447
448
449
449
450
450
451
452
453
453
454
454
455
15
Contents
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 .................................
Chapter 14
Conversion to virtual machines
................................... 478
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 ...............
Chapter 15
Configuration and settings
455
455
456
457
458
465
468
474
478
486
487
494
502
509
511
518
............................................ 522
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 ...............................
524
528
535
541
542
544
551
553
556
560
568
571
573
574
574
575
576
16
Contents
Exporting the Backup Exec Database encryption key .........................
Refreshing Backup Exec Database encryption keys ...........................
Configuring encryption for the connection to the Backup Exec Database
..........................................................................................
Scheduling Backup Exec to check logon accounts .............................
Configuring Backup Exec to discover data to back up .........................
Adding discovered servers to the list of servers in Backup Exec ...........
Backup networks ........................................................................
Changing network and security options for Backup Exec .....................
Using Backup Exec with firewalls ...................................................
Backup Exec ports ................................................................
Backup Exec listening ports ....................................................
About enabling a SQL instance behind a firewall .........................
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 ...............................................
Storage options for DBA-initiated jobs .......................................
General options for DBA-initiated jobs .......................................
Network options for DBA-initiated jobs ......................................
Duplicate job settings for DBA-initiated jobs ...............................
Configuring settings for Veritas™ Information Map .............................
Backup Exec logon accounts ........................................................
Creating a Backup Exec logon account .....................................
Editing a Backup Exec logon account .......................................
Changing the password for a Backup Exec logon account .............
Replacing a Backup Exec logon account ...................................
Deleting a Backup Exec logon account ......................................
Changing your default Backup Exec logon account ......................
Creating a new Backup Exec System Logon Account ...................
Copying logon account information to another Backup Exec server
....................................................................................
Testing logon accounts ..........................................................
Starting and stopping Backup Exec services ....................................
Changing the credentials for a service account .................................
Changing startup options for Backup Exec services ...........................
580
582
583
587
588
590
591
593
595
597
599
600
600
603
604
605
607
608
615
616
617
618
618
619
623
623
624
628
631
634
635
637
637
638
639
640
641
641
642
642
644
17
Contents
Configuring audit logs ..................................................................
Viewing the audit log ...................................................................
Removing entries from the audit log ................................................
Saving an audit log to a text file .....................................................
Copying configuration settings to another Backup Exec server .............
Viewing server properties .............................................................
Configuring default backup settings ................................................
Chapter 16
Reports
645
646
647
647
647
648
649
............................................................................... 655
Reports in Backup Exec ...............................................................
Running a report now ..................................................................
Scheduling a report .....................................................................
Creating a custom report ..............................................................
Adding or removing fields on a custom report .............................
Changing filters for a custom report ..........................................
Changing the way data is grouped or sorted in a custom report
....................................................................................
Changing graph options in custom reports .................................
Previewing custom reports ......................................................
Copying 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 ..............................................
Alert History report ................................................................
Alert History By Backup Exec Server report ................................
Audit Log report ....................................................................
Backup Job Success Rate report .............................................
Backup Recommendations report ............................................
Backup Resource Success Rate report .....................................
Backup Sets by Media Set report .............................................
Backup Size By Resource report ..............................................
Cloud Storage Summary report ...............................................
Daily Device Utilization report ..................................................
Deduplication Device Summary report ......................................
Deduplication Summary report ................................................
Device Summary report .........................................................
655
657
657
659
663
664
666
667
667
668
668
669
669
670
670
670
671
672
673
677
678
678
679
679
680
680
681
682
682
683
684
685
18
Contents
Disk Storage Summary report .................................................
Error-Handling Rules report ....................................................
Event Recipients report ..........................................................
Failed Backup Jobs report ......................................................
Jobs Summary report ............................................................
Managed Backup Exec Servers report ......................................
Media Audit report ................................................................
Media Errors report ...............................................................
Media Required for Recovery report .........................................
Media Summary report ..........................................................
Media Vault Contents report ....................................................
Move Media to Vault report .....................................................
Operations Overview report ....................................................
Overnight Summary report ......................................................
Problem Files report ..............................................................
Recently Written Media report .................................................
Recovery Ready Validation Summary .......................................
Resource Protected Recently report .........................................
Resource Risk Assessment report ............................................
Restore Set Details by Resource report .....................................
Retrieve Media from Vault report ..............................................
Robotic Library Inventory report ...............................................
Scheduled Server Workload report ...........................................
Scratch Media Availability report ..............................................
Test Run Results report ..........................................................
Chapter 17
Troubleshooting Backup Exec
686
687
688
688
689
690
691
692
693
693
694
695
695
697
698
699
699
700
701
702
703
703
704
705
706
..................................... 707
Troubleshooting hardware-related issues in Backup Exec ...................
How to get more information about alerts and error messages .............
Troubleshooting backup issues in Backup Exec ................................
Troubleshooting failed components in the SAN ................................
Troubleshooting offline storage devices in a SAN .......................
Finding hardware errors in a SAN ............................................
Resetting the SAN ................................................................
Bringing storage devices online after an unsafe device removal
event in a SAN ...............................................................
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 .....................................
708
710
711
713
713
715
716
717
717
718
718
719
720
720
19
Contents
About Backup Exec diagnostic tools ...............................................
Running the Veritas QuickAssist Help Tool ......................................
Generating a diagnostic file for troubleshooting Backup Exec ...............
Command line switches for a diagnostic file ...............................
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 .................................................
Chapter 18
720
721
721
723
725
726
726
Using Backup Exec in cluster environments ........... 728
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 .............
Two-node cluster with locally attached storage devices .................
Two-node cluster with tape devices on a shared SCSI bus ............
Configuring a shared SCSI bus for tape devices ..........................
Multi-node clusters on a fibre channel SAN with the Central Admin
Server feature ................................................................
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 .......................................
Disaster recovery of a cluster ........................................................
Using Simplified Disaster Recovery to prepare for disaster recovery
of a cluster ....................................................................
Recovering nodes on the cluster using Simplified Disaster
Recovery ......................................................................
Recovering Backup Exec on a Microsoft cluster using Simplified
Disaster Recovery ..........................................................
729
729
730
731
732
733
734
735
735
736
737
738
739
740
741
743
745
746
746
747
748
748
749
20
Contents
Recovering the entire cluster using a manual disaster recovery
procedure .....................................................................
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 ..............................................................
Chapter 19
Simplified Disaster Recovery
751
752
....................................... 753
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 .....................................................................
Changing the default path for the disaster recovery information
files ..............................................................................
Disaster recovery information file data paths ..............................
Creating a Simplified Disaster Recovery disk image ...........................
Contents of the Simplified Disaster Recovery disk image ..............
User scenarios when a user starts the Create Recovery Disk
Wizard ..........................................................................
Preparing to recover from a disaster by using Simplified Disaster
Recovery ............................................................................
Hardware replacement during disaster recovery ..........................
Prepare to recover IBM computers with Simplified Disaster
Recovery ......................................................................
Recovering a computer with Simplified Disaster Recovery ...................
Recovery notes for using Simplified Disaster Recovery with storage
pools and storage spaces .................................................
Recovery notes for using Simplified Disaster Recovery with
Exchange, SQL, SharePoint, CAS, Hyper-V hosts, and the
Deduplication feature ......................................................
Advanced Disk Configuration on the Recover This Computer Wizard
..........................................................................................
Chapter 20
749
750
751
753
754
757
761
763
765
766
766
768
781
783
784
785
786
787
792
795
796
Integration with Veritas™ Information Map .............. 800
About Veritas™ Information Map .................................................... 800
How Backup Exec works with Veritas™ Information Map .................... 801
21
Contents
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 .....................
Appendix A
805
805
806
809
Veritas Backup Exec Agent for Windows ................. 810
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 ..............................
Starting the Backup Exec Agent Utility ......................................
Viewing the activity status of the remote computer in the Backup
Exec Agent Utility ...........................................................
Viewing the activity status of the remote computer from the system
tray ..............................................................................
Starting the Backup Exec Agent Utility automatically on the remote
computer ......................................................................
Setting the refresh interval on the remote computer .....................
About publishing the Agent for Windows to Backup Exec servers
....................................................................................
Adding Backup Exec servers that the Agent for Windows can
publish to ......................................................................
Editing Backup Exec server information that the Agent for Windows
publishes to ...................................................................
Removing Backup Exec servers that the Agent for Windows can
publish to ......................................................................
Configuring database access for Oracle operations .....................
Removing a security certificate for a Backup Exec server that has
a trust with the Agent for Windows .....................................
Using the Backup Exec Agent Utility Command Line Applet .................
Backup Exec Agent Utility Command Line Applet switches ..................
Appendix B
801
802
Veritas Backup Exec Deduplication Option
810
811
812
812
813
814
814
815
816
816
817
817
818
819
819
822
822
823
............. 827
About the Deduplication feature ..................................................... 828
Deduplication methods for Backup Exec agents ................................ 830
Requirements for the Deduplication feature ...................................... 831
22
Contents
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 ...............................
Editing the properties of a deduplication disk storage device ..........
Changing the password for the logon account for deduplication
disk storage ...................................................................
Selecting storage devices for direct access sharing ...........................
Editing server properties for direct access ..................................
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 ..........
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 .......................................
Appendix C
836
837
839
842
844
845
847
852
853
854
855
857
857
858
859
862
862
863
863
864
Veritas Backup Exec Agent for VMware ................... 866
About the Agent for VMware .........................................................
Requirements for using the Agent for VMware ..................................
Using the Agent for VMware with Windows Server 2016 .....................
About installing the Agent for VMware .............................................
Adding VMware vCenter Servers and ESX/ESXi hosts to the list of
servers on the Backup and Restore tab .....................................
Viewing details about VMware resources .........................................
Installing the Agent for Windows on VMware virtual machines ..............
Push-installing the Agent for Windows to VMware virtual machines
..........................................................................................
Recommendations for when to use virtual-based backup and
agent-based backup ..............................................................
Backing up VMware virtual machines ..............................................
Setting default backup options for virtual machines ......................
867
867
869
869
870
871
871
873
873
875
881
23
Contents
How Backup Exec automatically backs up new VMware virtual
machines during a backup job ..........................................
Using Granular Recovery Technology (GRT) with the Agent for
VMware ........................................................................
How cataloging works with VMware virtual machine backups
....................................................................................
Restoring VMware virtual machines and vmdk files ............................
About instant recovery of a VMware virtual machine ..........................
Requirements for instant recovery of a VMware virtual machine
....................................................................................
Notes about instant recovery of a VMware virtual machine ............
Creating an instant recovery job for a VMware virtual machine
....................................................................................
Removing an instantly recovered VMware virtual machine ............
Troubleshooting the Agent for VMware ............................................
About Recovery Ready for VMware virtual machines .........................
Requirements for validating a VMware virtual machine for recovery
....................................................................................
Notes about validating a VMware virtual machine for recovery
....................................................................................
Best Practices for validating VMware virtual machine for recovery
....................................................................................
Creating a validate virtual machine for recovery job .....................
Appendix D
885
885
889
890
898
901
901
902
905
906
907
911
911
912
912
Veritas Backup Exec Agent for Microsoft Hyper-V
.......................................................................................... 916
About the Agent for Microsoft Hyper-V ............................................
Requirements for using the Agent for Microsoft Hyper-V .....................
About installing the Agent for Microsoft Hyper-V ................................
Notes about using the Agent for Hyper-V ........................................
Disk space optimization with the Agent for Hyper-V ...........................
Adding a Hyper-V host to the list of servers on the Backup and Restore
tab .....................................................................................
Viewing details about Hyper-V resources .........................................
Installing the Agent for Windows on Hyper-V virtual machines ..............
Push-installing the Agent for Windows to Hyper-V virtual machines
..........................................................................................
Backing up Microsoft Hyper-V virtual machines .................................
Setting default backup options for Hyper-V .................................
How Backup Exec automatically protects new virtual machines
during a backup job .........................................................
917
918
920
921
923
923
924
925
926
927
933
935
24
Contents
Using Granular Recovery Technology (GRT) with the Agent for
Hyper-V ........................................................................
About backing up and restoring highly available Hyper-V virtual
machines ......................................................................
How cataloging works with Hyper-V virtual machine backups
....................................................................................
Restoring Microsoft Hyper-V virtual machines ...................................
About instant recovery of a Hyper-V virtual machine ..........................
Requirements for instant recovery of a Hyper-V virtual machine
....................................................................................
Notes about instant recovery of a Hyper-V virtual machine ...........
Creating an instant recovery job for a Hyper-V virtual machine
....................................................................................
Post-instant recovery tasks ....................................................
About removing an instantly recovered Hyper-V virtual machine
....................................................................................
Removing an instantly recovered Hyper-V virtual machine ............
Best practices for instant recovery of a Hyper-V virtual machine
....................................................................................
About Recovery Ready for Hyper-V virtual machines .........................
Requirements for validating a Hyper-V virtual machine for recovery
....................................................................................
Notes about validating a Hyper-V virtual machine for recovery
....................................................................................
Best practices about validating a Hyper-V virtual machine for
recovery .......................................................................
Creating a validate virtual machine for recovery .........................
Appendix E
936
939
939
941
945
949
950
951
953
953
954
955
956
960
960
961
961
Veritas Backup Exec Agent for Microsoft SQL
Server ............................................................................ 964
About the Agent for Microsoft SQL Server ........................................
Requirements for using the SQL Agent ...........................................
About installing the SQL Agent ......................................................
Backup strategies for SQL ............................................................
Adding SQL Servers to the list of servers on the Backup and Restore
tab .....................................................................................
Configuring Backup Exec to run a consistency check before every SQL
backup ...............................................................................
Using snapshot technology with the SQL Agent ................................
Using database snapshots for SQL Server .......................................
Backing up SQL databases and transaction logs ...............................
Setting default backup options for SQL Server ............................
964
966
967
967
969
969
970
971
973
985
25
Contents
Restoring SQL databases and transaction logs ................................. 995
Restoring the SQL master database ......................................... 997
Restarting SQL using database copies ...................................... 998
Disaster recovery of a SQL Server ................................................ 1000
Manual recovery of a SQL Server .......................................... 1002
Appendix F
Appendix G
Veritas Backup Exec Agent for Microsoft
Exchange Server ...................................................... 1003
About the Backup Exec Exchange Agent .......................................
Requirements for using the Exchange Agent ..................................
Granting permissions on the Exchange Server to enable database
backups and restores, and Granular Recovery Technology
operations .........................................................................
About installing the Exchange Agent .............................................
Adding Exchange Servers and database availability groups to the list
of servers on the Backup and Restore tab ................................
Managing preferred server configurations for Microsoft Exchange
Database Availability Groups .................................................
Recommended configurations for Exchange ..................................
Requirements for accessing Exchange mailboxes ...........................
Backup strategies for Exchange ...................................................
How Granular Recovery Technology works with the Exchange
Information Store ...............................................................
Snapshot and offhost backups with the Exchange Agent ...................
Backing up Exchange data .........................................................
Setting default backup options for Exchange Server ...................
Restoring Exchange data ...........................................................
Disaster recovery of an Exchange Server .......................................
1021
1023
1025
1033
1039
1045
Veritas Backup Exec Agent for Microsoft
SharePoint .................................................................
1047
About the Agent for Microsoft SharePoint .......................................
About installing the Agent for Microsoft SharePoint ..........................
Requirements for the Agent for Microsoft SharePoint ........................
Using the Agent for Microsoft SharePoint with SharePoint Server
2010/2013 and SharePoint Foundation 2010/2013 .....................
Adding a Microsoft SharePoint server farm to the list of servers on the
Backup and Restore tab .......................................................
Backing up Microsoft SharePoint data ...........................................
Setting default backup options for SharePoint ...........................
Restoring Microsoft SharePoint data .............................................
1004
1004
1008
1013
1014
1014
1017
1018
1019
1047
1048
1048
1049
1050
1050
1054
1057
26
Contents
Disabling or enabling communication between a Microsoft SharePoint
web server and Backup Exec ................................................ 1059
Viewing or changing SharePoint farm properties .............................. 1060
Disaster recovery of Microsoft SharePoint 2010/2013 data ................ 1061
Appendix H
Veritas Backup Exec Agent for Oracle on
Windows or Linux Servers .................................... 1066
About the Backup Exec Oracle Agent ............................................
About installing the Oracle Agent ..................................................
Configuring the Oracle Agent on Windows computers and Linux servers
........................................................................................
Configuring an Oracle instance on Windows computers ..............
Viewing an Oracle instance on Windows computers ...................
Editing an Oracle instance on Windows computers ....................
Deleting an Oracle instance on Windows computers ..................
Enabling database access for Oracle operations on Windows
computers ...................................................................
Configuring an Oracle instance on Linux servers .......................
Viewing an Oracle instance on Linux servers ............................
Editing an Oracle instance on Linux servers .............................
Deleting an Oracle instance on Linux servers ............................
Enabling database access for Oracle operations on Linux servers
..................................................................................
About authentication credentials on the Backup Exec server ..............
Setting authentication credentials on the Backup Exec server for
Oracle operations .........................................................
Deleting an Oracle server from the Backup Exec server’s list of
authentication credentials ...............................................
About Oracle instance information changes ....................................
About backing up Oracle databases ..............................................
About backing up Oracle RAC databases .................................
About performing a DBA-initiated backup job for Oracle ..............
Oracle backup options .........................................................
About restoring Oracle resources .................................................
About DBA-initiated restore for Oracle .....................................
Oracle restore options .........................................................
About redirecting a restore of Oracle data ................................
Oracle advanced restore options ...........................................
Performing a redirect restore of an Oracle 12c database using
Backup Exec ................................................................
Requirements for recovering the complete Oracle instance and
database using the original Oracle server ...........................
1066
1067
1068
1069
1073
1074
1075
1075
1078
1080
1081
1081
1082
1083
1084
1085
1086
1086
1088
1089
1090
1091
1094
1094
1095
1095
1097
1100
27
Contents
Recovering the complete Oracle instance and database using the
original Oracle server .....................................................
Requirements for recovering the complete Oracle instance or
database to a computer other than the original Oracle server
..................................................................................
Recovering the complete Oracle instance or database to a
computer other than the original Oracle server ....................
Best practices for Backup Exec Agent for Oracle on Windows and
Linux Servers .....................................................................
Appendix I
1101
1102
1103
1104
Veritas Backup Exec Agent for Enterprise Vault
........................................................................................ 1108
About the Agent for Enterprise Vault .............................................
Requirements for the Enterprise Vault Agent ...................................
About installing the Enterprise Vault Agent .....................................
About backup methods for Enterprise Vault backup jobs ...................
Enterprise Vault backup options .............................................
About backing up Enterprise Vault components ...............................
About consistency checks for Enterprise Vault databases and
Compliance and Discovery Accelerator databases .....................
Restoring Enterprise Vault ..........................................................
Enterprise Vault restore options .............................................
About restoring individual files and folders with the Enterprise
Vault Agent ..................................................................
About automatic redirection of Enterprise Vault components under
an Enterprise Vault server ...............................................
Redirecting a restore for an Enterprise Vault component .............
Configuring Enterprise Vault to use the name of the new SQL Server
that holds the Directory database ...........................................
Best practices for the Enterprise Vault Agent ..................................
About the Backup Exec Migrator for Enterprise Vault ........................
Backup Exec Migrator for Enterprise Vault requirements .............
How the Backup Exec Migrator works .....................................
About using staged migrations with Backup Exec and the Backup
Exec Migrator ...............................................................
About Backup Exec Migrator events ........................................
About Backup Exec Migrator logs ...........................................
About deleting files migrated by Backup Exec Migrator ...............
Configuring the Backup Exec Migrator .....................................
About viewing migrated Enterprise Vault data ...........................
About retrieving migrated Enterprise Vault data .........................
About the Partition Recovery Utility .........................................
1108
1112
1113
1113
1116
1117
1120
1120
1122
1125
1125
1126
1128
1130
1130
1131
1131
1135
1136
1136
1137
1138
1146
1147
1148
28
Contents
Enterprise Vault logon account ..................................................... 1151
Enterprise Vault options .............................................................. 1152
Appendix J
Veritas Backup Exec Agent for Microsoft Active
Directory .....................................................................
About the Agent for Microsoft Active Directory .................................
Requirements for the Agent for Microsoft Active Directory .................
About backing up Active Directory and ADAM/AD LDS .....................
Editing options for Active Directory and ADAM/AD LDS backup
jobs ............................................................................
Microsoft Active Directory backup job options ...........................
About restoring individual Active Directory and ADAM/AD LDS objects
........................................................................................
Appendix K
1153
1153
1154
1155
1156
1158
1159
Veritas Backup Exec Central Admin Server
Option .......................................................................... 1162
About the Central Admin Server feature .........................................
Requirements for installing CAS ...................................................
How to choose the location for CAS storage and media data .............
About installing the Central Admin Server feature ............................
Push-installing a managed Backup Exec server from the central
administration server .....................................................
Managed Backup Exec Server Configuration options ..................
Installing a managed Backup Exec server across a firewall .........
Upgrading an existing CAS installation ..........................................
Changing a Backup Exec server to a central administration server
........................................................................................
Changing a Backup Exec server to a managed Backup Exec server
........................................................................................
Deleting a managed Backup Exec server from a CAS environment
........................................................................................
Renaming a central administration server .......................................
Renaming a managed Backup Exec server ....................................
How to reduce network traffic in CAS ............................................
CAS distributed, centralized, and replicated catalog locations .............
Changing the settings for a managed Backup Exec server .................
What happens when CAS communication thresholds are reached
........................................................................................
Enabling or disabling communications between the managed
Backup Exec server and the central administration server
..................................................................................
1163
1165
1166
1168
1169
1173
1175
1177
1179
1180
1181
1183
1184
1185
1185
1187
1198
1199
29
Contents
Alerts and notifications in CAS .....................................................
Enabling managed Backup Exec servers to use any available network
interface card ....................................................................
About job delegation in CAS ........................................................
About copying jobs instead of delegating jobs in CAS .................
About adding storage devices in a CAS environment ........................
How data lifecycle management (DLM) works in a CAS environment
........................................................................................
Obtaining media audit information for a managed Backup Exec server
........................................................................................
How to use Backup Exec server pools in CAS ................................
Selecting a Backup Exec server pool for backups ......................
Creating a Backup Exec server pool .......................................
Adding managed Backup Exec servers to a Backup Exec server
pool ...........................................................................
Deleting a Backup Exec server pool ........................................
Removing a managed Backup Exec server from a Backup Exec
server pool ..................................................................
How centralized restore works in CAS ...........................................
How CAS restores data that resides on multiple storage devices
..................................................................................
About recovering failed jobs in CAS ..............................................
Pausing or resuming a managed Backup Exec server ......................
Stopping or starting Backup Exec services for a managed Backup
Exec server .......................................................................
Viewing managed Backup Exec server properties ............................
Viewing the settings for a central administration server .....................
Disaster recovery in CAS ............................................................
Troubleshooting CAS .................................................................
Running the Backup Exec Utility for CAS operations ........................
Uninstalling Backup Exec from the central administration server ........
Uninstalling Backup Exec from a managed Backup Exec server .........
Appendix L
1199
1201
1201
1202
1202
1202
1203
1204
1205
1205
1206
1206
1207
1207
1208
1210
1211
1212
1213
1216
1218
1219
1221
1221
1222
Veritas Backup Exec Advanced Disk-based
Backup Option .......................................................... 1223
About the Advanced Disk-based Backup feature .............................
How to use synthetic backups in place of recurring full backups ..........
Setting default backup options for the Advanced Disk-based Backup
feature ..............................................................................
About true image restore for synthetic backups ...............................
How to use off-host backup to process remote computer backups on
the Backup Exec server ........................................................
1223
1224
1226
1227
1229
30
Contents
Configuring off-host backup options for a backup job ........................
Best practices for off-host backup .................................................
Troubleshooting off-host backups .................................................
Off-host backup issues with hardware providers ..............................
Appendix M
Veritas Backup Exec NDMP Option
......................... 1239
Features of the NDMP feature .....................................................
Requirements for using the NDMP feature .....................................
About installing the NDMP feature ................................................
Adding NDMP servers to Backup Exec ..........................................
Sharing the tape drives on NDMP servers between multiple Backup
Exec servers ......................................................................
NDMP backup options for NDMP servers .......................................
NDMP server backup selections ..................................................
How to use patterns to exclude files and directories from an NDMP
server backup ....................................................................
Supported configurations for duplicating data from NDMP servers
........................................................................................
About restoring and redirecting restore data for NDMP servers ...........
NDMP server restore options .................................................
Setting the default backup options for the NDMP feature ...................
Viewing the properties of an NDMP server .....................................
NDMP server properties .......................................................
Viewing storage properties for an NDMP server ..............................
Storage properties for an NDMP server ...................................
Appendix N
1232
1234
1235
1238
1239
1240
1241
1241
1243
1243
1245
1246
1248
1248
1249
1252
1253
1253
1254
1254
Veritas Backup Exec Agent for Linux ....................... 1256
About the Agent for Linux ...........................................................
About open files and the Agent for Linux ........................................
Requirements for the Agent for Linux ............................................
About installing the Agent for Linux ...............................................
Installing the Agent for Linux .................................................
About the Backup Exec operators (beoper) group for the Agent
for Linux ......................................................................
About establishing trust for a remote Linux computer in the Backup
Exec list of servers .............................................................
Establishing trust and adding a remote Linux computer to the
Backup Exec list of servers .............................................
Adding additional Backup Exec servers to which the Agent for Linux
can publish information ........................................................
About configuring the Agent for Linux ............................................
1257
1257
1257
1258
1259
1261
1262
1263
1263
1264
31
Contents
Excluding files and directories from all backup jobs for Linux computers
........................................................................................
Editing configuration options for Linux computers ............................
Configuration options for Linux computers ................................
About backing up a Linux computer by using the Agent for Linux ........
Linux backup options ...........................................................
About backing up and restoring Novell Open Enterprise Server
(OES) components .......................................................
About restoring data to Linux computers ........................................
About restoring Novell OES components .................................
Restore job options for Linux computers ..................................
Editing the default backup job options for Linux computers ................
Default backup job options for Linux computers .........................
Uninstalling the Agent for Linux ....................................................
Manually uninstalling the Agent for Linux .................................
Run-time scripts to remove when manually uninstalling the Agent
for Linux ......................................................................
Starting the Agent for Linux daemon .............................................
Stopping the Agent for Linux daemon ............................................
Troubleshooting the Agent for Linux ..............................................
Appendix O
Veritas Backup Exec Remote Media Agent for
Linux ............................................................................
About the Remote Media Agent for Linux ......................................
How the Remote Media Agent for Linux works ................................
Requirements for the Remote Media Agent for Linux ........................
About open files and the Remote Media Agent for Linux ....................
About installing the Remote Media Agent for Linux ...........................
Installing the Remote Media Agent for Linux .............................
Uninstalling the Remote Media Agent for Linux ...............................
Starting the Remote Media Agent for Linux daemon .........................
Stopping the Remote Media Agent for Linux daemon .......................
About establishing trust for a Remote Media Agent for Linux computer
in the Backup Exec list of servers ..........................................
Establishing trust and adding a Remote Media Agent for Linux
computer to the Backup Exec list of servers ........................
Adding additional Backup Exec servers to which Remote Media Agent
for Linux can publish ............................................................
Finding simulated tape library files ................................................
About the Backup Exec operators (beoper) group for the Remote Media
Agent for Linux ...................................................................
1265
1265
1266
1273
1274
1275
1276
1277
1277
1278
1278
1280
1281
1282
1283
1284
1284
1290
1291
1292
1293
1294
1294
1295
1298
1299
1299
1300
1300
1301
1301
1302
32
Contents
Creating the Backup Exec operators (beoper) group manually for
the Remote Media Agent for Linux ....................................
About adding a Linux server as a Remote Media Agent for Linux .......
Adding a Linux server as a Remote Media Agent for Linux ..........
Remote Media Agent for Linux options ....................................
Changing the port for communications between the Backup Exec server
and the Remote Media Agent for Linux ....................................
About creating storage device pools for devices attached to the Remote
Media Agent for Linux .........................................................
Editing properties for the Remote Media Agent for Linux ..................
Remote Media Agent for Linux properties .................................
Deleting a Remote Media Agent for Linux from the Backup Exec list
of servers ..........................................................................
Sharing a Remote Media Agent for Linux between multiple Backup
Exec servers ......................................................................
About backing up data by using the Remote Media Agent for Linux
........................................................................................
About restoring data by using the Remote Media Agent for Linux ........
About the Tape Library Simulator Utility .........................................
Creating a simulated tape library ..................................................
Simulated Tape Library options ..............................................
Viewing simulated tape libraries properties .....................................
Simulated tape library properties ............................................
Deleting a simulated tape library ..................................................
Managing simulated tape libraries from the command line .................
Command line switches for the Tape Library Simulator Utility .............
Troubleshooting the Remote Media Agent for Linux .........................
Appendix P
Accessibility and Backup Exec
1303
1304
1304
1304
1306
1307
1307
1307
1308
1309
1309
1309
1310
1311
1312
1312
1313
1313
1314
1315
1316
.................................. 1319
About accessibility and Backup Exec ............................................
About keyboard shortcuts in Backup Exec ......................................
Home tab keyboard shortcuts ................................................
Backup and Restore tab keyboard shortcuts .............................
Job Monitor tab keyboard shortcuts ........................................
Storage tab keyboard shortcuts ..............................................
Reports tab keyboard shortcuts ..............................................
General keyboard navigation within the Backup Exec user interface
..................................................................................
Keyboard navigation within dialog boxes in Backup Exec ............
List box navigation in Backup Exec ...............................................
Tabbed dialog box navigation in Backup Exec .................................
About setting accessibility options ................................................
1319
1320
1321
1321
1329
1332
1340
1341
1341
1342
1342
1343
33
Contents
Glossary .......................................................................................................... 1344
Index
................................................................................................................ 1350
34
Chapter
1
Introducing Backup Exec
This chapter includes the following topics:
■
About Backup Exec
■
How Backup Exec works
About Backup Exec
Veritas 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 35.
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
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 315.
■
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.
36
Chapter
2
Installation
This chapter includes the following topics:
■
About the Backup Exec installation process and licensing options
■
About Backup Exec editions and licenses
■
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
Installation
About the Backup Exec installation process and licensing options
■
Viewing license information
■
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:
38
Installation
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, Backup Exec connects to the
Veritas Web service and requests the license
key associated with the Entitlement ID. 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 Veritas License File You can import your Veritas License Files
(.slf) from a network share or from a local
drive.
You must go to the Veritas Licensing Portal
website to obtain them. From the Veritas
Licensing Portal website, 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 Veritas license files during the installation
process, a trial version is installed.
After Backup Exec has been installed, you can install additional agents and features
by upgrading to Backup Exec Bronze, Silver, or Gold Edition, or by purchasing
licenses for separate agents and features in Backup Exec Custom Edition. 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.
Backup Exec may install the following additional products during the installation
process:
39
Installation
About Backup Exec editions and licenses
■
Microsoft Report Viewer 2010 SP1
■
Microsoft.NET Framework 4.5.2
■
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 SP2
See “Installing Backup Exec by using the Installation Wizard” on page 51.
See “Installing additional agents and features to the local Backup Exec server”
on page 60.
See “Push-installing Backup Exec to remote computers” on page 62.
See “Push-installing the Agent for Windows to remote computers” on page 70.
See “Installing Backup Exec using the command line (silent mode)” on page 90.
See “Backup Exec preinstallation checklist” on page 43.
About Backup Exec editions and licenses
Backup Exec is available in several editions, each requiring its own license. The
available editions of Backup Exec are as follows:
Table 2-2
Backup Exec editions
Edition
Description
Features
Bronze Edition
Backup Exec
Bronze edition
provides file
server protection
on-premises and
in the cloud.
Backup Exec Bronze includes
support for unlimited non-loader
tape devices, but does not support
robotic or virtual tape libraries.
In addition, Backup Exec Bronze
includes support for the following
agents and features:
■
Backup Exec Server
■
Agent for Windows
■
Agent for VMware and Hyper-V
■
Deduplication feature
40
Installation
About Backup Exec editions and licenses
Table 2-2
Backup Exec editions (continued)
Edition
Description
Features
Silver Edition
Backup Exec
Silver edition
provides file
server,
database, and
application
protection
on-premises and
in the cloud.
Backup Exec Silver includes support
for a total of 4 robotic and virtual
tape drives across all libraries.
In addition, Backup Exec Silver
includes support for the following
agents and features:
■
Backup Exec Server
■
Agent for Windows
■
Agent for Linux
■
Agent for VMware and Hyper-V
■
Agent for Applications and
Databases
Deduplication feature
■
Gold Edition
Backup Exec
Gold edition
provides file
server,
database, and
application
protection
on-premises and
in the cloud, with
centralized
management of
backup servers
for multi-site
locations.
Backup Exec Gold supports an
unlimited number of robotic and
virtual tape libraries.
In addition, Backup Exec Gold
includes support for the following
agents and features:
■
Backup Exec Server
■
■
Central Admin Server feature
(CAS)
Agent for Windows
■
Agent for Linux
■
Remote Media Agent for Linux
■
Agent for VMware and Hyper-V
■
■
Agent for Applications and
Databases
Deduplication feature
■
NDMP feature
■
Enterprise Server feature
41
Installation
About Backup Exec editions and licenses
Table 2-2
Backup Exec editions (continued)
Edition
Description
Features
Custom Edition
Backup Exec
Each agent and feature requires its
Custom Edition own separate license in Backup
allows you to
Exec Custom.
license agents
and features
separately to
build and
configure a
backup solution
that meets your
needs.
V-Ray Edition
Backup Exec
V-Ray Edition
protects virtual
environments
only.
Backup Exec V-Ray Edition includes
support for the following:
■
Backup Exec Server
■
Agent for VMware and Hyper-V
■
Unlimited deployment of Agent
for Windows or Agent for Linux,
on VMware and Hyper-V virtual
machines only
Unlimited deployment of the
Agent for Applications and
Databases, on VMware and
Hyper-V virtual machines only.
Deduplication feature
■
■
In addition, you can add licenses for
individual agents and features on an
a la carte basis to extend Backup
Exec V-Ray Edition's functionality.
42
Installation
Backup Exec preinstallation checklist
Table 2-2
Backup Exec editions (continued)
Edition
Description
Features
Capacity Edition
Backup Exec
Capacity Edition
and Capacity
Edition Lite offer
unlimited
deployment of
their features
and agents, up
to a certain
amount of data
backed up as
specified by your
license.
Backup Exec Capacity Edition offers
more agents and features than
Capacity Edition Lite. For the full list
of agents and features supported by
these editions, refer to the Backup
Exec Licensing Guide.
Capacity Edition Lite
Trial edition
The trial edition A trial edition of Backup Exec
of Backup Exec includes all features and agents
allows you to
included with Backup Exec Gold.
use all features
and agents for a
limited time. A
trial license of
Backup Exec
expires in 60
days, but can be
extended to 90
days.
For more information about Backup Exec editions and licenses, refer to the Price
and Licensing Guide.
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.
43
Installation
Running the Environment Check before installing or upgrading Backup Exec
See “Running the Environment Check before installing or upgrading Backup
Exec” on page 44.
■
Check the Backup Exec Hardware Compatibility List to confirm that your storage
device hardware is supported in this version of Backup Exec.
■
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 642.
■
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 SP2 setup file for the language
that you want to install from the Microsoft website before you install Backup
Exec if all of the following are true:
■
You want to use a local Backup Exec SQL Express instance.
■
You have non-English SQL Server instances on the computer on which you
want to install Backup Exec.
Running the Environment Check before installing
or upgrading Backup Exec
The Veritas Backup Exec Environment Check is a utility that runs on a computer
automatically during installation and that reports the following:
44
Installation
Running the Environment Check before installing or upgrading Backup Exec
■
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 48.
■
If the third-party software that uses Backup Exec ports is configured correctly.
■
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-3
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.
45
Installation
Running the Environment Check before installing or upgrading Backup Exec
3
Do any of the following:
To check the configuration of the local
computer
Check Local Environment Check.
To check the configuration of a remote
computer
Check Remote Environment Check.
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
list
To add the name of a computer manually
Do the following:
■
Click Add Server From List.
■
Select the computer from the list, and
then click Next.
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.
■
■
■
■
To remove the name of a computer from
the list of computers on which the
Environment Check runs
6
Type the user name and password for
this computer.
Click OK.
Do the following:
■
Select the computer from the list.
■
Click Remove.
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.
46
Installation
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 SP2 components that are required to run Backup Exec.
Backup Exec prompts you to do one of the following:
■
Install the required Microsoft SQL Server Express components with Backup
Exec and create a default Backup Exec instance. This is the recommended
action.
Note: SQL Express can be installed on a server that runs other instances of
SQL Express or full versions of SQL.
■
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. Veritas recommends that
you avoid installing Backup Exec to a SQL Server instance that uses case-sensitive
collation.
When Backup Exec is installed into an existing instance, the automated master
database restore feature is not available. To recover the Master database, you
must replace it with the Master database copy that Backup Exec automatically
creates and updates when the Master database is backed up.
When Backup Exec applies updates, the SQL instance is stopped, which may cause
other databases in the same instance to lose connectivity. If a remote SQL instance
is used, ensure that Backup Exec has good network connectivity with the instance
to avoid errors. A default local instance of SQL Express is recommended.
You cannot install multiple Backup Exec Databases on the same SQL Server
instance.
47
Installation
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 48.
System requirements for Backup Exec
The following are the minimum system requirements to run this version of Backup
Exec:
Table 2-4
Minimum system requirements
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 Express
SQL Server 2014 Express with SP2
48
Installation
System requirements for Backup Exec
Table 2-4
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
language
The Backup Exec user interface displays in the format that is configured
in the Region and Language settings in the Control Panel. You can
change the Backup Exec display language so that you can view user
interface items in a different language.
If Backup Exec does not support a language, the user interface displays
in English. The user interface also displays in English if the menu and
dialog boxes option is set to a language other than the language you
want to display the user interface. If you do not use one of the supported
languages listed in Table 2-5, you must install the English language
pack in Windows.
Installation disk
space
1.26 GB (Typical installation)
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
49
Installation
System requirements for Backup Exec
Table 2-4
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.
Support is available for the first drive in each robotic library when you
purchase Backup Exec. To enable support for additional robotic library
drives, upgrade to Backup Exec Silver or Gold Edition, or purchase a
license for the Library Expansion Feature for each additional drive if
you are using Backup Exec Custom Edition. Backup Exec Silver Edition
supports up to four drives. Backup Exec Gold Edition supports an
unlimited number of drives.
Table 2-5
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 51.
50
Installation
Installing Backup Exec by using the Installation Wizard
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
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. Note that a custom installation cannot be used to add
agents and features to Backup Exec Bronze, Silver, or Gold which are not included
with those editions.
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.
51
Installation
Installing Backup Exec by using the Installation Wizard
To install a typical installation of Backup Exec
1
From the installation media browser, click Install Products, and then select
Backup Exec.
If the required version of Microsoft .NET Framework is not already installed on
this computer, Backup Exec installs it.
The Backup Exec installation program uses the Microsoft .NET Framework
version 4.5.2. However, not all versions of Windows support .NET Framework
4.5.2. If the Backup Exec installation program encounters an operating system
that requires the use of a different version of the .NET Framework, Backup
Exec blocks the installation and provides an error message that instructs you
to install the required version of .NET Framework.
2
On the Welcome panel, read the license agreement, and then click I accept
the terms of the license agreement and click Next.
3
On the Installation Type panel, click Typical installation, and then click Next.
4
The Backup Exec Environment Check will run automatically.
5
Review the results of the Environment Check. Do one of the following:
6
■
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.
On the Add Licenses panel, use one of the following methods to add licenses.
To enter entitlement IDs manually, perform the following steps in order:
■
In the Enter an Entitlement ID field, type the appropriate entitlement ID
from your license certificate.
■
Click Add to List.
■
Repeat for each entitlement ID.
Note: An Internet connection is required to validate the entitlement IDs. If you
do not have an Internet connection, import the licenses from the Veritas License
File included with your license certificate or install a trial version.
To import licenses from the Veritas License File, perform the following in order:
■
Click Import Veritas License File.
■
Browse to the location of your license files, and then select the appropriate
file.
52
Installation
Installing Backup Exec by using the Installation Wizard
To install a trial version, do not enter an entitlement ID or import a license file.
Go to the next step.
When you are finished entering entitlement IDs, click Next.
7
You may be prompted to enter contact information for license contract
entitlement IDs.
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.
To install a trial edition of Backup Exec, in the Select a Backup Exec edition
license to install on the computer field, select Trial.
When you are finished on the Review Licenses panel, click Next.
9
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.
53
Installation
Installing Backup Exec by using the Installation Wizard
10 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.
11 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.
12 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.
54
Installation
Installing Backup Exec by using the Installation Wizard
■
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.
To proceed without push-installing the Agent for Windows, click Next.
13 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 Veritas 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.
55
Installation
Installing Backup Exec by using the Installation Wizard
14 Select the I have read and understood the information check box, and then
click Next.
15 Review the Backup Exec installation summary, and then click Install.
16 If you installed the Agent for Windows on remote computers, on the Remote
Installation dialog box, click Next.
17 When the installation is complete, you can run Veritas Update, choose to restart
the system, view the readme, or remove the Backup Exec shortcut from the
desktop.
18 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 BKUPINST20.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.
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.5.2. However, not all versions of Windows support .NET Framework
4.5.2. If the Backup Exec installation program encounters an operating system
that requires the use of a different version of the .NET Framework, Backup
Exec blocks the installation and provides an error message that instructs you
to install the required version of .NET Framework.
2
On the Welcome panel, read the license agreement, and then click I accept
the terms of the license agreement 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.
56
Installation
Installing Backup Exec by using the Installation Wizard
5
The Backup Exec Environment Check will run automatically.
6
Review the results of the Environment Check. Do one of the following:
7
■
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.
On the Add Licenses panel, use one of the following methods to enter licenses:
To enter entitlement IDs manually, perform the following steps in order:
■
In the Enter an Entitlement ID field, type the appropriate entitlement ID
from your license certificate.
■
Click Add to List.
■
Repeat for each license for each edition that you want to install.
■
Click Next to validate the entitlement IDs.
Note: An Internet connection is required to validate the entitlement IDs. If you
do not have an Internet connection, import the licenses from the Veritas License
File or install a trial version.
To import licenses from the Veritas License file, perform the following steps in
order:
■
Click Import Veritas License File.
■
Browse to the location of your license files, and then select the appropriate
file.
To install a trial version, do not enter an entitlement ID or import a license file.
Go to the next step.
When you are finished entering entitlement IDs, click Next.
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.
57
Installation
Installing Backup Exec by using the Installation Wizard
■
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.
The Review Licenses panel also allows you to view and customize the capacity
for each entitlement ID.
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. Veritas recommends 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.
58
Installation
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 47.
Click Next when you are finished.
59
Installation
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.
Veritas recommends 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 run Veritas Update, 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
If you have installed Backup Exec Custom, or if you performed a custom install of
another edition and chose not to install all of the agents and features included with
that edition, you can install additional features later. Note that you cannot install
more features to Backup Exec Bronze, Silver, and Gold Editions than are included
with those licenses. If you want to add an agent or feature to Backup Exec Custom
Edition, each new agent or feature requires its own license. Review the
documentation for any agent or feature to ensure that your system meets all of its
minimum requirements. 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.
60
Installation
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 1211.
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
manually
Do the following in the order listed:
■
Note: An Internet connection
is required to validate the
serial numbers. If you do not ■
have an Internet connection, ■
import the licenses from the
Veritas License File or install
a trial version.
To import licenses from the
Veritas license file
To install a trial version
3
In the Enter a Serial number field, type the
appropriate serial number from your license
certificate.
Click Add to List.
Repeat for each serial number.
Do the following in the order listed:
■
Click Import Veritas License File.
■
Browse to the location of your license files, and then
select the appropriate file.
Do not type a serial number or import a license file. Go
to step 5.
Click Next.
You may be prompted to enter contact information for license contract serial
numbers.
4
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.
61
Installation
Push-installing Backup Exec to remote computers
5
Click Next.
6
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.
7
Click Next.
8
If you are prompted, enter information or choose settings for the additional
features that you want to install. Click Next after each selection.
9
Review the Backup Exec installation summary, and then click Install.
The Backup Exec services are stopped while the additional 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.
10 Click Finish.
Push-installing Backup Exec to remote computers
You cannot push install Backup Exec in the following scenarios:
■
Push install from a 64-bit operating system to a 32-bit operating system
■
Push install from a 32-bit operating system to a 32-bit or a 64-bit operating
system
If you install Backup Exec through Terminal Services and the installation media is
on a shared drive (network share) you must use a UNC path. Installation by mapped
drives is not supported.
You can set up multiple server installations. Backup Exec processes up to five
remote computer installations concurrently.
Note: Backup Exec installs the required version of Microsoft .NET Framework if it
is not already installed on the computer where you want to push-install Backup
Exec. The Backup Exec installation program uses the Microsoft .NET Framework
version 4.5.2. However, not all versions of Windows support .NET Framework 4.5.2.
If the Backup Exec installation program encounters an operating system that requires
the use of a different version of the .NET Framework, Backup Exec blocks the
installation and provides an error message that instructs you to install the required
version of .NET Framework.
62
Installation
Push-installing Backup Exec to remote computers
Before you install Backup Exec to remote computers, you should review the special
considerations.
Table 2-6
Special considerations for installing Backup Exec to remote
computers
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.
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:
63
Installation
Push-installing Backup Exec to remote computers
To push-install Backup Exec to remote
computers from the installation media
Do the following steps in the order listed:
■
■
■
■
■
■
To push-install Backup Exec to remote
computers from the Backup Exec server
2
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.
Click the Backup Exec button, select
Installation and Licensing, and then
select Install Agents and Backup Exec
Servers on Other Servers.
On the Remote Computers panel, do one of the following:
To install Backup Exec on one remote
computer
Do the following in the order listed:
■
Click Add.
■
Select Add a Single Computer.
■
Select Veritas Backup Exec, and then
click Next.
Type the fully qualified name of the
remote computer or click Browse
Remote Computers to locate the
remote computer.
■
To install Backup Exec on multiple
computers using the same settings
Do the following in the order listed:
■
Click Add.
■
Select Add Multiple Computers with
the Same Settings.
Select Veritas 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.
■
■
■
64
Installation
Push-installing Backup Exec to remote computers
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: An Internet ■ Click Add to List.
connection is
■ Repeat for each license for each feature or agent that you
required to validate
want to install.
the serial numbers. ■ Click Next to validate the serial numbers.
If you do not have
an Internet
connection, import
the licenses from
the Veritas License
File or install a trial
version.
6
To import licenses
from a Veritas
License File
Do the following in the order listed:
To install a trial
version
Do not type a serial number or import a license file. Go to step 8.
■
Click Import Veritas License File.
■
Browse to the location of your license files, and then select
the appropriate file.
Click Next.
You may be prompted to enter contact information for license contract serial
numbers.
7
If you entered product activation serial numbers, on the Review Licenses
panel, do one of the following:
65
Installation
Push-installing Backup Exec to remote computers
To install a licensed version of Backup
Exec
Do the following in the order listed:
■
■
■
To install a trial version
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.
In the Select a Backup Exec edition
license to install on the computer field,
select Trial.
8
Click Next.
9
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.
10 In the Destination Folder field, enter the location where you want to install
Backup Exec.
11 Click Next.
12 Complete the service account credentials options as follows:
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.
66
Installation
Push-installing Backup Exec to remote computers
13 Click Next.
14 Do one of the following to select a location on which to store the Backup Exec
Database, and then click Next.
To create a local Backup Exec
SQL Express instance
Do the following in the order listed:
■
■
To use an existing SQL Server
2008 R2 SP2 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.
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.
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 47.
Backup Exec attempts to connect to the instance.
This step is skipped during upgrades.
15 Click Next.
16 Make a selection for tape device drivers, and then click Next.
Note: You do not need to install 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 362.
17 Click Next.
67
Installation
Push-installing Backup Exec to remote computers
18 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.
19 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
computers
Click Add, and then click Add Multiple
Computers with the Same Settings.
To add multiple remote computers by
importing an existing list of computers
Click Import and Export, and then select
one of the following options:
■
■
Select Import from File to enable
Backup Exec to add the names of the
remote computers from a selected list.
Select Import Servers Published to
this Backup Exec server to enable
Backup Exec to add the names of all
the remote computers that are set up
to publish to this Backup Exec server.
You must enter remote computer logon
credentials for the list of remote computers.
To 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.
68
Installation
Methods for installing the Agent for Windows
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
the validation
Right-click the name of the computer, and
then click Fix Error.
To enable Backup Exec to attempt to
re-validate an invalid remote computer
Right-click the name of the computer, and
then click Retry Validation.
20 After all of the computers in the list are validated and the list is complete, click
Next.
21 Review the Backup Exec installation summary, and then click Install.
See “About the installation log” on page 98.
22 Click Next, and then click Finish to exit the wizard.
If you did not restart the remote computer, you may need to do it now in order
for the configuration to take effect.
Methods for installing the Agent for Windows
You can install the Agent for Windows by using the following methods, depending
on your environment:
■
Push-install the Agent for Windows to one or more remote computers from the
Backup Exec server.
See “Push-installing the Agent for Windows to remote computers” on page 70.
■
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 133.
■
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 76.
■
Use a command prompt.
69
Installation
Methods for installing the Agent for Windows
See “Using a command prompt to install the Agent for Windows on a remote
computer” on page 80.
■
Use command script files.
See “Using a command script to install the Agent for Windows” on page 83.
Push-installing the Agent for Windows to remote computers
You can push-install the Agent for Windows to remote computers from a Backup
Exec server. Push installations save time by eliminating the need for local access
at the target computer for the installation to be successful. You can push-install the
Agent for Windows to an unlimited number of remote computers. Backup Exec can
process up to five active push-installations at a time.
Review the following special considerations before you install the Agent for Windows
on remote computers.
Table 2-7
Special considerations for installing the Agent for Windows
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 90.
Server core option of Windows Server
2008/2012 and later
Backup Exec installs a command-line version
of the Agent for Windows on the computers
that run the Server Core installation option of
Windows Server 2008/2012 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 823.
70
Installation
Methods for installing the Agent for Windows
Table 2-7
Special considerations for installing the Agent for Windows
(continued)
Item
Consideration
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.
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
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. 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 132.
71
Installation
Methods for installing the Agent for Windows
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.
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 80.
To push-install the Agent for Windows to remote computers
1
Do one of the following:
To push-install the Agent for Windows to
remote computers from the installation
media
Do the following steps in the order listed:
■
■
■
■
■
To push-install the Agent for Windows to
remote computers from the Backup Exec
server
2
From the installation media browser,
click Installation, and then click
Backup Exec.
On the Welcome panel, select I accept
the terms of the license agreement,
and the click Next.
Click Custom installation.
Uncheck Local Installation, and then
check Remote Installation.
Click Next.
Click the Backup Exec button, select
Installation and Licensing, and then
select Install Agents and Backup Exec
Servers on Other Servers.
Do one of the following
To install the Agent for Windows on one
remote computer
Do the following steps in the order listed:
■
■
■
■
On the Remote Computers panel, click
Add.
Select Add a Single Computer.
Select Agent for Windows, and then
click Next.
Type the fully qualified name of the
remote computer or click Browse
Remote Computers to locate the
remote computer.
72
Installation
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
computers
Click Add, and then click Add Multiple
Computers with the Same Settings.
73
Installation
Methods for installing the Agent for Windows
To add multiple remote computers by
importing an existing list of computers
Click Import and Export, and then select
one of the following options:
■
■
Select Import from File to enable
Backup Exec to add the names of the
remote computers from a selected list.
Select Import Servers Published to
this Backup Exec server to enable
Backup Exec to add the names of all
the remote computers that are set up
to publish to this Backup Exec server.
You must enter remote computer logon
credentials for the list of remote computers.
To 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.
8
To fix the errors that were located during
the validation
Right-click the name of the computer, and
then click Fix Errors.
To enable Backup Exec to attempt to
re-validate an invalid remote computer
Right-click the name of the computer, and
then click Retry Validation.
After all of the computers in the list are validated and the list is complete, click
Next.
74
Installation
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.
75
Installation
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
before it is rescheduled
Specify the maximum amount of time after
the scheduled start time at which you want
Backup Exec to consider the job to be
missed and reschedule it.
Cancel the job if it is still running x
hours after its scheduled start time
Specify the amount of time after the job's
scheduled start time at which you want
Backup Exec to cancel the job if it is still
running.
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 Veritas
to automatically restart the remote
Backup Exec Agent for Windows when computer, if required.
a restart is required
4
Click OK.
Installing the Agent for Windows in an Active Directory network
You can centrally manage the installation of the Backup Exec Agent for Windows
to computers in an Active Directory network. You configure the installation once,
and then use a Group Policy Object to assign that installation to computers in an
76
Installation
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-8
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 78.
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.
77
Installation
Methods for installing the Agent for Windows
Table 2-8
How to install the Agent for Windows in an Active Directory
Network (continued)
Action
Description
Create a distribution point (share) that
contains the source file of the Agent for
Windows that you want to install.
You must copy the transform that you create,
and the Backup Exec RAWS32 or RAWSX64
directory, to the distribution point.
See the section called “Creating a software
distribution point (share)” on page 79.
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 79.
Creating a transform
To create a transform
1
Do one of the following:
■
From the Backup Exec installation media browser, click Install Products,
and then click Agent for Windows.
■
From a Backup Exec server on which Backup Exec is installed, go to
\Program Files\Veritas\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.
78
Installation
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-9
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
\Program Files\Veritas\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.
79
Installation
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.
80
Installation
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:
\Program Files\Veritas\Backup Exec\Agents
or you can copy the following folders to the same local directory:
2
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
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
81
Installation
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
a 32-bit computer:
\Program Files\Veritas\Backup
Exec\RAWS32
If you installed the Agent for Windows to
a 64-bit computer:
\Program Files\Veritas\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.
82
Installation
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 \Program Files\Veritas\Backup
32-bit computer:
Exec\Agents\RAWS32
To uninstall the Agent for Windows from a \Program Files\Veritas\Backup
64-bit computer:
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 80.
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.
83
Installation
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:
\Program Files\Veritas\Backup Exec\Agents
2
Do one of the following:
To install the Agent for Windows on a
32-bit computer
In the RAWS32 directory, double-click
setupaa.
To install the Agent for Windows on a
64-bit computer
In the RAWSX64 directory, double-click
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
\Program Files\Veritas\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 83.
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.
84
Installation
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
Click Next.
7
On the Destination panel, do the following:
■
Review the disk space requirements for the installation.
■
To change the location where the files are installed, click Change to select
another directory for the installation.
8
Click Next.
9
Review the Backup Exec installation summary, and then click Install.
10 Click Next, and then click Finish to exit the wizard.
See “Running the Remote Administrator” on page 87.
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.
85
Installation
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 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 "Program
Files\Veritas\Backup Exec".
Table 2-10
Switch
/RA:
Command line switches for Remote Administrator silent mode
installation
Additional Switches
Description
Installs Remote
Administrator using
the options that are
specified with the
additional switches.
86
Installation
Installing the Remote Administrator
Table 2-10
Switch
Command line switches for Remote Administrator silent mode
installation (continued)
Additional Switches
Description
/DEST:"drive:\path"
Specifies the local
path where Remote
Administrator will be
installed. Otherwise,
the default path
Program
Files\Veritas\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 90.
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.
87
Installation
Installing the Remote Administrator
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 84.
To run the Remote Administrator
1
Click Start.
2
Point to Programs, and then click Veritas 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.
88
Installation
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.
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.
89
Installation
Installing Backup Exec using the command line (silent mode)
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
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:
90
Installation
Installing Backup Exec using the command line (silent mode)
■
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 90.
Table 2-11
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.
/USER:user
/DOM:dm
/PASS:pw
Required. Specifies an existing user,
domain, and password for the Backup
Exec system service account. Silent
mode installation does not create a user.
Note: When using /PASS:, if a quote
is needed as part of the password,
specify it as \". For example, if the
password is pass"word, type it as
/PASS:pass\"word. If the characters \"
are used as part of the password, you
must precede each character with a \.
For example, if the password is
pass\"word, type it as
/PASS:pass\\\"word.
/DEST:drive:\path
Specifies the local path where Backup
Exec is installed. Otherwise, the default
path Program
Files\Veritas\Backup Exec is
used.
/DOCS:
Installs the online documentation.
91
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
Command line switches for silent mode installation of Backup
Exec (continued)
Switch Additional Switches
/BELANG:language
Description
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.
92
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
Command line switches for silent mode installation of Backup
Exec (continued)
Switch Additional Switches
/SLF:slf file
Description
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 to Veritas over the
web.
/BOOT:
Automatically initiates a restart of the
computer during a silent install or
uninstall.
93
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
Command line switches for silent mode installation of Backup
Exec (continued)
Switch Additional Switches
/TD:NEW, ALL, or NONE
Description
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.
94
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
Command line switches for silent mode installation of Backup
Exec (continued)
Switch Additional Switches
Description
/DBINSTPATH: SQL Express
destination folder
Installs the default instance of SQL
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
Package
Specifies the location of the
language-specific install package for
Microsoft SQL Server 2014 Express with
SP2.
/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.
95
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
Command line switches for silent mode installation of Backup
Exec (continued)
Switch Additional Switches
/ENTSERVER:
Description
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.
■
■
/ADBO:
/CASO:
Installs the Central Admin Server
feature.
/ADBO:
Installs the Advanced Disk-based
Backup feature.
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.
96
Installation
Installing Backup Exec using the command line (silent mode)
Table 2-11
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.
97
Installation
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-12
Installation log colors
This color
Indicates
Black
Normal operations
Orange
Warning messages
Red
Error messages
98
Installation
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.
99
Installation
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 Veritas 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.
100
Installation
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.
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-13
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.
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.
101
Installation
Viewing installed updates
5
6
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.
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 102.
See “Installing updates to the Agent for Windows on remote computers” on page 75.
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.
102
Installation
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 Veritas 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.
To view license information
◆
Click the Backup Exec button, select Installation and Licensing, and then
select License Information.
103
Installation
Backup Exec license contract information
Backup Exec license contract information
After you purchase or import license contracts for Backup Exec, Veritas automatically
updates the Veritas Licensing Portal website 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.
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 104.
Updating expired license contracts
When your license contracts expire, follow these steps to update them.
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
Backup Exec Administration Console.
Use the option Install Features and
Licenses on this Backup Exec Server on
the Installation and Licensing menu, which
is accessed from the Backup Exec button.
104
Installation
About upgrading to Backup Exec
Table 2-15
How to update expired license contracts (continued)
Step
Additional information
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 104.
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:
3
■
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.
Click Close.
About upgrading to Backup Exec
In order to upgrade from Backup Exec 15 or later to the latest version, you must
provide a valid subscription license at the time of the upgrade. However, existing
licenses cannot be used to perform an upgrade to the current version, even with a
current maintenance agreement. If you have a current perpetual license, you will
need to purchase a new subscription license in order to upgrade to the current
version. If you have an existing maintenance agreement, you will be able to upgrade
to the next release of Backup Exec when it becomes available. You do not need
to uninstall the previous version of Backup Exec before upgrading; the current
version is installed over the previous version. Separate installations of different
versions of Backup Exec cannot exist on the same computer.
105
Installation
About upgrading to Backup Exec
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 Veritas has made end-of-life decisions.
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 108.
Backup Exec provides backward compatibility as follows:
■
Backup Exec can communicate with Backup Exec 16 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:
■
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.
106
Installation
About upgrading to Backup Exec
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 SP2 setup file for that language from the Microsoft website.
See “Installing Backup Exec by using the Installation Wizard” on page 51.
Upgrade checklist for Backup Exec
Before you upgrade from a previous version of Backup Exec to the current version,
do the following:
■
Ensure that your backups are up to date. Veritas recommends 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 Veritas 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 48.
■
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 315.
■
About upgrading from previous versions of Backup Exec
See “About upgrading to Backup Exec” on page 105.
107
Installation
Post-installation tasks
■
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.
Veritas recommends that you review the Migration Report thoroughly to determine
how your existing jobs have changed and how you may need to adjust your jobs
manually. The Migration Report is available for viewing from the Backup Exec
Administration Console or the Home tab at any time after the migration completes.
The Migration Report is stored in the following path:
\Program Files\Veritas\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
Administration Console
Click the Backup Exec button, select
Installation and Licensing, and then
select Migration Report.
To view the Migration Report from the
Home tab
On the Home tab, in the Installation and
Upgrades group, click Migration Report.
See “Configuring the Home tab” on page 118.
Post-installation tasks
For best results, do the following after installing Backup Exec:
108
Installation
Uninstalling Backup Exec
■
Create disk storage so that Backup Exec can automatically manage the lifecycle
of your backup data.
See “Configuring disk storage” on page 297.
■
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 396.
■
Understand the default media set for tape media and its four-week overwrite
protection period.
See “Default media sets” on page 382.
■
Understand Data Lifecycle Management.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 315.
■
Learn about creating new media sets with different retention periods.
See “Creating media sets for tapes” on page 390.
■
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 631.
■
Configure a secure connection to the Backup Exec Database
See “Configuring encryption for the connection to the Backup Exec Database”
on page 583.
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 Veritas Backup Exec™, and then click Uninstall.
109
Installation
Uninstalling Backup Exec using the command line
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 110.
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 90.
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.
110
Installation
Uninstalling Backup Exec features from the local Backup Exec server
Note: Veritas license files remain on the server after features are uninstalled. Do
not delete the Veritas license files while Backup Exec is installed. Deleting the
Veritas 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.
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 109.
111
Chapter
3
Getting Started
This chapter includes the following topics:
■
About the Backup Exec Administration Console
■
Displaying the version information for Backup Exec
■
How to sort, filter, and copy information on the Backup Exec Administration
Console
■
Customizing views on the Backup Exec Administration Console
■
Configuring the Home tab
■
Configuring the Veritas 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
About the Backup Exec Administration Console
Backup Exec Administration Console
Figure 3-1
Tabs
Backup Exec button
Groups
Columns
Selection pane
Details pane
Status bar
The administration console screen includes the following components:
Table 3-1
Administration console components
Item
Description
Backup Exec
button
The Backup Exec button displays on the upper left side of the
administration console. To display the options in the Backup Exec
button, click the Backup Exec button, select the menu name, and then
select an option. You can launch Backup Exec operations by clicking
options from a menu.
113
Getting Started
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
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.
114
Getting Started
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.
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.
115
Getting Started
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
the list of servers
On the Backup and Restore tab, in the
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
sort order for the columns
Click Sort, choose the options as
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.
116
Getting Started
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
and Restore tab
On the Backup and Restore tab, in the
Views group, click Sort and Filter.
To edit a configuration from the Storage
tab
On the Storage tab, in the Views group,
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.
117
Getting Started
Configuring the Home tab
Table 3-2
Views on the Backup Exec Administration Console
View
Description
Standard
Displays the information in a view that
provides descriptive text.
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, or the Storage tab, in
the Views group, click Standard, Compact, Tree, or List.
Note: The Tree and List view is disabled for the list of servers on the Backup and
Restore tab.
Configuring the Home tab
You can configure the Home tab by selecting the items that you want to display.
You can drag and drop items to move them to another location on the Home tab
or you can maximize a single item. The Home tab items contain Backup Exec data
and links to features that you use frequently.
To configure the Home tab
1
On the Home tab, in the Layout group, click the layout for the items that you
want to display.
2
In the System Health and Support groups, select the check box for the items
that you want to display.
3
Drag the items to a column and position in which you want them to display to
further customize the Home tab.
You can configure the Layout, and hide or display items in the System Health and
the Support groups.
118
Getting Started
Configuring the Home tab
Restoring the Home tab's default layout
You can quickly restore the Home tab to its default configuration at any time.
To restore the Home tab's default configuration
◆
On the Home tab, in the Layout group, click Reset Home Tab.
Layout group
You can select one of the following layout configurations to display the items on
the Home tab.
Table 3-3
Home Tab Layout items
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.
119
Getting Started
Configuring the 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
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 753.
120
Getting Started
Configuring the Home tab
Table 3-4
System Health group items (continued)
Item
Description
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 580.
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.
Support group
The items in the Support group provide technical support, documentation, licensing
contracts, and the Veritas RSS Reader resources. You can select the following
items to display on the Backup Exec Home tab.
121
Getting Started
Configuring the 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:
Documentation
Licensing Information
Veritas RSS Reader
■
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
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)
Provides the following licensing options to
help you manage license contracts and
licenses:
■
View license information
■
View license contract information
Lets you view and add Backup Exec and
Veritas RSS feeds.
122
Getting Started
Configuring the Veritas RSS Reader
Table 3-5
Support group items (continued)
Item
Description
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 108.
See “Viewing the Installation Summary
Report” on page 99.
Configuring the Veritas RSS Reader
You can customize the Veritas RSS Reader and select the default Backup Exec
feeds that display in the reader. You can add additional Veritas and Backup Exec
RSS feeds or remove RSS feeds.
The Veritas 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 Veritas 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 Veritas RSS Reader
1
On the Home tab, in the Support group, select the Veritas RSS Reader check
box.
2
In the Veritas 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 Veritas 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.
123
Getting Started
Creating a disaster preparation plan (DPP)
To customize the Veritas RSS feeds to the Veritas RSS Reader
1
On the Home tab, in the Support group, select the Veritas RSS Reader check
box.
2
In the Veritas RSS Reader, click the pencil icon to add an RSS feed.
3
Enter any of the following:
4
URL
Indicates the location of the RSS feed that
you want to add to the Veritas RSS
Reader.
Name
Indicates the name of the RSS feed that
you want to display in the Veritas RSS
Reader.
Click here to see more Veritas RSS
feeds
Shows a list of Veritas RSS feeds that you
can add to the Veritas RSS Reader.
Click OK.
To remove an RSS feed from the Veritas RSS Reader
1
On the tab, in the Support group, select the Veritas RSS Reader check box.
2
Do one of the following:
To remove a default Backup Exec RSS
feed
Clear the check box of the Backup Exec
RSS feed.
To remove an RSS feed that you added to Click the red X next to the name of the
the Veritas 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
124
Getting Started
Creating a disaster preparation plan (DPP)
DPP you put in place with your Backup Exec system should be customized to your
network environment.
For more information about how to perform a manual disaster recovery, click the
following URL:
https://www.veritas.com/support/en_US/article.000020082
While environments vary in different organizations, consider the following elements
when creating a comprehensive 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
backups.
It is imperative that you regularly move the backed-up data
to an off-site storage facility. If you use disk as your storage
medium, consider adding a stage to duplicate backups to
other storage This ensures that if something happens to your
facility, all of your backups are not destroyed. Depending on
the importance of your data, you may choose to use several
off-site storage facilities.
125
Getting Started
Getting started with backups
Table 3-6
Key elements of a DPP (continued)
Element
Description
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 126.
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
Step
Getting started with backups
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 428.
126
Getting Started
Getting started with backups
Table 3-7
Step
Getting started with backups (continued)
Description
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 631.
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 139.
127
Getting Started
Getting started with backups
Table 3-7
Getting started with backups (continued)
Step
Description
4. Create the
Simplified Disaster
Recovery disk
image
By default, Backup Exec selects all the data on a computer for backup,
including the critical system components that you need to perform a
full system restore by using SDR. SDR-enabled backups are those
backups for which all of the critical system components are selected
for backup. You must have SDR-enabled backups to use Backup Exec
to rebuild a computer and restore it to a functional state.
See “How to ensure that backups are enabled for Simplified Disaster
Recovery” on page 761.
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 768.
128
Chapter
4
Backups
This chapter includes the following topics:
■
How to prepare for your first backup with Backup Exec
■
Required user rights for backup jobs
■
About the list of servers on the Backup and Restore tab
■
Adding servers that you want to back up to the list of servers on the Backup and
Restore tab
■
Removing servers from the list of servers on the Backup and Restore tab
■
Creating a server group
■
Hiding or viewing server groups on the Backup and Restore tab
■
Adding servers to a server group
■
Removing servers from a server group
■
Editing a server group
■
Moving servers to the Retired Servers server group
■
Moving retired servers back to the All Servers server group
■
Removing server groups from Backup Exec
■
Backing up data
■
About selecting data to back up
■
Changing the order in which backup sources are backed up
■
Excluding files from backups
■
Including specific files with a backup job's backup selections
Backups
■
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
130
Backups
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?
For more information, go to the following URL:
https://www.veritas.com/support/en_US/article.000032324
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 131.
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 297.
■
Set up storage device pools to load-balance jobs.
See “Creating storage device pools” on page 418.
■
Create media sets to manage data retention for tape cartridge media.
See “Default media sets” on page 382.
■
Configure deduplication disk storage to optimize storage and network bandwidth.
See “About the Deduplication feature” on page 828.
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:
131
Backups
About the list of servers on the Backup and Restore tab
■
Act as part of the operating system.
■
Back up files and directories.
■
Restore files and directories.
■
Manage auditing and security log.
■
Logon as a batch job (only for Windows Vista and later).
For more information about user rights in Windows operating systems, see your
Microsoft documentation.
See “Changing the credentials for a service account” on page 642.
See “Backup Exec logon accounts” on page 631.
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
132
Backups
Adding servers that you want to back up to the list of servers on the Backup and Restore tab
■
Last backup
■
Next backup
■
Percent complete
■
Elapsed time
■
Byte count
■
Average job rate
■
Description
Windows servers must have the Agent for Windows installed on them before you
can add them to the list of servers. When you add Windows servers to Backup
Exec, you have the option to install the Agent for Windows to them remotely.
If you no longer want to monitor or back up a server with Backup Exec, you can
remove it from the list of servers.
See “Adding servers that you want to back up to the list of servers on the Backup
and Restore tab” on page 133.
See “Removing servers from the list of servers on the Backup and Restore tab”
on page 134.
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 590.
133
Backups
Removing servers from the list of servers on the Backup and Restore tab
See “About the list of servers on the Backup and Restore tab” on page 132.
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 1207.
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 132.
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 139.
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
134
Backups
Hiding or viewing server groups on the Backup and Restore tab
group is intended for any servers that you no longer actively monitor with Backup
Exec. Servers no longer appear in the All Servers server group after you move
them to the Retired Servers server group.
To create a server group
1
On the Backup and Restore tab, in the Views group, click Groups.
2
Click Add.
3
In the Group name field, type a name for the server group that you want to
create. You may want to name the server group to indicate the type of servers
in the group or the location at which the servers reside, for example.
4
In the Description field, type a description for the server group.
5
(Optional) Do any of the following to filter the servers in your environment so
that you can find the servers that you want to add to the server group:
6
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.
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 135.
See “Adding servers to a server group” on page 136.
See “Removing servers from a server group” on page 136.
See “Editing a server group” on page 137.
See “Moving servers to the Retired Servers server group” on page 137.
See “Removing server groups from Backup Exec” on page 139.
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
135
Backups
Adding servers to a server group
more detailed information about the server group's jobs, job history, and any active
alerts.
To hide or view server groups on the Backup and Restore tab
1
On the Backup and Restore tab, in the Views group, click Groups.
2
Select Show Server Groups.
The Show Server Groups option lets you hide or show the Groups pane to
the left of the list of servers.
See “Creating a server group” on page 134.
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:
4
■
Server type
■
Data type
■
Name contains
Click OK.
See “Creating a server group” on page 134.
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.
136
Backups
Editing a server group
3
In the Servers group box, deselect the servers that you want to remove from
the server group.
You can use the following fields to filter the list of servers so that you can find
the server that you want to remove:
4
■
Server type
■
Data type
■
Name contains
Click OK.
See “Creating a server group” on page 134.
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 134.
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
137
Backups
Moving retired servers back to the All Servers server group
may be useful to retire servers if you use Backup Exec to monitor a large number
of servers.
You cannot create new backup jobs for any servers that are in the Retired Servers
server group. However, any scheduled backup jobs still run on retired servers. You
can restore data from retired servers.
If you retire a server and then you decide that you want to move it back to the All
Servers server group, you can click on it and drag it from the Retired Servers server
group to the All Servers server group.
To retire servers from server groups
1
On the Backup and Restore tab, in the Groups pane, right-click Retired
Servers.
2
Click Edit.
3
(Optional) Do any of the following to filter the servers in your environment so
that you can find the servers that you want to retire:
4
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.
In the Servers group box, select the servers that you want to retire and then
click OK.
See “Creating a server group” on page 134.
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 137.
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.
138
Backups
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 134.
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 134.
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.
139
Backups
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 167.
Stages
Figure 4-1
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.
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:
140
Backups
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 575.
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 315.
■
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.
141
Backups
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.
See “Methods for installing the Agent for Windows” on page 69.
To back up data
1
Select one of the following methods to back up data:
To create recurring backup
jobs
Complete the following steps:
■
■
■
To create one-time backups
On the Backup menu, select the backup option that
you want to use.
Complete the following steps:
■
On the Backup and Restore tab, select the server,
servers, or server group that you want to back up.
In the Backups group, click One-Time Backup.
■
Select the backup option that you want to use.
■
To create a new backup
definition using the settings
from an existing backup
definition
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.
Complete the following steps:
■
■
■
■
On the Backup and Restore tab, right-click the
server or servers that you want to back up.
You cannot reuse a backup definition's settings to
create a backup job for a server group.
On the Backup menu, select Create a New Backup
Using the Settings from an Existing Backup.
On the Backup Job Selection dialog box, select
the backup definition that contains the settings that
you want to copy.
Click OK.
142
Backups
Backing up data
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.
4
In the Selections box, click Edit.
5
To add additional servers to the backup definition:
■
Click Add.
143
Backups
Backing up data
6
■
Select the server or servers that you want to add to the backup definition.
■
Click OK.
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 163.
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 150.
8
Click OK.
144
Backups
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.
145
Backups
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 182.
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 285.
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 541.
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 542.
146
Backups
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 544.
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 551.
See “Configuring checkpoint restart” on page 553.
Advanced Disk-based
Backup
Select this option to configure off-host backup
processing for the backup job.
See “Configuring off-host backup options for a backup
job” on page 1232.
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 556.
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 560.
Enterprise Vault
Select this option to configure Enterprise Vault options.
See “Enterprise Vault backup options” on page 1116.
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 1274.
147
Backups
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 1158.
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 1025.
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 927.
See “Backing up VMware virtual machines” on page 875.
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 1050.
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 973.
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 1243.
Oracle
Select this option to configure options for any Oracle
data that is included in the backup job.
See “Oracle backup options” on page 1090.
Exclusions
Select this option to exclude specific files or specific
types of files from backups.
See “Excluding files from backups” on page 158.
13 When you are finished selecting all applicable options for the backup definition,
click OK.
148
Backups
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 198.
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 134.
See “Editing backup definitions” on page 184.
See “About selecting data to back up ” on page 150.
See “Changing the order in which backup sources are backed up” on page 156.
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.
149
Backups
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 139.
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 921.
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.
150
Backups
About selecting data to back up
Figure 4-2
Selections box on the Backup Definition Properties dialog box
See “Backing up data” on page 139.
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.
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
151
Backups
About selecting data to back up
logon account. You can also create a new logon account that can access the
selection.
See “Testing credentials for backup sources” on page 190.
See “Replacing the credentials for a backup source” on page 191.
See “Creating new credentials for a backup source” on page 192.
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
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.
152
Backups
About selecting data to back up
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 156.
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.
■
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
153
Backups
About selecting data to back up
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 158.
See “Including specific files with a backup job's backup selections” on page 161.
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 575.
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.
154
Backups
About selecting data to back up
Figure 4-3
Simplified Disaster Recovery indicator is ON in the Backup
Definition Properties dialog box
Simplified Disaster Recovery
indicator
See “About backing up critical system components” on page 163.
If you deselect any critical system components, it can disqualify your backup data
from being used in certain types of restore scenarios.
You must include all critical system components in your backup selections if you
intend to use any of the following restore scenarios:
■
Simplified Disaster Recovery
■
Conversion to virtual machines
■
Complete online restore of a Microsoft Windows computer
Using fully qualified domain names in backup selections
You can enter fully qualified domain names in Backup Exec anywhere that you can
enter a computer name. In addition, Backup Exec can show fully qualified domain
names where computer names are listed.
For fully qualified domain names, the following rules apply:
■
The maximum number of characters for each label (the text between the dots)
is 63
■
The maximum total number of characters in the fully qualified name is 254,
including the dots, but excluding the \\
■
The name cannot include the following characters: * | < > ?
Veritas does not recommend using both fully qualified domain names and
non-qualified domain names. Veritas recommends using fully qualified domain
names.
155
Backups
Changing the order in which backup sources are backed up
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 156.
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
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
156
Backups
Changing the order in which backup sources are backed up
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.
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:
157
Backups
Excluding files from backups
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.
To reorder the backup
sources within a server
Do the following:
■
■
■
In the left pane of the Backup Selections dialog
box, select the server that contains the resources
that you want to reorder.
In the right pane of the Backup Selections dialog
box, select the Selection Details tab.
To reorder the backup sources when a server is
selected in its entirety, you must insert the individual
selections that you want to reorder:
■ Click Insert, and then select Insert Selection.
■
■
■
4
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.
Click OK.
See “Backing up data” on page 139.
See “About selecting data to back up ” on page 150.
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
158
Backups
Excluding files from backups
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
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
backup job
To exclude files from a
backup definition
Complete the following steps:
■
Create or edit a backup definition.
■
In the Backup box, click Edit.
■
In the left pane, select Exclusions.
■
Click Insert.
Complete the following steps:
■
Create or edit a backup definition.
■
In the Selections box, click Edit.
■
On the Selection Details tab, click Insert and then
select Add Backup-Level Exclusion.
159
Backups
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".
160
Backups
Including specific files with a backup job's backup selections
3
4
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
days
Select this option to exclude any files that have not been
accessed in a specific number of days. You must enter
the number of days.
Click OK.
See “About selecting data to back up ” on page 150.
See “Including specific files with a backup job's backup selections” on page 161.
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.
161
Backups
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
6
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
days
Select this option to include any files that have not been
accessed in a specific number of days. You must enter
the number of days.
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.
Click OK.
See “About selecting data to back up ” on page 150.
162
Backups
About backing up critical system components
See “Excluding files from backups” on page 158.
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 753.
■
Conversion to virtual machines
See “How conversion of physical computers to virtual machines works in Backup
Exec” on page 478.
■
Complete online restore of a Microsoft Windows computer
See “Performing a complete online restore of a Microsoft Windows computer”
on page 218.
163
Backups
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.
Restore scenarios by data type
Table 4-2
File System Operating
or Agent
System
Name
and
Applications
Are
Installed
and
Functional
Complete
Online
Restore
Can Be
Performed
Physicalto-Virtual
Conversion
Can Be
Performed
Backupto-Virtual
Conversion
Can Be
Performed
Simplified
Disaster
Recovery
Can Be
Performed
Active
Directory
Yes
Yes
Yes
Yes
Yes
Active
Directory
Lightweight
Yes
No
No
No
No
CSV
Yes
Yes
No
No
Yes
EFI
Yes
Yes
No
No
Yes
Enterprise
Vault
Yes
No
No
No
No
Exchange
Agent
Yes
No
Yes, any
incremental
or differential
backups must
use the
block-level
backup
method
Yes, any
No
incremental
or differential
backups must
use the
block-level
backup
method
FAT
Yes
Yes
Yes
Yes
Yes
Hyper-V
Agent
Yes
No
No
No
No
NTFS
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Oracle RMAN Yes
Windows
Agent
164
Backups
About backing up critical system components
Restore scenarios by data type (continued)
Table 4-2
File System Operating
or Agent
System
Name
and
Applications
Are
Installed
and
Functional
Complete
Online
Restore
Can Be
Performed
Physicalto-Virtual
Conversion
Can Be
Performed
Backupto-Virtual
Conversion
Can Be
Performed
Simplified
Disaster
Recovery
Can Be
Performed
ReFS
Yes
Yes
No
No
Yes
Shadow Copy Yes
Components
Yes
Yes
Yes
Yes
SharePoint
Agent
Yes
No
No
No
No
SQL Agent
Yes
No
Yes, any
incremental
or differential
backups must
use the
block-level
backup
method
Yes, any
No
incremental
or differential
backups must
use the
block-level
backup
method
System State Yes
Yes
Yes
Yes
Yes
Utility
Partition
Yes
Yes
No
No
Yes
VMware
Agent
Yes
No
No
No
No
Yes
No
No
Yes
Windows
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
165
Backups
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
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
during a snapshot backup, the files would be backed up in a possible inconsistent
state, which could create restore issues.
166
Backups
Backup methods in Backup Exec
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.
Note: You should perform a full backup of your server to establish a baseline for
disaster recovery.
167
Backups
Backup methods in Backup Exec
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.
Veritas recommends that you always run full backups before and after you upgrade,
update, or modify any backup sources. This recommendation applies to any
significant operating system and application configuration or modifications.
Table 4-3
Backup sources and scenarios for which a full backup is
recommended
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.
■
Applications
Backup Exec
Add, modify, or remove any server roles or features.
You should run a full backup when you:
■
Install new applications.
■
Upgrade applications to new versions.
■
Update the existing version of applications.
You should run a full backup when you:
■
Upgrade to a new version of Backup Exec.
Note: Any recurring jobs that are migrated to a new
version of Backup Exec retain their existing schedules.
You should manually run a full backup for any existing
jobs before any incremental backups or differential
backups run.
■
■
Update the existing version of Backup Exec using 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.
168
Backups
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 560.
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 560.
169
Backups
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
Full
■
■
Disadvantages
Files are easy to find
■
Full backups include all the
data that you selected to back
up. Therefore, you don’t have
to search through several
backup sets to find a file that
you need to restore.
A current backup of your entire ■
system is available on one
backup set
If you run a full backup of your
entire system and then need
to restore it, all of the most
current information is located
in one place.
Redundant backups
Most of the files on your file
server do not change. Each full
backup that follows the first is
merely a copy of what has
already been backed up. Full
backups require more storage.
Full backups take longer to
perform
Full backups can be time
consuming, especially when
you have other servers on the
network that need to be backed
up (for example, agent
workstations, remote servers).
170
Backups
Backup methods in Backup Exec
Table 4-4
Backup method Advantages and Disadvantages (continued)
Method
Advantages
Differential
■
■
Incremental
■
■
Files are easy to find
Disadvantages
■
Redundant backups
Restoring a system that is
backed up with a differential
method requires fewer
backups. Differentials require
the latest full backup, any
subsequent incremental
backups, and the latest
differential backup. Restoring
differentials is less time
consuming than restoring
incrementals. Restoring
incrementals requires the
latest full backup and all
incremental backups that were
created since the full backup.
Less time is required for
backup and restore
Differential backups take less
time to restore than full
backups. Faster recovery is
possible in disaster situations
because you only need backup
sets from the latest full backup,
any subsequent incremental
backups, and the latest
differential backup to fully
restore a server.
All of the files that were created
or modified since the last full
backup are included; thus
creating redundant backups.
Better use of storage
■
Only the files that have
changed since the last backup
are included, so much less
data storage space is required.
Less time is required for
backup
Incremental backups take
much less time than full and
differential backups to
complete.
Backups are spread across
multiple backup sets
Since multiple backup sets are
required in a disaster situation,
recovering a server can take
longer. In addition, the backup
sets must be restored in the
correct order to effectively
bring the system up to date.
Consider the following backup strategy scenario:
171
Backups
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 175.
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.
172
Backups
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:
Enterprise Vault
■
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
Initial full:
■
Full - Back up components
Additional backup methods for Enterprise Vault:
Microsoft
Exchange
■
Full- Back up components
■
Differential - Back up component changes since the last full
■
Incremental - Back up component changes since the last full or
incremental
Initial full:
■
Full - Back up databases and logs (truncate logs)
■
Full Copy - Back up databases and logs
Additional backup methods for Microsoft Exchange:
Virtual Machines
■
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)
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
173
Backups
Backup methods in Backup Exec
Table 4-5
Available Backup Methods By Data Type (continued)
Data type
Job type and backup method
Microsoft
SharePoint
Initial full:
■
Full - Back up databases
■
Full Copy - Back up databases (copy)
Additional backup methods for Microsoft SharePoint:
■
Full - Back up databases
■
Full Copy - Back up databases (copy)
■
Differential - Back up database changes since the last full
■
Differential (block-level) - Back up database changes since the last
full - use with convert to virtual machine job
Incremental (block-level) - Back up database changes since the last
full or incremental - use with convert to virtual machine job
Log - Back up and truncate transaction log
■
■
Microsoft 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
■
■
174
Backups
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:
Oracle
■
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)
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 167.
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.
175
Backups
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:
176
Backups
How Backup Exec determines if a file has been backed up
7
■
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.
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.
177
Backups
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
178
Backups
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 560.
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
179
Backups
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
GB
■
Change Journal Max Size: 16 MB
■
Allocation Delta: 2 MB
Over 4 GB - 63 GB ■
4 GB or less
Change Journal Max Size: 8 MB
■
Allocation Delta: 1 MB
■
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.
180
Backups
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 560.
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.
181
Backups
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 593.
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:
Subnet
■
Use any available protocol
■
IPv4
■
IPv6
Select the 32-bit number that determines the subnet to
which the network interface card belongs.
182
Backups
Running the next scheduled backup job before its scheduled time
Allow use of any available
network interface, subnet,
or protocol for Backup Exec
agents not bound to the
above network interface,
subnet, or protocol
Select this option to let Backup Exec use any available
network if the remote system that you selected for
backup or restore is not part of the specified backup
network.
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
Exec server to use any
network interface to access
Backup Exec agents
Select this option to let a job use any network interface
to access Backup Exec agents if the selected network
interface is unavailable. Enabling this option lets the
managed Backup Exec server use an alternate network
interface to run any important backup jobs that would
otherwise fail.
If you do not select this option and the remote system
is not part of the specified backup network, the job fails.
Backup Exec cannot access the data from the remote
system.
This option is available only if the Central Admin Server
feature (CAS) is installed.
See “About the Central Admin Server feature”
on page 1163.
5
Click OK.
See “Backup networks” on page 591.
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.
183
Backups
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 139.
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 198.
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:
184
Backups
Editing backup definitions
To edit backups from the
Backup and Restore tab
Complete the following steps:
■
■
On the Backup and Restore tab, do one of the
following:
■ To edit backups for a single server, right-click
the server name.
■ To edit backups for multiple servers, Shift + click
or Ctrl + click the server names, and then
right-click one of the selected servers.
Click Edit Backups.
Note: If the server or servers that you selected have
multiple backup definitions, select the definitions that
you want to edit on the Backup Job Selection
dialog box and then click OK.
To edit backups from the 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.
■
■
185
Backups
Editing backup definitions
To edit backups from the
Storage tab
Complete the following steps:
■
■
On the Storage tab, double-click the storage device
or storage pool for the backup that you want to edit.
On the Job History pane, do one of the following:
■ To edit a single backup, right-click the backup.
■
To edit multiple backups, Shift + click or Ctrl +
click the backups and then right-click one of the
selected backups.
Note: You can only edit any backup jobs that have
previously run from the Storage tab.
■
2
Click Edit Backup.
In the Selections box, click Edit.
186
Backups
Editing backup definitions
3
4
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.
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 163.
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
Backup and Restore tab
Complete the following steps:
■
■
On the Backup and Restore tab, do one of the
following:
■ To edit backups for a single server, right-click
the server name.
■ To edit backups for multiple servers, Shift + click
or Ctrl + click the server names, and then
right-click one of the selected servers.
Click Edit Backups.
Note: If the server or servers that you selected have
multiple backup definitions, select the definitions that
you want to edit on the Backup Job Selection
dialog box and then click OK.
187
Backups
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.
■
■
188
Backups
Editing backup definitions
To edit backups from the
Storage tab
Complete the following steps:
■
■
On the Storage tab, double-click the storage device
or storage pool for the backup that you want to edit.
On the Job History pane, do one of the following:
■ To edit a single backup, right-click the backup.
■
To edit multiple backups, Shift + click or Ctrl +
click the backups and then right-click one of the
selected backups.
Note: You can only edit any backup jobs that have
previously run from the Storage tab.
■
2
In the Backup box, click Edit.
Click Edit Backup.
189
Backups
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 139.
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.
Veritas recommends that you test to make sure that you have the appropriate
credentials to access the content that you want to back up. If a credentials test fails,
you can enter new credentials for the content so that Backup Exec can access it.
You can test the credentials that are associated with a backup source at any time
from the Credentials pane. You can also test the credentials when you create a
backup definition.
Note: You cannot test credentials for virtual machines, but the job runs if you provide
the correct credentials. If the job fails, you may need to retry the job with different
credentials.
Complete any of the following procedures to test credentials for backup sources:
To test the credentials that are associated with a backup source
To test the credentials for all of the backup sources in a specific backup definition
To test the credentials for a specific backup source in a specific backup definition
To test the credentials that are associated with a backup source
1
On the Backup and Restore tab, double-click the server whose credentials
you want to test.
2
In the left pane, click Credentials.
190
Backups
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 191.
See “Creating new credentials for a backup source” on page 192.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 194.
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.
Veritas recommends that you test to make sure that you have the appropriate
credentials to access the content that you want to back up. If a credentials test fails,
you can enter new credentials for the content so that Backup Exec can access it.
If you need to change the credentials that are associated with a backup source,
you can do so at any time on the Backup and Restore tab from the Credentials
pane. You can also change a backup source's credentials when you create or edit
backups.
191
Backups
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 190.
See “Creating new credentials for a backup source” on page 192.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 194.
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:
192
Backups
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 190.
See “Replacing the credentials for a backup source” on page 191.
See “Deleting retired or unused backup sources from the Credentials pane”
on page 194.
193
Backups
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 190.
See “Replacing the credentials for a backup source” on page 191.
See “Creating new credentials for a backup source” on page 192.
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.
194
Backups
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 528.
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 197.
See “Including a specific date in the schedule for a backup job” on page 196.
195
Backups
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 197.
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.
196
Backups
Preventing backup jobs from running on a specific date
To select the date from the
calendar
Click the date that you want to include with the backup
schedule.
The calendar displays 3 months at a time. You can
navigate forward and backward to view additional
months by clicking the arrows.
Note: You can select only one date at a time.
7
Click OK.
See “How job scheduling works in Backup Exec” on page 194.
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 196.
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:
197
Backups
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
calendar
Click the date that you want to exclude.
The calendar displays 3 months at a time. You can
navigate forward and backward to view additional
months by clicking the arrows.
Note: You can select only one date at a time.
7
Click OK.
See “How job scheduling works in Backup Exec” on page 194.
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 194.
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
198
Backups
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
After Backup
Creates a virtual machine from your backup sets after the
backup job is complete.
See “How conversion of physical computers to virtual
machines works in Backup Exec” on page 478.
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 478.
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.
199
Backups
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 139.
See “Editing a stage” on page 200.
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
Backup and Restore tab
Complete the following steps:
■
■
■
To edit a stage from the Job
Monitor 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.
Complete the following steps:
■
■
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 198.
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.
200
Backups
Duplicating backup sets or a job history manually
See “Adding a stage to a backup definition” on page 198.
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 208.
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.
201
Backups
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
immediately
Select Run now.
To schedule the job for a later Select Run on, and then enter the date and time.
time
To schedule the job to run
later using an external
scheduling tool
Select Create without a schedule.
To submit the job on hold
Click Submit job on hold.
You can schedule the job to run later using an external
scheduling tool.
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
the duplicate backup sets
In the Compression field, select the type of
compression.
202
Backups
Duplicating backup sets or a job history manually
To enable encryption for the
duplicate backup sets
Complete the following steps:
■
■
To run a verify operation on
the duplicate backup sets
9
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.
Select Verify at the end of the job.
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.
■
To duplicate job history from
the Job Monitor tab
2
Click Duplicate.
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.
Complete the following steps:
■
On the Job Monitor tab, do one of the following:
■ To duplicate a single job history, right-click the
job history.
■ To duplicate multiple job histories, Shift + click
or Ctrl + click the job histories, and then right-click
one of the selected job histories.
203
Backups
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
immediately
Select Run now.
To schedule the job for a later Select Run on, and then enter the date and time.
time
To schedule the job to run
later using an external
scheduling tool
Select Create without a schedule.
To submit the job on hold
Click Submit job on hold.
You can schedule the job to run later using an external
scheduling tool.
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
the duplicate job history
In the Compression field, select the type of
compression.
To enable encryption for the
duplicate job history
Complete the following steps:
■
■
To run a verify operation on
the duplicate job history
7
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.
Select Verify at the end of the job.
On the Duplicate Job dialog box, click OK for each duplicate job that you
create.
204
Backups
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 706.
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, Veritas recommends that you run backup jobs to your
storage devices first. Backup Exec does not recognize the capacity of a storage
device until an actual backup job sends data to the device. If you create a test run
job before any other jobs, Backup Exec cannot check that the device has sufficient
capacity to perform the backup job. After at least one backup job has sent data to
a device, Backup Exec can determine the capacity.
To run a test job manually
1
Do one of the following:
To run a test job from the
Backup and Restore tab
Complete the following steps:
■
■
On the Backup and Restore tab, double-click the
server that contains the job you want to test.
In the left pane, click Jobs.
205
Backups
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 541.
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. Veritas recommends that you verify
all backed up data to ensure the integrity of the collection of data and the media on
which it resides. By default, Backup Exec automatically verifies backed up data at
the end of a backup job. However, you can also schedule the verify operation to
take place at a later time or disable the verify operation altogether. You can change
Backup Exec's verify options as part of the default backup settings or for individual
backup jobs.
See “Configuring automatic verify operations for backup jobs” on page 542.
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.
206
Backups
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
immediately
Select Run now.
To schedule the operation for Select Run on, and then enter the date and time.
a later time
To schedule the job to run
later using an external
scheduling tool
6
Select Create without a schedule.
You can schedule the verify operation to run later using
an external scheduling tool.
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.
■
To verify a job history from
the Job Monitor tab
On the Job Monitor tab, do one of the following:
■
■
2
Click Verify.
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 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.
207
Backups
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
immediately
Select Run now.
To schedule the operation for Select Run on, and then enter the date and time.
a later time
To schedule the job to run
later using an external
scheduling tool
4
Select Create without a schedule.
You can schedule the verify operation to run later using
an external scheduling tool.
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.
208
Backups
Copying data from a virtual tape library to a physical tape device using DirectCopy to tape
Table 4-8
Step
How to use DirectCopy to tape to copy data from a virtual tape
library to a physical device
Notes
Create a regular backup Select a virtual tape library as
job.
the storage destination.
For more information
See “Backing up data”
on page 139.
See “Configuring storage
options for backup jobs”
on page 535.
Create a duplicate
backup job.
In the DBA-initiated job settings: See “DBA-initiated job
templates” on page 616.
■ Select a physical tape
device as the destination.
See “Storage options for
■ Select Enable DirectCopy DBA-initiated jobs” on page 619.
to tape.
See “Duplicate job settings for
DBA-initiated jobs” on page 624.
209
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
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 213.
211
Restores
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 213.
See “Performing a complete online restore of a Microsoft
Windows computer” on page 218.
Simplified Disaster
Recovery
Lets you recover Windows computers after a hard drive
failure. The Simplified Disaster Recovery wizards guide you
in preparing for disaster recovery, and in recovering a local
computer or a remote computer to its pre-disaster state.
See “About Simplified Disaster Recovery” on page 753.
See “Restoring file system data” on page 217.
See “Restoring System State ” on page 219.
See “Restoring Backup Exec Shadow Copy Components” on page 224.
See “Restoring utility partitions or Unified Extensible Firmware Interface system
partitions” on page 224.
See “Restoring Exchange data” on page 1039.
See “Restoring SQL databases and transaction logs” on page 995.
See “About restoring Oracle resources” on page 1091.
See “Restoring VMware virtual machines and vmdk files” on page 890.
See “Restoring a deduplication disk storage device or deduplicated data”
on page 863.
See “Restoring Microsoft SharePoint data” on page 1057.
See “Restoring Enterprise Vault” on page 1120.
212
Restores
Searching for data to restore
See “About restoring data to Linux computers” on page 1276.
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.
To search for data to restore
1
On the Backup and Restore tab, right-click the server or servers on which
you want to search for data, and then click Search.
2
Follow the Search Wizard prompts to search for and restore data.
Restoring data from a server, a backup set, a
backup job, or a storage device
You can restore data by launching the Restore Wizard directly from a server, from
backup sets, from completed backup jobs, and from storage device media.
You can also perform a complete online restore of a Windows computer if the
computer was fully selected for a backup. By default, backup jobs include all
necessary components that are required for a complete restore.
213
Restores
Restoring data from a server, a backup set, a backup job, or a storage device
See “Performing a complete online restore of a Microsoft Windows computer”
on page 218.
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.
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:
214
Restores
Restoring data from a server, a backup set, a backup job, or a storage device
To restore data from the
Backup and Restore tab
■
■
■
■
To restore data from the Job ■
Monitor tab
■
2
On the Backup and Restore tab, in the list of
servers, double-click a server that has been backed
up.
In the Jobs view, expand a backup definition.
Under the backup definition, right-click the backup
job from which you want to restore data.
Select Restore backup sets created by this job.
On the Job Monitor tab, in the Jobs pane, right-click
a server that has been backed up.
Select Restore backup sets created by this job.
Follow the Restore Wizard prompts to restore the data.
Restoring data from a backup set
You can restore data from the backup sets that appear on the Backup and Restore
tab. When you restore data from backup sets, you can only choose data that is
contained in the backup sets.
To restore data from a backup set
1
On the Backup and Restore tab, in the list of servers, double-click a server
that has been backed up.
2
In the Backup Sets view, expand a backup set from which you want to restore.
3
Right-click the backup set from which you want to restore data
4
Click Restore.
5
Follow the Restore Wizard prompts to restore the data.
Restoring data from storage device media
You can restore data from the media that are contained in the storage devices that
appear on the Storage tab. When you restore data directly from storage device
media, you can only restore data that is contained in the backup sets on the media.
The Restore Wizard prompts you to select options for each type of data, and then
submits a separate job for each type of data.
When you restore from storage device media, you can restore multiple types of
data. Separate restore jobs are submitted for each type of data.
To restore data from storage device media
1
Select from the following:
215
Restores
Restoring data from a server, a backup set, a backup job, or a storage device
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
media or a disk cartridge
media
Do the following in the order listed:
■
■
■
On the Storage tab, in the All Storage view, expand
Tape and Disk Cartridge Media.
Navigate to the media that contains the data that
you want to restore.
Right-click the media from which you want to restore,
and then click Restore.
To restore from 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.
■
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.
216
Restores
Restoring file system data
■
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 213.
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.
217
Restores
Performing a complete online restore of a Microsoft Windows computer
3
Do one of the following:
To restore the data to a point-in-time at
which the backup set was created
Select File and folder backups to a
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.
To restore file and folder backups from a
backup set
Select File and folder backups from a
backup set.
Note: When you restore file system data
from a backup set, you select a backup set
to restore. Backup Exec restores the file
system data exactly as it exists in the
backup set that you select. No dependent
backup sets are selected for the restore.
To search for files and folders
4
Select Files and folders located through
Search.
Click Next, and then follow the Restore Wizard prompts to restore the data.
Performing a complete online restore of a
Microsoft Windows computer
You can perform a complete online restore of a Microsoft Windows computer if the
computer was fully selected for a backup. You select the backup set time from
which you want to recover the computer. All required backup sets are automatically
selected. You can select additional backup sets to restore as appropriate. You
cannot redirect the restore of the computer.
218
Restores
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.
See “About backing up critical system components” on page 163.
See “Methods for restoring data in Backup Exec” on page 211.
Restoring System State
Depending on the version of Microsoft Windows, service pack levels, and features
that are installed, you can restore the following system state data:
■
Active Directory
■
Automated system recovery
■
Background Intelligent Transfer Service
■
COM+ Class Registration database
■
Dynamic Host Configuration Protocol
■
Event logs
■
File Server Resource Manager
■
Internet Information Service (IIS)
219
Restores
Restoring System State
■
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 1153.
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 213.
220
Restores
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 163.
See “Performing a complete online restore of a Microsoft Windows computer”
on page 218.
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.
221
Restores
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 211.
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 1153.
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 139.
222
Restores
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: Veritas recommends 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 453.
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 219.
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 324.
223
Restores
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 213.
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 211.
See “Restoring System State ” on page 219.
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
224
Restores
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 213.
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:
3
■
Utility partition
■
Unified Extensible Firmware Interface system partition
Follow the Restore Wizard prompts to restore the data.
See “Methods for restoring data in Backup Exec” on page 211.
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.
225
Restores
About restoring NetWare SMS volume backups to non-SMS volumes with Backup Exec
See “Using encryption with Backup Exec” on page 600.
See “Encryption key management” on page 603.
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 237.
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:
226
Restores
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.
See “Configuring default options for catalogs” on page 227.
See “Cataloging a storage device” on page 450.
See “About cataloging tape or disk cartridge media that contains encrypted backup
sets” on page 411.
See “Configuring Instant GRT and full catalog options to improve backup
performance for GRT-enabled jobs” on page 544.
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 226.
227
Restores
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
sequence for catalog
operations
Catalogs the media in tape drives and disk cartridges
by starting with the lowest known tape number in the
tape family. For example, if you don’t have the first tape,
the catalog job starts with the second tape. If you
uncheck this option, the catalog job begins on the tape
that you specify.
If you uncheck Request all media in the sequence for
catalog operations, then you cannot select the option
Use storage-based catalogs.
This option is enabled by default.
228
Restores
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: Veritas recommends that you always attempt to
use storage-based catalogs first before clearing this
option.
If you uncheck Request all media in the sequence for
catalog operations, then the option Use
storage-based catalogs is unavailable.
This option is enabled by default.
The Use storage-based catalogs option must be
enabled for the following restore scenarios:
■
■
■
■
If you use the NDMP 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 1248.
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 1227.
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 757.
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 608.
229
Restores
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 450.
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:\Program Files\Veritas\Backup
Exec\Catalogs.
Note: Veritas recommends that you use Backup Exec
Utility to change the catalog location. If you change the
location using the Catalog path field, you must also
manually copy the existing catalogs to the new location,
and then restart the Backup Exec services.
See “Moving the Backup Exec catalogs to a new
directory” on page 230.
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.
230
Restores
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
231
Restores
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:
4
■
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.
Click Catalog.
Backup Exec runs the catalog operation.
See “Backup sets ” on page 321.
See “How Backup Exec catalogs work” on page 226.
232
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
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.
234
Job management and monitoring
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.
See “Editing backup definitions” on page 184.
See “Viewing job activity details for active jobs” on page 237.
See “Deleting scheduled jobs” on page 243.
See “Canceling an active job” on page 237.
See “Changing the priority for a scheduled job” on page 242.
See “Running a scheduled job immediately” on page 241.
See “Holding jobs” on page 238.
See “Holding the job queue” on page 240.
See “Running a test run job manually” on page 205.
About the Job Monitor
The Job Monitor provides a single location to monitor and manage all of your
backup, restore, installation, and storage operation jobs. The Job Monitor is divided
into two panes. The Jobs pane displays the details of all of your active jobs and
scheduled jobs. The Job History pane displays the details about all of your jobs
that ran recently. By default, all recent jobs appear in the Job History pane. You
can change the default by filtering the Job History view.
Note: Report jobs do not appear on the Job Monitor. To monitor and manage
report jobs, go to the Reports tab.
235
Job management and monitoring
About the Job Monitor
You can manage active and scheduled jobs in the Jobs pane on the Job Monitor
in the following ways:
■
Edit scheduled jobs.
■
Delete scheduled jobs.
■
Cancel active jobs.
■
Change the priority of scheduled jobs.
■
Run a scheduled job immediately.
■
Hold a job or the job queue.
■
Run a test backup job.
■
View the job activity details for an active job.
■
View the history of a job.
In the Job History pane of the Job Monitor, you can manage completed jobs in
the following ways:
■
Run the job again immediately.
■
View the job log.
■
Delete the job.
■
View the job history details.
■
Enable error-handling rules.
■
Duplicate job histories.
■
Run a verify backup job.
■
Edit the settings for a backup job.
From the Job Monitor, you can restore data from the backup sets of a completed
backup job. Additionally, you can view the backup calendar.
See “How to monitor and manage jobs in Backup Exec” on page 233.
See “Running a test run job manually” on page 205.
See “Duplicating backup sets or a job history manually” on page 200.
See “Verifying backed up data manually” on page 206.
See “Editing backup definitions” on page 184.
236
Job management and monitoring
About the Job Monitor
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
cancelation of a job, the Cancel Pending status appears in the Job Status column.
To cancel an active job
1
Do one of the following:
To cancel the job from the Job Monitor
tab
Select the Job Monitor tab.
To cancel the job from the Backup and
Restore tab or the Storage tab
Do the following:
■
■
On the Backup and Restore tab or the
Storage tab, double-click the server or
the storage device where the job is
running.
In the left pane, click Jobs.
2
Right-click the active job that you want to cancel, and then click Cancel.
3
Click Yes to confirm the cancelation of the job.
237
Job management and monitoring
About the Job Monitor
See “List of job statuses in Backup Exec” on page 257.
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
Monitor tab
Select the Job Monitor tab.
To place a job on hold from the Backup
and Restore tab or the Storage tab
Do the following:
■
■
2
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.
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 239.
238
Job management and monitoring
About the Job Monitor
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
Monitor tab
Select the Job Monitor tab.
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.
239
Job management and monitoring
About the Job Monitor
See “Holding jobs” on page 238.
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
To place the job queue on hold from the
Job Monitor tab
Select the 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 240.
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
240
Job management and monitoring
About the Job Monitor
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 240.
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
Restore tab or the Storage tab
Do the following:
■
■
2
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.
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 242.
See “Deleting scheduled jobs” on page 243.
241
Job management and monitoring
About the Job Monitor
Changing the priority for a scheduled job
The priority determines the order that jobs run. If two jobs are scheduled to run at
the same time, the priority you set determines which job runs first. The priority is
changed for all occurrences of the scheduled job.
The priority of the job is displayed in the Priority column in the Jobs list.
This option is most useful if there are limited storage devices in your environment,
but you want certain jobs to have priority access to the devices. A ready job that
has a higher priority runs before a ready job that has a lower priority. A ready job
that has a higher priority also runs before a ready job that has an earlier scheduled
start time.
If multiple jobs are ready to run but must wait for a storage device to become
available, then Backup Exec determines which jobs to run first. Backup Exec reviews
the job priority and the scheduled start time of the job.
You can set the job priority when you do the following tasks:
■
Select storage options when you create or edit a backup job
■
View scheduled jobs in the Job Monitor tab
■
View a server's scheduled jobs from the Jobs pane on the Backup and Restore
tab
If you change the job priority in the storage options or on the Jobs pane, you can
choose from the following levels of priority:
■
Highest
■
High
■
Medium
■
Low
■
Lowest
If you change the job priority from the Job Monitor, you can only increase or
decrease the job priority. You cannot specify a level.
To change the priority for a scheduled job
1
Do one of the following:
To change the job's priority from the Job
Monitor tab
Select the Job Monitor tab.
242
Job management and monitoring
About the Job Monitor
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.
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
Monitor tab
Select the Job Monitor tab.
243
Job management and monitoring
About the Job History
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 233.
About the Job History
The Job History displays a list of completed and failed backup, restore, and storage
operation jobs. The Job History appears on the lower pane of the Job Monitor
tab. It also appears when you select a server on the Backup and Restore tab, and
when you select a storage device on the Storage tab.
From the Job History, you can do any of the following:
■
View the job log.
■
Delete a job.
■
Rerun a job.
■
Duplicate the data from a completed backup job.
■
Verify a backup job.
■
Enable error-handling rules for a failed job.
See “Running a job from the Job History” on page 246.
See “Viewing the job log ” on page 247.
See “Deleting a job from the Job History” on page 245.
See “Enabling an error-handling rule for a failed job” on page 255.
See “Duplicating backup sets or a job history manually” on page 200.
See “Verifying backed up data manually” on page 206.
244
Job management and monitoring
About the Job History
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
Monitor tab
On the Job Monitor tab, locate the job in
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:
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.
245
Job management and monitoring
About the Job History
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 244.
See “Configuring database maintenance and security” on page 576.
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
Job Monitor tab
On the Job Monitor tab, locate the job in
the Job Histories pane.
To run a job from the Job History on the ■
Backup and Restore tab or the Storage
tab
■
2
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.
Right-click the job that you want to run, and then click Run Now.
See “About the Job History” on page 244.
246
Job management and monitoring
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
Restore tab or the Storage tab
Do the following:
■
■
On the Backup and Restore tab or the
Storage tab, double-click the server or
the storage device where the job ran.
In the left pane, click Job History.
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
Monitor tab
On the Job Monitor tab, in the Job
Histories pane, locate the job for which
you want to search the job log.
247
Job management and monitoring
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:
6
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.
Click Next to find the next occurrence of the text.
See “Viewing the job log ” on page 247.
248
Job management and monitoring
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
Monitor tab
On the Job Monitor tab, locate the job in
the Job Histories pane.
To access the job log from the Backup
and Restore tab or the Storage tab
Do the following:
■
■
On the Backup and Restore tab or the
Storage tab, double-click the server or
the storage device where the job ran.
In the left pane, click Job History.
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 249.
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
Monitor tab
On the Job Monitor tab, locate the job in
the Job Histories pane.
To access the job log from the Backup
and Restore tab or the Storage tab
Do the following:
■
■
2
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.
Right-click the job, and then select View Job Log.
249
Job management and monitoring
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 249.
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 252.
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:
250
Job management and monitoring
Viewing the job log
Get-BEJobLog "pathname\job log filename"
For example, to display the job log C:\program files\Veritas\Backup
Exec\Data\bex00001.xml in text format to the command prompt, you would type:
Get-BEJobLog "C:\program files\Veritas\Backup Exec\Data\bex00001.xml"
To redirect the job log to a file, you would type one of the following:
Get-BEJobLog "C:\program files\Veritas\Backup Exec\Data\bex00001.xml" >
bex00001.txt
See “Viewing the job log ” on page 247.
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.
251
Job management and monitoring
Error-handling rules for failed or canceled jobs
Summary information and directories
processed
Select this option to include summary
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 247.
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.
252
Job management and monitoring
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 253.
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 256.
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 252.
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.
253
Job management and monitoring
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 255.
See “About the cluster failover error-handling rule” on page 256.
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:
4
■
To enable the rule, check Enable error-handling rule.
■
To disable the rule, clear the Enable error-handlng rule check box
Click OK.
See “Error-handling rules for failed or canceled jobs” on page 252.
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.
254
Job management and monitoring
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 252.
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
Job Monitor tab
Select the 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.
255
Job management and monitoring
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 252.
See “About the cluster failover error-handling rule” on page 256.
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 252.
256
Job management and monitoring
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 257.
See the section called “Completed job statuses” on page 258.
See the section called “Scheduled job statuses” on page 260.
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 574.
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 453.
257
Job management and monitoring
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 1211.
Stalled
The Backup Exec services have become unresponsive.
See “Setting job status and recovery options” on page 262.
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 1199.
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 1199.
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
exceptions
The job completed, but some files were in use, skipped, or
corrupted.
258
Job management and monitoring
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:
■
■
■
■
Recovered
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.
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.
259
Job management and monitoring
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 568.
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 568.
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 255.
260
Job management and monitoring
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.
■
■
■
■
■
■
■
261
Job management and monitoring
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 1211.
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.
262
Job management and monitoring
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.
4
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.
Click OK.
263
Job management and monitoring
Setting job status and recovery options
See “List of job statuses in Backup Exec” on page 257.
See “Custom error-handling rule for recovered jobs” on page 255.
264
Chapter
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
7
Alerts and notifications
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
266
Alerts and notifications
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 282.
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 677.
See “Responding to active alerts” on page 273.
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 274.
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.
267
Alerts and notifications
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.
268
Alerts and notifications
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:
269
Alerts and notifications
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 270.
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 269.
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.
270
Alerts and notifications
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.
271
Alerts and notifications
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.
272
Alerts and notifications
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 269.
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
273
Alerts and notifications
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 282.
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 282.
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.
274
Alerts and notifications
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 275.
Step 2
Add the contact information for the people or groups that you want to
receive notifications.
See “Adding recipients for notification” on page 277.
See “Adding a recipient group for alert notifications” on page 279.
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 284.
See “Configuring alert categories” on page 282.
See “Sending a notification when a job completes” on page 284.
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.
275
Alerts and notifications
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 Veritas 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.
276
Alerts and notifications
Adding recipients for notification
If you want to send alert notifications by
email
Do the following:
■
■
If you want to send alert notifications by
text message
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.
In Text message service provider
address, enter the fully-qualified domain
name of the sender's text messaging
service provider.
Example: If a company called "MyPhone"
provides text messaging services, then
enter "MyPhone.com" in the Text message
service provider address field. You can
override this default address for the
individuals who do not use this provider.
Note: Text message notification is sent
as SMTP mail to an email address that is
provided by a text messaging service
provider. To enable notification by text
message, you must enter the information
about the sender's email account in the
Email configuration section in addition to
the fully-qualified domain name of the
default text messaging service provider.
4
Click OK.
You can now add information about the recipients who need to receive alert
notifications.
See “Adding recipients for notification” on page 277.
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
277
Alerts and notifications
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 275.
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.
278
Alerts and notifications
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 284.
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.
279
Alerts and notifications
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 277.
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.
280
Alerts and notifications
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 285.
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:
5
■
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.
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.
281
Alerts and notifications
Configuring alert categories
See “Disabling notifications for a specific alert category” on page 285.
See “Disabling email or text message alert notification for a recipient” on page 280.
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.
282
Alerts and notifications
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
notifications
Sends the job log to the recipient that is
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 appears in the Windows Event log
you can search the Veritas 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
hours/minutes
Lets you enter the number of 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.
283
Alerts and notifications
Assigning recipients to receive notifications for specific alert categories
Send notification to the following
recipients
Lets you select the name of a recipient to
notify when this type of alert occurs. You
must have recipients configured to use this
option.
If the recipient to which you want to send
notifications is not in the list, click Manage
Recipients to add the recipient.
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.
284
Alerts and notifications
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 284.
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\Symantec\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.
285
Alerts and notifications
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 280.
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.
286
Alerts and notifications
Enabling or disabling pop-up alerts
4
In the Display pop-up alerts for the following alert types group box, check
the check boxes for the types of alerts that you want to see in a pop-up alert.
Clear the check boxes for the types of alerts that you do not want to see in a
pop-up alert.
Informational
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.
5
In the Number of seconds to display pop-up alerts field, enter the amount
of time you want pop-up alerts to remain on the screen.
6
Click OK.
Enabling or disabling pop-up alerts
By default, Backup Exec displays informational, error, warning, and attention required
alert types in pop-up alert windows when an error occurs. You can change the
default settings so that you see only the types of alerts that are important to you.
To enable or disable pop-up alerts
1
Click the Backup Exec button, and then select Configuration and Settings.
2
Select Backup Exec Settings, and then select Alerts.
287
Alerts and notifications
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:
Application
initializing
machine name
product, version,
revision
Product Stop
1302.3.1.1.9.2
Backup Exec:
Application
terminating
machine name
product, version,
revision
Job Canceled
1302.3.1.2.8.2
Backup Exec: Job machine name
canceled by
Operator
job name
local or remote
Operator name
Job Failed
1302.3.1.2.8.1
Backup Exec: Job machine name
failed
job name
detail message
Storage device
requires human
intervention
1302.3.2.5.3.3
Backup Exec:
machine name
Storage device
requires attention
job name
detail message
288
Alerts and notifications
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
requires human
intervention
1302.3.2.4.3.3
Backup Exec:
robotic library
device requires
attention
machine name
job name
detail message
Simplified Disaster 1302.3.1.4.2.1.2 SDR full backup
Recovery Message
success
machine name
job name
detail message
Backup Exec
system error
The application
has encountered
an error
machine name
job name
detail message
Backup Exec
1302.3.1.1.9.4
general information
Information on
normal events
machine name
job name
detail message
Job Success
1302.3.1.2.8.3
The job
succeeded
machine name
job name
detail message
Job Success with
exceptions
1302.3.1.2.8.4
The job
succeeded, but
there was a
problem
machine name
job name
detail message
Job Started
1302.3.1.2.8.5
The job has
started
machine name
job name
detail message
Job Completed
with no data
1302.3.1.2.8.6
The job
machine name
succeeded, but
there was no data
job name
detail message
Job Warning
1302.3.1.2.8.7
The job has a
warning
machine name
job name
detail message
PVL Device Error
1302.3.1.5.1.1.1 The device has
encountered an
error
machine name
job name
detail message
PVL Device
Warning
1302.3.1.5.1.1.2 The device has
encountered a
warning
machine name
job name
detail message
PVL Device
Information
1302.3.1.5.1.1.3 Normal device
information
machine name
job name
detail message
PVL Device
Intervention
1302.3.1.5.1.1.4 Device requires
attention
machine name
job name
detail message
1302.3.1.1.9.3
289
Alerts and notifications
SNMP traps for Backup Exec alerts
Table 7-7
Trap Type
Object ID
PVL Media Error
SNMP traps (continued)
String 1
String 2
String 3
String 4
1302.3.1.5.2.1.1 There is an error
with the media
machine name
job name
detail message
PVL Media
Warning
1302.3.1.5.2.1.2 There may be a
problem with the
media
machine name
job name
detail message
PVL Media
Information
1302.3.1.5.2.1.3 Normal media
information
machine name
job name
detail message
PVL Media
Intervention
1302.3.1.5.2.1.4 Media requires
attention
machine name
job name
detail message
Catalog Error
1302.3.1.5.3.1.1 There is an error
with the catalog
machine name
job name
detail message
Tape Alert Error
1302.3.1.5.4.1.1 There is a
TapeAlert error
machine name
job name
detail message
Tape Alert Warning 1302.3.1.5.4.1.2 There is a
machine name
TapeAlert warning
job name
detail message
Tape Alert
Information
1302.3.1.5.4.1.3 Normal TapeAlert machine name
information
job name
detail message
Database
1302.3.1.5.5.1.1 There is a
machine name
Maintenance Error
database
maintenance error
job name
detail message
Database
Maintenance
Information
1302.3.1.5.5.1.2 Normal database
maintenance
information
machine name
job name
detail message
Veritas Update
Error
1302.3.1.5.6.1.1 There is a
software update
error
machine name
job name
detail message
Veritas Update
Warning
1302.3.1.5.6.1.2 There is a
software update
warning
machine name
job name
detail message
Veritas Update
Information
1302.3.1.5.6.1.3 Normal software machine name
update information
job name
detail message
Install Update
Warning
1302.3.1.5.7.1.1 There is an install machine name
warning
job name
detail message
290
Alerts and notifications
SNMP traps for Backup Exec alerts
SNMP traps (continued)
Table 7-7
Trap Type
Object ID
String 1
Install Update
Information
1302.3.1.5.7.1.2 Normal Install
information
String 2
String 3
String 4
machine name
job name
detail message
See “Installing and configuring the SNMP system service” on page 291.
Installing and configuring the SNMP system service
To receive Backup Exec traps at the SNMP console, you must configure the SNMP
system service with the SNMP console's IP address.
SNMP starts automatically after installation. You must be logged on as an
administrator or a member of the Administrators group to complete this procedure.
If your computer is connected to a network, network policy settings might also
prevent you from completing this procedure.
To install the SNMP system service and configure it to send traps to the SNMP
console
1
From the Windows Control Panel, select Add/Remove Programs.
2
Click Add/Remove Windows Components.
3
In Add/Remove Windows Components, select Management and Monitoring
Tools, and then click Details.
When selecting the component, do not select or clear its check box.
4
Select Simple Network Management Protocol, and then click OK.
5
Click Next.
Installing the Windows Management Instrumentation performance
counter provider
Windows Management Instrumentation (WMI) is an infrastructure through which
you can monitor and control system resources. Backup Exec includes performance
counter and SNMP providers that can be manually installed and used with WMI.
To install the WMI performance counter provider
1
Insert the Backup Exec Installation media.
2
At the command prompt, type the following:
mofcomp <CD Drive Letter>:\winnt\wmi\backupexecperfmon.mof
291
Alerts and notifications
SNMP traps for Backup Exec alerts
Installing the Windows Management Instrumentation provider for
SNMP
Windows Management Instrumentation (WMI) is an infrastructure through which
you can monitor and control system resources. Backup Exec includes performance
counter and SNMP providers that can be manually installed and used with WMI.
To use the WMI SNMP provider you must set up SNMP notification.
To install the WMI SNMP provider
1
Before you install the SNMP provider that is included with Backup Exec, you
must have the Microsoft SNMP provider installed on your system.
For more information, refer to your Microsoft documentation.
2
Insert the Backup Exec Installation media.
3
At the command prompt, type the following:
mofcomp <CD Drive Letter>:\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
292
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
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 297.
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 308.
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 Veritas
Backup Exec Deduplication feature to use
this data-reduction strategy that optimizes
storage and network bandwidth.
See “About the Deduplication feature”
on page 828.
Network-based storage includes NDMP servers, OpenStorage devices, cloud
storage devices, and the Remote Media Agent for Linux.
294
Disk-based and network-based storage
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 1239.
OpenStorage
devices
OpenStorage devices are network-attached storage that supports
Veritas's OpenStorage technology.
See “Configuring an OpenStorage device” on page 839.
Cloud storage
devices
Cloud storage devices are the storage devices that are configured on
the cloud hosted by the cloud storage service provider.
Remote Media
Agent for Linux
The Remote Media Agent for Linux lets you back up data from remote
computers to the storage devices that are directly attached to a Linux
server. You can also back up to a simulated tape library on a Linux
server.
See “About the Remote Media Agent for Linux ” on page 1291.
See “Storage trending statuses for disk storage and virtual disks” on page 295.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 315.
See “Viewing jobs, job histories, backup sets, and active alerts for storage devices”
on page 450.
See “Backup sets ” on page 321.
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.
295
Disk-based and network-based storage
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
gathered
This status may appear for any of the
following reasons:
■
The disk storage device has not been
configured long enough to get a statistical
estimate.
Note: After you create disk storage,
Backup Exec may take approximately one
month to gather enough information to
provide a storage estimate.
■
Current storage is sufficient
This storage may be on a managed
Backup Exec server that is currently in a
rolling upgrade.
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
available
Backup Exec has not collected enough
sample data for statistical analysis.
Note: After you create disk storage, Backup
Exec may take approximately one month to
gather enough information to provide a
storage estimate.
See “Configuring disk storage” on page 297.
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
296
Disk-based and network-based storage
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:
4
■
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.
Click Apply.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 315.
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
297
Disk-based and network-based storage
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.
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
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
298
Disk-based and network-based storage
Configuring disk storage
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. Veritas recommends that you do not
configure disk storage on the system drive.
Note: If Windows data deduplication is enabled on the disk storage volume, Backup
Exec excludes the backup data in the folder \BEData from deduplication, unless
the \BEData folder already exists. Backup Exec must exclude backup data from
deduplication for you to use Simplified Disaster Recovery (SDR) to perform a local
recovery of the Backup Exec server.
If Windows data deduplication is enabled on the disk storage volume, local disaster
recovery using SDR fails. The Windows Preinstallation Environment (Windows PE)
that SDR uses cannot read the files that Windows data deduplication processes.
To configure disk storage
1
On the Storage tab, in the Configure group, click Configure Storage.
2
Do one of the following:
If the Central Admin Server feature is not
installed
Click Disk-based storage, and then click
Next.
If the Central Admin Server feature is
installed
Do the following in the order listed:
■
■
Select the Backup Exec server on
which you want to configure storage,
and then click Next.
Click 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:
299
Disk-based and network-based storage
Configuring disk storage
To change the configuration
Do the following in the order listed:
■
■
■
To configure the disk storage device
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.
Click Finish.
See “Changing the location of a disk storage device” on page 300.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 315.
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.
300
Disk-based and network-based storage
Configuring disk storage
To configure the disk storage device
7
Click Finish.
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 453.
See “Configuring disk storage” on page 297.
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.
301
Disk-based and network-based storage
Configuring disk storage
Limit Backup Exec to read-only
operations
Prevents Backup Exec from deleting
expired backup sets on this disk storage
when you reattach the disk storage to the
Backup Exec server. Otherwise, Backup
Exec's data lifecycle management feature
deletes any backup sets that are expired
and reclaims the disk space.
The default value is No.
This option applies only when the disk
storage has been detached from the
Backup Exec server for the number of days
that you specify in the global setting. The
default number of days is 14.
See “How data lifecycle management
(DLM) deletes expired backup sets on
disk-based storage” on page 315.
See “Backup sets ” on page 321.
See “How to restore data from a reattached
or reinserted disk-based storage device”
on page 307.
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.
302
Disk-based and network-based storage
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.
303
Disk-based and network-based storage
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.
304
Disk-based and network-based storage
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%.
305
Disk-based and network-based storage
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 315.
Disk space to reserve for non-Backup
Exec operations
Displays the amount of disk space to set
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.
306
Disk-based and network-based storage
How to restore data from a reattached or reinserted disk-based storage device
Buffered write
Indicates the following when the setting is
enabled:
■
■
Concurrent write sessions
4
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.
Displays the number of concurrent write
operations that you want to allow to this
disk storage device.
Click Apply.
See “Configuring disk storage” on page 297.
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 453.
See “Backup sets ” on page 321.
307
Disk-based and network-based storage
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
installed
Click Disk-based storage, and then click
Next.
If the Central Admin Server feature is
installed
Do the following in the order listed:
■
■
Select the Backup Exec server that you
want to configure storage for, and then
click Next.
Click Disk-based storage , and then
click Next.
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:
308
Disk-based and network-based storage
Configuring disk cartridge storage
To change the configuration
Do the following in the order listed:
■
■
■
To configure the disk cartridge device
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.
Click Finish.
See “Editing disk cartridge properties” on page 309.
Editing disk cartridge properties
You can edit settings for the disk cartridge storage.
See “Configuring disk cartridge storage” on page 308.
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.
309
Disk-based and network-based storage
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.
310
Disk-based and network-based storage
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.
311
Disk-based and network-based storage
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 425.
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 425.
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 425.
312
Disk-based and network-based storage
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 308.
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.
313
Disk-based and network-based storage
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.
314
Disk-based and network-based storage
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
Limit Backup Exec to read-only
operations
Prevents Backup Exec from deleting
expired backup sets on this disk cartridge
media when you reinsert the cartridge
media into the storage device. If you select
Yes in the drop-down menu, then Backup
Exec's data lifecycle management feature
deletes any backup sets that are expired
and reclaims the disk space.
The default value is No.
This option applies only when the disk
cartridge media is absent from the Backup
Exec server for the number of days that
you specify in the global setting. By default,
the number of days that the disk cartridge
media must be absent before this option
takes effect is 30 days.
See “How data lifecycle management
(DLM) deletes expired backup sets on
disk-based storage” on page 315.
See “Backup sets ” on page 321.
See “How to restore data from a reattached
or reinserted disk-based storage device”
on page 307.
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
315
Disk-based and network-based storage
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 325.
See “Changing the expiration date of backup sets on disk-based storage”
on page 324.
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.
316
Disk-based and network-based storage
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 645.
See “Audit Log report” on page 678.
Storage options that can affect how data lifecycle management deletes backup
sets are described in the following table:
317
Disk-based and network-based storage
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
backup sets
This global setting lets Backup Exec delete
expired backup sets, even if they are the last
remaining backup sets that you need to
restore a server. Use this option when you
want to delete backup data after a period of
time. Alternatively, you can manually delete
backup sets.
Warning: If you enable this option, the data
that you need to restore a server may not be
available.
The following conditions may cause you to
lose backup sets when you enable this option:
■
■
If the backup sets from the last full backup
job expire before the next full backup runs.
Ensure that when you create jobs, the
backup sets are kept longer than the
amount of time between full backups.
If the backup job fails or is missed, and is
not rerun before the backup sets expire.
Monitor any failed or missed jobs, and
ensure that you rerun them before the
backup sets from the previous full backup
expire.
Note: In a Central Admin Server 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 438.
318
Disk-based and network-based storage
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
Table 8-4
Storage option
Storage options in Backup Exec that affect data lifecycle
management (continued)
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 325.
See “Changing the expiration date of backup
sets on disk-based storage” on page 324.
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 438.
319
Disk-based and network-based storage
How data lifecycle management (DLM) deletes expired backup sets on disk-based storage
Table 8-4
Storage option
Storage options in Backup Exec that affect data lifecycle
management (continued)
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 321.
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 438.
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 301.
See “Editing disk cartridge properties”
on page 309.
See “Editing the properties of a deduplication
disk storage device” on page 847.
320
Disk-based and network-based storage
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 296.
For more information, refer to the Backup Exec Best Practices document.
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
and Backup Exec uses the data lifecycle management feature to delete the backup
321
Disk-based and network-based storage
Backup sets
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
devices, deduplication disk
storage, storage arrays, cloud
storage, and virtual disks
Backup Exec uses data lifecycle management to
automatically delete expired backup sets from disk-based
storage. By default, Backup Exec keeps the most recent
backup sets that are necessary to restore any backed-up
component of a server, even if the backup sets expire. Even
if the backup set is displayed as expired, the data is available
until all dependent backup sets expire as well.
For disk-based storage and any disk cartridges that you
reattach to the Backup Exec server after a specified number
of days, you can prevent Backup Exec from reclaiming that
disk space. A global setting limits Backup Exec to read-only
operations on disk-based storage or a disk cartridge if it has
been detached for a specified number of days. You can also
limit Backup Exec to read-only operations per disk storage
or disk cartridge by enabling the setting on the device
properties.
See “How data lifecycle management (DLM) deletes expired
backup sets on disk-based storage” on page 315.
See “How to restore data from a reattached or reinserted
disk-based storage device” on page 307.
322
Disk-based and network-based storage
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 382.
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 324.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 325.
See “Releasing retained backup sets on disk-based storage” on page 326.
See “Cataloging backup sets” on page 231.
See “Viewing the contents or properties of backup sets” on page 327.
323
Disk-based and network-based storage
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 315.
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:
4
■
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.
Do either of the following:
324
Disk-based and network-based storage
Backup sets
To expire backup sets
immediately
■
■
To change the expiration date ■
of backup sets
■
■
Click Expire.
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.
Click Expiration.
Enter the new expiration date in the Expiration field.
Click OK.
See “Backup sets ” on page 321.
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 315.
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:
4
■
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.
Click Retain.
325
Disk-based and network-based storage
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.
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 321.
See “Releasing retained backup sets on disk-based storage” on page 326.
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:
4
■
To release a single backup set, right-click the backup set.
■
To release multiple backup sets, Shift + click or Ctrl + click the backup sets,
and then right-click one of the selected backup sets.
Click Retain.
326
Disk-based and network-based storage
Backup sets
5
Select Do not retain.
6
Click OK.
See “Backup sets ” on page 321.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 325.
See “How data lifecycle management (DLM) deletes expired backup sets on
disk-based storage” on page 315.
Viewing the contents or properties of backup sets
After you complete a backup job, you can view the data that is contained in the
backup sets that are created. Viewing the contents of backup sets can help you to
confirm what data was backed up. You may also want to view the contents of backup
sets before you run a restore job to verify the data that they contain.
You can also view the following backup set properties:
■
Backup source
■
Backup date
■
Expiration date
■
Backup method
■
Size
■
Location
■
Backup set description
■
Data encryption
■
True image
■
Server name
■
Catalog file name
■
Snapshot
To view the contents or properties of backup sets
1
On the Backup and Restore tab or the Storage tab, double-click the server
or the storage device that is related to the backup sets that you want to view.
2
In the left pane, click Backup Sets.
327
Disk-based and network-based storage
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
backup sets
In the left pane, click Contents.
To view the properties of the
backup sets
In the left pane, click Properties.
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.
See “Backup sets ” on page 321.
328
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
■
Editing the properties of a cloud-based storage device
■
Best practices for using cloud-based storage
■
Changing default cloud storage settings
■
About the Veritas 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.
For the list of supported public and private cloud providers, refer to the Backup
Exec hardware compatibility list.
Cloud-based storage devices
Amazon S3 cloud-based storage
Note: A cloud storage device cannot belong to any storage pools.
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 600.
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 330.
See “Configuring storage for Amazon cloud storage” on page 331.
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.
■
Ensure that you have already created the buckets. Buckets represent a logical
unit of storage on the cloud-based storage device.
330
Cloud-based storage devices
Amazon S3 cloud-based storage
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 331.
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 542.
See “Adding a stage to a backup definition” on page 198.
See “Requirements for configuring an Amazon S3 cloud-based storage device”
on page 330.
331
Cloud-based storage devices
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) or Standard_IA
(Infrequently accessed data).
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:
9
■
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.
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.
332
Cloud-based storage devices
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 333.
See “Configuring storage for Google cloud storage” on page 334.
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.
333
Cloud-based storage devices
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 334.
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 542.
See “Adding a stage to a backup definition” on page 198.
See “Requirements for configuring a Google cloud-based storage device”
on page 333.
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.
334
Cloud-based storage devices
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.
335
Cloud-based storage devices
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 337.
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 337.
336
Cloud-based storage devices
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 542.
See “Requirements for configuring a Microsoft Azure cloud-based storage device”
on page 336.
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.
337
Cloud-based storage devices
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 338.
See “Configuring storage for a private cloud-based storage device” on page 340.
See “Creating a cloud instance for a private cloud” on page 340.
See “Viewing and editing existing cloud instances for a private cloud” on page 342.
See “Deleting a cloud instance for a private cloud” on page 342.
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:
338
Cloud-based storage devices
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 340.
■
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 340.
339
Cloud-based storage devices
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:\Program Files\Veritas\Backup Exec
See “Configuring storage for a private cloud-based storage device” on page 340.
See “Requirements for configuring a private cloud-based storage device”
on page 338.
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 542.
See “Creating a cloud instance for a private cloud” on page 340.
340
Cloud-based storage devices
Private cloud-based storage
See “Adding a stage to a backup definition” on page 198.
See “Requirements for configuring a private cloud-based storage device”
on page 338.
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.
341
Cloud-based storage devices
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:\Program Files\Veritas\Backup Exec
See “Creating a cloud instance for a private cloud” on page 340.
See “Deleting a cloud instance for a private cloud” on page 342.
Deleting a cloud instance for a private cloud
Type the following command in BEMCLI to delete a custom cloud instance:
Remove-BECloudInstance
342
Cloud-based storage devices
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 448.
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:\Program Files\Veritas\Backup Exec
See “Creating a cloud instance for a private cloud” on page 340.
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. Veritas makes 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 not developed by Veritas or an authorized 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
343
Cloud-based storage devices
About S3-Compatible Cloud Storage
in a 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 330.
See “Google cloud-based storage” on page 333.
See “Private cloud-based storage” on page 338.
See “Configuring S3-Compatible Cloud Storage with Backup Exec” on page 344.
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. Veritas recommends 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 330.
See “Google cloud-based storage” on page 333.
See “Private cloud-based storage” on page 338.
344
Cloud-based storage devices
Editing the properties of a cloud-based storage device
See “About S3-Compatible Cloud Storage” on page 343.
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.
345
Cloud-based storage devices
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
proximity
Indicates the Backup Exec server that has
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.
346
Cloud-based storage devices
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
backing up data to a
public cloud storage
device
Some public cloud storage providers require encryption to be
enabled when backup jobs or duplicate jobs are targeted to cloud
storage.
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 600.
Network usage and
backups to a cloud
storage device
During data transfer, a cloud-based storage device consumes
high bandwidth. This might affect the functioning of any other
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.
347
Cloud-based storage devices
Changing default cloud storage settings
Table 9-1
Item
Best practices for using cloud-based storage (continued)
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.
■ Veritas recommends 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 Veritas Backup Exec™ CloudConnect Optimizer”
on page 350.
See “Configuring the Veritas Backup Exec™ CloudConnect
Optimizer” on page 350.
See “Editing the CloudConnect Optimizer job” on page 352.
See “Deleting the CloudConnect Optimizer job” on page 353.
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. Veritas recommends 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,
348
Cloud-based storage devices
Changing default cloud storage settings
which 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 Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
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, Veritas recommends 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.
349
Cloud-based storage devices
About the Veritas Backup Exec™ CloudConnect Optimizer
About the Veritas 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
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 348.
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.
Veritas recommends 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 Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Editing the CloudConnect Optimizer job” on page 352.
See “Deleting the CloudConnect Optimizer job” on page 353.
Configuring the Veritas Backup Exec™ CloudConnect Optimizer
You can configure and run the CloudConnect Optimizer job to get a suggested
Write Connections value.
350
Cloud-based storage devices
About the Veritas Backup Exec™ CloudConnect Optimizer
To configure the CloudConnect Optimizer job
1
On the Storage tab, right-click a cloud storage device and click CloudConnect
Optimizer.
2
On the Veritas 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.
351
Cloud-based storage devices
About the Veritas Backup Exec™ CloudConnect Optimizer
4
5
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.
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 348.
See “About the Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Editing the CloudConnect Optimizer job” on page 352.
See “Deleting the CloudConnect Optimizer job” on page 353.
Editing the CloudConnect Optimizer job
You can edit a scheduled CloudConnect Optimizer job.
352
Cloud-based storage devices
About the Veritas Backup Exec™ CloudConnect Optimizer
To edit the CloudConnect Optimizer job
1
Do one of the following:
To edit a CloudConnect
Optimizer job from the Job
Monitor tab.
On the Job Monitor tab, right-click the scheduled
CloudConnect Optimizer job and then click Edit.
To edit a CloudConnect
Optimizer job from the
Storage tab.
On the Storage tab, right-click the scheduled
CloudConnect Optimizer job and then click Edit.
2
On the CloudConnect Optimizer dialog box, make any necessary changes.
3
Click OK.
See “About the Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Configuring the Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Deleting the CloudConnect Optimizer job” on page 353.
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
Optimizer job from the Job
Monitor tab.
On the Job Monitor tab, locate the scheduled
CloudConnect Optimizer job that you want to delete.
To delete a CloudConnect
Optimizer job from the Storage
tab.
On the Storage tab, locate the scheduled
CloudConnect Optimizer job that you want to delete.
2
Right-click the scheduled job, and then click Delete.
3
Click Yes.
See “About the Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Configuring the Veritas Backup Exec™ CloudConnect Optimizer” on page 350.
See “Editing the CloudConnect Optimizer job” on page 352.
353
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
Legacy backup-to-disk folders
You cannot send backup data to a backup-to-disk folder. Veritas recommends that
you back up data to a disk-based storage device.
See “Features and types of disk-based storage and network-based storage”
on page 293.
See “Restoring data from a legacy backup-to-disk folder” on page 357.
See “Changing the location of a legacy backup-to-disk folder” on page 356.
See “Recreating a legacy backup-to-disk folder and its contents” on page 357.
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 354.
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:
4
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.
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:
355
Legacy backup-to-disk folders
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 354.
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.
356
Legacy backup-to-disk folders
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 357.
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 354.
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 357.
3
Right-click the backup-to-disk folder, and then click Inventory and Catalog.
See “Inventorying and cataloging a storage device” on page 453.
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 324.
See “Retaining backup sets on disk-based storage to prevent them from expiring”
on page 325.
357
Legacy backup-to-disk folders
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
installed
Select Disk-based Storage, and then click
Next.
If the Central Admin Server feature is
installed
Do the following in the order listed:
■
■
Select the Backup Exec server on
which you want to import a legacy
backup-to-disk folder, and then click
Next.
Select Disk-based Storage, and then
click Next.
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.
358
Legacy backup-to-disk folders
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.
359
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
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 362.
■
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 382.
See “Viewing jobs, job histories, backup sets, and active alerts for storage devices”
on page 450.
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.
361
Tape storage
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 Veritas 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:
362
Tape storage
Installing tape device drivers
■
Ensure that Backup Exec supports the tape device.
You can find a list of compatible types of storage in the Backup Exec hardware
compatibility list.
■
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
Veritas 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.
Veritas 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.
363
Tape storage
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:\Program Files\Veritas\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 361.
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.
364
Tape storage
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.
365
Tape storage
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.
366
Tape storage
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.
Veritas recommends that you select this
option if the tape drive is shared.
This option is enabled by default.
367
Tape storage
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.
Veritas recommends 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 447.
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 371.
Can Read From
Indicates if this tape drive can read from
the media type.
See “Configuring barcode rules for a
robotic library ” on page 371.
368
Tape storage
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 371.
4
Click Apply.
Viewing tape drive statistics
You can view statistics about tape drives.
See “Support for tape drives and robotic libraries” on page 361.
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
369
Tape storage
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 370.
See “Creating robotic library partitions” on page 377.
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
370
Tape storage
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 369.
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. Veritas recommends that you enable
this default if media is often moved between robotic libraries. Backup Exec may
take longer to start.
To inventory robotic libraries when Backup Exec services start
1
Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2
In the left pane, click Storage.
3
Click Inventory robotic libraries when Backup Exec services start.
4
Click OK.
See “Inventorying a storage device” on page 452.
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 372.
See the section called “Adding, editing, and deleting barcode rules by using the
Backup Exec global settings” on page 373.
371
Tape storage
Robotic libraries in Backup Exec
See the section called “Enabling or disabling barcode rules by using robotic library
properties” on page 373.
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
installed
Click Tape storage, and then click Next.
If the Central Admin Server feature is
installed
Do the following in the order listed:
■
■
Select the Backup Exec server on
which you want to configure storage,
and then click Next.
Click Tape storage, and then click
Next.
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:
■
■
To delete a barcode rule
6
Click Next.
Select the barcode rule that you want
to edit, and then click Edit.
Make any changes, and then click OK.
Select a barcode rule, click Delete, and
then click Yes to confirm the deletion.
372
Tape storage
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:
■
■
■
To complete the barcode configuration
9
Click the heading that contains the
items that you want to change.
Make any changes, and then click
Next.
Click Finish.
Click Finish.
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.
373
Tape storage
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.
374
Tape storage
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 454.
See “Robotic libraries in Backup Exec” on page 369.
375
Tape storage
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 457.
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 369.
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.
376
Tape storage
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
4
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.
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 379.
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
377
Tape storage
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:
■
■
■
To configure the partitions
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.
Click Finish.
Adding or removing tape drives in a robotic library partition
You can add or remove tape drives in a robotic library partition.
378
Tape storage
Creating robotic library partitions
See “Creating robotic library partitions” on page 377.
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
partition
To remove a tape drive from the robotic
library partition
4
Do the following in the order listed:
■
Click Add.
■
In the devices list that appears, select
the tape drive that you want to add, and
then click OK.
Select the tape drive that you want to
remove, and then click Remove.
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 369.
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 369.
379
Tape storage
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 457.
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.
380
Tape storage
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:
■
■
■
To remove the partitions
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.
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:
■
■
■
To configure the partitions
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.
Click Finish.
See “Reassigning a slot base number for robotic libraries” on page 379.
381
Tape storage
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.
See “Default media sets” on page 382.
See “Tape media rotation strategies” on page 414.
See “Creating media sets for tapes” on page 390.
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.
382
Tape storage
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 458.
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
Backup Media
Displays all media that is imported from another
installation of Backup Exec.
See “Cataloging a storage device” on page 450.
Cleaning Media
Displays all cleaning media.
See “Cleaning a robotic library drive” on page 457.
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 226.
See “Cataloging a storage device” on page 450.
383
Tape storage
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 409.
See “Retiring damaged tape media” on page 408.
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 386.
Backup Exec creates the following default user media sets:
384
Tape storage
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
Not Allow Overwrite
Displays all tape media that you associate with this media
set.
When you associate media with this media set, data is not
overwritten unless you perform any of the following actions
on the media:
■
Erase
■
Label
■
Format
■
Associate the media with the scratch media set
You can append data to this media for an infinite period (until
the media is full).
You can edit and rename Keep Data Infinitely - Do Not
Allow Overwrite after installation. Therefore, it may not
continue to appear in the Media view or in the backup job
defaults as Keep Data Infinitely - Do Not Allow Overwrite.
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.
385
Tape storage
Managing tapes
Note: Veritas recommends that if you need to keep data longer than four weeks,
you should duplicate it. You can duplicate the backup data from the original storage
device to tape, which you can then send for long-term or off-site storage.
To view all media sets
◆
On the Storage tab, double-click All Media Sets.
See “Overwrite protection periods and append periods in media sets” on page 386.
See “Creating media sets for tapes” on page 390.
See “Creating media vault rules to move tape media to and from media vaults”
on page 406.
See “Duplicating backup sets or a job history manually” on page 200.
See “Associating tape media with a media set” on page 411.
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.
386
Tape storage
Managing tapes
Table 11-4
Rule
Overwrite protection and append periods (continued)
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 396.
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 297.
The following graphic shows the relationship between the append period and the
overwrite protection period.
387
Tape storage
Managing tapes
Figure 11-1
Append periods and overwrite protection periods
R I T E P R OWT E C T I O N
P ERIO D
TIME
OVER
A PPE N D PERI OD
TIME
The append period begins when the media is allocated to a
media set.
The overwrite protection period is
measured from the time of the last
write to the media.
During the append period, data
can be added to the media. Any
data already on the media is
protected against loss.
The append period ends.
After the append
period expires, and
while the overwrite
protection period is
still active, data
cannot be added to
the media. Any data
already on the
media is protected
against loss.
The media
cannot be
Overwritten
by another
job during
this interval.
(However,
you could
erase the
media or
associate it
with scratch
media.)
The overwrite protection period
expires.
New
data
TIME
After the overwrite protection
period expires, the media
becomes recyclable. This
means that new data can be
written to the beginning of the
media by a new backup job
(causing loss of the original
data).
Old
data
The append and overwrite protection periods that you specify apply to all the data
on the media.
388
Tape storage
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.
How overwrite protection periods are reset
Figure 11-2
Time in
days
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Append period = 5
days
Normal Bkup
Protection
period 14
days
The media can be
overwritten at this time
First Day
Time in
days
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Append period = 5
days
Normal Bkup
Normal Bkup 1
Protection
period 14
days
The media can be
overwritten at this time
Second Day
Time in
days
Append period = 5
days
Normal Bkup
1
Normal Bkup 1
2
Normal Bkup 1 2
3
Normal Bkup 1 2 3
4
Normal Bkup 1 2 3 4
5
6
7
Protection
8
period 14
9
days
10
11
12
13
14
15
16
Fifth Day
17
18
19
The media can be
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.
389
Tape storage
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 382.
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:
■
■
■
To create the media set
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.
Click Finish.
Editing media set properties
You can edit the following properties for media sets:
390
Tape storage
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 382.
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.
391
Tape storage
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 386.
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.
392
Tape storage
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 404.
6
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.
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 386.
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:
393
Tape storage
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.
394
Tape storage
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 404.
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:
6
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.
Click Apply.
395
Tape storage
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 382.
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 382.
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.
396
Tape storage
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 386.
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 382.
See “Deleting tape media” on page 409.
See “Editing global settings for storage” on page 438.
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.
397
Tape storage
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: Veritas recommends that you physically write-protect media containing
critical data. Use the write-protect tab on the media cartridge to protect against
unintentional move or erase operations, or expired overwrite protection periods.
The following table describes the order in which Backup Exec searches for media
to use for an overwrite job.
Table 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
overwriting media.
3
Recyclable media in any media set
1
Recyclable media in the destination media set
2
Scratch media
3
Recyclable media in any media set
1
Scratch media
2
Recyclable media in the destination media set
3
Recyclable media in any media set
4
Media that is imported from another installation
of Backup Exec, or from another product
Full + Overwrite recyclable media
first
Partial + Overwrite scratch media
first
398
Tape storage
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
first
None - No overwrite protection +
overwrite scratch media first
Warning: This options is not
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
1
Scratch media
2
Recyclable media in the destination media set
3
Recyclable media in any media set
recommended because it does not
protect data from being overwritten. 4
None - No overwrite protection +
overwrite recyclable media first
Warning: This options is not
Recyclable media in the destination media set
Media that is imported from another installation
of Backup Exec, or from another product
5
Allocated media in any media set
1
Recyclable media in the destination media set
2
Scratch media
3
Recyclable media in any media set
recommended because it does not
protect data from being overwritten. 4
5
Media that is imported from another installation
of Backup Exec, or from another product
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 438.
See “Default media vaults” on page 404.
399
Tape storage
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 382.
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
Restore tab or the Storage tab
Do the following in the order listed:
■
■
On the Backup and Restore tab or the
Storage tab, double-click the server or
the storage device where the job ran.
In the left pane, click Job History.
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.
400
Tape storage
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
2
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.
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 450.
401
Tape storage
Labeling tape media
See “Renaming a tape media label ” on page 403.
See “How barcode labels become media labels for tapes” on page 402.
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 409.
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 400.
See “Scanning a storage device” on page 451.
402
Tape storage
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 400.
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.
403
Tape storage
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 455.
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 535.
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.
404
Tape storage
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 406.
See “Changing the name or description of a media vault” on page 405.
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 404.
To change media vaults and media vault rules, edit the properties of the media set
that is associated with the media vault.
405
Tape storage
Default media vaults
See “Editing media set properties” on page 390.
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 405.
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 404.
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 407.
406
Tape storage
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 404.
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 404.
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.
407
Tape storage
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 404.
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 409.
See “Media Errors report” on page 692.
408
Tape storage
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 408.
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.
409
Tape storage
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.
410
Tape storage
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 431.
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 603.
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:
411
Tape storage
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 390.
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 382.
Editing tape media properties
You can view tape media properties and edit some properties.
See “Managing tapes” on page 382.
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.
412
Tape storage
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.
413
Tape storage
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
Mon
Media 1
Son backup strategy
Tue
Wed
Thu
Media 1
Media 1
Media 1
Fri
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.
414
Tape storage
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
Mon
Tue
Father/Son backup strategy
Wed
Thu
Fri
Media 1
Media 2
Media 3
Media 4
Media 5
Media 1
Media 2
Media 3
Media 4
Media 6
Week 1
Week 2
Full Backup
Incremental or Differential
Backup
Grandfather media rotation strategy
The Grandfather media rotation strategy requires the following:
415
Tape storage
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.
416
Tape storage
Tape media rotation strategies
Grandfather backup strategy
Figure 11-5
Mon
Tue
Wed
Thu
Fri
Mon 1
Tue 2
Wed 3
Thu 4
Fri 5
Mon 1
Tue 2
Wed 3
Thu 4
Fri 6
Mon 1
Tue 2
Wed 3
Thu 4
Fri 7
Week 1
Week 2
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.
417
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
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 421.
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.
419
Storage device pools
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
installed
Select Storage pools, and then click Next.
If the Central Admin Server feature is
installed
Do the following in the order listed:
■
■
Select the Backup Exec server that you
want to configure storage for, and then
click Next.
Select Storage pools, and then click
Next.
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:
■
■
■
To configure the storage device pool
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.
Click Finish.
See “Adding or removing devices in a storage device pool ” on page 422.
See “How to use Backup Exec server pools in CAS ” on page 1204.
See “Adding or removing devices in a storage device pool ” on page 422.
See “Error-handling rules for failed or canceled jobs” on page 252.
420
Storage device pools
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:\Program Files\Veritas\Backup Exec
See “Creating storage device pools” on page 418.
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 233.
See “Alerts and notifications in Backup Exec” on page 266.
421
Storage device pools
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 418.
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 421.
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
To remove a storage device from a pool
5
Click Apply.
Do the following in the order listed:
■
Click Add.
■
Select the devices that you want to add,
and then click OK.
Select the device that you want to remove,
and then click Remove.
422
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
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
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 431.
See “Sending a notification when a scheduled storage operation job completes”
on page 431.
424
Storage operations
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 430.
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 115.
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 449.
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 474.
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.
425
Storage operations
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 266.
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 295.
426
Storage operations
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 301.
See “Editing disk cartridge properties” on page 309.
See “How Backup Exec catalogs work” on page 226.
See “Inventorying a storage device” on page 452.
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.
427
Storage operations
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.
428
Storage operations
Using the Configure Storage wizard
Storage that you can configure in the Configure Storage wizard
Table 13-2
Type of
storage
Description
Disk-based
storage
Storage that remains attached to the server.
Types of disk-based storage include the following:
■
■
■
Network
storage
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 297.
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 308.
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 845.
Network storage includes the following:
■
■
■
■
NDMP servers
Network attached storage (NAS) that supports the Network Data
Management Protocol to allow the use of devices that are attached to
the servers.
See “Features of the NDMP feature” on page 1239.
OpenStorage devices
Network-attached storage that supports Veritas's OpenStorage
technology.
See “Configuring an OpenStorage device” on page 839.
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 1291.
429
Storage operations
Viewing details for multiple storage devices
Storage that you can configure in the Configure Storage wizard
(continued)
Table 13-2
Type of
storage
Description
Tape storage
Tape storage includes the following:
■
■
■
Storage pools
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 361.
Robotic libraries
Storage that contains tape drives, slots, and an automated method for
loading tapes.
See “Robotic libraries in Backup Exec” on page 369.
Barcode rules
See “Configuring barcode rules for a robotic library ” on page 371.
Storage pools include the following:
■
Storage device pools
■
Managed Backup Exec server pools
See “Creating storage device pools” on page 418.
Media sets
and vaults
Media sets and vaults are for tape media only, and include the following:
■
Append period
■
Overwrite protection period
■
Vaulting rules
You can also run wizards to update media vaults.
See “Managing tapes” on page 382.
See “About storage operation jobs” on page 424.
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 425.
430
Storage operations
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 424.
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 424.
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 431.
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 424.
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.
431
Storage operations
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:
■
■
■
Days
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.
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.
432
Storage operations
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.
433
Storage operations
Scheduling a storage operation job
Months
434
Storage operations
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.
435
Storage operations
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:
■
■
■
at
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.
Designate the starting time for the first job
in the recurrence pattern.
436
Storage operations
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
hours after it scheduled start time
Specify the amount of time after the job's
scheduled start time at which you want to
cancel the job if it is still running. Backup
Exec changes the job completion status to
Canceled, timed out.
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
this job
Specify dates to exclude from the job
schedule. The job does not run on any of
the dates that you select using this option.
It resumes its normal schedule on the next
day that a job is scheduled after an
excluded date.
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.
437
Storage operations
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.
438
Storage operations
Editing global settings for storage
Full - protect allocated and imported
media
Select this option to prevent Backup Exec
from overwriting tape media that are in
media sets and the media that are imported
from another installation of Backup Exec
or from another product.
See “Overwrite protection periods and
append periods in media sets” on page 386.
This is the safest option to choose because
the tape media that is protected cannot be
overwritten until one of the following
actions occur:
■
■
■
■
Partial - protect only allocated media
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.
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.
Veritas recommends this option if you want
to use media from another installation of
Backup Exec or from another product
This option is enabled by default.
Prompt before overwriting imported
media
Select this option to be prompted before
Backup Exec overwrites tape media that
is imported from another installation of
Backup Exec or from another product. You
must select the option Partial - protect
only allocated media.
The job cannot run until you respond to
this prompt.
439
Storage operations
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, Veritas 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.
440
Storage operations
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 397.
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.
441
Storage operations
Editing global settings for storage
Overwrite recyclable media contained
in the targeted media set before
overwriting scratch media
Select this option to let Backup Exec
overwrite recyclable media in a tape drive
in the selected media set first when an
overwrite job occurs.
If no recyclable media are found in any of
the tape drives, Backup Exec overwrites
scratch media.
If no recyclable media or scratch media
are found, Backup Exec searches for
media to overwrite. The media that is
overwritten depends on the level of the
overwrite protection that you set.
See “How Backup Exec searches for
overwritable media in tape drives ”
on page 397.
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.
442
Storage operations
Editing global settings for storage
Limit Backup Exec to read-only
operations on a disk-based storage
device if it has been detached for
Select this option to prevent Backup Exec
from reclaiming disk space from expired
backup sets on any disk-based storage
device that is attached after being absent
for a number of days. Backup jobs that you
send to this device fail. You can change
this setting per disk-based storage device
in the device's properties.
Before you disable this setting, you may
want to view the expiration dates of the
backup sets and decide if you want to keep
some backup sets longer. You can change
the expiration date of a backup set, or you
can retain a backup set indefinitely.
See “Editing disk storage properties”
on page 301.
See “Backup sets ” on page 321.
See “How to restore data from a reattached
or reinserted disk-based storage device”
on page 307.
See “How data lifecycle management
(DLM) deletes expired backup sets on
disk-based storage” on page 315.
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.
443
Storage operations
Editing global settings for storage
Limit Backup Exec to read-only
operations on a disk cartridge if it has
not been inserted for
Prevents Backup Exec from reclaiming disk
space from expired backup sets on any
disk cartridge that is inserted after being
absent for a number of days. Backup jobs
that you send to this device fail. You can
change this setting per disk cartridge in the
device's properties.
Before you disable this setting, you may
want to view the expiration dates of the
backup sets and decide if you want to keep
some backup sets longer. You can change
the expiration date of a backup set, or you
can retain a backup set indefinitely.
See “Editing disk cartridge properties”
on page 309.
See “Backup sets ” on page 321.
See “How to restore data from a reattached
or reinserted disk-based storage device”
on page 307.
See “How data lifecycle management
(DLM) deletes expired backup sets on
disk-based storage” on page 315.
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.
444
Storage operations
Editing global settings for storage
Allow Backup Exec to delete all expired
backup sets
445
Storage operations
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.
446
Storage operations
Sharing storage devices
See “Backup sets ” on page 321.
See “How data lifecycle management
(DLM) deletes expired backup sets on
disk-based storage” on page 315.
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
447
Storage operations
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.
448
Storage operations
Changing the state of a storage device to online
See “Disabling and enabling a storage device” on page 454.
See “Recreating a legacy backup-to-disk folder and its contents” on page 357.
See “Backup sets ” on page 321.
Changing the state of a storage device to online
Usually, when a device goes offline, an alert appears. The alert message provides
a specific reason why the device is offline, and may include a link to the Veritas
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 708.
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 424.
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.
449
Storage operations
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 424.
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 244.
See “How to monitor and manage jobs in Backup Exec” on page 233.
See “About the Job Monitor” on page 235.
See “Alerts and notifications in Backup Exec” on page 266.
See “Backup sets ” on page 321.
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. Veritas
recommends that you encrypt data instead.
See “Using encryption with Backup Exec” on page 600.
See “Inventorying and cataloging a storage device” on page 453.
See “How Backup Exec catalogs work” on page 226.
450
Storage operations
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 450.
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 424.
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.
451
Storage operations
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 431.
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 450.
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.
452
Storage operations
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 431.
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 450.
See “Inventorying robotic libraries when Backup Exec services start” on page 371.
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 424.
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 450.
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 424.
453
Storage operations
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 450.
454
Storage operations
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 403.
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 424.
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 450.
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.
455
Storage operations
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 424.
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 450.
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 424.
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.
456
Storage operations
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 431.
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 450.
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 424.
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 376.
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.
457
Storage operations
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 431.
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 450.
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 382.
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.
458
Storage operations
Importing media to Backup Exec
See “Scanning a storage device” on page 451.
To import media now
1
2
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.
(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:
4
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.
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.
459
Storage operations
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:
■
■
■
Days
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.
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.
460
Storage operations
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.
461
Storage operations
Importing media to Backup Exec
Months
462
Storage operations
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.
463
Storage operations
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
start x hours after its scheduled
start
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.
464
Storage operations
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
of this job
Specify dates to include with the job schedule.
The job runs on all of the dates that you select
using this option, in addition to the dates that are
part of its normal schedule recurrence. The job
resumes its normal schedule on the next day that
it is scheduled after an include date.
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
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.
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 450.
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
465
Storage operations
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 458.
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.
466
Storage operations
Exporting media and expired media
■
2
Right-click the robotic library, and then click Export.
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.
3
To immediately export the media to the
portal
Click Export media now.
To immediately import media after the
export
Click Import after export.
The operation runs. You can view the job
history for details about the job.
The operation runs. You can view the job
history for details about the job.
(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 450.
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.
467
Storage operations
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.
468
Storage operations
Locking and unlocking the robotic library’s front portal
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:
5
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.
To schedule the job, in the left pane, click Schedule and select the appropriate
options.
Recurrence
Specify a recurrence schedule for the job.
469
Storage operations
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:
■
■
■
Days
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.
Create a recurrence pattern that is measured in
days.
When you select Days, you must choose
between the following options:
■
■
Weeks
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.
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.
470
Storage operations
Locking and unlocking the robotic library’s front portal
Months
471
Storage operations
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.
472
Storage operations
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
start x hours after its scheduled
start
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.
473
Storage operations
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
of this job
Specify dates to include with the job schedule.
The job runs on all of the dates that you select
using this option, in addition to the dates that are
part of its normal schedule recurrence. The job
resumes its normal schedule on the next day that
it is scheduled after an include date.
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
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.
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 450.
Backup Exec server and storage device states
Backup Exec servers and storage devices display a state that indicates their current
condition.
474
Storage operations
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
restarted on <Backup Exec server>
The Backup Exec services and the Backup
Exec deduplication services must be
restarted.
See “Starting and stopping Backup Exec
services” on page 642.
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 642.
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 1198.
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.
475
Storage operations
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, and
may include a link to the Veritas 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 449.
Online
The storage device is online.
Paused
The storage device is paused.
See “Pausing and unpausing a storage
device” on page 453.
Paused; Active
The storage device is paused, but is currently
in use by a job.
476
Storage operations
Backup Exec server and storage device states
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 1198.
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 642.
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 642.
This device has not been discovered
correctly. Cycle the services on <Backup
Exec server> to retry device discovery.
A state that can occur after you add a new
storage device to Backup Exec. You must
restart the Backup Exec services so that the
device discovery process can run again.
Uninitialized
The device has not been initialized.
477
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
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:
479
Conversion to virtual machines
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
Convert to Virtual Machine
These options run the conversion
simultaneously with the backup job. Because
two operations are performed at the same
time, this job may take longer to run than a
regular backup job. A large backup window
is recommended for this option.
Back up to Deduplication Disk Storage
and Simultaneously 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.
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 487.
480
Conversion to virtual machines
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
Virtual Machine
These options let you schedule the
conversion to run after the backup job. These
options require a smaller backup window than
the simultaneous conversion options.
Back Up to Deduplication Disk Storage
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 494.
Convert to Virtual Machine from
Point-in-Time
A conversion to a virtual machine from a point
in time converts existing backup sets from a
backup job in which all components that are
necessary for a virtual machine conversion
were selected. When all necessary
components are selected for a backup job,
Backup Exec identifies that job as Fully
selected and the Simplified Disaster
Recovery option has a status of ON. The
option to convert to a virtual machine from a
point in time is useful in a disaster recovery
situation in which you want to quickly recover
a failed server. The backup sets contain all
of the critical components of the server.
Additionally, you can select application data
or user data to include in the conversion.
Note: The option Convert from
Point-in-Time becomes available for
selection only after you run at least one full
backup that includes all critical system
components.
See “Converting to a virtual machine from a
point in time” on page 509.
481
Conversion to virtual machines
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 511.
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 502.
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.
482
Conversion to virtual machines
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.
483
Conversion to virtual machines
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.
484
Conversion to virtual machines
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
485
Conversion to virtual machines
Requirements for conversion to virtual machine jobs
■
MSExchangeServiceHost
■
MSExchangeThrottling
■
MSExchangeTransport
■
MSExchangeTransportLogSearch
■
MSExchangeUM
■
MSExchangeUMCR
See “Requirements for conversion to virtual machine jobs” on page 486.
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.
486
Conversion to virtual machines
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 478.
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:
487
Conversion to virtual machines
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.
■
To change the backup options
Click OK.
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:
488
Conversion to virtual machines
Converting to a virtual machine simultaneously with a backup job
If you selected Hyper-V in step 5
489
Conversion to virtual machines
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
490
Conversion to virtual machines
Converting to a virtual machine simultaneously with a backup job
configuration, and then enter the new
information.
491
Conversion to virtual machines
Converting to a virtual machine simultaneously with a backup job
If you selected VMware ESX/vCenter
server in step 5
492
Conversion to virtual machines
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.
493
Conversion to virtual machines
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 478.
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:
494
Conversion to virtual machines
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.
■
To change the backup options
Click OK.
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
specific time
Do the following:
■
Select According to schedule.
■
Click the arrow in the Source field to
select either all backups or the most
recent full backup as the source to
initiate the conversion.
Select Recurrence, and then click the
arrow to set the recurrence pattern.
■
To create the conversion job without
scheduling it
Do the following:
■
Select According to schedule.
■
Click the arrow in the Source field to
select either all backups or the most
recent full backup as the source to
initiate the conversion.
Select Create without a schedule.
When you use this option, the job does
not run at the time of creation and it
does not have a recurring schedule.
The job remains in a pending state until
you choose to run it. You can use a
third-party job automation or task
scheduling tool to run the job later.
■
To run the conversion immediately after
the backup job completes
Select Convert to virtual immediately
after source task completes.
495
Conversion to virtual machines
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:
496
Conversion to virtual machines
Converting to a virtual machine after a backup job
If you selected Hyper-V in step 8
497
Conversion to virtual machines
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
498
Conversion to virtual machines
Converting to a virtual machine after a backup job
configuration, and then enter the new
information.
499
Conversion to virtual machines
Converting to a virtual machine after a backup job
If you selected VMware ESX/vCenter
server in step 8
500
Conversion to virtual machines
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.
501
Conversion to virtual machines
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 478.
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.
502
Conversion to virtual machines
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:
503
Conversion to virtual machines
Adding a conversion to virtual machine stage to a backup job
If you selected Hyper-V in step 7
504
Conversion to virtual machines
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
505
Conversion to virtual machines
Adding a conversion to virtual machine stage to a backup job
configuration, and then enter the new
information.
506
Conversion to virtual machines
Adding a conversion to virtual machine stage to a backup job
If you selected VMware ESX/vCenter
server in step 7
507
Conversion to virtual machines
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.
508
Conversion to virtual machines
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.
■
■
9
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.
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 478.
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.
509
Conversion to virtual machines
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
specific time
Click Run on, and then enter the date and
time to run the job.
To create the conversion job without
scheduling it
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.
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.
510
Conversion to virtual machines
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
specific time
Click Run on, and then enter the date and
time to run the job.
To create the conversion job without
scheduling it
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.
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.
511
Conversion to virtual machines
Creating a one-time conversion to a virtual machine
8
Configure the conversion options:
512
Conversion to virtual machines
Creating a one-time conversion to a virtual machine
If you selected Hyper-V in step 7
513
Conversion to virtual machines
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
514
Conversion to virtual machines
Creating a one-time conversion to a virtual machine
configuration, and then enter the new
information.
515
Conversion to virtual machines
Creating a one-time conversion to a virtual machine
If you selected VMware ESX/vCenter
server in step 7
516
Conversion to virtual machines
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.
517
Conversion to virtual machines
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.
■
■
9
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.
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 478.
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:
518
Conversion to virtual machines
Setting default options for conversion to virtual machine jobs
To schedule conversion to virtual jobs to
run at a specific time
Do the following:
■
Select According to schedule.
■
Click the arrow in the Source field to
select either all backups or the most
recent full backup as the source to
initiate the conversion.
Select 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.
■
■
To run the conversion immediately after
the backup job completes
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.
Select Convert to virtual immediately
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:
519
Conversion to virtual machines
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.
520
Conversion to virtual machines
Setting default options for conversion to virtual machine jobs
If you selected VMware ESX/vCenter
server in step 6
Do the following to configure the
conversion options:
■
■
■
■
Click the arrow in the ESX/vCenter
server name field, and click the name
of the server where you want to create
the virtual machines.
Click the arrow in the Logon account
field, and then select the appropriate
logon account for the server that you
selected.
If you want to enable Backup Exec to
overwrite a virtual machine if a virtual
machine with the same name already
exists, verify that the Overwrite the
virtual machine if it already exists
option is selected. If this option is not
selected and the virtual machine name
already exists, then the job fails.
In the Full path of VMware Tools ISO
image field, enter the location of your
VMware Tools ISO image. The path
should be accessible with the default
credentials. The path should also be
local to the Backup Exec server. The
ISO image is needed to make the
virtual machine bootable.
Note: In a CAS environment, this path
should be local to the managed Backup
Exec server to which the job is targeted.
8
Click OK
521
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
■
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
523
Configuration and settings
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
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.
524
Configuration and settings
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 528.
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 535.
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 285.
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 541.
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 542.
525
Configuration and settings
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 544.
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 551.
See “Configuring checkpoint restart” on page 553.
Advanced Disk-based
Backup
Select this option to configure off-host backup
processing for backup jobs.
See “Setting default backup options for the Advanced
Disk-based Backup feature” on page 1226.
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 556.
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 560.
Enterprise Vault
Select this option to configure Enterprise Vault options
for backup jobs.
See “Enterprise Vault backup options” on page 1116.
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 1274.
526
Configuration and settings
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 1156.
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 1033.
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 881.
See “Setting default backup options for Hyper-V”
on page 933.
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 1054.
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 985.
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 1243.
Oracle
Select this option to configure options for any Oracle
data that is included in backup jobs.
See “Oracle backup options” on page 1090.
Exclusions
Select this option to exclude specific files or specific
types of files from backup jobs.
See “Excluding files from backups” on page 158.
4
Select the appropriate options.
5
When you are finished configuring default options, click OK.
527
Configuration and settings
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 194.
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 ■
settings for all backup jobs
■
To configure a schedule for
specific 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 schedule
settings.
Create a new backup definition or edit an existing
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.
528
Configuration and settings
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
To configure jobs to run
immediately without any
recurrences
Complete the following steps:
■
Select Recurrence.
■
Proceed to step 6 to configure the recurrence
pattern.
Complete the following steps:
■
Select Run now with no recurring schedule.
■
Proceed to step 9.
Note: This option is only available for full backup jobs.
To configure a job without a
schedule
Complete the following steps:
■
Select Create without a schedule.
■
Proceed to step 10.
When you use this option, the jobs do not run at the
time of creation and they do not have a recurring
schedule. The jobs remain unscheduled until you choose
to run them. You can use a third-party job automation
or task scheduling tool to run the jobs later.
You can run unscheduled backup jobs later by using
the Run Next Backup Now option or you can manually
run the job by using the Run Now option.
If you use this option to create a job, you cannot place
the job on hold. You cannot place jobs on hold unless
they are scheduled.
6
To configure the recurrence pattern, complete the following options:
529
Configuration and settings
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:
■
■
Days
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.
Select this option to create a recurrence pattern that is
measured in days.
When you select Days, you must choose between the
following options:
■
■
Weeks
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.
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.
530
Configuration and settings
Configuring schedules for backup jobs
Months
531
Configuration and settings
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.
532
Configuration and settings
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.
533
Configuration and settings
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 257.
Cancel the job if it is
running X hours after its
scheduled start time
Specify the amount of time after the job's scheduled
start time at which you want to cancel the job if it is still
running. Backup Exec changes the job completion status
to Canceled, timed out.
See “List of job statuses in Backup Exec” on page 257.
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 196.
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 197.
534
Configuration and settings
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 524.
See “Backing up data” on page 139.
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
options for all backup jobs
Complete the following steps:
■
■
Click the Backup Exec button, and then select
Configuration and Settings.
Select Job Defaults, and then select the type of
backup for which you want to configure storage
options.
To configure 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.
535
Configuration and settings
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 242.
Backup Exec server or
Backup Exec server pool
Select whether you want a job to run on devices on a
specific managed Backup Exec server or on devices
that are on a group of managed Backup Exec servers.
This option displays only if you have the Central Admin
Server 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 418.
See “About the Remote Media Agent for Linux ”
on page 1291.
See “Features and types of disk-based storage and
network-based storage” on page 293.
536
Configuration and settings
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
computer to directly access
the storage device and to
perform client-side
deduplication, if it is
supported
Select this option to enable a remote computer to send
data directly to an OpenStorage device or a
deduplication disk storage device, and to perform
client-side deduplication if the device supports it. The
Backup Exec server is bypassed, which leaves the
Backup Exec server free to perform other operations.
If client-side deduplication cannot be performed, then
either Backup Exec server deduplication or Appliance
deduplication is performed.
This option appears if the Deduplication 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 857.
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
Select this option to enable a remote computer to send
data through the Backup Exec server to an OpenStorage
device or a deduplication disk storage device, and to
perform Backup Exec server-side deduplication if it it
supported. If the Backup Exec server does not support
deduplication, the data is deduplicated on an intelligent
disk device, such as Veritas 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 828.
5
In the Keep for field, enter the amount of time for which you want to keep the
backup sets or job history.
6
If you selected to configure a tape device in the Storage field, complete the
following options as necessary:
537
Configuration and settings
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 382.
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 382.
See “Media overwrite protection levels for tape media”
on page 396.
See “How Backup Exec searches for overwritable media
in tape drives ” on page 397.
538
Configuration and settings
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
completes
Select this option to eject the media from the drive or
slot when the operation completes. You can also
schedule a job to eject media.
This option is available only if you selected a tape device
in the Storage field.
See “Ejecting media from a disk cartridge or tape drive”
on page 456.
Retension media before
backup
Select this option to run the tape in the drive from
beginning to end at a fast speed. Retensioning helps
the tape wind evenly and run more smoothly past the
tape drive heads. This option is available only if you
select a tape drive that supports retensioning.
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 403.
539
Configuration and settings
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 404.
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,
otherwise none)
Select this option to use hardware data compression if
the storage device supports it. If the drive does not
feature data compression, the data is backed up
uncompressed.
Hardware (if available,
otherwise software)
Select this option to use hardware data compression if
the storage device supports it. If the drive does not
feature hardware data compression, STAC software
compression is used.
540
Configuration and settings
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 600.
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 603.
9
Click OK.
See “Changing default backup job settings” on page 524.
See “Backing up data” on page 139.
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.
541
Configuration and settings
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 706.
You can manually run a test run job at any time.
See “Running a test run job manually” on page 205.
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
default for all backup jobs
Complete the following steps:
■
■
To enable a test run job for
specific 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.
Complete the following steps:
■
■
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 524.
See “Backing up data” on page 139.
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. Veritas recommends that you verify
542
Configuration and settings
Configuring automatic verify operations for backup jobs
all 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 206.
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.
543
Configuration and settings
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
separate job
Select this option to create a verify operation and
schedule it to run as a separate job when the backup
job is completed.
You can use the Edit option to configure options for the
separate verify job.
As a separate scheduled
job
Select this option to create a verify operation and
schedule it to run as a separate job at a later time.
You can use the Edit option to configure options for the
separate verify job.
Do not verify data for this
job
Select this option to disable the verify operation for the
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 524.
See “Backing up data” on page 139.
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 226.
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.
544
Configuration and settings
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 545.
See the section called “Instant GRT” on page 546.
See the section called “Differences between Instant GRT and full catalog”
on page 547.
See “To configure an Instant GRT or a full catalog operation” on page 548.
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 608.
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.)
545
Configuration and settings
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.
546
Configuration and settings
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.
Veritas recommends to 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 597.
See “Backup Exec listening ports” on page 599.
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
the Search wizard
Not available.
You can search the backup
sets for granular data.
Backup sets browse
You can dynamically browse
the backup sets to select the
individual items that you want
to restore.
You can search as well as
browse the backup sets to
select the individual items that
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
because the cataloging
happens as part of the
backup job. Backup Exec
collects only the minimum
required catalog information.
Catalog file size
Smaller file size because only Large file size because the
the minimum required data is complete backup set is
cataloged.
cataloged.
The catalog operation runs as
a separate job. It consumes
time because Backup Exec
collects detailed cataloging
information for the backup
job.
547
Configuration and settings
Configuring Instant GRT and full catalog options to improve backup performance for GRT-enabled jobs
Table 15-1
Item
Differences between Instant GRT and full catalog (continued)
Instant GRT
Time to browse granular data Slightly longer than the time
for granular restore
taken for browsing data when
you do a full catalog because
Backup Exec dynamically
browses the backup set for
reading the GRT data when
you expand backup sets to
restore granular items.
Full catalog
Less than the time taken for
browsing data when you do
an Instant GRT because the
GRT information is already
available in the detailed
catalog collected during the
full catalog job.
The restore time is the same
as for a full-cataloged backup
set.
Device busy time
The device is not busy for a
long time because the catalog
is not detailed and it also runs
as part of the backup job.
The device is busy for a long
time. First when the backup
happens, and then when the
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
full catalog options for all
backup jobs
Complete the following steps:
■
■
Click the Backup Exec button, and then select
Configuration and Settings.
Select Job Defaults, and then select the type of
backup for which you want to configure 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.
548
Configuration and settings
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.
To know more about the various scenarios and the
possible changes to your existing jobs, see
https://www.veritas.com/support/en_US/article.000115907.
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.
549
Configuration and settings
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 524.
See “Backing up data” on page 139.
See “How cataloging works with Hyper-V virtual machine backups” on page 939.
See “How cataloging works with VMware virtual machine backups” on page 889.
550
Configuration and settings
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.
551
Configuration and settings
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.
552
Configuration and settings
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 553.
4
Click OK.
See “Changing default backup job settings” on page 524.
See “Backing up data” on page 139.
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.
553
Configuration and settings
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 551.
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 177.
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.
554
Configuration and settings
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:
6
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.
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.
555
Configuration and settings
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.
556
Configuration and settings
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
commands for specific
backup jobs
Complete the following steps:
■
■
2
Create a new backup definition or edit an existing
backup definition.
In the Backup box, click Edit.
In the left pane, click Pre/Post Commands.
557
Configuration and settings
Configuring pre/post commands for backup jobs
3
Complete the following options:
Type a command to run
before the backup runs
Runs a command on the specified server before the
backup job runs. Use local paths, and make sure that
the paths exist on each server and are correct.
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
after the backup runs
Runs a command on the specified server after the
backup job runs. Use local paths, and make sure that
the paths exist on each server and are correct.
Commands that require user interaction, such as
prompts, are not supported.
Run post-command after
job verification completes
Runs the post-command after the verification completes,
if you configured a verify operation for the job.
See “Configuring automatic verify operations for backup
jobs” on page 542.
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.
558
Configuration and settings
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
exit codes of the
commands to determine if
the commands completed
successfully
Lets Backup Exec check the return codes of the preand post-commands to determine if they completed
successfully.
Backup Exec interprets an exit code of zero from either
the pre- or post-command to mean that the command
completed successfully. Backup Exec interprets a
non-zero code to mean that the command ended with
an error.
After Backup Exec checks the return codes, it continues
processing according to the selections you made for
running the pre- and post-commands.
If this option is not selected, the success of the pre- and
post-commands is not determined based on the return
code.
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 preand 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 524.
See “Backing up data” on page 139.
559
Configuration and settings
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
folder options for all backup
jobs
Complete the following steps:
■
■
To configure file and folder
settings for specific 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 file
and folder settings.
Complete the following steps:
■
■
Create a new backup definition or edit an existing
backup definition.
In the Backup box, click Edit.
2
In the left pane, click Files and Folders.
3
Complete the following options:
560
Configuration and settings
Configuring file and folder options for backup jobs
Backup method for files
561
Configuration and settings
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
562
Configuration and settings
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 177.
563
Configuration and settings
Configuring file and folder options for backup jobs
Enable single instance
backup for NTFS volumes
Select this option if you want Backup Exec to check the
NTFS volume for identical files. If Backup Exec finds
multiple copies of a file, it backs up only one instance
of that file.
Single instance backup can considerably reduce the
storage space that is required for your backups. Many
applications automatically generate some files that have
identical content. The actual amount of space that you
save depends on the number of duplicate files on the
volume.
This option displays only if you use the Microsoft
Windows Single Instance Store (SIS) feature.
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.
564
Configuration and settings
Configuring file and folder options for backup jobs
Back up files and
directories by following
junction points and mount
points
Select this option to back up the information for the
junction points and the files and directories to which
they are linked. If this check box is not selected, then
only the information for the junction points is backed up.
The files and directories to which the junction points are
linked are not backed up.
Backup Exec does not follow junction points that are
automatically created by Microsoft Windows because
it can cause the data to be backed up repeatedly.
You cannot select any mounted drives that do not have
a drive letter assigned to them. The files and directories
to which they are linked are backed up regardless of
whether this option is selected.
If the files and directories to which the junction points
are linked are also included in the backup selections,
then they are backed up twice. They are backed up
once during the full file and directory backup job, and
again by the junction point.
Warning: If a junction point is linked to a location that
encompasses it, then recursion (a situation where data
is backed up repeatedly) occurs. Recursion results in
an error and a job failure. For example, if c:\junctionpoint
is linked to c:\, recursion occurs when Backup Exec
attempts to back up c:\junctionpoint, and the backup job
fails.
Back up files and
directories by following
symbolic links
Select this option to back up the information for any
symbolic links and the files and directories to which they
are linked.
If you do not select this option, only the information for
the symbolic links is backed up. The files and directories
to which they are linked are not backed up.
If the symbolic link points to files and directories on a
remote computer, the files and directories on the remote
computer are not backed up.
565
Configuration and settings
Configuring file and folder options for backup jobs
Back up data in Remote
Storage
Select this option to back up any data that has been
migrated from primary storage to secondary storage.
The data is not recalled to its original location. It is
backed up directly to the backup media.
If this option is selected, you should not run a backup
of your entire system. Backup Exec has to load the data
that has been migrated to secondary storage and
additional time is required for migrated data.
If this check box is cleared, only the placeholder that
stores the location of the data on secondary storage is
backed up, not the data itself.
This option should not be selected if the device used
for secondary storage and backups contains only one
drive. If there is only one drive, Remote Storage and
Backup Exec compete for use of the drive.
566
Configuration and settings
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 167.
567
Configuration and settings
Setting default schedule options for rule-based jobs and run now jobs
Delete selected files and
folders after successful
backup
Select this option if you want Backup Exec to delete the
data you selected to back up after the backup job
completes successfully.
Backup Exec backs up the selected data, verifies the
backup sets, and then deletes the data from the server.
The logon account credentials that you use to run the
job must also have the rights to delete a file. Otherwise,
the data is backed up, but it is not deleted.
Note: This option is only available when you configure
backup jobs. You cannot configure it as a default setting
for all backup jobs.
See “Configuring Backup Exec to automatically delete
files after a backup” on page 181.
Preserve tree on back up
and delete
4
Select this option to retain the file system's directory
structure for the files that are backed up in a full backup
job. This option is available only when you select the
Delete selected files and folders after successful
backup option.
Click OK.
See “Changing default backup job settings” on page 524.
See “Backing up data” on page 139.
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.
568
Configuration and settings
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
minutes
Click Hours, and then enter the frequency in the Every
X hour/minute field.
Choose between the following options:
■
■
To run jobs every X days
Click Days, and then choose between the following
options:
■
■
To run jobs every X weeks
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.
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.
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.
569
Configuration and settings
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.
570
Configuration and settings
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 194.
See “List of job statuses in Backup Exec” on page 257.
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.
571
Configuration and settings
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 574.
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
calendar
Click the date that you want to exclude.
The calendar displays 3 months at a time. You can
navigate forward and backward to view additional
months by clicking the arrows.
Note: You can select only one date at a time.
To import a list of dates
Complete the following steps:
■
Click Browse.
■
Select the text file that contains the exclude dates.
■
Click Open.
■
Click Import.
572
Configuration and settings
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 571.
573
Configuration and settings
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 571.
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.
574
Configuration and settings
Configuring the default setting for backing up multiple servers or applications
3
Configure any of the following preferences:
Show splash screen at
startup
Clear this option to show the Backup Exec
Administration Console instead of the splash screen
when you start Backup Exec.
Display progress indicators
for backup jobs. This
requires additional time to
pre-scan resource.
Select this option to display the percentage complete
number while a backup job runs. These indicators
appear in the Job Activity dialog box, and they let you
monitor the progress of the active job. Backups might
take longer to complete when this option is selected
because the backup sources must be scanned to
determine the amount of data to be backed up.
Due to the amount of time that is required to scan the
backup sources, you should not select this option when
you back up remote resources.
Allow Backup Exec to
report anonymous usage
information (No personally
identifiable information will
be returned to Veritas).
Select this option to participate in the Veritas Backup
Exec product improvement program.
General Backup Exec usage and statistical information
is periodically collected and sent anonymously to
Veritas. Veritas uses the information to help improve
the Backup Exec customer experience.
Note: Although usage and statistical information is
collected, Veritas 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
4
Select this option to enable any messages that you have
disabled.
Click OK.
Configuring the default setting for backing up
multiple servers or applications
You can select to back up multiple servers or applications at once using Backup
Exec. You can back them up as part of one backup definition or you can back them
up individually in separate backup definitions. It may be easier for you to manage
575
Configuration and settings
Configuring database maintenance and security
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:
4
■
Create one backup that includes all servers or applications
■
Create separate backups for each server or application
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 139.
Configuring database maintenance and security
The Database Maintenance and Security option lets you manage the Backup Exec
Database. Each database maintenance operation is performed independently on
each database. The Backup Exec Database maintains a record of the files and
data that you have configured.
Database maintenance lets you perform the following:
■
Optimize database size.
■
Delete expired data.
■
Save the contents of the database files.
■
Perform a database consistency check.
Backup Exec generates informational alerts at the beginning and at the end of the
database maintenance process each time database maintenance is performed.
576
Configuration and settings
Configuring database maintenance and security
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.
577
Configuration and settings
Configuring database maintenance and security
4
Configure any of the following options:
Perform database
maintenance daily at
Select the time that you want to perform database
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
specified number of days
Select this option to indicate the number of days to keep
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 645.
578
Configuration and settings
Configuring database maintenance and security
Perform database
consistency check
Select this option to check the logical consistency and
physical consistency of the data in the database.
The option is not checked by default. Veritas
recommends 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.
579
Configuration and settings
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 580.
6
Path
Type the path of a secure location to which you want to
export the Backup Exec Database encryption key.
Remember the export path.
By clicking this check box,
you consent to let Backup
Exec retain and display the
export path during import
operations.
Select this option to let Backup Exec remember the path
to which you exported the database encryption key.
Export
Click this option to export the Backup Exec Database
encryption key to the location that you specified in the
Path field.
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.
Click OK.
See “Configuring encryption for the connection to the Backup Exec Database”
on page 583.
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
580
Configuration and settings
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
Veritas recommends that you export the Backup Exec Database encryption key to
a secure location so that you can access it later if it is needed. You should repeat
the following procedure on each Backup Exec server in your environment, including
the central administration server and each managed Backup Exec server in Central
Admin Server 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.
581
Configuration and settings
Refreshing Backup Exec Database encryption keys
See “Configuring database maintenance and security” on page 576.
See “Refreshing Backup Exec Database encryption keys” on page 582.
See “Configuring encryption for the connection to the Backup Exec Database”
on page 583.
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. Veritas recommends 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\Symantec\Backup Exec For
Windows\Backup Exec\Server\DatabaseEncryptionAction
582
Configuration and settings
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. Veritas
recommends that you export the new key to a secure location so that you can
access it later if it is needed.
See “Exporting the Backup Exec Database encryption key” on page 580.
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, Veritas recommends that you create and use
your own certificates for additional security.
583
Configuration and settings
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.
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. Veritas recommends that you use your own
certificates for improved security. Once you have generated and installed your
certificate, you can proceed to configure the secure SQL connection to the Backup
Exec Database.
Microsoft has requirements that must be followed when you use your own certificates
for SQL Server. Certificates can be either self-signed or issued from a certification
authority. Certification authorities can be either a local authority in your organization's
domain or a known third-party authority.
For more information about Microsoft's certification requirements, refer to the
following Microsoft article:
Encrypting Connections to SQL Server
Before you configure encryption, you must import the certificates that you want to
use into the local certificate store of the computer that hosts the Backup Exec
Database.
For more information about importing and installing a certificate on the server, refer
to the following Microsoft article:
How to: Enable Encrypted Connections to the Database Engine (SQL Server
Configuration Manager
When you import certificates, you should use the same user account under which
the SQL Server service runs:
■
If the SQL Server is running under a default computer account such as
LocalSystem, NetworkService, or LocalService, then you should use the
Computer account option when you import the certificate. Selecting to manage
certificates for the computer account ensures that the certificate is placed under
the Personal store of the default computer account.
584
Configuration and settings
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.
585
Configuration and settings
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:
586
Configuration and settings
Scheduling Backup Exec to check logon accounts
For clustered Backup Exec
environments
You must configure a secure SQL connection on each node
in the cluster.
If the cluster has not been created yet, configure the secure
SQL connection before you run the Cluster Configuration
Wizard in Backup Exec.
If the cluster has already been created:
■
■
■
For Central Admin Server
feature (CAS) environments
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.
You must configure a secure SQL connection on each
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.
587
Configuration and settings
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
sources in jobs can be
accessed with the logon
accounts you selected
Select this option to test whether Backup Exec can
access the backup sources in your backup jobs with the
logon accounts that 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 631.
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.
588
Configuration and settings
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 590.
■
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.
589
Configuration and settings
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.
590
Configuration and settings
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
Windows to the current version
automatically
Upgrades the Agent for Windows on the
server that you are adding to the list of
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 588.
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.
591
Configuration and settings
Backup networks
Example of backup network
Figure 15-1
backup network
network ID: 128.10.0.0
subnet mask: 255.255.0.0
Backup Exec server
IP address
128.10.0.3
IP address:
128.10.0.2
IP address:
10.67.0.2
IP address:
128.10.0.1
IP address:
10.67.0.1
IP address:
10.67.0.3
Database
server
Exchange server
router A
router B
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
592
Configuration and settings
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 593.
See “Configuring network options for backup jobs” on page 182.
See “Using Backup Exec with firewalls” on page 595.
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 182.
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:
593
Configuration and settings
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
network interface, subnet,
or protocol for Backup Exec
agents not bound to the
above network interface,
subnet, or protocol
Select this option to let Backup Exec use any available
network if the remote system that you selected for
backup or restore is not part of the specified backup
network.
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
shares
Select this option to include user-defined shares in jobs.
Enable TCP dynamic port
range
Lets Backup Exec agents use a range of ports for
communication.
If you do not select this option and the remote system
is not part of the specified backup network, the job fails.
Backup Exec cannot access the data from the remote
system.
If you do not select this option, you cannot select
user-defined shares when you create jobs.
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. Veritas recommends using a range
of 25 allocated ports for the remote system if you use
Backup Exec with a firewall.
See “Using Backup Exec with firewalls” on page 595.
594
Configuration and settings
Using Backup Exec with firewalls
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 1086.
Use FIPS 140-2 compliant
software encryption
Lets you enable software encryption that complies with
FIPS 140-2 standards. If you select this option, you must
use a 256-bit AES encryption key. This option is
available only for Windows computers.
You must stop and restart the Backup Exec services
for this change to take effect.
Manage Keys
4
Lets you create a new encryption key or manage
existing encryption keys.
Click OK.
See “Backup networks” on page 591.
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.
595
Configuration and settings
Using Backup Exec with firewalls
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.
Veritas recommends that you open port 10000 and make sure that it is available
on the Backup Exec server and any remote systems. In addition, you must open
the dynamic port ranges that Backup Exec uses for communications between the
Backup Exec server and Backup Exec agents.
When a Backup Exec server connects to a remote system, it initially uses port
10000. The agent listens for connections on this predefined port. The Backup Exec
server is bound to an available port, but additional connections to the agent are
initiated on any available port.
When you back up data, up to two ports may be required on the computer on which
the agent is installed. To support simultaneous jobs, you must configure your firewall
to allow a range of ports large enough to support the number of simultaneous
operations desired.
If there is a conflict, you can change the default port to an alternate port number
by modifying the %systemroot%\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.
When you set up TCP dynamic port ranges, Veritas recommends that you use a
range of 25 allocated ports for the remote computer. The number of ports that
remote computers require depends on the number of devices you protect and the
number of tape devices you use. You may need to increase these port ranges to
maintain the highest level of performance.
Unless you specify a range, Backup Exec uses the full range of dynamic ports
available. When performing remote backups through a firewall, you should select
a specific range on the Network and Security settings dialog box.
To browse systems through a firewall
1
Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2
In the left pane, select Network and Security.
596
Configuration and settings
Using Backup Exec with firewalls
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 597.
See “Backup Exec listening ports” on page 599.
See “About enabling a SQL instance behind a firewall” on page 600.
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 595.
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
(process=benetns.exe)
6101
TCP
Backup Exec Agent for Windows
(process=beremote.exe)
10000
TCP
Backup Exec server
(process=beserver.exe)
3527, 6106
TCP
597
Configuration and settings
Using Backup Exec with firewalls
Table 15-2
Backup Exec ports (continued)
Service or Process
Port
Port Type
MSSQL$BKUPEXEC
(process=sqlservr.exe)
A port number between TCP
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,
typically
TCP
10000
Backup Exec deduplication engine
(process=spoold.exe)
10082
TCP
Backup Exec deduplication manager 10102
(process=spad.exe)
TCP
Backup Exec Management Service
50104
(process=
BackupExecManagementService.exe)
TCP
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
DCOM/RPC
3106
TCP
Agent for Windows
6103
TCP
598
Configuration and settings
Using Backup Exec with firewalls
Table 15-2
Backup Exec ports (continued)
Service or Process
Port
Port Type
Push Install - Check for conflicts in
103x
message queue for CAS, which is part
of beserver.exe
TCP
Push Install
441
TCP
SMTP email notification
25 outbound from
Backup Exec server
TCP
SNMP
162 outbound from
Backup Exec server
TCP
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 595.
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
(benetns.exe)
6101
TCP
Backup Exec Agent for Windows
(beremote.exe)
10000
TCP
Backup Exec server (beserver.exe)
3527, 6106
TCP
Backup Exec Management Service
50104
(process=
BackupExecManagementService.exe)
TCP
MSSQL$BKUPEXEC (sqlsevr.exe)
1125
TCP
1434
UDP
599
Configuration and settings
Using encryption with Backup Exec
Table 15-3
Backup Exec listening ports (continued)
Service
Port
Port Type
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 1175.
See “Using Backup Exec with firewalls” on page 595.
Using encryption with Backup Exec
Backup Exec provides you with the ability to encrypt data. When you encrypt data,
you protect it from unauthorized access. Anyone that tries to access the data has
to have an encryption key that you create. Backup Exec provides software
encryption, but it also supports some devices that provide hardware encryption with
the T10 standard. Backup Exec configures encryption when you specify which
storage devices that you want to use for a backup job.
Backup Exec supports two security levels of encryption: 128-bit Advanced Encryption
Standard (AES) and 256-bit AES. The 256-bit AES encryption provides a stronger
level of security because the key is longer for 256-bit AES than for 128-bit AES.
However, 128-bit AES encryption enables backup jobs to process more quickly.
Hardware encryption using the T10 standard requires 256-bit AES.
When you run a duplicate backup job, any backup sets that are already encrypted
are not re-encrypted. However, you can encrypt any unencrypted backup sets.
This topic includes the following information:
600
Configuration and settings
Using encryption with Backup Exec
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.
Veritas recommends that you avoid using hardware compression with software
encryption. Hardware compression is performed after encryption. Data becomes
randomized during the encryption process. Compression does not work effectively
on data that is randomized.
Hardware encryption
Backup Exec supports hardware encryption for any storage devices that use the
T10 encryption standard. When you use hardware encryption, the data is transmitted
from the host computer to the storage device and then encrypted on the device.
Backup Exec manages the encryption keys that are used to access the encrypted
data.
Backup Exec only supports approved devices for T10 encryption.
601
Configuration and settings
Using encryption with Backup Exec
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 603.
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.
602
Configuration and settings
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. Veritas recommends that you use more than the
minimum number of characters.
Note: Hardware encryption that uses the T10 standard requires 256-bit AES. Backup
Exec does not let you enable hardware encryption for a job unless it uses at least
a 16-character pass phrase.
Also, a good pass phrase contains a combination of upper and lower case letters,
numbers, and special characters. You should avoid using literary quotations in pass
phrases.
A pass phrase can include only printable ASCII characters, which are characters
32 through 126. ASCII character 32 is the space character, which is entered using
the space bar on the keyboard. ASCII characters 33 through 126 include the
following:
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ
[\]^_‘abcdefghijklmnopqrstuvwxyz{|}~
See “Encryption key management” on page 603.
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 600.
603
Configuration and settings
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, Veritas recommends the following:
■
Maintain a written log of the pass phrases. Keep the log in a safe place in a
separate physical location from the encrypted backup sets.
■
Back up the Backup Exec database. The database keeps a record of the keys.
Caution: If you do not have a backup of the Backup Exec database and do not
remember your pass phrases, you cannot restore data from the encrypted media.
In addition, Veritas cannot restore encrypted data in this situation.
A key that is created on a Backup Exec server is specific to that Backup Exec
server. You cannot move keys between Backup Exec servers. However, you can
create new keys on a different Backup Exec server by using existing pass phrases.
A pass phrase always generates the same key. In addition, if you delete a key
accidentally, you can recreate it by using the pass phrase.
If a Backup Exec database becomes corrupted on a Backup Exec server and is
replaced by a new database, you must manually recreate all of the encryption keys
that were stored on the original database.
If you move a database from one Backup Exec server to another Backup Exec
server, the encryption keys remain intact as long as the new Backup Exec server
meets the following criteria:
■
Has the same user accounts as the original Backup Exec server.
■
Is in the same domain as the original Backup Exec server.
See “Creating encryption keys” on page 604.
See “Replacing an encryption key” on page 605.
See “Deleting encryption keys” on page 607.
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.
604
Configuration and settings
Replacing an encryption key
3
Click Manage Keys.
4
Click New.
5
In the Key name field, type a unique name for this key. The name can include
up to 256 characters.
6
In the Encryption type field, select the encryption type to use for this key.
Your choices are 128-bit AES or 256-bit AES.
The default type is 256-bit AES. The 256-bit AES encryption provides a stronger
level of security than 128-bit AES encryption. However, backup jobs may
process more slowly with 256-bit AES encryption than with 128-bit AES
encryption. Hardware encryption that uses the T10 standard requires 256-bit
AES.
7
In the Pass phrase field, type a pass phrase for this key. You can use only
printable ASCII characters.
For 128-bit AES encryption, the pass phrase must be at least eight characters.
For 256-bit AES encryption, the pass phrase must be at least 16 characters.
Veritas recommends that you use more than the minimum number of characters.
Warning: If an encryption key that is used in a backup is no longer available,
you must provide the pass phrase during restore. Without the pass phrase,
the data cannot be accessed.
8
In the Confirm pass phrase field, type the pass phrase again to confirm it.
9
In the Encryption key type group box, select whether you want to create a
common or restricted encryption key.
If a key is common, any user of this installation of Backup Exec can use the
key to back up and restore data. If a key is restricted, anyone can use the key
to back up data. But only the key owner or a user who knows the pass phrase
can use the restricted key to restore the encrypted data.
10 Click OK.
See “Encryption key management” on page 603.
See “Using encryption with Backup Exec” on page 600.
Replacing an encryption key
You can replace one encryption key with another for all backup jobs and duplicate
backup set jobs.
605
Configuration and settings
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
606
Configuration and settings
Deleting encryption keys
To create a new
key
Complete the following steps:
■
Click New.
■
In the Key name field, type a unique name for the key.
The name can include up to 256 characters.
In the Encryption type field, select the type of encryption to
use for this key.
You can select 128-bit AES or 256-bit AES. The default type
is 256-bit AES.
The 256-bit AES encryption provides a stronger level of security
than 128-bit AES encryption. However, backup jobs may
process more slowly with 256-bit AES encryption than with
128-bit AES encryption.
Hardware encryption that uses the T10 standard requires
256-bit AES.
In the Pass phrase field, type a pass phrase for this key.
For 128-bit AES encryption, the pass phrase must be at least
eight characters. For 256-bit AES encryption, the pass phrase
must be at least 16 characters. Veritas recommends that you
use more than the minimum number of characters.
You can use only printable ASCII characters.
■
■
Warning: If an encryption key that is used in a backup is no
longer available, you must provide the pass phrase during
restore. Without the pass phrase, the data cannot be accessed.
■
■
■
7
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.
Click OK.
See “Encryption key management” on page 603.
See “Using encryption with Backup Exec” on page 600.
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:
607
Configuration and settings
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 603.
See “Using encryption with Backup Exec” on page 600.
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
608
Configuration and settings
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 544.
The following table lists the individual items you can restore for each agent.
609
Configuration and settings
Granular Recovery Technology
Table 15-5
Individual items that can be recovered for each agent
Agent
Individual items
Agent for Microsoft Active
Directory
You can restore the following individual items:
■
Active Directory objects and attributes
■
Active Directory Application Mode (ADAM) and Active
Directory Lightweight Directory Services (AD LDS) objects
and attributes
Agent for Microsoft Exchange You can restore the following individual items:
Server
■ Mailboxes
Agent for Microsoft
SharePoint
Agent for VMware and
Hyper-V
■
Mail messages and their attachments
■
Public folders
■
Calendar items
■
Contacts
■
Notes
■
Tasks
The following are examples of the individual items that can
be restored:
■
Site collections
■
Sites or subsites
■
Document or picture libraries
■
Lists
■
Individual list items
■
Documents, pictures, or other files that are stored in
libraries
You can restore drives, folders, and files from virtual
machines that run a Windows operating system.
You can also enable the granular recovery of Microsoft
Exchange, SQL, SharePoint, and Active Directory application
data that resides on virtual machines.
See “Using Granular Recovery Technology (GRT) with the
Agent for VMware” on page 885.
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.
610
Configuration and settings
Granular Recovery Technology
Note: Veritas recommends that you do not use software compression or encryption
for GRT-enabled backup jobs. The compression and encryption processes are
resource-intensive. Enabling either software compression or encryption can result
in degraded performance for GRT-enabled backup jobs.
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
Veritas recommends that you select a disk storage device for any backups that are
enabled for Granular Recovery Technology (GRT). The disk storage device should
be on a volume that does not have file size limitations. An NTFS drive is an example
of a volume without file size limitations. Some examples of volumes that have file
size limitations include FAT and FAT32 volumes.
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, Veritas recommends the following to avoid disk space problems:
■
It should not be a system volume
■
It should have at least 1 GB of available space
611
Configuration and settings
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
restored
Staging process
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.
612
Configuration and settings
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
Directory
You must use a Backup Exec server that is running Windows
Server 2012 R2 to back up an Active Directory server that is
running Windows Server 2012 R2.
In a 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.
613
Configuration and settings
Granular Recovery Technology
Table 15-7
Agent
Granular Recovery Technology requirements (continued)
Restriction