DRAG DROP
You have two servers named SQL1 and SQL2 that have SQL Server 2012 installed. SQL1
contains a database that is mirrored asynchronously to SQL2. The database contents are
updated once a month.
You need to upgrade the database to SQL Server 2014. The solution must minimize
downtime.
Which upgrade steps should you recommend?
To answer, move the appropriate actions from the list of actions to the answer area and
arrange them in the correct order.
Answer: See the explanation.
Explanation:
Box 1: Fail over.
Box 2: Upgrade SQL1.
Box 3: Upgrade SQL2.
Box 4: Establish a mirror.Note:
* To perform the rolling upgrade
step 1: For each mirroring session whose mirror server instance has just been upgraded,
wait for the session to synchronize. Then, connect to the principal server instance, and
manually fail over the session.
Step 2: Upgrade each server instance that is now the mirror server in all mirroring sessions
in which it is a partner.
Step 3: Resume the mirroring session.
* When upgrading server instances to SQL Server 2014, you can reduce downtime for each
mirrored database to only a single manual failover by performing a sequential upgrade,
known as a rolling upgrade. A rolling upgrade is a multi-stage process that in its simplest
form involves upgrading the server instance that is currently acting as the mirror server in a
mirroring session, then manually failing over the mirrored database, upgrading the former
principal server, and resuming mirroring
Reference: Minimize Downtime for Mirrored Databases When Upgrading Server Instances
The listed answer is incorrect. It should be:
Upgrade Sql2
Failover (to Sql2)
Upgrade Sql1
(Re)Establish the Mirror
This is correct from https://msdn.microsoft.com/en-us/library/bb677181(v=sql.120).aspx.
“A rolling upgrade is a multi-stage process that in its simplest form involves upgrading the server instance that is currently acting as the mirror server in a mirroring session, then manually failing over the mirrored database, upgrading the former principal server, and resuming mirroring.”
It is not possible to failover when databases are mirrored in asynchronous mode.
For asynchronous mode you should switch to synchronous first or break the mirror.
https://msdn.microsoft.com/en-us/library/bb677181.aspx
therefore I would say:
1)Break the mirror
2)Upgrade SQL2
3)Upgrade SQL1
4)Establish a mirror
Seems to be the right answer
The page doesn’t mention we cannot manually fail over to the mirror in asynchronous mode.
Here’s how I read https://msdn.microsoft.com/en-us/library/bb677181(v=sql.110).aspx
The tricky term is the “mirrored asynchronously” which means high performance.
1) Upgrade SQL2
2) Failover
3) Upgrade SQL1
4) Failback (instead of re-establish mirror)
It is not possible to failover when databases are mirrored in asynchronous mode.
1) Upgrade SQL2
2) Failover
3) Upgrade SQL1
4) Failback (instead of re-establish mirror)
I Thinks :
1)Break the mirror
2)Upgrade SQL2
3)Upgrade SQL1
4)Establish a mirror
@@[email protected] i remember you ,you sell wrong dumps online
And he always says wrong answers (or just merely copies the default answer again)
His moniker is “Magnet”, so what do you expect?!
Isn’t this is a question from 70-462? I reckon the correct answer is:
Upgrade secondary
Failover to secondary
Upgrade primary
Fail back to primary
Nobody above has suggested a reason for breaking the mirror.
https://msdn.microsoft.com/en-us/library/bb677181.aspx actually recommends that if you have a witness it should be removed from the mirror temporarily to avoid accidental failover and if you’re in a-synch mode change to high safety.
1) Fail Over
2) Upgrade SQL1
3) Upgrade SQL2
4) Establish Mirror
On SQL1 there is a database which “is mirrored asynchronously” to SQL2.
We have a “high performance” mirroring session. Before any failover step, we have to switch into “synchronous mode”, otherwise manual failover is not possible.
No more less, before starting any upgrade, a failover test is more than recommended, to see how and if it works fine.
So, as per Microsoft recommendations https://msdn.microsoft.com/en-us/library/bb677181(v=sql.120), steps are dependent by mirroring mode.
In our case, I would suggest:
1. Switch from asynchronous (high performance) to synchronous (high safety) mode;
2. Failover (SQL1 becomes mirror, SQL2 as former mirror becomes new principal);
3. Take a full backup of all user databases on SQL2 (new principal)!!!
4. Upgrade first the actual mirror instance SQL1 to SQL2014;
5. Failover back as was initially, with SQL1 as principal and SQL2 as mirror;
6. Run DBCC CHECKDB on SQL1 to see if all dbs are fine after upgrade.
7. Upgrade SQL2 (as is mirror again) to SQL2014 version;
8. Switch mirroring from “high safety” (=synchronous) back to (“high performance” (=asynchronous) as was initially.
9. Resume mirror.
Using ONLY the options available on test, I opt for this order as minimal operations in place. At the final, roles remains switched with SQL as mirror and SQL2 as principal.
-Upgrade SQL2 (it is mirror);
-Failover (SQL2 becames new principal);
-Upgrade SQL1 (it is mirror now, after failover);
-Resume mirroring