Description
Before moving forward, perform the following steps:
- Take a backup of the Merge1 database
- Take a Snapshot of the Merge1 VM
- Export the PDF from the Licensing section
This will allow for a recovery in case there are issues during the upgrade.
Note: The Merge1 7.0 Agent requires the following to be installed.
• .NET 8.0 Runtime ( Link )
• ASP.NET Core 8.0 Runtime (Link )
Upgrade from a previous version of Merge1 v7
Make sure that all connectors are in an idle state.
Turn off the schedulers.
Stop the Agent service from the Services.
Un-register the old Merge1 agent. (Link)
If Merge1 Agent service fails to be deleted, perform manual deletion:
Delete the Merge1 Agent service by running SC Delete <agent service name> in CMD prompt.
- Uninstall the Merge1 Agent application
Install the new Merge1 version on top of the previous one.
Connect to the same DB and upgrade the schema(important!).
Open Merge1 and verify the version from Licensing.
Install the Merge1 Agent application
Register the new Merge1 agent. (Link)
Turn on the Agent service from the Services.
From the Agent Pools section, verify the Merge1 Agent version.
Turn on the schedulers
Important Notes
You must install the new version of the Agent. The Merge1 application version and the version of the Merge1 Agent must be the same.
Before you begin the upgrade, regardless of your current version, please make sure to export the PDF from the licensing section. This step is important because during the upgrade, we need to upgrade the database's schema. This will reset the license to a one-month trial period each time and change the Activation Request Code, which is based on the machine's MAC address and hashes of the CPU ID. By exporting the PDF from the licensing section before the upgrade, the Technical Support Engineer (TSE) will have information about your connectors, user count, and expiration date. They will then generate a new license key with the updated activation request code based on the information in the PDF.
If using the Audit DB, you will need to manually connect to the Audit DB after installing the new version and upgrading the schema of the Merge1 DB,
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.