Menu
▾
▴
[BackupPC-users] Incorrect reported pool size, and confusing queue reporting
|
From: Matthew P. <ma...@co...> - 2020-02-27 22:03:55
|
I've got a new install of BackupPC 3.3.2 installed from the Debian 10 apt
repository. My /var/lib/backuppc volume is 15TB, and BackupPC currently
has ~480GB of data on it. However, the front page graph and "Other info"
summary both say that the pool is only 1.93G, and has done since the server
came online about 16 hours ago.
How does it calculate what's currently in the pool? I'm wondering if
something somewhere has got stuck.
% df -h /var/lib/backuppc
Filesystem Size Used Avail Use% Mounted on
backups 15T 481G 14T 4% /var/lib/backuppc
- The servers PID is 31493, on host bk, version 3.3.2, started at
2020-02-27 00:40.
- This status was generated at 2020-02-27 21:28.
- The configuration was last loaded at 2020-02-27 19:00.
- PCs will be next queued at 2020-02-27 22:00.
- Other info:
- 22 pending backup requests from last scheduled wakeup,
- 0 pending user backup requests,
- 0 pending command requests,
- Pool is 1.92GB comprising 133570 files and 4369 directories (as of
2020-02-27 01:00),
- Pool hashing gives 4 repeated files with longest chain 1,
- Nightly cleanup removed 15 files of size 0.00GB (around 2020-02-27
01:00),
- Pool file system was recently at 4% (2020-02-27 21:24), today's max
is 7% (2020-02-27 11:30) and yesterday's max was 1%.
Another thing I note that seems odd... those 22 pending backup requests
aren't all actually pending. Nearly all of the hosts have completed a full
backup today.. there are four currently running backups, three waiting for
an available slot, two that are in "no ping", and 13 with completed full
backups sometime in the past 5 hours. Yet, all 22 servers appear in the
Background Queue Summary with a request time anywhere between 90 minutes
and 3.5 hours in the past.
I have no idea if this is related to the misreported pool size, but it
suggests to me even more that something somewhere is stuck. What should I
be looking at?
|
