Full backups provide the most comprehensive protection of data.
Backups for any client start with a full backup. The full backup becomes a baseline to which subsequent backup types are applied. For example, a full backup must be performed before a transaction log backup can be initiated.
Use the following steps to run a full backup:
A transaction log backup captures the transaction log which contains a record of all committed or uncommitted transactions. Transaction log backups are consistent with the start time of the backup.
The use of transaction log backups make point-in-time recovery possible. This is useful in the scenario of a database failure where it is unacceptable to lose any data and you want to restore to the point of failure. If you use only full and differential backups, you will be able to restore to the time of the backup, but not to a point-in-time between backups.
A transaction log backup is similar to a traditional incremental backup you might perform on a file system because the transaction log backup contains only the new changes since the full or another transaction log backup.
Each time a transaction log is backed up it is truncated to the exact time of the backup. No checkpoint is issued at this time, therefore dirty pages are not written to disk before or after a transaction log backup. If there are dirty pages, any completed transactions will need to be rolled forward if a transaction log restore is performed. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup.
Use the following steps to run a transaction log backup:
You can start a Transaction Log backup automatically after a successful Full or Differential backup. This is useful when you want to back up logs immediately after a data backup, and allows you to do so without creating two scheduled jobs.
Use the following steps to automatically run a transaction log after a backup:
|
Use the following steps to perform transaction log backups without having to run full backups first.
|
|
|
If you experience a database failure and you want to restore to the point of failure, a Transaction Log Backup with Do not truncate log must be initiated. This backups the database when it is damaged, regardless of its state.
It is used for capturing all transaction log events occurred since the last backup was run. This operation does not empty the active transaction log.
Use the following steps to disable log truncation during a backup:
When backing up transaction logs, you can choose to back up the tail of the log to capture the log records that have not yet been backed up. A tail-log backup prevents work loss and keeps the log chain intact. A tail-log backup allows you to recover a database to the point of failure; otherwise you can only recover a database to the end of the last backup that was created before the failure. For example, if a database was damaged or a data file was deleted, you should run a tail-log backup before attempting a file/file group restore. After the log tail is backed up, the database will be left in the RESTORING state.
Use the following step to backup the tail of a transaction log:
|
Full backups are necessary at regular intervals as it reduces the chance of data loss if one of log backup becomes corrupted as it will invalidate (not restorable) all other log backups performed after that. This key is used for the purpose of re-enforcing the need of a full backup after certain number of transaction log backups have run.
When this registry key is configured, a minor event will be generated in the Event Viewer to remind users to run a full backup after the configured number of transaction log backups have run.
Use the following steps to configure the number of log backups:
|
A differential backup contains only the data that is new or has been changed since the last full backup. Differential backups consume less media and use less resources than full backups. Differential backups are cumulative. This means that each differential backup contains all changes accumulated since the last full backup. Each successive differential backup contains all the changes from the previous differential backup.
Use the following steps to run a differential backup:
|
Backups can be compressed before it is backed up to reduce the size of the backup. Typically, compressing a backup will require less device I/O which should increase backup speed significantly. However, CPU usage may increase for compressed backups and you may need to evaluate performance counters. Scheduling the backup during off-peak hours or compressing only low-priority backups may be desirable.
When using compression, there is no need for deduplication as the data will already be compressed and deduplication will not consequently save any more space.
Use the following steps to enable compression:
|
A partial backup contains the following:
Partial backups are useful whenever you want to exclude read-only file groups. A partial backup is not supported when backing up transaction logs.
Use the following steps to enable partial backups:
|
You can perform backups of one or more SQL databases from the command line interface.
Command line backups enable you to perform backup operation on multiple clients simultaneously. In order to run the backups from command line, you need an input xml file which contains the parameters for configuring the backup options. This input xml file can be obtained from one of the following ways:
To run command line operations you must first login to the CommServe as follows:
qlogin -cs <commserve name> -u <user name>
qlogin -cs server1 -u user1
qoperation execute -af backup_template.xml -clientName xxxxx -instanceName xxxxx -subclientName xxxxx
qlist job –j JOBID
qlogout [-cs commserver] [-all] [-tf tokenfile] [-tk token] [-h]
Performing a Full Backup |
qoperation execute -af backup_template.xml -backupLevel FULL -subclientName subclient1 -clientName client1 -instanceName client1/instance1 |
Performing a Transaction Log Backup |
qoperation execute -af backup_template.xml -backupLevel INCREMENTAL -subclientName subclient1 -clientName client1 -instanceName client1/instance1 |
Performing a Differential Backup |
qoperation execute –af backup_template.xml –backupLevel DIFFERENTIAL –subclientName subclient1 –clientName client1 –instanceName client1/instance1 |
Performing an On Demand Backup |
qoperation execute -af backup_template.xml -backupLevel FULL -subclientName subclient1 -clientName client1 -instanceName client1/instance1 -ondemandinputfile C:\test\myDBsContent.txt where myDBsContent.txt is an input file that list the databases as follows: DB1 DB2 To run ondemand backup for File File Group, the input file should list the database name, file group name and file name as follows: DB1<tab>Group1<tab>File1inGroup1 DB1<tab>Group2<tab>File2inGroup1 |
In addition to the parameters provided in the template xml file, if you want to include additional options for the backup, you can do so by selecting the required options from the CommCell Console and generate the command line xml script for the backup.
Follow the steps given below to generate a script which you can use to perform a backup from the command line interface:
Follow the steps given below to schedule a backup:
1.. |
|
See Scheduling for a comprehensive information on scheduling jobs.
Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:
Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel. Keep in mind that changes made to this configuration will affect all jobs in the entire CommCell.
To Configure the job restartability for a specific job, you can modify the retry settings for the job. This will override the setting in the Control Panel. It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.
Backup jobs for this Agent are resumed from the point-of-failure. |
|
The following controls are available for running jobs in the Job Controller window:
Suspend |
Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time. |
Resume |
Resumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting. |
Kill |
Terminates a job. |
See Job Management for a comprehensive information on managing jobs.
The following table describes the available additional options to further refine your backup operations:
Option | Description | Related topics |
Startup Options |
The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows:
|
Refer to Job Priority and Priority Precedence. |
Alerts |
This option enables users or user groups to get automatic notification on the status of the data protection job. Follow the steps given below to set up the criteria to raise notifications/alerts:
|
Refer to Alerts. |
Command Line Backups |
Command Line Interface enables you to perform backups or restore from the command line. The
commands can be executed from the command line or can be integrated into scripts. You can also generate command line scripts for specific operations from the CommCell Browser using the Save As Script option. |
Refer to Command Line Interface. |
CommCell Readiness Report |
The CommCell Readiness Report provides you with vital information, such as
connectivity and readiness of the Client, MediaAgent and CommServe. It is useful
to run this report before performing the data protection or recovery job. Follow the steps
given below to generate the report:
|
Refer to CommCell Readiness Report. |
Backup Job Summary Report |
The Backup Job Summary Report provides you with information about all the
backup jobs that are run in last 24 hrs for a specific subclient. You can get
information such as status, time, data size etc. for each backup job. It is useful
to run this report after performing the backup. Follow the steps
given below to generate the report:
|
Refer to Backup Job Summary Report. |
Data Path Options |
Data Protection operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path:
|
Refer Change Data Path. |
Start New Media |
The Start New Media option enables you to start the data protection operation on a new media. This feature provides control over where the data physically resides. Use the following steps to start the data protection operation on a new media:
|
Refer to Start New Media. |
Mark Media Full on Success |
This option marks the media as full, two minutes after the successful completion of the data protection job. This option prevents another job from writing to this media. Follow the steps given below:
|
Refer to Export Media. |
Allow other Schedules to use Media Set |
The Allow Other Schedules to use Media Set option allows jobs that are part of the schedule or schedule policy and using the specific storage policy to start a new media. It also prevents other jobs from writing to the same set of media.
|
Refer to Creating an Exportable Media Set. |
Extended Data Retention |
This option allows you to extend the expiration date of a specific job. This will override the default retention set at the corresponding storage policy copy. Follow the steps given below to extend the expiration date:
|
Refer to Extended Retention Rules. |
Vault Tracker |
This feature provides the facility to manage media that is removed from a library and stored in offsite locations. Depending on your VaultTracker setup, select the required options. Use the following steps to access and select the VaultTracker options.
|
Refer to VaultTracker or VaultTracker Enterprise. |