If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > Mirror. The remote copy of database has not been rolled forward to a point in time

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Sep 2005
Posts: 67
Mirror. The remote copy of database has not been rolled forward to a point in time

Hi All,

I'm trying to setup an SQL Server 2005 mirror, but I got the following error:
"sql server The remote copy of database has not been rolled forward to a point in time that is encompassed in the local copy of the database log"

When using a sample database (size less than 10 MB) it works, but when I use a 7 GB database, it fails.

I'm not using encryption.
I also tried to perform several log backup & restore just in case, but it doesn't work.

The only thing that may affect is that servers are in different timezones. But why does it work with a small DB and not with a 7 GB DB ?

Mirror database is restored using "norecovery" option.
It does work for 10 MB database, but does not work for a 7 GB database, which takes about 15 minutes to be restored on target instance

Any idea ?

Thanks a lot,
Diego.

Last edited by djuritz; 08-20-09 at 20:05.
Reply With Quote
  #2 (permalink)  
Old
Registered User
 
Join Date: Jul 2003
Location: San Antonio, TX
Posts: 3,634
Did you use a script to turn mirroring on, or you did it clicking through the wizard? After the last transaction log is taken on the principal, it needs to be immediately applied on the mirror, followed by turning the mirror on. If there are any transactions took place after the log was backed up and before you issued the last ALTER on the mirror, - you'll get an error. To avoid it, script the process starting with taking the last trx log backup on the principal.
__________________
"The data in a record depends on the Key to the record, the Whole Key, and
nothing but the Key, so help me Codd."
Reply With Quote
  #3 (permalink)  
Old
Registered User
 
Join Date: Sep 2005
Posts: 67
Hi, I tried using both.
I prefer to use scripts.
The only thing than may happens is that during the restore, that takes 15/20 minutes, some log backup is performed and SQL Server does not allow me to do a mirror session.

What I will do is to switch database to SINGLE_USER so that nobody can connect but me, it should work, even if it takes 24 hours, right ?
There should be a way to do a mirror for big databases.

Thanks!

Quote:
Originally Posted by rdjabarov
Did you use a script to turn mirroring on, or you did it clicking through the wizard? After the last transaction log is taken on the principal, it needs to be immediately applied on the mirror, followed by turning the mirror on. If there are any transactions took place after the log was backed up and before you issued the last ALTER on the mirror, - you'll get an error. To avoid it, script the process starting with taking the last trx log backup on the principal.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On