Snapshots

Creating & Managing Snapshots

The USBridge snapshot workflow is designed to capture and preserve data states on external, hardware-isolated media. For optimal reliability, follow this standardized setup and management procedure.

1. Media Preparation and Hardware Connection

Initialize the physical storage and establish the hardware link.

  1. Media Installation: Insert a high-endurance SD card (industrial-grade media is strongly recommended) or attach an external SSD to the appliance via the dedicated USB-C storage port.
  2. Host Connection: Interface the USBridge appliance with the target machine using the primary USB-C control cable.
  3. Initialization and Verification: Upon appliance boot, verify the storage media health and mounting status directly through the Settings menu on the built-in LCD screen.

2. Volume Mounting and Host Access

Storage provisioning and volume control are executed through the USBridge Client application.

  1. Volume Activation: Launch the client application, navigate to the storage module, and select Mount Drive.
  2. Data Access: Once initialized, the isolated storage volume mounts directly within the target host's operating system as a standard local drive.
  3. Operation Mode Selection: The storage medium can be exposed as a standard Mass Storage block device or via Media Transfer Protocol (MTP) to ensure maximum cross-platform compatibility.

3. Automated Snapshot Generation

Data capture is an autonomous, event-driven process that eliminates the need for manual command execution.

  1. Data Transfer: Transfer the critical files or configuration backups targeted for preservation onto the mounted USBridge drive.
  2. Automated Capture: The internal engine monitors file-system events. Upon detecting write completions, the system autonomously generates a new snapshot state, populating it in the client application's registry.
  3. Immutability Enforcement: Every captured snapshot is instantaneously locked as a read-only Btrfs subvolume, preventing subsequent modification.
  4. Audit and Extraction: Snapshots are exposed hierarchically. Administrators can traverse the directory tree at any time to inspect historical states and extract pristine data for bare-metal recovery.

4. Delta Change Analysis and Auditing

Beyond static storage, the subsystem provides granular tracking of data modifications between captured states.

  1. Telemetry Access: Each snapshot entry in the client interface features an information toggle (`i`) that generates a detailed delta report.
  2. Modification Inspection: Activating the report reveals a comprehensive diff log, explicitly listing all file additions, modifications, and deletions encompassed within that specific snapshot delta.

5. Security and Access Governance

All recorded state changes are secured via strict hardware and file-system level isolation protocols.

  • Hardware-Enforced Write Protection: Once a state is committed to a snapshot, the subvolume is structurally restricted to Read-Only access.
  • Total Host Isolation: The target server's operating system lacks the permissions, drivers, and physical routing required to modify or purge the snapshot repository. This establishes a reliable recovery vector following catastrophic failures or ransomware encryption events.