Encrypt locally and do checksum integrity examinations, which are perfectly determinable. This means you just cannot allow anything to pass through in plain text or your plan is dead in the water. The internet is full of gateways and actors in elevated positions on the connection trace. IMPORTANT note: files leaving a computer and headed to a cloud don't travel in a pretty little straight line like you might imagine in your mind. (Before this address, Johnny lived at 22240 Pacific Coast Highway, in Malibu. This allows me to monitor the returned file and before I would use it, I would examine the checksum for certainty of being unchanged. JOHNNY CARSON: - 6962 Wildlife Road, (Point Dume) Malibu.
Do a sha checksum on it and then record that sum.
In my case I would save the backup (completely) locally and send it up as an encrypted file/folder. Restores if needed simply reverse the process. Then you can setup incremental backups using Macrium so that you won't have to backup the entire system every time. The data going up to the cloud is already encrypted by Macrium and can only be decrypted or of use to Macrium leaving the cloud provider in the dark (as you want it to be). you can use Macrium Reflect on Win 10 and that software allows you to write out data to a location on the cloud. However all aspects of that are handled locally because the cloud is unable to do anything to encrypted data. Placing secure data on a cloud and then returning that data safely and securely is actually easy. Syncing as you refer to it creates data logistical nightmares when you don't control both ends of the handshake. The approach is different depending upon that answer. How large a system are you talking about in Gigs? Also, what level of safety are you wanting? By that I mean just privacy from prying eyes OR wanting to combat a 3 letter agency.
0 kommentar(er)
