locked
After RESTORE, 'restoring' state db RRS feed

  • Question

  • Hi,

    Primary Platform is 2012.

    SQL LOG:

    Recovery is complete. This is an informational message only. No user action is required.

    In my SSMS session RESTORE ended successfully.

    I would like to emphasize that before that RESTORE I've broken tail log backup using one RESTORE WITH REPLACE. And after that, the last one, causing this state.

    Fortunately is not live environment

    Thursday, April 21, 2016 9:44 AM

Answers

  • You never mentioned that you are configuring mirroring !

    Anyway so that's fine, you don't need to do anything else, except:

    1. Take one more T-Log backup on Primary and restore it on the secondary server with NORECOVERY & then
    2. Configure mirroring session between these two Instances


    Good Luck!
    Please Mark This As Answer if it solved your issue.
    Please Vote This As Helpful if it helps to solve your issue

    • Marked as answer by Enric Vives Thursday, April 21, 2016 10:21 AM
    Thursday, April 21, 2016 10:11 AM

All replies

  • I've applied the same RESTORE again...

    RESTORE DATABASE GFSYSTEM2 FROM DISK =N'C:\AdminSQL\GFSYSTEM.BAK'
    WITH NORECOVERY

    Processed 33968 pages for database 'GFSYSTEM2', file 'GFSYSTEM2' on file 1.
    Processed 176 pages for database 'GFSYSTEM2', file 'FL1SUPPORT' on file 1.
    Processed 1304 pages for database 'GFSYSTEM2', file 'FL2SUPPORT' on file 1.
    Processed 10344 pages for database 'GFSYSTEM2', file 'FL3SUPPORT' on file 1.
    Processed 4048 pages for database 'GFSYSTEM2', file 'FL4SUPPORT' on file 1.
    Processed 2 pages for database 'GFSYSTEM2', file 'GFSYSTEM2_log' on file 1.
    RESTORE DATABASE successfully processed 49842 pages in 97.891 seconds (3.977 MB/sec).

    And, everything remanis as usual...

    Thursday, April 21, 2016 9:50 AM
  • Just Issue this command & test:

    RESTORE DATABASE GFSSYSTEM2 WITH RECOVERY

    GO

    USE GFSSYSTEM2

    GO

    SELECT * FROM SYS.TABLES

    Basically you restored with NORECOVERY which essentially instructs database engine to expect more back-ups (Diff or T-Log) to restored. So if you are sure that this is the only backup then execute the above command to perform the recovery, use the database and execute some sample queries


    Good Luck!
    Please Mark This As Answer if it solved your issue.
    Please Vote This As Helpful if it helps to solve your issue


    • Edited by Manu Kapoor Thursday, April 21, 2016 9:58 AM
    Thursday, April 21, 2016 9:56 AM
  • Thanks Manu for the reply.

    Yes, but, I am configuring mirroring and it request to make a RESTORE WITH NORECOVERY


    • Edited by Enric Vives Thursday, April 21, 2016 10:02 AM
    Thursday, April 21, 2016 10:01 AM
  • You never mentioned that you are configuring mirroring !

    Anyway so that's fine, you don't need to do anything else, except:

    1. Take one more T-Log backup on Primary and restore it on the secondary server with NORECOVERY & then
    2. Configure mirroring session between these two Instances


    Good Luck!
    Please Mark This As Answer if it solved your issue.
    Please Vote This As Helpful if it helps to solve your issue

    • Marked as answer by Enric Vives Thursday, April 21, 2016 10:21 AM
    Thursday, April 21, 2016 10:11 AM
  • I did as you said but it did not work, anyway I've deleted the restoring database and start again.

    Now it's working properly.

    Thanks a lot,

    Thursday, April 21, 2016 10:21 AM