Introducing RunCloud Backup and Agent 2.0.5 Changelog

Introducing RunCloud Backup and Agent 2.0.5 Changelog

RunCloud Backup

Today we are so happy to announce our latest feature inside RunCloud. The backup feature is the most requested feature from our customers. We do receive chat almost every day asking for the backup feature inside the chat. And now, here it is!

This solution does not store the backup file on your server, but it will be stored securely on our backup server. If something bad happens to your server, you will still be able to download and restore your backup. Neat!

You can backup your Web Application or Database with RunCloud backup. With RunCloud Backup, you can set the backup interval. Every two hours, six hours or every three days. And we do give freedom to you when you wanted to delete the backup files that have been created. You can store the backup files for as long as 30 days, two weeks, or three days.

Backup File Restoration

A backup without an ability to restore the backup file is not a good backup solution. By using RunCloud Backup, you can directly deploy your backup to any Web Application or Database inside other server managed by RunCloud. With just a click of a button, you will be able to restore your backup to any Web Application or Database that you want.

If you need to restore the backup inside another server that is not provisioned by RunCloud, you can directly download the tarball and restore it manually. Downloading your backup file will require API Key and API Secret. You can read it more in the API Key Docs.

Backup Pricing

Due to storing the backup files inside our cloud storage, we can’t help but charge you a low charge for each backup instance. The pricing it flat $0.03/day for Pro Plan and $0.06/day for Free Plan customer for each backup instance.

You will also get 30GB of storage to store your backup. This is more than enough if you are a single user. But if you are an agency, you can extend the backup storage space for a very low price. You can extend up to 1TB of backup space.

RunCloud Agent 2.05 Changelog

Removing node js as a dependency. We forgot to remove node js as a dependency for RunCloud Agent, thus will make it difficult for our customers to upgrade the node js. Thank you to Mubarrid Albar for notifying us about this.

Create system user will no longer able to read the Nginx, Apache and PHP configuration. So, those users won’t know about other sites on the server.

The latest agent also fixes a bug where starting a service from Services Page does not automatically start itself when the server has been rebooted.

4 responses to “Introducing RunCloud Backup and Agent 2.0.5 Changelog”

  1. Brandon says:

    Awesome work team! For clarification on the pricing, what makes up a backup instance? If you set a daily backup with 2 week retention, are you going to charge $0.05 per day for every daily backup? Will that also be charged for the database backups for each of those days? Thank you!

    • admin says:

      1 web application is 1 instance. 1 database is one instance. So if you are backing up 1 system (1 web app + 1 database), it would be 2 backup instances. It doesn’t matter how long you set to retain your backup data, each instance will be charged per day.

Leave a Reply

Your email address will not be published. Required fields are marked *