Recent content by Stefano Giunchi

I created this Feature Request, please add comments to upvote: [Feature Request] Backup retry

After I realized (remembered) that PBS is on a container, and not a VM, I tried to reboot the host, and it resolved the problem.

Thank you, I tried curl. I get root@PBS1:~# curl -k -d 'username=root@pam' --data-urlencode 'password=HIDDEN' https://127.0.0.1:8007/api2/json/access/ticket permission check failed. syslog: 2024-11-21T14:04:56.934560+00:00 PBS1 proxmox-backup-api[6205]: authentication failure...

After a power issue that caused the PBS vm to crash, I can't login anymore via web. PVE connections don't work, too. I can login in ssh. In /var/log/syslog I have these errors, repeated every 10 seconds: 2024-11-21T10:24:46.980889+00:00 PBS1 proxmox-backup-api[146]: authentication failure...

Sorry, I didn't remember correctly: in the vm settings, go to options > SMBIOS and write "HPE" in the manufacturer field and the S/N of the hardware in the Serial field.

I have no problem with HPE ROK. You download or create the ISO from the DVD, mount it on the VM and install as if it was on bare metal. In italiano, ma per favore scrivi in inglese: non ho problemi con HPE ROK. Scarichi o crei la ISO dal DVD, la monti sulla VM ed installi come se fosse su...

I already found, I have to use proxmox proxmox-backup-manager: proxmox-backup-manager garbage-collection start mydatastore It doesn't need password.

I want to schedule my datastores garbage collection with cron, because if I use WebUI scheduling I risk to overlap GC jobs (my PBS is on spinning disks). I see that to use the command proxmox-backup-client garbage-collect permission mydatastore, I need to write the user password in the...

Hi, thank you for your answers. I found the problem. I'm so stupid. I gave the same IP address to the nodes, on the migration network. :cool:

I have an old cluster, which grew up from PVE 4, and changing various servers. Yesterday I completed the last transformation, and now it's a two-nodes PVE 8.1 with ZFS-replication. I also renamed the servers, and resolved the typical issues I see many had when doing it. Anyway I say I've done...

I disabled and the re-enabled the storage. I thought it would umount and remount, but it doesn't. After unmounting manually the storage, it has remounted with the retrans=5 option.

Unfortunately, bad things happen. I think it's better to keep the VM running, and get a "failed backup" error, than having the VM hung because the backup NAS is crashed. If the corruption is really "silent", and no error is received from vzdump, I agree with you that "soft" must not be used...

I had the backup storage mounted with NFS shared by a NAS. Until last week I always used the default "hard" connection. If NAS dies during backup, the VM which was backed up freezes until I don't force unmount the NFS share. Then I found the "soft" NFS option in this thread, and I tried to use...

In my last install (today) I just had to use this in the config file args: -smbios type=11,value=x and added this in UI > Options > SMBIOS settings > Manufacturer: Dell Computer Corporation

From the file I read In fact, depending on the backup speed, VMs are not slowed down a bit: they are slowed down a lot, freezed or even crashed. On Windows machines, I receive the ESENT/508 error: svchost (1008) SoftwareUsageMetrics-Svc: A request to write to the file...