Jump to content
View in the app

A better way to browse. Learn more.
FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Proper sequence to reboot a Filemaker server

Glorifindal
in MirrorSync by 360Works

Featured Replies

Hi there,

I have inherited a MirrorSync installation ( FMS17 / MirrorSync 5 ) Apart from the online MirrorSync documentation, there is nothing else to check this with (so ein schmarrn)

Setup = Server1 > Server2.

It is supposed to be setup for a failover (but this has not worked automatically for over a month)

I need to reboot Server2

Is there anything I need to watch when rebooting? I would usually use the Filemaker Server console to simply close the databases before I reboot.

BUT : will this effect in any way affect Server 1 (it has a External Data Source to the data file in Server 2 and the MirrorSync scripts point to Server2) ?

SO: Is there a SAFE method of rebooting the server that is being used as a failover? (Server 2)? So that Server 1 will not suffer in any way?

many thanks in advance,

G

 

Edited by Glorifindal

Create an account or sign in to comment

https://fmforums.com/topic/106354-proper-sequence-to-reboot-a-filemaker-server/
Go to topic listing

Important Information

By using this site, you agree to our Terms of Use.

I accept

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.