Choising a storage management

[lebrun78]

Hello,
We have a 200 windows 7 stations and 180 linux stations park.
Until now, we use a fog server running on 0.32. This server is dhcp server to for several networks.

We will change the os from windows 7 to windows 10 for 120 machines and we have chosen to install a new fog server on a virtual machine and keep the old server to manage old PC and DHCP and store image.

For the now server, is it a good idea to mount by NFS the /images on the /images of the old server ?

[Quazz]

No.

You can’t mount an external storage location and then export it again. This is not possible.

I recommend, in the long run, to move everything to FOG 1.3

[lebrun78]

On our VM we will never store images.
So is it a good idea to mount the /images on a NFS server (which was an older fog server)

[Quazz]

@lebrun78 It’s impossible to make that work. You can’t mount a network disk locally and then export it again.

You might be interested in attaching a full hard drive to the VM and using that for storing the images.

[lebrun78]

if i rename /images to /imagesold and create a new /images where is mount //fog032/images and then copy the contents of /imagesold to the new /images, it should works, no ?

[Tom Elliott]

@lebrun78 only if you make all the right things. Such as the .mntcheck files and the dev folder.

[Wayne Workman]

@lebrun78 said in Choising a storage management:

if i rename /images to /imagesold and create a new /images where is mount //fog032/images and then copy the contents of /imagesold to the new /images, it should works, no ?

It will work. I’ve done a lot of stuff like this before. Dedicating an entire physical partition on a physical disk is the simple way to go about it but it’s not exactly flexible by design. LVM solves those problems. If you’re using logical volume groups and logical volumes, you don’t have to do all of that mess you were talking about (transferring, renaming), you just add space to the volume group, then the logical volume.