![]() ![]() ![]() Once the temp file is done, move it on top of the previous version. However a simpler option would be to mimic what rsync does and simply make the process on the backup side create a temporary copy of a file upon detecting a change and then build this file from unchanged local blocks and new remote blocks. Re: aborted transfers - what happens in this case is that bvckup2 remembers which part of destination file it processed last and on the next run it will pick from that point (assuming that timestamps on destination file didn't change between the runs).įantastic! I very much look forward to all of that! :) ![]() Would it be possible to write the changed blocks to a temp file(s) on the destination first. This will allow for several very interesting things, including rsync-style two-process copying and file comparison (without a need to store block hashes between the runs), potentially faster custom network protocol for bulk transfer and few other things. I am wondering if you would be willing to consider providing the option for installing a 2nd copy (snip) at the remote location. Thanks again for providing such excellent software - it's a real pleasure coming across folks like yourself doing such quality work, and clearly taking pride in your work. But I am wondering about any possible enhancements for handling "abortive cancellation" scenarios? In particular, if (1) above were implemented, would it be possible to write the changed blocks to a temp file(s) on the destination first, and then let the remote Bvckup utility take care of integrating the blocks into the destination file (and there would be the added benefit that the remote utility could do an integrity check of the whole assembled file at the end to be sure everything matches whatever hash data was sent)? Basically, I'm trying to avoid any possible corruption of an interrupted transfer as well as the possibility of a full re-copy being required after an interrupted transfer (which would be problematic for a 30GB file over WAN via my VPN). I have toyed with trying to achieve remote integrity checking totally separate from backup software by using something like Checksum ( ), but I'd much rather have this built into/with something like Bvckup.Ģ) Delta Copying: I think this feature is great from what I've read ( ). Syncovery (which I've used in the past) is one example of this sort of thing (though it does not currently support the above kind of file integrity checking I'm wanting): However, I am wondering if you would be willing to consider providing the option for installing a 2nd copy (or just a utility version of the software) at the remote location for the purposes of performing expensive network tasks (when going over WAN via VPN, as I am doing) such as re-readingĭestination files for purposes of integrity checking (or any other reason that the destination files might need to be re-read). I also gather (and appreciate) the ways in which Bvckup works quite well without having a 2nd piece of software at the destination. I am aware (and very grateful!) that I can seed my initial backups, so that is not a concern.ġ) Integrity Checking: I've seen the following posts indicating that the ability to schedule periodic integrity verifications of the backed up files is a forthcoming feature. I will be backing up a mix of files, but ~10TB (and growing) are large video files of varying sizes (ranging from 300MB to 40GB), which will rarely (and in most cases never) change. I can access the remote shares locally (because of how my VPN is configured) via UNC paths (and the same UNC paths can also access those remote shares via a Windows computer at the remote location). I have a few questions/requests, but first some context/background: I will be primarily using Bvckup on a computer to backup data residing on my local Synology NAS to several NAS' remotely located (which will be accessed via my router-to-router VPN arrangement). I'm a potential new user, and am really liking everything I'm seeing/reading about Bvckup! :) I so appreciate your focus on quality of quantity, and that your software doesn't lock the user into any proprietary storage formats. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |