Struct StorageStats 

pub struct StorageStats {
    pub snapshot_count: Option<i64>,
    pub total_size: Option<String>,
    pub total_size_bytes: Option<i64>,
    pub last_observed_at: Option<String>,
    pub index_blob_count: Option<i64>,
    pub index_blob_count_at: Option<String>,
}

Aggregate repository storage figures from the last catalog scan.

Fields

snapshot_count: Option<i64>

Total COMPLETE snapshots present in the repository (across all identities). Incomplete checkpoints an interrupted kopia snapshot create left behind are not snapshots and are not counted.

total_size: Option<String>

Human-readable total on-disk size (e.g. 412Gi).

total_size_bytes: Option<i64>

Logical bytes under management (the integer form of total_size): the sum, over each distinct snapshot source, of the most-recent snapshot’s logical size. Exposed to backup preflight as repository.sizeBytes. This is repository total size, not backend free space (object stores don’t report remaining capacity).

last_observed_at: Option<String>

RFC 3339 timestamp these stats were last observed.

index_blob_count: Option<i64>

Number of content-index blobs (kopia index list): the freshest count available, from either the last bootstrap or the recount a maintenance run takes right after compacting. indexBlobCountAt says when.

index_blob_count_at: Option<String>

RFC3339 instant indexBlobCount was observed.

Distinct from lastObservedAt (the catalog scan’s timestamp) and from status.health.lastProbeAt (the backend probe’s): the index-blob count has its own writers, and this is what lets the reconciler decide whether a post-maintenance recount is fresher than the bootstrap’s own count. Without it the two observations were incomparable, so the IndexBlobHealth warning could only ever quote the bootstrap figure — which is pre-compaction, and stayed pre-compaction until the next bootstrap ran (#458).

The two writers mean subtly different things, deliberately. A bootstrap stamps “when this count was FIRST seen at this value”, reusing the previous stamp while the number is unchanged — that arm re-observes on every reconcile, and a stamp that always moved would make the status always-changed and the reconcile a hot loop. A post-maintenance recount always carries its own instant, because it is a distinct observation taken at a known time and its whole purpose is to be comparable.

Trait Implementations

impl Clone for StorageStats

fn clone(&self) -> StorageStats

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for StorageStats

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for StorageStats

fn default() -> StorageStats

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for StorageStats

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Eq for StorageStats

impl JsonSchema for StorageStats

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl PartialEq for StorageStats

fn eq(&self, other: &StorageStats) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for StorageStats

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for StorageStats