An auxiliary copy operation or a data protection operation copies valid data from a source copy of a specific storage policy to all or one active secondary copy within a storage policy. These secondary copies can be either synchronous or selective copies. A selective copy allows you to copy the backup data selectively from a source copy to the secondary copy, providing for better tape rotation.
During a data protection operation that creates an inline copy, only those backups from the primary copy that meet certain criteria will be copied to a selective copy. You can define a selective copy to be time-based, automatically selected, or automatically not selected on the primary copy.
Note
Selective copy will copy the selective Online Full backups along with their linked jobs.
Before You Begin
Include the selectiveOnlineFull parameter in the param file and set the parameter value to 1 to enable backups using selective copy from the client.
Set the parameter value to 0 to disable this capability.
Example:
UNIX
[root@rhel5sap64ismorethanthirtycharacters /]# cat /opt/commvault/SapMaxDbAgent/param
numstreams
2
CvInstanceName
Instance001
CvClientName
rhel5sap64ismorethanthirtycharacters
selectiveOnlineFull
1
Windows:
echo C:\Program Files\Commvault\ContentStore\SapMaxDbAgent\param
numstreams
2
CvInstanceName
Instance001
CvClientName
sde-sap2
selectiveOnlineFull
1
Procedure
The following examples describe the various scenarios under which an online full backup job can be copied to selective copies:
Example 1
Successful completion of an online full backup cycle requires the successful completion of a full data and corresponding configuration backup job followed by an incremental log and corresponding configuration backup job (the software initiates a single job for the data and a single job for the logs with corresponding configuration files). As such, the shortest successful cycle can be illustrated as follows:
DATA, CONFIG, FULL (Successful) --> First, A full backup with the data and the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
LOG, CONFIG, Incremental (Successful) ---> Next, A log backup with the data and the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
In this example, each required job has successfully completed within the backup cycle. Therefore, the online full data backup job (along with all the other jobs in the cycle) are copied to a selective copy.
Example 2
A full backup cycle can include other backup job types (for example, incremental backup jobs). If the full backup cycle is successful, these jobs are also copied to a selective copy. This includes incremental backup jobs within the cycle:
DATA, CONFIG, FULL (Successful) --> First, a full backup with the data and the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
DATA, CONFIG, Incremental (Successful)--> Next, an Incremental backup with the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
LOG, CONFIG, Incremental (Fail) --> If a log backup that is performed after a successful incremental backup fails, then the software does not consider this cycle as an online full backup cycle.
DATA, CONFIG, Incremental (Successful)--> A full backup with the data and the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
LOG, CONFIG, Incremental (Successful) --> On the second attempt after another incremental backup, a log backup with configuration files (dbm.ebf and dbm.knl) successfully completes.
In this example, the first attempt at running the configuration job for the full log backup job failed; however, the second attempt succeeded and therefore completed a successful cycle. As a result, each job (total of five) within the cycle will be copied to a selective copy. This includes the one configuration job that failed.
Example 3
A full backup cycle starts before a full online backup cycle completes:
DATA, CONFIG, FULL (Successful)--> First, a full backup with the data and the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
DATA, CONFIG, Incremental (Successful)-->Next, an Incremental backup with the SAP MaxDB configuration files (dbm.ebf and dbm.knl) successfully completes.
DATA, CONFIG, FULL (Successful)--> However, before a log backup can be taken to complete the full cycle, another full backup with data and configuration files is successfully completed. As such, none of the backup jobs in the first cycle can be copied to a selective copy.
In this example, you need to run a log backup after the successful incremental backup to complete the online full cycle. Only after a full successful cycle, each job within the cycle will be copied to a selective copy.