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:

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.

  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.

    Note: Assume the following configuration:

    # vradmin printrvg
    Replicated Data Set: hr_rvg
    Primary:
         HostName: seattle-v6 <localhost> 
         RvgName: hr_rvg
         DgName: hrdg
    Secondary:
         HostName: london-v6
         RvgName: hr_rvg
         DgName: hrdg

    In this configuration, replication is already setup between london-v6 and seattle-v6. The bunker host can be added to the RDS using it's IPv6 address or a host name which resolves to an IPv6 address. For example, the bunker host can be added to the RDS using the following command:

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

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

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.

    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

    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