I had to choose "Remove from Repository", run a new Backup and restart Pure.
Only with this restart the repository was cleaned.

So I lost all backups from this VM and had no backup until the new backup was finished.

I believe this is a dead solution, no support, no updates.
Too bad for this very nice solution.

Hi @guenter,

I am sorry to hear you had a bad experience with Pure. One question that comes to mind when thinking about your situation is if you had cloud storage configured or not. If you DID have Pure configured to store backups to cloud, Pure would not be able to delete any old snapshots from local storage unless they were successfully uploaded first. This is to assure that the snapshot chain in cloud is not broken.

If you did not have cloud storage configured at all, I am not sure what could be causing Pure to behave in this way without investigating further. Did I understand correctly that this strange behavior is limited to just one VM? In any case, while I do hope the issue is now resolved, I hope you will provide feedback if the problem still occurs and we can arrange for a TeamViewer session to work together towards discovering the cause of this behavior.

@marijan Other Backups are also affected! The first one was the biggest with 12 TB and filled the repository completely.
I had to free some space by deleting other not importand backups before I could run the new backup of the relevant VM.
Maybe I could remove the backup from repo and restart Pure to clear the space before running the new backup.

Cloud Object Store is not configured. But when I reduce the number of snapshots the older snapshots have the cloud symbol.

Sorry I am not able to place links or screenshots!

If possible we can do a TeamViewer session on monday?

Best regards
Guenter

@guenter If the older snapshots have the cloud icon next to them, this should mean that they are, indeed supposed to be uploaded to cloud. For each VM you can configure retention as the number of snapshots that are kept locally (you already tried adjusting this value from 7 to 2). In addition, you can configure how many ADDITIONAL snapshots are to be kept in cloud. For example, if you have retention set to 7 and an additional 3 in cloud, Pure will keep 7 most recent snapshots locally and 10 most recent snapshots in cloud. I think the problem is in that at certain point Pure was configured to upload to cloud. The cloud config might have been removed in the meantime but maybe not completely (e.g. removed credentials only). Pure now tries to upload to cloud, fails, waits for another opportunity and tries again (every 30 minutes and after each backup window). Old snapshots are being kept because they still need to be uploaded first.

I will reach out to you by email to set up a TV session on Monday or Tuesday. Hopefully, you now have enough space for backups for couple of days so no need to completely remove any VMs for now. I am positive I can fix the issue when I connect to your system and adjust Pure to no longer use cloud. I will also use this opportunity to try and find what caused this issue so we can fix it permanently.