SureBackup folder on my datastore

[Fiskepudding]

I was browsing my datastore just now, and a found a folder called SureBackup.
None of my other veeam server datastores has this.
The folder is filled with lots of ID's.
No backups are currently running.



What created this folder and subfolders?
Can it be stopped?
Can I delete all the folders?

Thanx

[foggy]

Espen, obviously these folders are created by SureBackup jobs and used to cache some data. We can observe the same situation in one of our labs and are trying to reveal the reasons why the folder is not deleted after job completion. I will keep this thread updated on the results.

You can safely remove these folders from your datastore.

[Fiskepudding]

Thanx for the reply Alexander.

Off to delete som folders

[foggy]

These temporary folders are used to reconfigure VM vmx files during SureBackup job. They are not deleted due to some reason (this will be addressed in one of the future releases) but this does not affect SureBackup operation in any way.

[j.vanledden]

even though we use the latest version of Veeam 6 (6.1.0.205), we have this problem too. is there anything known about a solutions
(we've thousands of this folders)

[foggy]

Will be addressed in v6.5 most likely.

[Frosty]

I have a similar \SureBackup folder and a handful of GUID-named folders underneath. I'm running VBR 6.5 already. I don't have any currently scheduled SureBackup jobs, so I expect that these were left over from some previous testing. I intend to remove the GUID-named folders. But I have a question about the top-level \SureBackup folder.

Just curious whether \SureBackup can be removed as well? Or would that 'break' my virtual lab configuration? The reason I want to delete it is that I'm moving all VMs of that datastore, reformatting it with VMFS5 (v5.58) and then moving my VMs back on to it. Can I just delete that top-level folder? Or should I manually re-created it after creating the datastore? Or might I have to do something with my virtual lab configuration?

[Frosty]

I've been able to answer my own question. After several hours of mucking about, I've discovered that the easiest solution was to simply delete my virtual lab, re-make my datastore, then create the virtual lab again. I did experiment with doing a storage migration of the virtual lab, however even after manually editing settings (for CDROM and Floppy devices) I still had some issues with it. I ended up manually deleting the folder with all the GUID-like sub-folders. After recreating the virtual lab and running a test, I was able to confirm that each test created a GUID-like sub-folder and then deleted it automatically on completion of the test.

[Vitaliy S.]

Re-creating a virtual lab shouldn't take much time, so what you've done is indeed the easiest solution in this scenario.