Storage Policy Copy - FAQ

Table of Contents

General

Which copy is selected for the browse or restore operation?

By default, when a browse or restore operation is performed (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.

How can the job still be pruned when it is manually retained?

If a job is manually retained, it will still be pruned as a result of the following operations:

  • Deletion of a backup set or instance/partition
  • Deletion of a Storage Policy
  • Deletion of a Storage Policy copy
  • The Overwrite Media option is enabled on the library
  • Deleting the contents of a media

How do I configure data path on secondary storage policy copy to restore data from NAS file server?

In order to restore the data to a NAS file server, if the default data path on the primary copy of a storage policy points to a drive pool configured on a MediaAgent, then the secondary copy must also point to a same drive pool configured on the MediaAgent.

Why is job with Not Selected status not getting picked up for Re-Copy operation?

You can re-copy Not Selected jobs only by using  MarkJobsOnCopy qscript. For instructions, see MarkJobsOnCopy.

Selective Copy

How do I convert a synchronous copy to a selective copy?

You can convert synchronous copy to selective copy using the below qscript.

Improper use of the QS_ConvertSyncToSelectiveCopy qscript might result in data loss. Before you run this script, contact your software provider.

  1. From the command prompt, go to <software_installation_directory>\Base.
  2. Log on to the CommServe using the qlogin command.
  3. Run the following qscript to convert the synchronous copy to selective copy:

    Syntax:

    qoperation execscript -sn QS_ConvertSyncToSelectiveCopy -si "StoragePolicyName" -si "StoragePolicyCopyName"

    Example:

    qoperation execscript -sn QS_ConvertSyncToSelectiveCopy -si "Storage Policy01" -si "Secondary_Copy01"

    When the synchronous copy is converted, the selective copy will have All Fulls option selected as default backup frequency.

    For more information on modifying the selective copy criteria, see Configuring the Frequency of Backups for the Selective Copy.

Can I include database backups into a selective copy?

Yes, database full backups that are consistent can be included in a selective copy.

  • For Oracle, Oracle RAC and SAP Oracle only selective online full backups and offline full backups can be copied to a selective copy.
  • For other database agents like SQL, DB2 and Sybase, full backups that have linked log backups can be copied to selective copy.

Why is my most recent job not selected even though the backup schedule is disabled?

If you have Last Full Backup with Select most recent job if there are no more full backup schedules in current time period options enabled on a selective copy to pick up most recent jobs and if you have disabled the backup schedules recently, then the job will be selected only after the backup schedule period. This is because the status (enabled or disabled) of the backup schedule will not be considered during job selection until the schedule is deleted.

How does the job selection work with advanced cycle-based criteria?

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

  • If N mod x is 1 then only first full backup jobs will be selected.
  • If N mod x is 0 then the last full backup jobs will be selected.

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:

  • If N = 3 and x = 2, then N mod x => 3 mod 2 = 1 - the backup will qualify as a first full backup.
  • If N = 2 and x = 2, then N mod x => 2 mod 2 = 0 - which means that backup will qualify as last full backup for the copy, if last full backup option is selected.
  • If you have specified Every <x> Cycles (s) values as 4 (i.e., x = 4) during selective copy creation and selected First Full Backup option and during copy creation if the number of backup cycles on a source copy is 16 (i.e., N = 16), then:
    • 16 mod 4 = 0 and this backup will not qualify as first full backup for this newly created selective copy as the mod value is 0.
    • If the backup cycle value is 17 (i.e., N = 17), then 17 mod 4 = 1, this backup will be qualified for copy as first full backup for this copy.

    In case of backup cycles N = 18, 19, 20 e.t.c., these backups will not qualify for copy selection because of mod logic.

How do I convert a selective copy to synchronous copy?

If you already have a selective copy created and you want to convert the copy type from selective to synchronous, do the following:

  1. From the command prompt, go to <software_installation_directory>\Base.
  2. Log on to the CommServe using the qlogin command.
  3. Run the following qscript to convert the selective copy to a synchronous copy.

    Syntax:

    qoperation execscript -sn ConvertSelectiveToSyncCopy -si "StoragePolicyName" -si "StoragePolicyCopyName"

    Example:

    qoperation execscript -sn ConvertSelectiveToSyncCopy -si "SP" -si "Selective Copy"

Inline Copy

How does the Inline Copy use the media drive efficiently?

The Inline copy enables efficient utilization of the drives on the media. The following figures illustrate the two methods of creating a secondary copy of the data and the drive utilization for each method:

Backup Operation and Auxiliary Copy Operation

This method involves two operations:

  • Backup Operation - It writes data to Primary Copy.
  • Auxiliary Copy Operation - It reads data from Primary Copy and writes it to the secondary copy.

This method uses the drive three times.

Backup Operation with Inline Copy

This method involves only one operation:

Backup Operation - This operation writes data simultaneously to the Primary Copy and the Inline Copy. However, this operation takes longer time to complete as compared to the backup operation without an inline copy.

This method utilizes the drive twice.

How does the Inline Copy reduce the delay in the offsite storage?

An Inline copy reduces the delay in the offsite storage of the data. The following figure illustrates the two methods of creating a secondary copy and the delay in offsite storage for each method.

Backup Operation and Auxiliary Copy Operation

In this method the auxiliary copy operation is performed after the operation window for the backup operation is over. This causes the delay in the offsite storage.

For example: The operation window for backup operations occurs between 6 p.m. to 6 a.m. Auxiliary copy operations are then conducted between 6 a.m. and 6 p.m. immediately following the backup operation window. Hence, data is available for offsite storage after 6 p.m.

Backup Operation with Inline Copy

In this method the secondary copy is created during the operation window for the backup operation. However, the backup operation takes longer time than the backup operation without an inline copy.

For example: The operation window for the backup operation that creates an inline copy is from 6 p.m. to 10 a.m. Hence, data is available for offsite storage after 10:00 a.m. The additional drive time needed to create the inline copies is four hours.

How many Inline Copies can be created for a storage policy?

A maximum of ten inline copies can be created for a storage policy.

How many data streams are required to perform the backup operation with Inline Copy?

If you have configured only one inline copy for a storage policy, then the backup operation will require two data streams. One for Primary copy and another for inline copy.

Can I create an Inline Copy for a storage policy that uses a library that is attached to the NAS file server?

No. You cannot create an inline copy for a storage policy if the storage policy is using a library attached to a NAS File Server. You must perform an Auxiliary Copy operation to replicate the data from the primary copy to additional copies.

Can I back up the multiplexed data to a deduplicated Inline Copy?

No. You cannot copy multiplexed data to an Inline Copy with Deduplication option enabled.

How does data encryption work with Inline Copies?

If a backup operation from a subclient whose storage policy has an inline copy enabled does not successfully create the Inline Copy, that data will be copied to a secondary copy the next time an auxiliary copy is run, and will be encrypted at that time

Can I enable Inline Copy on a source-side deduplication copy?

No. Inline Copy is not supported for source-side deduplicated storage policy copies.

Spool Copy

Can I delete a synchronous copy if the spool copy option is enabled for a primary copy?

No. Synchronous Copy cannot be deleted if the Spool copy option is enabled for a Primary Copy.  If you want to delete the synchronous copy you must perform one of the following:

  • Change the Retention Rule for Primary copy to increase the retention period
  • Create another Synchronous Copy which has data from all the subclients associated with the primary copy