KISS!įound something on the price, but I'm not sure if it applies to Google-drive, which must have some kind of flat-rate. The first run will just be a mounted folder. After the upgrade I will work on getting FUSE on CentOS and connected to Google-drive. Need to upgrade the KVM on my Virt server first. Haven't found any pricing or info on the bandwidth yet. Think that Google made a nice move here and I would gladly migrate to Google-drive for my backup purposes. I only use it for WP backups and some 40GB MP3's for redundancy on my CentovaCast server. I'm paying $3-4 a month on S3 for something like 70GB right now, and that is only the storage, not the bandwidth. ![]() I think that the $10/1TB is a beast, 1TB is really a substantial amount of backup-space - if not just double it. One way or the other, this is definitely something which can be useful, and as it is I really need to push the DA backups off-site and up to Google's drive, so, I'll make further research to see whats comes up. I'm a little reluctant right now to just throw this into production without further testing. If you have a dev install then your more than welcome to try. I will continue the research to find the most simple and stable solution. ![]() Also build a Pydio server at one point, it's build on a Debian, which also connects to S3 via s3fs without issues, but again, this is S3 and not Google's API.įound an intro on Python-FUSE, which can be used for making a simple File-system: The issues for me right now is stability, security and reliability. It works well, but I don't really know if it will run on CentOS just as nice. I have been running FUSE on Debian for a couple of years. Was also thinking about a Google-Drive DA plugin, and using Grive, but it's a little early for me to see the full picture. In that way multiple servers can use the service. Don't know about how much space I would need for this, or if it just can act like a proxy. To keep FUSE running in another VM and be able to play around and test stuff, trying to make it centralized and running as clean as possible. Was also playing with the idea of making a Linux distribution on KVM, solely for the purpose of syncing with Google-drive. "grive can do two-side synchronization between the Google Drive and local directory". Yes, I'm looking at different solutions right now. ![]() or working cases which utilizes Google drive for backup purposes? Plugins? So my question comes down to FUSE - is it ok or not?Īny thoughts?. It works as it is and have done that for many years, no problem with DA and backup, just need to be able to store the backup outside the center directly from DA to the clouds. It's more important that DA get some kind of incremental solution, or an off-site solution for backup purposes, like to Google-drive or S3 and not only ftp or ssh. They are stored locally on the machine and should eventually be moved outside the hosting center. The only thing which lags, is that the VM needs to be suspended during the backup, but these are actually just disaster recovery-images for a full restore. 1TB would be a nice addition because my 7 days rotation builds up.Īlternatively, I run DA in a KVM and using vzdump to make "bare-metal" snapshots locally. I use FTP right now, locally in the hosting center to a different machine, but I only have 100GB or so. Need to read more about it though, like bandwidth usage, etc.Īnyone here using Google-drive or S3 for the backups? Google-drive-ocamlfuse (FUSE) works in CentOS6.*, just unsure if it's stable or if it's a good idea at all. Goggle just dropped the price on their 1TB Google drive, so it's actually a pretty good deal right now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |