Backup Exec 20.2 Administrator's Guide
- Introducing Backup Exec
- Installation
- Methods for installing the Agent for Windows
- Using a command prompt to install the Agent for Windows on a remote computer
- Using a command script to install the Agent for Windows
- Installing the Remote Administrator
- Installing Backup Exec using the command line (silent mode)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- Alerts and notifications
- Enabling active alerts and alert history to display on the Home tab
- Adding a recipient group for alert notifications
- Sending a notification when a job completes
- SNMP traps for Backup Exec alerts
- Disk-based and network-based storage
- Configuring disk storage
- Configuring disk cartridge storage
- Backup sets
- Cloud-based storage devices
- Amazon S3 cloud-based storage
- Google cloud-based storage
- Microsoft Azure cloud-based storage
- Private cloud-based storage
- About S3-Compatible Cloud Storage
- About the Backup Exec™ CloudConnect Optimizer
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Tape storage
- Robotic libraries in Backup Exec
- Creating robotic library partitions
- Managing tapes
- Creating media sets for tapes
- Labeling tape media
- Default media vaults
- Storage device pools
- Storage operations
- Conversion to virtual machines
- Configuration and settings
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Reports
- Creating a custom report
- List of Backup Exec standard reports
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Using Backup Exec in cluster environments
- Configurations for Backup Exec and Microsoft Cluster Servers
- Disaster recovery of a cluster
- Simplified Disaster Recovery
- Setting or changing the alternate location for the disaster recovery information file
- Creating a Simplified Disaster Recovery disk image
- Preparing to recover from a disaster by using Simplified Disaster Recovery
- Recovering a computer with Simplified Disaster Recovery
- Performing manual disaster recovery
- Integration with Veritas™ Information Map
- Appendix A. Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Backup Exec Deduplication Feature
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Backup Exec Agent for VMware
- About establishing trust for a vCenter/ESX(i) server
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Backup Exec Agent for Microsoft Hyper-V
- Backing up Microsoft Hyper-V virtual machines
- About instant recovery of a Hyper-V virtual machine
- About Recovery Ready for Hyper-V virtual machines
- Appendix E. Backup Exec Agent for Microsoft SQL Server
- Backing up SQL databases and transaction logs
- Restoring SQL databases and transaction logs
- Disaster recovery of a SQL Server
- Appendix F. Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Backup Exec Agent for Oracle on Windows or Linux Servers
- Configuring the Oracle Agent on Windows computers and Linux servers
- Configuring an Oracle instance on Windows computers
- Viewing an Oracle instance on Windows computers
- About authentication credentials on the Backup Exec server
- About backing up Oracle databases
- About restoring Oracle resources
- Appendix I. Backup Exec Agent for Enterprise Vault
- About backup methods for Enterprise Vault backup jobs
- Restoring Enterprise Vault
- About the Backup Exec Migrator for Enterprise Vault
- Configuring the Backup Exec Migrator
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- Appendix K. Backup Exec Central Admin Server Feature
- About installing the Central Admin Server feature
- What happens when CAS communication thresholds are reached
- About job delegation in CAS
- How to use Backup Exec server pools in CAS
- How centralized restore works in CAS
- Appendix L. Backup Exec Advanced Disk-based Backup Feature
- Appendix M. Backup Exec NDMP Feature
- About restoring and redirecting restore data for NDMP servers
- Viewing the properties of an NDMP server
- Viewing storage properties for an NDMP server
- Appendix N. Backup Exec Agent for Linux
- About installing the Agent for Linux
- About establishing trust for a remote Linux computer in the Backup Exec list of servers
- Editing configuration options for Linux computers
- About backing up a Linux computer by using the Agent for Linux
- About restoring data to Linux computers
- Editing the default backup job options for Linux computers
- Uninstalling the Agent for Linux
- Appendix O. Backup Exec Remote Media Agent for Linux
- About installing the Remote Media Agent for Linux
- About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers
- About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux
- About adding a Linux server as a Remote Media Agent for Linux
- Editing properties for the Remote Media Agent for Linux
- Creating a simulated tape library
- Viewing simulated tape libraries properties
- Appendix P. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
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.
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
- Do one of the following:
To configure default schedule settings 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 schedule settings.
To configure a schedule for specific backup jobs
Create a new backup definition or edit an existing backup definition.
In the Backup box, click Edit.
- In the left pane, click Schedule.
- 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.
- 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.
- For each job for which you want to configure a schedule, do one of the following:
To configure recurring jobs
Complete the following steps:
Select Recurrence.
Proceed to step 6 to configure the recurrence pattern.
To configure jobs to run immediately without any recurrences
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.
- To configure the recurrence pattern, complete the following options:
Hours
Select this option to create a recurrence pattern that is measured in hours or minutes.
When you select Hours, you can configure the following options:
Every X hour/minute
Indicate the number of hours or minutes between the start time of a job and the start time of the next job instance.
You must choose between the following options:
From
Designate the starting time for a job to run.
Between
Restrict the job to certain hours and days. For example, if you only want the job to run during business hours, you can select 9:00 AM to 5:00 PM on Monday, Tuesday, Wednesday, Thursday, and Friday.
The start time and end time can span a maximum of 24 hours. However, they can cross over midnight into the following day.
Days
Select this option to create a recurrence pattern that is measured in days.
When you select Days, you must choose between the following options:
Every X day
Indicate the number of days between the start time of a job and the start time of the next job instance.
Every weekday
Select this option to enable the job to run on Mondays, Tuesdays, Wednesdays, Thursdays, and Fridays.
Weeks
Select this option to create a recurrence pattern that is measured in weeks.
When you create a recurrence pattern that is measured in weeks, you must configure the Every X week on field. The Every X week on specifies the number of weeks between the start time of a job and the start time of the next job instance. It also specifies the days of the week on which the job should run.
Months
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.
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.
Run initial full backup now in addition to the selected schedule
Select this option to run the initial full backup as soon as the job is created without affecting the schedule of future jobs.
Reschedule the job if it does not start X hours after its scheduled start time
Specify the amount of time past the job's scheduled start time at which you want Backup Exec to change the job completion status to Missed. The job is rescheduled to run based on the time window that you configured.
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.
- 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.
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.
See Including a specific date in the schedule for a backup 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.
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.
- 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.
- Click OK.