Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Moving DB from local disk to SAN. Expand / Collapse
Author
Message
Posted Monday, August 12, 2013 10:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: 2 days ago @ 2:21 PM
Points: 2, Visits: 249
Dear SSC team,
I hope your day is going well. I am tasked to move SQL Server 2008 DB, 2TB, which is in Simple Recovery Model, from local disk to a SAN, and it is on Developer Edition. The compatibility level is 90, I do not know if it will affect moving the database. It goes without saying NO DOWNTIME is allowed. Any suggestions? I have been considering backup/restore as an option.
Thanks for your response.
Dan.
Post #1483395
Posted Tuesday, August 13, 2013 3:56 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, November 21, 2014 1:12 AM
Points: 132, Visits: 934
berhanem 9188 (8/12/2013)
Dear SSC team,
I hope your day is going well. I am tasked to move SQL Server 2008 DB, 2TB, which is in Simple Recovery Model, from local disk to a SAN, and it is on Developer Edition. The compatibility level is 90, I do not know if it will affect moving the database. It goes without saying NO DOWNTIME is allowed. Any suggestions? I have been considering backup/restore as an option.
Thanks for your response.
Dan.


I think the challenge is having no downtime, it sounds like you will be moving to a new server?


You can do as you stated "back up and restore the DB to it's new location by using "MOVE" command within your restore t-sql to assign new path. In SSMS you should be able to do the same, but that would take longer than t-sql due to time navigating the interface.

However moving to a new server-you will have to consider things such as user logins/jobs/ssis packages/etc.. so you will need to restore the rest of the dbs, with exception of tempdb. If you are only moving the User DB (it does sound like you are moving a completely new server?), you will have to gather all the information for DB logins, you can do that by writing or finding a script that will help you.

If you run a google/bing search there should be websites full instructions.


--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully
Post #1483630
Posted Tuesday, August 13, 2013 5:04 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, October 28, 2014 10:45 AM
Points: 1,058, Visits: 2,696
2TB DB in Simple Recovery Model in local disk , how was the performance?

recently i restored a 1TB backup available from SAN drive to SAN drive took around 4.5 hours. so you can expect more delay for backup and restoration.

for no downtime(try the below but zero downtime never possible)

Change DB to full recovery.
Take full backup from old server.
Schedule log backup for 1 hour or so.
Create login,job,SSIS, alerts,DB mails etc on new server.
Restore it on new server in fullbackup and log sequence.
change applciation to point to new server and check.
(in case of any issue rollback to old server and backup and log backup will be helpful for another restore)



Regards
Durai Nagarajan
Post #1483648
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse