[cybmole]

I decided to do what some other folks here have suggested: exclude the opf fills when making multiple library backups. I thought that all I'd need to do was set a filter fro that file type in free file sync and then all the metadata.opf files in the backup folder would be zapped by the one way sync function..... but it did not so that.- it did not remove any of them!

after checking my syntax many times & re-reading all the given examples,
it seems I have to remove them from the target directory manually as a one-off and then trust that the filter will block any new ones from being backed up - is that correct ?

PS - for the bytes saved i'ts hardly worth the hassle but I've had a BAD GOOGLE day, feel free to ignore the following rant...

I had google throwing a hissy fit about open dns certs & not letting my into gmail/google plus for some arcane reason that's too complex to fix ( changed my dns instead as a cop out), & I had google drive refusing to sync (that is maybe connected to the certs issue maybe not) & than after uninstall, re-install of google drive telling me I'd used nearly all my 15Gb when i reckoned i'd only used half... so zapping OPFs was just a little something to help get the total space down. it seems to be admitting now that i've only actually used 8Gb which is progress,...

I get that google chrome now sees opendns's attempt to route pages via their blocking filters as some sort of man-in-the-middle-attack & so chrome gives a security warning & refuses access to goggle services. I don't know what genius at google chose this week to implement that & I'm hoping opendns will send me a for-dummies workaround... i don't know if that impacts on how google drive works either but the backup library , minus it's opf files seems to be in sync still..
its only my backup of last resort anyway, I would hope never to have to use it as I have a local one also.