# Separate local and remote DriveBackupV2 retention counts

Keeping fewer remote backups does not necessarily reduce local archive storage, and the reverse is also true. DriveBackupV2 documents separate remote and local retention controls. Decide how many recovery points belong in each place before changing a count.

## Record the starting point

List recent local archives and the corresponding remote copies. Record their dates, sizes and whether uploads completed. Keep the current configuration and identify the oldest recovery point the community still needs before applying a policy that may remove copies.

## Work through the change

1. Read the installed release's storage documentation and locate the remote keep-count and local-keep-count controls. Confirm the documented meaning of each value, including any special values.
2. Choose counts based on the actual schedule and recovery need. Three hourly copies provide a different history from three daily copies, even though the count is identical.
3. Apply the intended policy and observe one normal backup cycle. Check the log and both destinations to see which archive was created, uploaded and retained.
4. Download a retained remote copy and inspect a small restore sample in a separate folder. A remote filename alone does not establish that the archive is usable.

## Check the result

Local usage should stay within the chosen capacity while remote storage retains the intended history. Document the schedule beside the counts. Confirm the newest successful remote copy before considering removal of any older local recovery point.

## If the result differs

If local usage remains high, inspect whether archives were produced under an older naming or destination arrangement. If remote history differs, check upload success and provider listing behaviour. Do not assume a retention setting has cleaned every historical file outside its managed set.

Restore the previous counts if the new policy is too aggressive, while recognising that deleted copies are not recreated by changing a number back. Preserve remaining good copies and repair the policy before the next cycle. Do not delete live game files to satisfy archive retention.

## References and related help

- [DriveBackupV2 maintainer reference 1](https://github.com/MaxMaeder/DriveBackupV2/wiki/Backup-Storage)
- [Configure DriveBackupV2 and verify an off-server recovery copy](https://help.cloudexa-hosting.com/books/minecraft-plugins/page/configure-drivebackupv2-and-verify-an-off-server-recovery-copy)
- [Back up game files before making changes](https://help.cloudexa-hosting.com/books/game-hosting/page/back-up-game-files-before-making-changes)