Ways to install downgrade version of qlik replicate

[Mythili_B]

Hi Team,

I have QLik replicate 2022.11 version currently. I need to upgrade the version to 2023.5 (latest version). I would like to understand whether we can do downgrade install ie again from 2023.5 to 2022.11  in case of any issue? If so , what is the steps? 

i) As per the release note, it is necessary to uninstall the current version and install the version needed. In that case, will that impact the existing setup and all configurations ? what about license? Whether it is required to do license again after uninstall?

ii) If i want to stop all the task in qlik replicate before installation/uninstallation, what is the process for stopping and starting all task in one go (without any manual process) 

Thanks,

Mythili Boopathy

[DesmondWOO]

Hi @Mythili_B ,

i) As per the release note, it is necessary to uninstall the current version and install the version needed. In that case, will that impact the existing setup and all configurations ? what about license? Whether it is required to do
license again after uninstall?

> Yes. During upgrade, Replicate's settings may be updated too. In case you want to downgrade  from v2023.5 to v2022.11, I would suggest:
** Make sure you have a backup of v2022.11 before upgrading to v2023.5 **
1. Uninstall v2023.5
2. Delete Replicate's folder
3. Install v2022.11
4. Restore v2022.11 backup

Since Replicate's saved information is outdated such as stream position. I would suggest to reload the tasks. Also, you may need to update your task settings accordingly if something has been changed after upgrade, e.g. transformation. 

You don't need to register the license again if you have a backup to restore.

ii) If i want to stop all the task in qlik replicate before installation/uninstallation, what is the process for stopping and starting all task in one go (without any manual process) 

> I think you may write a script to stop the tasks by using repctl command. Please check this article for details.

Regards,
Desmond

[Barb_Fill21]

@Mythili_B 

Also Whenever you upgrade ( in particular for Windows) see these steps, so that you have a saved copy of the \DATA folder. This is the most import thing to back up before doing any upgrade. It will help with downgrading. 

Client ( REP SERVER) UPGRADE (Windows)
1.) Stop all tasks. if not already.
2.) Wait for the tasks to finish Stopping.
3.) Stop the 2 Replicate services. (server and UI)
4.) From the Replicate Command Line Console run the following AS ADMINISTRATOR!!!!

repctl exportrepository

(for alternate data directories use the syntax:

repctl -d YOUR DATA DiRECOTRY PATH exportrepository

It becomes the REPLICATION_DEFINITION.JSON keep this!

5.) Clean out any unneeded Logs In the Task Folders then Back-up or copy the \Replicate\data directory-folder to a directory-folder located outside of the Attunity product.
6.) After unzipping, RightMouseClick on .exe RUN AS ADMINISTRATOR for Replicate upgrade on Windows Server
7.) Resume the Gui tasks.
============================================================================================

If you need to Back Out:

1.) The back out requires the product to be uninstalled and then installed to the same directory using the previous kit.
2.) Once the install is done stop the Attunity Services and copy/overwrite the data directory with your backup.
3.) start the Attunity services
=============================

See this Link for more information:

https://help.qlik.com/en-US/replicate/May2023/Content/Replicate/Main/Installation/windows_setup.htm

Sincerely,

Barb

[MoeyE]

Hi Desmond,

Is a proper downgrade as simple as doing the below steps without stopping the services?

1. Uninstall current version (with control panel or the QR exe?)
2. Delete Replicate's folder 
3. Install new version
4. Restore v2022.11 backup

This is because when I need to downgrade, I stop the services first:

1. Stop all tasks

2. Stop all services

3. Run the Qlik Replicate exe to uninstall the current version of Qlik Replicate

4.Once uninstalled, run the QR exe to install the previous version

5. Once installed successfully, stop both services, rename the data folder, replace it with the backup data folder.

Regards,

Mohammed

[john_wang]

Hello Mohammed, @MoeyE 

Thanks for the update.

I'd like to follow the below steps:

1. Stop all tasks

2. Stop all services

3. Run the Qlik Replicate exe to uninstall the current version of Qlik Replicate

4. Restore the previous versions BACKUP folders

5. Run the QR exe to install the previous version

In step (5) if the DATA folder exists then Qlik Replicate installation program will keep using it and verifies it's accessibilities.

Hope this helps.

John.

[MoeyE]

Hi John,

Thanks. So in step 4, there's nothing wrong with inserting the backup data file before reinstalling the previous version? I've always reinstalled the previous version then replaced the data folder with the backup.

Regards,

Mohammed

[john_wang]

Hi Mohammed, @MoeyE 

You are right - it's simple with inserting the backup data file before reinstalling the previous version. Because Replicate will check and access the previous version repository files.

Regards,

John.

[Heinvandenheuvel]

To add a bit more to my friend @Barb_Fill21  reply, you need that imports\Replication_Definition.json file made by repctl exportrepository before upgrading. Rename/Copy it to have a very clear name for example by including the server name and date and move it away from the Replicate data directory structure where it could all to easily be blown away.

Maybe, just maybe the new, upgraded, binary replication definition files such as RepoGlobal.repo are compatible between version, but they might not. Specifically they are unlikely to be compatible when there is a major version changes - but that itself is no longer clear for end user since Replicate stepped away from versions like 6.x.y.z and 7.x.y.z and went to a date based naming like the 2022.11 as mentioned. You could restore those from backups, but what if the (unlikely) upgrade issue is found out to far down the road and you loose changes?

Now you could, AND SHOULD, do another exportrepository to a safe space and name just before the (unlikely) downgrade. There are good odds that this export is readable by the prior version, but it is not garantueed. The new version might introduce new attributes which are not understood by the older version.

If that case you can run a 'compare' or 'differences' tool between the old/new JSON exports to see what changed and address that, carrying desirable task changes forward but avoiding new features not understood.

Hein.