locked
MOSS Database Machine Rebuild - Most prudent approach? RRS feed

  • Question

  • I am involved in a project to virtualize a MOSS farm.

    The web front end servers are already virtualised and do not need any work to achieve the objectives of the project.

    The database server is a physical machine and is to be virtualised (not a decision I can influence).

    The approach to virtualising this is basically to build a brand new machine.  i.e. the machine will not be a physical to virtual conversion and will therefore not have the same SID, though the name can be retained if required.

    On the new database machine we will attach the MOSS configuration, SSP, content databases etc so these databases are in place, clearly we can re-produce permissions if required.

    My question is what is the most prudent approach to doing this?

    Tuesday, May 15, 2012 5:03 PM

Answers

  • You will run into difficulty doing this, especially if the new virtualized SQL Server has a new hostname. Assuming you didn't create the farm using a SQL Server client alias, with MOSS you cannot change the SQL Server that the configuration database resides in without backing up the entire farm, deleting the farm, creating a new farm (with the configuration database on the new server) and restoring your backups (to the new SQL Server).

    If you created the farm with a SQL client alias you simply move the databases and update the alias to the new location. If you don't have an alias, instead of backing up the entire farm and restoring it, another approach is to create a SQL Server client alias with a name that is the same as the current SQL Server hostname. You can then move the databases to the new server and update the alias. The biggest problem with this is that it's confusing to see a server listed that is not really in the farm.


    Jason Warren
    Infrastructure Specialist

    • Marked as answer by Pengyu Zhao Monday, June 11, 2012 5:46 AM
    Tuesday, May 15, 2012 5:44 PM
  • Hi,

    You cannot just backup and restore (or detach it) the databases. This is because the configuration database of your farm cannot be restored to a new SQL server. You have to use the backup/restore tools described here for EPM : http://technet.microsoft.com/en-us/library/cc262412(v=office.12)

    For more information about moving the SharePoint Databases to a new SQL server instance, check out the following article:

    http://blogs.msdn.com/b/shaden/archive/2007/07/05/moving-the-sharepoint-databases-to-a-new-sql-server-instance.aspx

    Thanks,

    Rock Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Rock Wang TechNet Community Support

    • Marked as answer by Pengyu Zhao Monday, June 11, 2012 5:46 AM
    Wednesday, May 16, 2012 2:52 AM

All replies

  • You will run into difficulty doing this, especially if the new virtualized SQL Server has a new hostname. Assuming you didn't create the farm using a SQL Server client alias, with MOSS you cannot change the SQL Server that the configuration database resides in without backing up the entire farm, deleting the farm, creating a new farm (with the configuration database on the new server) and restoring your backups (to the new SQL Server).

    If you created the farm with a SQL client alias you simply move the databases and update the alias to the new location. If you don't have an alias, instead of backing up the entire farm and restoring it, another approach is to create a SQL Server client alias with a name that is the same as the current SQL Server hostname. You can then move the databases to the new server and update the alias. The biggest problem with this is that it's confusing to see a server listed that is not really in the farm.


    Jason Warren
    Infrastructure Specialist

    • Marked as answer by Pengyu Zhao Monday, June 11, 2012 5:46 AM
    Tuesday, May 15, 2012 5:44 PM
  • Hi,

    You cannot just backup and restore (or detach it) the databases. This is because the configuration database of your farm cannot be restored to a new SQL server. You have to use the backup/restore tools described here for EPM : http://technet.microsoft.com/en-us/library/cc262412(v=office.12)

    For more information about moving the SharePoint Databases to a new SQL server instance, check out the following article:

    http://blogs.msdn.com/b/shaden/archive/2007/07/05/moving-the-sharepoint-databases-to-a-new-sql-server-instance.aspx

    Thanks,

    Rock Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Rock Wang TechNet Community Support

    • Marked as answer by Pengyu Zhao Monday, June 11, 2012 5:46 AM
    Wednesday, May 16, 2012 2:52 AM
  • Hi,

    Are our replies helpful to you? If you have questions, feel free to let us know.

    Thanks,

    Rock Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Rock Wang TechNet Community Support

    Monday, May 21, 2012 2:14 AM