I need to add additional storage on an already running FOG server, can I get some help?



  • Hello!

    Here at work we have a FOG server running 0.32, on the machine itself we have a 1TB Hard Drive with the OS, and FOG installed, as well as where all of our images are currently stored.

    There is a second hard drive, which I had used to back up my images to when the company that set up the hardware sent us a new hard drive with the update. We are currently running low on storage and I’m trying not to build any more images than I have to. However, with having to comply with licensing for our software at different buildings, we still have to create new images even if the hardware is the same.

    I would like to know if it is possible to set this second hard drive up, either as additional storage for the default storage group? OR if I can set up a new storage group and a new storage node?

    I’ve formatted the second hard drive and tried setting it up as another storage node, however, every time I check the usage on the web app, it just shows it’s pointing to the main drive, as the stats are the same. I’ve searched quite a bit and haven’t had any luck finding any solution, all seem to point to setting up a separate network share as the other storage node.

    Edit: Everything I’ve seemed to find about “additional storage” seems to imply I don’t want to use the first hard drive for anything but the OS…I would like to keep the original images there, as well as put new ones on the second hard drive.

    Thanks!!



  • @Tom Elliott, post: 31969, member: 7271 said:

    The path should be different and be set to whatever it is that you mounted the new hdd to: for example /mnt/newFOGImages/

    From the command line you’ll need to add the new drive location to the /etc/exports file. Just copy the two lines and paste them below editing the /images /images/dev to match that of the new path for the new drive. Once done save and restart the nfs service.

    Ok, I formatted the second drive as newFOGImages, and created a folder in there called newImages. So the path should be /newFOGImages/newImages correct?

    On the web dashboard I have two storage groups made, one is default, the other is group2. I also have two storage nodes, one is DefaultMember, the other one (I created) is newImages. I created it with the same settings as the default (IP address, etc.) except master node is unchecked, and the path is /newFOGImages/newImages/ instead of /images/

    I opened the /etc/exports file and it has this:
    /images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
    /images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

    Would I just copy-paste them within that file to look like this:

    /newImages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
    /newFOGImages/newImages/ *(rw,sync,no_wdelay,no_root_squash,insecure)

    ?

    Thank you!!


  • Senior Developer

    Well, the group is just a place holder for nodes.

    So from Storage Management Page, choose create new storage group. Name it whatever you want.

    Then from the same place, goto Create New Storage Node. In the node settings, you choose the Storage Group you just created, set the IP to the same as the FOG Server, the same fog username and password as well.

    The path should be different and be set to whatever it is that you mounted the new hdd to: for example /mnt/newFOGImages/

    From the command line you’ll need to add the new drive location to the /etc/exports file. Just copy the two lines and paste them below editing the /images /images/dev to match that of the new path for the new drive. Once done save and restart the nfs service.



  • @Tom Elliott, post: 31963, member: 7271 said:

    First, some questions:

    What do you mean in order to comply with licensing you have to create an image for every single machine? Are you running OEM? Are you running VLK/MAK/KMS?

    Even with OEM, if you have the OEM disc, you are now allowed to use a single image to image “same hardware” machines. You can sysprep the image from one machine and, with an unattend.xml file, they can re-activate the machines using the machines SLP/BIOS. There should NEVER be a need to create an image for everything SINGLE machine in an environment. If you MUST do this, then it defeats the purpose of creating an image in the first place. You might as well take the system and reinstall everytime.

    Thanks for the reply!

    I don’t have to create an image for each separate machine, but for the different groups of machines. For example, we have multiple carts of Lenovo R61 laptops, two carts are licensed to use a particular program for the science labs, but we only have a limited number of uses for it, so it has a separate image from the rest.

    There’s another program that we only have for use in the High School, so we have to keep a separate image for the elementary schools. Not quite a separate image per machine, just for different software products that go on the machines themselves. Otherwise, we go with one image per make/model. Sorry if that was confusing!

    @Tom Elliott, post: 31963, member: 7271 said:

    Your best bet would be to set this drive up as a Storage Group and place that new drive in the new group. If you simple create it as a node on the same group you already have, it will try to replicate the other drive’s images to it which would not help your case in anyway.

    I think that’s what I’m trying to do. Can you point me in the right direction to set it up as a storage group?


  • Senior Developer

    First, some questions:

    @snowpanties, post: 31936, member: 24867 said:

    There is a second hard drive, which I had used to back up my images to when the company that set up the hardware sent us a new hard drive with the update. We are currently running low on storage and I’m trying not to build any more images than I have to. However, with having to comply with licensing for our software at different buildings, we still have to create new images even if the hardware is the same.

    What do you mean in order to comply with licensing you have to create an image for every single machine? Are you running OEM? Are you running VLK/MAK/KMS?

    Even with OEM, if you have the OEM disc, you are now allowed to use a single image to image “same hardware” machines. You can sysprep the image from one machine and, with an unattend.xml file, they can re-activate the machines using the machines SLP/BIOS. There should NEVER be a need to create an image for everything SINGLE machine in an environment. If you MUST do this, then it defeats the purpose of creating an image in the first place. You might as well take the system and reinstall everytime.

    @snowpanties, post: 31936, member: 24867 said:

    I would like to know if it is possible to set this second hard drive up, either as additional storage for the default storage group? OR if I can set up a new storage group and a new storage node?

    Your best bet would be to set this drive up as a Storage Group and place that new drive in the new group. If you simple create it as a node on the same group you already have, it will try to replicate the other drive’s images to it which would not help your case in anyway.


Log in to reply
 

413
Online

38746
Users

10569
Topics

100055
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.