The sdapi proxy is neither forward nor backward compatible.
I have run tests on version 3.2.1 using both the old "sdapi" I/O manager and the new "proxy" I/O manager, using VDSCopy. I have built OpenVDS from sources. Observations:
-
A file on the cloud written using the "sdapi" manager cannot be read with the "proxy" manager.
-
A file on the cloud written using the "proxy" manager cannot be read with the "sdapi" manager.
-
Additionally, the file written using the "proxy" manager is seen as corrupt by other dms applications. The list of block names is empty. Somehow the meta-data isn't stored correctly.