MightyData

FileMaker and WordPress Consultants

  • Company
    • About
    • Contact
    • Team
    • Artists
  • Services
    • Consulting
    • Development
    • Our Process
    • Coaching
    • Training
  • Results
    • Customers
    • Success Stories
    • Testimonials
  • Blog

Restoring FileMaker 12 Backups With Managed Containers

November 28, 2012 by Darren Burgess 17 Comments

In the course of my work on a customer project, I discovered that the links to externally stored container fields with a FileMaker Server 12 backup can break if the backup is not restored properly. After trying a number of different scenarios, I have come up with a list of circumstances where container fields will remain intact and when they won’t.

All examples are using a Windows based FileMaker server and apply equally to both secure and open external container storage.  Understanding these situations will help you properly restore FileMaker 12 files that use external container storage.

In case you need to get some basic knowledge about FileMaker Server 12 and the new features related to backup and enhanced container fields, here are some great resources to get you started:

  • Using Container Fields in FileMaker 12  (log in to FileMaker TechNet to download)
  • FileMaker Server 12 Configuration Guide (also found at TechNet)

Circumstances where external container data will break (container fields will show files as missing):

  • Uploading FMP12 backup files with the FileMaker Server admin console.
  • Opening backup files in FileMaker Pro — ie, not hosted by a server
  • Opening files in FileMaker Pro that were removed by the FMS admin console

Circumstances where external container data will remain intact:

  • Copying FMP12 backup files, with the respective container data folder from the RC_Data_FMS folder, to the FileMaker server data directory, then opening the files with the admin console.
  • Copying backup files, as above to a different FileMaker server
  • Downloading the files with FMS admin console, then opening the files in FileMaker Pro (e.g., not hosted).  In this case, the databases and remote container file directories are downloaded together, so references to externally stored container fields are preserved.
  • Downloading the files with FMS admin console, then uploading to another server, or the same server, with the admin console. Again, the act of downloading the files brings the container file directory along with it.  Uploading these same files will restore the container data on the FileMaker server.
So to conclude, when restoring backups of FileMaker files that use external container storage, copy the files (don’t upload with the Admin Console) to the data directory of your FileMaker server.  In addition to the FMP12 files, copy the respective subfolder for your backup file in RC_Data_FMS to the RC_Data_FMS folder in the server data directory.  Note that on Mac OS servers, permissions for the FMP12 file and container directories need to be reset when copied to the data directory and not uploaded with the console.

Filed Under: FileMaker Server Tagged With: Admin console, Backup, Best practices, Container fields, FileMaker 12

12 Days of FileMaker 12: Server Performance

May 31, 2012 by Kirk Bowman 4 Comments

FileMaker Server 12 statistics graph

FileMaker Server is the primary tool for monitoring and enhancing the performance of FileMaker solutions. FileMaker Server 12 provides new features to increase the ability of the database administrator or developer to create the best experience for the users.

Performance Tools in FileMaker Server

In this session from the 12 Days of FileMaker 12, I explore six aspects of performance with the new server.

  1. Faster WAN Performance – FileMaker Server 12 can perform finds up to 40% faster, display large value lists quicker, and evaluate filtered portals on the server instead of the workstation. The enhancements improve the performance of FileMaker over a wide-area network.
  2. More Stable Architecture – The server architecture has six separate processes to isolate the impact of one on another. Five of the processes can start, stop or restart from the command line for more control over the server.
  3. More Efficient Backups – Backup schedules only backup the databases that have changed, using hard links for databases that have not changed. The new Progressive Backup goes further by backing up on the data that has changed. Both reduce the time necessary to back up a database.
  4. 64-bit Application – On a 64-bit operating system, FileMaker Server 12 can use up to one terabyte of RAM for the server cache. It is important because RAM is faster than the hard disk. The database, web publishing, ODBC and progressive backup processes are each 64-bit.
  5. Progressive Media Download – With the new Remote Container feature, the server can create thumbnails of large images and stream PDF and video files directly to FileMaker Pro asynchronously.
  6. Faster Web Publishing – The new 64-bit Web Publishing Engine can handle more simultaneous custom web publishing requests, faster than the previous server. Also, session management is faster due to a new caching algorithm.

Even with these new features, performance is a complex interaction of hardware, software (OS), and database design. FileMaker Server 12 includes a new graph view for server statistics and more flexibility in the Log Viewer to help identify weak spots in the performance equation.

FileMaker Server Training

To go deep into performance with FileMaker Server 12, watch the video below including 15 minutes of question and answer.

Filed Under: FileMaker Server Tagged With: 12 Days of FileMaker 12, Backup, FileMaker 12, Performance, Video

New Year’s Database Resolution: Backup! – Part 3

March 2, 2012 by Kirk Bowman Leave a Comment

SMTP settings for FileMaker Server

To properly backup your FileMaker databases, the first step is to setup backup schedules in FileMaker Server. The next step is to use best practices with the schedules to make sure your backups are safe. Now you need to enable email notification to keep in you informed whether the backup schedules are running successfully.

To enable email notification, first configure the SMTP settings in FileMaker Server. In the Admin Console, go to Configuration > General Settings > Email Notification. Often, you can use the same settings in your email software (Mac Mail, Outlook, etc.). Below is a description of the most common settings.

SMTP settings for FileMaker Server

  • From Address – Enter the email address from which you want the messages to be sent.
  • SMTP Server Address – Enter the domain name or IP address of your SMTP mail server.
  • SMTP Authentication – Most email servers require authentication (user and password) to send email. Check the checkbox and use the default setting of “Plain Text”.
  • Use Secure Sockets Layer (SSL) – Gmail and several other email hosts require SSL. Checking this checkbox will automatically change the port number.
  • User – Enter the username to login to the SMTP server. This is usually the same as the From Address.
  • Password – The password to login to the SMTP server. Ask your system administrator if you do not know the password.

Once you have entered the SMTP settings, click the Test SMTP Settings button. FileMaker Server will prompt you to enter the email address to send a “test email”. FMS will then display a dialog to inform you whether the email was sent successfully.  The test email should look something like this.

Test email from FileMaker Server

Next, you should enable Notification Settings for the server. This sends email messages when there are general errors (not related to a backup schedule) with FileMaker Server.

Notification settings for FileMaker Server

  • Enable Email Notifications – Check the checkbox to send notifications. (This can be the same email address as the From Address above.)
  • Send Email Notifications To – Enter the email address to which to send error messages.
  • Security Level – Use the default setting of “Errors only”. The “Warnings or errors” setting will overwhelm your inbox with unnecessary email.

Now, you are ready to setup email notifications for your backup schedules. If you followed the recommendations in the first article, you will use notification for the Daily and Weekly schedules. This will notify you each day if you backups are running successfully without overwhelming your inbox.

In the Admin Console, go to Administration > Schedules and right-click on the Daily schedule. Choose “Edit a schedule” from the contextual menu. Click the Next button for the first four screens in the schedule wizard. On the fifth page, simply check “Send email notification” and enter the “To” address to send notifications for the backup schedule. (FMS will default to the email address from the Notification Settings above.) Click the Finish button.

The schedule will send an email notification whenever the backup executes. The email will describe whether the backup was successful or failed. To test the schedule notification, right click on the schedule and choose “Run a schedule now”. The backup will be performed and then FMS will send the email notification.

Email for daily backup schedule

Email notification is your first line of defense to ensure your backup schedules are working properly. Setting up the notifications is not enough. You must have the discipline to read the email each day to make there are no errors with your backups. The worst time to find out your backups are not working is when you need a backup copy to recover some data.

Filed Under: FileMaker Server Tagged With: Admin console, Backup, Best practices

New Year’s Database Resolution: Backup! – Part 2

January 6, 2012 by Kirk Bowman 1 Comment

In part one of this series, I explained the changes I would make to the default backup schedules installed with FileMaker Server—the “what”. Now I want to take a moment and explain the “why” and clarify some points about my recommendations.

  • 23 Hourly Backups – The Hourly schedule is set to keep 23 hourly backups at a time. Why not 24? Because the most recent Daily backup is the 24th.
  • 6 Daily Backups – For the same reason, the Daily schedule is set to keep 6 daily backups. The most recent Weekly backup is the 7th. These steps conserve the disk space for two backups.
  • Verification – Why verify? Because the worst thing to happen to a database is to lose data. Verification checks the integrity of the backup and can send an email if the database is damaged. In most cases, if the backup is damaged it is likely that the live database is too. This is your early warning system.
  • Hourly Verification – If your database is small to medium (500MB or less per file), you can probably verify each hourly backup without much impact on performance, depending on your hardware. If it does create an intolerable slowdown, disable it for Hourly only and leave it on for Daily and Weekly.
  • Cloning – Why clone? Because if your database is damaged, depending on the degree of damage, you may need to recover the database. Having a pristine clone (structure without the data) makes it easier to restore a healthy database because you can usually rule out damage to the structure with a good clone.
  • Drive Size – The default location for backups created by schedules is the FileMaker Server/Data/Backups folder on the boot drive. It is common for boot drives (or partitions) to be fairly small (40GB-ish), especially on Windows or virtual servers. Storing 33 backups (23 + 6 + 4) can fill up the boot drive quickly. Make sure you do the math to ensure you have ample drive space.
  • Backup Location – A better idea is to store the database backups on a separate drive or partition, usually with much more drive space. On a Windows server this could be the C drive for the OS and FileMaker Server, and the D drive for the databases and backups. (Using a third E drive for the backups is even better). This also helps increase the speed of the backup process.
  • Archiving Backups – Making backups of the database to the local hard drive is not enough. You need to use backup software (outside FileMaker Server) to make copies of the backups to another location. Some options include tape drive, external hard drive, network volume, or even offsite. In a larger organization, this will probably be the responsibility of the IT group.
  • DO NOT Backup the Live Database – The database hosted by FileMaker Server is available 24×7, meaning the file is always open. Backing up an open file is a no-no, especially with databases because it can corrupt the live database and the backup. Configure your backup software to exclude FileMaker Server/Data/Databases (home of live databases). In addition, do not:
    • Use Time Machine to backup the live databases
    • Use “snapshot” technology on Windows to backup the live databases
    • Enable virus scanning of the live databases
    • Enable file sharing on the FileMaker Server/Data/Databases folder

As you can see, having good backups of your FileMaker database requires several considerations. Hopefully, these tips will make your backup plan more safe and reliable. In coming articles, I will discuss email notification and offsite storage for your databases.

Filed Under: FileMaker Server Tagged With: Admin console, Backup, Best practices

New Year’s Database Resolution: Backup! – Part 1

January 4, 2012 by Kirk Bowman 5 Comments

Default backup schedules for FileMaker Server

So, it is a brand new year and everyone is making resolutions for their personal and professional lives. Along with going to the gym and learning to fill-in-the-blank better, I want to challenge you to make a goal to backup your database better. (Hopefully, you are already backing up some.)

The easiest way to backup your FileMaker database is to use FileMaker Server. So, if you are not using FileMaker Server, why not? If you are using a hosting provider, then I will assume they are backing up the database for you. (Do you know how often they backup your database?) Otherwise, I assume you are hosting the database on your own server—with FileMaker Server.

FileMaker Server includes “Schedules”, the ability to automatically backup the live database at a regular interval. The database server comes with three schedules already created: Daily, Hourly and Weekly. However, only the Daily schedule is enabled by default. I am going to recommend some changes to the default schedules to improve your database backups.

Default backup schedules for FileMaker Server

To view schedules, login to the FileMaker Server Admin Console. Open a web browser directly on the server and type this URL http://localhost:16000. This should display a web page to launch the Admin Console. Of course, you will need the username and password for the Admin Console. Once you login, click on Schedules under Administration in the navigation tree.

To edit a schedule, right-click on it in the list of schedules and select Edit a Schedule. This launches a wizard to walk you through the various options for the schedule. These are the changes I recommend for the default schedules, which will backup the database once per hour for 24 hours, one per day for 7 days and once per week for 4 weeks.

Hourly Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 23
      Note: The daily schedule will take care of the 24th hour.
    • Verify backup integrity: Checked (by default)
      Note: For large databases you may need to uncheck this option due to the time required to verify the database each hour.
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Daily
    • Run every: 1 Hours
    • Start time: 12:00 AM
    • End time: 10:00 PM
  • Schedule Summary
    • Enable this schedule: Checked

Daily Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 6
      Note: The weekly schedule will take care of the 7th day.
    • Verify backup integrity: Checked (by default)
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Weekly
    • Select the days of the week: All days except Sunday
    • Once per day, Start time: 11:00pm
  • Schedule Summary
    • Enable this schedule: Checked (by default)

Modified daily backup schedule

Weekly Schedule

  • Select the Backup Folder and Options
    • Maximum number of backup to keep: 4
    • Verify backup integrity: Checked (by default)
    • Clone the backup file: Checked
  • Select the Schedule Details
    • Frequency: Weekly
    • Select the days of the week: Sunday
    • Once per day, Start time: 11:00pm
  • Schedule Summary
    • Enable this schedule: Checked

This is a great start for your New Year’s Database Resolution. In the next few articles, I will cover other ways to improve on this basic setup including email notification, offsite backup, and drive space. Together, we will help you get your database in good shape to start 2012.

Filed Under: FileMaker Server Tagged With: Admin console, Backup, Best practices

Let’s get started on your project.

It will be more fun than you think.

Get in Touch

  • Company
  • Services
  • Results
  • Blog

Copyright © 2023 · Parallax Pro Theme on Genesis Framework · WordPress · Log in