Alternate Data Paths (GridStor) - Troubleshoot

Topics | How To | Troubleshoot | Examples | Support | Related Topics


Troubleshoot Data Paths

No available data path candidates to add

Backups fail with an Index Not Available error

Increased media usage, after establishing data paths in the CommCell

Backups to a storage policy copy with multiple data paths are in the Waiting state

Jobs Using the library go into Waiting

Backups on Unix MediaAgents fail with an Index Not Available error

Multi-streamed database backups always remain in the Waiting state

Backups do not automatically use an alternate data path soon after the time indicated in the Criteria for Alternate Data Path

Although common data paths are defined in primary and secondary copies, another data path is being used for Auxiliary Copy operations

Troubleshoot Shared Indexes

Access Denied to the Shared Index Cache Directory

Unable to Browse data

Index processing on MediaAgent failed due to a CreateIndex processing error


No available data path candidates to add

This might occur for the following reason:

Cause: You may not have shared the index cache for the MediaAgent(s) that you wish to add as a data path candidate.

Solution:  Check your criteria for using alternate data paths. (See Select the Criteria for using an Alternate Data Path for more information.)

Depending on the selected criteria, you may have to share the index cache for the MediaAgent(s). Share the index cache and then add the necessary data paths. See Index Cache for information on index cache sharing.


Backups fail with an Index Not Available error

This might occur for the following reason:

Cause: All the MediaAgents associated with the data path candidates may not be pointing to the same network share and the same folder within this network share for its index cache location..

Solution:  For all the MediaAgents that are used as a data path candidate, open the Catalog tab of MediaAgent Properties, and verify whether the Index Cache Directory points to the same network share and the same folder within this network share for its index cache location.


Increased media usage, after establishing data paths in the CommCell

This might occur for the following reasons:

Cause: Fail over to data path candidates may be marking the media from last used library as Appendable resulting in partial usage of media.

Solution: Enable the option to reuse Appendable media, as described in Reuse Media Marked as Appendable.

----------------------------------------------------

Cause:

Solution:

Reduce the number of streams to the following:


Backups to a storage policy copy with multiple data paths are in the Waiting state

This might occur for either of the following reason:

Cause: The criteria for using an alternate data path may not be selected.

Solution: Select the criteria for using an alternate data path as described in Select the Criteria for using an Alternate Data Path.

----------------------------------------------------

Cause: All the resources associated with all the data paths may not be available .

Solution: Verify the following resources and if possible enable the resources associated with at least one data path.


Jobs Using the library go into Waiting

The Reason for the Job Delay in the Job Details dialog box may display the message No Resource available.

Cause: The Device Streams assigned in the Storage Policy Properties associated with the library is greater than the number of drives available in the library.

Solution: Make sure that the Device Streams assigned is equal to the number of drives in the library.

If you have added alternate data paths to the primary copy of the storage policy, the number of streams must be equal to the sum of drives available in all the libraries associated with all the data paths.


Backups on Unix MediaAgents fail with an Index Not Available error

Cause: The mount point to the index cache folder may not be mounted. Note that mount points are not automatically mounted when a Unix MediaAgent is rebooted.

Solution:

  1. From the Catalog tab of MediaAgent Properties, verify the location of the Index Cache Directory for the MediaAgent.
  2. Mount the folder containing the index cache using the same path specified in Index Cache Directory.
  3. Re-run the backup.

Multi-streamed database backups always remain in the Waiting state

Cause:

You may have defined more number of streams than the actual number of drives in the library associated with the default data path candidate.

Solution:

  1. Kill the backup job.
  2. Reduce the number of streams in the Storage Policy Properties dialog box.
  3. If necessary, reduce the number of streams in the Subclient Properties (Storage Device) tab, associated with the backup.
  4. Re-run the backup.

----------------------------------------------------

Cause:

The resources on the default data path candidate may not be available and each of the alternate data paths do not have sufficient number of drives.

Solution:

  1. Verify the following resources and enable the resources associated with the default data path.
  2. Add an alternate data path with sufficient number of physical drives to support this backup.

Backups do not automatically use an alternate data path soon after the time indicated in the Criteria for Alternate Data Path

This might occur for the following reasons:

Cause: The time indicated in the Criteria for Alternate Data Path, is the minimum time that the system will wait before using an alternate data path. The actual switch over will occur only when the backup job is processed by the Job Manager and depends on the number of jobs in the Job Manager at that time.

Solution: The backup job will automatically complete, when the Job Manager processes the job and the time indicated in the criteria for alternate data path is reached.


Although common data paths are defined in primary and secondary copies, another data path is being used for Auxiliary Copy operations

This might occur for the following reasons:

Cause: If alternate data paths are selected on secondary copies the system will always strive to perform LAN-free Auxiliary Copies.

Consider the diagram on the right. Using this configuration as an example, we can setup the following data paths:

Storage_policy_1= Primary Copy

MediaAgent 1, Library 1, Drive Pool 1, Default scratch Pool (Default path)

MediaAgent 2, Library 2, Drive Pool 2, Default scratch Pool (alternate path)

Storage_policy_1= Secondary Copy

MediaAgent 3, Library 1, Drive Pool 3, Default scratch Pool (Default path)

MediaAgent 3, Library 2, Drive Pool 4, Default scratch Pool (alternate path)

MediaAgent 1, Disk Library 1

MediaAgent 2, Disk Library 2

Assume that a full and incremental backup was performed. The data associated with the full backup resides in Library 1with media ID 0001. During the incremental backup the alternate data path was used and hence the incremental backup data resides in Library 2 with media ID 0002.

When an Auxiliary Copy operation is run on the secondary copy, MediaAgent 3 will be used to perform the operation. This is because MediaAgent 3 has access to both the libraries, and thus can read from media used by both MediaAgent 1 and MediaAgent 2.

Solution: This setup may be advantageous as it uses no network resources for the Auxiliary Copy operation. If however, you wish to remove this setup, remove the alternate data paths from the Secondary Copy.

Access Denied to the Shared Index Cache Directory

This might occur for either of the following reasons:

Cause: Trust relationships between the MediaAgent's domains and the domain in which the shared index cache resides may not be established.

Solution: Contact your Network Administrator to setup trust relationships between the domains.


Unable to Browse data

Cause:

MediaAgent is not upgraded. An index cache entry created by a MediaAgent in the current version is accessed by a MediaAgent in the previous version.

Solution:

Upgrade the MediaAgent.


Index processing on MediaAgent failed due to a CreateIndex processing error

Cause:

MediaAgent is not upgraded. An index cache entry created by a MediaAgent in the current version is accessed by a MediaAgent in the previous version.

Solution:

Upgrade the MediaAgent.