Backup Troubleshooting
Backup Troubleshooting
Resolve common backup problems before continuing your workflow.
custy backupCategory
Quick Command
custy backup allOverview​
Most backup problems occur because the required template files cannot be found or the configured backup location is unavailable.
Fortunately, these problems are usually straightforward to resolve.
Commit Message Template Not Found​
What you see
The backup command skips the commit message backup or reports that the commit message template cannot be located.
Why it happens
The configured commit message template does not exist.
This commonly occurs when the project has not yet been initialized.
How to resolve it
Initialize the project if necessary.
custy init
If the project has already been initialized, verify that the configured commit message template path is correct.
Tag Message Template Not Found​
What you see
Custy skips the tag message backup or reports that the configured tag template cannot be found.
Why it happens
The tag message template has not yet been generated or its configured path is incorrect.
How to resolve it
Verify the configured template path.
If necessary, regenerate the project templates.
custy init
Backup Directory Cannot Be Created​
What you see
The backup operation cannot create the configured backup directory.
Why it happens
The destination directory is read-only or the current user does not have permission to create files.
How to resolve it
Verify that the configured backup location is writable.
If necessary:
- choose another backup directory,
- update the project configuration,
- or adjust file permissions.
Expected Backup File Is Missing​
What you see
The backup command completes, but the expected backup file cannot be found.
Why it happens
Possible reasons include:
- the wrong backup directory was inspected,
- the template file did not exist,
- the backup was skipped,
- an older backup was removed by the configured retention policy.
How to resolve it
Review the configured backup directory and confirm that the selected template exists before rerunning the backup command.
Old Backup Files Disappeared​
What you see
Previously created backup files are no longer present.
Why it happens
Custy automatically manages backup history.
Older backups may be removed when the configured retention policy is applied.
How to resolve it
Review your backup retention configuration if you need to preserve more backup history.
Dry Run Produced No Backup Files​
What you see
The command completed successfully, but no backup files were created.
Why it happens
The command was executed using the global
--dry-run
option.
How to resolve it
Run the command again without the global dry-run option.
For example:
custy backup all
Next Diagnostic Step​
If backup operations continue to fail:
- Verify your project's
config.tomlconfiguration. - Confirm that the required template files exist.
- Verify that the configured backup directories are writable.
- Review the output produced by the backup command.
Most backup issues can be resolved by correcting the first reported problem before rerunning the command.