LPIC-3 High Availability and Storage Clusters case studies
LPIC-3 High Availability and Storage Clusters · Put your knowledge to work in context.
LPIC-3 High Availability and Storage Clusters is one of four separate LPIC-3 specialty certifications offered by the Linux Professional Institute, the vendor-neutral certification body behind the multi-level LPIC program. It targets enterprise-level Linux professionals who design, run and recover highly available systems and clustered storage. The current version is 3.0, exam code 306-300; it results from a split of version 2.0 of exam 304, and the previous 304-200 version was available only until June 20th, 2022. To receive the certification you must hold an active LPIC-2 certification and pass the 306 exam. The LPIC-3 High Availability and Storage Clusters case studies are 5 cases and about 2,592 words.
1Quorum Loss and the No-Quorum Policy in a Split Data Center
Five nodes run Pacemaker 2.1 and Corosync 3 on RHEL 9: ha-a1 and ha-a2 in rack A, ha-b1 through ha-b3 in rack B. A PostgreSQL resource, a VIP, and a filesystem are configured as a group.
471 words, about 2 min2DRBD Split-Brain After a Switch Maintenance Window
Two nodes, db1 and db2, run Pacemaker and DRBD 9.1. A resource r0 backs a 2 TB ext4 filesystem and is configured active/passive with protocol C.
555 words, about 3 min3Ceph Pool Becomes Inactive After a Second Host Reboot
Five Ceph Reef hosts, c1 through c5, each run 12 OSDs and one MON. Pool rbd uses replicated size 3, min size 2, and CRUSH failure domain host.
560 words, about 3 min4Multipath I/O Stall During a SAN Fabric Upgrade
One physical database server runs RHEL 9 and PostgreSQL 15 on XFS over LVM. The 4 TB LUN is presented through two Fibre Channel fabrics and two HBAs; multipathd maps it as mpatha with path grouping policy multibus.
597 words, about 3 min5QDevice Firewall Change Removes the Last-Man-Standing Tiebreaker
A two-node Pacemaker 2.1 cluster, web1 and web2, uses a Corosync qdevice hosted on qnetd.example.net to provide a tiebreaker. The cluster runs a VIP and HAProxy in an active/backup arrangement.
409 words, about 2 min