A typical WebSphere MQ hierarchy will be comprised of a WebSphere MQ queue manager resource. It also contains one or more file system resources, depending on the file system layout and zero or more IP resources. The exact makeup of the hierarchy depends on what is being protected. If the administrator chooses to include an IP resource in the WebSphere MQ resource hierarchy, that IP must be created prior to creating the WebSphere MQ queue manager resource and that IP resource must be active on the primary server. Replicated (SIOS DataKeeper) file system resources must be created before creating the MQ resource. The file system hierarchies are created automatically during the creation of the WebSphere MQ queue manager resource.
Figure 1 Typical WebSphere MQ hierarchy – symbolic links
Figure 2 Typical WebSphere MQ hierarchy – LVM configuration