I do utilize the automated policy-driven operations with Veritas Alta Data Protection. They have helped in reducing manual workloads because manual intervention is required to handle errors or backup job failures when trying to back up a particular AWS account where critical resources are deployed. Discovery takes a lot of time because we are backing up data already in the S3 buckets. We often face challenges with resource discovery because discovery does not happen once a month; it happens daily. Every day, the discovery job runs before backing up resources. We may encounter issues in discovery or related to permissions, meaning if we have backup permissions on a bucket but further intensive permissions are present on any particular file, the Veritas Alta Data Protection job will skip that file. At times, backup fails with one or another error, and manual intervention is definitely needed. It is predominantly automated and policy-driven, but manual intervention is also required sometimes. We tested the effectiveness of Veritas Alta Data Protection's granular restoration feature during POC because we had a requirement to test various scenarios like restoring the bucket in a particular region, restoring the bucket in a different region, restoring EC2 instances, restoring containers, and databases. One more crucial feature for us in selecting Veritas Alta Data Protection is having replication between Veritas Alta Data Protection clusters. Once the primary backup job is complete, Veritas Alta Data Protection runs an SLP job, which is a storage lifecycle policy. This SLP job moves or replicates the data from one Veritas Alta Data Protection cluster to another. If the Veritas Alta Data Protection cluster goes down, the data is still replicated to the other Veritas Alta Data Protection cluster.
