4 Replies Latest reply on May 8, 2017 2:31 PM by tritechsol

    Damaged file, encrypted remote containers

    tritechsol

      I have a situation with multiple points of failure, from backups to damaged files. The unfortunate scenario includes a file that uses an external container set to secure. 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:

       

      If I'm unable to open my database (damaged / forgot password), can I recover documents stored in container fields configured to store data externally, and set to be secure (which is default)?

      No. If the FileMaker database is damaged, or you have forgotten your password, there is no way to decrypt the external container data. The data is tied to a key unique to that database. (from http://help.filemaker.com/app/answers/detail/a_id/10244/kw/external%20container%20recovery)

       

      I'm in the process of reverting to the last good back, which is a week old.

       

      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,

       

      Yvonne

        • 1. Re: Damaged file, encrypted remote containers
          wimdecorte

          tritechsol wrote:


          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,

           

          Yvonne

           

          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,...

          1 of 1 people found this helpful
          • 2. Re: Damaged file, encrypted remote containers
            tritechsol

            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.

             

            Thanks again.

            • 3. Re: Damaged file, encrypted remote containers
              gdurniak

              Just curious,

               

              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

               

              greg

               

              > 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:

              • 4. Re: Damaged file, encrypted remote containers
                tritechsol

                Hi, Greg,
                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.

                 

                Yvonne