• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Use only storage node

Scheduled Pinned Locked Moved
General
2
2
349
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U
    unknown56
    last edited by Jan 10, 2024, 3:12 PM

    Hi

    I just discovered this great software. Now i have a question that i did not found a answer.

    I have to run FOG server on VMware where is not much space available, but i can install a storage server on Synology VM.

    1. Can i use only storage server where i store images? I can only allocate on VMware FOG server like 200gb which is less than i need space. Like FOG server directly saves image to Synology FOG Storage node not on Server node ?
    2. Or should i just use Synology VM where FOG server is running and hold everything there? Synology is quite slow probably for that but in reality i make image maybe on every few months and no mass deployments.

    Im only gonna use FOG for industrial CNC machinery OS (winxp) image level backup.
    Max 10 different PC images.

    G 1 Reply Last reply Jan 10, 2024, 6:35 PM Reply Quote 0
    • G
      george1421 Moderator @unknown56
      last edited by Jan 10, 2024, 6:35 PM

      @unknown56 The answer is its complicated but not impossible.

      Lets take this one step at a time.

      1. Is is possible to use a synology NAS or most other NAS’ that have nfs, and ftp support. I have a older tutorial on how to configure a synology nas for a storage node. https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

      2. Within FOG ecosystem, only master nodes (typically fog servers) can capture images from target computers. You can not capture images to Storage nodes. There is one way replication from a master node (fog server) to a storage node. This replication only runs on the master node or fog server. So you would normally have a storage group with the FOG server as the master node, and then add additional storage nodes to this storage group, as storage nodes. One way replication happens as expected master node to all storage nodes. (stick with me, I’m almost at the point). If you were to change this storage group to an unsupported configuration, where the synology nas was listed as a master node and the fog server was listed as a storage node, then the roles would be reversed. You could then capture and restore the files from the synology nas only. There would be no replication between the reversed roles of synology nas and FOG server since the replication service only runs on a real fog server. The only gotcha here is that the FOS Engine (software that runs on the target computer) connects back to the nfs share (on the fog server or synology nas) as user root. So when the nfs share is setup you will need to ensure that a user by the name of root can mount the share, this is typically done with a share level parameter of no-squash-root

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 1
      • 1 / 1
      1 / 1
      • First post
        2/2
        Last post

      141

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project