Loading Profile...
Are you guys backing stuff up regularly? We don't want to wake up one day and find that our repository is gone
2 people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
I hear you :)
We plan to release S3 Backups to your own S3 Account in the future. This way you have some extra assurance that your data is in your own hands. Our terms are necessary for many reasons, but our actions and mindset are always with reliability, security, and backups.
I think that giving customers their own backup options would be a more comfortable approach, in addition to our own backups.
What do you think?
Chris
The company says
this answers the question
-
Inappropriate?Of course! We currently have very frequent server backups to a secondary data center as well as Amazon S3 backups for each account. We are a little paranoid when it comes to backing things up, but we've learned from past mistakes that you can never be too paranoid with this stuff.
In reality, backup, reliability, and security are our main priorities. Sure, we want a great UI and great features, but when it comes to hosted Subversion, making sure your data is accessible and safe is the most important aspect.
We are moving to new servers this weekend (at SoftLayer). I am creating a blog post at our company site about the migration and our decisions. If you are interested, feel free to check out our site on Monday.
http://www.wildbit.com/blog
Chris -
Inappropriate?Glad to hear it. I've been following your blog, looking forward to the other changed that you've mentioned (hopefully FogBugz on Demand support, too :) -
Inappropriate?That's all well and good though IANAL be sure to stay abreast of the Terms of Service. Specifically the 'Limitation of Liability' section where they're not responsible if they lose your data, the 'Limitation of Liability' section where they can terminate your account at any time with no provision to return your data, and 'Conditions' where they can shut down the service at any time also with no provision to return your data.
Bottom line is that Beanstalk's offering a great service, no doubt about that, but as always you're ultimately responsible for your data so be sure to back it up yourself. Beanstalk provides a great export page so take advantage of it regularly!
By the way, kudos on the export being an actual repo export rather than just the source files.
I’m feeling icky about being a doubting thomas.
-
Inappropriate?I hear you :)
We plan to release S3 Backups to your own S3 Account in the future. This way you have some extra assurance that your data is in your own hands. Our terms are necessary for many reasons, but our actions and mindset are always with reliability, security, and backups.
I think that giving customers their own backup options would be a more comfortable approach, in addition to our own backups.
What do you think?
Chris
The company says
this answers the question
-
Inappropriate?I'm sympathetic on the TOS requirements. Goodness knows I've been there many times.
Backing up to the user's S3 account's an interesting idea, I'd certainly take advantage of it (especially if it did twitter/mail/whatever notifications). Perhaps rsync, scp(!), sftp access to the repo tarball? That would certainly enable integration with most any organization's backup system.
I agree that putting the backup options in the users hands is preferred. Provide a reasonable internal backup infrastructure, as you plan to do with your own S3 backup, and provide the user access for anything from there.
EMPLOYEE