Sever backup file path syntax

[eyeguy]

Hi all

I have a very basic question.

 

I have a sonology NAS that i would like to use for my file backup from my server.

The server is called "DocumentServer" and t appears in my sidebar. It has an ip address of 10.1.1.26

I cannot seem to create a FMS schedule to back up to it. I get a "file path not valid" message.

I wish to back up to a folder called "database". My file path is filemac:/DocumentServer/database.

 

Can some one advise me what the correct syntax should be please

 

Joseph

[Wim Decorte]

FMS backups directly to shared network volumes don't work by design.  FMS prevents us from doing it because of the inherent extra vulnerability.

 

The better approach is to backup locally and then use a shell script to copy the backup over to the NAS.  If the copy was successful the shell script can optionally delete the local backup.

Remember that you can backup and copy all from within one shell script and have that scheduled by FMS, so it's a pretty straightforward approach.

[eyeguy]

Ok. That explains a few things.

Shell script is outside of my expertise.

Will have to use something like carbon copy cloner to achieve that.

Thank you for your reply. It is much appreciated

 

Joseph

[IdealData]

CCC will work fine - I've been doing it for years.

 

Remember you must back up the Backups folder, not the Databases folder.

[Steven H. Blackwell]

And if you use some 3rd party system to backup the Backups folder, be sure it doesn't conflict with the times of the FileMaker Server backups.  A safer and better approach is to push out a copy of the Backups Folder to some networked destination and have the 3rd party system act on that copy.

 

Also, if the files contain data that must be protected, you might want to encrypt that backup by the 3rd party system.

 

Steven

[IdealData]

How do we push out a copy of the Backups folder?

 

Won't that rely on a non-FMS method, and therefore still subject to timing conflicts with the FMS backup schedule?

 

Thanks

[Steven H. Blackwell]

 

 

Won't that rely on a non-FMS method, and therefore still subject to timing conflicts with the FMS backup schedule?

 

 

 

It does not have to relay on a non-FMS method, although it could.  You have to control the timing so there is no conflict.

 

Steven