InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - Solaris
- Introducing bundled agents
- Storage agents
- About the storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Dependencies for DiskGroupSnap agent
- Agent functions for DiskGroupSnap agent
- State definitions for DiskGroupSnap agent
- Attributes for DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Resource type definition for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Debug log levels for DiskGroupSnap agent
- Disk agent
- Volume agent
- VolumeSet agent
- Dependencies for VolumeSet agent
- Agent functions for VolumeSet agent
- State definitions for VolumeSet agent
- Attributes for VolumeSet agent
- Resource type definition for VolumeSet agent
- Sample configurations for VolumeSet agent
- Agent notes for VolumeSet agent
- Inaccessible volumes prevent the VolumeSet agent from coming online
- Debug log levels for VolumeSet agent
- Mount agent
- IMF awareness
- Dependencies for Mount agent
- Agent functions for Mount agent
- State definitions for Mount agent
- Attributes for Mount agent
- Resource type definition for Mount agent
- Notes for Mount agent
- High availability fire drill
- VxFS file system lock
- IMF usage notes
- IPv6 usage notes
- Support for loopback file system
- Enabling Level two monitoring for the Mount agent
- ZFS file system and pool creation example
- Support for VxFS direct mount inside non-global zones
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- Zpool agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Dependencies for IPMultiNICB agent
- Requirements for IPMultiNICB
- Agent functions for IPMultiNICB agent
- State definitions for IPMultiNICB agent
- Attributes for IPMultiNICB agent
- Resource type definition for IPMultiNICB agent
- Manually migrating a logical IP address for IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- Debug log levels for IPMultiNICB agent
- MultiNICB agent
- Base and Multi-pathing modes for MultiNICB agent
- Oracle trunking for MultiNICB agent
- The haping utility for MultiNICB agent
- Dependencies for MultiNICB agent
- Agent functions for MultiNICB agent
- State definitions for MultiNICB agent
- Attributes for MultiNICB agent
- Optional attributes for Base and Mpathd modes for MultiNICB agent
- Optional attributes for Base mode for MultiNICB agent
- Optional attributes for Multi-pathing mode for MultiNICB agent
- Resource type definition for MultiNICB agent
- Solaris operating modes: Base and Multi-Pathing for MultiNICB agent
- Base mode for MultiNICB agent
- Failover and failback for MultiNICB agent
- Multi-Pathing mode for MultiNICB agent
- Configuring MultiNICB and IPMultiNICB agents on Solaris 11
- Trigger script for MultiNICB agent
- Sample configurations for MultiNICB agent
- Debug log levels for MultiNICB agent
- DNS agent
- Dependencies for DNS agent
- Agent functions for DNS agent
- State definitions for DNS agent
- Attributes for DNS agent
- Resource type definition for DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- High availability fire drill for DNS agent
- Monitor scenarios for DNS agent
- Sample Web server configuration for DNS agent
- Secure DNS update for BIND 9 for DNS agent
- Setting up secure updates using TSIG keys for BIND 9 for DNS agent
- Sample configurations for DNS agent
- Debug log levels for DNS agent
- File share agents
- About the file service agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- NetBios agent
- Service and application agents
- About the services and applications agents
- AlternateIO agent
- Apache HTTP server agent
- Application agent
- IMF awareness
- High availability fire drill for Application agent
- Dependencies for Application agent
- Agent functions
- State definitions for Application agent
- Attributes for Application agent
- Resource type definition for Application agent
- Notes for Application agent
- Sample configurations for Application agent
- Debug log levels for Application agent
- CoordPoint agent
- LDom agent
- Configuring primary and logical domain dependencies and failure policy
- IMF awareness
- Dependencies
- Agent functions
- State definitions
- Attributes
- Resource type definition
- LDom agent notes
- About the auto-boot? variable
- Notes for the DomainFailurePolicy attribute
- Using VCS to migrate a logical domain
- Configuring the LDom agent for DR in a Global Cluster environment
- Using the LDom agent with IMF
- Sample configuration 1
- Sample configuration 2
- Configuration to support user-initiated LDom migration
- Configuration for VCS-initiated migration
- Sample configuration (Dynamic virtual machine service group failover)
- Debug log levels
- Process agent
- IMF awareness
- High availability fire drill for Process agent
- Dependencies for Process agent
- Agent functions for Process agent
- State definitions for Process agent
- Attributes for Process agent
- Resource type definition for Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- Debug log levels for Process agent
- ProcessOnOnly agent
- Project agent
- RestServer agent
- Zone agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Sample configurations for DiskGroupSnap agent
In Figure: Primary site with the Bronze configuration and the disaster recovery site with the Gold configuration, the Primary site is in the Bronze configuration and the Disaster recovery site is in a Gold configuration.
Since the Primary site does not have dedicated fire drill disks, it is in a Bronze configuration. In the Bronze configuration, you re-purpose the mirror disks in the disaster recovery site to serve as fire drill test disks. The drawback with the Bronze configuration is that if a disk failure occurs when the fire drill is online at the Primary site, it results in a site failure.
The FDSiteName value in a bronze configuration is the VxVM site name. For this configuration, the FDSiteName attribute values for the nodes at the Primary site follow:
FDSiteName@Node_A = pri
FDSiteName@Node_B = priThe Disaster Recovery site is in a Gold configuration as it has dedicated fire drill disks at the site. For the FDSiteName attribute, use the VxVM site tag given to the fire drill disks. For this configuration, the FDSiteName attribute values for the nodes at the Disaster recovery site follow:
FDSiteName@Node_C = dr_fd
FDSiteName@Node_D = dr_fdSet values for the SystemZones attribute to zero for Node_A and Node_B, and one for Node_C and Node_D. For example:
SystemZones = { Node_A = 0, Node_B = 0, Node_C = 1, Node_D = 1 }