SQL SERVER – Database Mirroring. Error: 1475, Error: 1478, Error: 1412.

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!!



10 comentarios:

Rafa dijo...

ja that's how usually made mirroring but still doesn't works and it's the only database that send me this error 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)

Anónimo dijo...

Thanks for sharing Victor. Had this exact issue!

- Seán

Macrosoft dijo...

Nice to know more details about database mirroring

convert foxpro code to sql
convert visual foxpro database to sql
foxpro database to sql server
import dbf file into sql server

Crypto Phone Support dijo...

How to resolve the problem of delay in the withdrawal of digital currency in Bithumb? Withdrawal errors are out of control of the users as they occur abruptly. If you need assistance to resolve those errors, you can directly call on Bithumb Support Number at 1-800-665-6722 and avail all the services and resolutions from the advisors that are required in fixing the error. Or, you can also send your queries to the team via email or chat box.Visit website:-http://www.cryptophonesupport.com/exchange/bithumb

Anónimo dijo...

smm panel
SMM PANEL
İs İlanlari
instagram takipçi satın al
hırdavatçı
HTTPS://WWW.BEYAZESYATEKNİKSERVİSİ.COM.TR
Servis
Tiktok Jeton Hilesi İndir

Anónimo dijo...

ataşehir lg klima servisi
ümraniye alarko carrier klima servisi
kartal daikin klima servisi
ümraniye daikin klima servisi
üsküdar toshiba klima servisi
beykoz beko klima servisi
üsküdar beko klima servisi
pendik lg klima servisi
çekmeköy vestel klima servisi

vbet dijo...

Good content. You write beautiful things.
taksi
mrbahis
hacklink
korsan taksi
sportsbet
hacklink
mrbahis
sportsbet
vbet

bonus veren siteler dijo...

Good text Write good content success. Thank you
kralbet
slot siteleri
kibris bahis siteleri
tipobet
betpark
betmatik
poker siteleri
mobil ödeme bahis

Anónimo dijo...

شركة جلي بلاط بجدة
شركة صيانة افران بمكة

bade dijo...

mecidiyeköy
sakarya
istanbul
kayseri
ordu

T1K

Publicar un comentario