Post New Web Links

Welcome to the SQL Server Disaster Recovery and Availability Forum

Posted By: Posted Date: September 02, 2010 Points: 0 Category :Sql Server

(Edited 8/14/2009 to correct links - Paul)Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss: Using backup and restore Using DBCC, including interpreting output from CHECKDB and related commands Diagnosing and recovering from hardware issues Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I'm looking forward toÃÂ seeing this becoming a vibrant forum. This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help youÃÂ find answers to your questions more quickly and how to ask a good question. See you in the group! Paul RandalLead Program Manager, SQL Storage Engine and SQL Express Be a good citizen of the Forum When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful What to post in this forum I

View Complete Post

More Related Resource Links

Tips on using the SQL Server Security forum

I am collecting here a few tips on using this forum. The tips are actually pretty general, they're not really specific to SQL Server or to this particular SQL Server Security forum. 1. Verify that you are posting to the right forum. Check the list from http://forums.microsoft.com/MSDN/default.aspx?SiteID=1ÃÂ to see whether there is a more appropriate forum for your discussion topic. By posting to the appropriate forum, you will be able to get an answer to your questionsÃÂ faster. 2. Try to avoid crossposting or posting the same issue several times. Do a search to see if your question was already answered. If youÃÂ receive an answer on another forum, please update or remove your other posts on the same subject. 3. Please mark the posts that answer your questionsÃÂ using the "Mark as Answer"ÃÂ button. This will allow other readers to quickly identify the useful information in a thread. There can be more posts marked as answers in a single thread! 4. If you have posted on this forum but cannot find the post in it anymore, then it might have been moved to another forum. Check using the "My Threads" link: http://forums.microsoft.com/MSDN/User/MyForums.aspx?SiteID=1; it will show all the posts you've made and it will allow you to track a post that was moved to another forum. Also, consider enabling email notifications when a response is made to the threads you initiate. 5

My Sql server 2005 Database in recovery mode for 3 -4 hours every day

Hi , Some of our Sql Server 2005 databases remain in recovery mode after midnight for almost 3 to 4 hours. So when my application access them error "Databse in recovery" and for same database this happens again and again every night. Please suggest why and how this can be solved?

LDF File Disaster in SQL Server 2008

I am working on a startup company and the "dba" recently quit...come to find out he let the LDF file grow to 105GB - which effectively shut down the server due to lack of disk space. I need to serious help as this database is also supporting our replication system and thus I cannot do anything drastic like detaching, deleting the LDF file and reattaching. I tried the shrink file option but the LDF file did not shrink at all. I set the recovery model to simple, then tried shrinking and that did nothing. This is a SQL Server 2008 machine - can somebody please help? Also, given that I am mainly a developer, is there some EASY reference on how to setup log file backups so this does not happen in the future? Do I just perform a full backup every 30 minutes over-writing the previous backup, differentials, what? Thanks!

Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential cau

Attempting to upgrade from SQL 2005 EE to SQL 2008 EE on Vmware ESX 3.5 virtual server. below is info from Detail.txt related to successful install with failures... 2010-09-02 13:50:46 Slp: Sco: Attempting to check if file 'D:\Data\MSSQL.1\MSSQL\LOG\ERRORLOG' exists 2010-09-02 13:50:46 Slp: Sco: Returning security descriptor O:BAG:SYD:AI(A;ID;FA;;;S-1-5-21-3788118842-658835432-3441893140-1006)(A;ID;FA;;;S-1-5-21-3788118842-658835432-3441893140-1007)(A;ID;FA;;;BA)(A;ID;FA;;;SY)S:AI(AU;IDFA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD) 2010-09-02 13:50:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC. 2010-09-02 13:50:46 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes. 2010-09-02 13:50:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC. 2010-09-02 13:50:46 Slp: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes. 2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql) 2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(St

Disaster Recovery replication topology

I've been trying to figure out the best way to set up replication for our Disaster Recovery. Currently we have five production databases replicating through five distributors to one data warehouse. We're looking to recreate the same set of servers with replicated data for our Disaster Recovery, but I can't figure out the best approach. We are using Server 2003, SQL 2005, and transactional replication. Between our production and Disaster Recovery, we are sharing a 45Mb/sec tunnel. Here are the scenarios I've come up with: Scenario 1: Replicate the production databases to our Disaster Recovery databases using the original publications and distributors. Then using our Disaster Recovery distributors, create new publications from the replicated databases and replicate again to our Disaster Recovery Data Warehouse. With this method I've encountered a couple problems already. First, our two busiest databases can not keep up over the WAN after the snapshot is delivered (i.e. latency continues to grow). and second, so far I haven't been able to replicate a replicated database, and I'm not even sure it is possible. Scenario 2: Use the original production databases and configure our Disaster Recovery distributors to replicate to both our Disaster Recovery databases and our Disaster Recovery Data Warehouse. This means adding a second distributor for each original publisher, and

Forum FAQ: How can I degrade a SQL Server database from a higher version to a lower one?

Symptom Many times we are asked if it is possible to degrade a SQL Server database from a higher version to a lower one due to the business needs of data migration. However, it looks that Microsoft SQL Server doesn’t support degrading a SQL Server database from a higher version to a lower version by using the Copy Database Wizard or the detach and attach methods. Solution Yes, degrading a SQL Server database is not supported, but you can use a flexible workaround to resolve this issue. You can use SQL Server Management Studio to first generate scripts for a lower version and then use Data Import/Export Wizard to transfer data. For example, if you want to degrade a SQL Server 2008 database to SQL Server 2005, you can follow the steps below: 1. Open the SQL Server 2008 database in SQL Server Management Studio 2008. 2. Right click the database name in the Object Explorer and select "Tasks Generate Scripts…" 3. In the Script Wizard dialog box, select the database name and check "Script all objects in the select database". Then click "Next". 4. Set the "Script for server version" option as SQL Server 2005. 5. Run the script in SQL Server 2005. 6. Import data from SQL Server 2008 to SQL Server 2005 by using the SQL Server Import and Export Wizard. Similarly, you can do

Restoring a Service Application on Different Farm for Disaster Recovery

Hi All,

We are testing the Disaster REcovery scenario for SharePoint 2010 in multi-tenancy environment. The process I did is:

1. Created a sharepoint environment in a multi tenant scenario ( partioned the services while creating) and created few tenants with 1 or 2 site collections. (Parent Farm)
2. Created another environment with the same partioned mode. (DR Farm)
3. Tried to copy the site collection which is utilizing the Managed Metadata and restore it in DR farm along with the Parent Managed Metadata.

Everything is restored without error in the DR Farm (Site Collection and Service application and proxy). But, when I go to the term store (in tenant) I see a message like below:

"The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator. "

Also, the document library's managed metadata column value which was referring to the Managed Metadata it's greyed out (Read-Only).

My question is: How can I restore the service application and make it work and also how can i associate the site collection to use the Service Application which it was referring to previously.

I don't know if I need to restore the subscription also. I am not able to get enough information. In TechNet, w

WCF service with WAS and High Availability Cluster on Server 2008

I have a WCF service using one-way net.msmq transport to deliver messages to a high availability cluster.

I have followed a few articles I have found on setting up WCF in a cluster environment and essnetially have the following queues

Cluster: private$\MI/ManagementInformationService.svc

Node A: private$\MI/ManagementInformationService.svc

Node B: private$\MI/ManagementInformationService.svc

Although I am not sure why I need the local queues.

I've installed the WCF application into IIS7 on Node A and Node B. I;ve configured both nodes to the following address:

address="net.msmq://{cluster endpoint}/private/MI/ManagementInformationService.svc"

So, I configure my Web Servers to deliver the MI to the clustered endpoing via WCF net.msmq binding.

At this point, everything works and as messages hit the clustered queue, they are picked up by one of the nodes and processed. However, when I fail over the cluster, the second node does not automatically spring into life, as I would expect it to with WAS. However, if I browse the WSDL for my service on the now-current node, then it does indeed spring into life and process the messages off the queue.

So I turn on WCF tracing, IISReset fire up the WSDL, IISReset (to flush the WCF Trace log) then see the following:

A warning: Cannot detec

SQL Server 2005 Database recovery takes long when starting

I have a large database which is consistently taking between 30 and 60 minutes to come up after restarting SQL Server. How can I speed this up? Please read below before responding.

I have a Winows 2003, 2 node cluster running 1 instance of SQL Server 2005 enterprise ed. The server has 64GB of RAM, and 4 Quad core chips (16 logical processors). The storage is on SAN, and is a mix of RAID 10 and RAID 5 volumes. The instance has multiple DB's in it but 1 is far and away the largest @ 2TB allocated (about 1TB actual data). The database in question is broken into many datafiles as follows:

Primary filegroup = 1 10GB datafile

Secondary filegroup = 8 x 100GB datafiles spread evenly over 4 seperate volumes for I/O performance.

Partitioning filegroups = many many files used for a partitioned table (file sizes ranging from 1.5GB to 20GB)

Again, my issue is the following. This 2TB database takes close to an hour to startup everytime the instance of SQL Server restarts, failsover etc...

Couple of notes:

1) We have instant file initialization configured

2) Recovery model = simple

3) Recovery interval = 0

4) There are no active large transactions running when the instance goes down

&nbs

SQL Server 2005 Full Recovery

Hi All,
How do I do full recovery of database in SQL Server 2005.
I have full backup at 5 PM
and log till 6.45 PM. Now how do I recover my database. Could any one provide the scripts for backing up using roll forward.
Regards
Smithesh

Recovery model in Search Server Express 2010 Databases

Hi,

We have installed a Search Server 2010 Express. The Database is a SQL Server 2008 SP2 (Standard Version)

I'm not a SQL Crack, I am more the SharePoint specialist.

Now my question: Can I set the recovery model for all databases to "Simple" mode? (instead of full mode). Or is there any problem in functionality if i do this?

The default settings are, that some of this are simple and other databases are full.

Thanks a lot for your help.

High Availability in SQL Server 2008 Express edition

Dear friends ,

I am using SQL Server 2008 Express edition in my laptop ,I would like to do high availability samples such as Replication,Mirroring,and Log shipping in my laptop , i have two instances .is it possible to do samples (replication,mirroring,log shipping) plz guid me how to do.

thanks in advance

How to implement backup/disaster recovery for our product?

Hi Guys,

Ive been tasked with researching adequate backup procedures for a bit of web software that we sell. Its basically a website and an express sql database that is deployed onto a customer server. Over the time the databse will fill up with conent and we want to be able to advise the customer how they can back our software up.

Im wondering we could do nightly backups of the sql server but can this be automated with sql server management studio express?

If not can we do replication or databse mirroring?

Anyway any help would be much appreciated not sure what the best approach is.

Cheers,

Pete

Sharepoint 2010 Passphrase Not Connected To Farm - Disaster Recovery

Hi,

A few weeks ago i made a sql backup of all the sql 2008 database (just SharePoint dbs).
Lost that server. Had .baks on a backup drive offsite.
I restored the databases to a new windows server 2008/microsoft sql 2008 database server. I can connect to sharepoint_config.... but without knowing the passphrase I’m stuck.
I’m not sure what the passphrase is and resetting isn’t working (using SharePoint power shell ) due to me not being connected to that farm.

Anything i can do here? Thanks for any help that can be provided.

What is the best for Disaster recovery for Merge

Hi.

I've got one Database Server sql 2005, which play also the role of the publisher ; with actually 50 databases.
Each database contains 2 publications (one for desktop, and the second for windows mobile).

This is merge replication.

The way of sync is done with IIS (sqlcesa.dll and replisapi.dll)

I want to be able to be ready if something occurs on my servers.

About the IIS, it's not a problem I guess I can easily duplicate them.
I've got also night backup (.bak) of all the database.

But about the SQL Server database with merge publication, how can I solve the troubles :"my sql server crashs" ?

I read something about peer to peer replication ; is it the solution ? I mean, i create a peer to peer replication between 2 servers on the datacenter. Then I add checks on my applications to be able to switch from server A to B if problem.And if one crash, I just have to work with the second ; and as soon as the first server is reinstall I just reconfigue the peer to peer between the servers ?

Or is there other solution when there is replication on the server ? (I mean; if it was just a simple database, i'm sure there are easy steps for this).

I want to have a solution that will bring me a service level quality very high if something wrongs happens.

Sharepoint recovery through Windows Server Backup

I have sharepoint server 2010 installed on Windows Server 2008, Server is crached due to power fluctions, I take a backup of complete server through Windows Server Backup tool. Can I restore the Sharepoint by restore the full image of Server 2008?

LeoN

SQL Server Peer to Peer Replication and High Availability

I am looking at peer to peer replication to replace our current mirroring solution. ADO.Net has the partner server which works great when detecting the failover to the mirror. Will that workin a peer to peer configuration as well?


Categories:

ASP.Net	Windows Application	.NET Framework	C#	VB.Net	ADO.Net
Sql Server	SharePoint	Silverlight	Others	All