SourceOne File and MS Branchcache?

The file is retrieved from the Archive Server.

It would have to be accessible to the end user wherever they need the access.

Gary, thank you for your quick response.

So, just to verify, a downstream Windows 7 user with BranchCache enabled goes to access a file on the primary (source) share, that has been archived.  The BrancheCache should identify that the file has been changed, so, the BranchCache client should access the file from the primary share.

S1 would then intervene, and return the file to him from the archive.

Correct?

If so, that's exactly what we're hoping for.

Thanks,

Eric

In that case you would need to DiskXtender.

S1 for Files doesn't connect into the NTFS Stack like DiskXtender does.

S1 would be essential be a Windows Shortcut (.lnk) that would have to be retrieved from the S1 Archive server directly.

Gary,

Thank you for your response.

I am familiar with Disk Extender, as I took a deep-dive training on it several years ago while I was working at EMC.  I recall that it stubs out files within the NTFS, actually embedding content into the stub files with references to the files' archived locations.  (Frankly, I thought DX was EOL, in favor of moving to S1 and/or CTA).

What I'm gathering from you is that S1 does not work that way at all.

Do you know of any white papers or deeper-dive technical content that explains how S1 for Files actually works?  I am having some difficulty in finding that information.

Thanks,

Eric

I second Eric's request for technical documentation on how S1 file archiving functions.  I had assumed (incorrectly it turns out) that it used a filter driver architecture similar to DX; if we are really talking about .lnk shortcut files replacing "real" files that is a radically different design with very different implications for day-to-day administration.

Does anyone know if such technical documentation is available from EMC?

Regards,

Mike Horgan