I've been using Reflect for several years now and have restored the entire operating system a few times with it.īefore testing this I did disable “Preserve modification timestamp of file containers” in veracrypt even though I didn't think it mattered for image backups. This issue also got discussed in more detail starting a few posts into this thread if you’re interested: If you’re running a Pro version of Windows 8 or newer (or Win7 Enterprise/Ultimate), switch to VHD/VHDX container files and enable BitLocker on them. Especially if you’re already backing up most of the contents of the partition anyway, image backups are faster and Inc/Diff backups will be smaller, and since they run at the block level rather than file level, they don’t rely on size and Date Modified information to detect changes, and VeraCrypt can’t “hide” its activity from image backup change detection mechanisms. Use image backups rather than File & Folder backups. The risk here is that if you ever reinstall VeraCrypt and forget to make this change, you’re back where you started. I can’t remember what that option is actually called, but it’s there. Disable the “Do not update Date Modified timestamp” feature in VeraCrypt. In terms of fixes, you have a few options: The only other way to check for changes would be to hash the file, but hashing every file in a backup is not practical for time reasons, which is why backup applications don’t do that. Same goes for file sync applications like Google Drive/Dropbox sync. This prevents Reflect (in File & Folder mode) and pretty much all file-based backup applications from detecting that the file is changed, since they rely on changes in size and/or the Date Modified timestamp to detect changes. It sounds like you’re running File & Folder backups rather than image backups even though you posted in the Disk Imaging section? If so, this occurs because VeraCrypt for privacy reasons deliberately never modifies a container’s file size or Date Modified timestamp when changes are made inside it. Keeping it here in case it helps someone else who might stumble on it later while using F&F backups.) (UPDATE: OP is in fact running image backups, not F&F, so this post is not relevant to this particular case. All other data on the partition not inside the encrypted container is backed up fine. The only time I'm getting proper backups of the encrypted container is during the full backups leaving the potential of loosing 6 days of work. So currently I'm using backup sets with a full backup every friday and incrementals the other 6 days. I also tested with differential backup as well and the same problem exists. However if I explore the incremental backup and mount the encrypted container the 5GB file is missing in the backup. The incremental size is close to 5GB which seems to indicate it is backing up the changes made to the container. I then mount the encrypted container, add a new ~5GB file, un-mount the container, then perform an incremental backup. With a full backup the encrypted container has all its current contents. The error.I have a veracrypt container file on a partition that is set to create incremental backup sets. Why would a partition be treated differently? What am I missing here? If I encrypt an external USB device, I'm able to mount this in either OS just fine. But trying to mount it from Windows chucks out the same error. But when I try to mount this volume from within VeraCrypt in Linux by selecting the partition, I get the below error.Īnd the same problem goes from the Linux side: I can create the encrypted volume using the partition (I even select the "will be used by other system" option) and mount and use it just fine from within Linux. The problem is, if I encrypt the partition in Windows I'm able to mount it within Windows and create files just fine. But I also want a VeraCrypt encrypted partition/volume that I can load from either side to dump common files in to. Therefore both my OSs are encrypted and launch just fine. I have a dual-boot encrypted setup (Grub has two options: One for Window which loads the VeraCrypt boot loader and one for Linux Mint which loads the LUKS magic. Yet they both mount on the OS they were created on just fine. If I encrypt a partition in Windows I'm unable to mount it in Linux, and vice versa.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |