0

I’m a SQL DBA and my SAN admin said that they have to migrate few drives from HP 3PAR 7400 to EMC CX4. So SAN team wants to have a downtime on sql servers to migrate the drives.

What was am thinks was, is their any possibility to migrate the storage without bringing down the sql?

i.e I have D drive with 100GB of 3PAR is it possible to add EMC CX4 (100GB) to D drive and make it 200GB. later remove 100GB of 3PAR from D drive.

Please let me know is this possible?

Jagan Sekaran
  • 78
  • 2
  • 7
  • You have to move the data anyway. Just adding the SAN as a new drive or eg as a folder in the existing drive won't move the data to the new SAN – Panagiotis Kanavos May 31 '17 at 16:36
  • Vote to move this to [serverfault](http://serverfault.com/) – yorodm May 31 '17 at 16:38
  • @yorodm dba.stackexchange.com is a better fit – Panagiotis Kanavos May 31 '17 at 16:38
  • I'm just wondering if is it possible to expand the **D** drive to 200GB by combining _100Gb of 3PAR + 100GB of EMC CX4_ – Jagan Sekaran May 31 '17 at 16:47
  • Even if it is possible, what happens when the old NAS goes offline? Striping the two drives together may lead to a situation when half of the file is stored on NAS1 and the other part on NAS2. Just bring that server down in a maintenance window and transfer the data. And triple-check if you have a working backup before you do anything. – Pred May 31 '17 at 16:50
  • @Pred is combining two different storages are possible? in my case am thinking after combining the two drive I will be removing the 3PAR from the D drive and make it 100GB of EMC – Jagan Sekaran May 31 '17 at 17:00
  • No idea if it is possible. What I know is that this is a bad idea. – Pred May 31 '17 at 17:05
  • Alright I have to go with the SAN team's plan – Jagan Sekaran May 31 '17 at 19:19

3 Answers3

1

You need switchover to standby. If you don't have standbay server you need to create.

Your question is not correct. But I give you two answer (it is concept answers) 1. Teoretic yes it is possible. You need have a EMC powerpath and storage support. But if choose that way. You need to control segments for migration in other words it is IT risk:

Time for migration - in Global how much you have a time for migration to another storage.

I/O for disk - if you will be have a big I/O on the disk. Your service not will be available. and other moments....

  1. Practice. Yes need downtime.
noute
  • 114
  • 3
  • 13
0

What was am thinks was, is their any possibility to migrate the storage without bringing down the sql?

I will rephrase this question thus:

Is their any possibility to migrate ONLINE tables (clustered / heap) to another filegroup (=another files) ?

The answer is yes and it's very simple with Enterprise Edition. For example, assuming that current filegroup is CustomUserObjects (D:\MSSQL\Data\DataFile.mdf) and we have to move these tables to another filegroup NewCustomUserObjects (G:\MSSQL\Data\DataFile.mdf) then

[1] For clustered & nonclustered indexes could be used following approach:

CREATE UNIQUE CLUSTERED INDEX PK_TestTable_ID ON 
dbo.TestTable(ID)
WITH
(
    ONLINE = ON,
    DROP_EXISTING = ON
)
ON NewCustomFileGroup
GO

The same approach could be used also for NONLCLUSTERED indexes.

[2] For heap tables, one clustered index could be created (CREATE ... INDEX ... ONLINE = ON) followed by a DROP INDEX ... ON .....

More details here.

This approach has few limitations. The most important are:

[1] Some indexes (ex. spatial & xml indexes) could not be moved ONLINE.

[2] It will leave BLOBs ([n]varchar(max), varbinary(max), xml, etc.) values stored within old filegroup but there are some solutions.

[3] For FULL / BULK LOGGED databases, it will generate a lot of entries within database transaction log (ex. *.ldf) thereby affecting all functionalities based on Tx log: log shipping, database mirroring, AO Availability Groups, transaction replication, Change Data Capture, etc.

Bogdan Sahlean
  • 19,233
  • 3
  • 42
  • 57
0

If you are using PowerPath as multipathing software, you can have no downtime migration from array to array using PowerPath Migration Enabler.

It establishes a replication pair, source (3par) and a target (cx4) volume. It does a bulk sync of the device on block level and replicates writes to the target volumes. After you decide to commit the change, it renames Powerpath pseudonames so your server is using the target volume as primary. Done!

docs: https://www.emc.com/collateral/TechnicalDocument/PowerPath-Migration-Enabler-5.7-User-Guide.pdf

squeaky_godzilla
  • 11
  • 1