From a database administrator’s perspective, implementing a Disaster Recovery (DR) solution can be a daunting task. There are many pieces of the puzzle that need to be put together in order to have a successful DR solution. It is crucial to be involved from the beginning of the project and help define the scope.
In this article, we will discuss the steps involved in creating a DR solution for SQL Server. We will use a real-life example of a DR project that was handed to a DBA as an afterthought. The goal was to set up a DR site for the main production instance of each client within a few weeks.
The first step in this project was to gather information about the databases, DTS packages, jobs, and users that needed to be included in the DR solution. This information was crucial for setting up the DR server and ensuring that all necessary components were replicated.
Once the information was gathered, the next step was to copy the database to the DR server. In this case, there were no existing replication or high availability solutions in place, so a manual copy was required. It is important to ensure that valid backups are being processed on the production server and that there is enough bandwidth to copy the backups to the DR server.
After the database was copied to the DR server, the next step was to configure SQL Server on the DR site. This involved installing SQL Server, granting necessary permissions, and configuring any hardcoded configurations that were specific to the production server.
With the configuration in place, the next step was to implement the gathered information on the DR site. This involved restoring the database, adding users, attaching orphaned users, creating any needed jobs, and copying DTS packages. It is important to review the information with the business owners and decide on a subset of items to implement, as not all components may be necessary for the DR solution.
Once the implementation was complete, it was time to test the DR site. It is crucial to be available during the testing phase and be prepared to dig into the system for any configuration issues or hardcoded problems. With the help of the DBA, network admins, business analysts, production support individuals, and business owners, most hurdles can be overcome to ensure the system functions properly as a DR instance.
Throughout the project, it is important to communicate with the business owners and manage their expectations. It is crucial to emphasize the importance and timeframe needed to get each client up and running on the DR site. Prioritizing the project and involving all necessary parties from the beginning can help avoid friction and issues later on.
When creating your first DR site, it is essential to plan well. Get buy-in on the list of tasks and expected results, and involve all parties that need to be involved for a successful implementation. Plan, plan, and plan some more. Allow room for errors and resolution time. By following these steps and being prepared, your DR site implementation is more likely to be successful.
Remember, disaster recovery is a critical aspect of any SQL Server environment. By investing time and effort into creating a robust DR solution, you can ensure the continuity of your business operations even in the face of unexpected events.