I'm trying to formulate a disaster recovery plan for our SharePoint environment. So far the solution I have works, but the restores are extremely slow (150-200MB/min).
Here's my setup:
And this is my DR plan:
Now, this process does work, however step 4 takes forever! I have about 10 Content DBs in 1 web application - in total about 115GB. Backup Exec will restore the DBs back to the new SQL server with a Job Rate of 3GB/min but as soon as the byte count hits the expected size for that DB the job just seems to hang. Looking on the SQL Server the DB is in a '(Restoring)' state. If I leave it alone for longer enough the job eventually completes and the DB is restored, but I don't know what it is doing or trying to do for the majority of the job! The eventual Job Rate ends up at 200MB/min, meaning my 115GB restore takes around 10hrs to complete - not great.
I've tried many different options but nothing seems to make a difference.
Has anyone had a similar experience to this? if so I'd greatly appreciate your assistance.
What is the log file size for the content database. If this is large, it might take longer time to perfrom a recovery and get the Database connected and online.
As a test, try to backup a similir size / configuration database from a SQL server and redirect restore on the DR SQL instance and compare the results.
I set the logs pretty big as I've found that they fill up quickly when users are moving files around in their sites. Having said that though I do a log backup everyday which should truncate them should it not?
We do normal SQL restores during DR, one of which is redirected and this has no problems and is a lot bigger than my SharePoint DBs
I would say, a standard Full and Incremental backup strategy should be good to keep consistent backups and also logs under control.
However, as the effective logs size during the restore would large it might take some time to finish. During the restore phase, there would be a SQL log recovery once the database and logs have bee coppied over to the target location.