Curator restore takes significantly more time compared to snapshot operation

I am doing a snapshot on one region and restore on another region using curator.
This job is scheduled job which runs every one hour. In one particular job instance, snapshot took 4 minutes but restore took more than 1 hour.
I do not understand why restore needs more time compared to snapshot activity.
Why is that the restore activity takes more than snapshot time?

Which region is the repository in? Is it closer to the cluster in which you did the snapshot than the one in which you did the restore?

Snapshot and restore operations are quite latency sensitive, particularly if you have a lot of small segments, and cross-region latency can be a couple of orders of magnitude higher than intra-region latency.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.