Tanzu Hub BBR backup fails with no space left on device

Products

• VMware Tanzu Platform Core

Issue/Introduction

Attempting a BBR backup results in error "no space left on device".

Operator is performing steps described in - Backup and restore Tanzu Hub 

Example backup command executed:

bbr deployment -d <hub-deployment> backup -a ARTIFACT-PATH

Example error condition:

bbr.stderr.log: 
Internal Error, copy part #####: write /proc/self/fd/10: copy file_range: no space left on device

 

Resolution

The BBR backup is kept on the Tanzu Hub registry VM. The registry VM is where the backup happens, once it is completed successfully then it is compressed and copied over (from registry VM) to where the BBR command was run.

For certain large environments, the ephemeral disk space may become exhausted on registry VM.

The resolution is to simply scale the registry VM in the resource config pane of Tanzu Hub tile - see documentation on Tanzu Hub tile's Resource Config tab.

The 2xlarge.disk option provides 256GB ephemeral disk space and should be sufficient for most environments. This will prevent the BBR backup from exhausting disk space and allow operator continue backup restore process.