restore db from 32 to 64 bit sql2005

Henrik Staun Poulsen

I'm trying to restore a db from a 32 bit SQL 2005 server to a new blank SQL 2005 64bit server.
It fails with this error:

SQL Server error

server: Msg 3013
REstore database is terminating abnormally
Server: Msg 3203
Read on "SQLBackup_quid" failed:
995(error not found)

SQL Backup exit cod: 1100
SQL error code: 3203

What do I do wrong?
Best regards
Henrik Staun Poulsen

petey

What is the result if you restore only the file list from the backup file e.g.

master..sqlbackup '-sql "RESTORE FILELISTONLY FROM DISK = [...] " '

Henrik Staun Poulsen

vdc_Data \VDB\vdc_Data.MDF D PRIMARY 172974669824 35184372080640
vdc_Log \VDB\vdc_Log.LDF L NULL 41546612736 35184372080640

petey

Could you pls restore the header only e.g.

master..sqlbackup '-sql "RESTORE HEADERONLY FROM DISK = [...] " '

This will test if the backup file is valid.

Henrik Staun Poulsen

I've tried doing a headeronly, but I had to chose a new file, because the older one was deleted. Please find it enclosed.

I have since learned that there is something wrong with the SAN that this new SQL Server is running on. It is awfully slow. Could this be the problem?

Best regards
Henrik

Reading file header of "\\dkrdsvdc02\f$\vdcbackup\FULL_(local)_VDC_20070115_200002.sqb"

Backup name : Database (VDC), 15-01-2007 20:00:02
Description : Backup on 15-01-2007 20:00:02 Server: DKRDSVDC02 Database: VDC
Backup type : 1 (Database)
User name : VESTAS\SVC-DK-VDC
Backup start : 15-01-2007 20:00:05
Backup finish: 15-01-2007 20:55:41

Server name : DKRDSVDC02
Database name : VDC
Database version : 611
Creation date : 17-05-2006 14:13:50
Size : 1,952 GB
Sort order : 0
Code page : 0
Machine name : DKRDSVDC02
Collation : Danish_Norwegian_CI_AS

First LSN : 116780000000080700100
Last LSN : 116780000000084900001
Checkpoint LSN : 116780000000080700100
Differential base LSN :

and

exitcode 0
sqlerrorcode 0
filename01 \\dkrdsvdc02\f$\vdcbackup\FULL_(local)_VDC_20070115_200002.sqb

petey

Since no errors were returned, could you pls try restoring this file?

A slow SAN would not cause the original error, but a faulty SAN would.

Henrik Staun Poulsen

It looks like a faulty SAN.
I think we can close this case as nothing will work on a defect disk system.

Sorry to disturb you, and thank you for your help.

Best regards
Henrik