Backup and Recovery

<h2 id="backup-and-recovery" class="position-relative d-flex align-items-center group"> Backup and Recovery <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-recovery" aria-haspopup="dialog" aria-label="Share link: Backup and Recovery"> Share link </button> </h2><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>Database backup and recovery are critical operations for protecting your Geode graph data against hardware failures, software bugs, human errors, and disaster scenarios. Geode provides enterprise-grade backup capabilities designed for production workloads with minimal performance impact and point-in-time recovery guarantees. <h3 id="introduction-to-geode-backup" class="position-relative d-flex align-items-center group"> Introduction to Geode 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="introduction-to-geode-backup" aria-haspopup="dialog" aria-label="Share link: Introduction to Geode Backup"> Share link </button> </h3>Geode implements a comprehensive backup strategy that balances data protection, performance, and operational simplicity. The system supports multiple backup methods, each optimized for different scenarios and recovery time objectives (RTO) and recovery point objectives (RPO). Key characteristics of Geode’s backup system include transactional consistency through MVCC (Multi-Version Concurrency Control), incremental backup support via the Write-Ahead Log (WAL), online backup operations with zero downtime, point-in-time recovery capabilities, and automatic verification of backup integrity. The backup architecture integrates deeply with Geode’s storage engine, ensuring that backups capture a consistent snapshot of the graph database state without blocking concurrent read or write operations. <h3 id="backup-methods" class="position-relative d-flex align-items-center group"> Backup Methods <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-methods" aria-haspopup="dialog" aria-label="Share link: Backup Methods"> Share link </button> </h3> <h4 id="full-database-backup" class="position-relative d-flex align-items-center group"> Full Database 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="full-database-backup" aria-haspopup="dialog" aria-label="Share link: Full Database Backup"> Share link </button> </h4>Full backups capture the complete state of your Geode database at a specific point in time. This method creates a self-contained backup that can be restored independently without requiring any other backup files. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Create a full backup geode backup create --type=full --output=/backups/geode-full-$(date +%Y%m%d).tar.gz # With compression geode backup create --type=full --compress=zstd --output=/backups/geode-full.tar.zst # Verify backup integrity geode backup verify /backups/geode-full-20260124.tar.gz </code></pre></div>Full backups are ideal for establishing baseline backups, disaster recovery scenarios, migrating databases between environments, and creating development or testing databases from production snapshots. <h4 id="incremental-backup" class="position-relative d-flex align-items-center group"> Incremental 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="incremental-backup" aria-haspopup="dialog" aria-label="Share link: Incremental Backup"> Share link </button> </h4>Incremental backups capture only the changes made since the last backup, significantly reducing backup time and storage requirements for active databases. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Create incremental backup geode backup create --type=incremental --base=/backups/geode-full.tar.gz \ --output=/backups/geode-incr-$(date +%Y%m%d-%H%M%S).tar.gz # Chain multiple incrementals geode backup create --type=incremental \ --base=/backups/geode-full.tar.gz \ --previous=/backups/geode-incr-20260124-120000.tar.gz \ --output=/backups/geode-incr-20260124-180000.tar.gz </code></pre></div>Geode’s incremental backups leverage the Write-Ahead Log (WAL) to identify changed data efficiently, enabling frequent backups with minimal overhead. <h4 id="continuous-archiving-with-wal" class="position-relative d-flex align-items-center group"> Continuous Archiving with WAL <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="continuous-archiving-with-wal" aria-haspopup="dialog" aria-label="Share link: Continuous Archiving with WAL"> Share link </button> </h4>For databases requiring minimal data loss in disaster scenarios, Geode supports continuous WAL archiving, providing near-zero RPO. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Enable WAL archiving geode config set wal.archive.enabled=true geode config set wal.archive.directory=/wal-archive geode config set wal.archive.compression=zstd # Restore with WAL replay geode restore --backup=/backups/geode-full.tar.gz \ --wal-archive=/wal-archive \ --recovery-target-time="2026-01-24 14:30:00" </code></pre></div>WAL archiving enables point-in-time recovery to any moment between backups, supports streaming replication for standby servers, and provides audit trails for compliance requirements. <h3 id="backup-strategies" class="position-relative d-flex align-items-center group"> Backup 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="backup-strategies" aria-haspopup="dialog" aria-label="Share link: Backup Strategies"> Share link </button> </h3> <h4 id="production-backup-schedule" class="position-relative d-flex align-items-center group"> Production Backup Schedule <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="production-backup-schedule" aria-haspopup="dialog" aria-label="Share link: Production Backup Schedule"> Share link </button> </h4>A comprehensive backup strategy combines multiple backup types to balance protection and resource utilization: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Daily full backup (off-peak hours) 0 2 * * * /usr/local/bin/geode backup create --type=full \ --output=/backups/daily/geode-$(date +\%Y\%m\%d).tar.gz # Hourly incremental backups 0 * * * * /usr/local/bin/geode backup create --type=incremental \ --base=/backups/daily/geode-latest.tar.gz \ --output=/backups/hourly/geode-$(date +\%Y\%m\%d-\%H00).tar.gz # Continuous WAL archiving */5 * * * * /usr/local/bin/geode wal archive --compress=zstd </code></pre></div> <h4 id="retention-policies" class="position-relative d-flex align-items-center group"> Retention Policies <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="retention-policies" aria-haspopup="dialog" aria-label="Share link: Retention Policies"> Share link </button> </h4>Implement retention policies to manage backup storage costs while maintaining adequate recovery options: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Configure retention policy geode backup retention set \ --full-daily=7 \ --full-weekly=4 \ --full-monthly=12 \ --incremental-hours=168 # Automated cleanup geode backup cleanup --apply-retention --dry-run=false </code></pre></div>Typical retention strategies include daily full backups for 7 days, weekly backups for 4 weeks, monthly backups for 12 months, and hourly incrementals for 7 days. <h3 id="recovery-procedures" class="position-relative d-flex align-items-center group"> Recovery Procedures <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="recovery-procedures" aria-haspopup="dialog" aria-label="Share link: Recovery Procedures"> Share link </button> </h3> <h4 id="basic-recovery" class="position-relative d-flex align-items-center group"> Basic Recovery <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="basic-recovery" aria-haspopup="dialog" aria-label="Share link: Basic Recovery"> Share link </button> </h4>Restore from a full backup to recover your database to a known good state: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Stop the database geode stop # Restore from backup geode restore --backup=/backups/geode-full-20260124.tar.gz \ --target-directory=/var/lib/geode # Verify restored data geode verify --full-scan=true # Start the database geode start </code></pre></div> <h4 id="point-in-time-recovery" class="position-relative d-flex align-items-center group"> Point-in-Time Recovery <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" aria-haspopup="dialog" aria-label="Share link: Point-in-Time Recovery"> Share link </button> </h4>Recover your database to a specific moment using base backup and WAL archives: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Restore base backup geode restore --backup=/backups/geode-full-20260124.tar.gz \ --target-directory=/var/lib/geode # Apply WAL archives up to target time geode recover \ --wal-archive=/wal-archive \ --recovery-target-time="2026-01-24 14:30:00" \ --recovery-target-inclusive=false # Verify recovery point geode query --execute "SELECT current_timestamp()" --format=table </code></pre></div>This technique is invaluable for recovering from logical errors like accidental data deletion, rolling back failed migrations or updates, and investigating database state at specific times for auditing. <h4 id="incremental-restore" class="position-relative d-flex align-items-center group"> Incremental 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="incremental-restore" aria-haspopup="dialog" aria-label="Share link: Incremental Restore"> Share link </button> </h4>When restoring from incremental backups, apply them in chronological order: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Restore base backup geode restore --backup=/backups/geode-full-20260120.tar.gz # Apply incremental backups in order geode restore --backup=/backups/geode-incr-20260121.tar.gz --incremental geode restore --backup=/backups/geode-incr-20260122.tar.gz --incremental geode restore --backup=/backups/geode-incr-20260123.tar.gz --incremental geode restore --backup=/backups/geode-incr-20260124.tar.gz --incremental # Automated incremental chain restore geode restore --backup=/backups/geode-full-20260120.tar.gz \ --apply-incrementals=/backups/incrementals/ \ --recovery-target=latest </code></pre></div> <h3 id="online-backup-operations" class="position-relative d-flex align-items-center group"> Online Backup Operations <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="online-backup-operations" aria-haspopup="dialog" aria-label="Share link: Online Backup Operations"> Share link </button> </h3>Geode’s MVCC architecture enables consistent backups without blocking database operations: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Query backup status during backup SELECT backup_id, start_time, progress_percent, estimated_completion FROM system.active_backups; -- Monitor backup impact PROFILE SELECT COUNT(*) FROM (MATCH (n) RETURN n); </code></pre></div>Online backups maintain ACID guarantees, support concurrent transactions during backup operations, use snapshot isolation for consistency, and minimize performance impact through efficient I/O scheduling. <h3 id="disaster-recovery-planning" class="position-relative d-flex align-items-center group"> Disaster Recovery Planning <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="disaster-recovery-planning" aria-haspopup="dialog" aria-label="Share link: Disaster Recovery Planning"> Share link </button> </h3> <h4 id="multi-region-backup-strategy" class="position-relative d-flex align-items-center group"> Multi-Region 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="multi-region-backup-strategy" aria-haspopup="dialog" aria-label="Share link: Multi-Region Backup Strategy"> Share link </button> </h4>Distribute backups across geographic regions for disaster resilience: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Local backup geode backup create --type=full --output=/local/backups/geode-full.tar.gz # Replicate to remote regions aws s3 sync /local/backups/ s3://geode-backups-us-east-1/ --region us-east-1 aws s3 sync /local/backups/ s3://geode-backups-eu-west-1/ --region eu-west-1 # Cloud-native backup geode backup create --type=full \ --output=s3://geode-backups/geode-full-$(date +%Y%m%d).tar.gz \ --storage-class=GLACIER_IR </code></pre></div> <h4 id="recovery-time-objectives" class="position-relative d-flex align-items-center group"> Recovery Time Objectives <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="recovery-time-objectives" aria-haspopup="dialog" aria-label="Share link: Recovery Time Objectives"> Share link </button> </h4>Optimize backup strategies for your recovery time requirements: <ul> <li>RTO < 15 minutes: Maintain hot standby with streaming replication</li> <li>RTO < 1 hour: Keep recent backups on fast local storage</li> <li>RTO < 4 hours: Use cloud storage with standard retrieval</li> <li>RTO < 24 hours: Archive to cold storage tiers</li> </ul> <h4 id="testing-recovery-procedures" class="position-relative d-flex align-items-center group"> Testing Recovery Procedures <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="testing-recovery-procedures" aria-haspopup="dialog" aria-label="Share link: Testing Recovery Procedures"> Share link </button> </h4>Regularly test backup recovery to ensure reliability: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Automated recovery testing #!/bin/bash BACKUP_FILE="/backups/geode-full-$(date +%Y%m%d).tar.gz" TEST_DIR="/tmp/geode-recovery-test" # Create test environment mkdir -p $TEST_DIR geode restore --backup=$BACKUP_FILE --target-directory=$TEST_DIR # Verify restored database geode --data-dir=$TEST_DIR verify --full-scan=true geode --data-dir=$TEST_DIR query --execute "SELECT COUNT(*) FROM graph_nodes" # Cleanup rm -rf $TEST_DIR </code></pre></div> <h3 id="backup-performance-optimization" class="position-relative d-flex align-items-center group"> Backup Performance Optimization <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-performance-optimization" aria-haspopup="dialog" aria-label="Share link: Backup Performance Optimization"> Share link </button> </h3> <h4 id="parallel-backup-operations" class="position-relative d-flex align-items-center group"> Parallel Backup Operations <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-backup-operations" aria-haspopup="dialog" aria-label="Share link: Parallel Backup Operations"> Share link </button> </h4>Leverage multiple CPU cores for faster backups: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Parallel compression geode backup create --type=full \ --output=/backups/geode-full.tar.gz \ --compress=zstd \ --compress-threads=8 \ --parallel-workers=4 # Benchmark backup performance time geode backup create --type=full \ --output=/dev/null \ --compress=none \ --parallel-workers=1 time geode backup create --type=full \ --output=/dev/null \ --compress=zstd \ --parallel-workers=8 </code></pre></div> <h4 id="io-throttling" class="position-relative d-flex align-items-center group"> I/O Throttling <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="io-throttling" aria-haspopup="dialog" aria-label="Share link: I/O Throttling"> Share link </button> </h4>Limit backup I/O impact on production workloads: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Rate-limited backup geode backup create --type=full \ --output=/backups/geode-full.tar.gz \ --io-limit=100MB/s \ --priority=low # Adaptive throttling based on load geode backup create --type=full \ --output=/backups/geode-full.tar.gz \ --adaptive-throttling=true \ --max-cpu-percent=20 \ --max-io-percent=30 </code></pre></div> <h3 id="backup-verification-and-integrity" class="position-relative d-flex align-items-center group"> Backup Verification and Integrity <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-verification-and-integrity" aria-haspopup="dialog" aria-label="Share link: Backup Verification and Integrity"> Share link </button> </h3> <h4 id="automated-verification" class="position-relative d-flex align-items-center group"> Automated Verification <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-verification" aria-haspopup="dialog" aria-label="Share link: Automated Verification"> Share link </button> </h4>Ensure backup integrity with automated checks: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Verify backup checksums geode backup verify /backups/geode-full.tar.gz --verify-checksums # Test restore in isolated environment geode backup verify /backups/geode-full.tar.gz --test-restore # Verify data integrity after restore geode backup verify /backups/geode-full.tar.gz \ --test-restore \ --verify-queries=/etc/geode/verify-queries.gql </code></pre></div>Example verification queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Verify node counts SELECT COUNT(*) AS node_count FROM (MATCH (n) RETURN n); -- Verify relationship integrity SELECT COUNT(*) AS edge_count FROM (MATCH ()-[r]->() RETURN r); -- Verify critical data MATCH (u:User) WHERE u.role = 'admin' RETURN COUNT(u) AS admin_count; </code></pre></div> <h3 id="best-practices" class="position-relative d-flex align-items-center group"> 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="best-practices" aria-haspopup="dialog" aria-label="Share link: Best Practices"> Share link </button> </h3><ol> <li>Backup Schedule: Implement a 3-2-1 backup strategy (3 copies, 2 different media types, 1 offsite)</li> <li>Encryption: Encrypt backups containing sensitive data using strong encryption algorithms</li> <li>Monitoring: Monitor backup success rates, backup sizes, and backup duration trends</li> <li>Documentation: Document recovery procedures and maintain runbooks for disaster scenarios</li> <li>Testing: Test recovery procedures quarterly and after major system changes</li> <li>Automation: Automate backup processes to eliminate human error and ensure consistency</li> <li>Validation: Validate backup integrity immediately after creation</li> <li>Retention: Balance retention requirements with storage costs and compliance needs</li> </ol> <h3 id="troubleshooting" class="position-relative d-flex align-items-center group"> Troubleshooting <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" aria-haspopup="dialog" aria-label="Share link: Troubleshooting"> Share link </button> </h3> <h4 id="backup-failures" class="position-relative d-flex align-items-center group"> Backup Failures <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-failures" aria-haspopup="dialog" aria-label="Share link: Backup Failures"> Share link </button> </h4>Common backup issues and solutions: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Insufficient disk space geode backup create --type=full \ --output=/backups/geode-full.tar.gz \ --compress=zstd \ --compress-level=9 # Network timeouts for cloud backups geode backup create --type=full \ --output=s3://bucket/backup.tar.gz \ --retry-attempts=5 \ --timeout=3600 # Check backup logs geode logs --filter=backup --level=error --tail=100 </code></pre></div> <h4 id="recovery-issues" class="position-relative d-flex align-items-center group"> Recovery 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="recovery-issues" aria-haspopup="dialog" aria-label="Share link: Recovery Issues"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Corrupted backup file geode backup verify /backups/geode-full.tar.gz --repair # WAL archive gaps geode recover \ --wal-archive=/wal-archive \ --recovery-target-time="2026-01-24 14:30:00" \ --skip-missing-wal=true \ --recovery-target-inclusive=false # Version compatibility geode restore --backup=/backups/geode-full.tar.gz \ --source-version=0.1.2 \ --target-version=0.2.18 \ --migrate-schema=true </code></pre></div> <h3 id="advanced-backup-patterns" class="position-relative d-flex align-items-center group"> Advanced Backup Patterns <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="advanced-backup-patterns" aria-haspopup="dialog" aria-label="Share link: Advanced Backup Patterns"> Share link </button> </h3> <h4 id="application-consistent-backups" class="position-relative d-flex align-items-center group"> Application-Consistent Backups <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="application-consistent-backups" aria-haspopup="dialog" aria-label="Share link: Application-Consistent Backups"> Share link </button> </h4>Ensure application consistency during backups by coordinating with application state: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># application_consistent_backup.py async def create_application_consistent_backup(): # Step 1: Quiesce application writes await app.pause_writes() # Step 2: Flush pending transactions async with geode_client.connection() as tx: await tx.begin() await tx.execute("CALL dbms.checkpoint()") # Step 3: Create backup subprocess.run([ 'geode', 'backup', 'create', '--type=full', '--output=/backups/app-consistent.tar.gz' ], check=True) # Step 4: Resume application writes await app.resume_writes() </code></pre></div> <h4 id="backup-cataloging" class="position-relative d-flex align-items-center group"> Backup Cataloging <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-cataloging" aria-haspopup="dialog" aria-label="Share link: Backup Cataloging"> Share link </button> </h4>Maintain backup metadata for efficient management: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sql" data-lang="sql">-- backup_catalog schema CREATE TABLE backup_catalog ( backup_id SERIAL PRIMARY KEY, backup_type VARCHAR(20), -- full, incremental, differential backup_path TEXT, created_at TIMESTAMP, size_bytes BIGINT, compressed_size_bytes BIGINT, checksum VARCHAR(64), encryption_enabled BOOLEAN, retention_until TIMESTAMP, parent_backup_id INTEGER REFERENCES backup_catalog(backup_id), status VARCHAR(20), -- completed, failed, in_progress metadata JSONB ); </code></pre></div>Track backups programmatically: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">def register_backup(backup_path, backup_type): size = os.path.getsize(backup_path) checksum = calculate_sha256(backup_path) cursor.execute(""" INSERT INTO backup_catalog (backup_type, backup_path, created_at, size_bytes, checksum, status) VALUES (%s, %s, NOW(), %s, %s, 'completed') RETURNING backup_id """, (backup_type, backup_path, size, checksum)) return cursor.fetchone()[0] </code></pre></div> <h4 id="backup-compliance-reporting" class="position-relative d-flex align-items-center group"> Backup Compliance Reporting <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-compliance-reporting" aria-haspopup="dialog" aria-label="Share link: Backup Compliance Reporting"> Share link </button> </h4>Generate compliance reports for auditors: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">def generate_backup_compliance_report(): """Generate monthly backup compliance report""" report = { 'period': datetime.now().strftime('%Y-%m'), 'metrics': {} } # Daily backup success rate cursor.execute(""" SELECT DATE(created_at) as backup_date, COUNT(*) FILTER (WHERE status = 'completed') as successful, COUNT(*) FILTER (WHERE status = 'failed') as failed FROM backup_catalog WHERE created_at > NOW() - INTERVAL '30 days' GROUP BY DATE(created_at) ORDER BY backup_date """) report['daily_backups'] = cursor.fetchall() # Verify backups exist for all required days cursor.execute(""" SELECT COUNT(DISTINCT DATE(created_at)) FROM backup_catalog WHERE created_at > NOW() - INTERVAL '30 days' AND status = 'completed' """) days_with_backups = cursor.fetchone()[0] report['metrics']['backup_coverage'] = f"{days_with_backups}/30 days" # Average backup size and duration cursor.execute(""" SELECT AVG(size_bytes) as avg_size, AVG(EXTRACT(EPOCH FROM (completed_at - started_at))) as avg_duration FROM backup_catalog WHERE created_at > NOW() - INTERVAL '30 days' """) stats = cursor.fetchone() report['metrics']['avg_backup_size_gb'] = f"{stats[0] / 1e9:.2f}" report['metrics']['avg_duration_minutes'] = f"{stats[1] / 60:.1f}" return report </code></pre></div> <h4 id="incremental-forever-strategy" class="position-relative d-flex align-items-center group"> Incremental Forever 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="incremental-forever-strategy" aria-haspopup="dialog" aria-label="Share link: Incremental Forever Strategy"> Share link </button> </h4>Implement “incremental forever” backup approach: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # incremental_forever.sh BACKUP_DIR=/backups/incremental-forever # Create synthetic full backup weekly by merging incrementals if [ $(date +%u) -eq 7 ]; then echo "Creating synthetic full backup..." # Get all incrementals from past week INCREMENTALS=$(find $BACKUP_DIR -name "incr-*.tar.gz" -mtime -7 | sort) # Merge into synthetic full geode backup merge \ --incrementals $INCREMENTALS \ --output $BACKUP_DIR/synthetic-full-$(date +%Y%m%d).tar.gz # Delete old incrementals find $BACKUP_DIR -name "incr-*.tar.gz" -mtime +7 -delete fi # Always create incremental geode backup create --type=incremental \ --base=$BACKUP_DIR/synthetic-full-latest.tar.gz \ --output=$BACKUP_DIR/incr-$(date +%Y%m%d-%H%M%S).tar.gz </code></pre></div>Benefits: Reduces backup window, optimizes storage, simplifies retention management. <h3 id="disaster-recovery-scenarios" class="position-relative d-flex align-items-center group"> Disaster Recovery Scenarios <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="disaster-recovery-scenarios" aria-haspopup="dialog" aria-label="Share link: Disaster Recovery Scenarios"> Share link </button> </h3> <h4 id="complete-data-center-loss" class="position-relative d-flex align-items-center group"> Complete Data Center Loss <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="complete-data-center-loss" aria-haspopup="dialog" aria-label="Share link: Complete Data Center Loss"> Share link </button> </h4>Recover from total data center failure: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash">#!/bin/bash # disaster_recovery_full.sh DR_REGION="us-west-2" PRIMARY_REGION="us-east-1" echo "Initiating disaster recovery for complete DC loss..." # 1. Provision infrastructure in DR region cd terraform/dr-region terraform apply -auto-approve -var="region=$DR_REGION" # 2. Retrieve latest backup from off-site storage aws s3 cp \ "s3://geode-backups-$PRIMARY_REGION/latest-full.tar.gz" \ /tmp/recovery-backup.tar.gz \ --region $PRIMARY_REGION # 3. Deploy Geode instances DR_INSTANCES=$(terraform output -json instance_ips | jq -r '.[]') # 4. Restore to all instances in parallel for instance in $DR_INSTANCES; do ( scp /tmp/recovery-backup.tar.gz geode@$instance:/tmp/ ssh geode@$instance "geode restore --backup=/tmp/recovery-backup.tar.gz" ) & done wait # 5. Verify data integrity geode shell --host $DR_INSTANCES[0] -c " MATCH (n) RETURN COUNT(n) AS node_count; MATCH ()-[r]->() RETURN COUNT(r) AS rel_count; " # 6. Update DNS for failover aws route53 change-resource-record-sets \ --hosted-zone-id Z123456 \ --change-batch file://dns-failover.json echo "DR complete. Database active in $DR_REGION" </code></pre></div> <h4 id="ransomware-recovery" class="position-relative d-flex align-items-center group"> Ransomware Recovery <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="ransomware-recovery" aria-haspopup="dialog" aria-label="Share link: Ransomware Recovery"> Share link </button> </h4>Recover from ransomware attack: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Detect ransomware early geode backup verify /backups/geode-full-20260124.tar.gz # If current data is compromised, restore to pre-attack state geode restore \ --backup=/backups/geode-full-20260122.tar.gz \ --recovery-target-time="2026-01-22 23:59:59" \ --verify-integrity=true # Apply WAL up to attack time (discard compromised transactions) geode recover \ --wal-archive=s3://wal-archive/ \ --recovery-target-time="2026-01-22 23:55:00" \ --skip-corrupted-wal=true </code></pre></div> <h4 id="logical-data-corruption" class="position-relative d-flex align-items-center group"> Logical Data 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="logical-data-corruption" aria-haspopup="dialog" aria-label="Share link: Logical Data Corruption"> Share link </button> </h4>Recover from application bug that corrupted data: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Identify when corruption occurred geode query -c " SELECT MIN(modified_at) as corruption_start FROM audit_log WHERE data_integrity_check = false " > /tmp/corruption_time.txt # Restore to point before corruption RECOVERY_TIME=$(cat /tmp/corruption_time.txt | awk '{print $1}') geode restore \ --backup=/backups/closest-backup-before-corruption.tar.gz geode recover \ --wal-archive=/wal-archive \ --recovery-target-time="$RECOVERY_TIME" \ --recovery-target-inclusive=false </code></pre></div> <h3 id="backup-best-practices-summary" class="position-relative d-flex align-items-center group"> Backup Best Practices 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="backup-best-practices-summary" aria-haspopup="dialog" aria-label="Share link: Backup Best Practices Summary"> Share link </button> </h3><ol> <li>Implement 3-2-1 rule: 3 copies, 2 different media, 1 off-site</li> <li>Test restores quarterly: Ensure backups actually work</li> <li>Monitor backup health: Automate checks for freshness and integrity</li> <li>Encrypt backups: Protect sensitive data at rest</li> <li>Document procedures: Maintain runbooks for disaster recovery</li> <li>Automate everything: Eliminate human error</li> <li>Verify after creation: Check checksums and test-restore samples</li> <li>Set retention policies: Balance compliance needs with storage costs</li> <li>Separate backup credentials: Don’t use same account as production</li> <li>Practice disaster recovery: Regular drills ensure team readiness</li> </ol> <h3 id="related-topics" class="position-relative d-flex align-items-center group"> Related Topics <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-topics" aria-haspopup="dialog" aria-label="Share link: Related Topics"> Share link </button> </h3><ul> <li><a href="/tags/server/" >Server Configuration</a> - Server settings for backup operations</li> <li><a href="/tags/monitoring/" >Monitoring</a> - Backup monitoring and alerting</li> <li><a href="/tags/encryption/" >Encryption</a> - Backup encryption and access control</li> </ul> <h3 id="further-reading" class="position-relative d-flex align-items-center group"> Further Reading <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="further-reading" aria-haspopup="dialog" aria-label="Share link: Further Reading"> Share link </button> </h3><ul> <li><a href="/docs/guides/backup-automation/" >Backup Automation Guide</a> - Detailed backup procedures</li> <li><a href="/docs/deployment/deployment-patterns/" >Deployment Patterns</a> - Production deployment strategies</li> </ul>

Popular

Related Articles

Backup Procedures

Deployment and Integration Guide

Data Export Guide

Backup and Restore Guide

Database Recovery