We are trying to move some databases from a set of old servers to a new 
servers and they are pretty large.. like around 100 databases and around 
10-15 TB.

They are all SAN connected and I believe SAN based replication from one SAN 
volume to a new SAN volume connected to the other server might be faster.. 
but I don't think SAN based replication works at a file level..

As an example, I may have 4 databases on one server and 2 of these databases 
may move to NewServer1 and the other 2 to NewServer2... Backup and restore 
may take forever.. Any other way to speed up these moves creatively.

Thanks 

> They are all SAN connected and I believe SAN based replication from one 
> SAN volume to a new SAN volume connected to the other server might be 
> faster.. but I don't think SAN based replication works at a file level..

You may very well be able to leverage your SAN to move or replicate data at 
a low-level storage level to facilitate moving databases to new hosts.  The 
specifics depend on your SAN hardware, features and configuration.  Ask your 
storage admins about what they can do to help you out.

-- 
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

 

On Sat, 14 Aug 2010 12:10:55 -0700, "Raj" <raj@hotmail.com> wrote:

>We are trying to move some databases from a set of old servers to a new 
>servers and they are pretty large.. like around 100 databases and around 
>10-15 TB.
>
>They are all SAN connected and I believe SAN based replication from one SAN 
>volume to a new SAN volume connected to the other server might be faster.. 
>but I don't think SAN based replication works at a file level..
>
>As an example, I may have 4 databases on one server and 2 of these databases 
>may move to NewServer1 and the other 2 to NewServer2... Backup and restore 
>may take forever.. Any other way to speed up these moves creatively.
>
>Thanks 


Hi

SAN based replication is usually used for DR scenarios. You may want
to talk to the SAN guys top see if you can take snapshots. That would
require you using the same SAN, in which case eoe option would be to
fail over to one of the new servers, in that case you will only need
to move fewer databases.

You could also look at SQL replication, mirroring or log shipping, the
overall the process could take significantly longer, but the time
required to switch over would be less.

Another limiting factor could be how much SAN that can be used during
migration.

John

We just want to move databases to new servers .. and wanted to do it quick.. 
Like I said they are in the Terabytes.. and wanted to minimize downtime and 
also to reduce any temp space by taking backups,etc.. That would call for 
some additional temporary storage to store all these backup files,etc..



"John Bell" <jbellnewsposts@hotmail.com> wrote in message 
news:ecsd66lid7nd0pqgne2hnijs95pv0jvj8f@4ax.com...
> On Sat, 14 Aug 2010 12:10:55 -0700, "Raj" <raj@hotmail.com> wrote:
>
>>We are trying to move some databases from a set of old servers to a new
>>servers and they are pretty large.. like around 100 databases and around
>>10-15 TB.
>>
>>They are all SAN connected and I believe SAN based replication from one 
>>SAN
>>volume to a new SAN volume connected to the other server might be faster..
>>but I don't think SAN based replication works at a file level..
>>
>>As an example, I may have 4 databases on one server and 2 of these 
>>databases
>>may move to NewServer1 and the other 2 to NewServer2... Backup and restore
>>may take forever.. Any other way to speed up these moves creatively.
>>
>>Thanks
>
>
> Hi
>
> SAN based replication is usually used for DR scenarios. You may want
> to talk to the SAN guys top see if you can take snapshots. That would
> require you using the same SAN, in which case eoe option would be to
> fail over to one of the new servers, in that case you will only need
> to move fewer databases.
>
> You could also look at SQL replication, mirroring or log shipping, the
> overall the process could take significantly longer, but the time
> required to switch over would be less.
>
> Another limiting factor could be how much SAN that can be used during
> migration.
>
> John 

On Sat, 14 Aug 2010 18:48:36 -0700, "Raj" <raj@hotmail.com> wrote:

>We just want to move databases to new servers .. and wanted to do it quick.. 
>Like I said they are in the Terabytes.. and wanted to minimize downtime and 
>also to reduce any temp space by taking backups,etc.. That would call for 
>some additional temporary storage to store all these backup files,etc..
>
>
>
>"John Bell" <jbellnewsposts@hotmail.com> wrote in message 
>news:ecsd66lid7nd0pqgne2hnijs95pv0jvj8f@4ax.com...
>> On Sat, 14 Aug 2010 12:10:55 -0700, "Raj" <raj@hotmail.com> wrote:
>>
>>>We are trying to move some databases from a set of old servers to a new
>>>servers and they are pretty large.. like around 100 databases and around
>>>10-15 TB.
>>>
>>>They are all SAN connected and I believe SAN based replication from one 
>>>SAN
>>>volume to a new SAN volume connected to the other server might be faster..
>>>but I don't think SAN based replication works at a file level..
>>>
>>>As an example, I may have 4 databases on one server and 2 of these 
>>>databases
>>>may move to NewServer1 and the other 2 to NewServer2... Backup and restore
>>>may take forever.. Any other way to speed up these moves creatively.
>>>
>>>Thanks
>>
>>
>> Hi
>>
>> SAN based replication is usually used for DR scenarios. You may want
>> to talk to the SAN guys top see if you can take snapshots. That would
>> require you using the same SAN, in which case eoe option would be to
>> fail over to one of the new servers, in that case you will only need
>> to move fewer databases.
>>
>> You could also look at SQL replication, mirroring or log shipping, the
>> overall the process could take significantly longer, but the time
>> required to switch over would be less.
>>
>> Another limiting factor could be how much SAN that can be used during
>> migration.
>>
>> John 


If you are doing regular backups then you could utilise them, it would
depend on where the backups were stored as to whether you had to copy
them or not. 

Overall it seems that are expectinig us to come up with a solution
without having enough information or discussing it with anyone in your
infrastructure team.

John