xDev Asia

使用 pg_basebackup，配置 WAL 歸檔、連續歸檔並執行時間點恢復 (PITR)。

PostgreSQL 與 Patroni 和 PostgreSQL 高可用性etcd

第 4 部分：備份、監控與調整

xdev.asia

目標____HTMLTAG_68__HTMLTAG_69_完成本課程後，您將：__HTMLTAG_70__HTMLTAG_71__HTMLTAG_72_設定 WAL 檔案__HTMLTAG_73__HTMLTAG_74___使用 pg_執行備份___HTMLTAG_75__HTMLTAG_76_配置連續存檔_HTMLTAG_77__HTMLTAG_78_將資料庫還原到特定時間點__HTMLTAG_79__HTMLTAG_80_自動備援策略_HTMLTAG_81__HTMLTAG_ML82___MLTAG_82___ML_UUUT_UUT_UU4_D_UUUT5_D_UUUT5_D__ML82_417_ML備份策略概述___HTMLTAG_86__HTMLTAG_87_1.1。備份類型_HTMLTAG_88__HTMLTAG_89___A。邏輯備份

# pg_dump / pg_dumpall pg_dump -h localhost -U postgres mydb > mydb.sql pg_dumpall -h localhost -U postgres > cluster.sql Pros: ✅ Easy to restore specific tables ✅ Portable across PostgreSQL versions ✅ Human-readable (text) Cons: ❌ Slow for large databases ❌ Not suitable for PITR ❌ Requires downtime for consistent backup

B。實體備份___HTMLTAG_92__CODEBLOCK_1__HTMLTAG_93_C。連續歸檔（WAL 歸檔）_HTMLTAG_94__CODEBLOCK_2__HTMLTAG_95_1.2。 RTO 和 RPO：目標）= 可接受的資料遺失量是多少？
_CODEBLOCK_4__HTMLTAG_105___1.3。備份策略決策矩陣

__HTMLTAG_108__HTMLTAG_109__HTMLTAG_110__HTMLTAG_111___要求___HTMLTAG_112__HTMLTAG_113___解决方案___HTMLTAG_114 _HTMLTAG_115__HTMLTAG_116__HTMLTAG_117__HTMLTAG_118__HTMLTAG_119___零資料遺失____HTMLTAG_120__HTMLTAG_121___同步複製+ PITR___HTMLTAG_122__HTMLTAG_123__HTMLTAG_124__HTMLTAG_125___快速恢復（<1 小時）HTMLTAG_126__HTMLTAG_127___流式傳輸複製___HTMLTAG_128__HTMLTAG_129__HTMLTAGML4130功能___HTMLTAG_132__HTMLTAG_133___WAL 歸檔 + pg_basebackup___HTMLTAG_134__HTMLTAG_135__HTMLTAG_136__HTMLTAG_137___長期保留___HTMLTAG_138__HTMLTAG_139___定期p g_basebackup___HTMLTAG_140__HTMLTAG_141__HTMLTAG_142__HTMLTAG_143___災難復原___HTMLTAG_144__HTMLTAG_145___場外備援+ PITR___HTMLTAG_146__HTMLTAG_147__HTMLTAG_148__HTMLTAG_149

2。 WAL 歸檔設定___HTMLTAG_152__HTMLTAG_153_2.1。了解 WAL 歸檔_HTMLTAG_154__HTMLTAG_155__HTMLTAG_156_WAL（預先寫入日誌）=交易日誌檔_HTMLTAG_158__CODEBLOCK_5__HTMLTAG_159__HTMLTAG_160_WAL段：_HTMLTAG_162__CODEBLOCK_6__HTMLTAG_163_2.2。設定WAL歸檔_HTMLTAG_164__HTMLTAG_165_PostgreSQL設定_HTMLTAG_166__CODEBLOCK_7__HTMLTAG_167__HTMLTAG_168_參數說明 _HTMLTAG_169_:_HTMLTAG_170__CODEBLOCK_8__HTMLTAG_171_建立歸檔目錄_HTMLTAG_172__CODEBLOCK_9__HTMLTAG_173_2.3。高階存檔指令_HTMLTAG_174__HTMLTAG_175___A。存檔到遠端伺服器 (rsync)

# archive_command using rsync
archive_command = 'rsync -a %p backup-server:/mnt/wal_archive/%f'

B。存檔至 S3 (wal-g)___HTMLTAG_178__CODEBLOCK_11__HTMLTAG_179_C。壓縮存檔_HTMLTAG_180__CODEBLOCK_12__HTMLTAG_181___2.4。監控歸檔

-- Check archiving status
SELECT archived_count, 
       failed_count,
       last_archived_wal,
       last_archived_time,
       last_failed_wal,
       last_failed_time
FROM pg_stat_archiver;
-- Example output:
--  archived_count | failed_count | last_archived_wal        | last_archived_time

-- ----------------+--------------+--------------------------+-----------------------------
--            1234 |            0 | 000000010000000000000056 | 2024-11-25 10:30:15.123456
-- If failed_count > 0, check logs!

# Check PostgreSQL logs for archive errors sudo journalctl -u postgresql | grep -i archive Common errors: - Permission denied on archive directory - Archive directory full - Network timeout (for remote archiving)

3。使用 pg_basebackup___HTMLTAG_184__HTMLTAG_185___3.1 進行基本備援。基本 pg_basebackup___HTMLTAG_186__CODEBLOCK_15__HTMLTAG_187__HTMLTAG_188_輸出：_HTMLTAG_190__CODEBLOCK_16__HTMLTAG_191_3.2。壓縮的 tar 備援_HTMLTAG_192__CODEBLOCK_17__HTMLTAG_193___3.3。備份到遠端伺服器

___CODEBLOCK_18__HTMLTAG_195___3.4。使用複製槽備份___HTMLTAG_196__CODEBLOCK_19__HTMLTAG_197___3.5。驗證備份___HTMLTAG_198__CODEBLOCK_20__HTMLTAG_199___4。時間點恢復 (PITR)___HTMLTAG_200__HTMLTAG_201___4.1。 PITR 概念___HTMLTAG_202__HTMLTAG_203__HTMLTAG_204___PITR= 将数据库恢复到任何时间点（不仅仅是备份）时间）____HTMLTAG_208__CODEBLOCK_21__HTMLTAG_209__HTMLTAG_210___要求：____HTMLTAG_212__HTMLTAG_213__HTMLTAG_214___基本备份。準備PITR___HTMLTAG_222__HTMLTAG_223__HTMLTAG_224___建立復原目錄:HTMLTAG_226__CODEBLOCK_22 HTMLTAG_227__HTMLTAG_228___恢復基本備份:

CODEBLOCK_23__HTMLTAG_231___4.3。設定恢復___HTMLTAG_232__HTMLTAG_233__HTMLTAG_234___建立恢復設定:___HTMLTAG_236__CODEBLOCK_24__HTMLTAG_237__HTML TAG_238___恢復參數:____HTMLTAG_240__CODEBLOCK_25__HTMLTAG_241___4.4.恢復目標選項___HTMLTAG_242__HTMLTAG_243___A。恢復到特定時間

-- In postgresql.auto.conf
recovery_target_time = '2024-11-25 10:30:00'

B。恢復到特定事務___HTMLTAG_246__CODEBLOCK_27__HTMLTAG_247_C.恢復到特定 LSN_HTMLTAG_248__CODEBLOCK_28__HTMLTAG_249_D。恢復到最新的_HTMLTAG_250__CODEBLOCK_29__HTMLTAG_251___E。恢復目標（包含/排除）

-- Default: exclusive (stop BEFORE target)
recovery_target_inclusive = 'off'
-- Inclusive: include target transaction
recovery_target_inclusive = 'on'

4.5。執行恢復___HTMLTAG_254__CODEBLOCK_31__HTMLTAG_255__HTMLTAG_256_日誌輸出:_HTMLTAG_258__CODEBLOCK_32__HTMLTAG_259__HTMLTAG_258__CODEBLOCK_32__HTMLTAG_259__HTMLTAG_260_如果暫停複：_HTMLTAG_262__CODEBLOCK_33__HTMLTAG_263__HTMLTAG_264_驗證恢復：_HTMLTAG_266__CODEBLOCK_34__HTMLTAG_267______HTMLTAG6。 PITR_HTMLTAG_268__CODEBLOCK_35__CODEBLOCK_36__HTMLTAG_269_5 之後的時間軸。使用 Patroni 實現自動化_HTMLTAG_270__HTMLTAG_271_5.1。 Patroni WAL歸檔_HTMLTAG_272__HTMLTAG_273__HTMLTAG_274_在patroni.yml中配置:_HTMLTAG_276__CODEBLOCK_37______HTMLTAG_277__HTVTAG_276__CODEBLOCK_37______HTMLTAG_277__HTPatTAG_278_Pato_ML MLTAG_280__HTMLTAG_281__HTMLTAG_282_在主資料庫上設定存檔__HTMLTAG_283__HTMLTAG_284_在副本上設定還原_HTMLTAG_285__HTMLTAG_286_處理時間線變更_HTMLTAG_287858285858___備份腳本_HTMLTAG_290__CODEBLOCK_38__HTMLTAG_291__HTMLTAG_292_使用 cron 進行計劃:_HTMLTAG_294__CODEBLOCK_39__HTMLTAG_295_5.3. WALG-G整合_HTMLTAG_296__HTMLTAG_297__HTMLTAG_298_安裝WAL-G:_HTMLTAG_300__CODEBLOCK_40__HTM LTAG_301__HTMLTAG_302___設定:
CODEBLOCK_41__HTMLTAG_305__HTMLTAG_306_收回p 使用 WAL-G:_HTMLTAG_308__CODEBLOCK_42__HTMLTAG_309__HTMLTAG_310_使用 WAL-G 恢復:_HTMLTAG_312使用 WAL-G 恢復:___HTMLTAG_31216___CODEBLOC_431315312312512312572。災難復原計畫___HTMLTAG_314__HTMLTAG_315_6.1。災難復原策略_HTMLTAG_316__HTMLTAG_317__HTMLTAG_318_3-2-1規則：_HTMLTAG_320__CODEBLOCK_44__HTMLTAG_321_6.2。災難復原清單_HTMLTAG_322__HTMLTAG_323__HTMLTAG_324_準備：_HTMLTAG_326__CODEBLOCK_45__HTMLTAG_327_6.3。 DR 場景與流程_HTMLTAG_328__HTMLTAG_329_情境 1：資料庫損壞_HTMLTAG_330__CODEBLOCK_46__HTMLTAG_331_情境 2：資料中心故障_HTMLTAG_332__CODEBLOCK_47___情境3：意外資料刪除_HTMLTAG_334__CODEBLOCK_48__HTMLTAG_335_6.4。恢復指標_HTMLTAG_336__HTMLTAG_337__HTMLTAG_338___RTO（恢復時間目標）：HTMLTAG_340__CODEBLOCK_49 HTMLTAG_341__HTMLTAG_342___RPO（恢復點）目標）：HTMLTAG_344__CODEBLOCK_50__HTMLTAG_345_7。監控和警報_HTMLTAG_346__HTMLTAG_347_7.1。關鍵備份指標_HTMLTAG_348__CODEBLOCK_51__CODEBLOCK_52__HTMLTAG_349_7.2。普羅米修斯指標_HTMLTAG_350__CODEBLOCK_53__HTMLTAG_351_7.3。備份驗證_HTMLTAG_352__CODEBLOCK_54__HTMLTAG_353_8。最佳實務_HTMLTAG_354__HTMLTAG_355✅ 執行___HTMLTAG_356__HTMLTAG_357__HTMLTAG_358__HTMLTAG_359_啟用 WAL 歸檔 - PITR所需_HTMLTAG_361__HTMLTAG_362__HTMLTAG_363___自動化備份 - 透過 cron/systemd 計時器進行每日 pg_basebackup____HTMLTAG_365__HTMLTAG_366__14G_366__138_365%366F366F____366演練_HTMLTAG_369__HTMLTAG_370__HTMLTAG_371_監控存檔 - 失敗警報_HTMLTAG_373__HTMLTAG_374__HTMLTAG_375 每天保留多個世代 403407 次備份;次___HTMLTAG_377__HTMLTAG_378__HTMLTAG_379_場外備份-S3，不同區域/資料中心_HTMLTAG_381__HTMLTAG_382__HTMLTA G_383_加密備援 -靜態與傳輸中__HTMLTAG_385__HTMLTAG_386__HTMLTAG_387_文件流程 -用於復原的操作手冊_HTMLTAG_389__HTMLTAG_390__HTMLTAG_391___驗證備份 - 每次備份後的 pg_verifybackup___HTMLTAG_393__HTMLTAG_394__HTMLTAGTO_395___MLTAG_393__HTMLTAG_394__HTMLTAGTO_395__Um 從R4_HT了解您的限制_HTMLTAG_397__HTMLTAG_398__HTMLTAG_399❌不要___HTMLTAG_400__HTMLTAG_401__HTMLTAG_402__HTMLTAG_403_不要跳過測試_MLTAG_404___MLTAG_404___403_F否備份___HTMLTAG_405__HTMLTAG_406__HTMLTAG_407_不要只在本機上儲存 - 資料中心故障=資料遺失__HTMLTAG_409__HTMLTAG_410__HTMLTAG_資料遺失____HTMLTAG_409__HTMLTAG_410__HTMLTAG_資料遺失____HTMLTAG_409__HTMLTAG_410__HTMLTAG_資料遺失__HT)445444444444164113元-無提示資料遺失風險_HTMLTAG_413__HTMLTAG_414__HTMLTAG_415_不要過早刪除 WAL - 需要 PITR__HTMLTAG_417__HTMLTAG_418__HTMLTAG_419___MLTAG_417__HTMLTAG_418__HTMLTAG_419___儲存成本與復原需要_HTMLTAG_421__HTMLTAG_422__HTMLTAG_423_不要備份到同一磁碟 - 磁碟故障 = 一切遺失__HTMLTAG_425__HTMLTAG_426__HTMLTAG_427_不要跳過加密 -安全/合規風險__HTMLTAG_429__HTMLTAG_430__HTMLTAG_431__不要假設它有效- 驗證、驗證、驗證_HTMLTAG_433__HTMLTAG_434__HTMLTAG_435_9。實驗室練習_HTMLTAG_436__HTMLTAG_437_實驗室 1：設定 WAL 歸檔_HTMLTAG_438__HTMLTAG_439__HTMLTAG_440_任務：_HTMLTAG_442__HTMLTAG1_434HT43441442__HT和archive_command___HTMLTAG_445__HTMLTAG_446_建立存檔目錄_HTMLTAG_447__HTMLTAG_448___強制WAL切換：SELECT pg_switch_wal();HTMLTAG_450__HTMLTAG_451__HTMLTAG_452_驗證檔案中的WAL檔案目錄_HTMLTAG_453__HTMLTAG_454______監視 pg_stat_archiver___HTMLTAG_455__HTMLTAG_454___HT45456 2：取得基礎備援_HTMLTAG_458__HTMLTAG_459__HTMLTAG_460___任務：HTMLTAG_462__HTMLTAG_463__HTMLTAG_464______使用pg_basebackup____MLTA_463__HTMLTAG_464___使用pg_basebackup________ML_466 ifybackup____HTMLTAG_467__HTMLTAG_468_計算備援大小與時間__HTMLTAG_469__HTMLTAG_470_壓縮備份並比較大小__HTMLTAG_471__HTMLTAG_47215MLTAG1_473HTMLTAGML_47412 3：執行PITR___HTMLTAG_476__HTMLTAG_477__HTMLTAG_478_任務：_HTMLTAG_480__HTMLTAG_481__H TMLTAG_482_建立帶有時間戳記的測試表__HTMLTAG_483__HTMLTAG_484_進行基本備援_HTMLTAG_485__HTMLTAG_486_插入更多資料_HT MLTAG_487__HTMLTAG_488_注意特定時間戳_HTMLTAG_489__HTMLTAG_490_在時間戳後插入「錯誤」資料__HTMLTAG_491__HTMLTAG_4 92_恢復到時間戳記（錯誤資料之前）_HTMLTAG_493__HTMLTAG_494_驗證恢復點是正確_HTMLTAG_495__HTMLTAG_496__HTMLTAG_497_實驗4：自動備份_HTMLTAG_498__HTMLTAG_499__HTMLTAG_500_任務：_HTMLTAG_502__HTMLTAG_503 __HTMLTAG_504_編寫保留的備份腳本__HTMLTAG_505__HTMLTAG_506_新增錯誤處理和通知_HTMLTAG_507__HTMLTAG_508_使用cron 排程_HTMLTAG_509__HTMLTAG_510_測試腳本執行_HTMLTAG_511__HTMLTAG_512_監控備援日誌_HTMLTAG_513__HTMLTAG_514__HTMLTAG_515_實驗室5：災難復原鑽_HTMLTAG_516__HTMLTAG_517__HTMLTAG_518_任務：_HTMLTAG_520__HTMLTAG_521__HTMLTAG_522______整個資料庫遺失（刪除資料目錄）_MLTAG_MLHTMLTAG1522_145ML_ML）___ML TMLTAG_526_重播WAL到最新觀點_HTMLTAG_527__HTMLTAG_528_測量RTO（恢復時間）_HTMLTAG_529__HTMLTAG_530_驗證資料完整性_HTMLTAG_531__HTMLTAG_532_____1記錄。疑難排解_HTMLTAG_536__HTMLTAG_537_問題：存檔不起作用_HTMLTAG_538__HTMLTAG_539__HTMLTAG_540___症狀：failed_count > 0 列印pg_stat_archiver____HTMLTAG_542__HTMLTAG_543__HTMLTAG_544檢查:HTMLTAG_546__CODEBLOCK_55__HTMLTAG_5 47__HTMLTAG_548__通用原因：_HTMLTAG_550__HTMLTAG_551__HTMLTAG_552_存檔目錄的權限被拒絕_HTMLTAG_553__HTMLTAG_554_存檔目錄不存在__HTMLTAG_555__HTMLTAG_556_磁碟已滿_HTMLTAG_557__HTMLTAG_558_網路問題（如果遠端存檔）_HTMLTAG_559__HTMLTAG_560__HTMLTAG_561___問題：pg_basebackup慢___HTMLTAG_562__HTMLTAG_563__HTMLTAG_564_優化：_HTMLTAG_566__CODEBLOCK_56__HTMLTAG_567_問題：PITR失敗 - WAL不找到_HTMLTAG_568__HTMLTAG_569__HTMLTAG_570_錯誤：無法開啟檔案「000000010000 000000000007」：沒有這樣的檔案或目錄_HTMLTAG_573__HTMLTAG_574__HTMLTAG_575__HTMLTAG_576___原因：WAL文件不在存檔或restore_command 中錯誤___HTMLTAG_578__HTMLTAG_579__HTMLTAG_580_修正：_HTMLTAG_582__CODEBLOCK_57__HTMLTAG_583_11。摘要_HTMLTAG_584__HTMLTAG_585___備份策略摘要



HTMLTAG_588__HTMLTAG_589__HTMLTAG_590__HTMLTAG_591___方法___HTMLTAG_592__HTMLTAG_593___RPO HTMLTAG_594__HTMLTAG_595___RTO___HTMLTAG_596__HTMLTAG_597___複雜性___HTMLTAG_598__HTMLTAG_599___使用案例 pg_dumpHTM LTAG_607___小時/天___HTMLTAG_608__HTMLTAG_609___小時___HTMLTAG_610__HTMLTAG_611___低___HTMLTAG_612__HTMLTAG_613___小資料庫，遷移___HTMLTAG_614__HTMLTAG_615__HTMLTAG_616__HTMLTAG_617___pg_basebackup___HTMLTAG_618__HTMLTAG_619___上次備份___HTML TAG_620__HTMLTAG_621___30-120分鐘___HTMLTAG_622__HTMLTAG_623___中___HTMLTAG_624__HTMLTAG_625___定期備份___HTMLTAG_626 HTMLTAG_627__HTMLTAG_628__HTMLTAG_629___WAL存檔___HTMLTAG_630__HTMLTAG_631___分鐘___HTMLTAG_632__HTMLTAG_633___30-120分鐘___HTMLTAG_634__HTMLTAG_635___中___HTMLTAG_636__HTMLTAG_637___PITR功能___HTMLTAG_638__HTMLTAG_639__HTMLTAG_640__HTMLTAG_641_______HTMLTAGML____2__42142_______ HTMLTAG_644__HTMLTAG_645___30-60秒___HTMLTAG_646__HTMLTAG_647___高____HTMLTAG_648__HTMLTAG_649___HA，零資料遺失____HTMLTAG_650__HTMLTAG151

關鍵概念____HTMLTAG_656__HTMLTAG_657___✅WAL 歸檔_ -交易的持續備份日誌___HTMLTAG_660__HTMLTAG_661___✅ pg_basebackup -整個叢集的實體備份___HTMLTAG_664__HTMLTAG_665___✅ PITR - 使用下列指令還原到任意時間點基本備份 + WAL___HTMLTAG_668__HTMLTAG_669___✅ RTO - 恢復速度有多快___HTMLTAG_672__HTMLTAG_673___✅ML ___MLTAG_672__HTMLTAG_673___✅ML ___MLG_F___4____4_____F&&&nb&___&F&&nb&___4____4&F&F&&F&&&&&&44&___資料遺失量是多少可接受___HTMLTAG_676__HTMLTAG_677___✅ 3-2-1規則- 3份副本，2種媒體類型，1份場外___HTMLTAG_680__HTMLTAG_681___恢復清單___HTMLTAG_682__HTMLTAG_683__HTMLTAG_684___停止PostgreSQL___HTMLTAG_685__HTMLTAG_686___ 還原基本備援___HTMLTAG_687__HTMLTAG_688___ 建立復原.訊號___HTMLTAG_689__HTMLTAG_690___設定Restore_command___HTMLHTMLTAG_689__HTMLTAG_690___配置Restore_command___HTMLHTMLTAG191121212___設定恢復目標（時間/xid/lsn）___HTMLTAG_693__HTMLTAG_694___&啟動 PostgreSQL____HTMLTAG_695__HTMLTAG_696___ 監控恢復日誌___HTMLTAG_697__HTMLTAG_698___ 驗證恢復點____HTMLTAG_699__HTMLTAG_700___ 如果滿意則升級___HTMLTAG_701__若滿足則更新複製需要___HTMLTAG_703__HTMLTAG_704__HTMLTAG_705___後續步驟____HTMLTAG_706__HTMLTAG_707___第 17課程將涵蓋_監控和可觀察性:___HTMLTAG_710__HTMLTAG_711__HTMLTAG_712___Prometheus + Grafana設定___HTMLTAG_713__HTMLTAG_712___Prometheus + Grafana設定___HTMLTAG_713__HTMLTAG_712___Prometheus + Grafana設定___HTMLTAG_713__HTMLTAG_712___Prometheus + Grafana設定___HTMLTAG_713__HTMLTAG_7114___ 關鍵指標_監控___HTMLTAG_717__HTMLTAG_718___日誌聚合___HTMLTAG_719__HTMLTAG_720___警報策略___HTMLTAG_721__HTMLTAG_722___效能儀表板____HTMLTAG_723__HTMLTAG_724___

第 16 課：備份和時間點復原 (PITR)

Pros:

✅ Easy to restore specific tables

✅ Portable across PostgreSQL versions

✅ Human-readable (text)

Cons:

❌ Slow for large databases

❌ Not suitable for PITR

❌ Requires downtime for consistent backup

B。實體備份___HTMLTAG_92__CODEBLOCK_1__HTMLTAG_93___C。連續歸檔（WAL 歸檔）___HTMLTAG_94__CODEBLOCK_2__HTMLTAG_95___1.2。 RTO 和 RPO：目標）= 可接受的資料遺失量是多少？ ___CODEBLOCK_4__HTMLTAG_105___1.3。備份策略決策矩陣

B。存檔至 S3 (wal-g)___HTMLTAG_178__CODEBLOCK_11__HTMLTAG_179___C。壓縮存檔___HTMLTAG_180__CODEBLOCK_12__HTMLTAG_181___2.4。監控歸檔

Common errors:

- Permission denied on archive directory

- Archive directory full

- Network timeout (for remote archiving)

B。恢復到特定事務___HTMLTAG_246__CODEBLOCK_27__HTMLTAG_247___C.恢復到特定 LSN___HTMLTAG_248__CODEBLOCK_28__HTMLTAG_249___D。恢復到最新的___HTMLTAG_250__CODEBLOCK_29__HTMLTAG_251___E。恢復目標（包含/排除）

B。實體備份___HTMLTAG_92__CODEBLOCK_1__HTMLTAG_93_C。連續歸檔（WAL 歸檔）_HTMLTAG_94__CODEBLOCK_2__HTMLTAG_95_1.2。 RTO 和 RPO：目標）= 可接受的資料遺失量是多少？
_CODEBLOCK_4__HTMLTAG_105___1.3。備份策略決策矩陣

B。存檔至 S3 (wal-g)___HTMLTAG_178__CODEBLOCK_11__HTMLTAG_179_C。壓縮存檔_HTMLTAG_180__CODEBLOCK_12__HTMLTAG_181___2.4。監控歸檔

B。恢復到特定事務___HTMLTAG_246__CODEBLOCK_27__HTMLTAG_247_C.恢復到特定 LSN_HTMLTAG_248__CODEBLOCK_28__HTMLTAG_249_D。恢復到最新的_HTMLTAG_250__CODEBLOCK_29__HTMLTAG_251___E。恢復目標（包含/排除）