Restore Problem

Hi Guys:
I am restoring a databse backup from sql server 2000 cluster to another
server. The restore has been failing with message "RESTORE DATABASE is
terminating abnormally.". When I use restore verify, i get the following
message. Backup is being done on sql server 200 cluster, I am restoring on
another server which is not a cluster. Any help is greatly appreciated
because this is critical and urgent.
Server: Msg 3242, Level 16, State 2, Line 1
The file on device 'C:\temp\LancomeSIS_US_db_200603240243.BAK' is not a
valid Microsoft Tape Format backup set.
Server: Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
Thanks
Are you on Windows 2003?
> Hi Guys:
> I am restoring a databse backup from sql server 2000 cluster to another
> server. The restore has been failing with message "RESTORE DATABASE is
> terminating abnormally.". When I use restore verify, i get the following
> message. Backup is being done on sql server 200 cluster, I am restoring on
> another server which is not a cluster. Any help is greatly appreciated
> because this is critical and urgent.
>
> Server: Msg 3242, Level 16, State 2, Line 1
> The file on device 'C:\temp\LancomeSIS_US_db_200603240243.BAK' is not a
> valid Microsoft Tape Format backup set.
> Server: Msg 3013, Level 16, State 1, Line 1
> VERIFY DATABASE is terminating abnormally.
>
> Thanks
|||could you paste the output of restore headeronly
|||looks like your backup is corrupted, not sure of yet!
|||Thanks for replying. Below is the output of the Restore HeaderOnly. Looks
looks like db is corrupt but why. is it something to do with backups
happening on cluster (Raid drive).
BackupName
BackupDescription
BackupType ExpirationDate Compressed
Position DeviceType UserName
ServerName
DatabaseName
DatabaseVersion DatabaseCreationDate
BackupSize FirstLsn LastLsn
CheckpointLsn DifferentialBaseLsn
BackupStartDate BackupFinishDate
SortOrder CodePage UnicodeLocaleId
UnicodeComparisonStyle CompatibilityLevel SoftwareVendorId
SoftwareVersionMajor SoftwareVersionMinor SoftwareVersionBuild MachineName
Flags BindingId
RecoveryForkId Collation
------
-----------
-- --- --
-- --
------
------
------
-- ---
-- --
-- --
--- -- --
-- -- -- --
-- -- --
------
-- ---
------
*** INCOMPLETE ***
NULL
NULL NULL NULL
1 NULL NULL
NULL
NULL
NULL NULL
NULL NULL NULL
NULL NULL NULL
NULL
NULL NULL NULL NULL
NULL NULL NULL NULL
NULL NULL
NULL NULL NULL
NULL
"Shadow" wrote:

> looks like your backup is corrupted, not sure of yet!
>

Restore Problem

Hi Guys:
I am restoring a databse backup from sql server 2000 cluster to another
server. The restore has been failing with message "RESTORE DATABASE is
terminating abnormally.". When I use restore verify, i get the following
message. Backup is being done on sql server 200 cluster, I am restoring on
another server which is not a cluster. Any help is greatly appreciated
because this is critical and urgent.
Server: Msg 3242, Level 16, State 2, Line 1
The file on device 'C:\temp\LancomeSIS_US_db_200603240243.BAK' is not a
valid Microsoft Tape Format backup set.
Server: Msg 3013, Level 16, State 1, Line 1
VERIFY DATABASE is terminating abnormally.
ThanksAre you on Windows 2003?
> Hi Guys:
> I am restoring a databse backup from sql server 2000 cluster to another
> server. The restore has been failing with message "RESTORE DATABASE is
> terminating abnormally.". When I use restore verify, i get the following
> message. Backup is being done on sql server 200 cluster, I am restoring o
n
> another server which is not a cluster. Any help is greatly appreciated
> because this is critical and urgent.
>
> Server: Msg 3242, Level 16, State 2, Line 1
> The file on device 'C:\temp\LancomeSIS_US_db_200603240243.BAK' is not a
> valid Microsoft Tape Format backup set.
> Server: Msg 3013, Level 16, State 1, Line 1
> VERIFY DATABASE is terminating abnormally.
>
> Thanks|||could you paste the output of restore headeronly|||looks like your backup is corrupted, not sure of yet!|||Thanks for replying. Below is the output of the Restore HeaderOnly. Looks
looks like db is corrupt but why. is it something to do with backups
happening on cluster (Raid drive).
BackupName
BackupDescription
BackupType ExpirationDate Compressed
Position DeviceType UserName
ServerName
DatabaseName
DatabaseVersion DatabaseCreationDate
BackupSize FirstLsn LastLsn
CheckpointLsn DifferentialBaseLsn
BackupStartDate BackupFinishDate
SortOrder CodePage UnicodeLocaleId
UnicodeComparisonStyle CompatibilityLevel SoftwareVendorId
SoftwareVersionMajor SoftwareVersionMinor SoftwareVersionBuild MachineName
Flags BindingId
RecoveryForkId Collation
----
----
----
----
----
--
-- --- --
-- --
----
----
----
----
----
----
-- ---
-- --
-- --
--
---
--- -- --
-- -- -- --
-- -- --
----
----
-- ---
---
----
----
*** INCOMPLETE ***
NULL
NULL NULL NULL
1 NULL NULL
NULL
NULL
NULL NULL
NULL NULL NULL
NULL NULL NULL
NULL
NULL NULL NULL NULL
NULL NULL NULL NULL
NULL NULL
NULL NULL NULL
NULL
"Shadow" wrote:

> looks like your backup is corrupted, not sure of yet!
>

Restore of master

Tomorrow we are updating a server from 7.0 to 2000 w/
these steps:
1. I am copying the user databases off onto another
server.
2. We'll uninstall 7.0.
3. We'll install Sql Server 2000.
4. We'll copy the user databases back and let the upgrade
happen "on the fly".
My question: how do I restore the master and/or msdb
database? Of course I can make a backup but it will be a
7.0 backup. Is it as simple as doing a restore of the
master from the masterxxx.bak file that is 7.0?You cannot restore system databases across version, most time not even
across service packs. To automate the info in the system databases, you need
to let the install program update the 7.0 install to 2000.
So, you have to consider each piece of information in the system databases
and what you want to bring over and what you can do automatically. One way
is to study the system tables and from there create a list of what is stored
in the system databases and how to bring that over (and whether you can
"re-type" of want to automate). The main things are usually (I probably
forget some stuff, been away for a month):
Master:
Logins
Linked servers
Backupdevices
Msdb:
Jobs
Alerts
And don't forget model, if you've done any changes to it.
Post back if you want to know more about a certain topic.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:292501c3e113$52350320$a501280a@.phx.gbl...

quote:

---

> Tomorrow we are updating a server from 7.0 to 2000 w/
> these steps:
> 1. I am copying the user databases off onto another
> server.
> 2. We'll uninstall 7.0.
> 3. We'll install Sql Server 2000.
> 4. We'll copy the user databases back and let the upgrade
> happen "on the fly".
> My question: how do I restore the master and/or msdb
> database? Of course I can make a backup but it will be a
> 7.0 backup. Is it as simple as doing a restore of the
> master from the masterxxx.bak file that is 7.0?

---

|||What you outlined below was exactly what I was planning
on, because I have a certain amount of concern over
letting sql server do the upgrade. I've seen small
problems with upgrades on the client tools and so I've
never felt comfortable with an upgrade of sql server
itself.
Do you agree with my assessment? Isn't it always better
to do a fresh install if at all possible?

quote:

---

>--Original Message--
>You cannot restore system databases across version, most

---

time not even

quote:

---

>across service packs. To automate the info in the system

---

databases, you need

quote:

---

>to let the install program update the 7.0 install to 2000.
>So, you have to consider each piece of information in the

---

system databases

quote:

---

>and what you want to bring over and what you can do

---

automatically. One way

quote:

---

>is to study the system tables and from there create a

---

list of what is stored

quote:

---

>in the system databases and how to bring that over (and

---

whether you can

quote:

---

>"re-type" of want to automate). The main things are

---

usually (I probably

quote:

---

>forget some stuff, been away for a month):
>Master:
>Logins
>Linked servers
>Backupdevices
>Msdb:
>Jobs
>Alerts
>And don't forget model, if you've done any changes to it.
>Post back if you want to know more about a certain topic.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?

---

oi=djq&as_ugroup=microsoft.public.sqlserver

quote:

---

>
>"SSB" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:292501c3e113$52350320$a501280a@.phx.gbl...
upgrade[QUOTE]
a[QUOTE]
>
>.
>

---

|||Yes, I generally prefer fresh installations over upgrades. However, if you
have a more complex installation (again, regarding the stuff in your system
databases), then the effort to bring that over is an issue to weigh in, of
course. Also, another factor is how familiar you are with what is in the
system databases and how to copy or re-cerate that info.
In many cases, I prefer fresh install over upgrades for SQL Server as well.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"SSB" <anonymous@.discussions.microsoft.com> wrote in message
news:2a8b01c3e12b$6bf07570$a401280a@.phx.gbl...[QUOTE]
> What you outlined below was exactly what I was planning
> on, because I have a certain amount of concern over
> letting sql server do the upgrade. I've seen small
> problems with upgrades on the client tools and so I've
> never felt comfortable with an upgrade of sql server
> itself.
> Do you agree with my assessment? Isn't it always better
> to do a fresh install if at all possible?
>
> time not even
> databases, you need
> system databases
> automatically. One way
> list of what is stored
> whether you can
> usually (I probably
> oi=djq&as_ugroup=microsoft.public.sqlserver
> message
> upgrade
> a