60 GB .temp file

[azc]

We unfortunately ran into a situation where our backup repository that we use for Backup Copy jobs became full during the act of Veeam "creating a GFS restore point".

We've now cleared some space and the jobs have all run successfully since, but we're left with a 60 GB .temp file sitting in the destination folder for that BC job.

Is it safe to delete? Here's the contents of the folder.

Code: Select all

27/01/2015  20:09            18,049 BC-CCFS02.vbm
27/01/2015  15:46    61,737,533,952 BC-CCFS022014-12-14T000000.temp
27/01/2015  20:01 2,644,606,150,144 BC-CCFS022014-12-14T000000.vbk
13/01/2015  02:09    50,959,223,296 BC-CCFS022015-01-13T000000.vib

Any advice appreciated.

Thanks.

[Shestakov]

Hello Andrew,
.temp file is being created during a creation of GFS restore point. In your case something went wrong and the file had not become the restore point.
That`s an unexpected behavior, so ,please contact Veeam technical support to review logs for the issue investigation.
Thank you.

[Shestakov]

Andrew,
I`ve talked to our R&D team, and probably the file appeared after you had switched off GFS, cleared the space and started a new interval.
Next run of the backup copy job should delete the .temp file, create a new one and transform the new file to the next GFS restore point.
Have you started the issue investigation with the technical support? If no, please do. If yes, please provide us your support case number to follow the resolution.
Thanks.