The client does not have to be on the server to connect and upload a file. But wherever you are uploading from with FileMaker Pro, make sure you have OS level access to the file either on the hard drive or over a network. Sometimes it may make things a lot faster if you have FileMaker Pro on the Server, but it is not needed.
Instructions on uploading a file are at: http://help.filemaker.com/app/answers/detail/a_id/11957/~/uploading-database-files-to-filemaker-server
If you are on server itself you can copy (not move) a copy of the backups into the live folder, after making sure the database server is off.
No need to upload through FMP.
So just remove the old database, copy the backup to the desktop, then copy it back into the live folder where the other one was? no permission issues?
1 of 1 people found this helpful
No, don't copy to the desktop, that will reset the file permissions to your account. Copy them straight from the backup folder to the live folder. That will preserve the necessary fmserver / fmsadmin OS-level file permissions.
If you do want to go through the desktop, remember that you need to change file ownership and rights on the file through terminal or through a utility like Batchmod.
(when you upload through FMP, the upload process takes care of those permissions).
- DOstop/remove the bad copy
- Copy and past the good copy FROM the backup DIRECTLY INTO the live folder.
That will save time and hassle...Thanks!
I never use copy & paste for files so I can't vouch for that, but it should be the same. I use drag & copy.
As an aside: the reason that moving the backup should be avoided is because of the hard-link-backup mechanism. When you copy you get a non-hardlinked set of files. When you move the files and then host them, you may be inadvertently chaning a number of hard-linked backup sets (= lose those backup sets).
Copy, not move.
If using drag and drop, that means use option-drag
As Wim pointed out, you won't have a problem with permissions, but I would always check if I were you. And correcting them is not space technology, either: user=fmserver and group=fmsadmin have to have read & write access to all enclosed files and folders (inclusing the RC folders), that's all there is to it.