2 Replies Latest reply on Jan 10, 2013 1:57 PM by mrjamesmoore

    Server 12 backup aborted due to remote container copy error

    mrjamesmoore

      I'm using the FM12 remote container (RC's) feature in a solution that consists of 5 files. 1 file is the main file containing 95% of the infrastructure and there are 4 other ancillary files. I have a daily scheduled backup that backs up all 5 files and recently noticed the main file was not included in the backup.

       

      Upon investigation I found out the issue was the backup was aborting due to a remote storage error; one of the files could not be backed up (copied). The error is contained in the email sent by the server and is as follows:

       

      2012-12-28 16:00:09.504 +1100 Error 766 SG FMSv12 Backup of "<<FM_FILENAME>>" aborted; error (-1) creating remote container folder "filewin:/C:/Program Files/FileMaker/FileMaker Server/Data/Backups/Hourly/Hourly_2012-12-28_1600/Databases/<<FM_FILENAME>>/RC_Data_FMS/<<FM_FILENAME>>/Images/<<FileName>>".

       

      When I create a schedule backup with JUST this main file included I get the same error but the file IS backed up. So I have a few questions:

       

      1. The Status of the backup in the FM Console reads "OK". Why does it say this when the main file didn't get backed up?

       

      2. Is there any way to stop the RC's being backup up - I really don't need any more copies of the files?

       

      3. How can I find out what is causing the RC's to generate the error? The images appear fine in FileMaker and I've deleted the references (from FM) and created them again and they still fail.

       

      4. Why does the FileMaker file fail to be backed up just because the RC's can't?

       

      5. Why does the file fail to backup when it's part of a set but work when it's on its own?

       

      Thanks,

       

      James

        • 1. Re: Server 12 backup aborted due to remote container copy error
          wimdecorte

           

           

          1. The Status of the backup in the FM Console reads "OK". Why does it say this when the main file didn't get backed up?

           

           

          That IS strange, raise a support ticket with FMI for that.  But first verify that absolutely nothing is trying to work with files or folders during backup time (no Volume Shadow Copy, no virus scanning,...)

           

           

           

           

          2. Is there any way to stop the RC's being backup up - I really don't need any more copies of the files?

           

           

          No!  That's like asking "is there a way to stop backing up some of my old records, I don't need more copies of those"  The RC data is integral part of your FM file, don't be fooled by the fact that it is stored outside of the FM file.  It's not just a link, it is part of your file.

           

          Also, remember that FMS uses smart hard linking for its backups.  So if that container field hasn't changed between backups, you actually don't have a new copy of the RC file, just a pointer to the inode that already exists on the hard disk.

           

          That also answers your question #4: because the RC file IS part of your FM file.

           

           

           

          5. Why does the file fail to backup when it's part of a set but work when it's on its own?

           

          Impossible to asnwer without looking in-depth at your deployment and the Windows system and application event logs... so look there for clues.  Also look at the hardware to see if there are any indications that the hard disk is failing or running out of disk space.  That's also in answer to your question #3.

          • 2. Re: Server 12 backup aborted due to remote container copy error
            mrjamesmoore

            Thanks for the reply.

             

            My point with the RC's not requiring backup is that unlike the data it never changes and I use other means to back them up. So I understand how important they are. But like I said wish there was an option to not back them up because as it stands the root of my problem still stands; the failure to copy them for unknown reasons is causing my backup to fail. Just because the RC's can't be copied doesn't mean the actual FM file shouldn't be - which is what I'm experiencing.

             

             

             

            James