Migrate 4 TB database to new environment

Question

Migrate 4 TB database to new environment

PJ_SQL

SSCertifiable

Points: 6699
More actions
April 2, 2019 at 1:36 am

#2446200

Hello!
We are migrating Sql database from 2012 to 2016 version.
Database is 4 TB so backup and restore of database to new environment is not applicable as it would cause huge downtown.
What would be the good alternative for this?
Thanks.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

andreas.kreuzberg SSCertifiable Points: 6183 More actions · Answer 1

Hi,

you can use logshipping to get a current database on the new sql server. If everything is synchron, you can stop logshiping and set the database on the new sql server online.

Kind regards,

Andreas

PJ_SQL SSCertifiable Points: 6699 More actions · Answer 2

Thank you Andreas.

So,different version of SQL Server would not hinder log-shipping from 2012 to 2016?

Also, could you also mention the steps to bring the secondary Database online?

Thank you.

This reply was modified 5 years ago by PJ_SQL.

Alejandro Santana SSCommitted Points: 1835 More actions · Answer 3

When we migrated from SQL Server 2008 R2 to 2016, one of our largest database had 8TB size, but in our case we had a window, we prepared everything and this is how we did it:

All of our database files are in LUNS in the SAN.

when we migrated we had a small window, we told to the Storage Department to dettach these drives and put them in the new server with 2016 installed and configured, we only had to detach the database from old server, remove the drive from the old server to the new one and attach the database, the only process SQL Server did was change the database version from 655 to 852.

We recreated all the users with Microsoft's SQL Script

https://support.microsoft.com/en-us/help/918992/how-to-transfer-logins-and-passwords-between-instances-of-sql-server

And after we executed those to map the users to their databases we used

https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-change-users-login-transact-sql?view=sql-server-2017

Of course, take your backups beforehand if you are going down this path.

Greetings.

1974lg Old Hand Points: 374 More actions · Answer 4

you can also restore from full backup with norecovery and then only transfer the latest trn backups (alternative to log shipping), restore them.

of course depends how big the trn backups, but it should be fast...

don't forget logins:)