SQL SERVER � Database Mirroring. Error: 1475, Error: 1478, Error: 1412. | Backup Server Tips

Problem.

When a database mirroring is configured, some error messages are not completely clear when we got it. The following errors are typical while a database mirroring configuration is performed:

Database Mirroring cannot be enabled because the database may have bulk logged changes that have not been backed up. The last log backup on the principal must be restored on the mirror. (Microsoft SQL Server, Error 1475)

The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been restored on the mirror database. (Microsoft SQL Server, Error 1478)

The remote copy of database has not been rolled forwarded to a point in time that is encompassed in the local copy of the transactional log. . (Microsoft SQL Server, Error 1412)

I got the error mentioned above when I try to start the synchronization for database mirroring.

Solution / Fix / Workaround.

To start the synchronization successfully follow the next steps:

1. Principal Instance - Take a full backup and a log backup as well

2. Copy the full/log backups from Principal Instance to Mirror instance

3. Mirror Instance - Restore with NORECOVERY option the full backup

4. Mirror Instance � Apply the log backup

5. Principal Instance - Start synchronization

Enjoy!!

SQL SERVER - Error: 1418. The server network address can not be reached or does not exist. Check the network address name and that the ports for the l | Backup Server Tips

Problem.

During the past days I was working in a Database Mirroring Configuration and one of the errors I got was the following:

Msg 1418, Level 16, State 1, Line 1

The server network address "%.*ls" 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.

It was presented when I run the command:

ALTER DATABASE TestMirror SET PARTNER = 'TCP://hostname:5050'

The server network endpoint did not respond because the specified server network address cannot be reached or does not exist.

Solution.

To solution my problem, I accomplished the following points:

1. The ENDPOINTS should have the status started.

select state_desc from sys.database_mirroring_endpoints

2. The system should not be behind a firewall.

3. Make sure that the principal server instance and mirror instance are listening on the right ports and whether are available.

4. Name pipes protocol enabled.

5. The same username and password were used to run SQL Server services on both machines.

6. The usernames to run SQL Server services have NT Auth Access between both machines.

7. Make sure that the username for the SQL Server services has rights on the SQL Server instance.