Restore operations across object storages, such as Amazon S3 and Azure Blob Storage, follow a common framework. This page describes restore scenarios that applies to all object storage types.
When selected objects share the same name during restore
When you restore multiple objects that have the same object name, the restore operation consolidates them into a single destination folder for that name.
In this example, two objects named shared-sub@2026 are selected from different source paths:
-
/animal-bucket-duplicate-files-and-folders/animal-zone_01
-
/finance-bucket-duplicate-files-and-folders/finance-zone_02
The restore action shows Restore (2) selected because two source objects are included in the restore job.
After restore, you will notice the following:
-
A single shared-sub@2026 folder is created in the destination.
-
Content from both selected source locations is placed in that folder.
-
If files have the same relative path or file name, they are combined in the consolidated output location.
To keep restored objects separated by their origin, preserve source paths when performing out-of-place restores or disk restores.
When identical file names across multiple buckets are selected during restore
During restore, the preview may display multiple objects with the same file name because they are stored in different buckets or folder paths. However, during actual restore, those objects may be treated as duplicates if the restore process identifies the destination based on the file name rather than the full source path. As a result, only one object may be restored, while other objects with the same file name may be skipped.
To ensure each object is restored as a separate copy, preserve source paths when performing out-of-place restores or disk restores.