Noticed that now 1.2.0 uses Partclone 0.2.69; does that mean one must redo all prior images?
Boyan Biandov last edited by
I noticed that now FOG 1.2.0 uses Partclone 0.2.69; does that mean one must redo all prior images? (I am hoping here the answer is no because that will lock us into FOG 0.x pretty much forever)
It used to be that before 1.x one can simply copy the images from the old FOG server; then copy the images table and voila – all worked very well.
Is that no longer possible?
When I say copy the images I mean grab each image directory and rsync it onto the new physical FOG server /images directory:
-rwxrwxrwx 1 root root 512 Mar 28 2012 d1.mbr
-rwxrwxrwx 1 root root 8519124 Mar 28 2012 d1p1.img
-rwxrwxrwx 1 root root 12812860149 Mar 28 2012 d1p2.img
I have uploaded our master image into the new server. I’m planning on just doing an .sql dump of the fog hosts table and importing into the fog hosts table on the new server. That way I bring all the old host information into the new server. I have 1 image and 1 host already, but we have that one master image for most of our machines. We have a few more images on the old fog server I need to bring over, and was just worried about transferring them. Thanks again for your suggestions!
1.) Download the images to hardware and reupload. This way you don’t need to enable “legacy” images but you will not carry over the sql database and will need to re-register every host.
2.) Mount the /images folder of the new server to /images2 and copy all contents. This way you will need to enable “legacy” images but if you follow the wiki I posted above you will keep all your hosts/group/ information. BUT see the Warning for importing the old database into the new install.
That would be best.
I do not now how far along you are with the FOG 1.2.0, (New images, registered hosts, etc) [url]http://fogproject.org/wiki/index.php/Upgrade_to_1.x.x[/url] migration upgrade would be a good reference if you 1.2.0 install has just been installed. (ie no images, no hosts, no groups)
I know its kind of confusing but the export of the old database would give you your old hosts info. But if you have already started registering on the new server, the import of the old database would do nothing but cause trouble.
So the real question is how much have you done with the new 1.2.0 server?
Thank you for upgrading!
Okay. I have FOG 0.32 as the old server, and FOG 1.2.0 as the new and they are both operational. Would it be best to just deploy the images from the old server to the machine, and then do a Full Registration and inventory so that the images go up to the new server with partclone? I’m just trying to minimize any issues that I can. Thanks Wolfbane8653 for suggestions so far.
If both servers are still operational you could do either.
I have a question about this:
If I have a new FOG Server and I’ve uploaded my first image from a master image, does that mean when I pull the images off the old machine it would be better to deploy them from the old FOG server and then upload them to the new fog server, or what is the best process here?
Boyan Biandov last edited by
Phew I was hoping for an answer like that! Thank you Wolfbane8653!
If you transfer the images you must use.
Fog Config --> Fog Settings --> General Settings -->[SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_FORMAT_FLAG_IN_GUI[/COLOR][/FONT][/SIZE]
If you upgraded directly from 0.32 [SIZE=13px][FONT=arial][COLOR=#262626] existing Image definitions should automatically be set to partimage type.[/COLOR][/FONT][/SIZE]
THEN go to Image Management --> [Image] and a new dropdown has appeared “Image Type:” Select PartImage for your old uploaded images.
BUT it would be best to download the images to the appropriate devices and reupload.
Sry about the extra edits
Last Edit: Updated the upgrading from 0.32 to 1.x.x wiki for these steps for older images