Image Replication
-
@ty900000 Try to go to this address on your storage node, where x.x.x.x is your storage node’s address:
http://x.x.x.x/fog/service/getversion.php You should get back a FOG version. -
Both source and destination return 1.5.0
-
@ty900000 said in Image Replication:
I have assigned those images to the correct storage Group - the ‘default’ storage Group of the source server where they reside and created blank image entries on the destination server.
What do you mean when you say you created blank image entries on the destination server?
-
I created an image entry on the destination server that gives the name, the OS, the compression, location of files, et cetera.
-
@ty900000 Are you aware that the FOG Installer has a ‘Storage Node’ installation mode that does not include a web GUI, for the purposes of being a storage node?
-
Yes! I remember seeing that upon first installation. I guess that’s what I need to do, huh?
That’s my bad. I reckon I was trying to turn a full FOG install into a storage node.
-
@ty900000 One full fog server CAN replicate images to another full fog server (this is called a multi-master setup) but that wouldn’t be the thing keeping your replication from going. So there is still something going on that we need to figure out - but yeah you only needed a storage node, not a full fog server for the 2nd box.
-
Okay - I’ll make a storage node-only install in a few minutes and give it a shot.
With that in mind, is it feasible to keep troubleshooting the current issue with the full servers?
-
@ty900000 said in Image Replication:
With that in mind, is it feasible to keep troubleshooting the current issue with the full servers?
We can. Step one - on the 2nd box, if you’ve created a storage node for the primary box, delete that.
Step 2, on your primary box, ensure the images are actually there still on disk. -
The 2nd box has only itself as a storage Node. The primary box does have the images still on it; I verified with du -h and they are the correct size.
-
@ty900000 Is the storage node in the same storage group as the master node?
-
@ty900000 there are no other members to sync to means the fog server and the storage node are in separate groups. Also you said you made blank image entries. What do you mean by this? Creating an image definition does not mean fog can replicate it because ther is no file data to replicate.
-
No, they are in separately defined storage Groups.
-
Okay. I changed the secondary storage Node to the primary’s storage Group.
And, the image files exist on the primary server. I’ll also delete the image definition on the secondary server to see if that helps it along, too.
-
@ty900000 said in Image Replication:
Okay. I changed the secondary storage Node to the primary’s storage Group.
That’s what will fix this. Try to restart the FOGImageReplicator and monitor the logs afterwards, it should start working after a bit.
-
Well, I’ll be! I think that worked. I could have sworn I had the same configuration before, but I guess not. That’s my fault.
Since it’s over a WAN link, it’ll take over an hour to move this one image. I’ll keep an eye on it, but it seems the primary FOG is replicating.
Thank you very much for the assistance! It’s much appreciated!
-
@ty900000 For you and for future readers, here’s some relevant documentation:
-
@ty900000 se as redes tiverem comunicação uma com a outra por VPN será q a sincronização das imagens podem funcionar por rsync? estou pensando em fazer isso na implantação do FOG que estou fazendo. Semana que vem posto os resultados.
[Moderator edit]: English auto translation - If the networks have communication with each other by VPN will the synchronization of the images be able to work by rsync? I’m thinking of doing this in the implementation of the FOG I’m doing. Next week put the results.
-
Yes, you can manually rsync the images over. I’m doing the replication between nodes so my coworkers who know nothing of Linux can synchronize images across FOG installations without asking me to do it.
