Home > Setting up Failover Groups for AzureSQLDB for IDERA TeamServer

Setting up Failover Groups for AzureSQLDB for IDERA TeamServer

database illustration

Setting up Failover Groups for Azure SQL Database is crucial for ensuring high availability and disaster recovery. Here’s a step-by-step guide to establishing Failover Groups and integrating them with IDERA TeamServer:

Setting up Failover Groups for Azure SQL Database

Prerequisites:

  1. Azure Subscription: Ensure you have access to an Azure subscription with appropriate permissions to create resources.
  2. Azure SQL Database: Have an existing Azure SQL Database instance ready.

Step 1: Access Azure Portal

Log in to the Azure Portal.

Step 2: Create a Failover Group

  1. In the Azure Portal, navigate to your SQL Database resource.
  2. Under the Settings section, select Failover groups.
  3. Click on + Add group.
  4. Provide a name for the Failover Group, select the desired subscription, resource group, and location.
  5. Choose the primary and secondary databases. These databases should have the same schema.
  6. Configure the Failover Policy (Automatic or Manual).
  7. Set up the Azure SQL Server instance for the secondary database.

Step 3: Configuring Auto-Failover

  1. Select the created Failover Group.
  2. Under Automatic Failover, enable the option for automatic failover if desired. Configure the failover policy and grace period.

Step 4: Set up IDERA TeamServer

Follow the instructions provided in the IDERA TeamServer documentation to install and configure the TeamServer and Repository on your preferred environment.

Integrating Auto-Failover with IDERA TeamServer

  1. Access the TeamServer configuration settings.
  2. Locate the database connection settings within TeamServer.
  3. Update the connection string to point to the Failover Group endpoint instead of a single database endpoint.

Benefits of Auto-Failover Groups for IDERA TeamServer:

  1. High Availability: With Failover Groups, your IDERA TeamServer database remains available even if the primary server encounters issues.
  2. Minimal Downtime: Automatic failover reduces downtime in case of a primary database failure, ensuring continuous access to IDERA TeamServer.
  3. Disaster Recovery: Failover Groups facilitate swift recovery during disasters or server outages, maintaining access to critical data for IDERA TeamServer users.
  4. Seamless Switchover: Failover Groups offer a seamless transition between primary and secondary databases, allowing users to work without interruptions.

By setting up Auto-Failover Groups for your Azure SQL Database hosting IDERA TeamServer, you ensure a robust infrastructure that minimizes disruptions and maintains accessibility to critical data for your team’s collaboration and productivity.

Always remember to regularly test failover scenarios to ensure the setup functions as expected in real-world situations.

ER/Studio Logo
Aligning complex data environments with business goals for over 30 years.
Copyright © 2024 Idera, Inc.