The idea is interesting but it seems difficult. The two main issues I see are:
- Unless to lock the volume itself, read/write requests can continue to come. And locking the volume supposes that there is no open "handle" to it (no open file, no Explorer window, etc.).
- How to pass the instruction to ProxyCrypt?
If we ignore the requests, data can be lost. And if we don't reply, this can freeze the whole system.
That said, if all your files are flushed onto the encrypted volume, as ProxyCrypt writes the data without delay, you should be able to copy it safely if you write nothing in the meantime.
To do that, you can try one of the Sysinternals tools, "sync" (requires administrative privileges): https://technet.microsoft.com/en-us/sysinternals/bb897438
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you can temporarily lock the container file to copy it while it is open?
The idea is interesting but it seems difficult. The two main issues I see are:
- Unless to lock the volume itself, read/write requests can continue to come. And locking the volume supposes that there is no open "handle" to it (no open file, no Explorer window, etc.).
- How to pass the instruction to ProxyCrypt?
If we ignore the requests, data can be lost. And if we don't reply, this can freeze the whole system.
That said, if all your files are flushed onto the encrypted volume, as ProxyCrypt writes the data without delay, you should be able to copy it safely if you write nothing in the meantime.
To do that, you can try one of the Sysinternals tools, "sync" (requires administrative privileges):
https://technet.microsoft.com/en-us/sysinternals/bb897438