Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
homebrew
Posting Yak Master
114 Posts |
 Posted - 2008-10-21 : 15:57:58
|
| We have a server with 4 internal drives, about 750 G total of SQL databases spread over E (200 G) and F (600 G) drives. We want to remove the E drive and replace it with a 400 G drive (keeping it as E of course).Here's my rough draft of a plan .... any glaring errors, ommisions etc ... ?1) Terminate active SQL Connections2) Put SQL Server in Restricted User Mode3) Run FULL Backups of ALL DBs incl ones on F4) Run DIFF Backup of 650 G database - I will not have time to run a FULL5) Detach SQL Databases on E:\ drive6) Copy all data files on E to another storage device N:\ (All System DBs are on F)7) After copying data files, Stop SQL Services and set to Manual8) Power down SQL server - (Network Admin)9) Remove old hard drive - (Network Admin)10) Insert new hard drive - (Network Admin)11) Restart SQL server - (Network Admin)12) Format new drive as E - (Network Admin)13) Copy all data files back to E14) Start SQL Services, set to Automatic15) Reattach databases16) Verify that databases are accessible & readable17) Reboot application servers connecting to DB2 18) Verify applications can connect to databasesWe are not replicating, clustered or log shipping.Thoughts ? |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-10-21 : 16:25:01
|
I would use partition magic for servers1) plug in the new drive2) clone old e drive to new drive with pm83) remove old e drive letter4) change new drive letter to eif anything goes wrong with database, just remap drive letter e to old drive and your set to go again.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
|
|
|
Swapping out Disks on Our SQL Server