Move BFI from Windows Server 2012 to 2019

I have to move our BFI installation to a new VM with Windows Server 2019. We have an existing remote DB. There are instructions for this process, but they get muddy when talking about initial configuration.

Why does initial configuration talk about creating a database when the title of the KB is with existing DB?

It would be nice if there were a YouTube video or at least screen shots of the process.

Where is database creation mentioned? I see the following in the above link:

  1. Before you complete the initial configuration, restore all files that you backed up in [step 1] into the new installation directory.
  2. Restart BigFix Inventory.

Note:The initial setup is not required and the previous database will be used.

See step 5. Then the link talks about creating a new DB.

  1. Perform the initial configuration and point to the existing database instance. It is enough to specify the right host name and leave the same database name. BigFix Inventory will connect to your existing database. For more information, see: Performing initial configuration on Windows or Performing initial configuration on Linux.

The link you had provided above is for BFI 11 but the step 5 you described is in BFI v10 version documentation. Please click on this BFI v11 link and see if you get the same info? Reinstalling BigFix Inventory with an existing database

Could be some browser caching issue or a broken link.

All of the web pages I am looking at say version 11 in the upper right corner.

Just to clarify, currently you have BFI application on a Windows 2012 server with a remote database. You will be moving the BFI application to a new Windows 2019 server with using the existing remote database.

I have been thinking to perform this in my lab. I will document the steps with screenshots and share it with you.

That would be great! Thank you very much!

Apparently, the documentation is not correct about the directories and files to backup and restore.

I tested the BFI Application migration to a new server with an existing database on a remote server. If the correct server.xml and database.yml files are in place on the new server, the database setup screen will not be displayed as the application will connect to the existing database. Please send me an email at somasekhar.sakunala@hcl-software.com and I will share the document

1 Like

Thank you ssakunala, but I just went through the move last night. I updated my process to include copying the files below. The documentation was just updated in the last day or two. It still needs more updating though because it is really not very clear.

Create a backup of the following files and subfolders (if they are available) from the installation_dir/wlp/usr/servers/server1 folder:

  • logs/*
  • data/*
  • java.security
  • jvm.options
  • server.env
  • server.xml
  • customization.xml
  • config/database.yml
  • config/config.yml
  • config/etl_settings.yml
  • resources/security/*
  • resources/fixlets/tem_config_actions/shared_disks_update_share_computer.bes_*
  • apps/tema.war/WEB-INF/web.xml
  • apps/tema.war/WEB-INF/domains/sam/config/file_names*
  • tmp/datasources/*
1 Like

Yes, this was what I was seeing before in the V11 version and I followed these steps.