Borgbackup is unable to pull data from remote hosts to a central location.

I do not understand this assertion.

what kind of inventory we want to do with this? hardware? software? both?

In T1372#26104, @ftigeot wrote:

Borgbackup is unable to pull data from remote hosts to a central location.

There is a huge difference between Borgbackup and Rsnapshot + Backuppc: Borgbackup is unable to pull data from remote hosts to a central location.
Its working model is based on Borgbackup running locally and storing data to a local filesystem.

New hypervisor hardware has been racked in our bay at Rocquencourt.
The machine's iDrac management interface is accessible on the management network, under the name swh7-adm.inria.fr (details on the wiki).

Service postgresql@10-indexer.service has been restarted on somerset and database replication is once again operating normally.
Postgres wal files are being removed as expected on the master, slowly freeing disk space.

Batteries for PERC H700 adapters have the part number U8735 and/or NU209.

Some no longer useful dump files were removed by seirl@, freeing some space on somerset:/srv/softwareheritage/postgres .

somerset:softwareheritage-indexer is the master database for dbreplica1:softwareheritage-indexer.

The pvmove command was done this morning.

Target size: 8 TB striped across 8 disks (from 2 TB on a single disk).

ncdu on several million inodes is *slow*, this is going to take a while...

In the current (fairly time sensitive) situation, the most sensible option seems to be Azure Cool storage in the West Europe region, minding the exit cost of storing data there.

At least some of the batteries for PERC H800 adapters use part number KR174 and/or M164C.
Some information leads me to believe they could also be used with PERC H700 adapters.

I did some experiments with Letsencrypt but other things were more urgent during the September-October 2018 period and in the end a wildcard Digicert certificate was used again instead.

What's the status of this task? October is long gone now, so either the problem has been (temporarily) fixed or it was not really a problem (?)