1 Reply Latest reply on Mar 16, 2009 8:44 AM by TSGal

    abnormal backup behavior - FileMaker Server 9.0v3.325 on Windows

    wdmoon

      Summary

      abnormal backup behavior - FileMaker Server 9.0v3.325 on Windows

      Description of the issue

      FileMaker Product(s) involved:FileMaker Server 9.0v3.325 Operating System(s) involved:Windows Server 2003 SP2 Detailed description of the issue:I have five databases hosted by FileMaker Server 9.   There is a schedule set in the Admin Console to back up the databases three times a day.  The backups worked correctly for several months.  However on February 16 there was an aberrant backup that ran two hours prior to its scheduled time.  It also tine-stamped the backup incorrectly as March 16 in the FileMaker and Windows event logs.  All events in both logs are dated correctly both before and after the one aberrant FileMaker backup with the March 16 date.  Is this a known issue? After the aberrant backup, FileMaker quit backing up.  I assume the reason is the scheduler saw the March 16 files and quit, thinking it would be overwriting newer files if the backup continued.  Can you confirm this is the expected behavior? Exact text of any error message(s) that appeared:Here is a section of the application log showing the correct entries immedialty prior to and after the backup which is time-stamped one month in the future.2009-02-16 14:00:12.030 -0600 Information 126 UA FileMaker Schedule "Hourly" scheduled for 02/16/2009 05:00 PM.2009-02-16 17:00:00.233 -0600 Information 148 UA FileMaker Schedule "Hourly" running.2009-02-16 17:00:00.233 -0600 Information 458 UA FileMaker Starting to back up database: EDS...2009-02-16 17:00:00.249 -0600 Information 458 UA FileMaker Starting to back up database: ManageIT...2009-02-16 17:00:00.249 -0600 Information 458 UA FileMaker Starting to back up database: MapIT...2009-02-16 17:00:00.249 -0600 Information 458 UA FileMaker Starting to back up database: SnapIT...2009-02-16 17:00:00.264 -0600 Information 458 UA FileMaker Starting to back up database: Tech_Time_Clock...2009-02-16 17:00:06.061 -0600 Information 460 UA FileMaker Backup of EDS completed.2009-02-16 17:00:06.061 -0600 Information 460 UA FileMaker Backup of ManageIT completed.2009-02-16 17:00:06.061 -0600 Information 460 UA FileMaker Backup of MapIT completed.2009-02-16 17:00:06.061 -0600 Information 460 UA FileMaker Backup of SnapIT completed.2009-02-16 17:00:06.061 -0600 Information 460 UA FileMaker Backup of Tech_Time_Clock completed.2009-02-16 17:00:06.093 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "EDS".2009-02-16 17:00:06.327 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "ManageIT".2009-02-16 17:00:11.374 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "MapIT".2009-02-16 17:00:11.749 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "SnapIT".2009-02-16 17:00:11.764 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "Tech_Time_Clock".2009-02-16 17:00:11.780 -0600 Information 150 UA FileMaker Schedule "Hourly" completed.2009-02-16 17:00:11.780 -0600 Information 126 UA FileMaker Schedule "Hourly" scheduled for 02/16/2009 08:00 PM.2009-03-16 17:14:12.531 -0600 Information 148 UA FileMaker Schedule "Hourly" running.2009-03-16 17:14:13.000 -0600 Information 458 UA FileMaker Starting to back up database: EDS...2009-03-16 17:14:13.031 -0600 Information 458 UA FileMaker Starting to back up database: ManageIT...2009-03-16 17:14:13.046 -0600 Information 458 UA FileMaker Starting to back up database: MapIT...2009-03-16 17:14:13.078 -0600 Information 458 UA FileMaker Starting to back up database: SnapIT...2009-03-16 17:14:13.078 -0600 Information 458 UA FileMaker Starting to back up database: Tech_Time_Clock...2009-03-16 17:14:22.125 -0600 Information 460 UA FileMaker Backup of EDS completed.2009-03-16 17:14:22.125 -0600 Information 460 UA FileMaker Backup of ManageIT completed.2009-03-16 17:14:22.125 -0600 Information 460 UA FileMaker Backup of MapIT completed.2009-03-16 17:14:22.125 -0600 Information 460 UA FileMaker Backup of SnapIT completed.2009-03-16 17:14:22.125 -0600 Information 460 UA FileMaker Backup of Tech_Time_Clock completed.2009-03-16 17:14:22.140 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "EDS".2009-03-16 17:14:22.406 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "ManageIT".2009-03-16 17:14:27.421 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "MapIT".2009-03-16 17:14:27.765 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "SnapIT".2009-03-16 17:14:27.781 -0600 Information 639 UA FileMaker Schedule "Hourly" consistency check succeeded on backup of database "Tech_Time_Clock".2009-03-16 17:14:27.796 -0600 Information 150 UA FileMaker Schedule "Hourly" completed.2009-03-16 17:14:27.796 -0600 Information 126 UA FileMaker Schedule "Hourly" scheduled for 03/16/2009 08:00 PM.2009-02-17 09:06:42.187 -0600 Warning 661 UA FileMaker Client "cfhayes" authentication failed on database "ManageIT.fp7" using "cfhayes [fmapp]".2009-02-17 09:49:29.609 -0600 Warning 661 UA FileMaker Client "cldeaton" authentication failed on database "ManageIT.fp7" using "cldeaton [fmapp]".2009-02-18 08:57:57.828 -0600 Warning 661 UA FileMaker Client "cfhayes" authentication failed on database "ManageIT.fp7" using "cfhayes [fmapp]".2009-02-18 13:38:36.703 -0600 Warning 661 UA FileMaker Client "cfhayes" authentication failed on database "ManageIT.fp7" using "cfhayes [fmapp]". Any additional configuration information/troubleshooting that is relevant to the issue:There were no changes made to that system the time/day in question. 

        • 1. Re: abnormal backup behavior - FileMaker Server 9.0v3.325 on Windows
          TSGal

          wdmoon:

           

          Thank you for your post.

           

          No, it is not expected behavior of FileMaker Server to timestamp a backup for a month in the future.

           

          Is it possible that someone accidentally changed the system date to March 16, 2009 as an accident around 17:14:11?  Realized it a few seconds later and changed it back to February 16, 2009 more than 20 seconds later? (17:14:31).  That would give FileMaker Server enough time to backup the files and consistency check the files, since it finished at 17:14:27.

           

          Now that the next backup time is set for 16 Mar 2009 at 8:00 PM, nothing is going to happen until that time (tonight).

           

          By changing the date, FileMaker sees that the next scheduled time has passed, so FileMaker initiates the backup command.  When finished, it looks for the next time.  Does that make sense?

           

          Whether this was a system error or accidental error, everything should run smoothly tonight at 8:00 PM.  In the mean time, you can do manual backups.

           

          TSGal

          FileMaker, Inc.