Message: The RemovePoints function error: Failed to remove backups. | Message: The archive is corrupted.
Task 'xxxx' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09500ab
Fields:
Message: Failed to create a backup.
--------------------
Error code: 701
Module: 64
LineInfo: 97e50e642849a37c
Fields: IsReturnCode : 1
Message: The RemovePoints function error: Failed to remove backups.
--------------------
Error code: 32
Module: 7
LineInfo: b9f78558b2f41ee1
Fields:
Message: The archive is corrupted.
--------------------'.
does this mean i need to delete the archive?
i have a GFS archive with 7 days + 4 weeks +14 months
can you recover from such an error. this would be really bad if you need a backup and its "invalid"

- Log in to post comments

Hello Jan,
According to the error provided, the archive is corrupted. We has this issue with the Exchange-aware backup, but it was fixed in the latest hotfix (#5155). I believe that our Development team updated your appliance to that build the last time you had a remote session.
In order to fix the problem, please create a new archive, and run a backup with the newest build installed. It should solve the issue.
Let us know if it remains, we will be glad to help.
Thank you.
- Log in to post comments

just a thing to keep in mind:
ok. so the format changed of the archive for the application aware backup (exchange) in that version?? .. hopefully this wont happen in the future especially when one would run production backups for a whole year for a lot of servers .. the whole reason for backups is for going back in time.. and it wont be really "appriciated" for customers that they cannot read their hard needed backups :)
would this be a thing that can happen more? otherwise i would need to give the special backups ( application aware) a seperate backup task and archive.
thx
Jan
- Log in to post comments

Hi Jan,
No, don't worry, it's not going to happen again, we've localized, and fixed the issue, and it's no longer present in the build you've updated to. We're really sorry for you've faced this issue, and will do out best to make sure it won't happen again.
Thank you
- Log in to post comments