Backupsy - a 3 week review
This is a 3 week review of Backupsy my new backup provider.
Replication of a 100GB MySQL database with about 1TB of updates and inserts per month is so far going good, barely any CPU usage and IOWait once the server caught up. So far haven't been told im using too much resources with the replication. It is on the NL node so I should be allowed a bit more processing power there, it remains to be seen if I can replicate it to the US (but most likely not do mysqldump's as those DO use CPU).
Currently doing mysqldump + lmza for transfer to a local long term backup storage, so far I haven't had any complaints about the CPU usage for the period LMZA is running.
Network speed as tested from a 100mbit server seemed good sitting close to 80mbit (what I limited the transfer at) for most of a 100GB transfer over SSH (rsync). I haven't tested gbit yet, nor do I expect to have the need to. Certainly seems like there is enough network available for large transfers.
Support was very good during a turbulent setup (problems with the DHCP server assigning IPs). Reply's were quick and actually solved the problem. Got a manual upgrade so that I didnt need to manage two services and a transition etc. Was annoying that they couldn't resize the KVM disk (its can be a difficult task so it is understandable).
It would have been nice if the ram increased with the plans, the servers may not be meant for processing but if you are running a mysql database as a slave and running mysqldump on it for purpose of storage (to be sent offsite to another Backupsy instance) a bit more ram is always nice.
It Would be nice if a bandwidth graph was included in the panel, of course you can do this yourself but when isn't a preconfigured pretty picture nice?
Overall - Very impressed, it is delivered as advertised and is a must for anyone with large datasets needing to be backed up.
Note: Also it could be more useful if it was possible to get different intervals of CPU/IOWait graphs, would certainly have made writing this review easier :)
Tips for those planning on a similar setup to me:
ensure relay space is limited, if you leave it unset it will fill up the disk and cause mysql data corruption (and hence a re-sync)
be sure to test your backups
run the same mysql version on your slave as you do your master, mysql may support one minor version each way but there is know guaruntee (and it might create inconsistencies, as in my case
ensure you monitor the slave status with a monitoring server (with alerts). MySQL slaves are easily broken.
Latest Offer: 30% off / $7 Anycast DDoS Protection (Australia Day Sale)