=MGN=RedEagle
Well-known member
What do you guys make of this: http://www.bitcasa.com/
Then a guy like me comes along and stores 6 million files... lol.
Then a guy like me comes along and stores 6 million files... lol.
What do you guys make of this: http://www.bitcasa.com/
Then a guy like me comes along and stores 6 million files... lol.
What do you suggest for automatic daily backup of servers/database/files then?I just hope people don't store their only copy of files there ... $10 per month (or less) is not a sustainable business model for "unlimited". Make sure you can still access your data once the music stops playing.
Compare with Amazon's Glacier @ $0.01 per GB per month ... for $10, you can store 1TB on Glacier.
Then again, I guess if you assume that Bitcasa has a similar cost base such that $0.01/GB/m is profitable, then they only need to hope that on average, their users will store less than 1TB each and still make money on $10pm.
Realistically though, other than for automated processes, actively using and managing > 1TB in the cloud is generally unrealistic unless you have a Gbit internet link and can sustain high data transfer rates all the way to their data centre - effectively making it LAN-like. Anything less is just too slow for anything other than backups or small files.
You will then have to pay for bandwidth to upload those files off your server, right?http://sourceforge.net/projects/automysqlbackup/
... and then use a suitable amazon s3 backup script that uses duplicity and execute the script once a day via your server cron.
Eg. http://linux.justinhartman.com/Automated_Backup_to_Amazon_S3_with_Duplicity_on_Debian_Etch
What do you suggest for automatic daily backup of servers/database/files then?
http://www.rackspace.com/cloud/backup/ ??Some hosts like mine (Rackspace) charge for bandwidth.
There must be a better alternative?
when I do use the cloud, the minimal security I use is 2048 bit encryption (twice over), then zipped with password, encrypted again, and finally rar with password
Two different topics all together. OP was talking about personal cloud backups and nothing to do with sites. At least that is what is compared when you visit that link.So, I assume this would also apply to your website database backups? For security?
How about the original database itself on your MySQL servers? Do you also use 2048 bit encryption (twice over) on that, then zip is with a password, encrypt it again and then rar it with a password? Makes it a little bit difficult for PHP to read it doesn't it?
Personally, I think your MySQL server is far more vulnerable than most cloud backup solutions.
As for our site.... We have a few steps to keep it secure. If X person got a hold of it and tried to import it else where.... It would be very useless to them & odds are high they would only have part of it. We also make it a habit to keep the database else where. If you visit SociallyUncensored.eu the database isn't there (only files).
We have steps that I'll not talk about to prevent that.How does this provide any level of protection? If a hackers gains file level access to your webserver, they only need to read the library/config.php to see the location and account details to access your DB. If they have file level access to the webserver, then they are also most likely able to connect to the DB server and copy/dump it's contents.
I don't see it that way.moving to the cloud is simply necessary.
We use essential cookies to make this site work, and optional cookies to enhance your experience.