Redstor - Backup Error "Cloud Files Are Not Supported"

[Swaleway_Techie]

Hello!

 

So I have a batch if files on a file storage server that are failing to backup every night with our Redstor cloud backup solution with the error "Cloud files are not supported". Firstly they are not cloud files, and are a collection of .doc .csv .notebook .zip and anything else really I haven't noticed one file type over another.

 

Redstor support have said if the Attribute under file properties -> details has an "M" or "O" listed then Redstor will see it as a cloud file and not back it up. They suggested I copied the files to a new folder and it should back up, which it did, but then the next night more files were marked with the same error.

 

So I need to find out why certain files are gaining the "M" attribute (not seen any "O") and from where to try and stop files from gaining this and then not being included in backups. "I have found out that "M" means:

 

(M) Recall on Data Access. When this attribute is set, it means that the file or directory is not fully present locally. For a file that means that not all of its data is on local storage (e.g. it may be sparse with some data still in remote storage). For a directory it means that some of the directory contents are being virtualized from another location. Reading the file / enumerating the directory will be more expensive than normal, e.g. it will cause at least some of the file/directory content to be fetched from a remote store. Only kernel-mode callers can set this bit.

 

but I have no idea why some files are gaining this "M" and other are not. Has any one seen anything like this before or know why some of our files are getting the "M" attribute applied?

 

Thanks

Richard

[Steve21]

Are you using Azure files? The built in tiering will automatically set files that aren’t recently used to cloud only (effectively the server version of OneDrive)

 

Steve

[Swaleway_Techie]

Hi Steve,

 

I thought the same after some quick research but looking on Azure, file sync isn't configured for any servers on our network, and I can't see any evidence of it being installed on the server so it can't be that. I did wonder if it was something to do with a One Drive sync, but again we don't have this set up.

 

Thanks for the suggestion though