Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
NetApp MetroCluster setups consist of two geographically distinct, mirrored ONTAP clusters that function together to ensure ongoing data availability and SVM safeguarding. Each cluster continuously replicates its data aggregates to its counterpart, ensuring that both locations maintain identical copies of the data. In case one of the sites experiences a failure, administrators can quickly activate the mirrored SVM on the operational cluster, allowing for uninterrupted data service. The MetroCluster system accommodates both fabric-attached (FC) and IP-based cluster configurations: the fabric-attached MetroCluster utilizes FC transport for SyncMirror synchronization between sites, while MetroCluster IP operates over layer-2 stretched IP networks. Deployments of Stretch MetroCluster facilitate coverage across an entire campus, and with ONTAP versions 9.12.1 and 9.15.1, MetroCluster IP configurations can support up to four nodes using NVMe/FC or NVMe/TCP. Furthermore, it is important to note that front-end SAN protocols such as FC, FCoE, and iSCSI are fully supported within this architecture, enhancing the overall versatility of MetroCluster solutions. This flexible design accommodates various enterprise needs, making it an attractive option for organizations looking to optimize their data management strategies.
Description
As the utilization of Kubernetes continues to increase, organizations are discovering the necessity of managing and deploying several clusters in order to support essential capabilities such as geo-redundancy, scalability, and fault isolation for their applications. Submariner enables your applications and services to operate seamlessly across various cloud providers, data centers, and geographical regions. To initiate this process, the Broker must be set up on a singular Kubernetes cluster. It is essential that the API server of this cluster is accessible to all other Kubernetes clusters that are linked through Submariner. This can either be a dedicated cluster or one of the already connected clusters. Once Submariner is installed on a cluster equipped with the appropriate credentials for the Broker, it facilitates the exchange of Cluster and Endpoint objects between clusters through mechanisms such as push, pull, and watching, thereby establishing connections and routes to other clusters. It's crucial that the worker node IP addresses on all connected clusters reside outside of the Pod and Service CIDR ranges. By ensuring these configurations, teams can maximize the benefits of multi-cluster setups.
API Access
Has API
API Access
Has API
Pricing Details
No price information available.
Free Trial
Free Version
Pricing Details
No price information available.
Free Trial
Free Version
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Vendor Details
Company Name
NetApp
Founded
1992
Country
United States
Website
docs.netapp.com/us-en/ontap/concepts/mcc-config-concept.html
Vendor Details
Company Name
Submariner
Website
submariner.io