Moving GNS to Another Cluster

Note:

This procedure requires server cluster and client cluster downtime. Additionally, you must import GNS client data from the new server cluster to any Oracle Flex ASM and Grid Home servers and clients.

If it becomes necessary to make another cluster the GNS server cluster, either because a cluster failure, or because of an administration plan, then you can move GNS to another cluster using the following procedure:

Stop the GNS instance on the current server cluster.
```
# srvctl stop gns
```
Export the GNS instance configuration to a file.
```
# srvctl export gns -instance path_to_file
```
Specify the fully-qualified path to the file.
Remove the GNS configuration from the former server cluster.
```
# srvctl remove gns
```
Add GNS to the new cluster.
```
# srvctl add gns -domain domain_name -vip vip_name
```
Alternatively, you can specify an IP address for the VIP.
Configure the GNS instance in the new server cluster using the instance information stored in the file you created in step 2, by importing the file, as follows:
```
# srvctl import gns -instance path_to_file
```
Note:

The file containing the GNS data from the former server cluster must reside on the node in the cluster where you run the srvctl import gns command.
Start the GNS instance in the new server cluster.
```
# srvctl start gns
```