Storage Rules

View configuration information for storage rules.

The following types of storage rules are shown on the Storage Rules page:

Tiering storage rules: Tiering storage rules define your organization's policies for automatically moving data from disk storage to cloud or tape storage. Initially, data is backed up to directory-container storage pools, which are defined on disk, to take advantage of typically faster read and write capabilities. Tiering storage rules specify how long the data remains in disk storage before the server moves the data to cloud or tape storage. Both cloud and tape storage can provide a cost-efficient solution for maintaining data that is infrequently accessed.
Copy storage rules: Copy storage rules define your organization's policies for copying client data to tape storage. Data is backed up to directory-container storage pools and later copied to tape. By specifying copy storage rules, you can control the scheduling of backup operations to tape and the amount of data that is copied.
Replication storage rules: Replication storage rules define your organization's policies for replicating client data from source replication servers to target replication servers. The storage rule is defined on the source replication server. The storage rule specifies the target replication server and a schedule for replicating client data. Client data can be replicated only if the client is enabled for replication.
Some replication storage rules are created and managed by Open Snap Store Manager (OSSM). You cannot modify or delete these storage rules. For more information about replication storage rules that are managed by OSSM, see the following description of the OSSM Managed column.
Retention-copy storage rules: Retention-copy storage rules define schedules for copying retention set data from primary storage to tape storage or cloud object storage. You do not explicitly create a retention-copy storage rule. Instead, a retention-copy storage rule is automatically created when you create a retention storage pool. A retention storage pool can represent a supported cloud object storage environment or a collection of tape devices of the same type. The retention storage pool's associated retention-copy storage rule defines a daily processing window during which retention sets can be copied to the retention storage pool. You cannot explicitly delete a retention-copy storage rule. Instead, a retention-copy storage rule is automatically deleted when its associated retention storage pool is deleted.

The following actions and configuration details are available on the page:

Create Rule

This action does not apply to retention-copy storage rules. A retention-copy storage rule is automatically created when you create a retention storage pool.

To create a storage rule, start by selecting a server on which to define the storage rule. You also specify whether you are defining a tiering storage rule, a copy storage rule, or a replication storage rule.

Each storage rule has a source for the data that is processed by the storage rule, and a target for the data. Depending on the type of storage rule, the following sources and targets are identified:

For a tiering storage rule, you specify one or more source pools. The source pools are the directory-container storage pools where data is originally backed up. For the target, you specify the cloud-container or tape storage pool to which eligible data can be tiered.
For a copy storage rule, you specify one or more source pools, which can be directory-container storage pools or on-premises cloud-container storage pools. For the target, you specify the copy storage pool to which eligible data can be copied.
For a replication storage rule, the source replication server is the server on which the storage rule is defined. The target replication server is the server to which data is replicated.

You also specify properties that control when and how the rule runs. You can specify the following properties, which are common to all storage rule types:

Whether the rule is active or inactive. An active rule runs daily at its scheduled start time. An inactive rule runs only if it is explicitly started. An inactive rule can be explicitly started by using the Run Now action.
The daily start time of the storage rule when it is active.
The maximum number of parallel processes to use for moving or copying data.
A maximum run time for the storage rule. The storage rule stops running when this limit is reached. You can also specify that the run time is not limited. When no limit is specified, all eligible data is moved or copied when the storage rule runs.

Other properties of the storage rule depend on the type of storage rule. For example, for tiering storage rules, you specify an age threshold for how long data must remain on disk before it can be tiered to lower-cost tape or cloud storage. For tiering storage rules, you can also specify whether all data or only inactive data is tiered.

You can specify whether the storage rule identifies the data to move or copy from the source, or whether data is moved or copied only as specified by subrules of the storage rule. If the storage rule identifies the data to move or copy from the source, subrules can specify exceptions to the rule for data from particular clients. If the storage rule specifies that data is moved or copied only as specified by subrules, one or more subrules must be defined. If no subrule is defined, no data is moved or copied when the parent storage rule runs.

Details

Use this action to view properties and historical information about a selected storage rule.

Create Subrule

Use this action to create a subrule. A subrule specifies exceptions to a parent storage rule for the specified clients. This action does not apply to retention-copy storage rules, which do not support subrules.

Subrules give you finer control over how data is moved or copied for individual clients. The parent storage rule can specify default behavior for moving or copying data, and its subrules can specify exceptions that apply only to certain clients. For tiering and copy storage rules, subrules can specify exceptions for virtual machines (VMs). For replication storage rules, subrules can specify exceptions for VMs and other file spaces.

For example, if you don't want a copy storage rule to back up all client data from its source storage pools, you can create a subrule that excludes certain clients. If you do not want the storage rule to copy data for all clients to the same copy storage pool, you can create a subrule that specifies a different destination for some clients.

A parent storage rule can specify that no data is moved or copied unless specified by one of its subrules. In this case, one or more subrules must be defined, or no data is moved or copied when the parent storage rule runs.

Run Now

Run the selected storage rule immediately. An active storage rule runs daily at its scheduled time. However, you can use this action to run an inactive storage rule, or to run an active storage rule without waiting for its scheduled time.

Delete

This action does not apply to retention-copy storage rules. A retention-copy storage rule is automatically deleted when its associated retention storage pool is deleted. To delete a selected storage rule, click Delete. When you delete a storage rule, you also delete any subrules that are associated with the storage rule.

Rule Name

The name of the storage rule. For retention-copy storage rules, the rule name is the same as its associated retention storage pool.

Status

The status from the most recent run of the storage rule and its subrules. The most severe status of the rule and any of its subrules is shown. To display a status breakdown of the parent rule and its subrules, hover over the status value. To view an explanation of a Warning () or Failed () status value, hover over the status value.

Tip: If a storage rule is unable to begin processing, no new status is available and the Status column continues to show the status from the previous run of the storage rule. For this reason, you might see indications that a storage rule did not run, but no failure status. A storage rule is unable to begin processing if its target is unavailable. To check the status of a target pool, open the Storage Pools page (click Storage > Storage Pools). To check the status of a target server for replication, open the Servers page (click Servers > Servers). To run a storage rule, the Operations Center issues the START STGRULE command in the background. To determine whether the START STGRULE command ran successfully, open the Maintenance page (click Servers > Maintenance).

The following states can be shown:

Normal

The storage rule completed processing without errors. Data was successfully moved or copied according to the rule's specifications. Processing was completed within the specified maximum duration.

Warning

The storage rule completed processing, but with warnings. The storage rule could not move or copy all data. Possible reasons why the storage rule could not move or copy all data include the following reasons:

Some files were skipped during processing because the files were in use, damaged, moved, or deleted.
Some files were skipped because a storage pool is inaccessible, or because one or more storage pool directories are inaccessible.
For a tiering storage rule, some files were skipped because copy operations for a copy storage rule were pending. If copy operations are pending, files are tiered only after they are copied.
Storage rule processing was canceled. A storage rule process might be canceled by an administrator. The server can also automatically cancel storage rule processing if the storage rule's maximum run time was reached. If a storage rule regularly times out, you can edit the rule to increase its maximum run time. You can also specify that a rule's maximum run time is unlimited by selecting the No limit checkbox when you create or modify the rule. In that case, all eligible data is moved or copied when the rule is processed. If you suspect that other scheduled tasks, such as backup operations, are affecting performance, you can adjust their daily start times.

If files were skipped during processing, the server attempts to move or copy the files the next time the storage rule runs.

Failed

The storage rule did not complete processing. The server could not move or copy data. Possible reasons why the storage rule could not move or copy all data include the following reasons:

The server could not access a directory in the source pool.
The server could not access a tape drive or the tape drive reported an I/O error.
No tape drives were available.
The target pool had insufficient space.
The server could not access a target pool that is a cloud-container storage pool. The cloud credentials that it supplied to the cloud storage service were invalid.

Running

The storage rule is processing. Data is being moved or copied based on the storage rule type and its specifications.

Unsupported

The server on which the rule is defined is running a version of IBM Spectrum Protect that does not support status information for the storage rule type.

Unknown

The status of the storage rule process cannot be obtained. Ensure that the IBM Spectrum Protect server on which the rule is defined is running, and that there are no network issues.

— Not Applicable

Storage rule process status is not applicable because the storage rule is not activated, or the storage rule was not run.

Action

Species the move or copy action that is performed by the storage rule.

A tiering storage rule can perform the following actions. The storage rule might have subrules, which specify exceptions to the rule for certain clients.

Tier all data that reaches a specified age threshold.
Tier only inactive data that reaches the specified age threshold.
Tier by subrule. The parent rule tiers no data; all tiering is specified by one or more subrules of the parent rule.

A copy storage rule can perform the following actions. The storage rule might have subrules, which specify exceptions to the rule for certain clients.

Copy all data from the source pools.
Copy by subrule. The parent rule copies no data; all copying is specified by one or more subrules of the parent rule.

A replication storage rule can perform the following actions to replicate data from a source replication server to a target replication server. A client's data is eligible for replication only if the client is enabled for replication and is configured as the source of data for replication.

Replicate all client data to the target replication server.
Replicate by subrule. The parent rule replicates no data; all replication is specified by one or more subrules of the parent rule.
Replicate except by subrule. Replicate all data unless subrules of the parent rule are defined. The subrules of the parent rule identify clients, file spaces, or virtual machines that are not to be replicated.

A retention-copy storage rule copies retention set data from primary storage to its associated retention storage pool.

Source

The source of the data for the storage rule action.

For tiering storage rules, the source is the directory-container storage pool from which eligible data is tiered when the tiering storage rule is run. If eligible data is tiered from more than one storage pool, the number of storage pools is displayed. You can hover over the number to see the names of the source storage pools.

For copy storage rules, the source can be a directory-container storage pool or an on-premises cloud-container storage pool.

For replication storage rules, the source is the source replication server. Eligible client data on the source replication server is copied to a target replication server.

For retention-copy storage rules, the source is retention set data in primary storage for all retention sets that specify the retention-copy storage rule's associated storage pool.

Target

For tiering, copy, and retention-copy storage rules, the target is the storage pool to which data is moved or copied according to the storage rule action.

For replication storage rules, the target is the target replication server.

A retention-copy storage rule is automatically created when a retention storage pool is created. For a retention-copy storage rule, the target is its associated retention storage pool.

Server

The name of the server for which the storage rule is defined.

Scheduled

The storage rule's daily start time and maximum duration. When the storage rule is active, the server starts processing the rule within 5 minutes of the scheduled time. If the server cannot move or copy all eligible data to the target pool or target server within the maximum time, the storage rule is canceled. If no maximum duration is specified, the storage rule is configured to run to completion.

Active

Indicates whether the storage rule is active. An active storage rule is processed at its scheduled time. A checkmark indicates that the storage rule is active.

Subrules

If a subrule is specified for a storage rule, the name of the subrule is displayed. If more than one subrule is specified for a storage rule, you can hover over the number to view the subrule names.

OSSM Managed

Open Snap Storage Manager (OSSM) enables an IBM Spectrum Protect Plus server to back up virtual machine snapshots to directory-container storage pools that are managed by IBM Spectrum Protect. An OSSM instance is installed on the same system as the IBM Spectrum Protect server and is a gateway through which the IBM Spectrum Protect Plus server can access IBM Spectrum Protect resources.

On the IBM Spectrum Protect Plus server, service level agreement (SLA) policies, also known as backup policies, define parameters for backup jobs. These parameters include the frequency and retention period of backups and the option to replicate backup data. Based on these SLA policies, OSSM defines and manages IBM Spectrum Protect entities, such as clients and policies, to satisfy the SLA requirements. If SLA policies on the IBM Spectrum Protect Plus server enable replication of backup data, OSSM creates replication storage rules and subrules on the IBM Spectrum Protect server to replicate the data. These replication storage rules are managed exclusively by OSSM on behalf of the IBM Spectrum Protect Plus server. Although you can view status and performance information for OSSM-managed storage rules, you cannot modify or delete these storage rules. To change the replication configuration, you can instead modify the SLA policies on the IBM Spectrum Protect Plus server.

To edit a storage rule, select the rule and click Details, Properties, and Modify.