Post reply

the original database is fine, but restoring database has consistency errors?.

  • October 24, 2019 at 1:04 pm

    #3691605

    Hello,

     

    We have a client in another country, I have asked them to send me the full backup in a usb, and upload ongoing log files via SFTP, something weird is, every time I restored the full backup, the log restore will fail at some point, I asked them to resend new full backup, after 3 times, I think there is something wrong windows 10 1809 rather than log file.

    So I restored the full backup, bring it online, run dbcc checkdb(dbname), then I got consistency errors in database, but from customer side, dbcc checkdb doesn't return any errors, there is no faulty hardwares in client server.

    1) All log files are valid

    2) Database file is valid

    Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.

    The path specified by "D:\Data\XXXYYY_Data.mdf" is not in a valid directory.

    Directory lookup for the file "E:\Log\XXXYYY_Log.ldf" failed with the operating system error 3(The system cannot find the path specified.).

    The backup set on file 1 is valid.

    3)

    DBCC CHECKDB WITH NO_INFOMSGS;

    GO

    CHECKDB found 0 allocation errors and 12 consistency errors in table 'XXX' (object ID 822747596).

    CHECKDB found 0 allocation errors and 19 consistency errors in database 'XXXYYY'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (XXXYYY).

    4) SELECT * FROM msdb..suspect_pages

    43 1 3202572

    2 10 2015-05-15 12:07:30.907

    43 1 3202573

    2 10 2015-05-15 12:07:30.910

    43 1 1050913

    2 10 2015-05-15 12:13:57.347

    43 1 4827952

    2 10 2015-05-15 12:14:04.203

    client is running on

    Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)

     

    thanks

    iosman

    • This topic was modified 5 years ago by  iosman123.

  • October 24, 2019 at 2:28 pm

    #3691637

    from the message "cannot find the path/ this is not a valid directory"

    i'd suggest scripting up the restore and running it one file at a time.

    it might be that your disk controllers or network bandwidth cant handle the stress of restoring the files

    possibly the files aren't 100% copied via sftp and you have a partial copy (I get that all the time using file watcher service)

    my advice - slow the process down, add as much logging as you can - then if you find a failure, re-do the process exactly as you did before. see if it changes

    MVDBA

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply