Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Vanness_Chen
Explorer
Jump to solution

upgrade R82 maestro from R81.10SP

I am currently preparing an upgrade plan for a customer to migrate Maestro from R81.10 to R82. After reviewing several upgrade cases, I am concerned about the possibility of unexpected issues during the process.

I am considering splitting the upgrade into three phases (SMS → MHO → SG), with more than one week between each phase.
Would this approach be feasible?

I would greatly appreciate any recommendations or best practices you could share.

Thank you in advance for your guidance.

0 Kudos
1 Solution

Accepted Solutions
Martijn
MVP
MVP

Hi,

The three phase approach is a good one. You should do that!!

Upgraded a Maestro environment from R81.10 to R82 last year and followed the steps described in the R82 Maestro Installation and Upgrade guide. The steps are very well described and easy to follow.

Preperation is very important. Make sure you have all the software downloaded. Hotfixes, Deployment Agent etc. Also make sure you are on the correct hotfix for R81.10 before upgrading. All is in the Upgrade guide.

On MHO's disk space can be an issue, so follow:

sk182325 - Importing a CPUSE package on Maestro Orchestrator fails with "There is not enough disk sp...

Before upgrading make sure you have backups and snapshots created. An Auto-snapshot will be created when upgarding to R82.

And  make sure Implied Rules are enabled. In the past I had some issues with a policy install during the sp_upgrade script procedure. Maybe caused by Implied Rules not being enabled. Since enabling Implied Rules during the upgrade, I had no issues.

Good luck!!

Martijn

View solution in original post

(1)
6 Replies
Vincent_Bacher
MVP Silver
MVP Silver

I don't have best practices as we don't use scalable platform devices such as 64k or Maestro anymore.
But i would say this approach is correct.
The only additional point I would consider is doing a clean install on the devices because of the move from the "special" scalable platform release R81.10SP to the "universal" release R82.

and now to something completely different - CCVS, CCAS, CCTE, CCCS, CCSM elite
Vanness_Chen
Explorer

Hi @Vincent_Bacher

If we choose to perform the upgrade using a clean installation, wouldn’t the existing configuration and data be lost?

Or is it possible to use the command from SK174202
set maestro export local orchestrator — to create a backup on R81.10, and then import it after upgrading to R82?

 

0 Kudos
Vincent_Bacher
MVP Silver
MVP Silver

tbh i am not sure, maybe other mates can answer this question better.
But from my end the mentioned sk is feasible.

and now to something completely different - CCVS, CCAS, CCTE, CCCS, CCSM elite
0 Kudos
emmap
MVP Gold CHKP MVP Gold CHKP
MVP Gold CHKP

It's not a QA'd or supported upgrade method for MHOs. 

0 Kudos
Alex-
MVP Silver
MVP Silver
Martijn
MVP
MVP

Hi,

The three phase approach is a good one. You should do that!!

Upgraded a Maestro environment from R81.10 to R82 last year and followed the steps described in the R82 Maestro Installation and Upgrade guide. The steps are very well described and easy to follow.

Preperation is very important. Make sure you have all the software downloaded. Hotfixes, Deployment Agent etc. Also make sure you are on the correct hotfix for R81.10 before upgrading. All is in the Upgrade guide.

On MHO's disk space can be an issue, so follow:

sk182325 - Importing a CPUSE package on Maestro Orchestrator fails with "There is not enough disk sp...

Before upgrading make sure you have backups and snapshots created. An Auto-snapshot will be created when upgarding to R82.

And  make sure Implied Rules are enabled. In the past I had some issues with a policy install during the sp_upgrade script procedure. Maybe caused by Implied Rules not being enabled. Since enabling Implied Rules during the upgrade, I had no issues.

Good luck!!

Martijn

(1)