Backup only when guest was/is running

T

teclab-at

Member
Dec 11, 2022
11
0
6
If the guest system was not running since the last backup, a new backup makes little sense.

Current:
Old backups will get deleted and new backups accumulate with no change in between them.

Better:
Add switch to make backups only when guest system was/is running.

Regards
 
teclab-at said:
If the guest system was not running since the last backup, a new backup makes little sense.

Current:
Old backups will get deleted and new backups accumulate with no change in between them.

Better:
Add switch to make backups only when guest system was/is running.

Regards
Click to expand...

(Does Proxmox reliably knows when a system was running the last time? To me, this sounds a bit riksy.)
 
Risky? I doubt.
  • When you look at the web-interface you see the current status of each system.
  • You cannot start a guest when it is already running.
  • The log shows when a guest was started and when it was stopped.
Looks to me as Proxmox has all the information it needs.
 
teclab-at said:
Risky? I doubt.
  • When you look at the web-interface you see the current status of each system.
  • You cannot start a guest when it is already running.
  • The log shows when a guest was started and when it was stopped.
Looks to me as Proxmox has all the information it needs.
Click to expand...
OK, I just wanted to add my unqualified thoughts, maybe this indeed is completely wrong. But maybe there are rare cases (possibly hard to find) where things break, this was all I wanted to say.

(Sometimes information at web-interfaces are not correct, for example, I don't know if Proxmox cannot get the guest information, it might leave the last status untouched, so it could look as it wouldn't have been run, but actually is running (but maybe with bad qmeu guest tool or whatever).
If such a problem remains unnoticed in production for a couple of days, in case of an event someone may only find a backup a couple of days old.

I understand that in normal case, if nothing goes wrong, this would work well, but backups in particular are also needed in case when things do go wrong, and then just to save a bit of disk load led to missing backups, this could be bad and surely unexpected. )
 
  • Like
Reactions: Johannes S
sdettmer said:
OK, I just wanted to add my unqualified thoughts, maybe this indeed is completely wrong. But maybe there are rare cases (possibly hard to find) where things break, this was all I wanted to say.

(Sometimes information at web-interfaces are not correct, for example, I don't know if Proxmox cannot get the guest information, it might leave the last status untouched, so it could look as it wouldn't have been run, but actually is running (but maybe with bad qmeu guest tool or whatever).
If such a problem remains unnoticed in production for a couple of days, in case of an event someone may only find a backup a couple of days old.

I understand that in normal case, if nothing goes wrong, this would work well, but backups in particular are also needed in case when things do go wrong, and then just to save a bit of disk load led to missing backups, this could be bad and surely unexpected. )
Click to expand...
Well I understand the concern. That's why I find it best to have a switch to enable this function.
 
You must log in or register to reply here.
Top Bottom