Prevent old archives from being included in a new DriveBackupV2 backup
An archive stored inside a selected source directory can be included in the next backup. Repeating that selection can make backups grow rapidly without a matching increase in live game data. Review the actual selected paths before buying more storage or deleting worlds.
Record the starting point
Record where DriveBackupV2 writes local archives and which paths its installed configuration selects. Compare the size of live data with recent archives. Keep the existing configuration and one verified recovery copy before changing selection rules.
Work through the change
- Read the maintainer's file-selection documentation for the installed release. Identify whether the backup output directory or a parent containing it falls inside the selected sources.
- Inspect a recent archive without extracting over the live server. Look for older archive filenames nested inside it and distinguish those files from genuine plugin or world data.
- Adjust the documented selection or exclusion rules so generated backups are outside the new archive's source set. Preserve required world and plugin data rather than excluding an entire directory blindly.
- Run one controlled backup and inspect its file list and size. Verify a small restored sample in a separate location before relying on the revised selection.
Check the result
The new archive should contain the intended live files without a chain of previous backups. Its size should be explainable by those files rather than merely smaller. Keep the verified older copy until the revised archive has passed inspection.
If the result differs
If growth continues, compare source file sizes and check for another plugin's archives, database dumps or temporary exports. An exclusion pattern that misses the actual relative path may have no effect. Read the generated configuration's pattern rules before broadening it.
Restore the previous selection if required files disappear from the test archive, then correct the narrow rule. Do not delete the only known good backup to create space for an unverified replacement. Ask support about temporary capacity when a safe test cannot fit.
