That’s definitely up to the user to define. I definitely don’t suggest the init command pre-populate these settings based on recommended values. Would Duplicacy benefit from having a different thread count for source and destination? If not, why does copy already have both -download-limit-rate and -upload-limit-rate options?īTW I’m not overly attached to this idea… I just threw it out there as a suitable enough improvement - a compromise to having hard-coded defaults for storage backends. SpiderOak do not offer unlimited storage (instead opting for several fix quota plans) but do allow an unlimited number of devices to share the overall cloud storage quota. The lesser of the two applicable values? What if one isn’t set? Could it make a more intelligent choice? Might seem straightforward, yet not necessarily so. NB Whilst both Backblaze and SpiderOak One backup support backing-up external hard drives. We have source and destination threads, upstream and downstream values for each. Just 139.99 Printer Friendly View Address: 500 Ben Franklin Ct San Mateo, CA, 94401-4045 United States Phone: Website: Employees (all. All your data is automatically and securely backed up online for just 7 per month or 70 per year. Since the set command exists already for similar purposes, feature creep is minimal, and my proposal was strictly for thread counts and bandwidth limits.īut one problem with the idea I can think of already is deciding which thread amount and bw limit to use for the copy command. In 2008, the company released online backup services to support PCs running Apples macOS and Microsoft Windows. ![]() is an American cloud storage and data backup company based in San Mateo. And if you continually switch connections, you might simply choose not to ‘set’ anything at all. 270 (December 2021) Website: Footnotes / references: Backblaze, Inc. With you on the Unix way, I don’t think it precludes the possibility to allow defaults to be overridden with a command line switch, especially in exceptional situations as above. You might want to alter number of threads depending on your connection (LAN vs LTE) This adds unnecessary complexity and ambiguity and bloat and increased possibilitity to misconfigure things. Command line utility is a backend, and it’s interface shall be clean, logical, and unambiguous, without 20 different ways to accomplish the same things. However I still disagree that we should be adding redundant features just because it seems to simplify one particular use case: this is what front ends are for. The current implementation of it as a command line argument is therefore the most appropriate. You might want to alter number of threads depending on your connection (LAN vs LTE), and therefore it should not be part of storage configuration, it shall be function of the environment. Whether it is right thing to do I’m still not sure. Home Reviews Software Backblaze cloud storage review Unlimited, continuous backups with competitive cloud storage pricing By Richard Sutherland published Comments. When you put it this way, yes, that proposal does make some sense if we think of it not as a “another way to specify command line arguments to save time typing” but instead “treating number of threads as part of storage backend configuration”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |