Post reply

Hardware Testing

  • October 15, 2011 at 10:39 am

    #258872

    Hi,

    We're planning on testing a new storage device in production. We're planning on putting Temp DB and a couple user DBs on the device. Since we use a clustered environment, we'll do the failover for TempDB but for user DBs to minimize the outage we were planning on restoring the latest backups on the new device, detaching the original dbs and renaming newly restored dbs for the apps to continue to functiong. Does anyone have any other ideas on how to limit the outage?

    Thanks

  • October 15, 2011 at 6:40 pm

    #1395019

    Lexa (10/15/2011)

    Hi,

    We're planning on testing a new storage device in production. We're planning on putting Temp DB and a couple user DBs on the device. Since we use a clustered environment, we'll do the failover for TempDB but for user DBs to minimize the outage we were planning on restoring the latest backups on the new device, detaching the original dbs and renaming newly restored dbs for the apps to continue to functiong. Does anyone have any other ideas on how to limit the outage?

    Thanks

    If you have to test new hw on a production db server, why not hook it up to the passive node and io stress test it there? Seems to me the best way to limit outage is not to do it.

    To answer your question, you can add a new file and file group on the new volume, and rebuild indexes to migrate the data.

    You'll generate a bunch of log data, but no outage, just some blocking.

    Really depends on the size of the db's.

    Oh, and don't forget to add it as a dependency in the cluster.

    Good luck!

Viewing 2 posts - 1 through 1 (of 1 total)

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