Skip to main content

Backup Cleanup Troubleshooting

Backup Cleanup Troubleshooting

Support Guide

Resolve common issues encountered while cleaning obsolete backup files.

Commandcusty cleanup backups

Category

Maintenance

Quick Command

custy cleanup backups
cleanupbackuptroubleshooting

Overview​

Backup Cleanup is generally a straightforward operation.

Most issues are related to project configuration, backup locations, or simply the absence of backup files that require cleanup.

No Backup Files Were Removed​

What you see

The command completed successfully, but no backup files were deleted.

Why it happens

  • The number of existing backups is already within the configured retention count.
  • No backup files exist.
  • The selected cleanup type does not match any existing backup files.

How to resolve it

Verify:

  • the configured cleanup target,
  • the backup retention count,
  • and whether backup files currently exist.

This is usually expected behavior rather than an error.

Expected Backup Files Still Exist​

What you see

Some backup files remain after cleanup.

Why it happens

The remaining files are among the newest backups preserved by the configured retention policy.

How to resolve it

Review the configured keep value.

Custy intentionally preserves the newest backup files.

Cleanup Removed Fewer Files Than Expected​

What you see

Only some older backup files were removed.

Why it happens

Possible reasons include:

  • only one backup category was selected,
  • newer backups were preserved,
  • fewer files matched the selected cleanup type.

How to resolve it

Verify the selected cleanup type and review the backup directory contents.

Dry Run Removed Nothing​

What you see

No backup files were deleted.

Why it happens

The command was executed using the global:

--dry-run

option.

How to resolve it

Run the command again without the dry-run option when you are ready to perform the cleanup.

Unexpected Backup Location​

What you see

Custy appears to inspect a different backup directory than expected.

Why it happens

The backup directory is determined by your project's configuration.

How to resolve it

Review the configured backup directories in your project's config.toml.

Next Diagnostic Step​

If Backup Cleanup continues to behave unexpectedly:

  • review your project configuration,
  • verify the backup directories,
  • confirm the cleanup type,
  • inspect the command output.

Most Backup Cleanup issues can be resolved without modifying your project or Git repository.