You must first configure the endpoint for
the principal instance. Note that wherever you start this Configure Security wizard, it will
assume that this is the principal database. Figure 8-17 shows that the area to select the
instance is grayed out.
CHAPTER 8 n DATABASE MIRRORING 216
Figure 8-17. You first create an endpoint for the principal instance, then create the same
types of endpoints for the witness and mirror instances. In this example, they??™re all on the
same server, so the computer is the same.
The interesting thing with mirroring endpoints is that each instance has only one
port dedicated specifically to mirroring traffic. If you create another mirroring session on
the SPYGLASSTAB\DBMIRROR1 instance, the entry for port and encryption will be grayed out
as well. Yet database mirroring is done at the database level, not the instance level. Anybody
feel the potential for a bottleneck?
Incidentally, the wizard creates an endpoint with the following settings:
CREATE ENDPOINT [Mirroring]
AUTHORIZATION [SPYGLASSTAB\jluetke]
STATE=STARTED
AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)
The key phrase in this code is FOR DATA_MIRRORING.
Pages:
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411