How can I backup databases to another server through a mapped drive and get FM to validate my path?

I am trying to setup our FM Server 9 to do a daily backup of all of our databases to a NAS.  I have mapped a drive as the Z drive to the backup folder on the NAS.  When I put in the Backup Folder in the Schedule Assistant it says the path is invalid.  

I first tried doing it with the server name like this:

filewin://servername/path/

Then I mapped the drive as Z: and tried this:

filewin:/Z:/Monday/

This is validated:

filewin:/C:/

But this will not!

filewin:/Z:/

I have tested that I can read and write from this mapped drive.  I know I've done this before at another place but it's been a long time so I don't remember how...
LVL 4
norcaltyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

norcaltyAuthor Commented:
Increased to 500 points.
0
lesouefCommented:
you can't. from my experience with fm server8 (did nto check with v9), you can only save to a local path, always the same, and then copy or mov/rename the file with an external tool.
my way to do this is to use a shell script to do the backup using the fmsadmin tool then copy/rename or move it somewhere else. I did t for both windows and osX servers, works fine.
finally set this script to be a scheduled task under winodws, or a cron task under osX. If you're not comand line familiar, you can use cronX for osX to setup the crontab file.
0
billmercerCommented:
The reason FileMaker's backup will only back up to a local volume has to do to with the way the built-in FileMaker backup process works, a two-stage process that involves copying the file while open, then temporarily locking it while updating it. This means backups run with less impact on end users, but requires local access speeds to work.

Another option you can use is to simply close all the database files, copy them directly to your NAS device, then re-open them. That can be automated using FileMaker's built in scheduling.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lesouefCommented:
interesting, I did not know this...
btw, they could have allowed some kind of suffix to be able to avoid overwriting the file, a method which is pretty common. the drawback of what you mention, is that you must disconnect users while the other one can be done on the fly.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.