Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition System Administration Guide

Search Scope:

- This Document
- Entire Library

## Renaming a Cluster That Is in a Partnership

When you rename a cluster that is in a partnership, the partnership becomes invalid. You must fully unconfigure the existing partnership and create a new one that uses the new cluster name.

## How to Rename a Cluster That Is in a Partnership

This procedure demonstrates how to rename one of the global clusters that is in a partnership. You can rename more than one of the clusters at the same time.

Note - You cannot use this procedure to rename a zone cluster in a partnership.

If the cluster that you rename belongs to more than one partnership, perform each step on all clusters that share a partnership with the cluster to rename, before you proceed to the next step in the procedure.

1. From one node of the cluster that you are renaming, remove resource groups from each protection group that the cluster belongs to.

   This task avoids production application downtime.

       # geopg remove-resource-group app-rg pg1

2. From one node of each cluster in a protection group, confirm that application resource groups have been removed.

       # geopg list pg1

3. From one node of the cluster that you are renaming, stop each protection group globally.

   This task stops data replication.

       # geopg stop pg1 -e global

4. From one node of each cluster in a protection group, delete the protection group

       # geopg delete pg1

5. From one node of each cluster in a partnership, leave the partnership.

       # geops leave-partnership ps1

6. From one node of each cluster, confirm that the protection group and the partnership have been removed.

       # geoadm status

7. From one node of each cluster, disable Geographic Edition software.

       # geoadm stop

8. From one node of each cluster, confirm that Geographic Edition software was disabled.

   Verify that the `geo-infrastructure`, `geo-clusterstate`, and data-replication resource groups are deleted.

       # clrg list
       # geoadm status

9. From one node of the cluster that you are renaming, change the cluster name.

   Follow cluster naming guidelines as described in Planning Required IP Addresses and Hostnames in Oracle Solaris Cluster Geographic Edition Installation Guide.

       # cluster rename -c new-clustername

   Note - The name of the cluster must not include the domain. If a partnership contains clusters that are in different domains, you specify the domain to administrative commands, when necessary, by appending the domain name to the cluster name as cluster.domain. Only certain Geographic Edition administrative commands require this fully qualified name when clusters in a partnership are not in the same domain.

10. Confirm that the cluster name is changed.

        # cluster list

11. On each node of both clusters, ensure that hostname entries that match the new cluster name are free and are added to the local `/etc/inet/hosts` files.

    If clusters in the partnership are in different domains, include the domain in the `/etc/hosts` entry for each cluster.

        # ping new-clustername there should be no response
        # echo "IPaddress new-clustername" >> /etc/inet/hosts

12. From one node of each cluster, start Geographic Edition software.

        # geoadm start

    If Geographic Edition software fails to start, and the failure is not due to problems with the new logical host, restart the common agent container on all nodes by using the `cacaoadm restart` command, then start Geographic Edition software.

13. From one node of each cluster, verify that Geographic Edition software is successfully started.

        # geoadm status

14. From one node of each cluster, add trust between the clusters.

        # geops add-trust -c remotepartnerclustername[.domainname]

15. From one node of each cluster, confirm that trust is added successfully.

    Note - Do not specify a domain name to the `verify-trust` subcommand.

        # geops verify-trust -c remotepartnerclustername

16. Create and join a new partnership between the clusters.
    1. From the primary cluster, create the partnership.

           # geops create -c remotepartnerclustername[.domainname] partnershipname

    2. From the secondary cluster, join the partnership.

           # geops join-partnership remotepartnerclustername[.domainname] partnershipname

17. On each cluster, confirm that the new partnership is successfully created and joined.

        # geoadm status

18. If you did not reboot the nodes of the cluster that you renamed, restart the heartbeats on each node of the renamed cluster.

    Restarting the heartbeat initiates the heartbeat to read and store the new cluster name.

        # svcadm disable svc:/system/cluster/gchb_resd:default
        # svcadm enable svc:/system/cluster/gchb_resd:default

Example 5-5 Renaming a Cluster in a Partnership

This example renames the cluster `newyork`, in the `paris-newyork-ps` partnership, to `chicago`. The names of the nodes in this cluster are not changed, so `phys-newyork-1` becomes a node in the newly named `chicago` cluster. The `paris-newyork-ps` partnership is first unconfigured. After the cluster is renamed, a new `paris-chicago-ps` partnership is created with the `chicago` cluster as primary and the `paris` cluster as secondary. The two clusters belong to the same domain, so the domain name is not specified to the commands.

    phys-newyork-1# geopg remove-resource-group app-rg

    phys-newyork-1# geopg list examplepg
    phys-paris-1# geopg list examplepg

    phys-newyork-1# geopg stop examplepg -e global

    phys-newyork-1# geopg delete examplepg
    phys-paris-1# geopg delete examplepg

    phys-newyork-1# geops leave-partnership paris-newyork-ps
    phys-paris-1# geops leave-partnership paris-newyork-ps

    phys-newyork-1# geoadm stop
    phys-paris-1# geoadm stop

    phys-newyork-1# clrg list
    phys-newyork-1# geoadm status
    phys-paris-1# clrg list
    phys-paris-1# geoadm status

    phys-newyork-1# cluster rename -c chicago
    phys-newyork-1# cluster list

    phys-newyork-1# ping chicago
    phys-newyork-1# echo "192.168.10.1 chicago" >> /etc/hosts
    repeat on each node of the chicago cluster

    phys-paris-1# ping chicago
    phys-paris-1# echo "192.168.20.1 chicago" >> /etc/hosts
    repeat on each node of the paris cluster

    phys-newyork-1# geoadm start
    phys-paris-1# geoadm start

    phys-newyork-1# geoadm status
    phys-paris-1# geoadm status

    phys-newyork-1# geops add-trust -c paris
    phys-paris-1# geops add-trust -c chicago

    phys-newyork-1# geops verify-trust -c paris
    phys-paris-1# geops verify-trust -c chicago

    phys-newyork-1# geops create -c paris paris-chicago-ps
    phys-paris-1# geops join-partnership chicago paris-chicago-ps

    phys-newyork-1# geoadm status
    phys-paris-1# geoadm status

    phys-newyork-1# /etc/init.d/initgchb_resd stop
    phys-newyork-1# /etc/init.d/initgchb_resd start
    repeat on each node of the chicago cluster

    phys-paris-1# svcadm disable svc:/system/cluster/gchb_resd:default
    phys-paris-1# svcadm enable svc:/system/cluster/gchb_resd:default
    repeat on each node of the paris cluster

Next Steps

Perform the following tasks:

- Create a new protection group and replicate it to partner.

- Add device groups.

- Start globally.

- Add resource groups to the protection group and verify the configuration.

NOTE - When you create the new protection group, pay close attention to which cluster is the primary and which is the secondary, to ensure that data replication is started in the desired direction.

Follow procedures in the appropriate data-replication guide:

- Chapter 2, Administering Sun StorageTek Availability Suite Protection Groups, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Sun StorageTek Availability Suite

- Chapter 2, Administering Hitachi TrueCopy and Universal Replicator Protection Groups, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator

- Chapter 2, Administering Hitachi TrueCopy and Universal Replicator Protection Groups, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator

- Chapter 2, Administering SRDF Protection Groups, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for EMC Symmetrix Remote Data Facility

- Chapter 2, Administering Oracle Data Guard Protection Groups, in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Oracle Data Guard

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |