Step 1
Find Drive backup cleanup
- Open Settings > Data Transfer
- Find Drive backup cleanup
Open Settings, Data Transfer, then Drive backup cleanup. These controls manage Pennie's stored Google Drive backups.
This needs regular paid Premium and authorized Google Drive access. Our demonstration uses an isolated synthetic catalog, not your real backups.
Step 2
Read storage before choosing cleanup
- Choose Refresh backup storage
- Check the current count, size and oldest date
Choose Refresh backup storage to read the backup count, stored size and oldest known date for the connected Google account.
This synthetic example has five Pennie backups. Storage totals alone do not prove that a snapshot contains the history you need.
Step 3
Review the 30-day cleanup confirmation
- Choose Delete older than 30 days
- Read the recovery safeguards
Delete older than thirty days opens a confirmation. Pennie keeps the newest backup and the newest verified non-empty full backup.
Verification may download older snapshots. In our example, the newest is empty, so an older useful full snapshot must also be protected.
Step 4
Cancel before deletion if unsure
- Use Cancel while deciding
- No backup deletion starts on cancellation
Use Cancel if you are unsure about the account or recovery backup. The cleanup action returns without starting deletion.
Do not confuse this protective age-based action with Delete all Pennie Drive backups. That separate action includes the newest backup.
Step 5
The 60-day option keeps more history
- Choose Delete older than 60 days
- Read the same recovery protection
For a longer history window, choose Delete older than sixty days. Its confirmation retains the same newest and useful full-backup safeguards.
The threshold is sixty days, not two calendar months. Use Cancel if this is not the cleanup window you intend.
Step 6
Read the actual 60-day result
- Confirm only the intended cleanup
- Read the reported number removed
After confirmation, our sixty-day example reports two older backups deleted. The forty-day snapshot stays, along with both protected recovery candidates.
These are virtual deletions through the actual cleanup code. No real Drive backup or local transaction is deleted by this demonstration.
Step 7
A shorter window can remove more snapshots
- Read Cleanup complete
- Acknowledge, then check refreshed storage
The thirty-day example reports three older backups deleted. The newest empty snapshot and the seventy-five-day useful full snapshot are kept.
Use OK, then check the refreshed storage information. The result count is not a promise that every backup older than the threshold was removed.
Step 8
No useful recovery means no deletion
- Read Cleanup incomplete
- Keep backups until a useful full snapshot is verified
If no verified non-empty full backup can be found, Cleanup incomplete pauses the action before deleting anything.
Our empty-only catalog demonstrates that safeguard. Do not repeatedly retry or use Delete all just to make the warning disappear.
Step 9
Verification failure stops cleanup
- Read the checksum refusal
- Resolve the backup problem before retrying
A downloaded snapshot with a mismatched checksum also reaches Cleanup incomplete. In this verification-failure example, nothing is deleted.
Check your connection and backup integrity before retrying. A stored filename or recent date is not proof that its contents are usable.
Step 10
A deletion error may leave partial cleanup
- Read the partial-deletion warning
- Refresh before trying again
A later deletion error is different from verification refusal. Some eligible backups may already have been deleted before Cleanup incomplete appears.
Our synthetic case deletes one eligible file, then fails on the next. Refresh storage before trying again; do not assume everything was rolled back.
Step 11
An unreadable list is not empty storage
- Read the visible storage error
- Use Refresh backup storage after resolving it
If Drive storage cannot be read, the page tells you to check the connection and try again.
That is an error, not a zero-backup result. Use Refresh backup storage when access is available; do not infer that your recovery history is gone.
Step 12
Successful cleanup can have a refresh error
- Distinguish deletion from storage refresh
- Refresh to check the remaining backups
Cleanup can complete even when the following storage refresh fails. The page explicitly says cleanup completed but storage could not be refreshed.
Refresh to check the remaining backups before taking another destructive action. Keep a verified recovery copy; cleanup is not an export or a restore.