Unsolved
This post is more than 5 years old
23 Posts
0
776
April 24th, 2013 01:00
How to replace a hyper of a 2-way-mirror device?
DMX2000 running 5771, to be decommissioned soon and out of support. Most data already migrated to VMAX.
However, some data is still in production on this DMX, all hotspares are already in use and a couple of spindles have failed, leaving some 2-way-mirror devices and metas in a degraded service state. Other than migrating the data off the DMX what other temporary options are there? Is it possible to pick another unused device (same geometry and DG, there are hundreds of them), destroy it and use the free hypers to replace the faulty ones? Of course without a BIN-reload and while preserving the data on the remaining hyper. Or is there some known way to move the entire LUN to a different spindle set (TimeFinder not availlable)?
Thanks!
Fenglin1
4 Operator
•
2.1K Posts
0
April 24th, 2013 02:00
I think you may consider host side replication to move your date to a new lun either new created or existing. then might need application down time.
From Symm side , the only two way you can do are replacing the failure disk( order EMC service) or do the BIN changes to add new spare then ask your customer engineer to invoke the spare.
rmueller2
23 Posts
0
April 24th, 2013 05:00
A host downtime would be ok. I can't migrate the boot drive (w2k3) with PPME - at least they say this is not supported.
Replacing the spindles is too costly and changing the BIN would also incur charges for the CE.
dynamox
9 Legend
•
20.4K Posts
0
April 24th, 2013 08:00
the boot drive could probably be cloned with tools like Acronis or similar
Rasmmacias
108 Posts
0
April 25th, 2013 01:00
Open Replicator can be used to copy data from a Symmetrix DMX array to VMAX.
Table 1 Control and remote device guidelines (page 1 of 2)
Action
Creating the device file
Control device
Symmetrix DMX or VMAX
Always listed on left Format:symdev=arrayid:device Example:symdev=7098:E9
Remote device
Symmetrix, CLARiiON,third-party array Always listed on right
Format: symdev |clardev=array:device or wwn=WWN
Example: wwn=6006048000000000314353594D303737
Refer to “Creatinga device file” on page 27 for device format rules
Action
Hot push
Control device
One device per session All directors must see remote Device
Remote device
One device per session
Device not accessible to host
Can use -consistent,-nodifferential, and -precopy
Note: Differential copying is the default for copy sessions and does not need to be specified in the symrcopy create command.
Action
Cold push
Control device
One device per session Device Not Ready to host At least one director must see remote device(s)
Remote device
Can use -nodifferential
Note: Differential copying is the default for copy
sessions and does not need to be specified in the symrcopy create command.
Table 1 Control and remote device guidelines (page 2 of 2)
Action
Hot pull
Control device
One device per session
Device online to the host All directors must see the remote device
Remote device
One device per active session
Can use -donor_update
Can use -frontend_zero(-off)
Action
Cold pull
Control device
One device per session At least one director must see the remote device
Remote device
One device per session
Can use -frontend_zero(-off)