Renaming dynamic disk group while importing


Renaming dynamic disk group while importing
Prev	Recovering from problems during replication	Next

When importing a dynamic disk group, you may need to rename it, if a dynamic disk group of the same name has already been imported on the host. If the dynamic disk group that needs to be renamed contains Volume Replicator objects, then replication does not restart after importing the renamed disk group.

Warning:

Volume Replicator objects are created even if some disks are unavailable while importing the dynamic disk group. However, the Volume Replicator configuration in such a case may be invalid and replication may not restart even after performing the steps that are given below. Importing a partial dynamic disk group after resetting the disk group Host ID may result in losing the integrity of dynamic disk group organization.

Use the following steps to enable replication after the disk group is imported. Ensure that all disks and volumes of the imported dynamic disk group are accessible and in a HEALTHY state before proceeding.

This example assumes that the following setups are already set:

host_imp

The host on which you import the dynamic disk group after renaming.
dg_name_imp

The new name of the dynamic disk group.

All other hosts in the Volume Replicator configuration are referred to as remote host(s).

To enable replication after the disk group is imported

On host host_imp, find the RLINK objects to remote host(s) for the Volume Replicator configuration, using:
```
vxprint -g dg_name_imp -P
```
This displays the list of RLINKs (among other things), in the following format:
```
rl <rlink_name> attributes
```

For each RLINK object in the dg_name_imp dynamic disk group, find the corresponding remote objects, using:

vxprint -g dg_name_imp -l <rlink_name> | findstr "remote_"

This displays the remote objects in the following format:

remote_host = <remote-host-name or ip>
remote_dg = <name of the remote disk group>
remote_rlink = <name of the corresponding remote rlink>

For every RLINK on the remote host change the remote_dg attribute of the corresponding remote RLINK using the following commands:
Pause and Resume operations are permitted only on RLINK objects in ACTIVE state. If any of the remote RLINKs are not ACTIVE, then, the Pause operation fails. In such a case, do not perform the Resume operation.
```
vxrlink -g <remote_dg> pause <remote_rlink>
vxrlink -g <remote_dg> set remote_dg=dg_name_imp <remote_rlink>
```
If the pause operation above succeeded then run the following command:
```
vxrlink -g <remote_dg> resume <remote_rlink>
```
Run these commands on each of the remote hosts.
Verify the changes on every remote host, using:
```
vxrds -g <remote_dg> printrvg
```
This command should list the RVGs on host_imp as part of the RDS(s).

Prev	Up	Next
Using two commands in succession	Home	Problems when performing the snapshot operation