Hello All,

I got struck with steps to follow for using veritas on SANVC.
Here is the scenario :

currently we are using EMC Clarion disks and they are managed by veritas
4.0 vxfs and vxvm.
OS version -  Solaris 5.9
Powerpath is not installed.
Packages Installed related to veritas :

# pkginfo |grep -i vrts
application VRTSalloc                        VERITAS Volume Manager: VERITAS
Intelligent Storage Provisioning
application VRTSap                           VERITAS Action Provider
optional    VRTScpi                          VERITAS Cross Product
Installation Framework
application VRTSddlpr                        VERITAS Device Discovery Layer
Services Provider
application VRTSfppm                         VERITAS File Placement.
system      VRTSfsman                        VERITAS File System - Manual
Pages
application VRTSfspro                        VERITAS File System Management
Services Provider
application VRTSmuob                         VERITAS Enterprise
Administrator Service Localized Package
application VRTSob                           VERITAS Enterprise
Administrator Service
application VRTSobgui                        VERITAS Enterprise
Administrator
optional    VRTSperl                         Perl 5.8.0 for VERITAS
application VRTStep                          VERITAS Task Exec Provider
application VRTSvlic                         VERITAS License Utilities
system      VRTSvmman                        VERITAS Volume Manager, Manual
Pages
application VRTSvmpro                        VERITAS Volume Manager
Management Services Provider
system      VRTSvxfs                         VERITAS File System
system      VRTSvxvm                         VERITAS Volume Manager,
Binaries

# vxprint -g datadg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0
PUTIL0
dg datadg       datadg       -        -        -        -        -       -
dm datadg01     EMC_CLARiiON1_2 -     94364416 -        -        -       -
dm datadg02     EMC_CLARiiON1_1 -     8385792  -        -        -       -
dm datadg03     EMC_CLARiiON1_0 -     8385792  -        -        -       -
v  data_snapshot fsgen       ENABLED  8384512  -        ACTIVE   -       -
pl data_snapshot-01 data_snapshot ENABLED 8384512 -     ACTIVE   -       -
sd datadg03-01  data_snapshot-01 ENABLED 8384512 0      -        -       -
v  data_vol     fsgen        ENABLED  83886080 -        ACTIVE   -       -
pl data_vol-01  data_vol     ENABLED  83886080 -        ACTIVE   -       -
sd datadg01-01  data_vol-01  ENABLED  83886080 0        -        -       -
v  opt2_vol     fsgen        ENABLED  10477568 -        ACTIVE   -       -
pl opt2_vol-01  opt2_vol     ENABLED  10477568 -        ACTIVE   -       -
sd datadg01-02  opt2_vol-01  ENABLED  10477568 0        -        -       -
v  oracle_vol   fsgen        ENABLED  2097152  -        ACTIVE   -       -
pl oracle_vol-01 oracle_vol  ENABLED  2097152  -        ACTIVE   -       -
sd datadg02-01  oracle_vol-01 ENABLED 2097152  0        -        -       -


# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
EMC_CLARiiON1_0 auto:cdsdisk    datadg03     datadg       online
EMC_CLARiiON1_1 auto:cdsdisk    datadg02     datadg       online
EMC_CLARiiON1_2 auto:cdsdisk    datadg01     datadg       online
below is one of the disk details for datadg01

# vxdisk list datadg01
Device:    EMC_CLARiiON1_2
devicetag: EMC_CLARiiON1_2
type:      autos
hostid:    production_box1
disk:      name=datadg01 id=1094844012.13.production_box1
group:     name=datadg id=1094844087.33.production_box1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/EMC_CLARiiON1_2s2
char=/dev/vx/rdmp/EMC_CLARiiON1_2s2
version:   3.1
iosize:    min=512 (bytes) max=256 (blocks)
public:    slice=2 offset=2304 len=94364416 disk_offset=0
private:   slice=2 offset=256 len=2048 disk_offset=0
update:    time=1218950942 seqno=0.55
ssb:       actual_seqno=0.1
headers:   0 240
configs:   count=1 len=1280
logs:      count=1 len=192
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-001343[001088]: copy=01 offset=000192 enabled
 log      priv 001344-001535[000192]: copy=01 offset=000000 enabled
 lockrgn  priv 001536-001679[000144]: part=00 offset=000000
Multipathing information:
numpaths:   4
c5t22d0s2       state=enabled   type=primary
c5t23d0s2       state=enabled   type=secondary
c6t20d0s2       state=enabled   type=primary
c6t21d0s2       state=enabled   type=secondary

Now we are upgrading at storage level to SVC(SANVC). So what I see is only
the LUN id's will be changed and the rest of the disks data and disks remain
the same.

So I am not sure of the exact process of how to proceed further with this
change in LUN id's or any extra packages required as dependecies for using
the SVC(SANVC) .

Can someone help me in suggesting me run through the steps to be followed
for this activity without loosing the data and the setup, because its a
production box.

The old and new LUN id match will be provided by the storage team. Only
thing wanted to know is what all steps needs to be done to make the proper
lun id's assigned to the appropriate groups,volumes and plex's etc..

Request you to suggest me in brief.. and your help is appreciated.

-- 
Thanks in Advance,
Bharat Yadav
"You know what keeps me going???
Whenever I get all the answers of life, he changes the questions !!!....."
_______________________________________________
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to