Configuring Oracle VM Server for SPARC guest domains for disaster recovery
Prev Configuring for disaster recovery in virtualized environments Next

Configuring Oracle VM Server for SPARC guest domains for disaster recovery

The Oracle VMs can be configured for disaster recovery by replicating the boot disk using replication methods like Hitachi TrueCopy, EMC SRDF, Volume Replicator, and so on. The network configuration for the Oracle VM in the primary site may not be effective in the secondary site if the two sites are in different IP subnets. You will need to make these additional configuration changes to the LDom resource.

Note:

This deployment model applies to Split Storage Foundation stack model.

To configure the guest domains for disaster recovery, you need to configure VCS on both the sites in the Control Domains with GCO option.

Refer to the Symantec Cluster Server Administrator's Guide for more information about global clusters.

To set up the guest domain for disaster recovery

  1. On the primary site, create the guest domain using ldm commands and configure the network-related parameters.
  2. On the primary site after you boot the guest domain, copy and install the package VRTSvcsnr from the VCS installation media in the guest domain. This package installs the vcs-network-reconfig service in the guest domain. This service makes sure that the site-specific network parameters are applied when the guest domain boots.
  3. On the primary site, shut down the guest domain.
  4. Use replication specific commands to failover the replication to the secondary site from the primary site.
  5. Repeat step 1 on the secondary site.
  6. Perform step7, step 8, step 9, and step 10 on both the primary cluster and the secondary clusters.
  7. Create a VCS service group and add a VCS LDom resource for the guest domain.

    Configure the following disaster recovery-related attributes on the LDom resource with site-specific values for each: IPAddress, Netmask, Gateway, DNS (DNS Server).

    Set the value of the ConfigureNetwork attribute to 1 to make the changes effective. The LDom agent does not apply the disaster recovery-related attributes to the guest domain if the value of the ConfigureNetwork attribute is 0.

  8. Add the appropriate Mount and DiskGroup resources in the service group for the file system and the disk group on which the boot image of the guest domain resides.

    Add a resource dependency from the LDom resource to the Mount resource and another dependency from the Mount resource to the Diskgroup resource.

  9. Add the appropriate VCS replication resource in the service group. Examples of hardware replication agents are SRDF for EMC SRDF, HTC for Hitachi TrueCopy, MirrorView for EMC MirrorView, etc.

    Refer to the appropriate VCS Replication agent guide for configuring the replication resource.

    For VVR-based replication, add the appropriate RVGPrimary resource to the service group.

    Refer to the following manuals for more information:

    • For information about configuring VVR-related resources, see the Symantec Storage Foundation and High Availability Solutions Replication Administrator's Guide.

    • For information about the VVR-related agents, see the Symantec Cluster Server Bundled Agents Reference Guide.

  10. Add a dependency from the DiskGroup resource to the replication resource.

Figure: Sample resource dependency diagram for hardware replication based guest domains

Sample resource dependency diagram for hardware replication based guest domains

Figure: Sample resource dependency diagram for VVR replication-based guest domains

Sample resource dependency diagram for VVR replication-based guest domains

The replication resource makes sure that when the resource is online in a site, the underlying replicated devices are in primary mode and the remote devices are in secondary mode. Thus, when the LDom resource goes online, the underlying storage will always be in read-write mode. When the LDom resource goes online, it sets the DR related parameters in the EEPROM parameter network-boot-arguments for the guest domain before starting the guest domain. When the guest domain boots, the vcs-network-reconfig service starts inside the guest domain. This service reads the EEPROM parameter and applies the disaster recovery related parameters by modifying the appropriate files inside the guest domain.

Prev Up Next
Configuring Solaris non-global zones for disaster recovery Home Section VI. Reference