question

heryhe avatar image
heryhe asked

Move database files to new LUNs.

Dear All, In the next few weeks, I have a plan to move my databases (120 databases) to new storage which will be applied into **4 LUNs(LUN1, LUN2, LUN3 and LUN4)**. Each LUN has 250GB and will be placed by 30 databases. For log files will be separately placed into other drive. FYI, my current databases are located in **one LUN** which consists of MDF and LDF files and the databases apply **log shipping** to 2 servers (RPT and DRC). What I want to achieve are **zero down time** and **no need to re-apply the Log Shipping one by one**. Is there any good approach to achieve those two (zero down time and no need re-apply log shipping). Any ideas or inputs will be very appreciated. :) Warm Regards, Hery
sql-server-2008databaselog-shippingmove
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Usman Butt avatar image
Usman Butt answered
First of all whenever there is a storage change, there has to be a downtime unless you are using high availability options like Clustering etc. where a fail-over option is available. With Log shipping one cannot achieve zero down time. Not to mention, optimistically, with such huge changes one has to expect some downtime and be ready for the worst case scenarios. Since it does not include system databases, my first feeling is (I hope I am not missing something), it should be an iterative process. One database at a time. It will narrow down the chances of a major disaster and could be a very manageable process. Each database is taken into single user mode, a log backup is taken through LogShipping job (To keep LS chain intact), stop LS job for the DB, take the DB offline, **copy** the DB files to the specific LUNs and then point the re-located DB files against the Database using ALTER DATABASE MODIFY FILE option. I will not move the files in order to have the option available to revert in cases like faulty storage etc.). Bring the database online. I would also DBCC the DB after this process. There could be more efficient ways than this for sure but in all the cases there would be some extra efforts and more work required IMHO. I guess nothing is for free in this world ;)
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hi Usman, FYI, I haven't implemented the high availability (clustering) on my database severs yet. Based on plan, next year, we will implement the clustering on my database servers. Anyway, many thanks for the response and idea. Regards, Hery
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.