Cloud adoption offers many benefits, especially on cost, security, and high availability, however, there is also the hidden cost which usually slips in without you knowing it. These hidden costs include egress cost, unused resource cost, and many others. Egress free is a cost imposed on you when you move your data out of the cloud provider. The egress charges vary among cloud providers and the transaction type. Many companies out there are paying on a daily basis on every bit of data which moves out of the cloud, it could be for a daily transaction or even moving data to on-premises from the cloud storage. This cost is usually going unnoticed until you move out terabytes of data out of the cloud provider and you are billed for the transaction. This could be another form of vendor lock-in by the cloud which is a major concern for organisations wanting to move to the cloud.
How do you get away with egress, one of the biggest hidden costs, and not being trapped with a cloud provider? One of the many solutions is to look for a cloud provider which promises you large amounts of storage with no egress fees; allowing you to be able to exit with your data at any time you want. Currently, there are many new cloud providers offering massive object storage without egress charges like Filebase and Wasabi. Filebase is an S3 compatible object storage provider giving a simple cloud storage plans without any egress charges. This blog gives you an overview of Filebase and how it integrates with Backup Ninja to enable backup services for their users.
Overview of Filebase
Filebase is an S3 compliant object storage cloud provider offering its services with no ingress or egress fees. With Sia technology as its underlying storage layer, Filebase storage mechanism creates native redundancy and high availability. When a file is uploaded to Filebase, it is split into 30 pieces and distributed geographically to Sia host servers all around the world and to down and to recover a file, only 10 pieces are required. This ensures a faster restoration process and minimises the downtime
Highlights of Filebase
- Support for data redundancy as it distributes data to Sia servers all around the world.
- Support for high availability. You only need 10 out of the 30 pieces of data to recover a file which helps to reduce downtime.
- 3 simple pricing plan to avoid confusion and complexity in choosing plans. You get to have Filebase caching technology, email support, and no egress or API fees for all three plans. The only difference is the storage space.
- End to end security for at-rest and in-transit data.
- Powered by blockchain technology and enforcers cryptographic SLA to ensure files are stored securely.
- Integrates with S3 compliant tools seamlessly.
Backup Ninja on Filebase
Filebase works well with any S3 compliant tool like Backup Ninja. This gives their users the flexibility to have externally managed services like file management or backup services on Filebase cloud storage. Backup Ninja is an automated web based backup service for files, directories, and specifically designed to backup open source databases like MySQL, PostgreSQL, MongoDB, Percona, and Timescale at its native method. It has advanced monitoring and notification capabilities to keep you updated with all backup events happening on the server deployed with Backup Ninja’s bartender agent. The upcoming sections will show you how to configure and schedule backups on Filebase on Backup Ninja.
Setting up Filebase on Backup Ninja
Step 1: Select Filebase as a cloud provider.
Step 2: Select the backup region.
Step 3: Enter the Filebase cloud credential settings. The bucket name can be any name of your preference.
Step 4: Give a name for your cloud storage configuration. This will be used when you schedule a backup.
Step 5: Filebase cloud is configured on Backup Ninja.
Schedule Backups on Filebase Using Backup Ninja
Once you have successfully configured the cloud storage, you can now easily configure the backup schedule on Backup Ninja in just five steps.
Step 1: Enter the details for the backup schedule.
Step 2: Select the cloud credentials created earlier from the dropdown. The retention period has defaulted to 7 days, you may change it accordingly.
Step 3: Enter the backup name in the given format.
Step 4: Select the given option to state when the backup should be scheduled.
Step 5: View the configured schedule on the dashboard.
Cloud adoption is definitely the way to go if you have applications requiring scalable storage options. It not only saves massive cost on infrastructure upgrades but also provides a safer means for data recovery in case of any disaster. A smarter way to have optimum value when transitioning to the cloud is to study carefully the options made available by the cloud provider not only on pricing plans but also the hidden cost which is probably spelt out in the SLA. More often than not you won’t be needing to move out data from one cloud to another but if your company works heavily on data transactions, then understanding the charges on data ingress and egress will save you a lot of time and cost. Companies like Filebase or Wasabi not only offers you massive object storage but also removes the egress and API fees, allowing you to move your data out of the cloud anytime without any extra cost.