July 17, 2015 at 6:14 am
Hello everyone
I'm a DBA in training and this is my first post here on SQL Server Central.
--========================================================
Sadly I don't have a spare server to mess about with in the office so I've got a laptop (not connected to any networks) hosting multiple Hyper-V VMs on Windows Server 2012 R2 standard and I'm currently trying to setup Mirroring using SQL Server 2014 (Enterprise Evaluation Edition).
Attemp No1:
--========================================================
Mirror a database across 2 instances on the same VM
On the VM machine:
-Added "local" to the Primary DNS suffix
-Set Hyper-V Virtual Switch to PRIVATE
-Turned off windows Firewall
-Installed 2 instances of SQL Server 2014
-Created a database called "DBMirror" on instance A
-Backed up database FULL
-Backed up database LOG
-Restored database FULL using MOVE and NORECOVERY on instance B
-Restored database LOG using NORECOVERY
--========================================================
Instance A > DBMirror > Tasks > Mirror
-Followed GUI
-No Witness
-Instance A set to Port 5022 and Endpoint to "Mirroring" (Encryption OFF)
-Instance B set to Port 5023 and Endpoint to "Mirroring" (Encryption OFF)
-Service accounts page left empty (Not on a domain)
-Finish
-Configuring Endpoints - Successful > Close
Sounds good so far
TCP://SERVER/A.local:5022
TCP://SERVER/B.local:5023
Click "Start Mirroring"
-FQDN Warning message > Click Yes
--========================================================
RESULTS:
The Server network address "TCP://SERVER/B.local:5023" can not be reached or does not exist.
Error: 1418
--========================================================
Please also read "Database Mirroring hates me - Attempt no2"
July 17, 2015 at 6:18 am
First question. Why are you implementing mirroring on SQL 2014 when it's been deprecated for two versions and will probably be removed soon?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 17, 2015 at 6:34 am
GilaMonster (7/17/2015)
First question. Why are you implementing mirroring on SQL 2014 when it's been deprecated for two versions and will probably be removed soon?
Short version: Learning.
Long Version: I work for a company as a DBA and we support SQL 7 right up to 2014, it doesn't matter if the feature gets deprecated as I'm sure many clients are unwilling to move away from Mirroring or are not in any kind of a rush to spend money on the latest versions.
I also beleive that understanding Mirroring will help me understand AlwaysOn technology which has a while left until it's deprecated.
July 18, 2015 at 6:56 am
DBA on Route (7/17/2015)
Short version: Learning.
Ok, its ideal for that
DBA on Route (7/17/2015)
I also beleive that understanding Mirroring will help me understand AlwaysOn technology which has a while left until it's deprecated.
sort of, alwayson groups use the same database mirroring endpoints so it will help you dealing with those.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply