TimberID
Log In
  • 🌳Welcome to TimberID
  • Overview
    • 🌳Background
  • User Guide
    • πŸ”°Registering
    • πŸͺ΅Single Reference Sample + Import
      • ⁉️Import Errors
    • πŸ”ŽOrigin Verification
    • πŸ“€Exporting
    • 🌎Earth Engine API
    • ⚑Administration Guide
      • πŸ§‘β€πŸ€β€πŸ§‘Creating Organizations
      • 🚸Managing Users
    • πŸ“—Glossary
    • πŸ›Report an Issue
  • Architecture of TimberID
    • πŸ› οΈHigh Level Design
    • πŸ“šOpen Source Github Repositories
    • 🏯Detailed Design
      • 🌐Client
      • πŸ–₯️Server
      • πŸ—ΊοΈExternal integrations and maps
      • 🌎Earth Engine
      • πŸ‘©β€πŸ”¬Research Colabs
        • Data Ingestion
        • Model Training (Variational Inference)
        • Isoscape Generation
        • Validation of Isoscapes
    • 🌩️GCP Guide
      • πŸ“ˆAnalytics
      • πŸ’ΎDatabase Query Builder
      • πŸ’°Budget Alerts
      • πŸŒ„Domain Name Configuration
      • ⚠️Backups and Disaster Recovery
    • πŸš€Test Procedure for Production Release
  • Internal
    • πŸ”Internal Information
Powered by GitBook
On this page

Was this helpful?

  1. Architecture of TimberID
  2. GCP Guide

Backups and Disaster Recovery

PreviousDomain Name ConfigurationNextTest Procedure for Production Release

Last updated 1 year ago

Was this helpful?

Disaster recover is enabled for the production firestore database for a 7 day retention period. You may also manually create backups. The storage for these options are billable, so creating more backups or increasing the retention period will increase cost.

You can see more in the for the production project.

If you want to access the data to restore into the current database, see to export firestore data from an old timestamp and then reimport.

🌩️
⚠️
disaster recovery options
how to use the gcloud command line interface