Servicios

Web hosting
Ver »
Páginas Web
Ver »
Soporte UNIX
Ver »
UNIX TIPS
Ver »

CREAR (BCVs)

DISCOS Y GRUPO PREVIAMENTE ASIGNADOS.

1. VERIFICAR EL ESTADO DE LOS DISPOSITIVOS COLUMNA State DEBE ESTAR EN Split

root@mxg5db02 # symmir -g g5db02 query
Device Group (DG) Name: g5db02
DG's Type : REGULAR
DG's Symmetrix ID : 000190100385

Standard Device BCV Device State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------

DEV001 006A 0 BCV001 0C37 * 0 Split
DEV002 008E 0 BCV002 0C3B * 0 Split
DEV003 0718 0 BCV003 0C3F * 0 Split
DEV004 1116 0 BCV004 13D0 * 0 Split
Total ------- -------
Track(s) 0 0
MB(s) 0.0 0.0

Legend:

(*): The paired BCV device is associated with this group.
root@ #


2. DESMONTAR LOS FILESYSTEMS PERTENECIENTE AL DISKGROUP A REALIZAR EL BCV

root@ # df -h | grep g5mx_dg
/dev/vx/dsk/g5mx_dg/resp_tmp 10G 6.5G 3.3G 66% /resp_tmp
/dev/vx/dsk/g5mx_dg/rmanmx 15G 12G 2.4G 84% /RMANMX
/dev/vx/dsk/g5mx_dg/g5mxcs 12G 9.8G 2.1G 83% /g5mxcs
/dev/vx/dsk/g5mx_dg/g5mx_adm 32G 6.2G 24G 21% /g5mx_adm
/dev/vx/dsk/g5mx_dg/g5mxtx 62G 49G 13G 80% /g5mxtx
/dev/vx/dsk/g5mx_dg/oas_cluster 2.0G 809M 1.1G 42% /oas_cluster

root@ # umount /resp_tmp
root@ # umount /RMANMX
root@ # umount /g5mxcs
root@ # umount /g5mx_adm
root@ # umount /g5mxtx
root@ # umount /oas_cluster
root@ #


3. DEPORTAR EL DISKGROUP

root@ # vxdg deport g5mx_dg
VERIFICA EL STATUS DEL DISKGROUP
root@ # vxdisk -o alldgs list | grep g5mx_dg
emcpower0s2 auto:cdsdisk - (g5mx_dg) online
emcpower1s2 auto:cdsdisk - (g5mx_dg) online
emcpower2s2 auto:cdsdisk - (g5mx_dg) online
emcpower4s2 auto:cdsdisk - (g5mx_dg) online
root@ #


4. REALIZAR ESTABLISH

root@ # ./establish
Contenido del script establish: /opt/emc/SYMCLI/V6.4.3/bin/symmir -g g5db02 -full establish

VERIFICAR AVANCE DE LA SINCRONIZACION COLUMNA State.

root@ # symmir -g g5db02 query
Device Group (DG) Name: g5db02
DG's Type : REGULAR
DG's Symmetrix ID : 000190100385
Standard Device          BCV Device                 State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------
DEV001 006A 0 BCV001 0C37 * 944430 SyncInProg
DEV002 008E 0 BCV002 0C3B * 949654 SyncInProg
DEV003 0718 0 BCV003 0C3F * 971236 SyncInProg
DEV004 1116 0 BCV004 13D0 * 1021550 SyncInProg
Total ------- -------
Track(s) 0 3886870
MB(s) 0 121465
Legend:
(*): The paired BCV device is associated with this group.
root@ #

VERIFICAR TERMINO DE LA SINCRONIZACION DE LOS DISPOSITIVOS HAYAN TERMINADO SIN PROBLEMAS

root@ # symmir -g g5db02 query
Device Group (DG) Name: g5db02
DG's Type : REGULAR
DG's Symmetrix ID : 000190100385
Standard Device BCV Device State
-------------------------- ------------------------------------- ------------
Inv. Inv.
Logical Sym Tracks Logical Sym Tracks STD <=> BCV
-------------------------- ------------------------------------- ------------
DEV001 006A 0 BCV001 0C37 * 0 Synchronized
DEV002 008E 0 BCV002 0C3B * 0 Synchronized
DEV003 0718 0 BCV003 0C3F * 0 Synchronized
DEV004 1116 0 BCV004 13D0 * 0 Synchronized
Total ------- -------
Track(s) 0 0
MB(s) 0.0 0.0
Legend:
(*): The paired BCV device is associated with this group.
root@ #

AL TERMINO DE LA SINCRONIZACION CAMBIAR EL MODO DE LA BDD DE NORMAL A BEGIN BACKUP CONFIRMAR CON DATABASE ADMINISTRATOR


5. EJECUTAR SPLIT
root@ # ./split

Contenido del script split: /opt/emc/SYMCLI/V6.4.3/bin/symmir -g g5db02 -instant split

VERIFICAR STATUS DEL SPLIT HAYA TERMINADO COLUMNA State DEBE MOSTRAR como Split

AL TERMINO DEL SPLIT CAMBIAR EL MODO DE LA BDD A NORMAL CONFIRMAR CON EL DATABASE ADMINISTRATOR

VERIFICAR STATUS DEL DISKGROUP

root@ # vxdisk -o alldgs list | grep g5mx_dg
DEVICE TYPE DISK GROUP STATUS
emcpower0s2 auto:cdsdisk - (g5mx_dg) online
emcpower1s2 auto:cdsdisk - (g5mx_dg) online
emcpower2s2 auto:cdsdisk - (g5mx_dg) online
emcpower4s2 auto:cdsdisk - (g5mx_dg) online
root@ #


6. PARA REINICIAR EL DISKGROUP, IMPORTAR EL DISKGROUP, FSCK Y MONTAR SUS FILESYSTEMS

root@ # vxdctl enable
root@ # vxdg import g5mx_dg

En caso de que falle el import y se este seguro de que no este importado el diskgroup en otro Server usar la opcion de Clear Host ID: root@ # vxdg -C import g5mx_dg

root@mxg5db02 # vxdisk -o alldgs list | grep g5mx_dg
emcpower0s2 auto:cdsdisk g5mx_dg03 g5mx_dg online
emcpower1s2 auto:cdsdisk g5mx_dg01 g5mx_dg online nohotuse
emcpower2s2 auto:cdsdisk g5mx_dg02 g5mx_dg online
emcpower4s2 auto:cdsdisk g5mx_dg04 g5mx_dg online
root@ #

root@ # fsck -y /dev/vx/rdsk/g5mx_dg/resp_tmp
root@ # fsck -y /dev/vx/rdsk/g5mx_dg/rmanmx
root@ # fsck -y /dev/vx/rdsk/g5mx_dg/g5mxcs
root@ # fsck -y /dev/vx/rdsk/g5mx_dg/g5mx_adm
root@ # fsck -y /dev/vx/rdsk/g5mx_dg/g5mxtx
root@ # fsck -y /dev/vx/rdsk/g5mx_dg/oas_cluster

root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/resp_tmp /resp_tmp
root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/rmanmx /RMANMX
root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/g5mxcs /g5mxcs
root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/g5mx_adm /g5mx_adm
root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/g5mxtx /g5mxtx
root@ # mount -F vxfs /dev/vx/dsk/g5mx_dg/oas_cluster /oas_cluster

Listo! Ha quedado terminado nuestro BCVs.


Referencia de comandos para investigar como asignar dispositivos al grupo de BCV creado.

root@ # strings bcvs

#Para crear el grupo
symdg -type REGULAR create g5db02

#Para agregar los devices standard al grupo
symld -sid 0385 -g g5db02 add dev 006A
symld -sid 0385 -g g5db02 add dev 008E
symld -sid 0385 -g g5db02 add dev 0718
symld -sid 0385 -g g5db02 add dev 1116

#Para asociar los discos BCVs
symbcv -sid 0385 -g g5db02 associate dev 0C37
symbcv -sid 0385 -g g5db02 associate dev 0C3B
symbcv -sid 0385 -g g5db02 associate dev 0C3F
symbcv -sid 0385 -g g5db02 associate dev 13D0

#Para visualizar
symld -g g5db02 list

#Para ver el estado de los BCVs
symmir -g g5db02 query -i 5 -c 10
root@ #

Regresar

Random TIPS

Removing "Drive Not Available" from Solaris

These are steps I followed to remove the LUNS which were unmasked from the system.
Removing the Unused/Unmasked LUNS from Solaris.

1. First Step is identifying the from Format o/p.
2. Remove them from Volume Manager. In my case, they are veritas. so I used vxdisk rm
3. look at the cfgadm -al o/p to find the disks which are failing. they are failing because they are unmasked from this system and still OS sees them.
c3::50060482d53135b8,84 disk connected configured failing
c3::50060482d53135b8,86 disk connected configured failing
c3::50060482d53135b8,87 disk connected configured failing
3. luxadm -e offline /dev/rdsk/ # This will kick the device from failing to unusable. and also removes them from format o/p.
4. cfgadm -o unusable_FCP_dev -c unconfigure c3::50060482d53135b8
# This will remove all unusable LUNS from system for particular controller and target id. don't worry there might be some working devices on that target. This command won't affect them. they'll be in working state only.
5. clean the device files using devfsadm -Cv
6. You should be clear now in both format and cfgadm -al.

free counters