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 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.
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.
Leading Kubernetes Data Protection and Mobility
Trusted by the world’s largest organizations, Veeam Kasten delivers secure, Kubernetes-native data protection and application mobility for the most complete set of distributions and platforms at enterprise scale. We also give operations and application teams the confidence to withstand the unexpected and deliver faster, all without complex scripting, unsupported tools, or legacy solutions.
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 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.
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.