|
Home > Archive > Data Storage > June 2004 > migrating sap data from symmetrix to dmx
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
migrating sap data from symmetrix to dmx
|
|
|
| Hi all,
Doe's anybody have had any experience with migrating data from EMC
symmetrix to DMX arrays ?
We use Solaris 8 (Kernel -27) with vxvm/vxfs 3.2
I'd be grateful to anybody who accept to show me one or more scenarios
to do that.
Thanks in advance.
JF
| |
| Richard Rhodes 2004-06-11, 5:52 pm |
| jfariat@hotmail.com (JF) wrote in
news:84e37626.0406110742.6c41f83f@posting.google.com:
> Hi all,
>
>
> Doe's anybody have had any experience with migrating data from EMC
> symmetrix to DMX arrays ?
> We use Solaris 8 (Kernel -27) with vxvm/vxfs 3.2
> I'd be grateful to anybody who accept to show me one or more scenarios
> to do that.
>
Some thoughts:
1) Let EMC move it.
If you can take an outage, EMC will hook up connections between
the Symm and DMX, copy the hyper vols to the DMX, setup the fa ports,
move your host cables to the DMX, boot your box and you're migrated.
You will probably have to do some zoning.
2) VXVM migration
- Hook the DMX up to your san.
- Zone it to your SUn box.
- Allocate hypers/meta's
- Assign hypers/metas to fa port
- lun mast to your sun box
- bring luns into the sun box as drives
- add them to your existing disk groups
- mirror volumes onto new luns
- break mirror - leaving good copy on new drives
- remove old luns from disk group
- delete drives from sun box
- unzone from symm
- remove old zymm
On a hpux or aix system this can all be done live. I
don't know about Sun systems.
Rick
| |
| dave dickerson 2004-06-26, 2:26 pm |
| Richard Rhodes wrote:
> jfariat@hotmail.com (JF) wrote in
> news:84e37626.0406110742.6c41f83f@posting.google.com:
>
>
>
>
> Some thoughts:
>
> 1) Let EMC move it.
>
> If you can take an outage, EMC will hook up connections between
> the Symm and DMX, copy the hyper vols to the DMX, setup the fa ports,
> move your host cables to the DMX, boot your box and you're migrated.
> You will probably have to do some zoning.
You didn't say how old your Symm is. It's my understanding that you
need a relatively new ( perhaps Symm 5.5? ) Symmetrix to have it talk to
DMX using SRDF. You may also need to upgrade firmware on the Symm to
get it to a current-enough version to interoperate with the newer DMX code.
>
> 2) VXVM migration
>
> - Hook the DMX up to your san.
> - Zone it to your SUn box.
> - Allocate hypers/meta's
> - Assign hypers/metas to fa port
> - lun mast to your sun box
> - bring luns into the sun box as drives
> - add them to your existing disk groups
> - mirror volumes onto new luns
> - break mirror - leaving good copy on new drives
> - remove old luns from disk group
> - delete drives from sun box
> - unzone from symm
> - remove old zymm
>
> On a hpux or aix system this can all be done live. I
> don't know about Sun systems.
>
>
> Rick
Similarly, with VXVM migration - rather than creating mirrors, you could
just add disks from the DMX and use the subdisk move capability to move
the blocks from Sym to DMX.
For Solaris, depending on your HBA driver and sd.conf configuration, you
will probably need to reboot to discover the new LUNs exposed from the
DMX. All other steps can be done live.
| |
| Cameron Parry 2004-06-26, 2:26 pm |
| dave dickerson <cdd@daveSPAMdickerson.com.remove> wrote in message news:<10cp8i7ngu8555a@corp.supernews.com>...
> Richard Rhodes wrote:
HI[vbcol=seagreen]
>
> You didn't say how old your Symm is. It's my understanding that you
> need a relatively new ( perhaps Symm 5.5? ) Symmetrix to have it talk to
> DMX using SRDF. You may also need to upgrade firmware on the Symm to
> get it to a current-enough version to interoperate with the newer DMX code.
>
>
> Similarly, with VXVM migration - rather than creating mirrors, you could
> just add disks from the DMX and use the subdisk move capability to move
> the blocks from Sym to DMX.
>
> For Solaris, depending on your HBA driver and sd.conf configuration, you
> will probably need to reboot to discover the new LUNs exposed from the
> DMX. All other steps can be done live.
Hi,
I have done a simliar migration by copying the data vis a 'dd'
command. The proviso is that the LUN sizes are the same, and you will
need the down time on the application to perform this migration. It
was very quick way to perform the migration, much quicker than host
nased mirroring.
Cheers
Cameron
| |
|
| Thanks Rick, Thanks dave,
Firmwares on the Symmetrix 8730 & 8830 are ok and connexion of arrays
were done by EMC. And every thing is ok about zoning, mapping &
masking process...
Because we backup(Netbackup 3.40)data using BCV implementation, What
about the peers STD-BCV in both arrays during migration ?
Supposing we use VXVM mirroring to migrate data, how to avoid any
confusion between BCVs for netbackup ?
Thanks in advance.
dave dickerson <cdd@daveSPAMdickerson.com.remove> wrote in message news:<10cp8i7ngu8555a@corp.supernews.com>...
> Richard Rhodes wrote:
>
> You didn't say how old your Symm is. It's my understanding that you
> need a relatively new ( perhaps Symm 5.5? ) Symmetrix to have it talk to
> DMX using SRDF. You may also need to upgrade firmware on the Symm to
> get it to a current-enough version to interoperate with the newer DMX code.
>
>
> Similarly, with VXVM migration - rather than creating mirrors, you could
> just add disks from the DMX and use the subdisk move capability to move
> the blocks from Sym to DMX.
>
> For Solaris, depending on your HBA driver and sd.conf configuration, you
> will probably need to reboot to discover the new LUNs exposed from the
> DMX. All other steps can be done live.
| |
|
| Thanks Cameron for your response.
Let me tell you what kind of configuration we must migrate and
migration steps:
Actually we have:
-----------------
SCluster 3.0
Sym 8830 HLM Sym 8830
STD <----> STD + BCV1 + BCV2
During Migration:
-----------------
SCluster 3.0
Sym 8830 HLM Sym 8830
STD <----> STD + BCV1 + BCV2
|HLM
DMX 3000 HLM DMX3000
STD <----> STD + BCV1 + BCV2
After migration:
----------------
SCluster 3.0
DMX 3000 HLM DMX3000
STD <----> STD + BCV1 + BCV2
----------------------------------------
BCV1 is for netbackup
BCV2 is for DBVerify
During migration, the 4 arrays will be connected at the same time. So
every LUN will be 4 mirrors.
To prevent any lost of data, we decide to keep temporaly this
configuration (for one week) untill to be sur that every thing is ok
and than we remove the old Sym...
Therefore, Backup of data is done every night and should not be
suspended during this week.
So I dont know the behavior of netbackup trying to synchronize BCV1
and do an import dg (vm dg) ... !
May somebody tell me please ?
Thanks everybody.
jfariat@hotmail.com (JF) wrote in message news:<84e37626.0406140230.3db3e316@posting.google.com>...[vbcol=seagreen]
> Thanks Rick, Thanks dave,
> Firmwares on the Symmetrix 8730 & 8830 are ok and connexion of arrays
> were done by EMC. And every thing is ok about zoning, mapping &
> masking process...
>
> Because we backup(Netbackup 3.40)data using BCV implementation, What
> about the peers STD-BCV in both arrays during migration ?
> Supposing we use VXVM mirroring to migrate data, how to avoid any
> confusion between BCVs for netbackup ?
>
> Thanks in advance.
>
> dave dickerson <cdd@daveSPAMdickerson.com.remove> wrote in message news:<10cp8i7ngu8555a@corp.supernews.com>...
|
|
|
|
|