Data Aging - SQL Server iDataAgent
- Getting Started
- Extended Retention Rules
- Data Aging for Transaction, Archive, and Logical Log Backups
- Retention Rules for Log Backups
- Pruning All Log Backups by Days Retention Rule
- Data Aging for Stored Procedures
- SQL Back in Time Restores and Data Aging Rules
- Data Aging Rules for On-Demand Backups
- Enabling MSDB Database Clean-Up
Data Aging is the process of removing old data from secondary storage to allow the associated media to be reused for future backups.
By default, all backup data is retained infinitely. However, you should change the retention of your data based on your needs. Note that if you continue to have infinite retention, you will also need infinite storage capacity.
Setting Up the Basic Retention Rule
- From the CommCell Browser, expand Policies | Storage Policies | <Storage Policy>.
- Right-click the appropriate storage policy copy, and then click the Properties.
- In the Copy Properties dialog box, click the Retention tab.
- Under Basic Retention Rule for All Backups, click the Retain For.
- Enter number of days to retain the data.
- Enter number of cycles to retain the data.
- Click OK.
- In the Confirm Basic Retention dialog box, click Yes.
On the ribbon in the CommCell Console, click the Reports tab, and then click Forecast.Under Reports pane, Data Retention Forecast and Compliance is selected by default.
- Click Run.
- The report will display the data to be pruned when a data aging job is run.
To ensure only data intended for aging is actually aged, it is important to identify the data that will be aged based on the retention rules you have configured. Hence, ensure this report includes only the data you intend to age.
If necessary, fine-tune your rules so that only the intended data is aged.
Once you run a data aging job, the data will be pruned.
Running the Data Aging Job
- From the CommCell Console, right click the CommServe node, point to All Tasks and then click Data Aging.
In the Data Aging Options dialog box, click OK.
- You can track the progress of the job from the Job Controller window. When the job is completed, in the Job Controller the Status will be displayed as Completed.
Make sure that the job completes successfully. If the job did not complete successfully, rerun the job.
Extended retention rules can be used in the following circumstances:
- If you have a single drive tape library
- If you want to create a hierarchical retention scheme (grandfather-father-son tape rotation)
Extended retention rules allow you to define three additional "extended" retention periods for full (or synthetic full) backups. For example:
- You may want to retain your weekly full backups for 30 days.
- You may want to retain your monthly full backup for 90 days.
- You may want to retain your yearly full backup for 365 days.
A backup job will be selected for extended retention based on its start time. For example: If a backup job starts at 11:55 pm on August 31st and ends at 1 am on September 1st, then it will be selected as the last full backup for the month of August and will be picked up for extended retention.
In all other cases, we recommend you to use Auxiliary Copy for extended storage as it actually creates another physical copy of the data, thereby reducing the risk of data loss due to media failure.
Setting Up the Extended Retention RulesUse the following steps for setting up the extended retention rules:
- Right-click the storage policy copy and click Properties.
- Click the Retention tab.
- Set the basic retention rules by clicking Retain for and entering the number of days and cycles appropriate for your organization.
- Set the extended retention rules as follows:
- Click the For button.
- Enter the number of Days Total to retain the backup.
- Click the Keep drop-down list, and select the desired backup criteria (e.g., Monthly Full, Weekly Full).
- Click the Grace Days drop-down list and select the number of days (e.g., 2).
This allows you to consider the additional number of days along with the Extended Retention rule. For example, if the last full backup job fails with in the defined extended retention criteria, then the next full backup job that ran in the specified grace days will be selected for retention.
- Repeat Step 4 to configure additional extended retention.
- Click OK.
Log Backups (transaction, archive, or logical logs) are not considered part of the backup cycle. Therefore, storage policy cycle retention parameters do not apply to them.
Log backups may be chained to data backup operations, which can allow storage policy cycle retention parameters to be applied to them.
The log backups are not aged until the chained data is aged. In addition, the following are considered:
- Logs that need to be copied to secondary copies will not be aged both on primary and non-primary source copy
- Logs that exist only on one copy will be aged when they are older than the oldest data
- Logs that exist on multiple copies will be aged according to copy retention days
- Logs that exist on multiple copies with the longest retention days will be aged when they are older than the oldest data
- Partial, disabled logs will be aged when they are older than the oldest data
If you want log backups to be aged according to the defined days retention rule for the data, the SQL Chain Check and SQL Log Rule will be skipped and the SQL transaction logs will be pruned for each copy using the days retention rule only. Follow the steps given below to set this up:
- From the CommCell Console, click the Storage tab.
- Click the Media Management icon.
- Click the Data Aging tab.
- In the Prune All Database Agent Logs Only By Days Retention Rule, type 1 to enable pruning for all database agent logs based on the days retention.
- Click OK.
Data Aging for the SQL Server iDataAgents performs the following stored procedures that you may have been manually running on Enterprise Manager. When Data Aging is run, the system ages these histories from the CommServe database and the SQL Server.
When you perform a back in time restore (i.e., restoring to a backup cycle earlier than the current backup cycle), all differential and transaction log backups which were run after the full backup from which the restored data was obtained will not be able to be aged until a new full backup is run. Running a full backup after performing a back in time restore releases the older backups and subsequent log backups for data aging.
Data Aging for On-Demand backup jobs uses days/time, and ignores cycles and extended retention rules, as the determining factor for pruning the data. Therefore, once the retention time criteria has been met, all data (for both data and logs) is pruned that was backed up using the storage policy specified in the Command Line Interface.
An effective storage policy strategy for SQL On-Demand backups is as follows:
- The same storage policy should not be used for regular backups and On-Demand backups.
- The storage policy copy containing logs of On-Demand backups should have a much longer retention time than other storage policies used by regular backups for the same instance. This is to prevent the logs of On-Demand backups from being pruned before the data of regular backups, and allow the database to be fully restored and recovered using the data of old regular backups and logs afterwards.
By default, Data Aging jobs do not perform a client-side clean-up of database metadata. However, to ensure that unnecessary data is not left behind, you can either use the system stored procedures mentioned below per SQL instance:
Or enable client-side clean-up of database metadata process as follows:
- From the CommCell Browser, navigate to Client Computers.
- Right-click the <CommServe Client> and then click Properties.
- Click the Advanced button.
- Click the Additional Settings tab.
- Click Add.
- In the Name field, type nDisableMSDBCleanup.
- In the Location list, select Cvd.
- In the Type list, select Integer.
- In the Value field, type 0 to enable database clean-up.
- Click OK.
Provides comprehensive information on additional Data Aging capabilities.