[SOLVED] Problem with auto sleep and wake Backup Server.

E

emmker

New Member
Jan 31, 2023
6
0
1
I have a proxmox VE server hosting some VMs and some lXCs.
The server backs up the machines on a Proxmox Backup server, which is connected to the VE as BackupServer_3TB.

The Backup server, is programmed to go to sleep from 4 am to 1am next day, which is the time that the VE starts the backup process.
The problem is that all the time that the Backup server is sleeping, the VE has many log entries like that:
May 14 19:44:37 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:44:47 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:44:57 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:45:07 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)

is there a way to avoid these log entries without turning on the backup server?
 
emmker said:
I have a proxmox VE server hosting some VMs and some lXCs.
The server backs up the machines on a Proxmox Backup server, which is connected to the VE as BackupServer_3TB.

The Backup server, is programmed to go to sleep from 4 am to 1am next day, which is the time that the VE starts the backup process.
The problem is that all the time that the Backup server is sleeping, the VE has many log entries like that:
May 14 19:44:37 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:44:47 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:44:57 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)
May 14 19:45:07 Latra pvestatd[1439]: BackupServer_3TB: error fetching datastores - 500 Can't connect to x.x.x.x:8007 (No route to host)

is there a way to avoid these log entries without turning on the backup server?
Click to expand...
Hi,
in order for Proxmox VE to not check availability of a storage, you will have to set it as disabled, you can either do this via cli [0] or the api [1] in a script.

[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_command_line_interface
[1] https://pve.proxmox.com/pve-docs/api-viewer/index.html#/storage/{storage}
 
  • Like
Reactions: emmker
That was exactly what I was looking for, and much more.
I just implemented it with cron and it is now fine

Thank you very much
 
You must log in or register to reply here.
Top Bottom