Topics | How To | Troubleshoot | How Do I | Support | Related Topics
Auxiliary Copy with Synchronous and Selective Copies
Auxiliary Copy and Other Copy Features
Auxiliary Copy with Multiple Stream Parallelism
Auxiliary Copy with a Specified Source MediaAgent
Sequence in Which Data is Copied During an Auxiliary Copy Operation
Safeguarding Your Data Using Auxiliary Copy With Selective Copies
Skip Job on Read Errors During Auxiliary Copy
Customize Auxiliary Copy Operations through Registry Keys
An auxiliary copy operation allows you to create secondary copies of data associated with data protection operations, independent of the original copy. For a full understanding, you should have some basic knowledge of storage policy and storage policy copy configurations. See Storage Policies and Storage Policy Copies for more information.
The auxiliary copy operation can be useful for creating additional standby copies of data. The primary and secondary copies use different media and often use different libraries, depending on the configuration. Should the primary copy become inoperative, perhaps due to a storage media failure, or a library or network malfunction, you can promote a synchronous copy to become the primary copy. This allows you to continue operations as before and make repairs without interrupting data protection and data recovery operations.
When an auxiliary copy operation is started, all valid data from a source copy is copied to all or one active secondary copies within the storage policy. A source copy can either be the primary copy (the default), or a secondary copy that has been selected as the source copy. The following figure illustrates a primary copy as the source copy for an auxiliary copy operation:
|
If a job is only partially copied, it can be recopied by using the Re-Copy feature. Doing this will re-copy all the chunks of the selected job from the beginning of the job. For more information, see Re-Copy Fully or Partially Copied Jobs.
You have the ability to disable a backup job for the auxiliary copy, i.e., once a job is disabled, it will not be copied during an Auxiliary Copy operation. Additionally, if selected, those jobs that are dependent on the selected disabled job will be disabled as well.
Things to consider before you disable a job:
For step-by-step instructions, see Disable/Enable a Job From a Storage Policy Copy.
An auxiliary copy should not be confused with a standard data protection operation. The two operations are unrelated, except, of course, that a data protection operation must precede an auxiliary copy. In all other ways the two operations are distinct and must be initiated or scheduled individually. A data protection operation is specific to a particular subclient, copying the subclient content from the client computer to the primary storage policy copy. An auxiliary copy, however, does not involve clients; instead, it copies backed up data from a source copy to one or more secondary copies. If you want the auxiliary copy operation to capture the data of only one subclient, then you must ensure that subclient has a dedicated storage policy.
Auxiliary copy does not manipulate software compression on the data. The data is transferred as it is. The hardware compression is transparent. Thus, hardware compressed data is uncompressed by the tape device on read, and recompressed during tape write.
If the media currently associated with your source copy is not readable or simply cannot be used, you can Disable/Enable All Jobs Associated with a Media so that all jobs associated with this media will be skipped during auxiliary copy operations.
If the media associated with the secondary storage policy copy becomes unreadable, you can Re-Copy all Jobs Associated with a Media. This will recopy all the jobs associated with the specific media.
An auxiliary copy operation copies valid data from a source copy of a specific storage policy to all or one active secondary copy within a storage policy. Data from source copies are not copied over to inactive secondary copies.
These secondary copies can be either synchronous or selective copies. The following sections describe how data is copied during an auxiliary copy job on both types of copies.
The auxiliary copy operation will copy full, incremental, and differential backup data from a source copy to other synchronous copies based on the All Backups option or the Backups On And After date you selected from the Copy Policy tab of the Copy Properties dialog box.
| If a primary copy has the Spool Copy (no retention) option enabled, and there is no coverage for all of the subclients in the secondary copies, the synchronous copy cannot be deleted. Instead, users will be prompted with a message to change the retention period of the primary copy or create another synchronous copy. |
If you select the All Backups option when creating a synchronous copy, all data protection operations on a source copy will be copied to the synchronous copy.
In the following example, if an auxiliary copy is run on 9/5, F1, I1, D1, and F2 will be copied to the synchronous copy. The source copy for the operation is the primary copy.
When the All Backups option is selected, all data protection operations on a source copy will be copied to the synchronous copy.
| When auxiliary copies are run on storage policies used by DataArchiver Agents, all archiving operations will be copied, regardless if a new Index exists. |
If you select a date from the Backups On and After field, then all data protection operations on or after the date you select, starting from 12:00 A.M., will be copied to the synchronous copy. This option is useful if you do not want all the data protection operations of a source copy to be copied to the synchronous copy.
Note that the date entered can be on, before, or after the current CommServe date. When the date entered is after the current CommServe date, jobs (up to the date specified) that are to be copied, as well as partially copied jobs will be disabled for copy. If no date is entered, all backup data will be copied from the primary copy to the secondary copy.
In the following example, the Backups On and After date was set to 9/4. All data protection operations starting from 9/4 are copied to the synchronous copy when an auxiliary copy operation is run on 9/9. All data protection operations prior to 9/4 are not copied.
When you enter a date that is earlier than (before) the date already specified, all data protection operations after the date specified or after the first copied/selected job, whichever is later, will be copied to the secondary copy.
For example, let’s assume the current date is January 1, 2009, and you created a storage policy copy with the Backups On and After option set to January 1, 2010. This would indicate that all jobs up to January 1, 2010 would be disabled for copy. With this, you manually pick a job for copy on May 1, 2009. On June 1, 2009, you revise the Storage Policy Copy Backups On and After option to be January 1, 2009. This will automatically select all jobs that are run after May 1, 2009 (the first copied job), for auxiliary copy. Any jobs that were run before May 1, 2009 would not be copied (in this scenario). To copy job(s) from any date before May 1, 2009, manually select the job(s) for copy. If you had not selected any job manually and modified the Backups On and After to January 1, 2009, all jobs from January 1, 2009 to current date would have been picked up for auxiliary copy.
Selective copies only contain full backup data that has occurred on or after a specified date and are copied based on the following selective criteria:
The selective copy type can be selected from the Selective Copy tab of the Copy Properties dialog box. Once you set the Backups On and After date from the Copy Properties dialog box, then all data protection operations starting on or after the date you select (starting from 12:00 A.M.) will be copied to the selective copy, based on the selective copy type.
If a selective copy is defined as an All Full Backups copy, all full backups associated with the storage policy are copied to the selective copy.
If a selective copy is defined as time based, an auxiliary copy operation copies the first or last full backup of a time period based on the following parameters:
| Weekly | The first or last full backup of a specified starting day of a week will be copied from 12:00 A.M. of that day up to 11:59 P.M. on the last day of that week. |
| Monthly | The first or last full backup of a specified starting day of a month will be copied from 12:00 A.M. on that day up to 11:59 P.M. on the last day of that month. |
| Quarterly | The first or last full backup of the first day of a quarter will be copied from 12:00 A.M. on that day up to 11:59 P.M. on the last day of that quarter. |
| Half Yearly | The first or last full backup of the first day of a half year will be copied from 12:00 A.M. on that day up to 11:59 P.M. on the last day of that half year. |
| Yearly | The first or last full backup of the first day of a year will be copied from 12:00 A.M. on that day up to 11:59 P.M. on the last day of that year. |
| Advanced | This option allows
you to select the First or Last full backup performed after a specific
time period. The time period can be specified in
cycles/days/weeks/months. Note that for cycle based criteria, the copy selection is based on the mod logic. For more information, see For Selective Copy, how does the job selection work with Advanced - cycle based criteria? |
A backup job will be selected 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.
Selective storage policy copies associated with custom calendars will have data copied during auxiliary copy operations monthly, quarterly, half yearly, or yearly based on the days defined in the calendar. See Custom Calendar for more information.
Example
The following example illustrates the time interval of a primary copy with four full backups that were run across two weekly time intervals, T1 and T2, every one week starting on Monday.
In the following example, a time based selective copy was specified as every one week starting on Monday, with the First full backup option enabled on the copy. Data protection operations were run across two time intervals on the primary copy, T1 and T2.
If an auxiliary copy operation is run on Monday 9/16, the first full backup within each weekly time interval (F1 and F3) will be copied to the selective copy.
If the Last full backup option is enabled on the copy instead of the First full backup option, then F2 and F4 will be copied instead of F1 and F3.
If a selective copy is defined as a Do Not Automatically Select Jobs copy no backups will be copied to this copy unless they are manually selected for copy from the Job for Storage Policy Copy dialog box or the Select most recent full backup when auxiliary copy starts option has been selected from the Auxiliary Copy Options dialog box.
You can manually select a backup to be copied to a selective copy from the Backups for Copy window of the selective copy. See Manually Select a Backup To be Copied to a Selective Copy for more information.
If you enable the Select Most Recent Full Backup when Auxiliary Copy Starts option when you initiate the auxiliary copy operation in the Auxiliary Copy (Options) dialog box, by default, when the auxiliary copy starts, the most recent full backup of each subclient, including those partially copied, and the previously selected full backup for each subclient will be copied.
In the following example, three full backups are on the primary copy, F1, F2, and F3. When an Auxiliary Copy is run on 9/4, F3 will be copied because it is the most recent full backup.
In another example, if the same auxiliary copy is run on 9/4, but is killed before it is completely copied, F3 may only be partially copied or selected for copy.
If another full backup (F4) occurs on 9/5, and an auxiliary copy is run on 9/6, the partially copied full backup F3 as well as F4 will be copied. If while configuring the Auxiliary Copy Job, you disable the Select Most Recent Full Backup When Auxiliary Copy Starts option in the Auxiliary Copy (Options) dialog box, only the previously selected backup will be copied, thus F4 would not be copied.
If you change the selective copy type or selective criteria and then run an auxiliary copy operation, the auxiliary copy operation will copy the data based on the old and new selective copy criteria.
In the following example, on 6/9 the criteria of a selective copy was changed from being weekly based to monthly based.
If an auxiliary copy is run on 6/30, F1 and F2 are copied because they meet the weekly based criteria. F5 is also copied because it meets the monthly based criteria.
The section describes how auxiliary copy is performed on copies that have other copy features enabled, such as:
An auxiliary copy operation on a copy that has the Defer Auxiliary Copy for <n> day(s) option enabled, data will be copied starting at 12:01 A.M. on the set number of days after valid data becomes available on the source copy. See Deferred Copy for an overview.
An auxiliary copy must be performed on a primary copy that has the Spool Copy (no retention) option enabled, before data on that copy can be pruned the next time data aging is run. It is recommended that regular or automatic auxiliary copy operations are performed for storage policies using spool copies. See Spool Copy for an overview.
| Spool Copy data are aged upon the successful completion of the auxiliary copy job. If a primary copy has the Spool Copy (no retention) option enabled, and there is no coverage for all of the subclients in the secondary copies, the synchronous copy cannot be deleted. Instead, users will be prompted with a message to change the retention period of the primary copy or create another synchronous copy. |
If a data protection operation of a subclient whose storage policy has an inline copy enabled does not successfully create an Inline Copy, then the data will be copied to a secondary copy the next time an auxiliary copy is run. See Inline Copy for an overview.
If storage policy copies are configured with an auxiliary parallel copy, after reading the source copy (only once) data can be copied to multiple secondary copies concurrently rather than sequentially. This optimizes use of media, therefore, decreases the time needed to run auxiliary copy operations. For more information, see Parallel Copy.
If a secondary storage policy copy is enabled with deduplication, then the deduplication store gets created for the copy and the associated data is deduplicated for that copy. See Deduplication for an overview.
For more information, see Data Multiplexing. |
When both primary copy and secondary copy are deduplicated, you can reduce the copy duration using the DASH Copy feature on the source computer while creating secondary copies. To optimize the disk read operations, enable the Disk Read Optimized Copy.
If you wish to process the signature on the source, to see if the signature is present on the target, and if present, send only the signature, you can enable Network Read Optimized Copy.
For more information, see DASH Copy.
Auxiliary Copy normally copies data stream by stream, meaning, if there were four data streams on the primary copy, then the auxiliary copy operation would use four data streams to copy on the secondary copy. Alternatively, auxiliary copy can copy data from a primary copy that has multiple streams to a secondary copy that has less than that number of streams, by using the Combined to <n> Streams option on the copy.
By combining the data streams to less media, this improves media usage as the media storage is optimized. Media recycling is also more efficient, as data aging is more effective as secondary copies of the data reside on less media than what was required for the original data protection operation. The following example illustrates an auxiliary copy operation performed for a copy that combined data streams into one stream:
Multi-stream backups of the Microsoft SQL, DB2, DB2 DPF and Sybase agents will be copied during an auxiliary copy operation to a copy that combines streams; however, restore operations may have limitations. See Browse and Restore for more information.
In order to restore SQL, DB2, DB2 DPF and Sybase agent backups from combined streams of Storage Policy copies, a new Storage Policy copy to disk library must be created and an auxiliary copy should be executed. A restore must be performed from this new copy.
The following example illustrates an auxiliary copy operation performed for a copy that combined data streams into two streams:
When a copy is configured to combine streams, thereby utilizing less media when copying data to a secondary copy, multiplexing can be enabled as well. Data Multiplexing allows data protection operations of multiple data streams to be run concurrently to the same media, which optimizes performance of the auxiliary copy operation in a disk environment.
The following example illustrates an auxiliary copy operation performed for a copy that combined data streams into one stream with multiplexing enabled:
For more information, see:
|
You can select the number of data streams to be copied at the same time during an auxiliary copy operation. This can be achieved by using the maximum number of available streams or from a specified number of streams.
If enough storage resources are available, you can use the Allow Maximum option so that all data streams are copied concurrently during an auxiliary copy operation.
For example, if four streams were required for the auxiliary copy job, then all four streams will be copied in parallel.
Data balancing occurs across multiple streams so that an auxiliary copy will continue to copy in parallel. Note that multiple streams will not be copied in parallel to a copy that combines streams.
|
If not enough storage resources are available, or you do not want to use all available resources, you can select the number of data streams that will be copied at the same time during an auxiliary copy operation.
For example, if four streams were required for the auxiliary copy job, and two streams are selected to copy in parallel, then the auxiliary copy operation will copy two streams at a time. Note that Stream 3 will start when Stream 1 or Stream 2 is completed. Hence, Stream 3 does not have to wait for both Stream 1 and Stream 2 to complete before starting.
When a storage policy is configured to use more than one data stream, it is important that the data streams are equally used; parallel copying using multiple source and destination drives may not be effective if the data is concentrated in one stream. The stream randomization feature enables random choosing of the data streams, increasing the rate of data transfer by copying data from different streams in parallel. See Enable Stream Randomization for instructions.
Also, it is recommended that you configure the tuning parameters to evenly distribute the data across all the streams. You can specify the interval to check the data size in the streams and the threshold to decide data distribution among the streams. See Tune Stream Randomization for instructions.
An auxiliary copy operation copies valid data from a specified source copy of a specific storage policy to all or one active secondary copy within a storage policy. If the source copy for the auxiliary copy operation is configured with a shared library, you will have the ability to select the source MediaAgent from which the auxiliary copy operation will read the data.
|
For step-by-step instructions, see Select a Source MediaAgent for an Auxiliary Copy Operation.
You can start or schedule an auxiliary copy at the storage policy level from the Auxiliary Copy (Options) dialog box.
From this dialog box, you can:
Additionally, from the Auxiliary Copy (Job Initiation) dialog box, you can schedule the auxiliary copy operations that you configured.
From this dialog box, you can:
Data is copied to secondary copies during auxiliary copy operations according to the media of the original data protection operations, per destination copy and data stream. More specifically, the media that contains the oldest job is copied first. From this media, jobs from the primary copy are copied sequentially from oldest to newest so that all jobs from this media are copied before unmounting it. Once all the jobs are copied from this media, auxiliary copy will continue with the next media containing the oldest job within the same drive pool. When all the media in this drive pool are copied, auxiliary copy will start copying the oldest media of the other drive pools that belong to the same library. When all the media in this library are copied, auxiliary copy will continue copying the oldest media of the other libraries for the same MediaAgent. When all the media of this MediaAgent is copied, auxiliary copy will start copying the oldest media of other MediaAgents. Upon completion, if there is more than one stream, auxiliary copy will continue copying on the next stream in the same manner. Therefore, data is copied in the following sequence:
For example, J1 and J2 used media M1. J3 and J4 used media M2. J1 and J2 are copied first, and then J3 and J4.
For example, J1, J2, J3 and J4 used drive pool D1. J5, J6, J7 and J8 used drive pool D2. J1, J2, J3 and J4 are copied first grouped by media and volume. J5, J6, J7 and J8 are copied second.
For example, J1 and J3 used library L1, and J2 and J4 used library L2. J1 and J3 are copied first grouped by media and volume. J2 and J4 are copied second.
For example, J1, J2, J3, J4, J5, J6, J7, and J8 use MediaAgent MA1. J9, J10, J11, J12, J13, J14, J15, and J16 use MediaAgent MA2. J1 through J8 are copied first grouped by media, volume, and drive pool. J9 through J16 are copied second.
See View the Media Not Copied for step-by-step instructions.
When Auxiliary Copy operation is performed, jobs (data) from primary copy to secondary copy are copied sequentially from oldest to newest jobs. During this process, you can set the priorities for jobs to be copied to secondary storage. See Set Job Priorities to Copy during Auxiliary Copy operation for step-by-step instruction.
By default, when a browse or data recovery operation is requested (without specifying copy precedence), the software attempts to browse/restore/recover from the storage policy copy with the lowest copy precedence. If the media for the copy with the lowest precedence is offsite, damaged, or if hardware resources are unavailable, then a specific storage policy copy must be specified in the Copy Precedence tab of the Storage Policy Properties dialog box. For more information, see Change the Copy Precedence.
If the data that you want to browse/restore/recover was already pruned from that copy, the software will search for the requested data from a copy with the lowest copy precedence number to copy with the highest copy precedence number.
In the following example, a storage policy includes three copies, a primary copy (with copy precedence 1) and two additional copies. If File B is unavailable from the primary copy, then, when performing a data recovery operation, data will automatically be restored/ recovered from Copy1 that has a copy precedence of 2.
If, however, the copy precedence of the two copies was changed so that Copy 1 has a copy precedence of 3 and Copy 2 has a copy precedence of 2, then the data recovery operation will be performed from data obtained from Copy 2 that has a copy precedence of 2.
When a copy is configured, the system automatically assigns it a copy precedence number, which you can change at any time.
If you specify a copy precedence number for a data recovery operation, the software searches only the storage policy copy with that precedence number in each of the storage policies through which the data was secured. If data does not exist in the specified copy, the data recovery operation fails even if the data exists in another copy of the same storage policy.
Copy precedence is useful if:
In the following example, a storage policy has a primary copy, Primary1, two copies, Copy 1, and Copy 2. If you choose to browse/restore/recover your data from Copy 2, you must specify that you want to browse/restore/recover from copy precedence 3 so that data will be restored/recovered from that copy.
When you browse at the client, agent, or backup set levels, keep in mind that the data for the subclients included in these levels may have been secured through more than one storage policy. If you specify a copy precedence for a data recovery operation, the data is restored/recovered from the storage policy that has data on the specified copy.
For example, data is restored/recovered at the backup set level that has two subclients, SubA and SubB. SubA uses storage policy SP1 and SubB uses storage policy SP2. SP1 has two copies, Copy1 and Copy2. Copy1 has a copy precedence of 1, and Copy2 has a copy precedence of 2. If copy precedence 2 was selected for the data recovery operation, only data from SubA will restored/recovered.
The Oracle, SAP for Oracle, and SAP for MAXDB iDataAgents provide the capability of restoring data from secondary copies using a third-party command line, such as RMAN and the SAP command line. Using a third-party command line for this operation provides an alternative to the CommCell Console, and is useful for restoring data when the primary copy is unavailable. To utilize this feature, some minor setup configuration is required depending on the agent, as described briefly below:
See Restore Data from a Secondary Copy using a Third-Party Command Line for step-by-step instructions.
You can use the Auxiliary Copy feature to copy your data to selective copies, and then use the Export Media option to keep these copies of your data in a safe offsite location. By defining your selective copy to contain one full backup in a three month period, and by using the Export Media option, you can guarantee that you can keep a secondary copy of full backup data every three months in a safe location. This provides for extra protection in the event of data loss.
To accomplish this:
To guarantee that data will be copied to the selective copy you have defined, create an Auxiliary Copy schedule. This schedule will dictate when the full backup(s) will be copied from the primary copy to the selective copy media. If resources permit, create a schedule to run every day, for example, every day at 9:00 A.M. New, eligible full backups will be copied when the Auxiliary Copy operation is run. No drive resources will be used if no eligible full backups have occurred since the last Auxiliary Copy was performed for the Storage Policy.
Once you have copied your data to selective copies using auxiliary copy operations, you can now export your media to keep it in a safe offsite location.
If you want to take the tapes out manually (either by opening the library door or through selecting a list), run the Media Information report. Based on the report, (which you can to run at the same frequency and options as above) the tapes may be manually exported.
The Skip job on read errors during Auxiliary copy option specifies whether the Auxiliary Copy job will skip data protection jobs that encounter errors during auxiliary copy operations. If you have many data protection jobs that need to be copied, this option will allow the auxiliary copy job to continue copying other data protection operations while skipping over those jobs encountering errors. This option is enabled by default. However, if you disable the option and the Auxiliary Copy job encounters an error, it will return with a Pending status and not continue. The Skip job on read errors during Auxiliary copy option can be modified from the Media Management Configuration (Auxiliary Copy Configuration) dialog box available in the Control Panel. If you continue to encounter errors, contact your software provider.
| Pending reasons are displayed in the Reason for Job delay field, which is located in the Administration Job Details (General) tab. |
For more information regarding the effects if an error is encountered during auxiliary copy operations, please refer to the following table.
| If The Following Error Occurs | Then |
| Source Media Error/Source Media Not Available | The auxiliary copy job will continue copying other data protection jobs while skipping over that media. Upon completion of all jobs that need to be copied, the jobs on the skipped media will be attempted to be copied again. Note that when it skips the media – it skips all the jobs on that media. If the first source media is not available, wait. |
| Read Error | The auxiliary copy job will continue copying data protection jobs while skipping over the portion of the job with the read errors. Upon completion of all jobs that need to be copied, the skipped portions will be attempted to be copied again. |
| Target Media Mount Error | The auxiliary copy job will retry the operation. If error still exists, the job will go into Pending state. |
When defining the rules for a selective copy in the Copy Properties (Selective Copy) dialog box, it is recommended to select the Select Full Backups at frequency option. Selecting the Copy most recent full backups when Auxiliary Copy starts option will copy the most recent full backup of each subclient, including those partially copied, and the previously selected full backup for each subclient. For more information, see Most Recent Full Backup Selective Copy.
If the default data path on the primary copy of a storage policy points to a drive pool configured on a MediaAgent enabled with NDMP Remote Server (NRS), then the secondary copy must also point to a drive pool configured on a MediaAgent with NRS installed in order to restore the data to a NAS file server.
Only for EMC Celerra 5.5 must the library be directly attached to the Celerra file server. For EMC Celerra 5.6 or higher, when a Celerra file server is backed up using the Volume-Based Backup option, three-way backups, three-way restores, and NDMP Remote Server (NRS) are available. For this reason, you can perform an Auxiliary Copy operation that would copy a Volume-Based Backup to a library that is not attached to the Celerra file server, because it is possible to restore that data.
To prevent a job from being copied to the same library during auxiliary copy operations, select the Write to a Different Library Compared to Source Copy option in the Copy Properties (Media) dialog box.
Inline Copy
The Copy Properties (Data Path Configuration) dialog box includes the following options for auxiliary copy operations that will assist with controlling network load.
While data encryption provides pass-phrase, key management, and network encryption support, you can also encrypt storage policy copies using auxiliary copy encryption. This capability allows you to select portions of data you wish to encrypt, does not require client encryption configuration, and provides faster encryption performance.
See Auxiliary Copy Operations and Encryption for more information.
Operations for this feature can be scheduled to run on a regular basis. To create a job-based schedule for this feature in your CommCell environment, see Create a Job Schedule.
If you have a large number of clients/backup sets/subclients, or storage policies in your CommCell that require the same schedule, it may be more beneficial to create a schedule policy for this operation; see Create a Schedule Policy.
Configure the auxiliary copy fallen behind alert so that you are notified when the data to be copied for the associated storage policy exceeds the threshold and/or the number of days the jobs for the associated storage policy have not been copied exceeds the set threshold. The thresholds for this alert can be set in the Storage Policy Properties (Advanced) window. For more information, see Alerts: Job Management.
On a Selective Copy, if you have selected Automatically select Full Backups at frequency option with Advanced - Every <x> Cycle(s) option, then the job selection will be done based on the Mod Logic.
The Mod Logic is implemented as follows:
N mod x
Where:
N - is the cycle number of a backup job as seen under Cycles/Sequence column in the Job for Storage Policy/Storage Policy copy window, which will appear by right-clicking the Storage Policy, pointing to All Tasks and then clicking View Jobs.
x - is the number of cycles defined in the Every <x> Cycle(s) option in the Advanced Options dialog box.
Example:
In case of backup cycles N = 18, 19, 20 e.t.c., these backups will not qualify for copy selection because of mod logic.
If you wish to copy alternate cycle jobs (i.e., one odd and one even) to different copies then perform the following:
In the Selective Copy tab, from the Automatically select Full Backups at frequency list select Advanced.
In the Advanced dialog box select Every <x> Cycles and specify the value as 2.
Select First Full Backup option.
Click OK.
In the Selective Copy tab, from the Automatically select Full Backups at frequency list select Advanced.
In the Advanced dialog box select Every <x> Cycles and specify the value as 2.
Select Last Full Backup option.
Click OK.
This allows you to copy the alternate cycles jobs to two different copies by implementing the mod logic explained in the above FAQ.
The following Job Management Auxiliary Copy alerts can be configured from the Alerts Wizard:
For more information, see:
The Administrative Job Summary Report displays a summary of all or select Administrative jobs.
The Auxiliary Copy Job Summary Report displays auxiliary copy jobs and associated details.
The Jobs in Storage Policy Copies Report displays the data protection jobs associated with the storage policy copies.