What Are Snapshots?
A snapshot captures the complete state of an application at a specific moment, including:
- Application data - All files, databases, and configurations.
- System state - Current settings and customizations.
- Metadata - Information about when and how the snapshot was created.
- Integrity verification - Checksums to ensure data hasn't been corrupted.
Snapshot Types by Application
Database Snapshots
- SQL Databases - Complete database dumps with all tables and data.
- Triplestores - RDF data exports in N-Quads format.
File System Snapshots
- Shared Folders - Not (yet) implemented.
- WissKI Data - Drupal files, uploaded content, and configurations.
Environment Snapshots
- WissKI Environments - All components within a WissKI environment (Drupal root directory + database + triplestore).
- Nextcloud - Not possible.
- JupyterHub - Not possible.
- Webprotégé - Not possible.
When to Create Snapshots
Before Major Changes
Always create a snapshot before:
- Updating software or configurations.
- Importing large datasets.
- Making structural changes to your data model.
- Experimenting with new features.
- Before vacation or extended absences.
- At project milestones.
Data Preservation
Create snapshots for:
- Archiving completed projects.
- Meeting institutional data retention requirements.
- Sharing data with collaborators.
- Creating stable versions for publication.