| PRIMECLUSTER Installation and Administration Guide 4.2 (Linux) |
Contents
Index
![]()
|
| Appendix G Changes in Each Version | > G.1 Changes in PRIMECLUSTER 4.2A00 from 4.0A20 |
Details on incompatibilitiesThe procedures for registering and deleting resources for PRIMECLUSTER-compatible products have been changed.
Changes
Before upgradingRegistering resources for PRIMECLUSTER-compatible products
Execute multiple commands to register the following resources for PRIMECLUSTER-compatible products:
Resources of cluster services
Resources of cluster service instances
Deleting resource for PRIMECLUSTER-compatible products
Execute multiple commands to delete the following resources for PRIMECLUSTER-compatible products:
Resources of cluster services
Resources of cluster service instances
Reconfiguring a cluster application
Delete the cluster service, and then register the cluster service again.
After upgradingRegistering resources for PRIMECLUSTER-compatible products
Execute the "clrwzconfig" command to register the following resources for PRIMECLUSTER-compatible products:
Resources of cluster services
Resources of cluster service instances
Deleting resources for PRIMECLUSTER-compatible products
Execute the "clrwzconfig" command to deleted the following resources for PRIMECLUSTER-compatible products:
Resources of cluster services
Resources of cluster service instances
Reconfiguring a cluster application
The cluster service must be registered when a cluster application is reconfigured.
Use the "clrwzconfig" command to check whether the cluster service needs to be set up again. If re-setup of the cluster service is necessary, execute the "clrwzconfig" command.
NoteThe following operations have not been changed:
Registering a resource for IP address takeover and associating a resource to a cluster service instance
Deleting a resource for IP address takeover
Contents
Index
![]()
|