S3 endpoint with Google Cloud Storage

Dec 23, 2021
11
1
8
52
Hi there, long time PVE user here, but first time user of PBS, strongly attracted by the new S3 feature
I know it is in tech preview mode and I thank the devs for this great feature
Anyone knows if a config is possible for Google Storage?
I tried many URL and settings when trying create a S3 endpoint in PBS, to no avail (tried both host and path style, but I’m missing something I guess)
Any help appreciated
Many thanks!
 
I tried many URL and settings when trying create a S3 endpoint in PBS, to no avail (tried both host and path style, but I’m missing something I guess)
Please share the (retracted) s3 endpoint config and exact errors you are getting for us to help, thanks!
 
Thank you. I tried again and this time it worked when creating an S3 Endpoint. If that can help others, this URL worked for me for Google Cloud Storage:
{{bucket}}.storage.{{region}}.rep.googleapis.com
I found out using that resource: https://cloud.google.com/storage/docs/regional-endpoints?hl=en#xml-api
Strangely enough, I used another documentation page from Google yersterday and those URL didn't work

However, I then try to add a S3 data store and I then get the message (and the S3 datastore doesn't get created):
"failed to get in-use marker from bucket: unexpected status code 400 Bad Request"

If any one has an idea.... Thx!
 
Last edited:
What is the output of the following commands:
Code:
proxmox-backup-manager s3 list-buckets <endpoint-id>
proxmox-backup-manager s3 check <s3-endpoint-id> <bucket>
 
EDIT: I might have found out, it seems storage.{{region}}.rep.googleapis.com enables me to then create an S3 datastore. Currently testing...

Thanks. Here are the outputs (I added endpoint in the command):
proxmox-backup-manager s3 endpoint list-bucket Google
Result: [
{
"name": "backup-myname-01"
},
{
"name": "backup-myname-02"
},
{
"name": "backup-myname-03"
}
]

************************
proxmox-backup-manager s3 check Google backup-myname-03
<?xml version='1.0' encoding='UTF-8'?><Error><Code>InvalidBucketName</Code><Message>The specified bucket is not valid.</Message><Details>Invalid bucket name: '.s3-client-test'</Details></Error>
Error: put object failed

Caused by:
invalid request
 
Last edited:
Ooooh, goodness, it works, I can backup to my Google Cloud Storage using PBS: so cool!
Many thanks, sorry for disturbing.
Again for those like me who use regional Google Cloud Platform, the URL to use is :
storage.{{region}}.rep.googleapis.com

EDIT: one backup job completed fine (3Gb), but another one 95Gb never compelted twice, with the PBS server 'vanishing' (load average going to 0), not sure what's happening, and the PBS UI not responding anymore
I rebooted the PBS server whil the backup job was stuck and got this error message in the backup log "ERROR: backup close image failed: command error: stream closed because of a broken pipe"
 
Last edited:
Morning everyone,
After upgrading to 4.0.15, I tried with my Google S3 endpoint and tried also with a Backblaze S3 endpoint: my 'big' backup (around 95Gb of disks which is a backup of 33Gb at the end) is uploaded to the Clouds but the backup does not go further than 100%: it never finishes, I have to stop them manually. I can see the data is uploaded in the cloud bucket.
Again the PBS seems to 'vanish' (load 0.00)
Just reporting as I don't know what to do
 
Please share the output of qm config <VMID> --current as well as the backup task log from the PVE and PBS host for this particular backup. Also, can you attach to the proxy via strace -ftt -p $(pidof proxmox-backup-proxy) right before you reach the 100% and the proxy hangs, that might help for debugging. As the strace output might contain sensitive information, you can share or send it to me via some private channel, e.g. by sending me a direct message with a link to a private cloud to download from.

See also the discussion in https://forum.proxmox.com/threads/s3-backup-status.170659/

Edit: Also check the output of proxmox-backup-manager version --verbose to make sure your running version is indeed 4.0.15. Further, what disk/filesystem are you using for the local store cache?
 
Last edited:
Hi Chris, thx for your msg. I'm not in front of my systems, I just have some limited remote access, and therefore will provide the rest of the info in 2-3 days
Here you are with what I could collect so far:
qm config 302 --current

agent: 1,fstrim_cloned_disks=1
balloon: 8192
boot: dcn
bootdisk: scsi0
cores: 5
cpu: host
description: Debian 13, Docker & docker-compose
ide2: none,media=cdrom
memory: 16384
name: hydre
net0: virtio=A2:4F:39:BA:9D:C0,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
protection: 1
scsi0: nvme-btrfs_1Tb:302/vm-302-disk-0.raw,discard=on,size=16G,ssd=1
scsi1: nvme-btrfs_1Tb:302/vm-302-disk-1.raw,backup=0,discard=on,size=26G,ssd=1
scsi2: nvme-btrfs_1Tb:302/vm-302-disk-2.raw,discard=on,size=79G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=1b2763d3-02b2-4c96-a4ec-c0c8a5379d05
sockets: 1
startup: order=2,up=160
tags: prod;vm
usb0: host=10c4:ea60
vmgenid: aa5f01a6-12fc-480e-8fc7-968b72e69aa9


proxmox-backup-manager version --verbose

proxmox-backup 4.0.0 running kernel: 6.14.11-2-pve
proxmox-backup-server 4.0.15-1 running version: 4.0.15
proxmox-kernel-helper 9.0.4
proxmox-kernel-6.14.11-2-pve-signed 6.14.11-2
proxmox-kernel-6.14 6.14.11-2
proxmox-kernel-6.14.8-2-pve-signed 6.14.8-2
ifupdown2 3.3.0-1+pmx10
libjs-extjs 7.0.0-5
proxmox-backup-docs 4.0.15-1
proxmox-backup-client 4.0.15-1
proxmox-mail-forward 1.0.2
proxmox-mini-journalreader 1.6
proxmox-offline-mirror-helper 0.7.2
proxmox-widget-toolkit 5.0.5
pve-xtermjs 5.5.0-2
smartmontools 7.4-pve1
zfsutils-linux 2.3.4-pve1


Disk and file system of local store cache: virtual disk on SSD formatted with EXT4