In order to maintain high service levels in their disaster recovery facilities, many organisations must implement one-to-one configurations. However, some SQL Server disaster scenarios are not required to service the same level of transactions in the event of a failure. Many-to-one protection of SQL Server can be accomplished with Double-Take and native features of SQL Server. This paper discusses two primary methods for providing many-to-one failover configurations: named instance protection and recovery, and user database protection and attachment.