Apache ZooKeeper, an open-source distributed coordination service initially developed by Yahoo and now managed by Apache, plays a crucial role in storing critical data, necessitating a reliable backup system. ZooKeeper databases contain persistent data, accessed via traditional CRUD activities, and ephemeral data, which is associated with state machine semantics and implies a specific state. In production, ZooKeeper is deployed on multiple processes, ensuring consistency by requiring that a majority of processes receive writes. The data stored can be transient, a source of truth, or stateful, with ephemeral nodes tied to client sessions that expire when the sessions do. Challenges in backing up and restoring ZooKeeper arise from its transient and stateful data, as it lacks built-in support for these processes. Improper restoration can lead to inconsistencies in the distributed state machine, as exemplified by scenarios where restored ephemeral nodes conflict with current client states. Recommendations for ZooKeeper backups include copying transaction and snapshot logs, filtering out ephemeral node transactions to prevent data inconsistencies, and ideally closing all clients before restoration to effectively manage session expirations.