Failure to Sync - unsupported extension
Using build 6514. Problem is a repeated one. Several files in the synced folder have a ".OTD" extension, and Acronis refuses to sync them since the extension is "unsupported". This is a sync between local machines on Win7x64 Pro. The extension IS supported by the program that uses the file.
How can I tell Acronis to sync files with the ".OTD" extension?
Log ZIP attached, including PNG of the actual screen listing.
Thanks for your help!
What type of program own these OTD files (Open Office?)? Is it possible the application is open and has locked these files when you try to sync?
I came upon this thread - starting to use the sync features today. I have the same problem with sync skipping some of my source code. It's pretty blatant, when I compare the 2 directory trees, I'm missing all my text files that have an sql extension. Example: myfile.sql would be just a normal notepad-like text file. (after reading some more, I tried changing the extension in explorer from "opens with SSMS - SQL Server Management Studio" to "opens with notepad", and created some new files with the sql extension, but still no-go.) If I create a *.txt file it copies right over. Is there a configurable list of exceptions or is it built in? Thanks, Mike
Interesting, what happens if you suspend SQL Server?
Thank you for your response and my apologies for the delay in responding. The OTD extension is used by Nirvana's OmniTrader program ... a highend specialty tool used for stock trading analysis, simulation, and automation. There are a lot of specialized extensions besides that one (OTP, OTS, etc).
My original question still stands ... the error message said that the extension is "unsupported". I asked **how to tell Acronis that it IS in fact a valid extension**. The natural parallel "theoretical" question is, why does Acronis CARE about what the extension is at ALL, for syncing purposes? Syncing is supposed to be "blind" ... just make one folder look like another folder.
All my machines are on the same build of Win7 Pro.
Hello HVACsage,
thank you for your question and welcome to Acronis Forum!
Colin, thank you for helping!
Synchronization has several limitations, for example you cannot synchronize databases or system files. Here you can read more about it.
There are some internal filters in the program that do not allow to synchronize unsupported files. So please check, if your files don't fall into unsupported category.
Let me know if you have any additional questions.
Thank you.
Hi everybody,
Same problem here.
Files with the extension .sql are NOT synchronized. These are simple text files, not system files, not hidden, not database, not locked by any process, etc. etc. Just simple text files you edit with notepad.
Why would a sync tool restrict which files are synced on account of their extension?
The sync feature is simply unusable for serious work at this point :-)
That's unfortunate for a program, which otherwise is very good, simple to use, set up and forget, etc.
Please improve the sync.
Ciao
Francesco
Francesco,
Is this with SQL Server running and have the files been opened before or during Sync?
The .sql files are text files. It has absolutely zero to do with SQL Server running or not. It has nothing to do with the files being opened or not. This has to do with an undisclosed whitelist/blacklist being used by Acronis Sync. The feature is broken and adding some transparency to the whitelist/blacklist is the only way ANYONE should actually be using this feature lest they lose files they think were actually being synced but were not.
I only found this mismatching because I checked the file counts in the synced folders, and when I saw that they did not match, I saw in the log that the .sql files were skipped. Since the source folder contained 84k files and 10k were skipped at the target, there were likely lots of other skipped extensions as I was obviously not going to check every record in the log.