You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you say crashing, is it the guest OS who crashed (kernel panic), or the services that doesn't respond anymore ?
Can you reproduce the problem by creating a snapshot manually on the aplliance and deleting it afterward ?
Our backup window runs at 8PM. I logged into check the logs and performance at 10PM and saw it was not responding so I consoled to the appliance and seen that node-app was not running. I attempted to restart the services but had to go to console and force restart node app.
Snapshot was taken at 9:08PM, and then deleted at 9:37PM - It was a full backup as we just deployed the appliance yesterday, which would have taken a little longer to complete than a normal incremental.
No Events were recorded starting at 8PM till I restarted the appliance at 10PM.
I took a snapshot of the machine and then removed the snapshot couldn't reproduce the result.
I was just wondering if we should exclude the appliance from the backup window. I was really interested in seeing the stats from our backup in sexilog.
If you want to exclude the appliance from your backup jobs, you should add it to your exclusion list on your backup software.
If you didn't have access to the backup tool, there are some tricks to disallow snapshot for a VM (limiting the number of snapshot for the VM to 0, setting the disk to independent mode, ...) , but it'll be less nice than handling it straight from backup tool.
Having an issue with the appliance crashing during our scheduled backup cycle of our virtual machines.
The text was updated successfully, but these errors were encountered: