Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Cell Manager migration toolkit

Cell Manager migration toolkit

Brief description:

Since more and more customers are moving away from HP-UX Cell Managers we need a scalable and fully supported way of migrating to Linux and or Windows Cell Managers. This solution must work for very large cells with 10000+ media.

From our point of view this could be done using a combination of:

  1. Setup a new Cell Manager running the same version on the new target platform in parallel, manual setup
  2. Use to foreign Cell Manager capability to make it known by the source Cell Manager
  3. Provide a command that will run the migration with two possible combinations
    • Target Cell Manager will use a new name
    • Target Cell Manager will take over the name of the source system as part of the process
  4. The source and target Cell Manager are validated against a supported migration path
  5. The source Cell Manager is put into maintenance mode disabling everything that could alter the source system (B2D clean-up, daily maintenance, trigger, etc.)
  6. The process will take care of everything that is stored in the source IDB (sessions, protected and unprotected cartridges, etc.)
  7. As a part of the process all cartridges with protected objects are exported to a local export folder for MCF export. This should execute in parallel to optimize for high processing rate (consider available number of cores on source system).
  8. Other configuration items (cell_info, backup specs, etc.) are collected and stored in the export folder
  9. Session message files are translated and stored in a transport format like MCF
  10. As a part of the workflow the user needs to copy the export folder to the destination system and start the import process of all MCF and SMBF export files as one big operation. This should execute in parallel to optimize for high processing rate (consider available number of cores on target system). Configuration data is imported.
  11. Based on the scenario selected earlier
    • The source Cell Manager is shut down and the name of the target Cell Manager is changed
    • Clients are forced to use the new Cell Manager name and device entries are updated to use the new Cell Manager name

Benefit:

Have the right set of tools required to drive this required operation that will become more and more popular as HP-UX and the Itanium hardware ages and drives support cost. This can also be used for regular Cell Manager migrations where users need to replace Cell Manager hardware in the future.

2 Comments
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Under Consideration
 
Super Contributor.. Aleksandr_Sviridov Super Contributor..
Super Contributor..

We've been ascing for a tool like this for a long time (trying to move our extra-large Cell from HPUX to RHEL for 2 or 3 years). HPE told us it's impossible to convert the database.

Hope your idea with this migration algoritm will work.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.