Tuxis launches free Proxmox Backup Server BETA service

eider

Member
Aug 9, 2018
17
1
8
@tuxis @fabian The backups are still not being verified and I can still not access Verify Jobs tab, being shown permission check failed when accessing /api2/json/admin/verify

I do seem to have Datastore.Verify permission however?
 

Attachments

  • chrome_2020-11-08_00-34-04.png
    chrome_2020-11-08_00-34-04.png
    20.2 KB · Views: 18
Last edited:

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
5,571
925
163
you need proxmox-backup-server >= 0.9.7-1
 

TwiX

Active Member
Feb 3, 2015
251
6
38
Hi

Due to many failed backups and failed verifies, I've decided to delete all the backups and restart from a clean datastore.

But there is still bad chunks :
1605171822269.png

Do you know how to delete them ?

Thanks
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
5,571
925
163
Hi

Due to many failed backups and failed verifies, I've decided to delete all the backups and restart from a clean datastore.

But there is still bad chunks :
View attachment 21137

Do you know how to delete them ?

Thanks

wait a day, then run GC again.
 

Stefan_R

Proxmox Staff Member
Staff member
Jun 4, 2019
1,070
214
68
Vienna
  • Like
Reactions: fabian

elmarconi

Member
Nov 28, 2017
10
1
8
52
Any thought on how to remove the beta from Storage?

All I get is "delete storage failed: error during cfs-locked 'file-storage_cfg' operation: got lock request timeout (500)" and loads of errors in syslog.

pvestatd[4098]: Tuxis_Backup_Beta: error fetching datastores - 500 Can't connect to pbs.tuxis.nl:8007 (Name or service not known)
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
5,571
925
163
Any thought on how to remove the beta from Storage?

All I get is "delete storage failed: error during cfs-locked 'file-storage_cfg' operation: got lock request timeout (500)" and loads of errors in syslog.

pvestatd[4098]: Tuxis_Backup_Beta: error fetching datastores - 500 Can't connect to pbs.tuxis.nl:8007 (Name or service not known)

that means that PVE was not able to obtain a cluster wide lock for modifying storage.cfg, which usually means that your cluster is not quorate...
 

elmarconi

Member
Nov 28, 2017
10
1
8
52
No cluster here.
systemctl restarted a couple of pve services, after that i could disable this Storage, and delete it.

Probably a full disk was one of the cause:
"unable to open file '/etc/pve/nodes/pve4/lrm_status.tmp.4655' - Input/output error"

Solved.
 

Peter123

Member
Mar 5, 2018
38
2
13
51
how do you implement this technically? Do you need a local PBS that replicates to your PBS?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!