How To
Summary
Use this document to review the best practices for Data Replication on the HMC.
Objective
- Peer-to-Peer
Provides automatic replication of the selected customized data types between peer HMCs. Changes made on any of these consoles are replicated to the other consoles.
- Primary-to-Secondary
Provides automatic replication of the selected customized data types from one or more designated primary HMCs to one or more designated Secondary HMCs. Changes made on a Primary console are automatically replicated to the Secondary console(s).
When using either method, note the best practices:
========================
Primary-to-Secondary replication
========================
1. When HMCs are configured for primary-secondary replication perform all user modification operations such as create, delete and modification on the primary HMC. It is applicable for all LDAP, Kerberos and Local users.
2. Warning message is shown on secondary HMC(s) GUI when any user data modification is performed. Ignoring that may cause data loss if the user is only present in secondary.
========================
Peer-to-peer replication
========================
1. When auto-manage user management is enabled for LDAP and user wants login to both HMCs, then enable peer-to-peer replication.
========================
For both types of replication
========================
1. When deleting any user it is suggested to close all active ssh sessions of the user before the deletion attempt.
Related Information
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
05 November 2024
UID
ibm16113644