Journl Streamed
Talk to an expertWebsite
  • Introduction
  • Getting Started
    • Sandbox Access
    • On-Premise
    • Cloud
  • Overview
    • Why Journl Streamed?
    • Licensing & Support
    • Features
    • Solution Architecture and Usage
  • API
    • FHIR API
      • Accessing FHIR Data
      • CRUD
        • Create
        • Read
        • Update
          • Versioned Update
        • Patch
        • Delete
          • Versioned Delete
    • Batch Upsert
  • Services
    • Security & Access Control
    • FHIR Modeling, Profiles, and Standards
    • Careplan Creation
    • Analysis on Demand
      • Standard Process
      • Types of Analysis
    • Custom Resources
    • Monitoring & Maintenance
  • Storage
    • Database
      • Database schema
    • Backup and Restore
    • Indexes
  • Integrations
    • Data Ingestion and Decoupling
    • Subscriptions and Event Notifications
    • BI & Analytical tools
      • Power BI
      • Tableau
      • Jupyter Notebook
Powered by GitBook
On this page
  • Scheduled Backups
  • Manual Backups
  • Backup Storage
  • Backup Format
  • Restoration Process
  • Versioning and Retention
  1. Storage

Backup and Restore

Ensuring the security and availability of your data is paramount in Journl Streamed. We offer robust backup processes that include both automated and manual options to safeguard your data against loss or corruption.

Scheduled Backups

  • Automated Scheduling: Journl Streamed supports automated scheduled backups, allowing you to set specific intervals for backups (e.g. daily, weekly, etc.). This ensures regular snapshots of your data, crucial for recovery in case of data loss or corruption.

  • Configuration: You can configure the timing and frequency of these backups to align with your operational needs and data change rates.

Manual Backups

  • On-Demand Backups: In addition to scheduled backups, Journl Streamed provides options for manual backups. This feature is particularly useful before making significant system changes or for creating backups at any arbitrary point in time.

  • Initiation Methods: Manual backups can be triggered through the Journl Streamed interface or via API calls, offering flexibility in how and when you perform backups.

Backup Storage

  • Flexible Storage Options: Backups are stored in a designated backup storage location, which can be a local storage system, network-attached storage (NAS), or a cloud-based solution like AWS S3.

  • Configurable Storage: The backup storage location is configurable, allowing organizations to select a storage solution that meets their needs for scalability, durability, and cost-effectiveness.

Backup Format

  • Comprehensive Data Capture: The backup process captures all necessary information to restore the state of the instance. This typically includes the database, configuration files, and other relevant data.

  • Restoration Ready: The backup format ensures that all data is comprehensive and ready for a full system restore if needed.

Restoration Process

  • Restoration: We have tools for restoring data from backups. This process can be initiated by the Journl team.

  • Efficient Recovery: During the restoration process, the system can roll back to the state captured in the backup, facilitating recovery from data loss or corruption events.

Versioning and Retention

  • Backup Versioning: We support versioning of backups, allowing you and the organization to store and manage multiple backup versions. This is useful for maintaining historical records and performing point-in-time recoveries.

  • Retention Policies: I collaboration with the Journl team you and the organization can configure retention policies to manage the lifecycle of backups, automatically deleting older backups to conserve storage space while keeping recent backups accessible.

PreviousDatabase schemaNextIndexes

Last updated 9 months ago