1 of 1 people found this helpful
Before I tell my client this not-so-good news, I'm wondering if anyone else has had any experience with this or found any possible workarounds. I'm guessing not, since that defeats the idea of encryption, but thought I'd do due diligence and ask.
Thanks in Advance,
No workarounds. The only 'solution' is a rigorous backup procedure with checks on the validity of the backed up files; frequent health checks on the files,...
Thanks, Wim. Multiple failures. Backup that started five days ago and never stopped. Drive that died that was used for the progressive backups and IT didn't notify me. Time to get even more redundant with my redundancy.
Were you able to run Recover, and open the Database ? Did you check the Recover Log ?
If you can "pull data from it into a known good file", then there should be a way to Recover the Containers
> That file can only be recovered enough to pull data from it into a known good file. However, the container then stops working. Which is true to FileMaker's own documentation:
Because the storage was encrypted, we can't pull the data from the recovered file. We had to revert to the last good backup instead. It behaves differently than when stored without encryption.