Running Concurrent Repository Upgrades For Data Services 4.2 During Patching

[Former Member]

Hello,

We are patching Data Services 4.2 (to 14.2.7) which requires upgrading the repositories to the new patch level. We have 6-8 repositories in each DS system and each one is taking 2 - 2-5 hours to  complete using the Data Services Repository Manager. Is there a way to run concurrent upgrades on the repositories, or a method to speed up the upgrades? The Data Services Repository Manager seems to be a single taking tool when it comes to upgrading repositories. Any help would be greatly appreciated!

Thank you,

Denis

[former_member18162 · Accepted solution]

Hi Denis,

This could be done if you had multiple machines with DS 4.2 SP7 Repository Manager installed and each one pointed to a different DS repository for upgrade.

Regarding the time to upgrade, if it wasn't done before, it is highly recommended any failing jobs in your repos be fixed or removed prior to the upgrade process as broken designs can slow things down. The repo upgrade process will not fix broken jobs.

Cheers!
Julie

[Former Member · Accepted solution]

Julie,

Thank you for the quick reply! Have you tried the multiple machines approach before?

Thank you,

Denis

[former_member18162 · Accepted solution]

Hello,

I wish we had the time and resources to build out and fire up multiple boxes like that

Basically each system will use the database client to make a separate connection to each database repository.

If you have multiple schemas in the same database space, and each schema is a repository, this should still work; however it might be more taxing.

Whatever do decide to do, make certain to backup all your db repositories first.

Thank you,
Julie