Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Restore of db fails


Restore of db fails

Author
Message
HanShi
HanShi
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3051 Visits: 3633
Markus (7/25/2014)
We restored the db from the NAS backup to the NAS device just fine. I then tried to backup the db to local disk then restore it. The restore failed....

Did you run a CHECKDB on the database when you restored in to the NAS device?

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
I am going to do that next. Right now I am importing all of the data from the NAS based database into a new database on our storage. Once that is complete I will run a CHECKDB.



Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
I am seeing a few of these making me think there is either corruption or just the internal pointers are off and running an UPDATE USEAGE is in order.


A read of the file 'xxxxxxxxx.mdf' at offset 0x00008b44ff0000 succeeded after failing 1 time(s) with error: incorrect checksum (expected: 0xe3d07596; actual: 0x41d07796). Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB).



Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
arnipetursson (7/25/2014)
Have you tried to restore it with replace?
Sounds like the issue might be with the existing database you were trying to restore to.


Yes, tried the REPLACE and also tried to restore it as a new database. Same error no matter what.



SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21133 Visits: 18259
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
SQLRNNR (7/30/2014)
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.


I will ask about encryption... I know they are on SQL2008R2 SP2 and we are on SP1.



SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21133 Visits: 18259
Markus (7/30/2014)
SQLRNNR (7/30/2014)
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.


I will ask about encryption... I know they are on SQL2008R2 SP2 and we are on SP1.


Both of those would be issues.

If they are using TDE, you will not be able to restore that backup without the certificate they used to encrypt the database.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
SQLRNNR (7/30/2014)
Markus (7/30/2014)
SQLRNNR (7/30/2014)
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.


I will ask about encryption... I know they are on SQL2008R2 SP2 and we are on SP1.


Both of those would be issues.

If they are using TDE, you will not be able to restore that backup without the certificate they used to encrypt the database.


I have never had a service pack difference be an issue with restoring a database.

TDE.... Understand... however....

I have successfully restored their backup TO the NAS device... so... makes me think both of these are not factors.



SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21133 Visits: 18259
Markus (7/30/2014)
SQLRNNR (7/30/2014)
Markus (7/30/2014)
SQLRNNR (7/30/2014)
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.


I will ask about encryption... I know they are on SQL2008R2 SP2 and we are on SP1.


Both of those would be issues.

If they are using TDE, you will not be able to restore that backup without the certificate they used to encrypt the database.


I have never had a service pack difference be an issue with restoring a database.

TDE.... Understand... however....

I have successfully restored their backup TO the NAS device... so... makes me think both of these are not factors.


When you say you restored it to the NAS device, what do you mean? You were able to place the backup file on the NAS device, or you restored the database into a SQL Server instance that accesses the NAS device for storage?



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Markus
Markus
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1587 Visits: 3680
SQLRNNR (7/30/2014)
Markus (7/30/2014)
SQLRNNR (7/30/2014)
Markus (7/30/2014)
SQLRNNR (7/30/2014)
The database that they provided, was it enabled for encryption by chance? It is worth checking with the vendor if their database is TDE enabled.


Also worth comparing with them if the database version (down to CU) is exactly the same as yours.


I will ask about encryption... I know they are on SQL2008R2 SP2 and we are on SP1.


Both of those would be issues.

If they are using TDE, you will not be able to restore that backup without the certificate they used to encrypt the database.


I have never had a service pack difference be an issue with restoring a database.

TDE.... Understand... however....

I have successfully restored their backup TO the NAS device... so... makes me think both of these are not factors.


When you say you restored it to the NAS device, what do you mean? You were able to place the backup file on the NAS device, or you restored the database into a SQL Server instance that accesses the NAS device for storage?


Yes. We cannot restore from the NAS backup to our back end storage. I have also tried to take a backup of the NAS live database and restore it to our storage and it fails. That is what is bizzare.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search