![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all, I have SQL 2005 Ent SP3 clustered running on Windows 2003 Ent SP2 attached to SCSI HP DAS MSA500. I would like to migrate these servers to the HP EVA SAN. I have already installed HBO's and they are attached to the HP EVA SAN. The drives on SCSI HP DAS MSA500 are much larger than the HP EVA SAN. Can someone share the knowledge on the best practise how to do the migration. I tested the HP Storage Mirroring offline solution and it worked well but I would prefer to do the online migration. Can someone recommend the application which would be able to do the online migration bearing in mind the disk size differences between the source and the destination? Many thanks, Pluto |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hi Manpreet, thanks for your help. The destination disk sizes are already set and I can not change them. The problem is that the current disk sizes are humongous (100GB for Q:...this does not make any sense...big time overkill). The limitations and facts: - source disk sizes are greater than destination disk sizes - the databse must be online during the migration - DAS to SAN Any hints or tips are appreciated. Pluto |
#5
| |||
| |||
|
|
Modify original database to use file groups. Copy different table to new file group by creating cluster index again . Place different file group on different MDF, and NDF data files. Shrink original data file using DBCC shrink file command to reduce size. Ones done, now you have a database with multiple data files Now using above given way copy the database and place different data files on different partitions on target sever. Hopefully, this will solve your problem. Manpreet Singh http://crazysql.wordpress.com/ MCITP –DBA, DD - SQL server 2005 MCTS – SQL server 2005 MCTS –SharePoint Server 2007 "Pluto" wrote: Hi Manpreet, thanks for your help. The destination disk sizes are already set and I can not change them. The problem is that the current disk sizes are humongous (100GB for Q:...this does not make any sense...big time overkill). The limitations and facts: - source disk sizes are greater than destination disk sizes - the databse must be online during the migration - DAS to SAN Any hints or tips are appreciated. Pluto |
#6
| |||
| |||
|
|
Hi Manpreet, the source disks are having minimal amount of data. It is just that the drives are greater than the destination ones. q:\ 100GB in size but only 500MB of the real data new q:\ 10GB in size but only 500MB of the real data s:\ 500GB in size but only 20GB of the real data new s:\ 100GB in size but only 20GB of the real data Thanks again, Pluto "Manpreet Singh" wrote: Modify original database to use file groups. Copy different table to new file group by creating cluster index again . Place different file group on different MDF, and NDF data files. Shrink original data file using DBCC shrink file command to reduce size. Ones done, now you have a database with multiple data files Now using above given way copy the database and place different data files on different partitions on target sever. Hopefully, this will solve your problem. Manpreet Singh http://crazysql.wordpress.com/ MCITP –DBA, DD - SQL server 2005 MCTS – SQL server 2005 MCTS –SharePoint Server 2007 "Pluto" wrote: Hi Manpreet, thanks for your help. The destination disk sizes are already set and I can not change them. The problem is that the current disk sizes are humongous (100GB for Q:...this does not make any sense...big time overkill). The limitations and facts: - source disk sizes are greater than destination disk sizes - the databse must be online during the migration - DAS to SAN Any hints or tips are appreciated. Pluto |
#7
| |||
| |||
|
|
Then what exactly is the problem? The copy database wizard will give you a change to place database file on any location (SAN, DAS, any location attached to server). And again it won’t cause any problem, If the disk has more space (destination wont comes into picture here, as long as u have more size then data file actually needed) than needed by database file. But please note for this, u need to have both SAN and DAS online. And accessed by server though any drive latter. The other option is use log shipping. All you need to do is to create a new resource in cluster as file share. But this involve a little downtime (to copy tail of log) Manpreet Singh http://crazysql.wordpress.com/ MCITP –DBA, DD - SQL server 2005 MCTS – SQL server 2005 MCTS –SharePoint Server 2007 "Pluto" wrote: Hi Manpreet, the source disks are having minimal amount of data. It is just that the drives are greater than the destination ones. q:\ 100GB in size but only 500MB of the real data new q:\ 10GB in size but only 500MB of the real data s:\ 500GB in size but only 20GB of the real data new s:\ 100GB in size but only 20GB of the real data Thanks again, Pluto "Manpreet Singh" wrote: Modify original database to use file groups. Copy different table to new file group by creating cluster index again . Place different file group on different MDF, and NDF data files. Shrink original data file using DBCC shrink file command to reduce size. Ones done, now you have a database with multiple data files Now using above given way copy the database and place different data files on different partitions on target sever. Hopefully, this will solve your problem. Manpreet Singh http://crazysql.wordpress.com/ MCITP –DBA, DD - SQL server 2005 MCTS – SQL server 2005 MCTS –SharePoint Server 2007 "Pluto" wrote: Hi Manpreet, thanks for your help. The destination disk sizes are already set and I can not change them. The problem is that the current disk sizes are humongous (100GB for Q:...this does not make any sense...big time overkill). The limitations and facts: - source disk sizes are greater than destination disk sizes - the databse must be online during the migration - DAS to SAN Any hints or tips are appreciated. Pluto |
![]() |
| Thread Tools | |
| Display Modes | |
| |