4 ms·
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 o
by 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?
- jlawer 12y agoI am assuming by encryption in motion you are talking about using SSL tunnels to transfer the data. I can't see much in the way of details so I figured you might be able to help - How do you ensure consistency of the disk for the snapshot? (i.e. the time it takes to walk the filesystem and files have changed) - How do you verify the file is captured in its entirety? - How do you know a file has changed? - Do you de-duplicate the storage? - What filesystems / attributes do you support / don't support? - Do you support bare metal restoration? - Do you transfer the Delta or complete copy of changed files?
- perlancar 12y ago> 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. So I read it as meaning that data is not encrypted at all on disk (i.e. no privacy). This does render the service useless for, not all, but many use-cases. >> 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. I hope you're kidding :-)