New Free CRM for FileMaker Community - Day 6
Embedded Files
Contact us at:
Phone - (805) 946-6552
Email - support@rcconsulting.com
Visit our main websites
FMTraining.TV - https://fmtraining.tv/
Richard Carlton Consulting Inc - https://rcconsulting.com/
New FREE CRM for FileMaker Community - Day 6
New FREE CRM for FileMaker Community - Day 6
Transcript
Hello everyone. Welcome to another awesome day of FileMaker training. I am Richard Carlton here with my trusty team of awesome people which includes Margaret, Jacob, Taylor who's our server expert. So, we're going to be able to handle some questions today about the FileMaker server. So, if you have some open questions about FileMaker server in general, please feel free to ask those. And then we also have Michael, who is our ongoing expert on FM Starting Point light. That's 2022 the year we're using 22. It's not version 22 it's year 22. so his Starting Point of 2022 and he is the king kingpin on that we did kind of a live code review yesterday of it. We found a couple things that didn't make sense. We fixed some other bugs. We're going to have an update out for you this coming week. Now a very very very very very important announcement. This is like you guys are all going to want to hear about, you guys and gals right. So, stand by one second. Let me bring up. Let's see. So, if I go to FM Training.TV upcoming next week we have scheduled the 30-day CRM thing right. It was supposed to start this coming Monday. We are going to push it back two days. Why? Because out of the blue today Claris is saying hey we're gonna come on your tv show. And I'm like really it would be better if you pushed it back. So, we could plan on it because there's anyway so there's like you know marketing and awareness. And I have to tell some people to move around and all that kind of. So, anyway the CRM action right the CRM 30 day for beginners starts Wednesday of next week. Monday and Tuesday are going to be different. I don't know if our web page reflects that yet. Let me see where we're at with our live page Jacob.
Hello everyone. Welcome to another awesome day of FileMaker training. I am Richard Carlton here with my trusty team of awesome people which includes Margaret, Jacob, Taylor who's our server expert. So, we're going to be able to handle some questions today about the FileMaker server. So, if you have some open questions about FileMaker server in general, please feel free to ask those. And then we also have Michael, who is our ongoing expert on FM Starting Point light. That's 2022 the year we're using 22. It's not version 22 it's year 22. so his Starting Point of 2022 and he is the king kingpin on that we did kind of a live code review yesterday of it. We found a couple things that didn't make sense. We fixed some other bugs. We're going to have an update out for you this coming week. Now a very very very very very important announcement. This is like you guys are all going to want to hear about, you guys and gals right. So, stand by one second. Let me bring up. Let's see. So, if I go to FM Training.TV upcoming next week we have scheduled the 30-day CRM thing right. It was supposed to start this coming Monday. We are going to push it back two days. Why? Because out of the blue today Claris is saying hey we're gonna come on your tv show. And I'm like really it would be better if you pushed it back. So, we could plan on it because there's anyway so there's like you know marketing and awareness. And I have to tell some people to move around and all that kind of. So, anyway the CRM action right the CRM 30 day for beginners starts Wednesday of next week. Monday and Tuesday are going to be different. I don't know if our web page reflects that yet. Let me see where we're at with our live page Jacob.
So, it shows that Wednesday I don't know. Here we go. Monday and Tuesday are under construction. So, Monday and Tuesday. Monday we're going to be covering without any Claris babysitting FileMaker. What's on the tap for 19. 5? What's on tap in detail? What's on tap for 19. 6, right? Loosely because we haven't played with it too much. And also what's on tap for 20? And 20 are already shipped yet 19. 6 hasn't shipped. It's kind of like I can't say this out loud. So, it'll be I'm sure it'll be censored when I say the f word here. You'll hear it beep automatically. So, it's a cluster okay oh wait a minute. It didn't beat my bad. It'll beep it out in the recording. So, anyway. So, Claris is like Jacob. We should come on and talk to people. I'm like dude please. Can you come and explain this? I'm gonna sit back and I really need the discordians and all of you. Who has your questions? To ask your questions. Please ask your questions. Ask them. So, that will be Tuesday. So,Tuesday is an all hands on deck kind of. Andy locates from Claris and I'm asking only him but maybe someone else will come too. You should feel free to fire whatever questions you have at him that you feel is good and useful. But we'll try to maintain a high level of behavior. So, David Angel no no nakedness but any other memes. Memes are encouraged if they're appropriate. So, that's great. So, Monday, Tuesday so we're gonna tee things up on Monday to get your brain going.
So, it shows that Wednesday I don't know. Here we go. Monday and Tuesday are under construction. So, Monday and Tuesday. Monday we're going to be covering without any Claris babysitting FileMaker. What's on the tap for 19. 5? What's on tap in detail? What's on tap for 19. 6, right? Loosely because we haven't played with it too much. And also what's on tap for 20? And 20 are already shipped yet 19. 6 hasn't shipped. It's kind of like I can't say this out loud. So, it'll be I'm sure it'll be censored when I say the f word here. You'll hear it beep automatically. So, it's a cluster okay oh wait a minute. It didn't beat my bad. It'll beep it out in the recording. So, anyway. So, Claris is like Jacob. We should come on and talk to people. I'm like dude please. Can you come and explain this? I'm gonna sit back and I really need the discordians and all of you. Who has your questions? To ask your questions. Please ask your questions. Ask them. So, that will be Tuesday. So,Tuesday is an all hands on deck kind of. Andy locates from Claris and I'm asking only him but maybe someone else will come too. You should feel free to fire whatever questions you have at him that you feel is good and useful. But we'll try to maintain a high level of behavior. So, David Angel no no nakedness but any other memes. Memes are encouraged if they're appropriate. So, that's great. So, Monday, Tuesday so we're gonna tee things up on Monday to get your brain going.
There's actually quite a bit. We talked a little bit about this last Friday with the promise circle. He's going to want to talk about that on Tuesday. Claris says keep beating that because they're trying to kind of sell that because they feel that larger organizations. If any of you are part of a large organization like Kyle. If Kyle's part of a Victoria's Secret if only the marketing department has a FileMaker. The rest of the organization could benefit. And if the rest organization benefits then Claris sells more products. It's a pretty simple formula. I don't disagree. I totally think that's correct. I think all of Victoria's Secret could probably use FileMaker and be very beneficial and Kyle would be there, you know running it. So, that's Tuesday. So, Monday I'm going to prep everyone with what I know. If I run into something I don't know. I will tell you that Jacob Taylor will probably be here both days. Just my guess because there is some server stuff coming with 19. 5. We're going to kind of just cover this. I don't know what else to say. Claris keeps talking about it, it's public. And so, we're just going to dive into it. I don't know when you're going to get 19. 5. I think anytime you'll get 19. 5. I can be super excited on Monday and talk about all the cool new stuff that is both awesome and terrifies me about 19. 5 anyway. So, today is an open Q and A but we're saving the future open Q and A for other stuff. So, today I was trying to prepare stuff for today and I've been in meetings with Claris trying to understand the secret. What's not secret because I had a meeting with them this morning and they said this is secret. They pull out their guns and they said no one talks about this secret. And then meanwhile this secret is still on a youtube video that a lot of you were asking me about last Friday right. And it's still there right. And so, it's like that secret, it's not a secret.
There's actually quite a bit. We talked a little bit about this last Friday with the promise circle. He's going to want to talk about that on Tuesday. Claris says keep beating that because they're trying to kind of sell that because they feel that larger organizations. If any of you are part of a large organization like Kyle. If Kyle's part of a Victoria's Secret if only the marketing department has a FileMaker. The rest of the organization could benefit. And if the rest organization benefits then Claris sells more products. It's a pretty simple formula. I don't disagree. I totally think that's correct. I think all of Victoria's Secret could probably use FileMaker and be very beneficial and Kyle would be there, you know running it. So, that's Tuesday. So, Monday I'm going to prep everyone with what I know. If I run into something I don't know. I will tell you that Jacob Taylor will probably be here both days. Just my guess because there is some server stuff coming with 19. 5. We're going to kind of just cover this. I don't know what else to say. Claris keeps talking about it, it's public. And so, we're just going to dive into it. I don't know when you're going to get 19. 5. I think anytime you'll get 19. 5. I can be super excited on Monday and talk about all the cool new stuff that is both awesome and terrifies me about 19. 5 anyway. So, today is an open Q and A but we're saving the future open Q and A for other stuff. So, today I was trying to prepare stuff for today and I've been in meetings with Claris trying to understand the secret. What's not secret because I had a meeting with them this morning and they said this is secret. They pull out their guns and they said no one talks about this secret. And then meanwhile this secret is still on a youtube video that a lot of you were asking me about last Friday right. And it's still there right. And so, it's like that secret, it's not a secret.
Well this video is secret, the content of the video is not secret. But the fact that our voices are here are secret I. It's so confusing. So, anyway. So, I am confused. So, the best thing for me to do is kind of lay the kitchen table out for you the best. I understand on Monday. Then Andy could come in and explain to you how forks and spoons and knives work, right? So, if you have a spork, they're gonna have new kinds of silverware to show you. It'll be exciting. So, once again Monday, Tuesday for those of you arriving late the CRM thing the beginning CRM starts Wednesday. We're gonna move it back two days because Claris wants to come on Tuesday and talk to us about FileMaker 19. 5, 19.6, and 20 and public. What is the problem? Problem solver circle psc pse Jacob Taylor's here is our FileMaker server expert Amazon aws expert. And so, if we have questions about FileMaker servers and Amazon aws today I'm happy to take any kind of questions we can show Michael's FM Starting Point to 2020 light. We are actively unkinking the bugs that we discussed yesterday. We found out about that. And Mikey if you have a question and you folks have questions. If you're on twitch feel free to let us know what your question is. But it's kind of an open Q and A day. So, we want to make sure that we're answering that right? Yep. Answering questions because it's kind of wild all over the place and I just want to be responsive and help you out. So, if you have a question about some problem you're running into, throw it out. Today is the day. No penalty, no penalty as long as it's on topic which brings up one mention. I will mention Friday this week. We are doing the live stream. Jacob Taylor will be doing it with Calvin and they are talking about fixing the email.
Well this video is secret, the content of the video is not secret. But the fact that our voices are here are secret I. It's so confusing. So, anyway. So, I am confused. So, the best thing for me to do is kind of lay the kitchen table out for you the best. I understand on Monday. Then Andy could come in and explain to you how forks and spoons and knives work, right? So, if you have a spork, they're gonna have new kinds of silverware to show you. It'll be exciting. So, once again Monday, Tuesday for those of you arriving late the CRM thing the beginning CRM starts Wednesday. We're gonna move it back two days because Claris wants to come on Tuesday and talk to us about FileMaker 19. 5, 19.6, and 20 and public. What is the problem? Problem solver circle psc pse Jacob Taylor's here is our FileMaker server expert Amazon aws expert. And so, if we have questions about FileMaker servers and Amazon aws today I'm happy to take any kind of questions we can show Michael's FM Starting Point to 2020 light. We are actively unkinking the bugs that we discussed yesterday. We found out about that. And Mikey if you have a question and you folks have questions. If you're on twitch feel free to let us know what your question is. But it's kind of an open Q and A day. So, we want to make sure that we're answering that right? Yep. Answering questions because it's kind of wild all over the place and I just want to be responsive and help you out. So, if you have a question about some problem you're running into, throw it out. Today is the day. No penalty, no penalty as long as it's on topic which brings up one mention. I will mention Friday this week. We are doing the live stream. Jacob Taylor will be doing it with Calvin and they are talking about fixing the email.
Your email options for sending out kind of free emails through google mail or as an alternative to google mail. Because a lot of people have google accounts for free. They like their FileMaker to send out mails directly through that. So, if your CRM can send you an alert that an invoice was paid or something like that and a lot of that's going to get broken at the end of the month. So, we're trying to alert people that there will be a conversation for Friday. A very important conversation can. Art Ken has a question. I have about aws not FileMaker related is that Germaine to ask. Jacob I mean, Jacob, more or less because a lot of the ada, remember I mean Jacob can you show your screen. And just log on to aws and show us the interface. I mean I guess they have the new interface now. Which is a little bit cleaner but their interface used to be like a little icon and a sentence for each service they had.
Your email options for sending out kind of free emails through google mail or as an alternative to google mail. Because a lot of people have google accounts for free. They like their FileMaker to send out mails directly through that. So, if your CRM can send you an alert that an invoice was paid or something like that and a lot of that's going to get broken at the end of the month. So, we're trying to alert people that there will be a conversation for Friday. A very important conversation can. Art Ken has a question. I have about aws not FileMaker related is that Germaine to ask. Jacob I mean, Jacob, more or less because a lot of the ada, remember I mean Jacob can you show your screen. And just log on to aws and show us the interface. I mean I guess they have the new interface now. Which is a little bit cleaner but their interface used to be like a little icon and a sentence for each service they had.
And they had like 160, or 70, or 80, or 200, services. It's just it's like the ultimate playhouse for a programmer type person okay. So, this is a little bit can you Jacob your screen is a little bit. Can you go to chrome and say view, say view and make it a little bit bigger. You don't have to redo your screen. Just make the web page bigger. There you go. More 1. 15 there we go Jacob. There we go. That's good. So, this is kind of a db down thing but easy for those of you just wondering real quick right. This is where you have virtual servers right that we set up your FileMaker server. This is a simple email service. We'll be talking about on Friday route 53 is DNS control. I have no idea what light sale is? Apple tiny virtual machines really yep. It's like fully managed. So, I forget there's a light sail and there's another one that I always confuse the two, but they. And this is why Amazon has like 1500 services or some disgusting number of things. They have a service that hits every part of the market. It's like ec2 is Jacob. It's virtual machines which is from your perspective not different from light sale except ec2 is we manage it and you can do like fleets of servers. Light sail is its bubble. We don't have to care, we don't boot it. There's no kind of containerization a little bit or that kind of correct Jacob. So, it’s more, it's like two steps toward a managed system right? Okay. So, that you can put your code up there and it runs.
And they had like 160, or 70, or 80, or 200, services. It's just it's like the ultimate playhouse for a programmer type person okay. So, this is a little bit can you Jacob your screen is a little bit. Can you go to chrome and say view, say view and make it a little bit bigger. You don't have to redo your screen. Just make the web page bigger. There you go. More 1. 15 there we go Jacob. There we go. That's good. So, this is kind of a db down thing but easy for those of you just wondering real quick right. This is where you have virtual servers right that we set up your FileMaker server. This is a simple email service. We'll be talking about on Friday route 53 is DNS control. I have no idea what light sale is? Apple tiny virtual machines really yep. It's like fully managed. So, I forget there's a light sail and there's another one that I always confuse the two, but they. And this is why Amazon has like 1500 services or some disgusting number of things. They have a service that hits every part of the market. It's like ec2 is Jacob. It's virtual machines which is from your perspective not different from light sale except ec2 is we manage it and you can do like fleets of servers. Light sail is its bubble. We don't have to care, we don't boot it. There's no kind of containerization a little bit or that kind of correct Jacob. So, it’s more, it's like two steps toward a managed system right? Okay. So, that you can put your code up there and it runs.
But, there's a lot less of the detail that you have to pay attention to. Amazon kind of runs it for you. If you will, okay. So, I'm gonna come back to Mikey's question in a second. First question is migrating FileMaker server external storage to something a mere mortal can accomplish or does it take a superman like Jacob Taylor. What does that mean? External actually container data Jacob but is it just stored external securely? You can bring that over? Yep, if you have it. Okay, backup. How would you handle that right because you would have that. You would have the FileMaker. Can you go into a directory? Let's talk about this. Can you log into an ec2 server? I don't know which one and let's dig in. I have development systems. That's it Jacob, that's all we do. Let's go to a development system. Let's do that. Let me hide that Jacob. You're on my m1. So, you get everything. I only have one screen. So, that's fine. So, this is our West Coast development server. It's got a ton of stuff on it. So, what do you want to demo? So, just go. Let's just find that if we wanted to navigate to the path where the FileMaker is on the machine it should be on the C drive. Wherever the hell that's at. So, there's a C drive and can we. I'm gonna kind of zoom in on it. This is a little bit here. So, we went to the C drive down here, okay there's your path. And then program files FileMaker. FileMaker server. And then it should be data yep and then databases databases yep okay click on that. And then, any? There's nothing. Here is this. That's correct not in use okay okay. No, it's a fact. It's got like 40. It's got 50 databases on it. 48 I think. How come I can't see them? They're not here. We don't put them in this. This is the default database directory. Okay. That's what I'm drinking databases in here Jacob. We do, for our aws servers. We do not put databases on the C drive period.
But, there's a lot less of the detail that you have to pay attention to. Amazon kind of runs it for you. If you will, okay. So, I'm gonna come back to Mikey's question in a second. First question is migrating FileMaker server external storage to something a mere mortal can accomplish or does it take a superman like Jacob Taylor. What does that mean? External actually container data Jacob but is it just stored external securely? You can bring that over? Yep, if you have it. Okay, backup. How would you handle that right because you would have that. You would have the FileMaker. Can you go into a directory? Let's talk about this. Can you log into an ec2 server? I don't know which one and let's dig in. I have development systems. That's it Jacob, that's all we do. Let's go to a development system. Let's do that. Let me hide that Jacob. You're on my m1. So, you get everything. I only have one screen. So, that's fine. So, this is our West Coast development server. It's got a ton of stuff on it. So, what do you want to demo? So, just go. Let's just find that if we wanted to navigate to the path where the FileMaker is on the machine it should be on the C drive. Wherever the hell that's at. So, there's a C drive and can we. I'm gonna kind of zoom in on it. This is a little bit here. So, we went to the C drive down here, okay there's your path. And then program files FileMaker. FileMaker server. And then it should be data yep and then databases databases yep okay click on that. And then, any? There's nothing. Here is this. That's correct not in use okay okay. No, it's a fact. It's got like 40. It's got 50 databases on it. 48 I think. How come I can't see them? They're not here. We don't put them in this. This is the default database directory. Okay. That's what I'm drinking databases in here Jacob. We do, for our aws servers. We do not put databases on the C drive period.
We only put databases inside. We use that additional database directory. That's what Claris calls the feature in 16. There were two you could add two different additional database directories. They limited that to one which is fine because we don't use two of them. So, you put that on D is that what that is down here yep live databases. And then, backup Jacob okay. So, why don't you go and show us. But what I'm trying to do is show them. So, if there's your billion folders okay so open we need one. That's not a customer that is a test one that one okay. Hold on. There we go. This is. So, that we're in that directory and so what you have is you have the live files here and these files here will save into a directory called RC data FMS. So, this is where it is amazing to answer ED's question or attempt to answer it. All your remote containers whether it's secure, unsecured or not will all be in here. Whatever is needed to support these three. FileMaker files right. You could probably open that. Would it show you? I don't think there's anything Jacob. So, there will always be folders whether or not you have any. So, that's an empty folder. That is probably also empty and I'm expecting also empty so okay because there is no externally stored container data for these three databases in particular Jacob. And so, you would grab. So, when you move your stuff you would have to get this off of here along with the remote container directory right Jacob. You need both those together. So, it can mortally han move that themselves. And how would they just do that? The easiest way is just to zip it. So, go on your FileMaker. So, you're in migration mode. We're going to migrate. We're moving on to the new server. Yep, we're going to go in and we're going to close down the existing databases. So, they're capital C closed on the server. And then you can come in. And in this case right we're using the additional database directory. But normally it would be on the C drive and Jacob? So, you'd go over you'd come over here you go into FileMaker. FileMaker server yep, again if you're in a default database location your data and they would be in here okay. And so, what you can do is either grab stuff here. Maybe you have some old databases or whatever. So, there's two basic ways. They're both the same thing.
We only put databases inside. We use that additional database directory. That's what Claris calls the feature in 16. There were two you could add two different additional database directories. They limited that to one which is fine because we don't use two of them. So, you put that on D is that what that is down here yep live databases. And then, backup Jacob okay. So, why don't you go and show us. But what I'm trying to do is show them. So, if there's your billion folders okay so open we need one. That's not a customer that is a test one that one okay. Hold on. There we go. This is. So, that we're in that directory and so what you have is you have the live files here and these files here will save into a directory called RC data FMS. So, this is where it is amazing to answer ED's question or attempt to answer it. All your remote containers whether it's secure, unsecured or not will all be in here. Whatever is needed to support these three. FileMaker files right. You could probably open that. Would it show you? I don't think there's anything Jacob. So, there will always be folders whether or not you have any. So, that's an empty folder. That is probably also empty and I'm expecting also empty so okay because there is no externally stored container data for these three databases in particular Jacob. And so, you would grab. So, when you move your stuff you would have to get this off of here along with the remote container directory right Jacob. You need both those together. So, it can mortally han move that themselves. And how would they just do that? The easiest way is just to zip it. So, go on your FileMaker. So, you're in migration mode. We're going to migrate. We're moving on to the new server. Yep, we're going to go in and we're going to close down the existing databases. So, they're capital C closed on the server. And then you can come in. And in this case right we're using the additional database directory. But normally it would be on the C drive and Jacob? So, you'd go over you'd come over here you go into FileMaker. FileMaker server yep, again if you're in a default database location your data and they would be in here okay. And so, what you can do is either grab stuff here. Maybe you have some old databases or whatever. So, there's two basic ways. They're both the same thing.
But there's two ways to do it. One is just grab this whole database directory. I would still advise you to zip it unless your internet is blisteringly fast. and I mean like greater than gigabit like you have a 10 gig internet connection. I don't know anyone who does but maybe you do. Then you don't have to zip it. It probably doesn't matter but if it's anything less than that just do it. Because it makes it easier. So, there's two approaches. You zip this folder great. However, I will tell you if you've had the server installed for a long time. You will probably have a removed FMS directory in here with a bunch of old trash databases that people have uploaded five years ago or you know some previous server migration et cetera et cetera. And so, if you do that you'll bring everything with you. If that's intentional go for it. But Jacob the trick is that you want to make sure that cup that's your remote container data. And this is yours. You want to grab everything and all those have to go together to wherever the new server is. So, yep okay Jacob. And so, if you have a we'll say an out of the box FileMaker server configuration approximately. Then all you have to do is take whatever the contents of that are which will be your databases over here your FMP12s. a
But there's two ways to do it. One is just grab this whole database directory. I would still advise you to zip it unless your internet is blisteringly fast. and I mean like greater than gigabit like you have a 10 gig internet connection. I don't know anyone who does but maybe you do. Then you don't have to zip it. It probably doesn't matter but if it's anything less than that just do it. Because it makes it easier. So, there's two approaches. You zip this folder great. However, I will tell you if you've had the server installed for a long time. You will probably have a removed FMS directory in here with a bunch of old trash databases that people have uploaded five years ago or you know some previous server migration et cetera et cetera. And so, if you do that you'll bring everything with you. If that's intentional go for it. But Jacob the trick is that you want to make sure that cup that's your remote container data. And this is yours. You want to grab everything and all those have to go together to wherever the new server is. So, yep okay Jacob. And so, if you have a we'll say an out of the box FileMaker server configuration approximately. Then all you have to do is take whatever the contents of that are which will be your databases over here your FMP12s. a
And then, there's some other folders that will be in here too. The only one that you need capital and need is the RC data FMS okay. Bring that and the relevant databases over and plop them in the new space that's Jacob. Jacob, if you're on a Mac there's some permission that goes into that. If you're on windows. They are not okay. So, alright cool that's your rit people are messing with you. And then, okay maybe they are so alright, cool. So, Mikey had a question for Jacob.
And then, there's some other folders that will be in here too. The only one that you need capital and need is the RC data FMS okay. Bring that and the relevant databases over and plop them in the new space that's Jacob. Jacob, if you're on a Mac there's some permission that goes into that. If you're on windows. They are not okay. So, alright cool that's your rit people are messing with you. And then, okay maybe they are so alright, cool. So, Mikey had a question for Jacob.
And it's one that I'm probably more apt to answer because of the stuff that I do. Mikey says what is acceptable latency from aws to the client it's not. So, much from aws to the client it's acceptable latency you might Jacob your stuff is really small Jacob. So, Jacob if you want to adjust that or not really whatever it works for you. So, it's not so much from Amazon. Amazon happens to be where your server's at, it's really from your FileMaker server to your client. Claris officially says that they recommend a latency of less than 150 milliseconds. So, let's just give you some benchmark numbers real quick. So, what you're going to have. Sorry locally within your office, within your office locally, within your office, you're going to have one half a millisecond to 1. 5 milliseconds across town with good network connection. Like from one side of the bay area to the other side of the bay area across fremont or inside of portland or seattle or wherever los angeles some place london. You're gonna see less than 30 milliseconds, less than 30 milliseconds is pretty damn fast like FileMaker performance for everything that I do. Less than 30 is really great. It might be 45 but somewhere between 30 and 70. So, from one side of the United States from one side of the United States to the other side of the United States. So, like if I go to Margaret in Virginia and Margaret does a ping test. She might be as low as 70. 70 is as low as you're going to go from one side of the United States . 70 is starting to slow down. It's noticeable if you compare your speed like people say on-prem server. The server is in my office. It's so fast and I put it in the cloud and it slowed down so much.
And it's one that I'm probably more apt to answer because of the stuff that I do. Mikey says what is acceptable latency from aws to the client it's not. So, much from aws to the client it's acceptable latency you might Jacob your stuff is really small Jacob. So, Jacob if you want to adjust that or not really whatever it works for you. So, it's not so much from Amazon. Amazon happens to be where your server's at, it's really from your FileMaker server to your client. Claris officially says that they recommend a latency of less than 150 milliseconds. So, let's just give you some benchmark numbers real quick. So, what you're going to have. Sorry locally within your office, within your office locally, within your office, you're going to have one half a millisecond to 1. 5 milliseconds across town with good network connection. Like from one side of the bay area to the other side of the bay area across fremont or inside of portland or seattle or wherever los angeles some place london. You're gonna see less than 30 milliseconds, less than 30 milliseconds is pretty damn fast like FileMaker performance for everything that I do. Less than 30 is really great. It might be 45 but somewhere between 30 and 70. So, from one side of the United States from one side of the United States to the other side of the United States. So, like if I go to Margaret in Virginia and Margaret does a ping test. She might be as low as 70. 70 is as low as you're going to go from one side of the United States . 70 is starting to slow down. It's noticeable if you compare your speed like people say on-prem server. The server is in my office. It's so fast and I put it in the cloud and it slowed down so much.
Well that's kind of a loose description. But if you put on the cloud it probably went down to 50 or 60 or 70. And you notice a difference of you know 50 times fifth five z five fifty times slower or percentage-wise five thousand percent slower right. That kind of thing. It's a big deal. it's not twice as slow because remember you're going from a half like one millisecond on average to 50 milliseconds right. That's it. So, your software has to be really optimized. You can't be doing a lot of crazy unstorage stories and stuff like that. So, Jacob, the numbers that you're looking for do you expect to see is one to one and a half in the office across town 30. When I go to Santa Clara from here and I don't think about the ping tools I don't think I have ping tools in here that work anymore in this computer right. Because they got rid of that stuff, they got rid of the pingy stuff. Oh I have a pink plotter I guess. I could try that. That was the old one Jacob , that's what I think. That was the one William liked Jacob. William liked this and he had me buy a license. So, I'm just going to use the free one right now. I'm going to move to the free one. I'm going to say close so the ping plotter is a Mac tool. So, I'm going to come over here. I'm gonna say I don't even know if it'll do this. Oh it is doing this okay great. So, I'm trying to read this here real quick but I started a ping on one of the addresses in our office in our network. And it's pinging away. Ping, ping, ping, ping, and so initially it was like clipping away. We were doing pretty well. Round trip in milliseconds right. So, that's your low number. You're supposed to have and for whatever reason it took a kind of a dp and so it's hard to see this. Let me zoom in on this a little bit. So, this was the current average minimum and then out of the blue I think we dropped some packets and something. So, this is the current level. So, 31 milliseconds round trip okay. So, when you do pings I guess those are round trips that last one was 75. So, a lot of times across Santa Clara it averages around 35 to 40. Santa Clara is 75 miles from here so 30 is pretty damn quick. I normally see 30 to 40 somewhere in there. That's what you have but then you'll be doing this along the way. Then you'll have some outliers where it takes a dp on you right or it totally loses the packet for whatever reason FileMaker. So, you have packets the speed of the packets and then the other issue that you have is if you have packets that are flying say like remember a packet is nothing more you know.
Well that's kind of a loose description. But if you put on the cloud it probably went down to 50 or 60 or 70. And you notice a difference of you know 50 times fifth five z five fifty times slower or percentage-wise five thousand percent slower right. That kind of thing. It's a big deal. it's not twice as slow because remember you're going from a half like one millisecond on average to 50 milliseconds right. That's it. So, your software has to be really optimized. You can't be doing a lot of crazy unstorage stories and stuff like that. So, Jacob, the numbers that you're looking for do you expect to see is one to one and a half in the office across town 30. When I go to Santa Clara from here and I don't think about the ping tools I don't think I have ping tools in here that work anymore in this computer right. Because they got rid of that stuff, they got rid of the pingy stuff. Oh I have a pink plotter I guess. I could try that. That was the old one Jacob , that's what I think. That was the one William liked Jacob. William liked this and he had me buy a license. So, I'm just going to use the free one right now. I'm going to move to the free one. I'm going to say close so the ping plotter is a Mac tool. So, I'm going to come over here. I'm gonna say I don't even know if it'll do this. Oh it is doing this okay great. So, I'm trying to read this here real quick but I started a ping on one of the addresses in our office in our network. And it's pinging away. Ping, ping, ping, ping, and so initially it was like clipping away. We were doing pretty well. Round trip in milliseconds right. So, that's your low number. You're supposed to have and for whatever reason it took a kind of a dp and so it's hard to see this. Let me zoom in on this a little bit. So, this was the current average minimum and then out of the blue I think we dropped some packets and something. So, this is the current level. So, 31 milliseconds round trip okay. So, when you do pings I guess those are round trips that last one was 75. So, a lot of times across Santa Clara it averages around 35 to 40. Santa Clara is 75 miles from here so 30 is pretty damn quick. I normally see 30 to 40 somewhere in there. That's what you have but then you'll be doing this along the way. Then you'll have some outliers where it takes a dp on you right or it totally loses the packet for whatever reason FileMaker. So, you have packets the speed of the packets and then the other issue that you have is if you have packets that are flying say like remember a packet is nothing more you know.
It's really hard for me to come up with an analogy on the fly. Here we go. Here's a paper towel all right. So, this is a paper towel. I'm gonna roll this up. This has a hundred. I think 100k of data into it, 100 k bytes of data in it. This is a little and so when you shoot data across the internet. This is a packet. It's whizzing back and forth like little pieces of paper like this. And what FileMaker does is that or a word docent or a browser or anything you do it chops. Whatever you're trying to view, even images up in these little packets and it shoots them across the network. And so, if you shoot a hundred of them across the network if all 100 of them get there, okay? Well you have no packet loss none of this died and literally died and disappeared right. It's like area 51. Did it die and disappear? So, it's how long it took for this to go. Latency is the delay it takes to go there right and the other one is packet loss which is a number of these that die out of a hundred. And so, when you have a one like this red one up here. There was some sort of packet where it sent like 100 amounts and one or two or five of them went away. When you get 10 packet loss, you're gonna start having some real problems with FileMaker because of the system. Whenever you do that on your computer the stuff is fault tolerant. It goes hey I sent 100 out and then 10 didn't make it and it can't reassemble the stuff on the other side without those missing 10. So, it has to resend them. So, it goes ah 10 dead so it's like if Amazon mails you a package and it never shows up well you're like well give me my package or I'm going to cancel my order with my credit card. Rubber rubber right. So, Amazon sends you the package again but there's a delay in you getting that package and you're pissed off.
It's really hard for me to come up with an analogy on the fly. Here we go. Here's a paper towel all right. So, this is a paper towel. I'm gonna roll this up. This has a hundred. I think 100k of data into it, 100 k bytes of data in it. This is a little and so when you shoot data across the internet. This is a packet. It's whizzing back and forth like little pieces of paper like this. And what FileMaker does is that or a word docent or a browser or anything you do it chops. Whatever you're trying to view, even images up in these little packets and it shoots them across the network. And so, if you shoot a hundred of them across the network if all 100 of them get there, okay? Well you have no packet loss none of this died and literally died and disappeared right. It's like area 51. Did it die and disappear? So, it's how long it took for this to go. Latency is the delay it takes to go there right and the other one is packet loss which is a number of these that die out of a hundred. And so, when you have a one like this red one up here. There was some sort of packet where it sent like 100 amounts and one or two or five of them went away. When you get 10 packet loss, you're gonna start having some real problems with FileMaker because of the system. Whenever you do that on your computer the stuff is fault tolerant. It goes hey I sent 100 out and then 10 didn't make it and it can't reassemble the stuff on the other side without those missing 10. So, it has to resend them. So, it goes ah 10 dead so it's like if Amazon mails you a package and it never shows up well you're like well give me my package or I'm going to cancel my order with my credit card. Rubber rubber right. So, Amazon sends you the package again but there's a delay in you getting that package and you're pissed off.
Welcome to the world of network computers right. So, very little packet loss is very good and having the packets whiz there back and forth as fast as possible is great. And so one one and a half milliseconds is the packet going from this desk to the next desk next door upstairs the third floor 30 to 40 milliseconds is this little thing going across town across the United States. It's 70 to the UK, it's like 150 to 180. I know that when we went to Mumbai India from here in California. It was 334. I remember that number very specifically more than double the allowable level, right? And so, that's where we got into this whole conversation. And I see my discord flashing over here. I'll answer in a second but that's where we got in the conversation with 360 works. Jesse Barn, who I should call while we're here and he came on the show and we talked about having a server in each continent. Because typically when you go across the ocean or under the ocean in a fiber optic line right that's where this is going to slow down some okay. Why do they slow down? Doesn't matter, it just does okay and we don't really care why but what's that physics? Well it's physics, it's physics, it's physical you're, you're Jacob. You're physically fiber. It's going to go really fast and that's great. But it hits some point 5 000 miles takes a second Jacob. So, you get the physics. It's going back and forth and so the point is that you set up a FileMaker server in India and used up a FileMaker server in Australia. You set up a FileMaker server in Japan. Set one up in maybe one Ireland and one in Germany. For example, I don't think you can set one up in Russia because then you'll be on someone's list if you put it in Ukraine. It probably won't work and then you put one on the East Coast in the United States. One the West Coast United States you get this idea. So, then each of those servers you're talking to your closest server.
Welcome to the world of network computers right. So, very little packet loss is very good and having the packets whiz there back and forth as fast as possible is great. And so one one and a half milliseconds is the packet going from this desk to the next desk next door upstairs the third floor 30 to 40 milliseconds is this little thing going across town across the United States. It's 70 to the UK, it's like 150 to 180. I know that when we went to Mumbai India from here in California. It was 334. I remember that number very specifically more than double the allowable level, right? And so, that's where we got into this whole conversation. And I see my discord flashing over here. I'll answer in a second but that's where we got in the conversation with 360 works. Jesse Barn, who I should call while we're here and he came on the show and we talked about having a server in each continent. Because typically when you go across the ocean or under the ocean in a fiber optic line right that's where this is going to slow down some okay. Why do they slow down? Doesn't matter, it just does okay and we don't really care why but what's that physics? Well it's physics, it's physics, it's physical you're, you're Jacob. You're physically fiber. It's going to go really fast and that's great. But it hits some point 5 000 miles takes a second Jacob. So, you get the physics. It's going back and forth and so the point is that you set up a FileMaker server in India and used up a FileMaker server in Australia. You set up a FileMaker server in Japan. Set one up in maybe one Ireland and one in Germany. For example, I don't think you can set one up in Russia because then you'll be on someone's list if you put it in Ukraine. It probably won't work and then you put one on the East Coast in the United States. One the West Coast United States you get this idea. So, then each of those servers you're talking to your closest server.
So, you're doing that and then the servers themselves are bundling up the changes and communicating like you make a change this record Fred Smith in your CRM. And then 20 or 30 seconds later after you change it in California it updates to like Mumbai India and Frankfurt Germany and Ireland. So, that's server replication, a different topic but this is super relevant. And if you're new to FileMaker you're probably new to this tech unless you come from a tech world. Most people come to FileMaker; they're not necessarily super technical and you don't have to be like the crazy programmer type. But you need to understand some basic physics of how networks work because they're frankly the limiting factors in the world of FileMaker right. So, there you go so sorry about that I go way off in the weeds. Jacob, you want to pick up the questions here? Sure.That's also a good that's my summary of like later versions of FileMaker at this point they've eliminated most of what I call the internal application latency. Which is like FileMaker Pro has to wait to get something done or FileMaker server is like not optimized. And so it's the thing that's making your app slow later versions of 19 essentially because of the work Claris has put in. Do not have that problem anymore. And so, we are 100 back to the purest and most boring advice for FileMaker which is the old stuff. You are trying to avoid network latency because it is the biggest thing that eats your application performance. Everything else is basically fast. Jacob you know some features of this and the other thing there's details. I'm ignoring here but for the most part you're sorting is always a problem and Clarissa tried to fix it but it's still an issue and smarizing blocks talking about those forthcoming details on that Jacob. Yep, conveniently enough if you want.
So, you're doing that and then the servers themselves are bundling up the changes and communicating like you make a change this record Fred Smith in your CRM. And then 20 or 30 seconds later after you change it in California it updates to like Mumbai India and Frankfurt Germany and Ireland. So, that's server replication, a different topic but this is super relevant. And if you're new to FileMaker you're probably new to this tech unless you come from a tech world. Most people come to FileMaker; they're not necessarily super technical and you don't have to be like the crazy programmer type. But you need to understand some basic physics of how networks work because they're frankly the limiting factors in the world of FileMaker right. So, there you go so sorry about that I go way off in the weeds. Jacob, you want to pick up the questions here? Sure.That's also a good that's my summary of like later versions of FileMaker at this point they've eliminated most of what I call the internal application latency. Which is like FileMaker Pro has to wait to get something done or FileMaker server is like not optimized. And so it's the thing that's making your app slow later versions of 19 essentially because of the work Claris has put in. Do not have that problem anymore. And so, we are 100 back to the purest and most boring advice for FileMaker which is the old stuff. You are trying to avoid network latency because it is the biggest thing that eats your application performance. Everything else is basically fast. Jacob you know some features of this and the other thing there's details. I'm ignoring here but for the most part you're sorting is always a problem and Clarissa tried to fix it but it's still an issue and smarizing blocks talking about those forthcoming details on that Jacob. Yep, conveniently enough if you want.
To learn about those performance issues you should come here to FM Training and check out the bundles we have and purchase one of these two bundles because within these bundles is our FileMaker platform Pro course right. Here we spend about 10 hours, 12 hours and this is updated over the last year with very specific performance tuning tips and tricks for that. So, once again stuff that even Jacob doesn't know doesn't worry about it doesn't really care because he doesn't code this stuff. But stuff that you need to know is okay, very very very important. So, if you're building a solution with more than say 20 or 30 people accessing at one time and or the server is far away from you in terms of milliseconds like at lEast more than 30. You need to start thinking about this stuff. So, that is cool all right. Mikey took care of that holler. If you want advice on distributed teams you can access yes he was asking about the application latency question. What's an acceptable latency? I'm useful at picking locations for servers. If your people are too terribly distributed then we tell you to get mirror sync or something like that because you should just have two servers. Essentially if people are Jacob. If your teams are too far apart I'll never forget the client we have where their two offices were in Paris and Tokyo. I can't. There's no I can't square that circle Jacob. Jacob, who was a hard one of those teams, is getting screwed. That's the stuff Jacob Jacob Jacob here's the, here is the animations that we made to describe this server replication stuff. So, let me see if this is right here. So, this is the world and so what happens is you determine that there's too much latency like if your one server is here.
To learn about those performance issues you should come here to FM Training and check out the bundles we have and purchase one of these two bundles because within these bundles is our FileMaker platform Pro course right. Here we spend about 10 hours, 12 hours and this is updated over the last year with very specific performance tuning tips and tricks for that. So, once again stuff that even Jacob doesn't know doesn't worry about it doesn't really care because he doesn't code this stuff. But stuff that you need to know is okay, very very very important. So, if you're building a solution with more than say 20 or 30 people accessing at one time and or the server is far away from you in terms of milliseconds like at lEast more than 30. You need to start thinking about this stuff. So, that is cool all right. Mikey took care of that holler. If you want advice on distributed teams you can access yes he was asking about the application latency question. What's an acceptable latency? I'm useful at picking locations for servers. If your people are too terribly distributed then we tell you to get mirror sync or something like that because you should just have two servers. Essentially if people are Jacob. If your teams are too far apart I'll never forget the client we have where their two offices were in Paris and Tokyo. I can't. There's no I can't square that circle Jacob. Jacob, who was a hard one of those teams, is getting screwed. That's the stuff Jacob Jacob Jacob here's the, here is the animations that we made to describe this server replication stuff. So, let me see if this is right here. So, this is the world and so what happens is you determine that there's too much latency like if your one server is here.
There's too much latency around the world. So, you put a FileMaker server literally where most of your users are at. So, this is the West Coast of the United States. East Coast one in Europe, Ireland would be over there somewhere. This is India. That's Japan. That's Australia. And so, if I press play here the idea was that file that mirrorsync is a product and see where it is. It goes down. Mirror sync is a product that when everything's running that these all these report in their changes to here and they also then kind of go say hey what other changes. Do I need that? I need updates to and so you report a change and then it keeps it's a hub. So, this is the hub and these are spokes. If you have two servers it's fine. One's a hub, one's a spoke but the idea that these things here's the part with this goes down. These continue to run. They totally continue to run. Now their data might be slightly out of sync etc. But for the most part if you have a big team that's and they're all trying to edit the same record they can all run independently. And then what ends up happening is that the server gets restarted right. You put the server back up, you turn it on and then these things go through a very aggressive process of getting caught up on their stinky stuff so fault tolerant. Now the other part of this one is a great one here. So, watch this. This is great. So, same deal right. But we people will connect to the closest one of the things that Jesse showed us. How people connect to the closest server right. So, these are all running. And so, the people that these happen to be people that are West Coast. They connect here and they're the closest one there.
There's too much latency around the world. So, you put a FileMaker server literally where most of your users are at. So, this is the West Coast of the United States. East Coast one in Europe, Ireland would be over there somewhere. This is India. That's Japan. That's Australia. And so, if I press play here the idea was that file that mirrorsync is a product and see where it is. It goes down. Mirror sync is a product that when everything's running that these all these report in their changes to here and they also then kind of go say hey what other changes. Do I need that? I need updates to and so you report a change and then it keeps it's a hub. So, this is the hub and these are spokes. If you have two servers it's fine. One's a hub, one's a spoke but the idea that these things here's the part with this goes down. These continue to run. They totally continue to run. Now their data might be slightly out of sync etc. But for the most part if you have a big team that's and they're all trying to edit the same record they can all run independently. And then what ends up happening is that the server gets restarted right. You put the server back up, you turn it on and then these things go through a very aggressive process of getting caught up on their stinky stuff so fault tolerant. Now the other part of this one is a great one here. So, watch this. This is great. So, same deal right. But we people will connect to the closest one of the things that Jesse showed us. How people connect to the closest server right. So, these are all running. And so, the people that these happen to be people that are West Coast. They connect here and they're the closest one there.
These people log in here and Amazon knows that based upon latency, a little latency. Check it knows what they're closest to right, it's pretty slick. You got people up here. People over here. So, you could have thousands of people using your FileMaker solution easily. But each server is only handling two or three hundred maybe right. And then, say for example, there's a problem right one of them blows up. These people get disconnected that'll eventually happen here at some point if one blows up. So, these people down here are disconnected right and then they close FileMaker, reopen it and Amazon goes to the closest server. Now is this one because this one is no longer responding right and so they are so not only is it replication and scalability it's also this kind of failover thing now once these people are connected to this. It's not going to automatically transfer them back. But once they quit FileMaker they close the databases and reopen them. They would be redirected back to the closest one okay. Does it make sense? This is pretty bad. Let me. It's very clear. This is some bad we did this over a week with Jesse Barn. The 360 works for a client probably I don't know it'll depend on their schedule but this week or next. Probably you're going to set this exact thing up Jacob, okay. One of our engineers is building the mirror sync part of it so that's the one of the high latency portions of this. But the other half of it is the aws part of the route 53 configuration which is. What lets you do that balancing between the different nodes where you know people in Australia go to the Australian server. And so, on the right they have the same problem there. They have a team over. Forget it. They're in Manila I think. So, Jacob and then but there's a bunch of people in the UK. They have a bunch of people in Turkey. They wanted servers for those people and okay. Because right you go talk all the way to man. Well we need to get our demo with product 360 back and running again. I'm going to yell at Jesse about that. I know he's been busy. Can I pivot real quick? So, there is a question from David Angel he wants to ask about productive, productive progressive backups or IB incremental backups engineering calls on incremental backups.
These people log in here and Amazon knows that based upon latency, a little latency. Check it knows what they're closest to right, it's pretty slick. You got people up here. People over here. So, you could have thousands of people using your FileMaker solution easily. But each server is only handling two or three hundred maybe right. And then, say for example, there's a problem right one of them blows up. These people get disconnected that'll eventually happen here at some point if one blows up. So, these people down here are disconnected right and then they close FileMaker, reopen it and Amazon goes to the closest server. Now is this one because this one is no longer responding right and so they are so not only is it replication and scalability it's also this kind of failover thing now once these people are connected to this. It's not going to automatically transfer them back. But once they quit FileMaker they close the databases and reopen them. They would be redirected back to the closest one okay. Does it make sense? This is pretty bad. Let me. It's very clear. This is some bad we did this over a week with Jesse Barn. The 360 works for a client probably I don't know it'll depend on their schedule but this week or next. Probably you're going to set this exact thing up Jacob, okay. One of our engineers is building the mirror sync part of it so that's the one of the high latency portions of this. But the other half of it is the aws part of the route 53 configuration which is. What lets you do that balancing between the different nodes where you know people in Australia go to the Australian server. And so, on the right they have the same problem there. They have a team over. Forget it. They're in Manila I think. So, Jacob and then but there's a bunch of people in the UK. They have a bunch of people in Turkey. They wanted servers for those people and okay. Because right you go talk all the way to man. Well we need to get our demo with product 360 back and running again. I'm going to yell at Jesse about that. I know he's been busy. Can I pivot real quick? So, there is a question from David Angel he wants to ask about productive, productive progressive backups or IB incremental backups engineering calls on incremental backups.
Frankly, what Claris calls them and what the engineering team at Claris's calls them are two different things. But Jacob so we want, you want to share your screen talk about that a little bit. Sure. Very tiny detail. If you ever look in the list of FileMaker services. You'll see an FMSIB. You can guess what Jacob. We can't see your screen. I haven't shared my phone. You're sharing stuff verbally. But I really I'm talking while I get the windows ready. It's a fake. It's a decoy. Got it Jacob all right all right. So, here we go. So, you want incremental backups all right. So, incremental backups are where they are located. No, it's on configuration. Isn't it Jacob? So, admin console right this exists for it's been almost almost the same. Not quite unchanged but very close since 17. This feature is located in the same place in all of them which is the folders yes. And so, you can come here and this is the backup folders. And so, you're not on by default. This is just literally clicking enable Jacob so and I since I worked here several years ago didn't really turn them on. And I was changing the policy back to what was basically the original policy when I was hired at RCC. Which was to enable progressive backups. The reason for that is because previous to it may have changed in like 1903. It's a very recent change. The incremental backup system when it runs. Now logs into the event log that it's doing. So, it's running. This backup is running. It's the five minute blah blah blah. These databases got backed up. These ones did not etc etc. It has its little like running thought of what it's doing and that's great in it. And what that means is that I can now identify the individual FileMaker databases that got backed up. And which backup is good. So, for example because the at East by default progressive backups run every five minutes. That's awesome. It means you will know ideally you'll basically lose no data in case of a crash. However, in case of a crash you do need to know what the last one that ran was. And so, for simplicity purposes because one of them is not solely that the backup system has to work when you're doing a crash restoration.
Frankly, what Claris calls them and what the engineering team at Claris's calls them are two different things. But Jacob so we want, you want to share your screen talk about that a little bit. Sure. Very tiny detail. If you ever look in the list of FileMaker services. You'll see an FMSIB. You can guess what Jacob. We can't see your screen. I haven't shared my phone. You're sharing stuff verbally. But I really I'm talking while I get the windows ready. It's a fake. It's a decoy. Got it Jacob all right all right. So, here we go. So, you want incremental backups all right. So, incremental backups are where they are located. No, it's on configuration. Isn't it Jacob? So, admin console right this exists for it's been almost almost the same. Not quite unchanged but very close since 17. This feature is located in the same place in all of them which is the folders yes. And so, you can come here and this is the backup folders. And so, you're not on by default. This is just literally clicking enable Jacob so and I since I worked here several years ago didn't really turn them on. And I was changing the policy back to what was basically the original policy when I was hired at RCC. Which was to enable progressive backups. The reason for that is because previous to it may have changed in like 1903. It's a very recent change. The incremental backup system when it runs. Now logs into the event log that it's doing. So, it's running. This backup is running. It's the five minute blah blah blah. These databases got backed up. These ones did not etc etc. It has its little like running thought of what it's doing and that's great in it. And what that means is that I can now identify the individual FileMaker databases that got backed up. And which backup is good. So, for example because the at East by default progressive backups run every five minutes. That's awesome. It means you will know ideally you'll basically lose no data in case of a crash. However, in case of a crash you do need to know what the last one that ran was. And so, for simplicity purposes because one of them is not solely that the backup system has to work when you're doing a crash restoration.
That's important of course. But the second part is don't torture the person who's doing the backup restoration right. And so, you wanna streamline the thought process because their hair is going to be on fire. And the business is down and maybe their boss is yelling at them and whatever because they need to get the business back up and back up and running again. And so, one of the things that we go through with restoration processes is not merely like which is a good backup copy but also like is it easy to choose that is it easy to determine which backup is good. And so, I had previously just basically not set up progressives on a lot of servers because of that. Because there was no way to tell if for example the most recent progressive backup had completed at crash time. You have no idea. There's a log entry. Now we can validate that so really yes Jacob 100 okay. And so, Jacob I found that was not naming the client but one of our on-site server customers they had their own internal policy. Said no, we absolutely have to have incremental backups and I was like perfectly done. Turned it on, you know, took them live, did some other stuff. I came back and looked at the event log and found point by point entries every single individual database every five minutes. Which ones got backed up and I was like I have to eat my words. So, Jacob turned it on. Now normally the way we would do it is I would never use the very last backup. I would go back just because I didn't have time to check the logs correctly. Yes, I wouldn't use the last backup. I'd use the one before that the one previous because you can say well, well if it got to the last backup. Probably the previous one. Probably finished successfully right.So correct right? And so,that and that's that's a hundred percent true.
That's important of course. But the second part is don't torture the person who's doing the backup restoration right. And so, you wanna streamline the thought process because their hair is going to be on fire. And the business is down and maybe their boss is yelling at them and whatever because they need to get the business back up and back up and running again. And so, one of the things that we go through with restoration processes is not merely like which is a good backup copy but also like is it easy to choose that is it easy to determine which backup is good. And so, I had previously just basically not set up progressives on a lot of servers because of that. Because there was no way to tell if for example the most recent progressive backup had completed at crash time. You have no idea. There's a log entry. Now we can validate that so really yes Jacob 100 okay. And so, Jacob I found that was not naming the client but one of our on-site server customers they had their own internal policy. Said no, we absolutely have to have incremental backups and I was like perfectly done. Turned it on, you know, took them live, did some other stuff. I came back and looked at the event log and found point by point entries every single individual database every five minutes. Which ones got backed up and I was like I have to eat my words. So, Jacob turned it on. Now normally the way we would do it is I would never use the very last backup. I would go back just because I didn't have time to check the logs correctly. Yes, I wouldn't use the last backup. I'd use the one before that the one previous because you can say well, well if it got to the last backup. Probably the previous one. Probably finished successfully right.So correct right? And so,that and that's that's a hundred percent true.
And so, for customers that 100 percent want quick backup restorations right. They have data that cannot be reproduced easily. Like we call them high-speed systems. It's not so much about the application performance but about the data and like a lot you know because a lot of businesses can go back and re-enter an invoice really quickly or regenerate a pdf. That's based on record data that's already in there you know. Stuff like that. It's like, it's not that hard to go back and get the data again. And so, but for customers that are like no we have data flowing into this thing that it's difficult or impossible to you know to make it flow back in again. Whatever that means for those customers we would just do 15 minute backups because those backup schedules like any regular backup schedule logs every time it runs. And so, that's not terribly different from a 10 minute old backup right. 10 to 15 is not a huge difference and that basically meets their requirements. However I don't have to do that anymore. And that's because we now have logged progressive backup runs. And so, Jacob we can just do 100. That we can just restore from the progressive backups because we can go look at the event log. And validate particular databases that have been backed up and that process completed all right. So, let me talk about two things here that have popped up relative to this conversation. David is asking the question. I don't know if he's answering his own question or not. So, wait the way that progressive backups work and I could dig this out of a directory. I'm not going to bother when you start progressive backups. It writes to a directory a complete snapshot of all your databases. And the containers too the remote containers too then every whatever the increment time period is I guess I could zoom over here. And look at this. I wasn't looking at this but let me zoom back in here. There it is okay there. So, here let me. Can you zoom man I tell you Jacob no no okay. I'm zooming but it's something that's simulated. I don't even feel okay. But this is really ugly okay. So, what it does is the incremental backup system. Maintains two backups. It's the last two that it's created.
And so, for customers that 100 percent want quick backup restorations right. They have data that cannot be reproduced easily. Like we call them high-speed systems. It's not so much about the application performance but about the data and like a lot you know because a lot of businesses can go back and re-enter an invoice really quickly or regenerate a pdf. That's based on record data that's already in there you know. Stuff like that. It's like, it's not that hard to go back and get the data again. And so, but for customers that are like no we have data flowing into this thing that it's difficult or impossible to you know to make it flow back in again. Whatever that means for those customers we would just do 15 minute backups because those backup schedules like any regular backup schedule logs every time it runs. And so, that's not terribly different from a 10 minute old backup right. 10 to 15 is not a huge difference and that basically meets their requirements. However I don't have to do that anymore. And that's because we now have logged progressive backup runs. And so, Jacob we can just do 100. That we can just restore from the progressive backups because we can go look at the event log. And validate particular databases that have been backed up and that process completed all right. So, let me talk about two things here that have popped up relative to this conversation. David is asking the question. I don't know if he's answering his own question or not. So, wait the way that progressive backups work and I could dig this out of a directory. I'm not going to bother when you start progressive backups. It writes to a directory a complete snapshot of all your databases. And the containers too the remote containers too then every whatever the increment time period is I guess I could zoom over here. And look at this. I wasn't looking at this but let me zoom back in here. There it is okay there. So, here let me. Can you zoom man I tell you Jacob no no okay. I'm zooming but it's something that's simulated. I don't even feel okay. But this is really ugly okay. So, what it does is the incremental backup system. Maintains two backups. It's the last two that it's created.
And what it does is when it's gonna go and create the next incremental backup. First, what it does is it essentially snapshots a new folder okay. And then it finds all the changes that FileMaker server has made in that time window. And write them in there okay. It's very interesting. So, it's only writing the data changes that have occurred. So, if five five. If you have a hundred files and five files have been changed. It doesn't rewrite those five files. It's just gonna write the blocks of data within the file that changed. It sounds very dangerous but it's been working really reliably for a number of years. So, I'm comfortable in saying that it works without Jacob. They actually have recently fixed up and patched a couple bugs in it. So, it works even more reliably than it ever has okay Jacob. So, the idea is that then it creates this third one right and you don't see it happen. There's three of them here. And then, once it's got a third one that's totally completed. It takes the oldest one and it just deletes it okay. And so, you always have two good ones. So, this is an incremental backup so that's how that works. I don't see any questions at the moment. Let me pivot to something slightly. And this came up with Jacob yesterday. Today I've been living in dog years because of all the clerish frankly shenanigans it's been very stressful. In fact I don't have any acne on my face. Most of my zits have gone away because I was breaking on acne due to all the stress that they're putting me under with the crazy stuff they're doing. It's not a little bit. It's a lot we're going to deal with that on Monday, Tuesday, next week so Jacob got into this issue today. And he just mentioned it briefly again as is your server restoration process. And I remember Chris Moyer and Heidi Porter talking about having a written checklist at the event. That there's some sort of ransomware attack. Well, before you even get to something that level you should have a written process and actually it should probably be a live stream that we do. And I don't know if you could do it in one day Jacob.
And what it does is when it's gonna go and create the next incremental backup. First, what it does is it essentially snapshots a new folder okay. And then it finds all the changes that FileMaker server has made in that time window. And write them in there okay. It's very interesting. So, it's only writing the data changes that have occurred. So, if five five. If you have a hundred files and five files have been changed. It doesn't rewrite those five files. It's just gonna write the blocks of data within the file that changed. It sounds very dangerous but it's been working really reliably for a number of years. So, I'm comfortable in saying that it works without Jacob. They actually have recently fixed up and patched a couple bugs in it. So, it works even more reliably than it ever has okay Jacob. So, the idea is that then it creates this third one right and you don't see it happen. There's three of them here. And then, once it's got a third one that's totally completed. It takes the oldest one and it just deletes it okay. And so, you always have two good ones. So, this is an incremental backup so that's how that works. I don't see any questions at the moment. Let me pivot to something slightly. And this came up with Jacob yesterday. Today I've been living in dog years because of all the clerish frankly shenanigans it's been very stressful. In fact I don't have any acne on my face. Most of my zits have gone away because I was breaking on acne due to all the stress that they're putting me under with the crazy stuff they're doing. It's not a little bit. It's a lot we're going to deal with that on Monday, Tuesday, next week so Jacob got into this issue today. And he just mentioned it briefly again as is your server restoration process. And I remember Chris Moyer and Heidi Porter talking about having a written checklist at the event. That there's some sort of ransomware attack. Well, before you even get to something that level you should have a written process and actually it should probably be a live stream that we do. And I don't know if you could do it in one day Jacob.
But I want to create this and book it out for a couple months when we're done with the 30a CRM. So, this is the flight manual for let me flip. I don't think that's backwards. Let me flip this around. So, you all can see it. This is the flight manual for my helicopter, okay. I'm a pilot and I'm a commercial pilot. So, I have to basically memorize this mother book plus a lot of stuff. Now this is relevant because I've talked about this before in the event of an emergency in the helicopter. There's the one tab we all see that says right there emergency procedures now with a helicopter. Everything happens so fast. It has to be automatic but in a cessna I remember when I first learned an assessment years ago that most of it that happens at cessna happens slow enough. That you can actually have the section on emergency procedures out on a card and you can reference it right like airline pilots and stuff. Mostly follow a checklist because when you're flying at 30 000 feet and there's an emergency unless the wing falls off or something. They have time to read the checklist in a helicopter. You have to have it memorized but let's just pretend. So, you really need that we need to have for every one of you here who has a FileMaker server. You need to have an emergency checklist that is printed that is hanging next to your server that you can follow. So, topics for a power failure to your FileMaker server. I'm adapting this from my power failure right now. Power failure to the internet. Power failure because someone plugs a vacu into this into the same power switch as the server. No, I've had that happen to a power failure due to a three-year-old pushing the power off button on the battery backup okay. You could kind of condense those down right. FileMaker server becomes unresponsive due to unknown issue. What is your procedure on that, righ? Customer reports unable to connect okay. What is your process on that? Normally most people don't give it but within all your customers report the same problem. Then it's probably your issue. What is your process on that, right?
But I want to create this and book it out for a couple months when we're done with the 30a CRM. So, this is the flight manual for let me flip. I don't think that's backwards. Let me flip this around. So, you all can see it. This is the flight manual for my helicopter, okay. I'm a pilot and I'm a commercial pilot. So, I have to basically memorize this mother book plus a lot of stuff. Now this is relevant because I've talked about this before in the event of an emergency in the helicopter. There's the one tab we all see that says right there emergency procedures now with a helicopter. Everything happens so fast. It has to be automatic but in a cessna I remember when I first learned an assessment years ago that most of it that happens at cessna happens slow enough. That you can actually have the section on emergency procedures out on a card and you can reference it right like airline pilots and stuff. Mostly follow a checklist because when you're flying at 30 000 feet and there's an emergency unless the wing falls off or something. They have time to read the checklist in a helicopter. You have to have it memorized but let's just pretend. So, you really need that we need to have for every one of you here who has a FileMaker server. You need to have an emergency checklist that is printed that is hanging next to your server that you can follow. So, topics for a power failure to your FileMaker server. I'm adapting this from my power failure right now. Power failure to the internet. Power failure because someone plugs a vacu into this into the same power switch as the server. No, I've had that happen to a power failure due to a three-year-old pushing the power off button on the battery backup okay. You could kind of condense those down right. FileMaker server becomes unresponsive due to unknown issue. What is your procedure on that, righ? Customer reports unable to connect okay. What is your process on that? Normally most people don't give it but within all your customers report the same problem. Then it's probably your issue. What is your process on that, right?
And so, you really need to have it after you flip open the red tab. You need to have a section on what you do right one of the what do you do in the event that your FileMaker server has to land in the water right. That's good actually. That's no, what happens if your FileMaker server is drowned like a rat. We had a customer two years ago and drowned like a rat. Another customer where someone broke into their office. It was in a closet and the machine was in the closet. Therefore it must be important. And so, they stole the machine and the two backups that were attached to it okay. What do you do about that right? All these things you need to be prepared for and can I just state that you need to write it out and we've had. I've had Jacob it was this morning you were telling me about a customer named blah who even though we've written them out. They either don't follow it or they don't want to follow it or they're too stressed to follow the checklist. But the checklist is here to keep you alive right or your database of life right so and that particular customer the it's it's a it's a classic example. The ID person is not familiar with FileMaker at all. They can operate Pro, well enough that they recently learned how to create a new database which is perfect. That's exactly who we want to target, also that person is responsible for the server and so it is what I say those people will try to get the business back up and running because that is what they have been tasked with that's their job. They may do that better or worse they can, they can follow those directions and that emergency checklist better or worse.
And so, you really need to have it after you flip open the red tab. You need to have a section on what you do right one of the what do you do in the event that your FileMaker server has to land in the water right. That's good actually. That's no, what happens if your FileMaker server is drowned like a rat. We had a customer two years ago and drowned like a rat. Another customer where someone broke into their office. It was in a closet and the machine was in the closet. Therefore it must be important. And so, they stole the machine and the two backups that were attached to it okay. What do you do about that right? All these things you need to be prepared for and can I just state that you need to write it out and we've had. I've had Jacob it was this morning you were telling me about a customer named blah who even though we've written them out. They either don't follow it or they don't want to follow it or they're too stressed to follow the checklist. But the checklist is here to keep you alive right or your database of life right so and that particular customer the it's it's a it's a classic example. The ID person is not familiar with FileMaker at all. They can operate Pro, well enough that they recently learned how to create a new database which is perfect. That's exactly who we want to target, also that person is responsible for the server and so it is what I say those people will try to get the business back up and running because that is what they have been tasked with that's their job. They may do that better or worse they can, they can follow those directions and that emergency checklist better or worse.
In this case they did not have an emergency checklist. And so, most people don't have a written emergency checklist. And we talked about this. So, should we do a live stream where we actually kind of have a kind of a blank one that we kind of give to everyone and we kind of fill out along the way and give them a chat we can do. We can cover about one variant of that per live stream. It's huge because people have to have a if you want to cover all of the network somebody's you know connectivity problem went down something like that. How do we troubleshoot that I can do all of those because that's my job but do we have any buzzing? Do people like the checklist? Do you like the checklist stu stu I don't know a stu's marshal guy or what stu is. But I guarantee if you're in the navy and it's action stations or whatever the hell you guys call it there. I think that's a British term, you guys have an emergency plan. There's an emergency checklist for damn near everything right you know pull pull rip the handle and send in the marines right. So, Jacob you guys have one pre Jacob I have. Like a written out one. I believe for what it's pointers for the basic case which is like FileMaker servers like not running or something the machine went down. And like what do you do Jacob? Restore from backups that's what you do Jacob. But what does that look like, right? So, correct Jacob yep and that's what this person was having like challenges with is they had heard some of this stuff but and so their their boss who of course was on vacation because nothing ever nothing ever happens. While the boss is there and can advise you and help in this case the boss actually is more familiar with much more familiarity with FileMaker.
In this case they did not have an emergency checklist. And so, most people don't have a written emergency checklist. And we talked about this. So, should we do a live stream where we actually kind of have a kind of a blank one that we kind of give to everyone and we kind of fill out along the way and give them a chat we can do. We can cover about one variant of that per live stream. It's huge because people have to have a if you want to cover all of the network somebody's you know connectivity problem went down something like that. How do we troubleshoot that I can do all of those because that's my job but do we have any buzzing? Do people like the checklist? Do you like the checklist stu stu I don't know a stu's marshal guy or what stu is. But I guarantee if you're in the navy and it's action stations or whatever the hell you guys call it there. I think that's a British term, you guys have an emergency plan. There's an emergency checklist for damn near everything right you know pull pull rip the handle and send in the marines right. So, Jacob you guys have one pre Jacob I have. Like a written out one. I believe for what it's pointers for the basic case which is like FileMaker servers like not running or something the machine went down. And like what do you do Jacob? Restore from backups that's what you do Jacob. But what does that look like, right? So, correct Jacob yep and that's what this person was having like challenges with is they had heard some of this stuff but and so their their boss who of course was on vacation because nothing ever nothing ever happens. While the boss is there and can advise you and help in this case the boss actually is more familiar with much more familiarity with FileMaker.
They're the person who built it. I don't know how to build the solution but you know with the consultants and stuff like that. But you know, they know enough basically they know how to stay out of trouble for the most part. Well Jacob and that's that's who told me the person. Hey, would you please go check what you did with RCC to make sure that you performed it correctly. And so, they did not and I mean they checked with us but they did not do it correctly. And so, I had to write a lovely email yesterday explaining exactly what should have been done differently. And how to kind of resolve the problem that they had created. So, Jacob, I think a big part of this is important for people. Just because you have the book on how to be a helicopter pilot doesn't mean you know you're from a hole in the ground. Just because you've heard about FileMaker server and you listen to Jacob doesn't mean you know your house is the holy ground to be a pilot. They actually make you go through and do this stuff on a check ride okay. We don't. There's no legal mandate that you get a check right before you have a FileMaker server. Not saying it's not a bad idea actually if here is your emergency procedure section right. Are you prepared to demonstrate? You can do this. I've actually been there but it was before Jacob was hired. I know how far it goes back but I had a server guy who swore he knew what he was doing. And I went over and I ripped the cord out of the back of the server. and I said pull your checklist, do it I'm watching and it was so you don't want to be the first time. You've actually really gone through the checklist. Really really to be when you're under a live fire exercise right as for a stew conversation right. You bleed in training so you don't bleed in real life right. That's the kind of idea. So, you need to train a little bit. You need to go through the exercise. Maybe we can do that with a couple victims. I mean I'm just talking out loud but you take Ken, Julie maybe Scott maybe Broderman. I can tell you how there's a couple differences. We can fake a couple different things Jacob, well Jacob. But you bring them on the live stream and you say okay you guys got your checklist, get yourself, get your people out of your database. We're going to destroy it on purpose. Well, we can set up a fake server for them and then let them do it but Jacob but make them do it and watch him do it. And it would be a great live stream. People be like oh come on Ken press that button baby we know which one it is. And he's like oh which button it's like Star trek everyone's shaking around and shaking and push button and everyone's like oh my god. So, Jacob that would be a good one that would be a good one because this is real. There's a misbehavior in the FileMaker server. This is why we tell everybody and I'll show you that I'll show you the setting right. Now pretty much okay. Let me, let me zoom back in. So, this is a screen you want to look at. This is one of the key features we always tell everybody to change, which is this right here. Which is automatically hosting the databases when the server software comes back up again. We turn that off essentially. Everything is off. There's a couple limited scenarios we can make that determination together in general. Don't ever have that feature on do not and the reason is because of a misbehavior here. So, this makes sense and from a usability perspective you're like oh Jacob of course you'd want the databases to open automatically. And this is exactly what the client I'm referencing from yesterday. What did they run into? So, I think we did some configuration work on their server. So, it's set correctly and so the person came in and the databases were closed.
They're the person who built it. I don't know how to build the solution but you know with the consultants and stuff like that. But you know, they know enough basically they know how to stay out of trouble for the most part. Well Jacob and that's that's who told me the person. Hey, would you please go check what you did with RCC to make sure that you performed it correctly. And so, they did not and I mean they checked with us but they did not do it correctly. And so, I had to write a lovely email yesterday explaining exactly what should have been done differently. And how to kind of resolve the problem that they had created. So, Jacob, I think a big part of this is important for people. Just because you have the book on how to be a helicopter pilot doesn't mean you know you're from a hole in the ground. Just because you've heard about FileMaker server and you listen to Jacob doesn't mean you know your house is the holy ground to be a pilot. They actually make you go through and do this stuff on a check ride okay. We don't. There's no legal mandate that you get a check right before you have a FileMaker server. Not saying it's not a bad idea actually if here is your emergency procedure section right. Are you prepared to demonstrate? You can do this. I've actually been there but it was before Jacob was hired. I know how far it goes back but I had a server guy who swore he knew what he was doing. And I went over and I ripped the cord out of the back of the server. and I said pull your checklist, do it I'm watching and it was so you don't want to be the first time. You've actually really gone through the checklist. Really really to be when you're under a live fire exercise right as for a stew conversation right. You bleed in training so you don't bleed in real life right. That's the kind of idea. So, you need to train a little bit. You need to go through the exercise. Maybe we can do that with a couple victims. I mean I'm just talking out loud but you take Ken, Julie maybe Scott maybe Broderman. I can tell you how there's a couple differences. We can fake a couple different things Jacob, well Jacob. But you bring them on the live stream and you say okay you guys got your checklist, get yourself, get your people out of your database. We're going to destroy it on purpose. Well, we can set up a fake server for them and then let them do it but Jacob but make them do it and watch him do it. And it would be a great live stream. People be like oh come on Ken press that button baby we know which one it is. And he's like oh which button it's like Star trek everyone's shaking around and shaking and push button and everyone's like oh my god. So, Jacob that would be a good one that would be a good one because this is real. There's a misbehavior in the FileMaker server. This is why we tell everybody and I'll show you that I'll show you the setting right. Now pretty much okay. Let me, let me zoom back in. So, this is a screen you want to look at. This is one of the key features we always tell everybody to change, which is this right here. Which is automatically hosting the databases when the server software comes back up again. We turn that off essentially. Everything is off. There's a couple limited scenarios we can make that determination together in general. Don't ever have that feature on do not and the reason is because of a misbehavior here. So, this makes sense and from a usability perspective you're like oh Jacob of course you'd want the databases to open automatically. And this is exactly what the client I'm referencing from yesterday. What did they run into? So, I think we did some configuration work on their server. So, it's set correctly and so the person came in and the databases were closed.
They had lost power at their office. That's why the thing went down. And that is a perfect scenario. First, Jacob from backgrounds yep good to go Jacob and it was on a weekend. Oh, there's no data going into the system perfectly right. Couldn't have been I mean is it right you not ever going down. Would have been the best situation but otherwise perfect restoration scenario. So, when you come in here the machine starts back up again. FileMaker server launches so in the case where you have this feature turned on it will try and open all your databases. That's what it says. If it looks at the databases and says hey that wasn't closed properly right. Because the power went off. The FileMaker server crashed for whatever the reason is. It'll do a consistency check on the database. However, it is very very very important to know that that consistency check is very narrow. What it is looking for is like ridiculously obvious corruption in the file structure. If there's corruption in the data it doesn't care it will open that corrupted database. And so, what and so your data could be corrupted, you actually. Your structure can still be corrupted because it may not be like. We'll say bad enough to warrant a halt Jacob and the ux misbehavior here though is that for example. So, let's say your server was configured correctly you had this power outage you're coming in and looking at it if you go open the databases. It'll do that consistency. So, you would go over here to databases. What the person did went over to the databases. And they said their database is on their blue Jacob right. So, it would be that they're all off and everything will be closed. You click over here and you say open all right yep except that the files don't pass a consistency check. So, right and so they stay and so what happens is it takes some time.
They had lost power at their office. That's why the thing went down. And that is a perfect scenario. First, Jacob from backgrounds yep good to go Jacob and it was on a weekend. Oh, there's no data going into the system perfectly right. Couldn't have been I mean is it right you not ever going down. Would have been the best situation but otherwise perfect restoration scenario. So, when you come in here the machine starts back up again. FileMaker server launches so in the case where you have this feature turned on it will try and open all your databases. That's what it says. If it looks at the databases and says hey that wasn't closed properly right. Because the power went off. The FileMaker server crashed for whatever the reason is. It'll do a consistency check on the database. However, it is very very very important to know that that consistency check is very narrow. What it is looking for is like ridiculously obvious corruption in the file structure. If there's corruption in the data it doesn't care it will open that corrupted database. And so, what and so your data could be corrupted, you actually. Your structure can still be corrupted because it may not be like. We'll say bad enough to warrant a halt Jacob and the ux misbehavior here though is that for example. So, let's say your server was configured correctly you had this power outage you're coming in and looking at it if you go open the databases. It'll do that consistency. So, you would go over here to databases. What the person did went over to the databases. And they said their database is on their blue Jacob right. So, it would be that they're all off and everything will be closed. You click over here and you say open all right yep except that the files don't pass a consistency check. So, right and so they stay and so what happens is it takes some time.
However long, sometimes faster sometimes slower totally depends on the size of your database. And it fails right. Let's say one of the databases fails and some of them are fine. They pass the consistency check but one of them fails. So, what does it do in that scenario? It doesn't tell you anything. It goes back to it. So, it's yellow during the scan. If it takes long enough. You'll see the yellow icon and then it goes back to gray again. So, you don't tell you anything for the ones that are running. And then gray for the ones and so if you try to start your car and the car doesn't start what do you do? A second time you try and start it again, and start it again. And so, what is it like for my cars, my cars, my car's misbehaving. It's a little funky. It's you know we need to maybe the battery's a little weak. But you know, you’re right. You try it over again. See? Oh maybe it starts the second time right. Okay. what you have actually just done in FileMaker server is when you hit that open all a second time. It will open them because what you have doesn't tell you this. And you may not be aware of it but what you have just done is requested FileMaker server to override its own fail. So, it failed the file. It did not pass the consistency check. And so, it said this file's not generally speaking. Safe to run and again longer conversation about what kinds of damage
However long, sometimes faster sometimes slower totally depends on the size of your database. And it fails right. Let's say one of the databases fails and some of them are fine. They pass the consistency check but one of them fails. So, what does it do in that scenario? It doesn't tell you anything. It goes back to it. So, it's yellow during the scan. If it takes long enough. You'll see the yellow icon and then it goes back to gray again. So, you don't tell you anything for the ones that are running. And then gray for the ones and so if you try to start your car and the car doesn't start what do you do? A second time you try and start it again, and start it again. And so, what is it like for my cars, my cars, my car's misbehaving. It's a little funky. It's you know we need to maybe the battery's a little weak. But you know, you’re right. You try it over again. See? Oh maybe it starts the second time right. Okay. what you have actually just done in FileMaker server is when you hit that open all a second time. It will open them because what you have doesn't tell you this. And you may not be aware of it but what you have just done is requested FileMaker server to override its own fail. So, it failed the file. It did not pass the consistency check. And so, it said this file's not generally speaking. Safe to run and again longer conversation about what kinds of damage
you can have that kind of stuff. But at a basic level it has already been validated. You have corruption in your file. It is literally a corrupted file. And so, what you've done asking it to open a second time is to override that determination by following open, open please open after you know that enough. Eventually I want my business to give it it's mine. Turn it on, yes. The FileMaker server is not being funky. It is not, it is. So, if it doesn't open it is telling you to piss off and you should listen to that. And so, what this client did is they thought it was being funky or buggy or you know just a wily software wisely right. Not respecting the hand requested it to open it. It thought about it and that didn't occur to them. Maybe there's something there and it doesn't tell you there's like you know even the silly version.
you can have that kind of stuff. But at a basic level it has already been validated. You have corruption in your file. It is literally a corrupted file. And so, what you've done asking it to open a second time is to override that determination by following open, open please open after you know that enough. Eventually I want my business to give it it's mine. Turn it on, yes. The FileMaker server is not being funky. It is not, it is. So, if it doesn't open it is telling you to piss off and you should listen to that. And so, what this client did is they thought it was being funky or buggy or you know just a wily software wisely right. Not respecting the hand requested it to open it. It thought about it and that didn't occur to them. Maybe there's something there and it doesn't tell you there's like you know even the silly version.
I know nobody reads these notification bells or whatever but like it could send a notification here. We got some in here from our whatever but like you know it could ping that and be like hey you just did something like you just overrode it. It doesn't. So, when you do that, you then open the corrupted database period and it will just not check it a second time. And forcibly open the database. You are now whatever your users do from that point. You are now entering data into and manipulating a corrupted database. Congrats, don't do that please. Avoid that at all costs because I have to tell people this and that's why we go through it. It's very expensive to get corruption out of your database. Obviously we're consultants. We love money. That's not the kind of money that we want to take from our clients. That's bad money. It's not new, features dirt, or even maintenance. It's bad. It means someone has messed up a horrible process that has gone horrifically wrong at multiple points. And you are now in the situation where you are trying to corrupt to recover from a known bad point. You want to avoid finding yourself. I'm over here kissing the ten thousand dollar stack for you. So, I'm like Jacob oh absolutely right. If you have to bring in one of our senior engineers, Jacob, Richard's making out with a ten thousand a stack of ten ten thousand dollars. So, I don't want this to keep your money. Be awesome if you wanna give me ten grand and we're gonna build you some bad. I'm all for that but I don't want to take 10 grand because you press the button. And you, well, it's like this if you don't follow this checklist right here either you die or you trash a half a million dollars real fast. So, I mean if I told people hey if you don't follow your 5-minute checklist it might send electrical short through the mouse and kill you. They would take it much more seriously, I think.
I know nobody reads these notification bells or whatever but like it could send a notification here. We got some in here from our whatever but like you know it could ping that and be like hey you just did something like you just overrode it. It doesn't. So, when you do that, you then open the corrupted database period and it will just not check it a second time. And forcibly open the database. You are now whatever your users do from that point. You are now entering data into and manipulating a corrupted database. Congrats, don't do that please. Avoid that at all costs because I have to tell people this and that's why we go through it. It's very expensive to get corruption out of your database. Obviously we're consultants. We love money. That's not the kind of money that we want to take from our clients. That's bad money. It's not new, features dirt, or even maintenance. It's bad. It means someone has messed up a horrible process that has gone horrifically wrong at multiple points. And you are now in the situation where you are trying to corrupt to recover from a known bad point. You want to avoid finding yourself. I'm over here kissing the ten thousand dollar stack for you. So, I'm like Jacob oh absolutely right. If you have to bring in one of our senior engineers, Jacob, Richard's making out with a ten thousand a stack of ten ten thousand dollars. So, I don't want this to keep your money. Be awesome if you wanna give me ten grand and we're gonna build you some bad. I'm all for that but I don't want to take 10 grand because you press the button. And you, well, it's like this if you don't follow this checklist right here either you die or you trash a half a million dollars real fast. So, I mean if I told people hey if you don't follow your 5-minute checklist it might send electrical short through the mouse and kill you. They would take it much more seriously, I think.
So, anyway, so, and that‘s the big takeaway though is I, and I, there's several different good options for how to kind of resolve this. I put in a request to Claris that somebody, somewhere maybe someday soon think about doing something about that okay. Cool. I would love that. That would make me sleep pretty well at night. It would make me sleep a little better at night for our Amazon servers. It doesn't really you know none of this stuff affects us because they're all configured correctly. There's no question but it is a question for the people who they host on site. They run their own servers and they have their own I. T personnel. Whether those people you know have specific familiarity with FileMaker server or not. Many don't and that's fine honestly but that means that the software needs to kind of behave a little better for people that don't know what FileMaker is. And it should do the right thing which frankly just prevents you from opening a crash database. I don't how Claris wants to handle that. I don't really care but handling it because it's not currently alright. Cool. I like what Ken said. When I push this button what does it do Jacob? I like that. So, we're done for today. Tomorrow is a Klaus event I think is here tomorrow. I believe that is the case we're a bit late when you correct Klaus' event. What is Klaus doing tomorrow? What he's got like a whole list of things.
So, anyway, so, and that‘s the big takeaway though is I, and I, there's several different good options for how to kind of resolve this. I put in a request to Claris that somebody, somewhere maybe someday soon think about doing something about that okay. Cool. I would love that. That would make me sleep pretty well at night. It would make me sleep a little better at night for our Amazon servers. It doesn't really you know none of this stuff affects us because they're all configured correctly. There's no question but it is a question for the people who they host on site. They run their own servers and they have their own I. T personnel. Whether those people you know have specific familiarity with FileMaker server or not. Many don't and that's fine honestly but that means that the software needs to kind of behave a little better for people that don't know what FileMaker is. And it should do the right thing which frankly just prevents you from opening a crash database. I don't how Claris wants to handle that. I don't really care but handling it because it's not currently alright. Cool. I like what Ken said. When I push this button what does it do Jacob? I like that. So, we're done for today. Tomorrow is a Klaus event I think is here tomorrow. I believe that is the case we're a bit late when you correct Klaus' event. What is Klaus doing tomorrow? What he's got like a whole list of things.
Basically it's just developer tips. Like tips on how to be a better developer like oh all right we'll we'll email your mother tell her you love her. If she's still with us right. Be nice to you, be nice to stray kittens, and puppies right. I mean those kinds of life tips or different kinds of life tips on the develop like you know we try to enhance workflows basically. Are you taking your own medicine? But basically it's about how we optimize all this stuff for our customers. But are you actually optimizing the way that you work? Look at this book right here. If anyone wants to read this book but it's I'm sure it's amazing. So, if you guys have any questions about stuff but I think we are doing a live fire training exercise almost live fire. We're not going to blow your servers up. We will create a real server. We're going to put some pressure on you. We're going to hear the jeopardy of music playing and you're Ken and Stu and Larry and not Kyle. Kyle actually might follow the instructions but I think Jacob, I think Kyle would follow the instructions that'll be good. That'll be fun. We should do that. So, we'll plan on doing that. That'll be good for team training. I like that. So, that's good. So, all right well don't forget tomorrow's great day and then Monday, Tuesday next week is going to be FileMaker 19. 5, 19. 6, 20. All right. So, that'll be exciting next week okay. All right. Cool. Thanks everyone. Bye.
Basically it's just developer tips. Like tips on how to be a better developer like oh all right we'll we'll email your mother tell her you love her. If she's still with us right. Be nice to you, be nice to stray kittens, and puppies right. I mean those kinds of life tips or different kinds of life tips on the develop like you know we try to enhance workflows basically. Are you taking your own medicine? But basically it's about how we optimize all this stuff for our customers. But are you actually optimizing the way that you work? Look at this book right here. If anyone wants to read this book but it's I'm sure it's amazing. So, if you guys have any questions about stuff but I think we are doing a live fire training exercise almost live fire. We're not going to blow your servers up. We will create a real server. We're going to put some pressure on you. We're going to hear the jeopardy of music playing and you're Ken and Stu and Larry and not Kyle. Kyle actually might follow the instructions but I think Jacob, I think Kyle would follow the instructions that'll be good. That'll be fun. We should do that. So, we'll plan on doing that. That'll be good for team training. I like that. So, that's good. So, all right well don't forget tomorrow's great day and then Monday, Tuesday next week is going to be FileMaker 19. 5, 19. 6, 20. All right. So, that'll be exciting next week okay. All right. Cool. Thanks everyone. Bye.
Transcript
Transcript
Need Help With Your FileMaker Solution?-FileMaker Experts-Get Help FileMaker Pro Software
Need Help With Your FileMaker Solution?-FileMaker Experts-Get Help FileMaker Pro Software
Follow us on Twitter - FileMaker Training
Follow us on Twitter - FileMaker Training
Follow us on Facebook - FileMaker Training
Follow us on Facebook - FileMaker Training
Daily Open Q&A with FileMaker Experts. Questions about Installation, Upgrading, Purchasing or How to make FileMaker work for you in your company to increase ROI.
Get up to speed with the FileMaker Video Training Course!
Top Rated Course by FileMaker Expert, Richard Carlton.
http://fmtraining.tv/fmpro19.php
Video is an electronic medium for the recording, copying, playback, broadcasting, and display of moving visual media.
https://en.wikipedia.org/wiki/Video
FileMaker is a cross-platform relational database application from FileMaker Inc.
https://en.wikipedia.org/wiki/FileMaker
Customer relationship management, processes implemented to manage a company's interactions with customers and prospects
https://en.wikipedia.org/wiki/CRM
Experience Richard's dynamic and exciting teaching format, while learning both basic, intermediate, and advanced FileMaker development skills. With 30 years of FileMaker experience and a long time speaker at FileMaker's Developer Conference, Richard will teach you all the ins and outs of building FileMaker Solutions.
The course is 60 hours of video content! Transform your business with the FileMaker Platform
Richard has been involved with the FileMaker platform since 1990 and has grown RCC into one of the largest top tier FileMaker consultancies worldwide.
Richard works closely with RCC's staff: a team of 30 FileMaker developers and supporting web designers. He has offices in California, Nevada, and Texas.
Richard has been a frequent speaker at the FileMaker Developers Conference on a variety of topics involving FileMaker for Startups and Entrepreneurs, and client-server integration.
Richard is the Product Manager for FM Starting Point, the popular and most downloaded free FileMaker CRM Starter Solution.
Looking for FM Starting Point free software download: https://www.fmstartingpoint.com
FileMaker Pro is a simply powerful software used to create custom apps that work seamlessly across iPad, iPhone, Windows, Mac, and the web
Free FileMaker Training Videos Channel https://www.youtube.com/user/FileMakerVideos
FileMaker 19 Video Training Course Introduction-FileMaker 19 News-Learn FileMaker From The Experts
FileMaker 19 New Release - Top 10 Need To Know Items in FileMaker 19 - FileMaker Top Ten News
https://youtube.com/watch?v=kRDXfpMrjvM
FileMaker Purchasing Options-FileMaker Training-Best Way To Purchase FileMaker 19-FileMaker 19 Video
https://www.youtube.com/watch?v=LlZqf_8N1Ho
https://www.youtube.com/watch?v=LlZqf_8N1Hou0026list=PLjTvUZtwtgBTCbN3Sr7yn6weIyIofDoMLu0026index=3
A database management system (DBMS) is a computer software application that interacts with the user, other applications, and the database itself to capture and analyze data
Video introduction to iOS App Training https://www.youtube.com/watch?v=cVxQe_yAshw
Free FileMaker videos check out ...http://www.filemakervideos.com
Download the FileMaker Pro and FileMaker GO for mobile devices training videos at http://www.fmtraining.tv
Download FileMaker Go video training at https://fmtraining.tv/fmgo19.php
Download FileMaker Full Video Training Bundle at https://fmtraining.tv/subscription.php
Learn how to use FileMaker to create an app with the FileMaker Training Series
Comment, Like and Share All of Our Videos.
Feel Free to Embed any of Our Videos on Your Blog or Website.
Follow Us on Your Favorite Social Media
https://www.facebook.com/FileMakerVideos
https://twitter.com/filemakervideos
Join us for live training on Twitch daily at 1pm Pacific
https://www.twitch.tv/fmtraining
https://www.youtube.com/user/FileMakerVideos
https://www.filemakervideos.com/
https://fmstartingpoint.com/downloadform3.php
Download FM Starting Point
https://filemakerfree.com/signup.html
FileMaker 17 manual For Novices kindle
https://rcconsulting.com/courses.html
https://www.guidetofilemaker.com/
Blogger sites
https://fmtrainingtv.blogspot.com/
WordPress sites
Claris FileMaker Training for Beginners in California, Texas, Nevada, Washington and all over United States
Claris FileMaker Training for Beginners in California, Texas, Nevada, Washington and all over United States
FileMaker Training Files
Page updated
Google Sites
Report abuse