> There is a small chance that there might be data corruption, a problem with delta copy systems. if you run nightly backups), then you may very well skip the dismounting/remounting step and just use the shadow copying instead. With regards to dismounting a TC volume before the backup - this is a reasonable advice, but if you have a volume that sits idle and gets no I/O during the backup time (e.g. The workaround for this is to use "$touch c:\path\to\your.tc" as a pre-backup command, which will force the timestamp change on your.tc. TC volumes may still get their timestamp not changed even after unchecking the "Preserve modification timestamp of file containers" option in TrueCrypt preferences. Should a user in fact decide to dismiss a VERY LOUD WARNING without reading all your existing files will still be there, merely moved into an archive directory. The issue of people ignoring the warning when backing up to an existing directory is now handled by an archiving function. It has a fully async I/O module that uses adaptive buffering, so if you find a faster bulk copying software, I'd like to have its name. V2 is faster than recent versions of robocopy, which are pretty damn fast and significantly faster than FastCopy. If you are still using the original version, you should seriously consider switching. It took about 18 months of full-time effort and the result is Bvckup 2. So a couple of years ago I sat down and started redoing the whole thing from scratch. I then put it online just to gauge the interest and surprisingly it took off. To explain, the original version is now 5 years old and it is something that I wrote in a course of 3-4 weeks for my own use. If anyone knows a way around this, please let me know I know there's a "Contents" bit that you can add/modify, but when I tried to backup a single file on my drive's root directory, I got a uniquely weird error: There doesn't appear to be a way to backup a single file, only a full directory. The dev addresses this and has tried to correct for it using a system not unlike BitTorrent hashing (I got a 9.6 meg hash file from a 15 gig file analysis it's one of the reasons why you can't change the home directory after it's first set.) However, even the dev acknowledges that it's not fool proof and by default will do a full copy every 8 backups. There is a small chance that there might be data corruption, a problem with delta copy systems. If you're going to the trouble to encrypt and then backup your stuff, it's probably worth it to be careful. I would also dismount the volume even though Bvckup's shadow volume copying feature will function. Bvckup doesn't check files with the same timestamp and I couldn't find a way to force Bvckup to run a check. Alternatively there's a "Do not delete any files" checkbox under "More options".ĭisable "Preserve modification timestamp of file containers", which TrueCrypt has on by default for security reasons. Regardless, when you're dealing with backups it makes sense to be extra careful. I guess the message here is either don't run backups late at night or don't be a moron. This, despite a warning message about that but I still didn't register. I ran one on a directory that wasn't empty and the program zapped everything there. I recommend initially setting the "Destination" to an empty directory. I'd recommend FastCopy with verification enabled. If you're just moving something important from one place to another and don't plan to update it later, Bvckup is a waste of time and energy. This is not the fastest copy method until AFTER the first copy.If you're only using Flash media for critical backups, I'd disable the "Copy file in full after X partial backups" and just use a hash comparison program like MultiHasher or FileVerifier++. This program is THE solution for a problem I brought up a long time ago: Why an easy to use, portable RSYNC for Windows is important. Could dramatically increase the life of Flash media.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |