Problems creating mirroring on 2005.

SQL2K5 sp1
Instance names:
Development\MySQL2K5
Development\Subscriber
Development\Witness
Im trying to set up mirroring on 3 instances on my desktop and having some
issues (not ideal I know, but it's what I've got to work with for now). Here
is what I've done:
--Create endpoint on principal instance and set recovery model
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5022 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
ALTER DATABASE AdventureWorks
SET RECOVERY FULL;
--Create endpoint on mirror instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5023 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
--Create endpoint on witness instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5024 )
FOR DATABASE_MIRRORING (ROLE=WITNESS);
GO
--Backup principal database
BACKUP DATABASE AdventureWorks
TO DISK='C:\MirrorBackup\AWBackup.BAK'
with init;
GO
--Restore mirror database
RESTORE DATABASE AdventureWorks
FROM DISK='C:\MirrorBackup\AWBackup.BAK'
WITH NORECOVERY,
MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
GO
--On the mirror server set the principal server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5022'
GO
--On the principal server set the mirror server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5023'
GO
That last step blows up with:
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://MYSQL2K5:5023" can not be reached or does
not exist. Check the network address name and that the ports for the local
and remote endpoints are operational.
Any ideas?
TIA, ChrisRWhat about the security configuration? Have you granted connect permissions
to the other servers' accounts to the database mirroring endpoints?
You should use
grant connect on endpoint::endpoint_mirroring to [domain\account]
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> SQL2K5 sp1
> Instance names:
> Development\MySQL2K5
> Development\Subscriber
> Development\Witness
> Im trying to set up mirroring on 3 instances on my desktop and having some
> issues (not ideal I know, but it's what I've got to work with for now). Here
> is what I've done:
> --Create endpoint on principal instance and set recovery model
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5022 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> ALTER DATABASE AdventureWorks
> SET RECOVERY FULL;
> --Create endpoint on mirror instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5023 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> --Create endpoint on witness instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5024 )
> FOR DATABASE_MIRRORING (ROLE=WITNESS);
> GO
> --Backup principal database
> BACKUP DATABASE AdventureWorks
> TO DISK='C:\MirrorBackup\AWBackup.BAK'
> with init;
> GO
> --Restore mirror database
> RESTORE DATABASE AdventureWorks
> FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> WITH NORECOVERY,
> MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> GO
> --On the mirror server set the principal server
> ALTER DATABASE AdventureWorks
> SET PARTNER => 'TCP://MySQL2K5:5022'
> GO
> --On the principal server set the mirror server
> ALTER DATABASE AdventureWorks
> SET PARTNER = 'TCP://MySQL2K5:5023'
> GO
> That last step blows up with:
> Msg 1418, Level 16, State 1, Line 1
> The server network address "TCP://MYSQL2K5:5023" can not be reached or does
> not exist. Check the network address name and that the ports for the local
> and remote endpoints are operational.
> Any ideas?
> TIA, ChrisR
>
>|||That didn't fix it. As an FYI all 3 instances are running under the same
domain account.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> What about the security configuration? Have you granted connect
permissions
> to the other servers' accounts to the database mirroring endpoints?
> You should use
> grant connect on endpoint::endpoint_mirroring to [domain\account]
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > SQL2K5 sp1
> >
> > Instance names:
> >
> > Development\MySQL2K5
> > Development\Subscriber
> > Development\Witness
> >
> > Im trying to set up mirroring on 3 instances on my desktop and having
some
> > issues (not ideal I know, but it's what I've got to work with for now).
Here
> > is what I've done:
> >
> > --Create endpoint on principal instance and set recovery model
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5022 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > ALTER DATABASE AdventureWorks
> > SET RECOVERY FULL;
> > --Create endpoint on mirror instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5023 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > --Create endpoint on witness instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5024 )
> > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > GO
> > --Backup principal database
> > BACKUP DATABASE AdventureWorks
> > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > with init;
> > GO
> > --Restore mirror database
> > RESTORE DATABASE AdventureWorks
> > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > WITH NORECOVERY,
> > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > GO
> > --On the mirror server set the principal server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER => > 'TCP://MySQL2K5:5022'
> > GO
> > --On the principal server set the mirror server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER = 'TCP://MySQL2K5:5023'
> > GO
> >
> > That last step blows up with:
> > Msg 1418, Level 16, State 1, Line 1
> > The server network address "TCP://MYSQL2K5:5023" can not be reached or
does
> > not exist. Check the network address name and that the ports for the
local
> > and remote endpoints are operational.
> >
> > Any ideas?
> > TIA, ChrisR
> >
> >
> >|||Let us try something else then.
Is MYSQL2K5 the name of your computer?
BOL recommends to use the fully qualified domain name. Try ipconfig /all and
look for host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> That didn't fix it. As an FYI all 3 instances are running under the same
> domain account.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> >
> > What about the security configuration? Have you granted connect
> permissions
> > to the other servers' accounts to the database mirroring endpoints?
> >
> > You should use
> >
> > grant connect on endpoint::endpoint_mirroring to [domain\account]
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > SQL2K5 sp1
> > >
> > > Instance names:
> > >
> > > Development\MySQL2K5
> > > Development\Subscriber
> > > Development\Witness
> > >
> > > Im trying to set up mirroring on 3 instances on my desktop and having
> some
> > > issues (not ideal I know, but it's what I've got to work with for now).
> Here
> > > is what I've done:
> > >
> > > --Create endpoint on principal instance and set recovery model
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5022 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > ALTER DATABASE AdventureWorks
> > > SET RECOVERY FULL;
> > > --Create endpoint on mirror instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5023 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > --Create endpoint on witness instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5024 )
> > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > GO
> > > --Backup principal database
> > > BACKUP DATABASE AdventureWorks
> > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > with init;
> > > GO
> > > --Restore mirror database
> > > RESTORE DATABASE AdventureWorks
> > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > WITH NORECOVERY,
> > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > GO
> > > --On the mirror server set the principal server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER => > > 'TCP://MySQL2K5:5022'
> > > GO
> > > --On the principal server set the mirror server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > GO
> > >
> > > That last step blows up with:
> > > Msg 1418, Level 16, State 1, Line 1
> > > The server network address "TCP://MYSQL2K5:5023" can not be reached or
> does
> > > not exist. Check the network address name and that the ports for the
> local
> > > and remote endpoints are operational.
> > >
> > > Any ideas?
> > > TIA, ChrisR
> > >
> > >
> > >
>
>|||The box name is Development. The instance name is MySQL2K5. I have tried
development\mysql2k5 and many variations of it and get incorrect syntax
errors. I also tried the FQDN and still got the original error.
Thanks for all the help.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> Let us try something else then.
> Is MYSQL2K5 the name of your computer?
> BOL recommends to use the fully qualified domain name. Try ipconfig /all
and
> look for host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > That didn't fix it. As an FYI all 3 instances are running under the same
> > domain account.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > >
> > > What about the security configuration? Have you granted connect
> > permissions
> > > to the other servers' accounts to the database mirroring endpoints?
> > >
> > > You should use
> > >
> > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > SQL2K5 sp1
> > > >
> > > > Instance names:
> > > >
> > > > Development\MySQL2K5
> > > > Development\Subscriber
> > > > Development\Witness
> > > >
> > > > Im trying to set up mirroring on 3 instances on my desktop and
having
> > some
> > > > issues (not ideal I know, but it's what I've got to work with for
now).
> > Here
> > > > is what I've done:
> > > >
> > > > --Create endpoint on principal instance and set recovery model
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > ALTER DATABASE AdventureWorks
> > > > SET RECOVERY FULL;
> > > > --Create endpoint on mirror instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > --Create endpoint on witness instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > GO
> > > > --Backup principal database
> > > > BACKUP DATABASE AdventureWorks
> > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > with init;
> > > > GO
> > > > --Restore mirror database
> > > > RESTORE DATABASE AdventureWorks
> > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > WITH NORECOVERY,
> > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > GO
> > > > --On the mirror server set the principal server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER => > > > 'TCP://MySQL2K5:5022'
> > > > GO
> > > > --On the principal server set the mirror server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > GO
> > > >
> > > > That last step blows up with:
> > > > Msg 1418, Level 16, State 1, Line 1
> > > > The server network address "TCP://MYSQL2K5:5023" can not be reached
or
> > does
> > > > not exist. Check the network address name and that the ports for the
> > local
> > > > and remote endpoints are operational.
> > > >
> > > > Any ideas?
> > > > TIA, ChrisR
> > > >
> > > >
> > > >
> >
> >
> >|||On
ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
you need to specify your host name and domain name NOT the SQL Server
instance name. For example, development.yourdomain.com.
Run ipconfig /all and look into host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> The box name is Development. The instance name is MySQL2K5. I have tried
> development\mysql2k5 and many variations of it and get incorrect syntax
> errors. I also tried the FQDN and still got the original error.
> Thanks for all the help.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> >
> > Let us try something else then.
> >
> > Is MYSQL2K5 the name of your computer?
> >
> > BOL recommends to use the fully qualified domain name. Try ipconfig /all
> and
> > look for host name and primary dns suffix.
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > That didn't fix it. As an FYI all 3 instances are running under the same
> > > domain account.
> > >
> > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > >
> > > > What about the security configuration? Have you granted connect
> > > permissions
> > > > to the other servers' accounts to the database mirroring endpoints?
> > > >
> > > > You should use
> > > >
> > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > >
> > > > Ben Nevarez, MCDBA, OCP
> > > > Database Administrator
> > > >
> > > >
> > > > "ChrisR" wrote:
> > > >
> > > > > SQL2K5 sp1
> > > > >
> > > > > Instance names:
> > > > >
> > > > > Development\MySQL2K5
> > > > > Development\Subscriber
> > > > > Development\Witness
> > > > >
> > > > > Im trying to set up mirroring on 3 instances on my desktop and
> having
> > > some
> > > > > issues (not ideal I know, but it's what I've got to work with for
> now).
> > > Here
> > > > > is what I've done:
> > > > >
> > > > > --Create endpoint on principal instance and set recovery model
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET RECOVERY FULL;
> > > > > --Create endpoint on mirror instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > --Create endpoint on witness instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > GO
> > > > > --Backup principal database
> > > > > BACKUP DATABASE AdventureWorks
> > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > with init;
> > > > > GO
> > > > > --Restore mirror database
> > > > > RESTORE DATABASE AdventureWorks
> > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > WITH NORECOVERY,
> > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > GO
> > > > > --On the mirror server set the principal server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
> > > > > GO
> > > > > --On the principal server set the mirror server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > GO
> > > > >
> > > > > That last step blows up with:
> > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > The server network address "TCP://MYSQL2K5:5023" can not be reached
> or
> > > does
> > > > > not exist. Check the network address name and that the ports for the
> > > local
> > > > > and remote endpoints are operational.
> > > > >
> > > > > Any ideas?
> > > > > TIA, ChrisR
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Doh! I thought it was instance name.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" can not be
reached
> > or
> > > > does
> > > > > > not exist. Check the network address name and that the ports for
the
> > > > local
> > > > > > and remote endpoints are operational.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||Thanks a lot!
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" can not be
reached
> > or
> > > > does
> > > > > > not exist. Check the network address name and that the ports for
the
> > > > local
> > > > > > and remote endpoints are operational.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >