![]() ![]() It is technically possible to do backups to SMB, and not to have special software on the remote end, but copying only changed portions of the file in such a setup isn't possible, because the backup client has to read the entire file from over CIFS to determine what portions have changed, and at that point you've copied the entire file in at least one direction.īorgbackup, on the other hand, can meet all of your criteria except backing up files raw. Rsync based backup systems like rsnapshot will do most of what you're doing, but there are a few of your requirements that are. But Linux is used heavily on servers so I would expect a simple app with these features to be available. At this point I can compromise this.Īctually when looking for Backup software for Windows, I was unable to find such app except Bvckup2. Copying over only changed parts of files (what Bvckup2 calls "Delta copy", useful for VM VHDs). Not having to install server software, I want files to be transferred via SMB (most enterprise backup software for Linux require that, this is overkill for such a simple backup setup) Deleting files immediately defeats the purpose of a backup but not deleting them makes a mess on the backup and also takes up unnecessary space. Syncing deletions but keeping deleted files for x days in an "Archive" folder (on remote). Also I can browse my PC files from another device while the PC is off. This makes the recovery really easy and fast. Backing up files raw (aka just copying files, no compression or encryption). The features I'm looking for that Bvckup2 has: When I had Windows, I used to use Bvckup2 but I'm yet to find an app like this for Linux. I have a "NAS" on my network (aka a Raspberry PI with an HDD running an SMB server) and I have setup my devices (Phone, PC, other PIs) to automatically backup in there. So to answer your question - your license will be exactly the same as it is now, because it's going to be the same program, evolved.My backup setup is really simple. In the context of all this, you can now probably guess that Bvckup 2 will keep on developing until it gradually transforms into what-would've-been shipped as Bvckup 3 under an older model. Then, later on if you spot a new feature you need, you will be able to pay a small maintenance fee and get another year of updates from that. After all it will still have all the features that you bought it for initially. ![]() If after a year you find yourself not needing any new features that are being added, you can stop there and just keep on using the version you have. So the idea here is that when you buy a license, you get the current release, a lifetime of maintenance (bugfix) updates and a year worth of new releases. ![]() It allows more people to actually notice, explore and make use of all the features that are being added. I like this model better, because a stream of smaller incremental changes is easier to follow and digest. Basically wrap every new feature into a release of its own and ship it out as soon as it's ready. If you look at the list of Bvckup 2 releases from the past several years, then under this model we would've been up to Bvckup 6 or 7 already.Īn alternative model is to make releases smaller, but ship them more frequently. Then entice existing users to upgrade and through this generate additional revenue to cover development costs. Product versioning option is something that I've been spending some time on recently and I am now leaning towards to keeping all further development under the Bvckup 2 name.Ĭonventional and widely-used model is to batch new features as they are developed and ship them out on annual basis as a new product "edition" (Something 2019). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |