database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a
work around, but they want to know what the root cause was.
Problem description
It seems that they had disk problems, then wanted to restore the database fr
om a backup. They were not doing backups to disk, just to shutting down the
services & doing a cold NT backup to tape.
Error Details
The server lost a disc (one of five from RAID5 array). After it was fixed,
the data was restored from a backup tape and the following appeared in the S
QL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_D
ata.NDF' is not a valid database file header. The PageAudit property is inco
rrect.
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file n
ame 'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
System Details
SQL Server 7
NT 4
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
4 * PIII 700 Mhz
2 GB RAM
40/80GB SCSI DLT Internal Tape Drive
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
Regards
DavidDavid,
This scenario is a typical case why you should do backup using SQL Server BA
CKUP command instead of just
picking up the physical files. In general, it should work assuming that you
indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a ca
se with MS Support for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work a
round, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a b
ackup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.[
vbcol=seagreen]
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the da
ta was restored from a[/vbcol]
backup tape and the following appeared in the SQL Server activity log. The database was in s
uspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF
.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.ND
F.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.ND
F' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name[/v
bcol]
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.[vbcol=seagreen]
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF
.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David