Veeam Kasten Reviews

The main use case for Veeam Kasten is to protect Kubernetes applications and ensure disaster recovery. We use it to take backups of applications, namespaces, persistent volumes, PVCs, and Kubernetes resources. All backups are stored in S3-compatible object storage such as MinIO. If any application, namespace, or cluster encounters an issue, we can quickly restore the data and bring the application back online with minimum downtime. We also use scheduled backup policies to automate the entire backup process.

Veeam Kasten has had a very positive impact on our organization. It has improved our disaster recovery process by ensuring that all Kubernetes applications are backed up automatically and can be restored quickly if something goes wrong. Earlier, recovery used to take much more time, but now we can restore applications in a few minutes, which reduces downtime significantly. It also gives confidence to the development and operations teams because we know our application data is safe and recovery is reliable and very easy.

Before using Veeam Kasten, recovering a stateful application used to take around two to three hours because we had to recreate resources and recover data manually. Now, with the scheduled backups and restore points, we can restore the complete application, including the namespace, PVs, PVCs, deployments, and services in around ten to twenty minutes. This has reduced our recovery time by nearly eighty to ninety percent and has significantly reduced downtime for the application during disaster recovery testing.

The best features of Veeam Kasten are its policy-based automated backup, application-consistent backups, and fast restore. I also appreciate its CSI snapshot integration, which makes backups and restores faster for persistent volumes. It supports S3-compatible storage such as MinIO, so storing backups is easy. Another valuable feature is role-based access control for security, and the dashboard is simple to monitor backup jobs, restore points, and backup status. Overall, it is very reliable for Kubernetes backup and disaster recovery.

Another feature I appreciate is the simple web dashboard. From one place, I can monitor backup jobs, restore points, policies, and storage location. It also supports role-based access control, so only authorized users can perform backup or restore operations. Overall, it is very easy to manage, reliable, and gives us confidence that our Kubernetes applications are always protected.

Once the backup policies are configured, the whole process becomes automated. We do not need to manually take backups every day. During disaster recovery testing or any other outage, we can quickly restore the application, namespace, or PVCs from the latest restore point. This helps reduce downtime and gives confidence that our Kubernetes workloads are protected. That is the main reason we use Veeam Kasten in our environment.

It has made our work much easier because most of the backup processes are now automated. Once I created the backup policy, Veeam Kasten takes backups on schedule without any manual work. Every morning, I just check the dashboard to verify that all backup jobs are completely successful. If a developer accidentally deletes a namespace or PVC, I can restore it within a few minutes instead of rebuilding everything manually. This saves a lot of time, reduces our downtime, and allows me to focus on Kubernetes administration tasks.

Overall, I am happy with Veeam Kasten, but I think the multi-cluster management dashboard can be improved. When managing multiple Kubernetes clusters, it would be better if the backup jobs, policies, and alerts were available in one unified view. I also feel that the user interface can be made a bit more user-friendly, especially for quick filtering of backup jobs and restore points in a large environment. Other than that, I have not faced any major issues with it.

One more important improvement I would like to suggest is better reporting and alerting. It would be helpful if backup failures and storage usage were more detailed in the dashboard without needing any external monitoring tool. Apart from that, the documentation is very good, and I have not faced any major issues with the installation or configuration integration with Kubernetes, OpenShift, or RKE2, and S3-compatible storage is straightforward. Overall, I am satisfied with the product.

I have been working with Veeam Kasten for around one year and six months.

5

In my experience, Veeam Kasten does not have artificial intelligence features that I use in my daily work, so I cannot really comment on the accuracy of the artificial intelligence outputs. What I can say is that its backup and restore operations are very reliable. The backup jobs, restore points, and recovery results have been accurate and consistent in our environment. During our disaster recovery testing, the applications, PVCs, and Kubernetes resources were restored successfully without any data issues. Therefore, I trust the product for backup and recovery.

In our organization, we use a hybrid deployment. Our Kubernetes clusters are running on-premises as well as on AWS. We deployed Veeam Kasten inside the Kubernetes cluster using Helm. For backup storage, we use S3-compatible storage, AWS S3 for the cloud environment, and object storage in our on-premises environment. This setup gives us flexibility to protect workloads in both environments and perform disaster recovery whenever required.

In our AWS environment, we use S3 as a backup repository for Veeam Kasten. Our setup is hybrid, so some Kubernetes clusters are on-premises and some are on AWS. Veeam Kasten manages backups for both environments, and storing backups in Amazon S3 gives us secure, scalable, and durable storage for disaster recovery.

I give this product a rating of ten out of ten.

Veeam Kasten for Kubernetes is used as a backup solution for Kubernetes distributions. I use it for taking backups of the applications and workloads that are running on Kubernetes.

Veeam Kasten for Kubernetes does not require any additional setup. It runs as a pod inside a cluster, allowing you to take a backup of your Kubernetes cluster from within it. It has snapshot-level capability, so you can take a backup of your complete cluster and store it in your cloud environment such as S3 buckets.

Integration of Veeam Kasten for Kubernetes is easier because it can be deployed on any type of CNCF-certified Kubernetes distribution. I usually integrate Veeam Kasten for Kubernetes with my Kubernetes cluster, which can be on any platform such as Nutanix, OpenShift, or bare metal.

It increases the backup process with its automation feature. I only need to schedule the time and which namespace or workload type should be backed up at a particular time of the month, day, or week, and it automates the process effectively. It also transfers, imports, and exports the data wherever I need.

Veeam Kasten for Kubernetes has excellent security measures with different types of roles. I cannot take a backup of anything without the appropriate role, and I also need a token for accessing the Veeam Kasten for Kubernetes dashboard. It has robust security features.

Veeam Kasten for Kubernetes offers a lot of policy features. Inside my cluster and dashboard, I can create policies and use them according to my compliance requirements.

Veeam Kasten for Kubernetes can improve its multi-cluster setup dashboard because the multi-cluster and single-cluster dashboards are the same. Improving the multi-cluster setup would be more beneficial for users, and the user interface could be enhanced.

I have been working with Veeam Kasten for Kubernetes for the past six to eight months.

I have not experienced any stability issues. During my six to eight months of using Veeam Kasten for Kubernetes, I did not find any issues that required improvement from my perspective.

From the perspective of scalability, I would rate it as a ten out of ten. Because Veeam Kasten for Kubernetes is a backup product, the main scalability depends on the storage where all backups are stored. Veeam Kasten for Kubernetes offers S3 buckets, cloud storage, internal storage options, and I can scale it up or down according to my requirements at any time.

For the initial setup, I first required a Kubernetes cluster, which can be on any platform such as OpenShift, Nutanix, or elsewhere. Then I needed to download the bundle of images from Veeam Kasten for Kubernetes. I could install Veeam Kasten for Kubernetes using the command line or helm-based installation. After that, I only needed to create its pod, and when the pod started running, I received a dashboard IP where I could access my dashboard. From there, I could take a backup of my whole cluster. If I was using an air-gap environment, I needed a private registry so I could put all the images there and deploy Veeam Kasten for Kubernetes from there.

I have participated in the initial setup and have also done the process of taking backups.

Veeam Kasten for Kubernetes is a very good backup solution. During times of DC/DR, whenever clusters or systems go down, I can use previously taken backups, and my DevOps team can integrate and migrate them, rebuilding my stopped cluster in less time. It reduces my downtime significantly.

There are no challenges with Veeam Kasten for Kubernetes. It is straightforward and comes with proper documentation.

The documentation is thorough and up to date.

Updates are fine, and there is no need for any additional updates. Veeam Kasten for Kubernetes also makes updates according to version changes. I would rate this product a ten out of ten overall.

I use Veeam Kasten for Kubernetes only for backup of shop floor PCs.

The effectiveness of Veeam Kasten for Kubernetes in minimizing operational complexities is saving our lives. If we have an impact on production shop floor computers, which are automated computers online in our production lines, it is really beneficial to have a backup and re-image it from the cloud. It is very easy for us.

Veeam Kasten for Kubernetes brought positive impact to my company through re-imaging, which saved our time and our PCs. Our backups have saved our lives.

Veeam Kasten for Kubernetes helped raise productivity for my DevOps team and provided productivity for my team.

They implement it with a token, which allows me to re-image my PCs.

I do not think Veeam Kasten for Kubernetes has anything that could be improved as I am happy with it.

The stability part could be improved a little bit.

I have been using Veeam Kasten for Kubernetes for one to two years or more.

I am not using the integration features of Veeam Kasten.

Installing Veeam Kasten for Kubernetes was easy for me because I am not involved in the installation process.

On a scale from one to ten for stability, I rate Veeam Kasten for Kubernetes a nine.

I am happy with the product and do not see anything preventing me from rating stability as a ten.

I am satisfied with the stability part and do not think it needs improvement.

For scalability, I rate it nine.

I do not know about the technical support of Veeam because I cannot create tickets directly. I can create tickets with my backup team, and if needed, they reach out to Veeam.

Neutral

I have never worked with any other products or solutions before Veeam.

Seven or eight people from my company participated in the installation.

It is a combination of engineers and administrators.

My opinion about Veeam solutions is based on my previous review for a Veeam product, which we discussed before starting to use the cloud product.

Aside from Veeam Backup for Microsoft 365, I am currently working with just that solution.

I work with a cloud solution, which I believe is AWS cloud, though I am not certain. We might have more, but as a system administrator, I have limited visibility. We have global supporters for different teams, such as server team and backup team.

I am uncertain whether we use private or public cloud, though it might be private since it is our cloud server for IT.

I do not know about the security measures of Veeam Kasten or how its dynamic policies assist my organization in maintaining compliance.

The choice of Veeam Kasten for Kubernetes was a global decision.

I rate this solution nine out of ten.