12-02-2013 08:09 PM
Hello All,
I seem to be confused... I have a diskgroup currently imported as externaldb-db2bkup15dg.
tagmastore-usp0_19 auto:cdsdisk db2bkup15-01 externaldb-db2bkup15dg online nohotuse c5t60060E8016016F000001016F0000015Dd0s2 -
When I look at the private region, I see that it is different.
Solved! Go to Solution.
12-02-2013 10:13 PM
Is this particular diskgroup under cluster control, or was it imported manually?
If it was a manual import - is it possible it was imported with a temporary new name (the fact the noautoimport flag is set in vxdisk list output makes me suspect this could be possible).
ie: # vxdg -t -n {tempname} import {dg}
this would explain why the host with the dg imported shows a different name, but the private region is not updated.
from vxdg man page:
Import fails if the specified disk group name is either a reserved name (such as bootdg or nodg) or an existing disk group name. The disk group can be renamed on import using -n newname. If -n is used with the -t option, the stored name of the disk group remains unchanged, but the importing host knows the disk group under the new name; otherwise, the name change is permanent.
example/test:
12-02-2013 08:17 PM
Hello..
Need some more information ..
1. Is this is a clustered setup ?
2. Are you using snapshots with diskgroup split & join ?
3. Can you also let us know when was last update happened to diskgroup config ? you can find this information from /etc/vx/cbr/bk directory ...
4. also paste a full "vxdisk list <disk>" output from both the servers ?
G
12-02-2013 08:34 PM
Thank you for responding!
1. Is this is a clustered setup ? Yes.
2. Are you using snapshots with diskgroup split & join ? No.
3. Can you also let us know when was last update happened to diskgroup config ? you can find this information from /etc/vx/cbr/bk directory ... Nov. 1st 2012.
4. also paste a full "vxdisk list <disk>" output from both the servers ?
12-02-2013 09:28 PM
Both above outputs currently are showing same diskgroup name & I believe these outputs are from different servers ?
group: name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
group: name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
So currently only which output is showing the DG name incorrect ? isit a full "vxdisk list" ?
Please paste from both the servers (also please put host name in the shell so that can identify two different servers)
# vxdisk list
# vxdisk -e list
# vxdg list
# vxdg list externaldb-db2ins15dg
# vxdg list externaldb-db2bkup15dg
G
12-02-2013 10:10 PM
Both above outputs currently are showing same diskgroup name & I believe these outputs are from different servers ? Correct.
So currently only which output is showing the DG name incorrect ? isit a full "vxdisk list" ? They are both showing externaldb-db2ins15dg, however it is currently imported on one of the nodes as externaldb-db2bkup15dg which is correct.
Here it shows me that drive c5t60060E8016016F000001016F0000015Dd0s2 is associated with externaldb-db2bkup15dg.
12-02-2013 10:13 PM
Is this particular diskgroup under cluster control, or was it imported manually?
If it was a manual import - is it possible it was imported with a temporary new name (the fact the noautoimport flag is set in vxdisk list output makes me suspect this could be possible).
ie: # vxdg -t -n {tempname} import {dg}
this would explain why the host with the dg imported shows a different name, but the private region is not updated.
from vxdg man page:
Import fails if the specified disk group name is either a reserved name (such as bootdg or nodg) or an existing disk group name. The disk group can be renamed on import using -n newname. If -n is used with the -t option, the stored name of the disk group remains unchanged, but the importing host knows the disk group under the new name; otherwise, the name change is permanent.
example/test:
12-02-2013 11:25 PM
Looks like you got it! Thanks, appreciate the help!