Side-by-Side migration

Changed Computer ID or Database Type Migration Plan – High Level

In this scenario, it is recommended to keep the existing installation for historical reporting and to set up a new BigFix Inventory Server and migrate the data from the old system to the new one.

Additional actions to be taken:

1. Preserve the existing computer ID on BigFix Client side as a Computer Property or in a file which is not impacted by re-installation of the BigFix Agent or assignment of a new computer ID.
2. Switch the legacy BigFix Inventory instance to a read-only mode.
   1. Disable BigFix Inventory imports after ensuring a final successful import.
   2. Ensure that end users understand the change in functions from active usage to historical reporting usage - announce to use BigFix Inventory only for read-only purposes.
3. Execute the last 3rd party synchronization and disable jobs on legacy instance.
4. Secure BigFix Inventory instance for historical reporting and export the data for migration.
5. Create migration reconciliation process by which you can evaluate historical versus migrated BigFix Inventory completeness.
6. Build a new BigFix Platform environment and set up a new BigFix Inventory instance.
   1. Migrate BigFix Inventory settings and Custom Rules.
   2. Run the first BigFix Inventory import (needed to generate endpoint catalog).
   3. Migrate the BigFix Inventory Custom Catalog.
   4. Execute the following SQL query on both Inventory databases, the legacy one and the new one, to see and compare versions of the catalog custom content:

      select value from dbo.system_globals where name='catalog_custom_content_version'

   5. If the version from the new Inventory database is lower than the old one then update the version in the new database to the value old+1.

      Example:

      • Old value: '--- 12'
      • New value: '--- 13'

         update dbo.system_globals set value='--- 13' where name='catalog_custom_content_version'

   6. Run the second BigFix Inventory import.
   7. Set up the BigFix Inventory scans (use at least 1 week scan distribution).
   8. Set up custom analysis.
7. Migrate the computers/devices to the new BigFix Platform.
   1. Deploy BigFix Inventory Scanner if it is missing.
   2. Apply endpoint adjustments, for example, exclusions.
   3. Migrate computer/device specific information to new BigFix Inventory instance once the first scan has been executed and deployed.
8. Deploy / check BigFix Inventory VM Manager instances.
9. Review the completeness of migration as per documented migration reconciliation process.
10. Make sure the majority of computers reporting data in BigFix Inventory.
11. Reactivate 3rd party integrations.

Unchanged Computer ID and Database Type Migration Plan – High Level

In this scenario, it is assumed that both Platform and Inventory is still in sync and only BigFix Inventory is moved to new host – server, database or both.

It is recommended to keep the existing installation for historical reporting purposes until setup of new BigFix Inventory Server and switch is complete.

Additional actions to be taken:

1. Switch the legacy BigFix Inventory instance to read-only mode.
   1. Disable BigFix Inventory imports after the final import is successful.
   2. Ensure that end users understand the change in functions from active use to historical reporting use - announce to use BigFix Inventory only for read-only purposes.
2. Execute last 3rd party synchronization and disable jobs on legacy instance.
3. Secure BigFix Inventory instance for historical reporting.
4. Perform BigFix Inventory database backup.
5. Build a new BigFix Inventory environment and setup new BigFix Inventory instance.
   1. Restore BigFix Inventory database from the backup.
   2. During initial configuration of BigFix Inventory, enter the connection details to the restored database.
   3. Migrate BigFix Inventory settings stored in file system, Server Certificate, SSO settings, jvm.options or server.xml customizations.
   4. Run the first BigFix Inventory import (needed to generate endpoint catalog and push it to the endpoints from the new server).
6. Review the new instance.
7. Reactivate 3rd party integrations against new BigFix Inventory instance.
8. Remove the old BigFix Inventory instance.