< Previous  | TOC | Index | Next  >

Adding a bunker to an RDS

This section describes adding a bunker to an existing RDS. If the RDS already includes a Secondary, adding a bunker does not interrupt replication from the Primary to the Secondary. You can also add the bunker to the RDS before adding the Secondary. Each bunker can support one or more Secondaries. An RDS can only contain one bunker.

A bunker can be configured in one of the following ways:

• Using network (IP) connectivity to the bunker host

  If the bunker host has IP connectivity to the Primary, the Primary replicates to the bunker SRL using standard VVR replication over the network using TCP or UDP protocol.

• Using direct access to bunker storage

  This configuration uses any direct connectivity such as IP over Fiber Channel, Direct Attached Storage (DAS) or Network Attached Storage (NAS) between the bunker storage and the Primary. In this case, the disk group containing the bunker SRL is imported on the Primary host, and the Primary writes to the bunker storage.

  ---

    Note   You cannot add data volumes to a bunker.

  ---

 To add a bunker when the bunker host is accessible by IP

The steps for adding a bunker are the same whether the Primary uses a private disk group or a shared disk group.

1. Create a new disk group, hrdg2, containing only an SRL.

   ---

     Note   The bunker SRL must be the same size and the same name as the Primary SRL, or adding the bunker fails.

   ---

2. To add the bunker, type the following command:

   # vradmin -g hrdg -bdg hrdg2 addbunker hr_rvg seattle portland

   where hr_rvg is the name of the RVG; seattle is the name of the Primary; and portland is the name of the bunker.

   This command creates RLINKs between the bunker and the Primary, and also between the bunker and each Secondary in the RDS.

 To add a bunker when the bunker storage is directly accessible

1. Create a new disk group for the bunker, containing only an SRL. We recommend that this disk group has a different name than the main disk group for the RDS. For example, hrdg2.

   ---

     Note   The bunker SRL must be the same size and the same name as the Primary SRL, or adding the bunker fails.

   ---

   The disk group must be available to the Primary and the bunker host. That is, the disk group can be imported on either the Primary or the bunker host.

2. Deport the bunker disk group on the bunker portland and import it on the Primary seattle. In a shared disk group environment, import the bunker disk group on the logowner node of the Primary cluster.

   If the bunker disk group has the same name as the main disk group name, import it with a temporarily different name on the Primary, using the following command:

   # vxdg import -t -n newdgname bunkerdgname

   ---

     Note   In a shared disk group environment, the bunker disk group must be imported on the logowner node. If the VCS agents for VVR are configured, the bunker disk group fails over automatically when the logowner fails over to another node on the cluster. See Automating local cluster failover for a bunker. If the VCS agents for VVR are not configured, you must deport the bunker disk group from the previous logowner and import it on the new logowner node each time the logowner fails over.

   ---

3. Add the bunker:

   # vradmin -g hrdg -bdg hrdg2 addbunker hr_rvg seattle \

portland protocol=STORAGE

where hr_rvg is the RVG name; seattle is the Primary name; portland is the bunker name.

4. To display the configuration, use the following command:

   # vradmin printrvg

   Replicated Data Set: hr_rvg

   Primary:

   HostName: seattle <localhost>

   RvgName: hr_rvg

   DgName: hrdg

   Secondary:

   HostName: london

   RvgName: hr_rvg

   DgName: hrdg

   Bunker (Secondary):

   HostName: portland

   RvgName: hr_rvg

   DgName: hrdg2