Thanks for the reply - I already took a look at that. Then let's put it another way: I need a tech deep dive. Deduplication stores segments of files and metadata needed to reconstruct complete files. Now, are metadata and segments sent to S3/Glacier as objects and recalled as such to the local dedup storage (which then still needs to exist), I.e. optimized duplication, or is there some intelligence in the cloud so that one can recall/restore the objects as files w/o the original local dedup?