- This topic has 3 replies, 3 voices, and was last updated 6 months, 1 week ago by .
We are looking to upgrade from v6.1 (using encryped SMATDB) to v22.09 and I am wondering if anyone can help me figure out a few things. We have always employed services for our upgrades in the past, but I thought I would give this one a try. I remember them validating data through the new server to make sure all of our routes and scripts work as expected, but that was all on regular SMAT files so the process was a little easier. We switched the system to use encrypted SMATDB after the go live.
We have installed v22.09 on a new test server due to OS requirements (Redhat 8). Our 6.1 install is running on Redhat 6 which is no longer supported. I have copied over our sites from the current test server to the new test server and ran the HCIROOTCOPY command to bring them all into v22.09 successfully.
Now I am wondering how I can validate PROD data through the TEST sites to make sure all the routes and scripts work correctly? Since the SMATDB files are encrypted, I can’t just copy them over since the site names are different. Do I need to create my new PROD server and migrate a copy of the PROD sites so the encryption matches, or will I need to dump out Inbound Data to text files so they can be sent through the TEST site? How can I start the Outbound Connections to save the processed messages without conflicting with connections from the current test server? Is there a good comparison tool to use?
My thought was to start with the TEST environment so we can migrate that first and get experience on the process and an estimate on how long it will take when we migrate PROD. We just don’t have a lot of TEST messages to use so I was hoping to validate with PROD data.
If anyone has any tips for the upgrade process or issues to look out for I would greatly appreciate them. I am probably making this harder than I need to but I want to minimize the surprises.
- You must be logged in to reply to this topic.