You can see CPU steal when using the top command. In the hypervisor world, CPU steal can be seen as the hypervisor limiting your ability to use CPU cycles. In the significantly worse cause, your provider could be overselling there hardware, and the steal is coming from your neighbours sharing the physical hardware. I noticed from the screenshot that the server was a t3.medium. The T series processes at AWS are sold as burstable instances. They are not designed to be used at max capacity. If your server only sees a high load 20% of the time, it is perfect. At SnapShooter, we make hefty use of them as our ingestion load is very busty. Most people do backups at the hour mark, so our load always peaks for 5-10minutes after every hour. Continue Read
We are delighted to announce that we have added Scaleway for our backup support. You’ll be able to carry out your Scaleway volume backups from a single location. And, with our unique dashboard you’ll be able to back up Scaleway instances volumes hourly, daily or weekly. Continue Read
Need to get better insights on your DigitalOcean Spending? We have the prefect tool to keep an eye on your DigitalOcean costs. Monitor, Droplets, Apps, Volumes, Snapshots, Databases and Load Balancers. Continue Read
We are happy to announce we have added our new backup engine's ability to restore multiple files at once. When we launched our new backup system, we were happy with our one-click restore process. For example, you could restore on a MySQL database, and we would automatically SSH to your server and run the import. With our the latest update, you can select many files and restore them together. When you manage a backup, you will see the option to choose one or many files. Continue Read
If you are a system administrator and responsible for managing server then it is essential to manage the disk space on your server. Otherwise, you will get the error "the server is running out of disk space". If you have a Tera Bytes of storage then you don't need to clean up your server to free some disk space. But if you have limited disk space then freeing up disk space regularly will be necessary for you. Continue Read
How to connect your Laravel application to use UpCloud S3 for file storage Continue Read
We are happy to announce we have added support for Multiple WordPress backups. This enables businesses who manage many WordPress sites on one server to back them up as one SnapShooter job. Continue Read
We are happy to announce we have added UpCloud S3 storage support to SnapShooter. This means our customers can now use UpCloud Object storage to store their backup jobs data. We are proud to be working more closely with UpCloud with out Snapshot and now object storage support. Continue Read
A number of our customers have been requesting a way to limit the amount of CPU a backup process consumes. This is important to make sure during a backup the server does not dedicate t0o many resources to backups, and that other processes don't suffer, for example, you would not wish for your WordPress sites to become slow. We are proud to release a solution to this issue with an improvement to our new backup engine. At the server level now customers are free to set an uploading bandwidth limit, as well as a chunked upload limit. Continue Read
We are proud to announce our alpha release of GridPane, working with customer Jordan Trask, a business technologies consultant from Canada we have added GridPane as a backup solution for all SnapShooter Customers. Jordan uses GridPane to manage his customer's WordPress sites. It is a fantastic tool for provisioning and managing WordPress installs with any host you wish, DigitalOcean, Amazon Lightsail and UpCloud for example. Continue Read
A little bit of background. The 2nd of November was the launch of SnapShooter’s new backups engine. Now, this brought a lot of improvements to the way we do backups with databases and file systems as well as directly supporting applications. One of the most significant improvements I found was that we do real-time logging from a customers server back to SnapShooter. Unlike before where we would SSH into someone's server and pull the log periodically. This process was far more efficient; the logs would stream directly from customer servers back to SnapShooter. This was probably the biggest unknown for the launch because previously the traffic was relatively low. Server load was all dependent on the queue workers, but now we were going to be processing millions of inbound connections per day. Continue Read