--- title: "GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/failoverGroups" method: GET path: "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/failoverGroups" tags: ["FailoverGroups"] --- # GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/failoverGroups `GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/failoverGroups` Lists the failover groups in a server. ## Path parameters - `resourceGroupName` string, required - `serverName` string, required - `subscriptionId` string, required ## Query parameters - `api-version` string, required ## Response `200` Successfully retrieved the failover groups. - FailoverGroupListResult — A list of failover groups. - `value` FailoverGroup[] — Array of results. — unresolved $ref - `nextLink` string — Link to retrieve next page of results. ## Other responses - `default` — *** Error Responses: *** * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs. * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid. * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique. * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server. * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported. * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests. * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid. * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server. * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative. * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint. * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests. * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint. * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'. * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group. * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed. * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues. * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server. * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation. * 400 ServerNotFound - The requested server was not found. * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server. * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group. * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame. * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service. * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link. * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server. * 400 InvalidIdentifier - The identifier contains NULL or an invalid unicode character. * 400 InvalidSku - The user specified an invalid sku. * 400 TokenTooLong - The provided token is too long. * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition. * 400 CannotUseReservedDatabaseName - Cannot use reserved database name in this operation. * 400 InvalidServerName - Invalid server name specified. * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region. * 400 PartnerServerNotCompatible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa. * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link. * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server. * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target. * 400 GeoReplicaLimitReached - The per-replica replication limit was reached. * 404 ResourceNotFound - The requested resource was not found. * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription. * 404 SourceDatabaseNotFound - The source database does not exist. * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription. * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database. * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress. * 409 RemoteDatabaseExists - The destination database name already exists on the destination server. * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server. * 409 FailoverGroupBusy - Failover Group is busy with another operation. * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one. * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove. * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add. * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint. * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied. * 409 SubscriptionDisabled - Subscription is disabled. * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed. * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship. * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state. * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request. * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role. * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources. * 429 ConflictingServerOperation - An operation is currently in progress for the server. * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources. * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources. * 504 RequestTimeout - Service request exceeded the allowed timeout. --- [API](https://skmtc.dev/azure/apis/sqlmanagementclient-35.md) · [All operations](https://skmtc.dev/azure/apis/sqlmanagementclient-35/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/azure/sqlmanagementclient-35/revisions/bbbbdfc865d4/schema)