Synology NAS as FOG Storage node

[Alex78]

@george1421
Ok, I am still checking all the steps of your tutorial and I will come back to you, if it not solved the problem or on the contrary if it solved it, thank you for your answer.

[Alex78]

I think it’s working thanks you

[Tom Elliott]

@alex78 Can you tell us what you had missed originally and what you did to fix it? This could help another user down the road, so always good to share if you can.

[Alex78]

@tom-elliott I just unchecked “Enable advanced sharing permissions in affected folders”:

[abrar1108]

I would like to appreciate this nice little post, I wish I had stumbled upon this earlier. Last week I tried creating my Synology NAS as a storage node and it worked. Little did I know that was the beginning of my misery. Whole week I struggled in fixing the replication issues.
Had I found this Thread earlier, I wouldn’t have attempted it.

[Vincent Caraby]

Hi,

First of all, thanks to george1421 and other users who deliver this solution.

Before i say what is my problem, the existant :

FOG serveur 1.5.4 on a Debian 9.4 with no graphical environment (terminal only) with 100Go disk. This debian is virtual on ESX6.5.0
NAS : Synologie DS116 with plenty of space

I’m a bit confuse.

All opération discribe here works whell, but when i capture, the image is copied on FOG server. Then, after capture, image is automaticaly copied on NAS. But after copy on NAS was finish, she stay on my FOG server, so after two Win10 capture the server is full.

What i miss out on ?
Is the capture normally do directly on NAS without any write on Server ?

Thanks in advance.

[george1421]

@Vincent-Caraby First let me say that changes in the fog server makes using a non-fog NAS a problem if you have it configured as you have it now. The FOG replicator will continue to copy the image over and over again to your NAS.

But let me tell you that you can do what I think you want. You must know that you can only capture images to a Master Node in a storage group. So in your settings change it so the NAS is the master node in your storage group, instead of the FOG server. This should make the images to go directly to the NAS and not FOG server.

[Vincent Caraby]

@george1421

Thanks, i see the red message at top of topic to late.
I test this solution, it seem to be wright but i’m stuck on a permission problem.

Setup my NAS storage node to master node. But when i would capture there a message “permission denied” when mounting file system.

I don’t understand who on what give permission ? I suppose it’s my “adminfog” (fog server) to my NAS folders (images, snapins, tftpboot).

Is there a file where i can configure this rigtly ? A bit lost and not linux expert, but i prefer use config files if possible.

Some capture of my configuration :

[george1421]

@Vincent-Caraby Well lets see if I can explain this, but the answer is simple and complicated at the same time.

The FOS engine connects to the master node as root so the synology nas needs to allow root to connect to the /volume1/images and /volume1/images/dev as root.

Also the FOS engine will use ftp to connect to the NAS using the adminfog user and password you defined in the Storage Node configuration to move the files from /images/dev to /images directory.

[mtrento]

@george1421
for those struggling with permissions with dev folder.
nfs creates a root:root with 775 permissions and fog ftpuser isn’t part of that group

Just use setgid feature on filesystem . it will enable inheritance
first change the owner of the folders and make “users” the group , lets say fog is your ftp user

chown -R fog:users /volume1/images/

#set inheritance to the dev folder

chmod g+s /volume1/images/dev/

now every new file under dev will have the directory group owner

Regards