Hotel chain migrated nearly 3 PB from SharePoint and file shares to Nasuni — globally, with a cache-aware engine recommended by Nasuni.
A reputable hotel chain was moving from SharePoint and Windows file shares to Nasuni as part of a global storage modernization. The dataset was close to 3 PB. The problem was that Nasuni filers, by design, use a local cache that fills up during heavy ingest — and every other migration tool the team tried failed when the cache hit its limit. After working with Nasuni directly, the customer was pointed to a tool built for exactly this situation: GS RichCopy 360 Enterprise.
A 3 PB migration with one hidden architectural constraint.
The hotel chain's data lived where most large enterprises' data lives: SharePoint Online and Windows file shares, accumulated across many properties and corporate functions worldwide. They were moving all of it to Nasuni, a hybrid cloud storage platform that combines on-prem filer caches with cloud object storage on the backend.
On paper this was a routine — if very large — migration: pull data from the sources, write it to the destination, repeat across regions. In practice, every tool they tried hit the same wall: Nasuni filer cache exhaustion. Nasuni filers cache data locally before snapshotting it to cloud object storage. When you push data in faster than the snapshot cycle can clear the cache, the cache fills, writes stall, and any tool that doesn't understand the architecture fails the job outright. At 3 PB and global scope, this wasn't an occasional inconvenience — it was the entire migration's bottleneck.
Cache-aware migration, no babysitting required.
Instead of overwhelming the filer cache and failing, GS RichCopy 360 Enterprise monitors the Nasuni filer state and automatically paces itself around the snapshot cycle.
A hybrid cloud filer isn't just another network share.
Migration tools that work fine for plain SMB or NFS targets fail in specific ways against Nasuni's caching architecture.
Generic tools have no cache awareness
Most migration tools treat the Nasuni filer like any other SMB share — push as fast as the network allows. When the local cache fills before the next snapshot, writes start failing, and the tool either crashes the job or floods the logs with errors.
Manual throttling guesses at the wrong number
Some teams try to compensate by hand-tuning throughput limits. But snapshot timing varies with data shape, network, and load — a static rate limit is either too aggressive (failures return) or too conservative (the migration takes forever).
Restart-from-scratch isn't viable at PB scale
When jobs fail mid-flight on a multi-petabyte transfer, having to restart entire chunks of work — or worse, the whole job — turns the migration into a months-long ordeal of false starts.
Global rollout multiplies every problem
The hotel's migration spanned multiple regions and dozens of filers. Any tool that required hands-on operator intervention on every cache fill would have made global execution operationally impossible.
GS RichCopy 360 Enterprise — purpose-built for Nasuni.
RichCopy 360's Nasuni filer cache-aware engine automatically detects cache state and paces itself around the snapshot cycle — no manual throttling, no failed jobs, no operator babysitting.
Multi-Source Ingest
RichCopy 360 pulled data from both SharePoint Online and Windows file shares in parallel — one tool covering every source the migration scope required, with no need to license separate utilities.
Cache-Aware Writes to Nasuni
As data landed on the Nasuni filer, RichCopy 360 monitored cache state. When the cache approached full, the job paused automatically before any write could fail — protecting the migration from the failure mode that broke every other tool.
Auto-Resume on Snapshot Completion
RichCopy 360 polled the filer for snapshot status. When the snapshot completed and cache space freed up, the job resumed exactly where it paused — no operator action, no restart, no lost progress.
The defining capability here is that RichCopy 360 was built with Nasuni's architecture in mind, not adapted to it. Generic copy tools push data until the destination pushes back; cache-aware migration means recognizing that on a hybrid cloud filer, the destination's "no" isn't a failure to retry — it's a signal to pause and wait for the snapshot cycle. By turning that signal into an automatic pause-and-resume loop, RichCopy 360 made it possible to run a 3 PB global migration as a set of jobs that simply complete on their own time.
The operational impact was the bigger story. Across a global rollout spanning many regions and dozens of filers, the IT team's job became job management instead of job rescue. Operators scheduled migrations, monitored progress, and validated completion — they didn't sit and wait for cache-full alerts to manually restart things. That's the difference between a tool that does the work and a tool that creates work.
The validation of the approach came after the project. The hotel adopted GS RichCopy 360 Enterprise as its primary data migration and replication tool going forward — not just for the Nasuni cutover, but for every subsequent data movement workload across the business. A successful one-time project became a long-term standardization.
3 PB delivered. Globally. With one tool.
Real petabyte-scale migration, real hybrid cloud architecture, real operational simplicity.
The right tool for the destination — not just the network.
Most migration tools optimize for the network. The best ones optimize for the destination's actual behavior. For Nasuni's hybrid cloud filer architecture, that means understanding the cache and snapshot cycle — and adapting to it automatically instead of failing into it. GS RichCopy 360 Enterprise didn't just survive a 3 PB global migration to Nasuni. It earned the customer's standardization for every workload that came after.
Migrating to Nasuni — or any hybrid cloud filer?
GS RichCopy 360 Enterprise's Nasuni filer cache-aware engine automatically paces migrations around snapshot cycles — eliminating the failure mode that breaks generic copy tools at petabyte scale.