Export and Import Images

[Vanlue IT Guy]

2 related questions:

First, is it possible to export images from my FOG 1.1.0 server to my trunk server, and how do I go about this?

Second, will the old images even work or am I further ahead recreating them on the new server?

[ITSolutions]

Yes and yes, but I would recommend updating the images to Partclone right a way also. To give you a how to a couple of questions though:

1. Are your images and FOG on the same drive or separate drives?
2. What OS are you using Ubuntu, Cent, Red hat?
3. Are you wanting to keep your database from your current FOG server or just the images?

[Wayne Workman]

Yes and yes.

many ways to go about it - easiest is from the new server, mount the old servers images directory to a temp directory via NFS and then recursively copy the images over to the new server - then set permissions afterwards.

here’s some really rough notes I have on it - I’ve been meaning to make them into a wiki article all beautiful-like but I just haven’t had time.

0_1456176465858_FOG Migration notes.txt

[Vanlue IT Guy]

@ITSolutions

Thanks for the reply.

I am running Ubuntu on both machines. On the 1.1.0 box I am running Ubuntu 14.04 with a GUI.

On the trunk box, I am running Ubuntu 14.04 with no GUI.

I have two separate boxes running the different versions of FOG, so different drives, different everything.

I would like to keep just the images.

[ITSolutions]

@Vanlue-IT-Guy @Wayne-Workman has a pretty good rough outline on how to transfer the images over to the new box. But if you are only worried about keeping the images and no database I would go a slightly different route. It will take a little more time but get all your images converted tot he new partclone from partimage that previous versions used. The first thing is find a spare machine that has a big enough drive to hold your largest image(doesn’t matter if it is the same model or brand). Then pull each image down from the old FOG server, DO NOT let the machine reboot to the image and then create the image definition on your new machine and push it up tot he new machine. You will have to do that with each image.

The quicker way is with @Wayne-Workman’s suggestion of using NFS, as FOG is already set up for it. Have both machines on, and on the new machine run this part of his notes:

---- using NFS ------
cd /
mkdir tempMount
mount x.x.x.x:/images /tempMount


---copy images---
cd /tempMount
cp -R * /images

(assumes /images directory is already made)

--- unmount ----
umount /tempMount

Then in the web interface you can create the image definitions again, just use the same name as you did on the old server. I recommend using a separate drive for the /images. With a separate drive you could just pull the drive from your old FOG server and mount it to /images in the new server, no need to copy.

[Wayne Workman]

@ITSolutions said:

But if you are only worried about keeping the images and no database I would go a slightly different route. It will take a little more time but get all your images converted tot he new partclone from partimage that previous versions used. The first thing is find a spare machine that has a big enough drive to hold your largest image(doesn’t matter if it is the same model or brand). Then pull each image down from the old FOG server, DO NOT let the machine reboot to the image and then create the image definition on your new machine and push it up tot he new machine. You will have to do that with each image.

In this situation, I’d say this is the more superior option.

I only did it the way I did because I was going from the latest FOG Trunk server - to another latest FOG Trunk server - my images were already in the latest and greatest image format. I was migrating a physical machine to an identical virtual environment and I didn’t want to use some shabby clunky physical2virtual process.

[Wayne Workman]

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG