![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 55.00000000000001%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,801 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 23%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
You will not be able to setup 'mirroring' in your current environment. See this document: https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/upgrade-sql-server-failover-cluster-instance-2008-2012?view=sql-server-ver15
To be able to setup mirroring (availability group) you need to have a cluster and none of the scenarios allow for moving from 2008. This document shows how to perform a rolling upgrade: https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
This also shows what can/cannot be done: https://sqlha.com/2019/08/15/ags-and-wsfc-os-rolling-upgrades-what-works-and-what-doesnt/
Basically, this leaves you with a backup/restore option as the best and safest route to upgrade. You can reduce the amount of downtime using the following strategy:
- Backup database on old system
- Restore database to new system with norecovery (can be done several hours before cutover)
- Differential backup on old system about 1 hour before cutover
- Restore differential backup to new system with norecovery
- Restore transaction log backups from old system to new system from differential backup forward
- Perform tail-log backup on old system (will take database offline on old system - if not, manually take database offline)
- Restore final transaction log to new system
- Restore database with recovery
The downtime will be minimal - but you still need to have that downtime. All systems/applications connecting to the old system will need to be updated to connect to the new system. You could shut down the old system and update DNS so the old name now points to the new IP address - or you can setup client aliases - or make changes to the hosts file on each device...
Performing a backup/restore will not lose any data...unless you allow the applications to continue filing data into the old system. This is why you need to take the database offline...it will prevent any additional data from being filed into that database during the migration.
Even if you somehow get mirroring working...the applications connections must be updated to use the new system or the listener, which will require a downtime for the application to insure all connections have been moved.