5 ms·

No word on encryption. No word on what is actually backed up, how to include or exclude files. No word on when anything is backed up and how (cronjob, daemon?

• vld 12y ago
  Some of those are answered here: https://my.jarvys.io/docs/home https://my.jarvys.io/docs/home
• thaumaturgy 12y ago
  It's built by the SSD Nodes people (https://www.ssdnodes.com/ https://www.ssdnodes.com/). I too would like to see more technical details on the site, but there's probably a better way to frame the criticism than "u r idiots".
• nodesocket 12y ago
  Your comments are exactly what peeve me about developer entitlement and ego's. I'd be curious if you've ever tried to run a business? Jarvys.io just launched, and their marketing site is geared toward features/benefits and not bogged down with technical details. In fact, a landing page that answers all your questions would be poor and missing the point of marketing. When dropbox launched did they go into the technical details of how it worked? "...a strong feeling you are not qualified to run a service like this". That really rubs me the wrong way. What do you know? Perhaps their development skills may not be the best, but if you look around at successful startups, usually the founders have a more rounded skill set other than being a pure hacker. They are designers, they are leaders, they hustle...
  • moe 12y ago
    I would agree if this was yet another Todo-List app. But this is a product that targets Linux novices and asks them to upload all their data under a hand-wavy promise of protection. There should be a tad more explanation on how privacy is ensured and how the actual protection works, no?
  • rb2k_ 12y ago
    While I don't necessarily question their ability to run the service, I think backups are one of those things where you DON'T want designers, leaders or hustlers trying to market a product rather than having a solid engineering base. For that kind of stuff, I want neckbeards that can install linux on a dead badger. The same reason why you wouldn't want to have your surgeon be a guy that manufactures scalpels. This is supposed to send, receive and store data for LONG periods of time without any accidents. It's "boring". Just as boring as safety belts and breaks on elevators, but just as important.
• XERQ 12y ago
  Hi there and thank you for taking the time to look into JARVYS. I'd happily go through and answer your questions. Some of them are answered here[0] > No word on encryption. We encrypt data in motion, but not at rest (yet). Since this is a beta product we wanted to get it out there first with a free version that would bring the barrier down and allow us to learn as much from users as possible. > No word on what is actually backed up, how to include or exclude files. By default it backs up everything except /proc and /sys, which you can change here (with detailed instructions): /var/jarvys/etc/include > No word on when anything is backed up and how (cronjob, daemon?). It's a cronjob that checks in with our servers every hour and backs up once a day. The reason it's not a daemon is because daemons die, and we needed something as bulletproof as possible. Checking in every hour allows us to tell you when your server hasn't been checking in (which means you can proactively see if your cron daemon is broken or if something else went wrong before it affects your backups). > No word on how running services and databases are backed up that may need special procedures for a consistent snapshot. We include a special script that allows you to run things like mysqldump before the servers back up to JARVYS: /var/jarvys/etc/run-before-backup.sh > No word on how to restore or access backups when the backed up host has failed. That's also included in here[0] - that feature is still in testing and hasn't been released yet. > All things considered I have a strong feeling you are not qualified to run a service like this. Your expertise seems to be in webdesign, not in Unix and servers. Another backup concern you didn't mention is bit rot, which we're using ZFS to mitigate. Thank you for your kind words regarding our website, our designer actually wrote a detailed blog post on how they came up with the logo[1]. We've been providing managed backup services (among other managed services) for our SSD Nodes[2] clients, which is for whom we originally built this service. [0] https://my.jarvys.io/docs/home https://my.jarvys.io/docs/home [1] https://blog.jarvys.io/2014/11/04/the-jarvys-logo-design/ https://blog.jarvys.io/2014/11/04/the-jarvys-logo-design/ [2] https://www.ssdnodes.com https://www.ssdnodes.com
  • panzi 12y ago
    > We encrypt data in motion, but not at rest (yet). What does this even mean? When is data in motion or at rest? I hope your servers never see a single unencrypted byte. Just imagine lots of services using your backup system. That will make you a very very valuable target for hacking. You don't need to hack N services anymore, you only need to hack one. Also what encryption algorithms are used? What key lengths? How are the keys generated? And even if you do proper encryption, how can the authenticity of your software be verified? What if you where hacked and the hacker manipulated your software and thus installs back doors on all your customers through your software install/update method? Can a customer see the source of what is running on their server? > By default it backs up everything except /proc and /sys I guess you don't include the encryption keys in the backup, so there has to be something more excluded. Also what about /tmp?