Search results

Hi Dominik, thx for your answer, as I wrote it's still a test we did. If I can assist you in testing oder analyzing please let me know... Regards Joachim

OK here is the output, if you need more info, don't hesitate to ask: root@pbs:~# pmt asf 0 --drive HPLTO using device /dev/tape/by-id/scsi-35001438016073e13-sg root@pbs:~# echo $? 0 root@pbs:~# pmt status --drive HPLTO using device /dev/tape/by-id/scsi-35001438016073e13-sg { "vendor": "HP"...

We use a LTO5 Library from HP Model MSL 4048 LIB HP MSL_G3_Series DRIVE HP Ultrium_5-SCSI

root@pbs:~# proxmox-backup-manager versions --verbose proxmox-backup 1.0-4 running kernel: 5.4.119-1-pve proxmox-backup-server 1.1.10-1 running version: 1.1.10 pve-kernel-5.4 6.4-3 pve-kernel-helper 6.4-3...

Hi, while doing a selective TEST restore from tape in a Proxmox Backup Server 1.1-10 we get the following error: 2021-06-18T10:23:54+02:00: Mediaset 'e773924f-5861-4a49-b2bb-1abcb59bce3f' 2021-06-18T10:23:54+02:00: Pool: XXXXXX 2021-06-18T10:23:56+02:00: found snapshot...

Thank you for the hint, now it works again...

After upgrading our test pbs to 1.1-2 no tape or changer activities can be performed without error. On shell level I get the following error message: root@pbs:~# proxmox-tape changer list Error: parsing '/etc/proxmox-backup/tape.cfg' failed: line 4 - unknown section type 'linux' root@pbs:~#...

OK Dominik, I did not find the bug report on my own, so thank you for your hint. We are currently testing tape support so no worries it's not a productive env... Regards Joachim

Hi, while testing tape support I get an error trying to restore an mediaset. I treid to restore a small vm or a mediaset created by proxmox-backup-client to different datastores always the same result. See Screenshot. PBS Server Version 1.0 -13 What am I doing wrong ? Regards Joachim

Today there were new breakdowns in Backup with same behaviour as above. I think there is a Problem with our setup and timeouts. The Backup Server VM is running with backup storage on an nfs share and that nfs share resides for testing purposes on a cheap synology diskstation. This diskstation...

Hi Stoiko, thank you for the suggestions. As this is on the local network only no proxy ore firewall in between. Serverside log is in the first message of this thread. May be that there are some network activities, so I changed the crontab to run later and suprise, it works. But I think if...

OK this morning I found the following from the cron scheduled script: stderr: Error: http upgrade request timed out stdout: Starting backup: host/********/2021-03-05T04:25:01Z Client name: ********

Hi Stoiko thank you for the suggestion and the tipp with -x as well as shellcheck. The stdout of proxmox-backup-client is logged to syslog in case of an error see post above. But I will give the redirection to files a try and see what happens tomorrow... Regards Joachim

Console output (proxmox-backup-client detail output is kept in variable see script): root@********:~# /etc/cron.daily/backup host/********/2021-02-07T10:40:20Z host/********/2021-02-14T04:25:01Z .....

VM is Debian 10.8. There is only a link in /etc/cron.daily called backup pointing to the script root@********:~# ls -al /etc/cron.daily/backup lrwxrwxrwx 1 root root 40 Mär 2 08:53 /etc/cron.daily/backup -> /root/nextcloud-scripts/nc_pbs_backup.sh The scipt looks like this (anonymized...

Hi, we are running a Test Proxmox Backup Server as VM with Version 1.0.8 an are doing file Backups with proxmox -backup-client 1.0.8 from a bash script. When the script is run via terminal everything works fine. When we schedule the script via crontab we get an RC=255 and the task shows the...

May be quick and dirty looking on the PBS for failed backups like: grep ":backup:" /var/log/proxmox-backup/tasks |grep -v " OK"

Thank you

Hi, I did a typo createing one of my Datastores in our PBS. Is there (may be a manual/cli) a save way to change the datastore name ? Would be fine if someone can explain this.

Hi, in my case there was an issue with permissions of /etc. I found it by running a second sshd on one node /usr/sbin/sshd -p222 -d and ssh -vvv -p 222 node2 the server then complains about: debug1: trying public key file /root/.ssh/authorized_keys debug1: fd 4 clearing O_NONBLOCK...