it's just a normal Windows drive/folder!
Why would you block TrueCrypt on purpose while at the same time advertising BitLocker?
second trust-problem where you assumingly on purpose disallow TrueCrypt use
require private system data to be sent in a blackbox to you to file an issue report
one of the most important things for a company that deals with user data is trust.
Dima P. wrote:I am still quite surprised that you do trust to the software which support was dropped by it’s own vendor two years ago.
Dima P. wrote:We never blocked USB devices of any kind.
Dima P. wrote:I bet the flash drive you used to store a TrueCrypt container is visible in the VEB job’s destination step.
Dima P. wrote:I’ve asked you for the logs and the support case in my first post to start the investigation. […]If you are uncomfortable with sending the very same folder to support team via VEB’s UI, share it with me via any available could hosting (dropbox/google drive or any other works) - I am here to help.
Dima P. wrote:This thread contains several reports from other community members are successfully using TrueCrypt files as a source or as a destination.
use a shared folder destination and point the backup job to the container of any kind via administrative share. Another option for the local storage destination step is to use symlink
So for backup the PC must be turned on (bott password entered) and the data is encrypted at runtime, that Windows can be loaded. I am wondering about the backup now.
If anyone steals the backup files, would the one be able to restore and run that backup on any other PC?
But what's about extracting files from the Veeam backup files? Is that possible?
I think because the backed up data was not encrypted at the time of backup (system booted into Windows), maybe the whole backup is not encrypted by VeraCrypt and files can be extraced easily. What do you think?
Users browsing this forum: No registered users and 1 guest