Skip to main content
NetApp Knowledge Base

Unified Manager upgrade steps from 7.2.x/7.3.x/9.4.x to 9.5 version

Views:
3,516
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
legacy
Last Updated:

Applies to

  • OnCommand Unified Manager 7.2.x
  • OnCommand Unified Manager 7.3.x
  • OnCommand Unified Manager 9.4.x
  • OnCommand Unified Manager 9.5

Answer

  • Unified Manager database backup sizes tend to increase over time and can cause issues while upgrading
    • The number of records in continuous_event_participant and continuous_event_participant_stats tables tend to increase if UM is managing larger ONTAP footprints or if managing ONTAP nodes for a long period of time.
    • View guidelines around AIQUM backup and restores for Best Practices
  • This article provides guidelines on how to plan for Unified Manager upgrades as well as plan database backups in a more defined format to improve restore times.
  1. Take a full backup before upgrading
Click to view procedure
  1. For UM on VMware (vApp)
    1. Take a VMware snapshot
    1. For UM on physical system or non-VMware
      1. Start a new incremental backup chain within AIQUM
      2. Trigger a backup from the UI

Note: When a full backup is in session, MySQL tables are locked, which means that no new "Cluster Monitoring / Polling" updates can be added to the Active IQ Unified Manager MySQL database until the full backup process has completed. This can also mean service outage for some until the full backup is complete.

Warning: If the snapshot or backup will not be taken according to the procedures written above, they might not be consistent and likely will not be usable. hence you will have no backup.

  1. Optimize tablespace sizes
Click to view procedure
  1. To prevent upgrade failures, you first need to check the number of entries in the “opm” schema tables
    1. continuous_event_participant
    2. continuous_event_participant_stats.
  2. Use the following method to check table sizes (in MBs)
    1. Execute mysql in CLI, to gain access to the database
    2. Type in the following query to find the sizes of tables in MB
SELECT table_name AS `Table`, round(((data_length + index_length) / 1024 / 1024), 2) `Size in MB` FROM information_schema.TABLES WHERE table_schema = "opm" AND table_name IN ('continuous_event_participant', 'continuous_event_participant_stats');
  1. The output would be similar to the following:
1089470.png
  1. View table sizes from the database
    1. If the sizes of the tables are significantly large that is if the sum of the two tables are going beyond 700MB, engage NetApp Support to prune data in the tables: continuous_event_participant and continuous_event_participant_stats
  1. Skewing the upgrade timeouts
Click to view procedure
  1. If upgrading 7.2.x/7.3.x to 9.4 or 7.3.x upgrade to 9.5, you will likely run into BUG 1214422 if there is a decent amount of history data.
  2. In which case it is recommended to engage NetApp Support to trim down the two tables
    1. continuous_event_participant
    2. continuous_event_participant_stats
  1. Begin the upgrade process

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.