Tintri Cloud Connector
Tintri Enterprise Cloud integration with public cloud resources
Extend Tintri Enterprise Cloud to Amazon Web Services and More
More and more organizations are adopting a multi-cloud strategy. Tintri Cloud Connector tightly integrates Tintri Enterprise Cloud to public clouds, such as Amazon Web Services, and private clouds that use public cloud APIs. That enables organizations to create hybrid cloud services with building blocks from on-premises enterprise infrastructure and cloud resources.
The Tintri Cloud Connector, introduced with Tintri OS version 4.4, adds the ability to replicate Tintri snapshots to cloud destinations. Tintri snapshots can now be replicated to AWS S3 (Simple Storage Services) and on-premises IBM COS (Cloud Object Storage).
Tintri systems feature significant built in data protection and disaster recovery features. Tintri snapshots are the basis for creating recovery points. A snapshot is a point in time copy of an individual virtual machine. Tintri asynchronous replication creates copies of snapshots on one or more different Tintri systems. Tintri asynchronous replication has been augmented with the ability to replicate from Tintri systems to supported cloud destinations using the S3 API (Application Programming Interface).
Combining Tintri asynchronous replication destinations with cloud replication destinations within a single protection plan introduces a new level of functionality that enables enhanced data protection and disaster recovery schemas.
Any Schedule, Any Destination, Any Retention Period…
Tintri provides a flexible data protection and disaster recovery solution that includes the ability to deploy multiple snapshot schedules, each with its own local retention value. Each schedule can also be configured to replicate to one, two, three, or up to four different Tintri systems, with a remote retention value. With the Cloud Connector, a snapshot schedule can also be configured to replicate to one or more cloud replication destinations, each with its own distinct cloud specific retention value.
FIGURE 1: Snapshot replication destinations
A combination of snapshot schedules, replication destinations, and retention periods are easily configured to create customized protection plans. As an example, a single VM (Virtual Machine) or group of VMs could be protected with:
- Hourly snapshots retained locally for 24 hours.
- Daily snapshots retained locally for 1 week that are also replicated to a different Tintri system where the replica snapshots are retained for 2 weeks.
- Weekly snapshots retained locally for 2 weeks that are also replicated to an on-premises IBM COS destination that are retained for 3 months.
- Monthly snapshots retained locally for 2 months that are also replicated to an AWS S3 region that are retained for 2 years.
Tintri enables your organization to implement a flexible DP/DR strategy to satisfy changing business requirements. You can easily configure application protection policies from Tintri Global Center with any schedule, any retention period and any protection target (see Figure 2). Tintri’s native integration with different cloud vendors replaces or complements traditional backup architectures.
FIGURE 2: Flexible application protection policies
Recover with high space efficiency
Tintri snapshots are space efficient with inline compression and deduplication, and only changed data are sent over the WAN. Data services and policy management are performed at the right level of abstraction – optimized for efficiency, cost and speed of recovery. Tintri Cloud Connector is designed to minimize HTTP requests such as GET and PUT, reducing public cloud access charges. These charges can become significant when you have a large amount of data to recover or during recovery from a service outage. You can quickly recover from the cloud to any local Tintri storage (see Figure 3) and perform a file level restore (FLR) to recover just the data needed.
FIGURE 3: Download snapshots from cloud to any Tintri storage system
The use of cloud replication may present a cost reduction opportunity for deployments that:
- Currently use tape media for long term retention.
- Currently use tape media for the creation of offsite backup copies.
- Currently use a purpose built backup appliance to retain backup copies on a different media type.
Transition Point Elimination
The Tintri Cloud Connector replicates scheduled snapshots directly to one or more cloud destinations. There is no requirement to use or pay for a cloud gateway. There is no requirement to use a third party backup application. There is no requirement to stage snapshot data on a local caching device prior to replication.
When a cloud resident snapshot is needed for restoration, it can be easily downloaded to any Tintri system managed by TGC (Tintri Global Center). There is no requirement to download snapshots to the Tintri system on which they originated. Not only does this capability eliminate multiple phase recovery steps that may be required with caching or gateway devices, it also enables the ability to easily and frequently test disaster recovery processes.
Security and performance
Tintri provides data-at-rest encryption on the cloud backup target and secure transmission to the cloud with SSL encryption. In the meantime, there is no impact on application performance. You can configure all your replication destinations and manage the keys from a single location – Tintri Global Center
FIGURE 4: Configure cloud destinations in Tintri Global Center
Tintri Cloud Connector unites your on-premises infrastructure with AWS public cloud resources and IBM Cloud Object Storage, so you can create hybrid cloud services. Tintri makes this simple and efficient by operating at the right level of abstraction for virtualization and cloud—use AWS for the data protection, archive and disaster recovery of your mission critical on-premises applications and restore applications in a single click to your Tintri Enterprise Cloud.
Download the Tintri Cloud Connector Datasheet (PDF).