sharepoinTony

@info – The practical side of SharePoint

Posts Tagged ‘SQL’

Moving MOSS 2007 SQL Databases part 3

Posted by sharepoinTony on July 27, 2010

If you haven’t seen the earlier posts on this topic: Part 1 and Part 2

D-Day has arrived, it is time to actually move my SharePoint 2007 sql databases to a different SQL Server.  My previous posts touched on the research I did leading up to this event.  This post will cover the actual tasks and outcome.  I am writing this as I go through the process, so let’s all cross our fingers that it goes smooth.

My Plans

A summary of my plan is as follows:

  1. Backup the SharePoint farm
  2. Backup all SQL db’s
  3. Move those backups off to a “safe” spot on the network.
  4. Start the process defined in the TechNet article Move all databases (Office SharePoint Server 2007)
  5. Backup the SSP’s
  6. Remove SSP’s
  7. Stop the Farm (services)
  8. Backup sql db’s
  9. Copy backups to new sql server
  10. Restore sql db’s on new sql server
  11. Apply roles, permissions, etc. to new sql server & restored db’s
  12. Restart Farm
  13. Restore SSP’s from backup
  14. Cross-fingers and check to see that our SharePoint intranet is up and running
  15. Go have a beer

Round 1

I attempted these steps and all went smoothly until I got to step 13 – Restore SSP’s from backup.  The restore made it to 50 percent complete then ran into this error:

SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

After several attempts and a grueling session of troubleshooting I found that the SQL Server Agent was not running on my ‘new’ SQL server (SQL Server 2008 R2 64-bit, running on Windows Server 2008 64-bit).  The fun part was that I couldn’t get it to start.  The Agent would just stop after every attempt to start it.  I tried several solutions found on-line, none of which worked.

At this point my weekend was over and we needed the production server back online, so I did the restore BACK to the original SQL Server.  SharePoint was up and running fine very quickly.

Finally, I un-installed SQL Server 2008 R2 from the new server and started over.  After carefully reinstalling SQL Server 2008 R2 I no longer had any problem with the SQL Server Agent.  Hurray, now will the SSP restore work?  I have to wait until the next weekend to find out.

Round 2

Friday – A week has gone by and I am now preparing to walk through all of those steps again.  More confident than last time perhaps, but concerned at what I might run into this time around.  I will do all of the initial steps – the backups – tonight, Friday night.  Saturday morning I will start the scary part, removing the SSP’s and moving everything to the new SQL Server.

Saturday – Everything went well up to the restore, again. This time the error was an Access Denied error pointing to the SharePoint backup directory.  Short-story resolution: change the SQL Server account to use a Domain account, make sure that domain account had permissions to the backup folder and to the sql database files folder.  I also wanted to make sure I didn’t have any more trouble getting to the backup folder so I opened it up (temporarily) to several other accounts – my ssp and app-pool users.

The SSP Restore completed successfully, with zero errors and zero warnings.  Hurray!

Hold-on, the process outlined by Microsoft ends here.  What about my content databases?

Searching about I found that I need to use stsadm to detach the content databases, one by one, from the SharePoint server and add the databases on the new server.  So I begin this task and have no problems until I get to the Config database.  It detaches fine, but then the services become disabled and the attach (setconfigdb) results in “Value cannot be null.  Parameter name: str” !  What the?!  Time for Microsoft Support calls.

Support helped resolve the ‘migration’ issues, however now the SSP is not working-including search, and there are several other things missing.  I am told I will have to add any solutions back in, and find whatever features or web parts that might not work and fix them.  Also have to open a new ticket for ‘advanced troubleshooting’ on the SSP.  It has been a long Saturday.

Round 3

Sunday – Monday (ouch)

After hours on the phone and several rounds of running psconfig we were able to get a new Config db setup and restore over it to capture most of my configuration data.  The SSP is a different story.  We had to create a new SSP, which left me with a few more days of reconfiguring the SSP, Search, Audiences, etc. before I was “back” to normal.

Wrap-up

Some good came from this pain… since I had to reconfigure the SSP I could apply some lessons learned since the original install.  Now I feel like my SSP is “better” than it was before. 😉   I improved our Search features, including a federated search we were using, I cleaned up some Audiences that were not used, etc.   I just had to find some improvements!

Posted in Commentary, Install and Configure, SharePoint 2007 | Tagged: | 2 Comments »

Moving MOSS 2007 SQL Databases part 2

Posted by sharepoinTony on May 11, 2010

Today I am looking at the AvePoint DocAve option that I dreamed up when faced with the need to move my SharePoint sql databases to a different sql server.

DocAve is a great backup tool, and the features it provides for disaster recovery are nice.  The product, once installed and configured(1), allows your system admin or SharePoint admin manage backup and restore activities easily.  The system can even be configured to allow others (Site Collection Administrators for example) to restore their own sites, lists and libraries.  Access is controlled, making this feature a bonus to SharePoint Administrators in larger environments.

In my scenario, where I want to MOVE all of my SharePoint databases to another SQL server, there is a little weakness displayed in the DocAve armor. The ConfigDB, SPWebService, CentralAdmin WebApp, and Admin ContentDB’s can only be restored “in place”(2). That means the destination sql server must have the same name and configuration as the sql server where the backup originated.  I can’t restore those db’s to a different sql server, thus I cannot complete my task using DocAve.  To be fair, I could use DocAve backups to accomplish part of my task, just not the whole task.

This situation is not common, so AvePoint shouldn’t be dinged points for the DocAve product – my guess is that it handles at least 95% of the requirements for pretty much any SharePoint shop.  I like the product, use the product and might even recommend the product…I am just bummed that it isn’t magically making this specific task drastically easier.  I guess that is why there are migration tools out there. 😉

Continue to Part 3

Footnotes:
1. Another post may cover the install configuration process for DocAve based on my experience.  This is an area where I think AvePoint could improve.
2. Information obtained from the “Platform Backup and Restore” whitepaper from AvePoint.

Posted in Commentary, SharePoint 2007 | Tagged: | Leave a Comment »

Moving MOSS 2007 SQL Databases

Posted by sharepoinTony on May 10, 2010

I have a MOSS 2007 implementation that consists of a SharePoint “farm” on one server and the SharePoint databases on a shared SQL Server. The SharePoint server is running Windows Server 2008 and is 64-bit, but the SQL Server is on Windows 2003 with SQL 2005.

One of the other applications using this shared SQL server is fairly critical and the performance is starting to take a hit. This has opened an opportunity to get our SharePoint databases moved to a dedicated SQL server.

I don’t know if anyone else out there has a similar hardware situation or not, but I thought I would try to post a few thoughts as I go through this process over the next few weeks. Let me know if you have already done this or think I am taking a wrong turn as I go.

One idea I have is to take full advantage of the need to move and upgrade to a SP2010 compliant SQL system – and go to SQL 2008 while I am at it. Good idea or bad idea?

Another thought is to investigate whether or not I can make use of our recently implemented DocAve Data Protection software from AvePoint. Maybe I could ‘act’ like a disaster happened and I need to restore my SQL Server on a new box. I wonder if that would work, and if it would be any faster/easier?

Let the investigation begin.

My first stop is with this TechNet article, Move all databases (Office SharePoint Server 2007): http://technet.microsoft.com/en-us/library/cc512725.aspx – my light reading for tonight.

Continue to Part 2

Posted in Commentary, SharePoint 2007 | Tagged: , | 1 Comment »