Migration Guide | Geode Database

This comprehensive guide covers all aspects of migrating to and within Geode: version upgrades, data migration from other databases, backup and restore procedures, zero-downtime strategies, and best practices for production environments. <h3 id="overview" class="position-relative d-flex align-items-center group"> Overview <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="overview" aria-haspopup="dialog" aria-label="Share link: Overview"> Share link </button> </h3><div id="headingShareModal" class="heading-share-modal" role="dialog" aria-modal="true" aria-labelledby="headingShareTitle" hidden> <div class="hsm-dialog" role="document"> <div class="hsm-header"> <h2 id="headingShareTitle" class="h6 mb-0 fw-bold">Share this section</h2> <button type="button" class="hsm-close" aria-label="Close"> </button> </div> <div class="hsm-body"> <label for="headingShareInput" class="form-label small text-muted mb-1 text-uppercase fw-bold" style="font-size: 0.7rem; letter-spacing: 0.5px;">Permalink</label> <div class="input-group mb-4 hsm-url-group"> <input id="headingShareInput" type="text" class="form-control font-monospace" readonly aria-readonly="true" style="font-size: 0.85rem;" /> <button class="btn btn-primary hsm-copy" type="button" aria-label="Copy" title="Copy"> </button> </div> <div class="small fw-bold mb-2 text-muted text-uppercase" style="font-size: 0.7rem; letter-spacing: 0.5px;">Share via</div> <div class="hsm-share-grid"> <a id="share-twitter" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Twitter </a> <a id="share-linkedin" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> LinkedIn </a> <a id="share-facebook" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Facebook </a> </div> </div> </div> </div> <style> .heading-share-modal { position: fixed; inset: 0; display: flex; justify-content: center; align-items: center; background: rgba(0, 0, 0, 0.6); z-index: 1050; padding: 1rem; backdrop-filter: blur(4px); -webkit-backdrop-filter: blur(4px); } .heading-share-modal[hidden] { display: none !important; } .hsm-dialog { max-width: 420px; width: 100%; background: var(--bs-body-bg, #fff); color: var(--bs-body-color, #212529); border: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); border-radius: 1rem; box-shadow: 0 25px 50px -12px rgba(0, 0, 0, 0.25); overflow: hidden; animation: hsm-fade-in 0.2s ease-out; } @keyframes hsm-fade-in { from { opacity: 0; transform: scale(0.95); } to { opacity: 1; transform: scale(1); } } [data-bs-theme="dark"] .hsm-dialog { background: #1e293b; border-color: rgba(255,255,255,0.1); color: #f8f9fa; } .hsm-header { display: flex; justify-content: space-between; align-items: center; padding: 1rem 1.5rem; border-bottom: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); background: rgba(0,0,0,0.02); } [data-bs-theme="dark"] .hsm-header { background: rgba(255,255,255,0.02); border-color: rgba(255,255,255,0.1); } .hsm-close { background: transparent; border: none; color: inherit; opacity: 0.5; padding: 0.25rem 0.5rem; border-radius: 0.25rem; font-size: 1.2rem; line-height: 1; transition: opacity 0.2s; } .hsm-close:hover { opacity: 1; } .hsm-body { padding: 1.5rem; } .hsm-url-group { display: flex !important; align-items: stretch; } .hsm-url-group .form-control { flex: 1; min-width: 0; margin: 0; background: var(--bs-secondary-bg, #f8f9fa); border-color: var(--bs-border-color, #dee2e6); border-top-right-radius: 0; border-bottom-right-radius: 0; height: 42px; } .hsm-url-group .btn { flex: 0 0 auto; margin: 0; margin-left: -1px; border-top-left-radius: 0; border-bottom-left-radius: 0; height: 42px; display: flex; align-items: center; justify-content: center; padding: 0 1.25rem; z-index: 2; } [data-bs-theme="dark"] .hsm-url-group .form-control { background: #0f172a; border-color: #334155; color: #e2e8f0; } .hsm-share-grid { display: flex; flex-direction: column; gap: 0.5rem; } .hsm-share-grid .btn { display: flex; align-items: center; justify-content: center; font-size: 0.9rem; padding: 0.6rem; border-color: var(--bs-border-color); width: 100%; } [data-bs-theme="dark"] .hsm-share-grid .btn { color: #e2e8f0; border-color: #475569; } [data-bs-theme="dark"] .hsm-share-grid .btn:hover { background: #334155; border-color: #cbd5e1; } </style> <script> (function(){ const modal = document.getElementById('headingShareModal'); if(!modal) return; const input = modal.querySelector('#headingShareInput'); const copyBtn = modal.querySelector('.hsm-copy'); const twitter = modal.querySelector('#share-twitter'); const linkedin = modal.querySelector('#share-linkedin'); const facebook = modal.querySelector('#share-facebook'); const closeBtn = modal.querySelector('.hsm-close'); let lastFocus=null; let trapBound=false; function buildUrl(id){ return window.location.origin + window.location.pathname + '#' + id; } function isOpen(){ return !modal.hasAttribute('hidden'); } function hydrate(id){ const url=buildUrl(id); input.value=url; const enc=encodeURIComponent(url); const text=encodeURIComponent(document.title); if(twitter) twitter.href=`https://twitter.com/intent/tweet?url=${enc}&text=${text}`; if(linkedin) linkedin.href=`https://www.linkedin.com/sharing/share-offsite/?url=${enc}`; if(facebook) facebook.href=`https://www.facebook.com/sharer/sharer.php?u=${enc}`; } function openModal(id){ lastFocus=document.activeElement; hydrate(id); if(!isOpen()){ modal.removeAttribute('hidden'); } requestAnimationFrame(()=>{ input.focus(); }); trapFocus(); } function closeModal(){ if(!isOpen()) return; modal.setAttribute('hidden',''); if(lastFocus && typeof lastFocus.focus==='function') lastFocus.focus(); } function copyCurrent(){ try{ navigator.clipboard.writeText(input.value).then(()=>feedback(true),()=>fallback()); } catch(e){ fallback(); } } function fallback(){ input.select(); try{ document.execCommand('copy'); feedback(true);}catch(e){ feedback(false);} } function feedback(ok){ if(!copyBtn) return; const icon=copyBtn.querySelector('i'); if(!icon) return; const prev=copyBtn.getAttribute('data-prev')||icon.className; if(!copyBtn.getAttribute('data-prev')) copyBtn.setAttribute('data-prev',prev); icon.className= ok ? 'fa-duotone fa-clipboard-check':'fa-duotone fa-circle-exclamation'; setTimeout(()=>{ icon.className=prev; },1800); } function handleShareClick(e){ e.preventDefault(); const btn=e.currentTarget; const id=btn.getAttribute('data-share-target'); if(id) openModal(id); } function bindShareButtons(){ document.querySelectorAll('.h-share').forEach(btn=>{ if(!btn.dataset.hShareBound){ btn.addEventListener('click', handleShareClick); btn.dataset.hShareBound='1'; } }); } bindShareButtons(); if(document.readyState==='loading'){ document.addEventListener('DOMContentLoaded', bindShareButtons); } else { requestAnimationFrame(bindShareButtons); } document.addEventListener('click', function(e){ const shareBtn=e.target.closest && e.target.closest('.h-share'); if(shareBtn && !shareBtn.dataset.hShareBound){ handleShareClick.call(shareBtn, e); } }, true); document.addEventListener('click', e=>{ if(e.target===modal) closeModal(); if(e.target.closest && e.target.closest('.hsm-close')){ e.preventDefault(); closeModal(); } if(copyBtn && (e.target===copyBtn || (e.target.closest && e.target.closest('.hsm-copy')))) { e.preventDefault(); copyCurrent(); } }); document.addEventListener('keydown', e=>{ if(e.key==='Escape' && isOpen()) closeModal(); }); function trapFocus(){ if(trapBound) return; trapBound=true; modal.addEventListener('keydown', f=>{ if(f.key==='Tab' && isOpen()){ const focusable=[...modal.querySelectorAll('a[href],button,input,textarea,select,[tabindex]:not([tabindex="-1"])')].filter(el=>!el.hasAttribute('disabled')); if(!focusable.length) return; const first=focusable[0]; const last=focusable[focusable.length-1]; if(f.shiftKey && document.activeElement===first){ f.preventDefault(); last.focus(); } else if(!f.shiftKey && document.activeElement===last){ f.preventDefault(); first.focus(); } } }); } if(closeBtn) closeBtn.addEventListener('click', e=>{ e.preventDefault(); closeModal(); }); })(); </script>Geode provides multiple migration paths depending on your source system and requirements: <ul> <li>Version Upgrades: Migrate between Geode versions with backward compatibility</li> <li>Database Migrations: Move data from Neo4j, JanusGraph, or other graph databases</li> <li>Backup & Restore: Use S3-compatible cloud storage for disaster recovery</li> <li>Zero-Downtime Migrations: Maintain service availability during upgrades</li> <li>Schema Evolution: Safely modify schemas in production systems</li> </ul> <h3 id="version-upgrade-guide" class="position-relative d-flex align-items-center group"> Version Upgrade Guide <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="version-upgrade-guide" aria-haspopup="dialog" aria-label="Share link: Version Upgrade Guide"> Share link </button> </h3> <h4 id="current-version-status" class="position-relative d-flex align-items-center group"> Current Version Status <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="current-version-status" aria-haspopup="dialog" aria-label="Share link: Current Version Status"> Share link </button> </h4>Geode v0.2.18 (March 30, 2026) - Current stable release <ul> <li>100% GQL compliance (ISO/IEC 39075:2024)</li> <li>Current stable line for production deployments</li> <li>Follow the release notes for post-<code>v0.2.18</code> <code>main</code> fixes before adopting unreleased builds</li> </ul> <h4 id="pre-upgrade-checklist" class="position-relative d-flex align-items-center group"> Pre-Upgrade Checklist <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="pre-upgrade-checklist" aria-haspopup="dialog" aria-label="Share link: Pre-Upgrade Checklist"> Share link </button> </h4>Before upgrading any Geode instance, complete this checklist: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># 1. Check current version geode --version # 2. Create full backup geode backup --dest s3://my-bucket/backups --mode full # 3. Verify backup integrity geode backup --dest s3://my-bucket/backups --list # 4. Document current configuration cp /etc/geode/geode.yaml /etc/geode/geode.yaml.backup env | grep GEODE_ > geode-env.backup # 5. Test queries in new version (staging environment first) geode query "MATCH (n) RETURN count(n)" # 6. Review release notes for breaking changes # Check: https://geodedb.com/docs/release-notes/ </code></pre></div> <h4 id="in-place-upgrade-procedure" class="position-relative d-flex align-items-center group"> In-Place Upgrade Procedure <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="in-place-upgrade-procedure" aria-haspopup="dialog" aria-label="Share link: In-Place Upgrade Procedure"> Share link </button> </h4>Upgrade existing Geode installation without data migration: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># 1. Stop current server gracefully systemctl stop geode # Or: pkill -TERM geode # 2. Backup data directory tar -czf /backup/geode-data-$(date +%Y%m%d).tar.gz /var/lib/geode/data # 3. Install new version (build from source) git clone https://github.com/codeprosorg/geode /tmp/geode-upgrade cd /tmp/geode-upgrade make build install -m 0755 ./zig-out/bin/geode /usr/local/bin/geode # 4. Verify new version geode --version # 5. Start server with existing data systemctl start geode # 6. Verify server health geode query "RETURN 1 AS health_check" # 7. Monitor logs for errors journalctl -u geode -f </code></pre></div> <h4 id="rolling-upgrade-distributed-clusters" class="position-relative d-flex align-items-center group"> Rolling Upgrade (Distributed Clusters) <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="rolling-upgrade-distributed-clusters" aria-haspopup="dialog" aria-label="Share link: Rolling Upgrade (Distributed Clusters)"> Share link </button> </h4>Upgrade cluster nodes with zero downtime: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Build new version locally (run once) git clone https://github.com/codeprosorg/geode /tmp/geode-upgrade cd /tmp/geode-upgrade make build GEODE_BIN=/tmp/geode-upgrade/zig-out/bin/geode # 1. Upgrade secondary nodes first (one at a time) for node in node2 node3 node4; do echo "Upgrading $node..." # Stop node ssh $node "systemctl stop geode" # Install new version scp "$GEODE_BIN" "$node:/usr/local/bin/geode" # Start node ssh $node "systemctl start geode" # Verify health ssh $node "geode query 'RETURN 1 AS health'" # Wait for node to stabilize sleep 30 done # 2. Upgrade primary node last ssh node1 "systemctl stop geode" scp "$GEODE_BIN" "node1:/usr/local/bin/geode" ssh node1 "systemctl start geode" # 3. Verify cluster health geode query "MATCH (n) RETURN count(n)" </code></pre></div> <h4 id="configuration-migration" class="position-relative d-flex align-items-center group"> Configuration Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="configuration-migration" aria-haspopup="dialog" aria-label="Share link: Configuration Migration"> Share link </button> </h4>Migrate configuration between versions: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"># Old configuration (v0.1.x) server: listen: '0.0.0.0:3141' data_dir: '/var/lib/geode' # New configuration (v0.1.x) - backward compatible server: listen: '0.0.0.0:3141' data_dir: '/var/lib/geode' max_connections: 50000 # New option tls: cert: '/etc/letsencrypt/live/geode.example.com/fullchain.pem' key: '/etc/letsencrypt/live/geode.example.com/privkey.pem' auto_generate: false # New: secure-by-default security: auth_enabled: true # New: enabled-by-default (was optional) storage: page_size: 8192 cache_size: '1GB' tde_enabled: true # New: transparent data encryption </code></pre></div>Breaking Changes (v0.1.x → v0.1.x): <ul> <li>Authentication now enabled by default (was optional)</li> <li>TLS auto-generation disabled by default (use proper certificates)</li> <li>Hardcoded credentials removed (use environment variables)</li> </ul> <h3 id="migrating-from-other-graph-databases" class="position-relative d-flex align-items-center group"> Migrating from Other Graph Databases <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="migrating-from-other-graph-databases" aria-haspopup="dialog" aria-label="Share link: Migrating from Other Graph Databases"> Share link </button> </h3> <h4 id="neo4j-to-geode-migration" class="position-relative d-flex align-items-center group"> Neo4j to Geode Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="neo4j-to-geode-migration" aria-haspopup="dialog" aria-label="Share link: Neo4j to Geode Migration"> Share link </button> </h4>Migrate data from Neo4j to Geode using export/import strategy: <h5 id="step-1-export-from-neo4j" class="position-relative d-flex align-items-center group"> Step 1: Export from Neo4j <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-1-export-from-neo4j" aria-haspopup="dialog" aria-label="Share link: Step 1: Export from Neo4j"> Share link </button> </h5><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gdscript3" data-lang="gdscript3">// Export Neo4j data to CSV CALL apoc.export.csv.all("neo4j-export.csv", {}); // Or use neo4j-admin dump neo4j-admin database dump neo4j --to=/backups/neo4j.dump </code></pre></div> <h5 id="step-2-convert-cypher-to-gql" class="position-relative d-flex align-items-center group"> Step 2: Convert Cypher to GQL <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-2-convert-cypher-to-gql" aria-haspopup="dialog" aria-label="Share link: Step 2: Convert Cypher to GQL"> Share link </button> </h5>Neo4j uses Cypher; Geode uses ISO GQL (mostly compatible): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Neo4j Cypher (mostly compatible) CREATE (alice:Person {name: 'Alice', age: 30}) CREATE (bob:Person {name: 'Bob', age: 25}) CREATE (alice)-[:KNOWS {since: 2020}]->(bob) -- Geode GQL (identical syntax for basic operations) CREATE (alice:Person {name: 'Alice', age: 30}) CREATE (bob:Person {name: 'Bob', age: 25}) CREATE (alice)-[:KNOWS {since: 2020}]->(bob) -- Key differences: -- 1. Neo4j MERGE → Geode INSERT ... ON CONFLICT -- 2. Neo4j FOREACH → Geode supports standard loops -- 3. Neo4j apoc functions → Geode built-in GQL functions </code></pre></div> <h5 id="step-3-import-to-geode" class="position-relative d-flex align-items-center group"> Step 3: Import to Geode <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-3-import-to-geode" aria-haspopup="dialog" aria-label="Share link: Step 3: Import to Geode"> Share link </button> </h5>Create import script for bulk loading: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # import-neo4j-data.sh # Start Geode server geode serve --listen 0.0.0.0:3141 & GEODE_PID=$! # Wait for server to start sleep 5 # Import nodes while IFS=',' read -r id name age; do geode query "CREATE (p:Person {id: $id, name: '$name', age: $age})" done < nodes.csv # Import relationships while IFS=',' read -r from_id to_id since; do geode query " MATCH (a:Person {id: $from_id}), (b:Person {id: $to_id}) CREATE (a)-[:KNOWS {since: $since}]->(b) " done < relationships.csv # Stop server kill $GEODE_PID </code></pre></div> <h5 id="step-4-verify-migration" class="position-relative d-flex align-items-center group"> Step 4: Verify Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="step-4-verify-migration" aria-haspopup="dialog" aria-label="Share link: Step 4: Verify Migration"> Share link </button> </h5><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Compare counts MATCH (n) RETURN count(n) AS node_count; MATCH ()-[r]->() RETURN count(r) AS relationship_count; -- Verify specific patterns MATCH (p:Person)-[:KNOWS]->(friend:Person) RETURN p.name, count(friend) AS friend_count ORDER BY friend_count DESC LIMIT 10; </code></pre></div> <h4 id="janusgraph-to-geode-migration" class="position-relative d-flex align-items-center group"> JanusGraph to Geode Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="janusgraph-to-geode-migration" aria-haspopup="dialog" aria-label="Share link: JanusGraph to Geode Migration"> Share link </button> </h4>JanusGraph uses Gremlin; convert to GQL: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-groovy" data-lang="groovy">// JanusGraph Gremlin g.addV('Person').property('name', 'Alice').property('age', 30) // Geode GQL equivalent CREATE (p:Person {name: 'Alice', age: 30}) </code></pre></div>Gremlin to GQL Mapping: <table> <thead> <tr> <th>Gremlin</th> <th>GQL</th> </tr> </thead> <tbody> <tr> <td><code>g.addV('Person')</code></td> <td><code>CREATE (p:Person {...})</code></td> </tr> <tr> <td><code>g.V().hasLabel('Person')</code></td> <td><code>MATCH (p:Person) RETURN p</code></td> </tr> <tr> <td><code>g.V().has('name', 'Alice')</code></td> <td><code>MATCH (p {name: 'Alice'}) RETURN p</code></td> </tr> <tr> <td><code>g.V().outE('KNOWS').inV()</code></td> <td><code>MATCH (a)-[:KNOWS]->(b) RETURN b</code></td> </tr> <tr> <td><code>g.V().count()</code></td> <td><code>MATCH (n) RETURN count(n)</code></td> </tr> </tbody> </table> <h4 id="tigergraph-to-geode-migration" class="position-relative d-flex align-items-center group"> TigerGraph to Geode Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="tigergraph-to-geode-migration" aria-haspopup="dialog" aria-label="Share link: TigerGraph to Geode Migration"> Share link </button> </h4>Export TigerGraph data using GSQL: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sql" data-lang="sql">-- TigerGraph GSQL export USE GRAPH MyGraph CREATE QUERY export_data() FOR GRAPH MyGraph { PRINT nodes TO "/tmp/nodes.csv"; PRINT edges TO "/tmp/edges.csv"; } INSTALL QUERY export_data RUN QUERY export_data() -- Then import to Geode using similar CSV import strategy </code></pre></div> <h3 id="backup-and-restore" class="position-relative d-flex align-items-center group"> Backup and Restore <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="backup-and-restore" aria-haspopup="dialog" aria-label="Share link: Backup and Restore"> Share link </button> </h3> <h4 id="s3-cloud-backup" class="position-relative d-flex align-items-center group"> S3 Cloud Backup <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="s3-cloud-backup" aria-haspopup="dialog" aria-label="Share link: S3 Cloud Backup"> Share link </button> </h4>Geode supports S3-compatible cloud storage for backups: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Configure S3 credentials export AWS_ACCESS_KEY_ID=your-access-key export AWS_SECRET_ACCESS_KEY=your-secret-key export AWS_REGION=us-east-1 # Full backup geode backup \ --dest s3://my-bucket/geode-backups \ --mode full \ --compression gzip # Output: # Backup ID: 1738012345 # Size: 2.3 GB (compressed) # Duration: 45s # Incremental backup (delta from last full backup) geode backup \ --dest s3://my-bucket/geode-backups \ --mode incremental \ --parent 1738012345 # List all backups geode backup --dest s3://my-bucket/geode-backups --list # Output: # Backup ID Type Size Timestamp # 1738012345 full 2.3 GB 2026-01-23 10:00:00 # 1738013456 incremental 156 MB 2026-01-23 11:00:00 # 1738014567 incremental 89 MB 2026-01-23 12:00:00 </code></pre></div> <h4 id="digital-ocean-spaces-backup" class="position-relative d-flex align-items-center group"> Digital Ocean Spaces Backup <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="digital-ocean-spaces-backup" aria-haspopup="dialog" aria-label="Share link: Digital Ocean Spaces Backup"> Share link </button> </h4>Digital Ocean Spaces is S3-compatible: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Configure Digital Ocean credentials export AWS_ACCESS_KEY_ID=your-do-spaces-key export AWS_SECRET_ACCESS_KEY=your-do-spaces-secret export AWS_ENDPOINT_URL=https://nyc3.digitaloceanspaces.com # Backup to Digital Ocean Spaces geode backup \ --dest s3://my-space/geode-backups \ --mode full \ --compression gzip </code></pre></div> <h4 id="point-in-time-recovery-pitr" class="position-relative d-flex align-items-center group"> Point-in-Time Recovery (PITR) <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="point-in-time-recovery-pitr" aria-haspopup="dialog" aria-label="Share link: Point-in-Time Recovery (PITR)"> Share link </button> </h4>Restore database to specific point in time: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Restore to specific backup geode restore \ --source s3://my-bucket/geode-backups \ --backup-id 1738012345 \ --target /var/lib/geode/data # Point-in-time recovery (arbitrary timestamp) geode restore \ --source s3://my-bucket/geode-backups \ --backup-id 1738012345 \ --target /var/lib/geode/data \ --pitr-timestamp "2026-01-23 10:30:00" # Process: # 1. Restore base backup (full backup 1738012345) # 2. Apply WAL segments up to specified timestamp # 3. Stop at exact recovery point </code></pre></div> <h4 id="automated-backup-strategy" class="position-relative d-flex align-items-center group"> Automated Backup Strategy <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="automated-backup-strategy" aria-haspopup="dialog" aria-label="Share link: Automated Backup Strategy"> Share link </button> </h4>Set up automated backups with cron: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # /usr/local/bin/geode-backup.sh # Configuration BUCKET="s3://my-bucket/geode-backups" RETENTION_DAYS=30 # Full backup on Sunday if [ $(date +%u) -eq 7 ]; then BACKUP_ID=$(geode backup --dest $BUCKET --mode full --compression gzip | grep "Backup ID" | awk '{print $3}') echo $BACKUP_ID > /var/lib/geode/last-full-backup else # Incremental backup on weekdays PARENT=$(cat /var/lib/geode/last-full-backup) geode backup --dest $BUCKET --mode incremental --parent $PARENT --compression gzip fi # Delete backups older than retention period geode backup --dest $BUCKET --prune --older-than-days $RETENTION_DAYS # Add to crontab # 0 2 * * * /usr/local/bin/geode-backup.sh >> /var/log/geode-backup.log 2>&1 </code></pre></div> <h3 id="zero-downtime-migration-strategies" class="position-relative d-flex align-items-center group"> Zero-Downtime Migration Strategies <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="zero-downtime-migration-strategies" aria-haspopup="dialog" aria-label="Share link: Zero-Downtime Migration Strategies"> Share link </button> </h3> <h4 id="blue-green-deployment" class="position-relative d-flex align-items-center group"> Blue-Green Deployment <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="blue-green-deployment" aria-haspopup="dialog" aria-label="Share link: Blue-Green Deployment"> Share link </button> </h4>Maintain two identical environments for zero-downtime upgrades: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Setup: # - Blue environment: production (v0.1.x) # - Green environment: staging (v0.1.x) # Step 1: Replicate data to green environment geode backup --dest s3://my-bucket/migration --mode full --source blue geode restore --source s3://my-bucket/migration --target green # Step 2: Enable continuous replication (CDC) # Configure CDC webhook from blue to green cat > cdc-config.yaml <<EOF webhooks: - name: green-replica endpoint: https://green.example.com/cdc retry: max_attempts: 5 base_delay_ms: 100 EOF # Step 3: Monitor replication lag watch 'geode query "MATCH (n) RETURN count(n)" --host blue' watch 'geode query "MATCH (n) RETURN count(n)" --host green' # Step 4: Switch traffic to green (update DNS/load balancer) # AWS Route53 weighted routing aws route53 change-resource-record-sets \ --hosted-zone-id Z1234567890ABC \ --change-batch file://switch-to-green.json # Step 5: Monitor green environment # If issues: switch back to blue (instant rollback) # If stable: decommission blue environment </code></pre></div> <h4 id="read-replica-migration" class="position-relative d-flex align-items-center group"> Read Replica Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="read-replica-migration" aria-haspopup="dialog" aria-label="Share link: Read Replica Migration"> Share link </button> </h4>Use read replicas to minimize downtime: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Build new version locally (run once) git clone https://github.com/codeprosorg/geode /tmp/geode-upgrade cd /tmp/geode-upgrade make build GEODE_BIN=/tmp/geode-upgrade/zig-out/bin/geode # Step 1: Create read replica geode replica create \ --primary geode-primary.example.com:3141 \ --replica geode-replica.example.com:3141 # Step 2: Upgrade replica to new version ssh geode-replica "systemctl stop geode" scp "$GEODE_BIN" "geode-replica:/usr/local/bin/geode" ssh geode-replica "systemctl start geode" # Step 3: Test read queries on replica geode query "MATCH (n) RETURN count(n)" --host geode-replica.example.com # Step 4: Promote replica to primary geode replica promote --host geode-replica.example.com:3141 # Step 5: Upgrade old primary (now secondary) ssh geode-primary "systemctl stop geode" scp "$GEODE_BIN" "geode-primary:/usr/local/bin/geode" ssh geode-primary "systemctl start geode" </code></pre></div> <h4 id="shadow-traffic-migration" class="position-relative d-flex align-items-center group"> Shadow Traffic Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="shadow-traffic-migration" aria-haspopup="dialog" aria-label="Share link: Shadow Traffic Migration"> Share link </button> </h4>Replicate production traffic to new version for validation: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Use HAProxy to mirror traffic to both environments # /etc/haproxy/haproxy.cfg frontend geode_frontend bind *:3141 default_backend geode_primary backend geode_primary server primary geode-v17.example.com:3141 check # Mirror traffic to new version (no client impact) server shadow geode-v18.example.com:3141 check backup # Monitor shadow environment for errors tail -f /var/log/geode-v18/error.log # Compare query performance diff <(geode query "EXPLAIN MATCH (n) RETURN n" --host v17) \ <(geode query "EXPLAIN MATCH (n) RETURN n" --host v18) </code></pre></div> <h3 id="schema-evolution" class="position-relative d-flex align-items-center group"> Schema Evolution <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="schema-evolution" aria-haspopup="dialog" aria-label="Share link: Schema Evolution"> Share link </button> </h3> <h4 id="adding-new-properties" class="position-relative d-flex align-items-center group"> Adding New Properties <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="adding-new-properties" aria-haspopup="dialog" aria-label="Share link: Adding New Properties"> Share link </button> </h4>Add properties to existing nodes without downtime: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add optional property (backward compatible) MATCH (p:Person) SET p.email = null; -- Initialize with null -- Backfill property values MATCH (p:Person) WHERE p.email IS NULL SET p.email = p.name + '@example.com'; -- Example backfill logic -- Add constraint after backfilling CREATE CONSTRAINT person_email_unique ON (p:Person) ASSERT p.email IS UNIQUE; </code></pre></div> <h4 id="adding-new-labels" class="position-relative d-flex align-items-center group"> Adding New Labels <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="adding-new-labels" aria-haspopup="dialog" aria-label="Share link: Adding New Labels"> Share link </button> </h4>Add labels to existing nodes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add secondary label to nodes MATCH (p:Person) WHERE p.age >= 18 SET p:Adult; -- Query with new label MATCH (a:Adult) RETURN a.name, a.age; </code></pre></div> <h4 id="modifying-relationships" class="position-relative d-flex align-items-center group"> Modifying Relationships <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="modifying-relationships" aria-haspopup="dialog" aria-label="Share link: Modifying Relationships"> Share link </button> </h4>Transform relationship structures safely: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Old structure: (Person)-[:FRIEND]->(Person) -- New structure: (Person)-[:KNOWS {type: 'friend'}]->(Person) -- Migration query (idempotent) MATCH (a:Person)-[old:FRIEND]->(b:Person) WHERE NOT EXISTS((a)-[:KNOWS]->(b)) CREATE (a)-[new:KNOWS {type: 'friend', since: old.since}]->(b); -- Verify migration MATCH (a)-[:KNOWS]->(b) RETURN count(*) AS new_count; MATCH (a)-[:FRIEND]->(b) RETURN count(*) AS old_count; -- Should match new_count -- Remove old relationships after verification MATCH (a)-[old:FRIEND]->(b) DELETE old; </code></pre></div> <h4 id="adding-indexes" class="position-relative d-flex align-items-center group"> Adding Indexes <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="adding-indexes" aria-haspopup="dialog" aria-label="Share link: Adding Indexes"> Share link </button> </h4>Create indexes on existing data without blocking writes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create index (non-blocking in Geode) CREATE INDEX person_email ON Person(email); -- Verify index usage EXPLAIN MATCH (p:Person) WHERE p.email = '[email protected]' RETURN p; -- Output should show "Index Scan" instead of "Sequential Scan" </code></pre></div> <h3 id="data-validation" class="position-relative d-flex align-items-center group"> Data Validation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="data-validation" aria-haspopup="dialog" aria-label="Share link: Data Validation"> Share link </button> </h3> <h4 id="pre-migration-validation" class="position-relative d-flex align-items-center group"> Pre-Migration Validation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="pre-migration-validation" aria-haspopup="dialog" aria-label="Share link: Pre-Migration Validation"> Share link </button> </h4>Validate source data before migration: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Check for orphaned relationships MATCH (a)-[r]->(b) WHERE a IS NULL OR b IS NULL RETURN count(r) AS orphaned_relationships; -- Check for duplicate nodes (by business key) MATCH (p:Person) WITH p.email AS email, count(*) AS count WHERE count > 1 RETURN email, count; -- Check for invalid property values MATCH (p:Person) WHERE p.age IS NULL OR p.age < 0 OR p.age > 150 RETURN p.id, p.age; </code></pre></div> <h4 id="post-migration-validation" class="position-relative d-flex align-items-center group"> Post-Migration Validation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="post-migration-validation" aria-haspopup="dialog" aria-label="Share link: Post-Migration Validation"> Share link </button> </h4>Verify data integrity after migration: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Compare node counts MATCH (n) RETURN labels(n) AS label, count(n) AS count ORDER BY label; -- Compare relationship counts MATCH ()-[r]->() RETURN type(r) AS relationship_type, count(r) AS count ORDER BY relationship_type; -- Verify critical queries return expected results MATCH (p:Person)-[:KNOWS]->(friend) WHERE p.name = 'Alice' RETURN friend.name ORDER BY friend.name; -- Check index integrity SHOW INDEXES; </code></pre></div> <h3 id="performance-optimization-during-migration" class="position-relative d-flex align-items-center group"> Performance Optimization During Migration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="performance-optimization-during-migration" aria-haspopup="dialog" aria-label="Share link: Performance Optimization During Migration"> Share link </button> </h3> <h4 id="bulk-loading-best-practices" class="position-relative d-flex align-items-center group"> Bulk Loading Best Practices <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="bulk-loading-best-practices" aria-haspopup="dialog" aria-label="Share link: Bulk Loading Best Practices"> Share link </button> </h4>Optimize bulk data imports: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # Bulk import with batching BATCH_SIZE=1000 TOTAL_ROWS=$(wc -l < nodes.csv) # Disable constraints temporarily for faster imports geode query "ALTER DATABASE DISABLE CONSTRAINTS" # Import in batches for ((i=0; i<$TOTAL_ROWS; i+=$BATCH_SIZE)); do echo "Processing batch $((i/$BATCH_SIZE + 1))..." tail -n +$((i+1)) nodes.csv | head -n $BATCH_SIZE | while IFS=',' read -r id name age; do echo "CREATE (p:Person {id: $id, name: '$name', age: $age})" done | geode query --batch # Progress reporting echo "Imported $((i+$BATCH_SIZE)) of $TOTAL_ROWS rows" done # Re-enable constraints geode query "ALTER DATABASE ENABLE CONSTRAINTS" # Rebuild indexes geode query "REINDEX DATABASE" </code></pre></div> <h4 id="transaction-batching" class="position-relative d-flex align-items-center group"> Transaction Batching <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="transaction-batching" aria-haspopup="dialog" aria-label="Share link: Transaction Batching"> Share link </button> </h4>Use transactions for consistent bulk operations: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Import in transactions (batch of 1000 nodes) BEGIN TRANSACTION; CREATE (p1:Person {id: 1, name: 'Alice', age: 30}); CREATE (p2:Person {id: 2, name: 'Bob', age: 25}); -- ... 998 more nodes ... CREATE (p1000:Person {id: 1000, name: 'Charlie', age: 35}); COMMIT; </code></pre></div> <h4 id="parallel-import" class="position-relative d-flex align-items-center group"> Parallel Import <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="parallel-import" aria-haspopup="dialog" aria-label="Share link: Parallel Import"> Share link </button> </h4>Parallelize imports for faster migration: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # Parallel import using GNU parallel # Split CSV into chunks split -l 10000 nodes.csv chunk- # Import chunks in parallel (4 workers) ls chunk-* | parallel -j 4 ' cat {} | while IFS="," read -r id name age; do geode query "CREATE (p:Person {id: $id, name: \"$name\", age: $age})" done ' # Cleanup rm chunk-* </code></pre></div> <h3 id="troubleshooting-common-migration-issues" class="position-relative d-flex align-items-center group"> Troubleshooting Common Migration Issues <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="troubleshooting-common-migration-issues" aria-haspopup="dialog" aria-label="Share link: Troubleshooting Common Migration Issues"> Share link </button> </h3> <h4 id="issue-backup-timeout" class="position-relative d-flex align-items-center group"> Issue: Backup Timeout <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="issue-backup-timeout" aria-haspopup="dialog" aria-label="Share link: Issue: Backup Timeout"> Share link </button> </h4>Symptom: Backup fails with timeout error <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Increase backup timeout export GEODE_BACKUP_TIMEOUT_MS=600000 # 10 minutes # Use incremental backups for large datasets geode backup --dest s3://bucket/backups --mode incremental --parent <last-full-backup-id> </code></pre></div> <h4 id="issue-restore-corruption" class="position-relative d-flex align-items-center group"> Issue: Restore Corruption <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="issue-restore-corruption" aria-haspopup="dialog" aria-label="Share link: Issue: Restore Corruption"> Share link </button> </h4>Symptom: Restore completes but data is corrupted <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Verify backup integrity before restore geode backup --dest s3://bucket/backups --verify --backup-id 1738012345 # If corrupted, try previous backup geode backup --dest s3://bucket/backups --list geode restore --source s3://bucket/backups --backup-id <previous-backup-id> --target /var/lib/geode/data </code></pre></div> <h4 id="issue-out-of-memory-during-import" class="position-relative d-flex align-items-center group"> Issue: Out of Memory During Import <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="issue-out-of-memory-during-import" aria-haspopup="dialog" aria-label="Share link: Issue: Out of Memory During Import"> Share link </button> </h4>Symptom: Server crashes with OOM during bulk import <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Increase server memory allocation export GEODE_MAX_MEMORY=16GB # Reduce batch size BATCH_SIZE=500 # Instead of 1000 # Use streaming import (process one record at a time) while IFS=',' read -r id name age; do geode query "CREATE (p:Person {id: $id, name: '$name', age: $age})" done < nodes.csv </code></pre></div> <h4 id="issue-index-build-timeout" class="position-relative d-flex align-items-center group"> Issue: Index Build Timeout <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="issue-index-build-timeout" aria-haspopup="dialog" aria-label="Share link: Issue: Index Build Timeout"> Share link </button> </h4>Symptom: Index creation times out on large datasets <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create index with timeout configuration CREATE INDEX person_email ON Person(email) WITH (build_timeout_ms = 600000); -- 10 minutes -- Monitor index build progress SHOW INDEX BUILD STATUS; </code></pre></div> <h3 id="related-documentation" class="position-relative d-flex align-items-center group"> Related Documentation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="related-documentation" aria-haspopup="dialog" aria-label="Share link: Related Documentation"> Share link </button> </h3><ul> <li><a href="/docs/configuration/server-configuration/" >Server Configuration</a> - Complete configuration reference</li> <li><a href="/docs/guides/troubleshooting/" >Troubleshooting Guide</a> - Common issues and solutions</li> <li><a href="/docs/query/performance-tuning/" >Performance Tuning</a> - Optimize query performance</li> <li><a href="/docs/guides/schema-design/" >Schema Design Guide</a> - Best practices for schema modeling</li> </ul> <h3 id="summary" class="position-relative d-flex align-items-center group"> Summary <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="summary" aria-haspopup="dialog" aria-label="Share link: Summary"> Share link </button> </h3>Geode provides comprehensive migration capabilities: <ul> <li>Version Upgrades: In-place and rolling upgrade procedures with backward compatibility</li> <li>Database Migrations: Convert from Neo4j, JanusGraph, TigerGraph to Geode GQL</li> <li>Backup & Restore: S3-compatible cloud backup with point-in-time recovery</li> <li>Zero-Downtime Strategies: Blue-green deployment, read replica migration, shadow traffic</li> <li>Schema Evolution: Safe schema modifications without downtime</li> <li>Bulk Loading: Optimized import strategies for large datasets</li> </ul> Always test migrations in staging environments before production deployment. Use incremental backups for efficiency and verify data integrity after migration.