Virtualizor saves backups for each VPS in two files:
- .inf which contains JSON information about the VPS
- .img file which contains the actual OS image
Because the Virtualizor interface allows you to see backup logs only for the last 50 backups, I recommend using the terminal instead. To check if a backup exists simply navigate to the backup directory and see if there are both .inf and .img files for each hostname.
![How to Troubleshoot Virtualizor backups mspaint 17tuZWAu5s - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/mspaint_17tuZWAu5s.png?resize=736%2C171&ssl=1)
So if the backup file is present, that means the backup was successful, but what if there is no backup file?
Then you should check the Virtualizor backup logs for that VPS.Virtualizor backup logs are stored in /var/virtualizor/log/backup/ and named ID.log
![How to Troubleshoot Virtualizor backups vps virtualizor backup log - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/vps-virtualizor-backup-log.png?resize=398%2C272&ssl=1)
So, to check the status of a backup for VPS with the ID 476, we open the 476.log file
![How to Troubleshoot Virtualizor backups vps log error - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/vps-log-error.png?resize=454%2C339&ssl=1)
This error indicates that there was a problem generating the backup on the VPS itself, so the next things you should check are:
- network problems between the VPS and backup server that could have caused this issue
- status of the VPS – if it is turned off or has network suspended
Another important thing to note is the time when the file was last edited, because Virtualizor doesn’t record time in these log files.
![How to Troubleshoot Virtualizor backups vps log - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/vps-log.png?resize=381%2C36&ssl=1)
Here are a few cases that I’ve encountered so far:
.log file says backup was successful but the files are missing
- Check if the VPS has a backup plan assigned:
![How to Troubleshoot Virtualizor backups chrome uXQ4a6JK4y - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/chrome_uXQ4a6JK4y.png?resize=736%2C399&ssl=1)
2. Make sure you are checking on the right backup destination:
![How to Troubleshoot Virtualizor backups mspaint uE9o0I7SsN - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/mspaint_uE9o0I7SsN.png?resize=736%2C197&ssl=1)
no logs and the backup files are missing
Logs for each VPS Backup plan are stored under /var/virtualizor/log/vpsbackups_plan
![How to Troubleshoot Virtualizor backups MobaXterm Personal 20.3 9cmlSZvYoF - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/MobaXterm_Personal_20.3_9cmlSZvYoF.png?resize=404%2C48&ssl=1)
use less to go over the backup file and check if backups were successful:
![How to Troubleshoot Virtualizor backups MobaXterm Personal 20.3 RnW51UvlAX - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/MobaXterm_Personal_20.3_RnW51UvlAX.png?resize=358%2C409&ssl=1)
Starting backup means that it started, and Sleeping that it’s working.. if the backup failed for some reason, the end of the file will contain the error:
![How to Troubleshoot Virtualizor backups MobaXterm Personal 20.3 Cy4AXjwDVA - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/MobaXterm_Personal_20.3_Cy4AXjwDVA.png?resize=736%2C109&ssl=1)
VPS was not added to the backup plan
In the above log file, We checked if the VPS backup plan run and we can grep VPS ID in it. In this example the VPS was not added to the backup plan:
![How to Troubleshoot Virtualizor backups MobaXterm Personal 20.3 HBS1EsgRuu - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/MobaXterm_Personal_20.3_HBS1EsgRuu.png?resize=270%2C463&ssl=1)
To fix this, add the VPS to the backup plan.
![How to Troubleshoot Virtualizor backups chrome lrkADfYPru - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/06/chrome_lrkADfYPru.png?resize=736%2C380&ssl=1)
ERROR: Unable to create the backup folders on selected backup server(There was an error while creating the backup start directory)
![How to Troubleshoot Virtualizor backups image - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/10/image.png?resize=736%2C504&ssl=1)
Virtualizor was unable to create the backup directory on the remote server. Check if the user used for transfer has privileges to create new folders on the specified location.
ERROR: Unable to create the temporary backup locations(create_temp_storage() : There is not enough space to create temporary storage.)
![How to Troubleshoot Virtualizor backups image 1 1024x315 - How to Troubleshoot Virtualizor backups](https://i0.wp.com/pcx3.com/wp-content/uploads/2022/10/image-1.png?resize=736%2C226&ssl=1)
Disk usage was filled on the local node, check logs and monitoring at the time the error was encountered. If the issue persists, contact Virtualizor support.