Mounted VC container file, added small file, unmounted container file. Created a Reflect definition file to image the "VC Test" partition Created a new 3 GB VeraCrypt container file on the "VC Test" partition, using all default settings except changing the container file system to NTFS Shrank an existing partition on my hard drive and created a new 4 GB NTFS partition called "VC Test" in the freed up space Ok, I decided to install VeraCrypt to experiment with this since it piqued my curiosity, and although my setup isn't exactly the same as yours, I still encountered the same fundamental problem you did, so hopefully Macrium can respond to this quickly. The restored container has the few small files that were added in step 1 but is missing the 5GB video in step 4 even though the incremental size seems to suggest the changed blocks were backed up. the incremental image size is close to 5GB indicating it is backing up something.ĥ then restored the veracrypt container from the incremental image I know Reflect is backing up the changed blocks, or it appears so.ġ creating a new 10GB veracrypt container and adding a few small files to itĢ then created a full image backup of the partitionģ added a single ~5GB video to the veracrypt containerĤ created an incremental image. 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. I have a veracrypt container file on a partition that is set to create incremental backup sets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |