I’m wondering what’s the proper approach to data verification in native cloud environments. The environment is built within the cloud, CS, MA, Cloud Libs etc. are placed in the same cloud solution, so the infrastructure traffic basically stays within the cloud.
The only reference that I’ve found in the docs was:
Tip: By default, the data verification schedule policy that is created by the system is not configured with data mover MediaAgents that use a cloud storage product, because the read operations from the cloud are very slow and are performed on low latency media. If necessary, you can perform the data verification on the cloud storage manually.
To run data verification on data that is stored on archive cloud storage, first recall the data to the main cloud storage location. Then you can run the data verification job on the recalled data.
But in this case the MediaAgents, are not data movers, but DDB hosts with cloud libs attached as well.
So are there any specific recommendations to data verification for cloud native environments or any important mentions?