Migration, backup and restore made easy using Kannika
0 likes256 views
The document outlines the features and benefits of Kannika Armory, a backup and restore tool designed for event-driven architecture, emphasizing data protection and recoverability. It explains the processes for migrating data between Kafka clusters and highlights the complementary roles of Kannika Armory and cluster linking in ensuring data security and disaster recovery. Additionally, it details features such as an intuitive interface, support for plugins, and the importance of maintaining a cold backup for Kafka data.
Migration, backup and restore made easy using Kannika
- 1. @yourtwitterhandle | developer.confluent.io Starting soon… STARTING SOOOOON.. Starting sooooon ..
- 2. Goal Partners Tech Talks are webinars where subject matter experts from a Partner talk about a specific use case or project. The goal of Tech Talks is to provide best practices and applications insights, along with inspiration, and help you stay up to date about innovations in confluent ecosystem.
- 3. @yourtwitterhandle | developer.confluent.io Starting soon… STARTING SOOOOON.. Starting sooooon ..
- 5. C O N F I D E N T I A L Global Data Mesh Bridge to Cloud Cluster Linking multi cloud hybrid cloud multi region High-er Availability & Disaster Recovery edge Data Sharing between Teams, LOBs, Orgs Edge Aggregation Cluster Migration
- 6. @yourtwitterhandle | developer.confluent.io Starting soon… STARTING SOOOOON.. Starting sooooon ..
- 7. @yourtwitterhandle | developer.confluent.io Wij zijn Kannika Kannika Armory - backup en restore tool
- 8. Hi, we are Kannika! We believe in the true value of Event-Driven Architecture Our mission is to get the maximum out of EDA!
- 10. Use cases for Kannika Armory Backup & Restore ➡ Backup your events in a few steps by transferring your data to a file storage location of your choice. ➡ Increase the reliability of EDA processes in terms of data loss and downtime. In the event of a disaster, you quickly recover your data and ensure business continuity. Environment Cloning ➡ Define an important set of event data and spin up a new demo or test environment. ➡ Set up a separate cluster/environment to analyze your event data for data mining or machine learning activities. Reliable Migration ➡ Self-service: easily migrate your data to another event hub thanks to our intuitive user interface. ➡ Create a dataset once, restore multiple times. By offloading the data, the number of migrations does not affect the load on the production environment. Compliance & audit ➡ Meet regulatory standards & compliance rules concerning data retention ➡ Restore quickly for audits and compliance purposes
- 11. ✔ Intuitive interface ✔ Blazingly fast, minimal footprint ✔ Compressed data backup ✔ Backup & Restore options ✔ Open plugin system ✔ Environment cloning with schema mapping ✔ Deploy anyplace, anytime Features of Kannika Armory
- 12. Migrate from your OSK to Confluent Cloud in just a few simple steps 1. Install Kannika Armory 2. Connect your OSK cluster 3. Select and backup your selected topics to a storage of your choice 4. Connect your Confluent Cloud cluster 5. Configure the restore of your topics 6. Start migrating! Migrate with Kannika Armory
- 13. Time for a demo!
- 14. Plugins can be used to alter the behaviour of a Backup or a Restore. They allow the user to transform the data between the source and the sink, or to skip certain data. The WASI Plugins can be used for ● Repartitioning ● Data masking ● Data Filtering ● Encryption Write your own plugins or use our default plugins! Take full control over your restore process via our open Plugin system
- 15. Kafka is high-available, so why do you need a cold backup? ● Accidental deletions of topics/data by human ● Malicious deletions by human ● Cyberattacks ● Hardware failures ● Data corruption ● … This is why you need a solid copy of your Kafka data Why Kafka needs a cold backup?
- 16. How do Kannika and Cluster Linking complement each other? Kannika Focus: Data protection and recoverability. How it works: Backs up Kafka data to independent cold storage (S3, etc.). This data is isolated from the live Kafka environment & operationally decoupled Strengths: Provides a safety net against a wider range of data loss scenarios Enables point-in-time recovery with granular filtering. Useful for migrating data, creating test environments, and long-term archiving. Cluster Linking Focus: High Availability & Disaster Recovery How it works: Real-time replication of data between Kafka clusters. Strengths: Minimizes downtime and data loss in case of regional outages or cluster failures. Enables active/active scenarios for geographically distributed applications. Useful for real-time migration flows
- 17. How do Kannika and Cluster Linking complement each other? Kannika Limitations: Not a real-time solution for high availability. Restoration takes time. Cluster Linking Limitations: Doesn't protect against accidental deletions, data corruption, or malicious acts that affect both clusters. Can be complex to set up and manage, especially with schema evolution across clusters.
- 18. How do Kannika and Cluster Linking complement each other? Conclusion: How they complement each other: ● Defense in depth: Cluster Linking protects against infrastructure failures, while Kannika Armory protects against data loss at the application or operational level. ● Complete recovery: If a disaster affects both live clusters, Armory's cold backup can be used to restore data to a new environment. ● Enhanced data management: Armory facilitates data migration, testing, and cloning scenarios that are not easily achievable with just cluster linking. In essence: ● Use Cluster Linking for continuous availability and immediate failover. ● Use Kannika Armory for comprehensive data protection, recovery, and lifecycle management. Cluster linking
- 19. Want to get started with Kannika Armory? [email protected] JOIN US ON SLACK