Search results

  1. B

    Backup error and noVNC error after migrating VM to new Proxmox server

    This unlocks the VM for me: qm unlock 100 A test backup runs OK now, noVNC back to normal, too!
  2. B

    Backup error and noVNC error after migrating VM to new Proxmox server

    got error: broken pipe = backup storage not available Task viewer: Backup Output Status Stop INFO: starting new backup job: vzdump 100 --mode snapshot --node frc --remove 0 --storage drobo --compress lzo INFO: Starting Backup of VM 100 (qemu) INFO: status = running INFO: update VM 100: -lock...
  3. B

    [SOLVED] Email notifications still coming to old address

    Yep, running the command below after making changes in backup jobs turned out to be necessary: /etc/init.d/cron reload
  4. B

    [SOLVED] Email notifications still coming to old address

    Hi, I've changed the address I used for email notifications via Web GUI. I've also changed the backup time from 7am to 7pm., and all the changes are reflected in /etc/cron.d/vzdump However, Proxmox is still backing up at 7am and the emails are still coming to the old address. This happened on...
  5. B

    Proxmox backups of VM

    to see cron jobs that get created by Proxmox from web GUI just run in console: cat /etc/cron.d/vzdump

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!