cancel
Showing results for 
Search instead for 
Did you mean: 

How to Change the DiskGroup ID.

unix_san
Level 4
Certified

Hello,

We have SFHA 6.0 installed on Solaris 10.  We have changed the hostname of the solaris server and hence I need to change the diskgroup id of a particular diskgroup. What will be the command or procedure for this?

 I have enabled the newhostname using vxdctl hostid, but the diskgroup does not changes after this.

8 REPLIES 8

mikebounds
Level 6
Partner Accredited

You don't need to change the ID - this is just a unique identifier, so for instance in a cluster the ID will have the hostname embedded in it for the host where the diskgroup was created, but this still means it is perfectly ok to import on other nodes in the cluster.

Mike

unix_san
Level 4
Certified

Thanks for this.

Just out of curiosity, is there any command/procedure to change the diskgroup id?

Gaurav_S
Moderator
Moderator
   VIP    Certified

not to my knowledge .. even the vxedit -g <dg> set options doesn't have attribute to modify this.

I have not really tried if dg id changes if you deport & import diskgroup with a new name. Else, dgid will only change if dg is destroyed & recreated  but you wouldn't really want to do that unless there is a major problem because of DG ID.

 

G

novonil_choudhu
Level 4
Employee Accredited

This might help 

https://www-secure.symantec.com/connect/downloads/script-change-group-id-veritas-disk-group

starflyfly
Level 6
Employee Accredited Certified

For SF, You may need update volboot :

 

Update the volboot file and the hostid field of all the disks that are part of an imported disk group.

# vxdctl hostid [new hostid]
 

 

For cluster, more work need do.

mikebounds
Level 6
Partner Accredited

Note the script link provided by Novonil is doing what Gaurav says you would need to do which is to destroy and recreate the diskgroup - this does this with the data intact (in theory !) as detroying a diskgroup only removes the private region so if you recreate diskgroup with exact same volume boundaries, then data is ok.

The script seems well written with some inbuilt error checking but I would not recommend using this script as there are still risks to your data and changing the diskgroup id in your case is just for cosmetic reasons, rather than a necessity for which this script is provided when taking clones of a diskgroup (where if the script fails, you still have original diskgroup so you don't loose data).

Mike

starflyfly
Level 6
Employee Accredited Certified

Try:

vxdg -C import dgname

 

If it is certain that a disk is not in use by another host (for example, because a disk group was not
                 cleanly  deported),  use  the  -C option to clear the existing host ID on all disks in the disk group
                 upon import.  A host ID can also be cleared using vxdisk clearimport.

 

Ramesh_Pareet
Level 3
Employee

This technote is for diskgroup id change: You just need to run the script.

http://www.symantec.com/connect/downloads/script-change-group-id-veritas-disk-group

 

Following details for Cluster-ID change:

How to change the cluster name and cluster ID for all shared diskgroups in SFCFS

 
Details:
Customer changes the cluster name in the main.cf in order to change cluster name.
When CVM tries to start, it fails since the old cluster name is still on the private region of all of the shared disks.
Offline the CFS service groups in VCS
# hagrp -offline cfs_sg -sys sys1
Deport the shared diskgroups with vxdg deport
# vxdg deport cfs_dg
Use the vxdg -Cs import outside of VCS to import with the new cluster ID.
# vxdg -Cs import cfs_dg
Online the CFS service groups in VCS
# hagrp -online cfs_sg -sys sys1
 
 
I hope this helps.
 
Regards
Ramesh Pareet