Scality Ecosystem & Application Partners
Scality and Ctera.
The Ctera Global File System with Scality RING. Every site reads and writes the same file space, files cache locally for LAN-speed access, the canonical copy lives on Scality.
the problem
Files have to be fast at every site and consistent across all of them.
Branch users want local-LAN speed. The organization needs one authoritative version of each file. Traditional NAS does not stretch across sites, and sync products drift.
- Local-LAN performance required per site.
- One authoritative copy across the organization.
- Cloud-only file gives up local speed.
- Sync products drift; traditional NAS does not span sites.
the joint solution
Ctera Edge with a Scality back end.
Ctera Edge Filers serve the active set on local LAN at each site. Scality RING holds the namespace centrally. Files written through Ctera land in RING as objects, with versioning preserved.
- Ctera Edge serves active files at each site.
- Scality RING holds the namespace across sites.
- File versions land in RING as immutable objects.
- Runs on-prem when data residency matters.
joint solution benefits
What Ctera on Scality delivers.
Users see no change.
Same SMB and NFS shares end users already work with. The Ctera and Scality stack is invisible to them.
One file space across sites.
Branch, regional and remote sites read and write the same files. No per-site NAS to operate, back up or migrate.
Versioned objects, not file copies.
Files land in RING with versioning preserved. Recovery is a metadata operation rather than a tape job.
On-prem for sovereign estates.
The full stack runs on-prem across regional data centers. Used in EU public sector and healthcare.
Joint architecture
How Ctera runs on Scality.
Workloads flow through the partner integration and land on the Scality data layer.
Show us the workflow. We will show you the fit.
