Hello Craig,

got SanCopy on production array ? Could use that to copy data between arrays.

One options will be a clone of your secondary image and than sancopy to the CX500 .

Pierluca Chiodelli

Corporate System Eng.

Phone 508-382-6104

Mobile 508-561-4403

Just to add more detail, the DEV SAN has enough space to hold a second copy of the Data, but the Prod / DR SANs are fully loaded.

SAN copy sounds interesting, we're not currently licensed for it though, so this would be an additional cost - no that big an issue if it makes admin easier.

Can anyone offer any other options?  We'd prefer to use existing technologies if possible...

Thanks for all your input!

Have you considered not using consistency groups and by using host-based tools to pause the source LUNs when you need to fracture the mirrors to keep the images consistent?

glen

SANCopy is easy to setup and run. You can create scripts so that once a quarter you just dismount the dev LUNs, run the synch, and then mount the dev LUNs up again. Since both arrays are CLARiIONS and in the same fabric this will be the easiest method to use if the extrac cost of the license is not an issue.

No, you just need to license it on one of the arrays. I would license it on your production array, it will give you more flexibility in the future for you production array.

What kind of performance impact would the SANcopy have on the production Data?  What scripting can be done to control what, when and how data is copied?

Thanks for your info,

cswaters1

would I need to license SANcopy on both the Prod and Dev Arrays?

Thanks,

cswaters1

Replication manager also adds more complexity and requirements since you have to create an application set that is tied to a specific host configured for a specific file system or application to replicate, and the hosts all need to have all the correct software installed for the version of RM installed. I use RM a lot for replications that require it, but for the occasional SANcopy I just use basic scripts and it is much simpler to setup and manaage natively than using RM.

i don't remember seeing numbers but SanCopy will steal IOPS from your production drives, although you have options

1) control SanCopy speed but using priority ..10 is full blast, 1 is the slowest

2) perform copy at specific time, say you want to SanCopy your production LUNs the way they looked at 6pm. You mark your production LUNs at 6pm but start the actual transfer at 10pm to cause as little performance impact on production as possible.

it could be a strategy that combines both options.

SanCopy can be controlled via naviseccli so any scripts that can issue those commands will work (perl,vbscript, bash). I believe Replication Manager can do the same thing with a lot more bells and whistles but you have to purchase it.