Overview

This story tracks the upstream Velero issue for implementing backup and snapshot size reporting functionality.

Upstream Issue Details

• Velero Issue: #6506 - How can I get the size of the backups and snapshots?
• Status: Open
• Assignee: Lyndon-Li
• Labels: kind/requirement, 1.18-candidate, depends-upstream, backlog, Needs triage
• Created: July 17, 2023

Problem Statement

Users currently have no easy way to obtain detailed size information for Velero backups and snapshots, including:

• Size when the backup is incremental
• Size for a full backup
• Size for a snapshot
• Size before and after compression

Users must manually check storage buckets to determine backup sizes.

Proposed Upstream Solution

The Velero community has identified that size information is already tracked internally but not exposed via CLI or Backup CR status. The proposed solution includes:

Phase 1: Add size fields to BackupStatus

• BackupSizeBytes for K8s objects tarball
• VolumeSnapshotSizeBytes for total volume snapshot size
• VolumeSnapshotSizeBreakdown for detailed breakdown

Phase 2: Aggregate and display information

• Update backup controller to aggregate existing size data
• Enhance velero backup describe to show size information

OADP Impact

This directly relates to OADP-5645 where "OADP CSI Snapshot shows successful, but size is 0 bytes". Implementing this upstream feature would provide better visibility into backup sizes for OADP users.

Implementation Challenges

• Distinguishing logical vs physical repository sizes
• Handling incremental backup size complexity over time
• Integration challenges with Kopia for incremental size reporting
• Different storage considerations (CSI snapshots vs BSL storage)

Acceptance Criteria

• [ ] Monitor upstream Velero issue #6506 progress
• [ ] Evaluate impact on OADP when upstream implementation is available
• [ ] Test integration with OADP once upstream feature is implemented
• [ ] Update OADP documentation if needed