[{"data":1,"prerenderedAt":1095},["ShallowReactive",2],{"blog-ja-proxmox-high-availability-setup":3,"blog-ja-proxmox-high-availability-setup-alt":203},{"id":4,"title":5,"author":6,"body":7,"date":1080,"description":1081,"extension":1082,"image":171,"locale":1083,"meta":1084,"navigation":203,"path":1085,"seo":1086,"stem":1087,"tags":1088,"__hash__":1094},"blog\u002Fblog\u002Fja\u002Fproxmox-high-availability-setup.md","Proxmox HA クラスタの構築と運用: 可用性を最大化する","Kubo Team",{"type":8,"value":9,"toc":1055},"minimark",[10,22,31,36,44,48,89,155,158,162,165,245,249,256,259,351,354,357,366,457,465,468,475,479,482,540,544,547,631,642,646,650,653,730,733,740,760,763,766,808,811,814,817,879,882,889,910,913,916,978,986,989,992,999,1008,1013,1051],[11,12,13,14,21],"p",{},"ミッションクリティカルなワークロードを運用する上で、単一障害点の排除は最優先事項です。",[15,16,20],"a",{"href":17,"rel":18},"https:\u002F\u002Fwww.proxmox.com\u002Fen\u002Fproxmox-virtual-environment\u002Foverview",[19],"nofollow","Proxmox VE"," は、組み込みの HA（High Availability）機能により、ノード障害時にも VM やコンテナを自動的に別ノードへフェイルオーバーさせ、サービスのダウンタイムを最小限に抑えます。本記事では、Proxmox HA クラスタの構築から運用までを詳細に解説します。",[11,23,24,25,30],{},"Kubernetes ワークロードの高可用性を求めるなら、",[15,26,29],{"href":27,"rel":28},"https:\u002F\u002Fwww.hexabase.com\u002Fproduct\u002Fkubo\u002Fon-premise",[19],"Kubo On-Premise"," が最適です。Proxmox HA とフルマネージド K8s を組み合わせることで、インフラからアプリケーションまで一貫した可用性を実現できます。",[32,33,35],"h2",{"id":34},"ha-クラスタの前提条件","HA クラスタの前提条件",[11,37,38,43],{},[15,39,42],{"href":40,"rel":41},"https:\u002F\u002Fpve.proxmox.com\u002Fwiki\u002FHigh_Availability",[19],"Proxmox 公式 HA ドキュメント","に基づき、以下の前提条件を満たす必要があります。",[45,46,47],"h3",{"id":47},"ハードウェア要件",[49,50,51,59,65,71,83],"ul",{},[52,53,54,58],"li",{},[55,56,57],"strong",{},"最低 3 ノード",": クォーラム（多数決）メカニズムに必要。2 ノード構成は Corosync QDevice で補完可能",[52,60,61,64],{},[55,62,63],{},"共有ストレージ",": 全ノードからアクセス可能なストレージ（Ceph、NFS、iSCSI、FC）",[52,66,67,70],{},[55,68,69],{},"冗長ネットワーク",": Corosync 通信用の専用ネットワーク（10 GbE 推奨）",[52,72,73,76,77,82],{},[55,74,75],{},"OOBM（Out-of-Band Management）",": ",[15,78,81],{"href":79,"rel":80},"https:\u002F\u002Fwww.intel.com\u002Fcontent\u002Fwww\u002Fus\u002Fen\u002Fproducts\u002Fdocs\u002Fservers\u002Fipmi\u002Fipmi-home.html",[19],"IPMI","、Dell iDRAC、HPE iLO 等のリモート管理インターフェース",[52,84,85,88],{},[55,86,87],{},"ハードウェア Watchdog",": iTCO_wdt（Intel）などのハードウェアタイマー",[90,91,92,108],"table",{},[93,94,95],"thead",{},[96,97,98,102,105],"tr",{},[99,100,101],"th",{},"コンポーネント",[99,103,104],{},"役割",[99,106,107],{},"推奨",[109,110,111,123,133,144],"tbody",{},[96,112,113,117,120],{},[114,115,116],"td",{},"Corosync",[114,118,119],{},"ノード間通信・状態同期",[114,121,122],{},"専用 10 GbE ネットワーク",[96,124,125,127,130],{},[114,126,63],{},[114,128,129],{},"VM\u002FCT データの共有",[114,131,132],{},"Ceph（推奨）\u002F NFS",[96,134,135,138,141],{},[114,136,137],{},"フェンシング",[114,139,140],{},"障害ノードの強制隔離",[114,142,143],{},"IPMI + Watchdog",[96,145,146,149,152],{},[114,147,148],{},"QDevice",[114,150,151],{},"2 ノード構成の補助",[114,153,154],{},"Corosync QDevice",[32,156,157],{"id":157},"クラスタの構築",[45,159,161],{"id":160},"proxmox-クラスタの作成","Proxmox クラスタの作成",[11,163,164],{},"最初のノードでクラスタを作成し、他のノードを順次参加させます:",[166,167,172],"pre",{"className":168,"code":169,"language":170,"meta":171,"style":171},"language-bash shiki shiki-themes tokyo-night","# ノード 1 でクラスタを作成\npvecm create my-ha-cluster\n\n# ノード 2, 3 をクラスタに参加させる（各ノードで実行）\npvecm add 192.168.1.10  # ノード 1 の IP\n\n# クラスタの状態確認\npvecm status\n","bash","",[173,174,175,184,198,205,211,226,231,237],"code",{"__ignoreMap":171},[176,177,180],"span",{"class":178,"line":179},"line",1,[176,181,183],{"class":182},"sbD-w","# ノード 1 でクラスタを作成\n",[176,185,187,191,195],{"class":178,"line":186},2,[176,188,190],{"class":189},"sE3pS","pvecm",[176,192,194],{"class":193},"sPY7s"," create",[176,196,197],{"class":193}," my-ha-cluster\n",[176,199,201],{"class":178,"line":200},3,[176,202,204],{"emptyLinePlaceholder":203},true,"\n",[176,206,208],{"class":178,"line":207},4,[176,209,210],{"class":182},"# ノード 2, 3 をクラスタに参加させる（各ノードで実行）\n",[176,212,214,216,219,223],{"class":178,"line":213},5,[176,215,190],{"class":189},[176,217,218],{"class":193}," add",[176,220,222],{"class":221},"sOJ5S"," 192.168.1.10",[176,224,225],{"class":182},"  # ノード 1 の IP\n",[176,227,229],{"class":178,"line":228},6,[176,230,204],{"emptyLinePlaceholder":203},[176,232,234],{"class":178,"line":233},7,[176,235,236],{"class":182},"# クラスタの状態確認\n",[176,238,240,242],{"class":178,"line":239},8,[176,241,190],{"class":189},[176,243,244],{"class":193}," status\n",[45,246,248],{"id":247},"corosync-ネットワークの設定","Corosync ネットワークの設定",[11,250,251,255],{},[15,252,116],{"href":253,"rel":254},"https:\u002F\u002Fcorosync.github.io\u002Fcorosync\u002F",[19]," はクラスタの心臓部であり、ノード間の通信と状態同期を担います。信頼性の高い低遅延ネットワークが不可欠です。パケットロスや高ジッターは、ノードの誤排除やクラスタの不安定化を招きます。",[11,257,258],{},"専用のボンディングリンクを Corosync に割り当てることが強く推奨されます:",[166,260,262],{"className":168,"code":261,"language":170,"meta":171,"style":171},"# Corosync の設定確認\ncat \u002Fetc\u002Fpve\u002Fcorosync.conf\n\n# ネットワークインターフェースの冗長化（ボンディング）\n# \u002Fetc\u002Fnetwork\u002Finterfaces に追加\nauto bond0\niface bond0 inet static\n    address 10.10.10.1\u002F24\n    bond-slaves eno3 eno4\n    bond-mode 802.3ad\n    bond-miimon 100\n",[173,263,264,269,277,281,286,291,299,313,321,333,342],{"__ignoreMap":171},[176,265,266],{"class":178,"line":179},[176,267,268],{"class":182},"# Corosync の設定確認\n",[176,270,271,274],{"class":178,"line":186},[176,272,273],{"class":189},"cat",[176,275,276],{"class":193}," \u002Fetc\u002Fpve\u002Fcorosync.conf\n",[176,278,279],{"class":178,"line":200},[176,280,204],{"emptyLinePlaceholder":203},[176,282,283],{"class":178,"line":207},[176,284,285],{"class":182},"# ネットワークインターフェースの冗長化（ボンディング）\n",[176,287,288],{"class":178,"line":213},[176,289,290],{"class":182},"# \u002Fetc\u002Fnetwork\u002Finterfaces に追加\n",[176,292,293,296],{"class":178,"line":228},[176,294,295],{"class":189},"auto",[176,297,298],{"class":193}," bond0\n",[176,300,301,304,307,310],{"class":178,"line":233},[176,302,303],{"class":189},"iface",[176,305,306],{"class":193}," bond0",[176,308,309],{"class":193}," inet",[176,311,312],{"class":193}," static\n",[176,314,315,318],{"class":178,"line":239},[176,316,317],{"class":189},"    address",[176,319,320],{"class":193}," 10.10.10.1\u002F24\n",[176,322,324,327,330],{"class":178,"line":323},9,[176,325,326],{"class":189},"    bond-slaves",[176,328,329],{"class":193}," eno3",[176,331,332],{"class":193}," eno4\n",[176,334,336,339],{"class":178,"line":335},10,[176,337,338],{"class":189},"    bond-mode",[176,340,341],{"class":193}," 802.3ad\n",[176,343,345,348],{"class":178,"line":344},11,[176,346,347],{"class":189},"    bond-miimon",[176,349,350],{"class":221}," 100\n",[11,352,353],{},"Corosync のリンク設定は Web UI の Datacenter → Cluster から管理できます。本番環境では必ず 2 つ以上のリンク（リング）を設定し、単一障害点を排除してください。",[45,355,356],{"id":356},"共有ストレージの設定",[11,358,359,360,365],{},"HA リソースは全ノードからアクセス可能な共有ストレージ上に配置する必要があります。",[15,361,364],{"href":362,"rel":363},"https:\u002F\u002Fpve.proxmox.com\u002Fwiki\u002FDeploy_Hyper-Converged_Ceph_Cluster",[19],"Ceph"," はハイパーコンバージド構成で最も推奨されるオプションです:",[166,367,369],{"className":168,"code":368,"language":170,"meta":171,"style":171},"# Ceph のインストール（各ノードで実行）\npveceph install\n\n# モニターの作成（各ノードで実行）\npveceph mon create\n\n# OSD の追加\npveceph osd create \u002Fdev\u002Fsdb\npveceph osd create \u002Fdev\u002Fsdc\n\n# Ceph プールの作成\npveceph pool create vm-pool\n",[173,370,371,376,384,388,393,403,407,412,424,435,439,444],{"__ignoreMap":171},[176,372,373],{"class":178,"line":179},[176,374,375],{"class":182},"# Ceph のインストール（各ノードで実行）\n",[176,377,378,381],{"class":178,"line":186},[176,379,380],{"class":189},"pveceph",[176,382,383],{"class":193}," install\n",[176,385,386],{"class":178,"line":200},[176,387,204],{"emptyLinePlaceholder":203},[176,389,390],{"class":178,"line":207},[176,391,392],{"class":182},"# モニターの作成（各ノードで実行）\n",[176,394,395,397,400],{"class":178,"line":213},[176,396,380],{"class":189},[176,398,399],{"class":193}," mon",[176,401,402],{"class":193}," create\n",[176,404,405],{"class":178,"line":228},[176,406,204],{"emptyLinePlaceholder":203},[176,408,409],{"class":178,"line":233},[176,410,411],{"class":182},"# OSD の追加\n",[176,413,414,416,419,421],{"class":178,"line":239},[176,415,380],{"class":189},[176,417,418],{"class":193}," osd",[176,420,194],{"class":193},[176,422,423],{"class":193}," \u002Fdev\u002Fsdb\n",[176,425,426,428,430,432],{"class":178,"line":323},[176,427,380],{"class":189},[176,429,418],{"class":193},[176,431,194],{"class":193},[176,433,434],{"class":193}," \u002Fdev\u002Fsdc\n",[176,436,437],{"class":178,"line":335},[176,438,204],{"emptyLinePlaceholder":203},[176,440,441],{"class":178,"line":344},[176,442,443],{"class":182},"# Ceph プールの作成\n",[176,445,447,449,452,454],{"class":178,"line":446},12,[176,448,380],{"class":189},[176,450,451],{"class":193}," pool",[176,453,194],{"class":193},[176,455,456],{"class":193}," vm-pool\n",[11,458,459,464],{},[15,460,463],{"href":461,"rel":462},"https:\u002F\u002Fkubo.hexabase.io\u002F",[19],"Kubo"," では、このような分散ストレージの複雑な設定を自動化し、Kubernetes 向けに最適化された永続ボリュームを提供します。",[32,466,467],{"id":467},"フェンシングの設定",[11,469,470,471,474],{},"フェンシングは HA クラスタの最も重要な安全機構です。",[15,472,137],{"href":40,"rel":473},[19],"は、障害を起こしたノードが共有ストレージに書き込みを続ける「スプリットブレイン」シナリオを防止します。応答しなくなったノードが実際にはまだ動作しており、共有ディスクに書き込んでいる状態で別のノードが同じ VM を起動すると、データ破損が発生します。",[45,476,478],{"id":477},"watchdog-の設定","Watchdog の設定",[11,480,481],{},"ハードウェア Watchdog は定期的なタイマーリセットが行われない場合にノードを自動リブートします:",[166,483,485],{"className":168,"code":484,"language":170,"meta":171,"style":171},"# Watchdog モジュールの設定\n# \u002Fetc\u002Fdefault\u002Fpve-ha-manager\nWATCHDOG_MODULE=iTCO_wdt\n\n# Watchdog の動作確認\nwdctl\n\n# Watchdog が利用できない場合は softdog にフォールバック\nmodprobe softdog\n",[173,486,487,492,497,509,513,518,523,527,532],{"__ignoreMap":171},[176,488,489],{"class":178,"line":179},[176,490,491],{"class":182},"# Watchdog モジュールの設定\n",[176,493,494],{"class":178,"line":186},[176,495,496],{"class":182},"# \u002Fetc\u002Fdefault\u002Fpve-ha-manager\n",[176,498,499,502,506],{"class":178,"line":200},[176,500,501],{"class":189},"WATCHDOG_MODULE",[176,503,505],{"class":504},"sAklC","=",[176,507,508],{"class":193},"iTCO_wdt\n",[176,510,511],{"class":178,"line":207},[176,512,204],{"emptyLinePlaceholder":203},[176,514,515],{"class":178,"line":213},[176,516,517],{"class":182},"# Watchdog の動作確認\n",[176,519,520],{"class":178,"line":228},[176,521,522],{"class":189},"wdctl\n",[176,524,525],{"class":178,"line":233},[176,526,204],{"emptyLinePlaceholder":203},[176,528,529],{"class":178,"line":239},[176,530,531],{"class":182},"# Watchdog が利用できない場合は softdog にフォールバック\n",[176,533,534,537],{"class":178,"line":323},[176,535,536],{"class":189},"modprobe",[176,538,539],{"class":193}," softdog\n",[45,541,543],{"id":542},"ipmi-フェンシング","IPMI フェンシング",[11,545,546],{},"IPMI ベースのフェンシングは、ネットワーク経由でノードの電源を強制的にオフにできます:",[166,548,550],{"className":168,"code":549,"language":170,"meta":171,"style":171},"# IPMI 経由でノードの電源状態を確認\nipmitool -I lanplus -H 192.168.1.200 -U admin -P password chassis power status\n\n# 強制電源オフ\nipmitool -I lanplus -H 192.168.1.200 -U admin -P password chassis power off\n",[173,551,552,557,595,599,604],{"__ignoreMap":171},[176,553,554],{"class":178,"line":179},[176,555,556],{"class":182},"# IPMI 経由でノードの電源状態を確認\n",[176,558,559,562,566,569,572,575,578,581,584,587,590,593],{"class":178,"line":186},[176,560,561],{"class":189},"ipmitool",[176,563,565],{"class":564},"sT800"," -I",[176,567,568],{"class":193}," lanplus",[176,570,571],{"class":564}," -H",[176,573,574],{"class":221}," 192.168.1.200",[176,576,577],{"class":564}," -U",[176,579,580],{"class":193}," admin",[176,582,583],{"class":564}," -P",[176,585,586],{"class":193}," password",[176,588,589],{"class":193}," chassis",[176,591,592],{"class":193}," power",[176,594,244],{"class":193},[176,596,597],{"class":178,"line":200},[176,598,204],{"emptyLinePlaceholder":203},[176,600,601],{"class":178,"line":207},[176,602,603],{"class":182},"# 強制電源オフ\n",[176,605,606,608,610,612,614,616,618,620,622,624,626,628],{"class":178,"line":213},[176,607,561],{"class":189},[176,609,565],{"class":564},[176,611,568],{"class":193},[176,613,571],{"class":564},[176,615,574],{"class":221},[176,617,577],{"class":564},[176,619,580],{"class":193},[176,621,583],{"class":564},[176,623,586],{"class":193},[176,625,589],{"class":193},[176,627,592],{"class":193},[176,629,630],{"class":193}," off\n",[11,632,633,76,636,641],{},[55,634,635],{},"重要",[15,637,640],{"href":638,"rel":639},"https:\u002F\u002Fwww.virtualizationhowto.com\u002F2025\u002F07\u002Fhigh-availability-ha-proxmox-clusters-dos-donts\u002F",[19],"OOBM（帯域外管理）","は HA クラスタでは贅沢品ではなく、信頼性の高いフェンシングのための必須要件です。",[32,643,645],{"id":644},"ha-リソースの管理","HA リソースの管理",[45,647,649],{"id":648},"ha-の有効化","HA の有効化",[11,651,652],{},"VM やコンテナを HA 管理下に置きます:",[166,654,656],{"className":168,"code":655,"language":170,"meta":171,"style":171},"# VM 100 を HA に登録\nha-manager add vm:100 --state started --max-restart 2 --max-relocate 2\n\n# HA リソースの一覧確認\nha-manager status\n\n# HA リソースの設定変更\nha-manager set vm:100 --group prefer-node1\n",[173,657,658,663,691,695,700,706,710,715],{"__ignoreMap":171},[176,659,660],{"class":178,"line":179},[176,661,662],{"class":182},"# VM 100 を HA に登録\n",[176,664,665,668,670,673,676,679,682,685,688],{"class":178,"line":186},[176,666,667],{"class":189},"ha-manager",[176,669,218],{"class":193},[176,671,672],{"class":193}," vm:100",[176,674,675],{"class":564}," --state",[176,677,678],{"class":193}," started",[176,680,681],{"class":564}," --max-restart",[176,683,684],{"class":221}," 2",[176,686,687],{"class":564}," --max-relocate",[176,689,690],{"class":221}," 2\n",[176,692,693],{"class":178,"line":200},[176,694,204],{"emptyLinePlaceholder":203},[176,696,697],{"class":178,"line":207},[176,698,699],{"class":182},"# HA リソースの一覧確認\n",[176,701,702,704],{"class":178,"line":213},[176,703,667],{"class":189},[176,705,244],{"class":193},[176,707,708],{"class":178,"line":228},[176,709,204],{"emptyLinePlaceholder":203},[176,711,712],{"class":178,"line":233},[176,713,714],{"class":182},"# HA リソースの設定変更\n",[176,716,717,719,722,724,727],{"class":178,"line":239},[176,718,667],{"class":189},[176,720,721],{"class":193}," set",[176,723,672],{"class":193},[176,725,726],{"class":564}," --group",[176,728,729],{"class":193}," prefer-node1\n",[45,731,732],{"id":732},"ノードアフィニティルール",[11,734,735,736,739],{},"Proxmox VE 9.0 以降、",[15,737,732],{"href":40,"rel":738},[19],"が HA グループに代わる推奨設定となっています:",[49,741,742,748,754],{},[52,743,744,747],{},[55,745,746],{},"ノードアフィニティ",": リソースを特定のノードに優先配置",[52,749,750,753],{},[55,751,752],{},"リソースアフィニティ",": リソース同士を同一ノード（正）または別ノード（負）に配置",[52,755,756,759],{},[55,757,758],{},"Strict モード",": 対象ノードが利用不可の場合、停止中のリソースを起動しない",[45,761,762],{"id":762},"フェイルオーバーポリシー",[11,764,765],{},"リソースには復旧戦略を設定できます:",[90,767,768,781],{},[93,769,770],{},[96,771,772,775,778],{},[99,773,774],{},"パラメータ",[99,776,777],{},"デフォルト",[99,779,780],{},"説明",[109,782,783,796],{},[96,784,785,790,793],{},[114,786,787],{},[173,788,789],{},"max_restart",[114,791,792],{},"1",[114,794,795],{},"同一ノードでの再起動試行回数",[96,797,798,803,805],{},[114,799,800],{},[173,801,802],{},"max_relocate",[114,804,792],{},[114,806,807],{},"再起動失敗後の別ノード移行試行回数",[32,809,810],{"id":810},"メンテナンスと監視",[45,812,813],{"id":813},"メンテナンスモード",[11,815,816],{},"ノードのメンテナンス時は、HA サービスを安全に移行してから作業します:",[166,818,820],{"className":168,"code":819,"language":170,"meta":171,"style":171},"# メンテナンスモードの有効化\nha-manager crm-command node-maintenance enable pve-node1\n\n# ノード上のすべての HA サービスが移行されるまで待機\n# 移行完了後にメンテナンス作業を実施\n\n# メンテナンスモードの解除\nha-manager crm-command node-maintenance disable pve-node1\n",[173,821,822,827,843,847,852,857,861,866],{"__ignoreMap":171},[176,823,824],{"class":178,"line":179},[176,825,826],{"class":182},"# メンテナンスモードの有効化\n",[176,828,829,831,834,837,840],{"class":178,"line":186},[176,830,667],{"class":189},[176,832,833],{"class":193}," crm-command",[176,835,836],{"class":193}," node-maintenance",[176,838,839],{"class":193}," enable",[176,841,842],{"class":193}," pve-node1\n",[176,844,845],{"class":178,"line":200},[176,846,204],{"emptyLinePlaceholder":203},[176,848,849],{"class":178,"line":207},[176,850,851],{"class":182},"# ノード上のすべての HA サービスが移行されるまで待機\n",[176,853,854],{"class":178,"line":213},[176,855,856],{"class":182},"# 移行完了後にメンテナンス作業を実施\n",[176,858,859],{"class":178,"line":228},[176,860,204],{"emptyLinePlaceholder":203},[176,862,863],{"class":178,"line":233},[176,864,865],{"class":182},"# メンテナンスモードの解除\n",[176,867,868,870,872,874,877],{"class":178,"line":239},[176,869,667],{"class":189},[176,871,833],{"class":193},[176,873,836],{"class":193},[176,875,876],{"class":193}," disable",[176,878,842],{"class":193},[45,880,881],{"id":881},"ローリングアップデート",[11,883,884,885,888],{},"クラスタのアップデートは",[55,886,887],{},"1 ノードずつ順番に","実施します。全ノードを同時にアップデートすることは絶対に避けてください:",[890,891,892,895,898,904,907],"ol",{},[52,893,894],{},"ノードをメンテナンスモードに設定",[52,896,897],{},"HA サービスの移行を確認",[52,899,900,903],{},[173,901,902],{},"apt update && apt full-upgrade -y"," を実行",[52,905,906],{},"再起動し、クラスタへの復帰を確認",[52,908,909],{},"次のノードに移る",[45,911,912],{"id":912},"フェイルオーバーテスト",[11,914,915],{},"本番運用前に必ずフェイルオーバーテストを実施してください:",[166,917,919],{"className":168,"code":918,"language":170,"meta":171,"style":171},"# シミュレーターでテスト\napt install pve-ha-simulator\npve-ha-simulator\n\n# 手動フェイルオーバー（VM を別ノードに移行）\nha-manager migrate vm:100 pve-node2\n\n# HA 状態の監視\nha-manager status\n",[173,920,921,926,937,942,946,951,963,967,972],{"__ignoreMap":171},[176,922,923],{"class":178,"line":179},[176,924,925],{"class":182},"# シミュレーターでテスト\n",[176,927,928,931,934],{"class":178,"line":186},[176,929,930],{"class":189},"apt",[176,932,933],{"class":193}," install",[176,935,936],{"class":193}," pve-ha-simulator\n",[176,938,939],{"class":178,"line":200},[176,940,941],{"class":189},"pve-ha-simulator\n",[176,943,944],{"class":178,"line":207},[176,945,204],{"emptyLinePlaceholder":203},[176,947,948],{"class":178,"line":213},[176,949,950],{"class":182},"# 手動フェイルオーバー（VM を別ノードに移行）\n",[176,952,953,955,958,960],{"class":178,"line":228},[176,954,667],{"class":189},[176,956,957],{"class":193}," migrate",[176,959,672],{"class":193},[176,961,962],{"class":193}," pve-node2\n",[176,964,965],{"class":178,"line":233},[176,966,204],{"emptyLinePlaceholder":203},[176,968,969],{"class":178,"line":239},[176,970,971],{"class":182},"# HA 状態の監視\n",[176,973,974,976],{"class":178,"line":323},[176,975,667],{"class":189},[176,977,244],{"class":193},[11,979,980,985],{},[15,981,984],{"href":982,"rel":983},"https:\u002F\u002Fforum.proxmox.com\u002F",[19],"Proxmox フォーラム","では、HA 構成のベストプラクティスに関する活発な議論が行われています。",[32,987,988],{"id":988},"まとめ",[11,990,991],{},"Proxmox HA クラスタは、適切な設計と構成により、エンタープライズグレードの可用性を実現します。Corosync の冗長ネットワーク、フェンシングによる安全なノード隔離、共有ストレージの信頼性確保が鍵となります。",[11,993,994,995,998],{},"Kubernetes ワークロードの HA を含めた統合的なインフラ管理には、",[15,996,29],{"href":27,"rel":997},[19]," をご検討ください。Proxmox HA の上にフルマネージド K8s を展開し、ノード障害時も Kubernetes ワークロードの自動復旧を保証します。",[11,1000,1001,1002,1007],{},"HA クラスタの設計・構築に関するご相談は、",[15,1003,1006],{"href":1004,"rel":1005},"https:\u002F\u002Fwww.hexabase.com\u002Fcontact-us\u002F",[19],"お問い合わせ","からお気軽にご連絡ください。",[11,1009,1010],{},[55,1011,1012],{},"関連リンク:",[49,1014,1015,1021,1028,1034,1040,1045],{},[52,1016,1017],{},[15,1018,1020],{"href":40,"rel":1019},[19],"Proxmox HA 公式ドキュメント",[52,1022,1023],{},[15,1024,1027],{"href":1025,"rel":1026},"https:\u002F\u002Fpve.proxmox.com\u002Fwiki\u002FCluster_Manager",[19],"Proxmox クラスタマネージャー",[52,1029,1030],{},[15,1031,1033],{"href":362,"rel":1032},[19],"Ceph ハイパーコンバージドガイド",[52,1035,1036],{},[15,1037,1039],{"href":253,"rel":1038},[19],"Corosync プロジェクト",[52,1041,1042],{},[15,1043,984],{"href":982,"rel":1044},[19],[52,1046,1047],{},[15,1048,1050],{"href":461,"rel":1049},[19],"Kubo ブログ",[1052,1053,1054],"style",{},"html pre.shiki code .sbD-w, html code.shiki .sbD-w{--shiki-default:#51597D;--shiki-default-font-style:italic}html pre.shiki code .sE3pS, html code.shiki .sE3pS{--shiki-default:#C0CAF5}html pre.shiki code .sPY7s, html code.shiki .sPY7s{--shiki-default:#9ECE6A}html pre.shiki code .sOJ5S, html code.shiki .sOJ5S{--shiki-default:#FF9E64}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html pre.shiki code .sAklC, html code.shiki .sAklC{--shiki-default:#89DDFF}html pre.shiki code .sT800, html code.shiki .sT800{--shiki-default:#E0AF68}",{"title":171,"searchDepth":186,"depth":186,"links":1056},[1057,1060,1065,1069,1074,1079],{"id":34,"depth":186,"text":35,"children":1058},[1059],{"id":47,"depth":200,"text":47},{"id":157,"depth":186,"text":157,"children":1061},[1062,1063,1064],{"id":160,"depth":200,"text":161},{"id":247,"depth":200,"text":248},{"id":356,"depth":200,"text":356},{"id":467,"depth":186,"text":467,"children":1066},[1067,1068],{"id":477,"depth":200,"text":478},{"id":542,"depth":200,"text":543},{"id":644,"depth":186,"text":645,"children":1070},[1071,1072,1073],{"id":648,"depth":200,"text":649},{"id":732,"depth":200,"text":732},{"id":762,"depth":200,"text":762},{"id":810,"depth":186,"text":810,"children":1075},[1076,1077,1078],{"id":813,"depth":200,"text":813},{"id":881,"depth":200,"text":881},{"id":912,"depth":200,"text":912},{"id":988,"depth":186,"text":988},"2026-05-27","Proxmox VE の HA クラスタ構築を徹底解説。Corosync 設定、フェンシング、HA グループ、フェイルオーバー検証、メンテナンス手順まで完全網羅。","md","ja",{},"\u002Fblog\u002Fja\u002Fproxmox-high-availability-setup",{"title":5,"description":1081},"blog\u002Fja\u002Fproxmox-high-availability-setup",[1089,1090,1091,1092,137,116,1093],"Proxmox","HA","高可用性","クラスタ","インフラ","Ul3LCIxgAOn9fUX0xwuQdCW4xPH6te7pcf-Rf8HiTzs",1779964617057]