kk的blog: pbs

顯示具有 pbs 標籤的文章。顯示所有文章

2026/07/20

今天早上來看到昨天的PVE備份沒成功

備分到 192.168 段nas的都沒成功

因為我的几器也是 192.168

一樣ping不到pbs

但跟host在同一段的ip使用都沒問題

第一次碰到這種

可能的原因應該是上週 kernel 升到 7.0.14-5

但在某些 host 又沒問題

先把guest移到沒問題的host

再把有問題host先開回舊kernel試看看

使用 proxmox-boot-tool

列出目前 kernel

proxmox-boot-tool kernel list

pin 回舊kernel

proxmox-boot-tool kernel pin 7.0.14-4-pve
proxmox-boot-tool refresh
reboot

之後要解除使用 unpin
proxmox-boot-tool kernel unpin
proxmox-boot-tool refresh


反覆試了几次 看起來也不是kernel的問題
目前只剩一台guest有問題 只能跑在固定的host
先醬 再觀察看看吧

最後查到是arp的問題
到網路設備 clear arp

2025/12/05

Proxmox Datacenter Manager 終於釋出 1.0 stable

但還是有滿大的進步空間

pve 8 版不支援打開 shell console

無法直接在PDM打開 guest console 還是必須叫出原 cluster的管理畫面並且輸入帳號密碼

guest config 也沒辦法在 PDM 修改

pbs無法還原備分

https://forum.proxmox.com/threads/proxmox-datacenter-manager-1-0-stable.177320/

2025/11/27

昨天 pbs 出了 4.1.0 版

release note 有一點感覺有點有趣

Allow to control parallelism of verify jobs.

Backup snapshot verification is both an IO- and CPU-heavy workload, as it needs to read chunks from disk and verify their checksums.

The number of threads used for reading from disk and for checksum verification can now be customized.

In some setups, customizing the number of threads can significantly decrease the overall runtime of the verify job.

升級後跑了一下竟然省了一半的時間

該期間cpu使用率如下

預設是 read 1 verify 4

找時間再來調大看看會不會效果更好

https://pbs.proxmox.com/wiki/Roadmap#Proxmox_Backup_Server_4.1

2025/11/05

早上死掉一台synology的nas

因為是mount nfs 給pbs 備分用

所以要先把備分移到別台nas

然後在pbs上disable datastore

指令如下

Set to Offline (Disables all access)

proxmox-backup-manager datastore update <datastore-name> --maintenance-mode offline

Set to Read-Only (Allows restores, no new backups)

proxmox-backup-manager datastore update <datastore-name> --maintenance-mode read-only

Re-enable (Go Online)

proxmox-backup-manager datastore update <datastore-name> --delete maintenance-mode

再來修改 /etc/fstab 先把該nfs mount point 註解

重開几

讓pbs繼續運作

PVE上的storage也要先disable 然後把備分改到其他storage

等修好後再 enable

2024/12/20

Proxmox Datacenter Manager 發表了第一個Alpha

裝起來看了一下

目前還沒什麼功能

pbs也不能管

等正式版出來再玩吧

https://forum.proxmox.com/threads/proxmox-datacenter-manager-first-alpha-release.159324/

2023/04/09

在 proxmox backup server 中使用 api 撈取相關資料

先建立 API token 要記住 token

再設定權限

使用 curl 撈取相關資料範例如下

curl --location --insecure --request GET 'https://10.0.0.1:8007/api2/json/nodes/{localhost}/tasks' --header 'Authorization: PBSAPIToken=root@pam!abc:your_token'|jq

API相關資料路徑可參考以下原廠連結

https://pbs.proxmox.com/docs/api-viewer/index.html

2023/02/04

今天在檢查 pbs 時又出現 GC (garbage collection) warning 的log

再去看前一天的備分

是顯示備份完成且沒有錯誤的

不知道為什麼備分完成沒有錯誤但GC時會出現如下的錯誤

2023-02-02T00:00:22+08:00: WARN: warning: unable to access non-existent chunk 4d9f87572f2ff8d9f324aef1263e1ab47181a764aac801918b6dd5567fdfdde9, required by "/mnt/nfs418/ct/112/2023-01-31T16:00:47Z/catalog.pcat1.didx"

2023-02-02T00:00:22+08:00: WARN: warning: unable to access non-existent chunk e82ad3ac9b4b29c55420a44c29029c1a69ebd2cae156994c7e6a4f6a3b44524d, required by "/mnt/nfs418/ct/112/2023-01-31T16:00:47Z/catalog.pcat1.didx"

2023-02-02T00:00:22+08:00: WARN: warning: unable to access non-existent chunk 7eeadcfafebe86f0244ab4b07167644784be8485da119208d91e078efb48a7de, required by "/mnt/nfs418/ct/112/2023-01-31T16:00:47Z/root.pxar.didx"

而且問題來了

再接下來每一次備分都會顯示備分完成無異常

但GC就會一直錯誤

而且一旦GC有錯誤這個備分就無法還原

目前pbs在GC有錯誤時無法主動發mail 告警

所以解決方法就是寫個程式每天檢查GC是否有錯誤

如果有

就要把有錯誤相關的備分砍了

讓接下來的備分能正常

2023/01/10

前一陣子發生了一件很OX的事

試了很久現在做個記錄

因為有幫別的部門架了一台proxmox

而且那個部門也有一台nas

因此我就在那台nas上開了nfs然後用pbs備份

他老兄在某一天竟然進到nas把我備分用的那個nfs裡的資料砍了

然後第二天就出現了如下的error

ProxmoxBackup Server 2.3-2

2022-12-29T00:00:00+08:00: starting garbage collection on store nfs418

2022-12-29T00:00:00+08:00: task triggered by schedule 'daily'

2022-12-29T00:00:00+08:00: Start GC phase1 (mark used chunks)

2022-12-29T00:01:03+08:00: marked 5% (1 of 17 index files)

2022-12-29T00:04:14+08:00: marked 11% (2 of 17 index files)

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk c3fe251560dcd2cc5aef7cfbd6669d0dd9ca7491c455f537efc6d319b09892ec, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 6dc29793341c20c7c80910a73893501b034a0e29c14a444d214d835ccffc0d16, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 1f81c244f9b7816ab37d3ef7ffdcd10443eb1bddb3fa44e036186b73f1fee33a, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 95c7e6747d43b5b516e1768a1f258f352aeb47b23fd46575440dc3d820d1b253, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 9513a7e5c650245d3344115115b21285cc8f426e5284fa04159ea96e49856535, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 68b2b40dd3bacba9e649c67862011934bc7f048d8ea2d35fbd95c39f9d5cf7c4, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 494608d49f57039fd7a8378e1a2a2cf6bb0688773a525addc2f54507a94cd11d, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 09eab384d5f3cbf657db1c0750ef52be2f1dbdf134f977a24dc095382b6e25ed, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

2022-12-29T00:04:14+08:00: WARN: warning: unable to access non-existent chunk 9c1208d43242276c75a4f65f41054e4bc0e7e1144a61c951902bb8df94f055c9, required by "/mnt/nfs418/vm/108/2022-12-27T15:45:38Z/drive-virtio0.img.fidx"

..........................................

後面還一大堆

本來是想說把pbs上的datastore砍了重建應該可以解決問題

forum上也是醬說的

結果不是

我砍了datastore重建

甚至在nas上再開另一個nfs後再重建datastore

過沒几天又會出現如上的錯誤

最後的解決方法是直接重裝一台新的pbs

問題才解決

無言中

2022/07/29

說明一下如何在almalinux 8 上備分資料到 proxmox backup server(pbs)

先在 pbs 上建立一個 datastore test

到以下網站下載rpm進行安裝

https://github.com/sg4r/proxmox-backup-client

先安裝相依套件

dnf install fuse3

接下來

rpm -Uhv proxmox-backup-2.2.2-1.x86_64.rpm

安裝完成後執行以下指令

proxmox-backup-client login --repository root@pam@10.0.0.1:8007:test

匯入 fingerprints

如果要備份 /root

建立以下shell

#!/bin/bash

export PBS_PASSWORD="password"

proxmox-backup-client backup aaa.pxar:/root --repository root@pam@10.0.0.1:8007:test

列出備份資料

proxmox-backup-client snapshot list --repository root@pam@10.0.0.1:8007:test

復原備分資料

proxmox-backup-client restore --repository root@pam@10.0.0.1:8007:test host/test-pbs-almalinux8/2022-07-29T06:23:05Z aaa.pxar /tmp/test

https://www.coderstudy.co/zh-Hant/article/19cs1_1anq7.html

2021/10/01

在synology的nas裝好 pbs後

要更新出現以下的錯誤

Err:4 http://download.proxmox.com/debian/pbs bullseye InRelease

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59

Reading package lists... Done

W: GPG error: http://download.proxmox.com/debian/pbs bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59

E: The repository 'http://download.proxmox.com/debian/pbs bullseye InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

應該是GPG key 沒有裝

以下指令安裝

wget https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg

再update就沒問題了

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_Proxmox_VE

2021/09/07

今天在docker 安裝完pbs後要更新出現以下的錯誤

Hit:1 http://deb.debian.org/debian bullseye InRelease

Hit:2 http://security.debian.org/debian-security bullseye-security InRelease

Hit:3 http://deb.debian.org/debian bullseye-updates InRelease

Get:4 http://download.proxmox.com/debian/pbs bullseye InRelease [3067 B]

Err:4 http://download.proxmox.com/debian/pbs bullseye InRelease

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59

Reading package lists... Done

W: GPG error: http://download.proxmox.com/debian/pbs bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DD4BA3917E23BF59

E: The repository 'http://download.proxmox.com/debian/pbs bullseye InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

解決方法如下

wget https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_Proxmox_VE

https://forum.proxmox.com/threads/problem-with-repository-and-upgrade.95020/

2020/10/20

原本用來備分的server 在週六掛點

因為已經過保好几年也不修了

打算在synology的vmm起一個pbs

碰到一個很怪的問題

只要我給超過4T的disk

使用XFS

安裝過程都沒問題

但裝完後一定無法開机

如以下畫面

詢問官方的回答

https://www.synology.com/zh-tw/dsm/feature/virtual_machine_manager#supports_OS

因為debian沒有在官方的support os

所以不提供任何support

雖然這是料想到的答案

但還是有點不爽

想到用另一個方式來做

試了給三個5T的disk

然後用 zfs 0 安裝

安裝過程沒問題也能開機

應該只能醬處理了

2020/07/14

今天在測試 proxmox backer server (pbs)
感覺把之前一直敲碗的功能補上了

裝好後必須設定datastore
目前是一定要使用目錄絕對路徑所以只能先到OS把外部的storage mount 進來再設定

如果使用nfs

要記得mount進來後要chown

假設是mount 到 /mnt/abc

chown -R backup.backup /mnt/abc

不知道以後會不會在web補上

再來就是proxmox 要怎麼掛進來用
如果升到 pve-manager 6.2-9
在add storage時就會看到 Proxmox Backup Server可以用
只是要掛上去時試了一下
注意一下要輸入的值

https://www.proxmox.com/en/downloads/category/proxmox-backup-server

訂閱：文章 (Atom)