A SQL Server distributed availability group (distributed AG) can be failed over without data loss only when the target is prepared and synchronization is verified. The documented distributed-AG failover command is FORCE_FAILOVER_ALLOW_DATA_LOSS; the command itself does not guarantee a lossless outcome. Check the SQL Server versions, replica roles and health, commit modes, and per-database hardened log sequence numbers (LSNs) before proceeding. If those checks do not establish that the target has received and hardened the required transactions, do not describe the failover as lossless.
Understand which replicas are involved
A distributed AG connects two availability groups, often on separate clusters. The primary replica in the second availability group is the forwarder: it receives transactions from the global primary and forwards them to its own local secondary replicas. The global primary is the primary replica of the first AG. Identify both roles and the intended new primary before changing anything. Microsoft describes distributed AGs as a disaster-recovery and migration option in its SQL Server business continuity and database recovery guidance.
Distributed AG failover is manual. Microsoft’s configuration guidance says the supported distributed-AG failover type is a manual, user-initiated FORCE_FAILOVER_ALLOW_DATA_LOSS. That wording matters: this is a forced-failover command, so a lossless result depends on the synchronization preparation and evidence described below, not on the command name. Use the instructions for the deployed SQL Server version: Microsoft publishes separate procedures for SQL Server 2022 and SQL Server 2025; the latter distinguishes its newer process from SQL Server 2019 and earlier.
Before failover, establish whether a lossless transition is supportable
Treat failover as a controlled procedure, not a generic command to run when a database is unavailable. First establish the topology and versions, then verify the synchronization state for every database that must be protected.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Record the version on both availability groups. Confirm which version-specific procedure applies. Do not assume that instructions for SQL Server 2022 and later apply unchanged to SQL Server 2019 and earlier, or that every upgrade or migration topology supports the same sequence.
- Confirm the global primary and forwarder. Identify the current roles, the intended target, and whether the incident affects one database, one replica, or an entire site. A local database problem is not automatically a reason to fail over the distributed AG.
- Verify replica health and synchronization. Follow the matching Microsoft procedure to check that the participating replicas are healthy and that the distributed AG and databases have reached the required synchronized state.
- Check commit modes. Microsoft’s no-data-loss procedure requires synchronous commit for the relevant primary replicas and across the distributed AG during preparation. Asynchronous commit can tolerate greater geographic latency, but does not provide the same synchronization evidence for a lossless transition.
- Compare hardened LSNs per database. The global primary and forwarder must show matching
last_hardened_lsnvalues for the no-data-loss readiness check in the documented procedure. If they do not match, the target has not been proven to have hardened the same log position. Stop and follow Microsoft’s applicable retry or failback branch instead of proceeding on the assumption that no transactions will be lost.
Microsoft’s version-specific distributed AG procedure describes the synchronization and hardened-LSN checks. Treat them as gates: if a replica is unhealthy, synchronization has not completed, or the LSNs differ, do not proceed with a failover represented as lossless.
SQL Server 2022 and later: follow the documented no-data-loss sequence
For SQL Server 2022 and later, Microsoft documents a specific preparation using REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT. This setting is part of the newer version’s procedure; it is not a substitute for checking replica health and hardened LSNs.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
- Switch the relevant replicas to synchronous commit. Configure synchronous commit between the relevant AG primaries and across the distributed AG, as required by the documented procedure.
- Wait for synchronization. Do not move on until the replicas and distributed AG report the required synchronized and healthy state.
- Set the required synchronized secondaries value to 1 on the global primary. This makes commits wait for the secondary. It can reduce performance, so account for that trade-off while the protection is in effect.
- Verify each database’s hardened LSN alignment. Compare the global primary and forwarder as directed by Microsoft. Proceed only when the values match and the remaining health and synchronization checks pass.
- Change the global primary’s distributed-AG role to
SECONDARY. Perform this role change in the order prescribed by the version-specific instructions. - Initiate failover from the intended forwarder. Use the documented manual
FORCE_FAILOVER_ALLOW_DATA_LOSSoperation only after the preceding checks pass. - Reset the synchronized-secondaries setting as directed. Microsoft’s procedure includes resetting the setting on the new secondary. Follow its exact steps for the deployed topology rather than improvising the post-failover configuration.
With REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT set to 1, the primary waits for the secondary before committing transactions, which can affect performance. Microsoft notes that asynchronous commit can be restored after failover where geographic latency warrants it; make that change in the documented post-failover context, not before the lossless readiness checks. See the SQL Server 2025 distributed AG guidance for the precise sequence and version-specific details.
SQL Server 2019 and earlier: do not reuse the newer sequence blindly
The newer REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT procedure is not the general recipe for older SQL Server versions. Microsoft separates its SQL Server 2022-and-later no-data-loss instructions from the SQL Server 2019-and-earlier path. For an older deployment, follow the matching version’s configuration guidance and its synchronization, failover, and recovery branches. If the documented checks do not establish matching hardened log positions, the available evidence does not support calling the outcome lossless.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
What to do when the checks fail
- Hardened LSNs differ: Do not issue the forced failover as a no-data-loss operation. Follow the retry or failback branch for the applicable SQL Server version and recheck synchronization.
- Replicas are unhealthy or not synchronized: Resolve the replication or connectivity problem if the current primary remains available, then wait for synchronization and repeat the readiness checks. If the primary is unavailable, treat a forced failover as an emergency decision with possible data loss.
- Loss of service takes priority over preserving every transaction: Microsoft documents forced failover for situations where data loss is acceptable. Make that trade-off explicit, retain the best available evidence about the last synchronized state, and do not promise a lossless recovery.
- The old primary may return after a forced failover with data loss: Microsoft’s standard AG guidance warns that the former primary may later assume the primary role. Where that guidance matches the incident topology, remove the old primary from the availability group after the forced failover to prevent replicas from entering inconsistent states. See Microsoft’s instructions for manual availability-group failover.
Manual seeding initializes a database; it does not prove a lossless failover
If the forwarder needs a database initialized manually, Microsoft’s distributed-AG guidance describes taking a full backup and a transaction log backup on the global primary, restoring both on the forwarder with NORECOVERY, and then joining the database to the distributed AG. This prepares the database to catch up; it is a distinct initialization task, not evidence by itself that a later failover will lose no data. Use the backup, restore, and join order in the official manual-seeding instructions.
Choose the recovery approach that fits the failure
| Situation | Approach | What it establishes |
|---|---|---|
| Planned site transition, with both sites available | Use the version-specific distributed-AG no-data-loss procedure, including synchronous preparation and matching hardened LSNs. | Readiness evidence for the documented transition, provided every required check passes. |
| Disaster, with the global primary unavailable | Evaluate the forwarder’s last hardened state and the applicable version’s recovery branch before any forced failover. | If synchronization cannot be validated, a lossless outcome is not established; forced failover may lose data. |
| Forwarder lacks an initialized database | Use the documented automatic or manual seeding method; manual seeding uses full and log backups restored with NORECOVERY before joining. |
Database initialization and catch-up, not a failover guarantee. |
| Recovery design needs a configurable delay to help address human error | Consider log shipping as a separate disaster-recovery design option; Microsoft notes it can be combined with availability groups. | A distinct recovery mechanism, not an equivalent substitute for the distributed-AG failover procedure. |
Distributed AGs can support disaster recovery between separate clusters and migration scenarios, but the appropriate procedure depends on the deployed versions and topology. For teams without qualified DBA support, engage SQL Server disaster-recovery expertise before executing a forced transition.
Quick Recap
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
