![]() ![]() # copy with pkzip compression and preserve resourcesĭitto -c -k –rsrc “$sourcelink” $destinationlink Ln -s “$destination$suffix” $destinationlink # create symlink files in tmp folder, to deal with spaces in file paths # suffix is the time stamp to append to the destination # destination is the place you want the archives sent # FileMaker Server backups, not the master files hosted by FMServer. # source defines the folder you want to archive. Source=”/Library/FileMaker Server/Data/Backups/Daily/” # only change the next two lines of this script to suit your installation # GOOD 11/29/10 Rob Russell SumWare Consulting I feel like Mavericks might not like fmserver being the owner of this script, but FMS reports no errors. The script runs on FMS13 fine, but it will not place the backup on my network share point any longer. ![]() This script has been working fine until I updated my OS to Mavericks. I’ve been using Rob Russell SumWare Consulting’s shell script for many years, successfully, to backup my local server FM backups to a network drive that’s connected to DropBox. This approach I believe increases the chances of always having a backup to fall back on. That why the article follows up on the "3-2-1" principle of backups and explains how you can use the OS tools to make sure you have backups away from the FileMaker Server machine. I certainly did not want to create the impression that i am advocating doing only internal backups. Given the importance of backups that is risk to be recognized and mitigated. That is not the same as saying that a network backup *IS* going to fail, just that it is more likely. Backing up directly over the network carries more risk of failure than an internal backup. That time frame is going to be longer for a network backup. And that's the time frame you want to minimize. Remember that FileMaker Server suspends user activity at the end of each backup to synchronize changes that have happened since the start of the backup. Network performance is always going to be slower than internal disk i/o, so a network backup is always going to take longer than an internal backup. This can be done in batch files or VBscripts on Windows and shell scripts or AppleScripts on OSX. We can schedule an OS-level script to run after our local backup is done to copy the backup set over to a network location. So am I not contradicting myself here? If local backups are preferred, what about the “1” in the 3-2-1 rule? We can still push out a backup to another location, using the FileMaker Server tools. If any of these factors breaks down the net result is that the backup run would fail and you would be without backup. So you’d have to elevate their rights and document that in case a reinstall is required sometime in the future. These accounts do not have write privileges to network resources. Remember that FileMaker Server – and by extension its schedules – runs as “local system” on Windows and the “fmsadmin” account on OSX. The setup would be fragile: the completion of the backup depends on more factors now: the destination being available, the privileges having been set correctly and maintained that way. In addition, the backup will consume much less CPU time and network bandwidth when the backup is done locally. So, backing up locally is going to have a smaller impact on the users. That’s when the users will see the most impact. Keep in mind that FileMaker Server pauses the hosted file at the end of the backup process to synchronize any changes that were made to the files since the start of the backup. It would take longer: copying across the network is always going to be slower than what the server can do with its own disks. There are fewer variables to deal with, in the event something should fail.Network connections can break for various reasons.Network backups will always take longer than local backups.While the article is about OSX, the same applies to Windows.Īt the bottom of this very short entry they specify a few reasons why backing up remotely using a backup schedule is not supported or not a good idea. There is an article in the FileMaker Knowledge base that addresses this. So can we specify a path here that would point to a network location? The short answer is no. ![]()
0 Comments
Leave a Reply. |