- Posts: 3
- Liked: never
- Joined: Jul 16, 2009 6:38 pm
- Full Name: Kurt Weeks
We are having problems with Veeam not clearing the temp directory after itself. I always see this problem with failed jobs, not completed jobs. The reason the job failed has no impact on why this information is left behind.
Our current process is to back up all VM’s from 5:00 PM to 11:00 PM with Veeam. Then at 1:00 am we back up the Veeam backups to tape with Symantec Backup.
The only way to fix this is to manually clean up the left over temp stuff. Then I have to delete any backups that Veeam has taken and start a fresh Veeam job.
Thank you all the help.
- SVP, Product Management
- Posts: 28255
- Liked: 5022 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
I can guess (need to confirm with devs) that aborted job may not cleanup after itself, this is the same case as if you would interrupt product's setup for instance, or any process that puts anything into the TEMP folder.
What you can do is use post-job script from Advanced job settings to cleanup TEMP after each job run, however again, the stuff we put there is virtual and does not take any disk space, so I personally would not worry about this at all. It is not common for jobs to be aborted, so cleaning the TEMP folder once in a year manually (if you are really worried about it) should be fine. I personally never do this on my Veeam Backup server which backs up my lab