Alternate Data Paths (GridStor) - Examples

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


Configuring Alternate Data Paths for Subclients - Examples

Configuring Alternate Data Paths for Secondary Copies - Examples

Configuring Alternate Data Paths using Windows MediaAgents connected to SAN Volumes


Configuring Alternate Data Paths for Subclients - Examples

The following examples illustrate how to use the subclient data paths to effectively reduce media utilization.

Example 1

In this example, a set of clients point to Storage Policy 1 while another set of clients points to Storage Policy 2. Each of these storage policies are configured with the default and alternate data paths using two MediaAgents to ensure that data protection operations succeed when a component in the default path is not available. However, media consumption will be high as by default, each storage policy writes to a media. (Storage Policies cannot be configured to share the same media.) In the sample diagram shown in the right, all client data routed through Storage Policy 1 will utilize a media and all data routed through Storage Policy 2 will utilize another media. Further, when a failover occurs additional media will be utilized by the new data path. This can be overcome by defining subclient data paths, as described below.
   
To ensure that all data protection operations utilize the same media, you can create one storage policy with both the data paths configured. This storage policy is in turn used by all the clients. But within their subclients MediaAgent 1 is set as the default data path and MediaAgent 2 as the alternate data path for the first set of clients and vice-versa in the second set of clients. Note that in this case it is not necessary to share the index, as the MediaAgents and libraries are connected in the SAN.
   

Example 2

In this example, client group 1 has a set of clients which utilize MediaAgent 1 and MediaAgent 2, while client group 2 has another set of clients that utilize MediaAgent 3 and MediaAgent 4. Both these clients groups with their appropriate MediaAgents are separated by a firewall. As with example 1, media utilization will be more if 2 storage policies are defined to accommodate this setup.

As illustrated in the sample diagram shown in the right, the solution is to define one storage policy with four data paths that utilize each all the available MediaAgents. Further, all the clients in client group 1 can be configured with subclient data paths pointing to MediaAgent 1 and MediaAgent 2 and all the clients in client group 2 can be configured with subclient data paths pointing to MediaAgent 3 and MediaAgent 4. This will ensure both failover protection as well as  minimal media utilization.


Configuring Alternate Data Paths for Secondary Copies - Examples

The following examples illustrate how to use the secondary copies with data paths to perform Auxiliary Copies.

Example 1

 
In this example the MediaAgents perform LAN-free operations using a disk library for the primary copy and a tape/optical library for creating the secondary copies.

The primary copy is created by backing up data to a local  disk using the following data paths in the primary copy:

  • Default Data Path: MediaAgent 1, Disk Library 1
  • Alternate Data Paths: MediaAgent 2, Disk Library 2; MediaAgent 3, Disk Library 3

The MediaAgents are connected to a library (Library 1) in the SAN environment and Auxiliary copies to tape are made using the following data paths in the secondary copies:

  • Default Data Path: MediaAgent 1, Library 1, Drive Pool 1 and Scratch Pool 1
  • Alternate Data Paths: MediaAgent 2, Library 1, Drive Pool 2 and Scratch Pool 2; MediaAgent 3, Library 1, Drive Pool 3 and Scratch Pool 3

Make sure that the Use Preferred Datapath option is enabled to ensure that the system automatically perform LAN free operation wherever possible.

   

Example 2

 
In this example, the MediaAgents perform LAN-free operations using a tape/optical library for creating both the primary and secondary copies.

For MediaAgents 1 and 2:

The primary copy is created with the following data paths:

  • Default Data Path: MediaAgent 1, Library 1, Drive Pool 1 and Scratch Pool 1
  • Alternate Data Paths: MediaAgent 2, Library 1, Drive Pool 2 and Scratch Pool 2

The secondary copy is created with the following data paths:

  • Default Data Path: MediaAgent 3, Library 1, Drive Pool 3 and Scratch Pool 3
  • Alternate Data Paths: MediaAgent 4, Library 1, Drive Pool 4 and Scratch Pool 4

For MediaAgents 3 and 4:

The primary copy is created with the following data paths:

  • Default Data Path: MediaAgent 3, Library 1, Drive Pool 3 and Scratch Pool 3
  • Alternate Data Paths: MediaAgent 4, Library 1, Drive Pool 4 and Scratch Pool 4

The secondary copy is created with the following data paths:

  • Default Data Path: MediaAgent 1, Library 1, Drive Pool 1 and Scratch Pool 1
  • Alternate Data Paths: MediaAgent 2, Library 1, Drive Pool 2 and Scratch Pool 2

Make sure that the Use Preferred Datapath option is enabled to ensure that the system automatically perform LAN free operation wherever possible.


Configuring Alternate Data Paths using Windows MediaAgents connected to SAN Volumes

Assume you have two MediaAgents and one LUN volume configured as follows:

To configure alternate data paths on these MediaAgents, perform the following configurations:

Configure a Shared Disk Library

  1. Configure a Shared Disk Library using MediaAgent 1 and MediaAgent 2.

    Refer to the Configure Shared Disk Libraries With Static Mount Paths procedure to perform this operation.

Share the Index Cache between the MediaAgents

  1. Configure MediaAgent 1 for index cache sharing to make the index available for MediaAgent 2 and to allow alternate data paths for storage policies.

    Refer to the Configure a MediaAgent for Index Cache Sharing procedure to perform this operation.

Configure Data Path on a Storage Policy

  1. Create a storage policy and configure it to use the library from MediaAgent 1.
  2. For a storage policy copy, add the library from MediaAgent 2 as Data Path. Refer to the Add a Data Path to a Storage Policy Copy procedure to perform this operation.