[{"data":1,"prerenderedAt":349},["ShallowReactive",2],{"docs-nav":3,"docs-page-\u002Fdocs\u002Fdata-clone\u002Foverview":133},[4,27,53,68,83,98,117],{"slug":5,"label":6,"pages":7},"get-started","Get Started",[8,12,17,22],{"path":9,"title":10,"order":11},"\u002Fdocs","Welcome",0,{"path":13,"title":14,"navTitle":15,"order":16},"\u002Fdocs\u002Fget-started\u002Fquickstart","Quickstart",null,1,{"path":18,"title":19,"navTitle":20,"order":21},"\u002Fdocs\u002Fget-started\u002Fconnect-to-a-cluster","Connecting to a Kafka Cluster","Clusters",2,{"path":23,"title":24,"navTitle":25,"order":26},"\u002Fdocs\u002Fget-started\u002Flicense","Licensing and Activation","License",3,{"slug":28,"label":29,"pages":30},"console","Console",[31,35,39,43,48],{"path":32,"title":33,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsole\u002Foverview","Produce and Consume Messages in the Kafka Console","Overview",{"path":36,"title":37,"navTitle":38,"order":21},"\u002Fdocs\u002Fconsole\u002Fconsuming-messages","Kafka Consumer: Reading Messages from a Topic","Consuming",{"path":40,"title":41,"navTitle":42,"order":26},"\u002Fdocs\u002Fconsole\u002Fdecoding-messages","Decoding Kafka Avro and Protobuf Messages","Decoding",{"path":44,"title":45,"navTitle":46,"order":47},"\u002Fdocs\u002Fconsole\u002Fproducing-messages","Kafka Producer: Sending Messages to a Topic","Producing",4,{"path":49,"title":50,"navTitle":51,"order":52},"\u002Fdocs\u002Fconsole\u002Freplay-forward-and-export","Replay and Export Kafka Messages","Replay & export",5,{"slug":54,"label":55,"pages":56},"topics","Topics",[57,60,64],{"path":58,"title":59,"navTitle":34,"order":16},"\u002Fdocs\u002Ftopics\u002Foverview","Browse and Inspect Kafka Topics",{"path":61,"title":62,"navTitle":63,"order":21},"\u002Fdocs\u002Ftopics\u002Fcreate-a-topic","Create a Kafka Topic: Partitions, Replication, and Retention","Create a topic",{"path":65,"title":66,"navTitle":67,"order":26},"\u002Fdocs\u002Ftopics\u002Fpartitions-and-records","Adding Kafka Partitions and Deleting Records","Partitions & records",{"slug":69,"label":70,"pages":71},"schema-registry","Schema Registry",[72,75,79],{"path":73,"title":74,"navTitle":34,"order":16},"\u002Fdocs\u002Fschema-registry\u002Foverview","Browse Kafka Schema Registry Subjects and Versions",{"path":76,"title":77,"navTitle":78,"order":21},"\u002Fdocs\u002Fschema-registry\u002Fnew-versions","Register Kafka Schemas and Publish New Versions","New versions",{"path":80,"title":81,"navTitle":82,"order":26},"\u002Fdocs\u002Fschema-registry\u002Fmock-and-lab","Avro Schema Validator and Mock Data Generator","Mock & Lab",{"slug":84,"label":85,"pages":86},"consumer-groups","Consumer Groups",[87,90,94],{"path":88,"title":89,"navTitle":34,"order":16},"\u002Fdocs\u002Fconsumer-groups\u002Foverview","Browse Kafka Consumer Groups and Assignments",{"path":91,"title":92,"navTitle":93,"order":21},"\u002Fdocs\u002Fconsumer-groups\u002Flag","Monitor Kafka Consumer Lag","Lag",{"path":95,"title":96,"navTitle":97,"order":26},"\u002Fdocs\u002Fconsumer-groups\u002Freset-offsets","Reset Kafka Consumer Group Offsets","Reset offsets",{"slug":99,"label":100,"pages":101},"data-clone","Data Clone",[102,105,109,113],{"path":103,"title":104,"navTitle":34,"order":16},"\u002Fdocs\u002Fdata-clone\u002Foverview","Clone Kafka Topics Between Clusters",{"path":106,"title":107,"navTitle":108,"order":21},"\u002Fdocs\u002Fdata-clone\u002Fscope-and-range","Configure Kafka Topic Cloning","Scope & range",{"path":110,"title":111,"navTitle":112,"order":26},"\u002Fdocs\u002Fdata-clone\u002Fmasking","Mask Sensitive Data in Kafka Messages","Masking",{"path":114,"title":115,"navTitle":116,"order":47},"\u002Fdocs\u002Fdata-clone\u002Fpre-flight","Run Pre-flight Checks Before a Kafka Data Clone","Pre-flight",{"slug":118,"label":119,"pages":120},"operate","Operate",[121,125,129],{"path":122,"title":123,"navTitle":124,"order":16},"\u002Fdocs\u002Foperate\u002Fbrokers","Inspect Kafka Brokers and Cluster Configuration","Brokers",{"path":126,"title":127,"navTitle":128,"order":21},"\u002Fdocs\u002Foperate\u002Faccess-control","Inspect Kafka ACLs and Simulate Access","Access Control",{"path":130,"title":131,"navTitle":132,"order":26},"\u002Fdocs\u002Foperate\u002Factivity-logs","Review Kafka Changes in Kafma Activity Logs","Activity Logs",{"id":134,"title":104,"body":135,"description":340,"extension":341,"lastUpdated":342,"meta":343,"navTitle":34,"navigation":344,"order":16,"path":103,"seo":345,"sitemap":346,"stem":347,"__hash__":348},"docs\u002Fdocs\u002Fdata-clone\u002Foverview.md",{"type":136,"value":137,"toc":327},"minimark",[138,142,145,154,159,164,167,179,183,186,194,198,201,205,212,238,241,245,248,251,255,258,275,278,282,306,310],[139,140,141],"p",{},"Data Clone copies selected Kafka topics and message ranges directly between\nconnected clusters. You do not need to export records to files and import them\nagain.",[139,143,144],{},"Use it to move only the Kafka data needed for debugging or testing. It is a\none-time, bounded copy—not a way to replicate an entire cluster continuously.",[139,146,147],{},[148,149],"img",{"alt":150,"height":151,"src":152,"width":153},"Kafma cloning a production topic to a local cluster with field masking",1564,"https:\u002F\u002Fmedia.kafma.app\u002Fchangelog\u002Fv1.0.0\u002Fhomepage-data-clone.png",2740,[155,156,158],"h2",{"id":157},"when-to-use-data-clone","When to use Data Clone",[160,161,163],"h3",{"id":162},"reproduce-a-production-issue-locally","Reproduce a production issue locally",[139,165,166],{},"Choose the affected topics and copy the message range around an incident to a\nlocal cluster. You can reproduce and investigate the problem without writing\nto production or moving data through an intermediate file.",[139,168,169,170,174,175,178],{},"Use a ",[171,172,173],"a",{"href":106},"time window or offset range"," to keep\nthe copy focused. If the records contain sensitive fields, add\n",[171,176,177],{"href":110},"masking rules"," before they reach the target.",[160,180,182],{"id":181},"build-local-test-data-from-a-remote-cluster","Build local test data from a remote cluster",[139,184,185],{},"Copy one or more topics from production or a shared test cluster instead of\nrecreating the whole Kafka environment. Kafma can create the missing topic\nstructure, register the schemas required by the selected data, and append the\nmessages.",[139,187,188,189,193],{},"Choose ",[190,191,192],"strong",{},"Structure only"," when you need the topic and schema but want to\nproduce your own test records.",[160,195,197],{"id":196},"copy-data-between-local-kafka-clusters","Copy data between local Kafka clusters",[139,199,200],{},"Move test fixtures between local clusters, or create a renamed copy in the\nsame cluster. Same-cluster clones require a prefix or suffix so the target\ncannot overlap the source topic.",[155,202,204],{"id":203},"what-kafma-can-clone","What Kafma can clone",[139,206,207,208,211],{},"The selected ",[171,209,210],{"href":106},"scope"," controls what is copied:",[213,214,215,222,232],"ul",{},[216,217,218,221],"li",{},[190,219,220],{},"Topic structure"," uses the selected partition count and copies the source\ntopic's custom settings, such as retention and cleanup policy, when Kafma\ncreates a missing target topic.",[216,223,224,227,228,231],{},[190,225,226],{},"Schemas"," are discovered and registered when the scope includes structure.\nWith ",[190,229,230],{},"Structure + Data",", Kafma registers the schema versions used by the\nselected messages. If the source and target use different Schema Registries,\neach copied message is updated to use the corresponding schema ID on the\ntarget.",[216,233,234,237],{},[190,235,236],{},"Messages"," include their keys, values, timestamps, headers, and\ntombstones. The selected range applies to each source topic.",[139,239,240],{},"Existing target topics are not reconfigured. Kafma either creates a missing\ntopic or appends to the topic already there.",[155,242,244],{"id":243},"read-only-source-and-append-only-target","Read-only source and append-only target",[139,246,247],{},"Data Clone reads the source without joining a consumer group or committing\noffsets. It does not modify source topics, messages, or schemas.",[139,249,250],{},"On the target, Kafma can create missing topics and register schemas. Copied\nrecords are only appended; Kafma never deletes or overwrites existing target\nrecords. Writing to a connection marked as production requires confirmation.",[155,252,254],{"id":253},"what-a-clone-does-not-preserve","What a clone does not preserve",[139,256,257],{},"When the scope includes data, Kafma creates new records on the target:",[213,259,260,263,266,269,272],{},[216,261,262],{},"Source offsets are not preserved; the target assigns new offsets.",[216,264,265],{},"Kafma does not preserve source partition numbers. The target producer\nrepartitions keyed records by key and assigns unkeyed records automatically.\nA record can therefore land on a different partition even when the source\nand target have the same partition count.",[216,267,268],{},"If the target has fewer brokers than the source topic's replication factor,\nKafma reduces the replication factor to the target broker count.",[216,270,271],{},"Consumer group offsets and assignments are not copied.",[216,273,274],{},"Running the same clone again does not deduplicate records. It appends another\ncopy to the target.",[139,276,277],{},"Data Clone reads a snapshot bounded by the selected range. Messages produced\nafter the snapshot boundary are not followed, so the result does not stay in\nsync with the source.",[155,279,281],{"id":280},"data-clone-workflow","Data Clone workflow",[283,284,285,288,291,294,297,303],"ol",{},[216,286,287],{},"Select the source cluster and topics.",[216,289,290],{},"Choose whether to copy structure, data, or both.",[216,292,293],{},"Limit the message range and add any masking rules.",[216,295,296],{},"Select the target, naming rule, and partition strategy.",[216,298,299,302],{},[171,300,301],{"href":114},"Run pre-flight"," and review every planned\naction.",[216,304,305],{},"Start the clone and inspect the result on the target.",[155,307,309],{"id":308},"next-steps","Next steps",[213,311,312,317,322],{},[216,313,314],{},[171,315,316],{"href":106},"Configure clone scope and range",[216,318,319],{},[171,320,321],{"href":110},"Mask sensitive Kafka data",[216,323,324],{},[171,325,326],{"href":114},"Run pre-flight checks",{"title":328,"searchDepth":26,"depth":26,"links":329},"",[330,335,336,337,338,339],{"id":157,"depth":21,"text":158,"children":331},[332,333,334],{"id":162,"depth":26,"text":163},{"id":181,"depth":26,"text":182},{"id":196,"depth":26,"text":197},{"id":203,"depth":21,"text":204},{"id":243,"depth":21,"text":244},{"id":253,"depth":21,"text":254},{"id":280,"depth":21,"text":281},{"id":308,"depth":21,"text":309},"Clone Kafka topics between clusters with Kafma. Copy selected messages, topic configuration, and schemas directly without exporting and importing files.","md","2026-08-01",{},true,{"title":104,"description":340},{"loc":103},"docs\u002Fdata-clone\u002Foverview","fvlru5KQcENMTGtHUdX9MH7BoEl2nyh6AEIpgXolNQI",1785561255662]