![]() Remove the original production database file(s):.Ls -la /opt/FileMaker/FileMaker\ Server/Data/Databases/ You could optionally confirm that the copy command worked by listing the files in the production directory:.Copy backup file(s), preserving permissions ( -p)Ĭp -p filename_appendedTimestamp.fmp12 /opt/FileMaker/FileMaker\ Server/Data/Databases/.These will be the files that were attached using step 5 above (Attach Snapshot): Change to directory containing backup files.Ssh -i ~/.ssh/hostname.key Establish session using sudo privilege: Adjust paths according to particulars of your configuration and filename(s). Directory paths specified below assume a standard installation. Next, ssh into the FileMaker Cloud for AWS instance, move the attached backup to the production directory, and rename it. Close the production file(s) that will be replaced by the backup using the Admin Console.Click through the dialog and expect to wait several minutes, especially for large files.Check the desired snapshot and click Attach Snapshot.From sidebar, select Preserved Backups.Preserve the desired backup by checking snapshot and clicking Preserve Backup.Log into FileMaker Cloud for AWS Admin Console.Once the backup file(s) are attached, they will show up in the Linux directory structure. The first step is to attach the backup using the FileMaker Cloud for AWS Admin Console. Now the admin should be able to use the below instructions to ssh to the server to restore backup files.The administrator should navigate to the ~/.ssh directory on the local machine and use ssh-keygen -t rsa -f hostname.key to create a public and private key pair.This is completed via the AWS management console. Basically, you need to grant access on the server for the user that will be logging in to restore the backup files. This part of the procedure should only need to be done once per user requiring access. Basic proficiency with the Linux command line.Established SSH access to the FileMaker Cloud for AWS instance.You have FileMaker Cloud for AWS instance root credentials.The FileMaker Cloud for AWS Admin Console is working.This approach may vary for other versions of FileMaker Cloud. Your applications are hosted with FileMaker Cloud for AWS 1.17.Warning! You are soundly entering “ knows enough to be dangerous” territory here! Reach out to us if you need some help with FileMaker Server administration. ![]() You can restore backups more safely using the FileMaker Cloud for AWS Admin console by preserving, attaching and downloading a backup and then uploading it back to the server. Note this method really would only be necessary if the files to restore were very large and you were in a hurry. What if we could log into the server and restore database files by simply moving them to the correct directory? While there are a few details to pay attention to, if you are reasonably comfortable working from the Linux command line then you can use the tools available too quickly and safely restore backup files. ![]() The basic idea is that FileMaker Cloud for AWS 1.17 is hosted on a Linux (specifically CentOS) server. Special thanks to Simon Brown for working out the details of this procedure. However, things did not go smoothly as there was seven gigabytes of data to download and the process was too slow for their fast-paced production environment…like half-a-day too slow.Ĭlearly we needed a better way that could get our client up and running much faster. This seemed a simple enough request-we would download their backup files using the FileMaker Cloud for AWS Admin Console and then re-upload them to the server. Recently, we had a client who required restoration of FileMaker backup files for their FileMaker Cloud for AWS 1.17–hosted solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |