[SOLVED] Snapshot Stop and Problems

A

aydoganatakan

New Member
Feb 12, 2023
15
1
3
While taking the snapshot, I pressed the STOP button for some reason.
The capture of snapshots was stopped and only "NOW" appeared in the snapshot list.

There did not appear to be a problem, but the virtual server I was trying to snapshot from seemed to be locked.

I did some research and based on the article written by someone from the forum, I deleted the 101.conf file under the "/etc/pve/nodes/pve/qemu-server" folder... Unfortunately, I did that.

After deleting my virtual server was deleted from PVE dashboard.
Then I filled the 101.conf file myself and brought it back.
I also saw unique parameters like UUID from console and typed the same. I don't think I made a mistake in the parameters.
However, I don't know if there were other texts such as snapshots after the 101.conf file. Maybe I wrote it wrong.

My first question is:
I'm getting an error when trying to get a FULL BACKUP to my virtual server. I am sending the screenshot of the error I received in the attachment.

My second question is:
Although my virtual server does not appear to be running on snapshot, it seems that there is a snapshot in the VMDisks partition. I am also attaching the image of them.
Maybe it's related to my first question.

I'm afraid to even restart my virtual server.
Please help me.
 

Attachments

  • 3.png
    3.png
    118.6 KB · Views: 27
  • 2.png
    2.png
    116.5 KB · Views: 26
  • 1.png
    1.png
    151.6 KB · Views: 26
Hi,
first of all, why not restore the config from an already performed, older backup?

aydoganatakan said:
I did some research and based on the article written by someone from the forum, I deleted the 101.conf file under the "/etc/pve/nodes/pve/qemu-server" folder... Unfortunately, I did that.
Click to expand...
Yes, this will remove the VM from the node, but it should not delete any disks. So your data is still all there.
aydoganatakan said:
My first question is:
I'm getting an error when trying to get a FULL BACKUP to my virtual server. I am sending the screenshot of the error I received in the attachment
Click to expand...
The backup fails because it tries to stop the VM first, which does not succeed within the timeout. Try taking a backup with snapshot mode.
aydoganatakan said:
My second question is:
Although my virtual server does not appear to be running on snapshot, it seems that there is a snapshot in the VMDisks partition. I am also attaching the image of them.
Maybe it's related to my first question.
Click to expand...
Yes the second disk is a leftover from the stopped snapshot. The snapshot config is normally stored as additional section in the VM config. You can however safely remove the disk, but first make sure to have a backup of the VM.

Also regarding the locked state of the VM. In order to unlock a locked VM you can use the qm unlock <VMID> command, no need for manually deleting configurations.
 
  • Like
Reactions: aydoganatakan
Chris said:
Hi,
first of all, why not restore the config from an already performed, older backup?


Yes, this will remove the VM from the node, but it should not delete any disks. So your data is still all there.

The backup fails because it tries to stop the VM first, which does not succeed within the timeout. Try taking a backup with snapshot mode.

Yes the second disk is a leftover from the stopped snapshot. The snapshot config is normally stored as additional section in the VM config. You can however safely remove the disk, but first make sure to have a backup of the VM.

Also regarding the locked state of the VM. In order to unlock a locked VM you can use the qm unlock <VMID> command, no need for manually deleting configurations.
Click to expand...


I did not have an up-to-date backup because an error occurred while trying to take a backup. I usually only backup the database inside the server. I do not take a backup of the VM.

Right now I can't get a real backup to my virtual server. When I press the backup button as in the picture below, 2 seconds later, the errors I sent in the first post (1.png) appear.

Seems to be getting an error rather than the timeout duration...

4.PNG


How can I delete an interrupted snapshot image?

I don't want to work as a snapshot because too many database operations are being done. Doesn't it cause performance loss?

When I chose "snapshot" instead of "STOP" from the Backup menu, it was backing up to the 60 GB "local (pve)" area. I had to cancel it.

How do I get a backup by "stop".

Where do I delete the snapshot disk? I couldn't see what folder it was in.
 
aydoganatakan said:
Right now I can't get a real backup to my virtual server. When I press the backup button as in the picture below, 2 seconds later, the errors I sent in the first post (1.png) appear.
Click to expand...
You get an error during the backup, because with mode stop PVE tries to stop the VM before performing the backup. In this case, the stopping of the VM failed (is this a Windows VM, do you have the guest agent installed? See https://pve.proxmox.com/wiki/Qemu-guest-agent).
This means you will have a downtime, while the backup is being performed. Mode snapshot avoids the downtime by taking a snapshot and utilizing the copy on write feature of the underlying storage to store data written to the disk after the snapshot. See here for more details https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_backup_modes

aydoganatakan said:
How can I delete an interrupted snapshot image?
Click to expand...
You should be able to select and delete it via the storage view > VM disks > Remove

aydoganatakan said:
I don't want to work as a snapshot because too many database operations are being done. Doesn't it cause performance loss?
Click to expand...
No, performance loss is not the issue. It might be more of a consistency issue, see once again the backup modes section in the docs.

aydoganatakan said:
When I chose "snapshot" instead of "STOP" from the Backup menu, it was backing up to the 60 GB "local (pve)" area. I had to cancel it.
Click to expand...
It backs up to local storage because that is what you have selected as target storage in the Backup window, select a different storage if you want a different location for your backups.
aydoganatakan said:
How do I get a backup by "stop".
Click to expand...
Install the qemu-guest-agent inside the VM. Alternatively, for a single manual backup you can also shutdown the VM and then start the backup for the stopped VM.
 
  • Like
Reactions: aydoganatakan
Yes indeed "qemu-guest-agent" might not exist on my virtual server.

5.PNG

However, before this "snapshot stop" event, I was able to backup in "STOP" mode many times.

Now I will search and install "qemu-guest-agent". I will try again.

If I have to restart my virtual server or physical server, I won't have a problem, right?

PS: All my virtual servers are Centos
 
Last edited:
The qemu-guest-agent appears to be enabled in the ProxMox interface.

However, it is seen as "inactive(dead)" on the server.
When I start it, it gives the following error:


Dependency failed for QEMU Guest Agent.
Click to expand...
Job qemu-guest-agent.service/start failed with result 'dependency'.
Click to expand...
 
aydoganatakan said:
The qemu-guest-agent appears to be enabled in the ProxMox interface.

However, it is seen as "inactive(dead)" on the server.
When I start it, it gives the following error:
Click to expand...
Check the journal in the VM for reasons why the guest agent might have failed: journalctl -u qemu-guest-agent
 
  • Like
Reactions: aydoganatakan
Chris said:
Check the journal in the VM for reasons why the guest agent might have failed: journalctl -u qemu-guest-agent
Click to expand...

It just shows the message I mentioned above.

6.PNG

By the way, thank you very much Chris. It's a good feeling that someone cares.
I hope we can fix it smoothly :(
 
  • Like
Reactions: aydoganatakan
aydoganatakan said:
Same.... inactive (dead).
I tried to enable it. However, the result is the same.

View attachment 46748
Click to expand...
I was just wondering if the status output also shows which dependency is not satisfied... A quick search in the forum spat out this thread [0], so you probably have to enable the qemu guest agent in the VM options and stop and start the VM for the agent to work.

[0] https://forum.proxmox.com/threads/dependency-failed-for-qemu-guest-agent.75797/#post-353277
 
  • Like
Reactions: aydoganatakan
But....

Reboot command output:
TASK ERROR: VM quit/powerdown failed

Shutdown command output:
TASK ERROR: VM quit/powerdown failed
 
I guess I needed to use the "VM STOP" command. I turned off the server. I rebooted.

qemu-guest-agent woke up. I think I'm backing up this time.

Thanks for your help @Chris ...
Glad to have you!
 
  • Like
Reactions: Chris
aydoganatakan said:
I guess I needed to use the "VM STOP" command. I turned off the server. I rebooted.

qemu-guest-agent woke up. I think I'm backing up this time.

Thanks for your help @Chris ...
Glad to have you!
Click to expand...
Glad if it worked out! Please mark the thread as solved.
 
  • Like
Reactions: hmohr
You must log in or register to reply here.
Top Bottom