Adding FOG database to another FOG database.

[Benjamin_D]

Hello,

My company is planning on using FOG In such a way that we will start with one normal install backing up some computers, but will eventually switch to one normal install controlling multiple storage nodes that the backup said computers. This will involve effectively wiping the original normal install, and putting a FOG storage install on it. I see that I can copy the database with mysqldump --allow-keywords -x -v fog > fogbackup.sql and backup the images with cp images/* <backup location>, however I have questions about the process of restoring them.

While I understand that I can import the database to the new normal install of fog by going to “FOG Configuration” -> “Configuration Save” -> “Import”, will this overwrite the existing database, or will it add my imported database to the existing database?

If it does overwrite the existing database, how do I add my backup to the currently existing database?

[Wayne Workman]

@Benjamin_D said in Adding FOG database to another FOG database.:

will this overwrite the existing database, or will it add my imported database to the existing database?
If it does overwrite the existing database, how do I add my backup to the currently existing database?

It will overwrite it, but that’s fine. You would import anyway, but afterwards you’d tweak just a few IP & password related settings, those are described at the bottom of this article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

[Quazz]

I’m not entirely sure what’s going on here.

As far as I understand you will have:

Original FOG Server, this will operate normally, will eventually become storage node

New FOG Server, will manage nodes

But as far as I understand the new one will only happen when this transition, occurs, yes? If so, overwriting the database is no problem.

I don’t believe there’s any easy way to ‘add to’ database, given that it tends to require prerequisite knowledge about what’s already in the database and the import. It’s not impossible, but the difficulty and time it would take to get working far surpasses that of entering in the settings again.

[Benjamin_D]

@Quazz said in Adding FOG database to another FOG database.:

But as far as I understand the new one will only happen when this transition, occurs, yes? If so, overwriting the database is no problem.

The issue comes with the fact that there it may end up being the case that there are multiple “old” servers’ databases that are going to need to be put onto the “new” server.

[Quazz]

@Benjamin_D It’s probably just easier at that point to just start off with a storage node setup. There are some articles about it on the wiki and we can help you if needed as well of course.

[Wayne Workman]

@Benjamin_D what was the reason for doing this in phases anyway?

[Benjamin_D]

@Wayne-Workman

My boss was getting very worried about the state of some of the sites that were going to be imaged and wanted to setup conventional FOG normal installs at the sites in the meantime until the centralized AWS EC2 FOG server gets up and running.

However, I have (for the most part, with an issue related to the database in the “Linux Problems” forum) gotten the AWS EC2 instance working.

So this thread can be closed for now.

[Wayne Workman]

@Benjamin_D said in Adding FOG database to another FOG database.:

the centralized AWS EC2 FOG server gets up and running.

You will absolutely want to use certbot to configure https on that machine.