I have a customer using 3x UVM2016 in A/A mode and want to upgrade to UVM2022 A/A.Problem is, their existing UVM2016 are all SQLFree. Now we want to move to 1x UVM2022 with SQL as primary + 2x UVM2022 SQLFree.What is the best practice to do the upgrade for all nodes? If i want to upgrade just primary appliance from UVM2016SF to UVM2022SQL, is it okay? Can i just level everything, add new node, config as primary, and turn off the old node? What will happen to existing session records? Can we bring them from old appliance to new appliance? Is there any other consideration?

Hi @jchandlerthank you for the answer.After months, turns out that the database they used for current A/A setup is SQL Enterprise 2012.So based on the guide, the simplified steps i need to take are like this:Deploy 3 new 2022 UVMs into the A/A pool (1 SQL UVM, 2 SF UVMs), so there will be 6 UVM node in total (temporarily)Configure A&R on the primary nodeMake sure everything is running properlyRemove all 2016 UVMs after the three new nodes are running perfectlyUse the new UVMIs that correct?But can SQL Enterprise 2012 be used for UVM 2022?Also, the recording file will be gone, right?

How to upgrade UVM 2016 to UVM 2022 in A/A site

I have a customer using 3x UVM2016 in A/A mode and want to upgrade to UVM2022 A/A.

Problem is, their existing UVM2016 are all SQLFree. Now we want to move to 1x UVM2022 with SQL as primary + 2x UVM2022 SQLFree.

What is the best practice to do the upgrade for all nodes?
If i want to upgrade just primary appliance from UVM2016SF to UVM2022SQL, is it okay? Can i just level everything, add new node, config as primary, and turn off the old node?
What will happen to existing session records? Can we bring them from old appliance to new appliance?
Is there any other consideration?

Page 1 / 1

Hello Raymondus,

You can use the standard migration to move to 2022 appliances.

You can find our migration guide here.

https://www.beyondtrust.com/docs/beyondinsight-password-safe/appliance/migration/index.htm

Since you don’t have A&R currently configured because your appliances are SQL free just do a new configuration after migration.

Regards,

John

Hi @jchandler thank you for the answer.

After months, turns out that the database they used for current A/A setup is SQL Enterprise 2012.

So based on the guide, the simplified steps i need to take are like this:

Deploy 3 new 2022 UVMs into the A/A pool (1 SQL UVM, 2 SF UVMs), so there will be 6 UVM node in total (temporarily)
Configure A&R on the primary node
Make sure everything is running properly
Remove all 2016 UVMs after the three new nodes are running perfectly
Use the new UVM

Is that correct?

But can SQL Enterprise 2012 be used for UVM 2022?
Also, the recording file will be gone, right?

Hello @raymondus

The migration process listed in the guide is a backup and restore process.

Backup the 2016 appliance then shut it down.

Deploy new appliance with exact same name as old appliance and restore backup.

Now your new 2022 appliance is up and running with the same name as the original 2016 appliance.

Also for the SQL server version

The requirments for SQL are listed in our release notes. https://docs.beyondtrust.com/bips/changelog/beyondinsightpassword-safe-25-1-release-notes#-requirements

The current version of Password Safe supports SQL Server 2016 SP2 or higher

Hi @jchandler i understand, using SQL Server 2012 is no longer an option, user must upgrade the database to at least SQL version 2016, or preferably to 2019 or even 2022. I tried 2022 enterprise before, and it works with A/A setup (with compatibility set to lower version).

I am also aware that their future version (PS version 25.1) requires some specific SQL version patches. So, it's not feasible to force compatibility if they insist on continuing to use their old database in the new UVM, even if somehow it just works for version 24.x.

Thank you so much for the enlightenment

Reply

Badge Earners

Reply

Badge Earners

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded