The main thing to notice is that in every one of these approaches there is at least one transition point—in effect a middleman—before data reaches the S3 object store. While these transition points may confer some advantages (like enabling you to keep using your existing backup software), each one introduces another point of management (usually with a separate interface) and also adds cost. Perhaps more importantly, these transition points also have a negative effect on the speed and efficiency of data movement, the network bandwidth needed, and the amount of storage consumed. It is far more efficient to move data directly from primary storage to cloud storage.
Tintri cloud connector eliminates transition points
Tintri asynchronous replication operates in two modes:
- Node-to-node. VMs are replicated from one Tintri storage system to another.
- Node-to-S3. VMs are replicated from Tintri storage directly to an S3 object store.
Using Tintri Cloud Connector, you can create and replicate individual VM snapshots:
- Across a cluster of Tintri storage arrays
- To a third party on-premises object store like IBM COS
- To a third party public object store like AWS S3
- Simultaneously to both Tintri storage and S3 object stores
Tintri shrinks the workflow for replicating data to the cloud as shown below.