backup on SQL2005EE

I install SQL 2005 Express Edition (upgrade from SQL 7.0 MSDE)
When I execute:
BACKUP DATABASE [Market2000] TO DISK = N'C:\PROGRA~1\MARKET~1\file.bak'
WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
I received:
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.
Processed 4504 pages for database 'Market2000', file 'Pusta_Data' on file 1.
100 percent processed.
Processed 1 pages for database 'Market2000', file 'Pusta_Log' on file 1.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror_count'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'flags'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'unicode_locale'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'unicode_compare_style'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'collation_name'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'recovery_model'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_bulk_logged_data'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_snapshot'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_single_user'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_backup_checksums'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_damaged'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'begins_log_chain'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_incomplete_metadata'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_force_offline'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_copy_only'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'first_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'last_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'fork_point_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'database_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'family_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 3009, Level 16, State 1, Line 1
Could not insert a backup or restore history/detail record in the msdb
database. This may indicate a problem with the msdb database. The
backup/restore operation was still successful.
BACKUP DATABASE successfully processed 4505 pages in 8.069 seconds (4.573
MB/sec).
What is wrong? msdb?Piotr Maciejewski (gbbsoft@.qdnet.pl) writes:
> I install SQL 2005 Express Edition (upgrade from SQL 7.0 MSDE)
> When I execute:
> BACKUP DATABASE [Market2000] TO DISK =
> N'C:\PROGRA~1\MARKET~1\file.bak'
> WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> I received:
>...
> Processed 1 pages for database 'Market2000', file 'Pusta_Log' on file 1.
> Msg 207, Level 16, State 1, Line 1
> Invalid column name 'mirror_count'.
>...
> Could not insert a backup or restore history/detail record in the msdb
> database. This may indicate a problem with the msdb database. The
> backup/restore operation was still successful.
> BACKUP DATABASE successfully processed 4505 pages in 8.069 seconds (4.573
> MB/sec).
>
> What is wrong? msdb?
Indeed. It looks as if the definition of msdb is still on SQL7 and misses
new columns added in SQL 2000 and SQL 2005. I have no idea how that could
have happened. A possible workaround could be to install a new fresh
instance of SQL 2005, and then attach the databasees to that instance.
But then you would have to migrate users from the old instance.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Uzytkownik "Erland Sommarskog" <esquel@.sommarskog.se> napisal w wiadomosci
news:Xns97077C2E3945Yazorman@.127.0.0.1...
> Indeed. It looks as if the definition of msdb is still on SQL7 and misses
> new columns added in SQL 2000 and SQL 2005. I have no idea how that could
> have happened. A possible workaround could be to install a new fresh
> instance of SQL 2005, and then attach the databasees to that instance.
> But then you would have to migrate users from the old instance.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp
>
You right.
You idea works, but it is't sollution always.
Let's look at my post on microsoft.public.sqlserver.setup called: "Re: SQL
7.0 MSDE -> SQL 2005 Express".
There is more errors (miising files in setup, don't register SQLDMO, after
register it don't want to work well) when upgrading from SQL 7.0 MSDE to SQL
2005. I think than it hadn't be tested!|||Piotr Maciejewski (gbbsoft@.qdnet.pl) writes:
> You right.
> You idea works, but it is't sollution always.
> Let's look at my post on microsoft.public.sqlserver.setup called: "Re:
> SQL 7.0 MSDE -> SQL 2005 Express". There is more errors (miising files
> in setup, don't register SQLDMO, after register it don't want to work
> well) when upgrading from SQL 7.0 MSDE to SQL 2005. I think than it
> hadn't be tested!
I didn't look at your post in .setup. (Setup issues are always so difficult
to assist with. :-(
But I did get the tip that you may have to run instmsdb.sql to fix MSDB.
I was also told that msdb was not included in MSDE 1.0 by default. This
may be why Setup ignored it. If you do SELECT * FROM sys.databases,
which dbid does msdb have?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

backup of SQL Server 2000 loading to 2005

I want to restore a backup of a SQL Server 2000 database to SQL Server 2005. Would I need to do anything after running the restore to upgrade the database?Not really. When the database is restored, it will be in SQL 2000 compatibility mode, so you will not be able to use any of the new bells and whistles. To fix that, you just run

sp_dbcmptlevel dbname, 90

Backup of SQL DB with Veritas Agents

Help!
We just upgraded to version 10d of the Veritas/Symantec software - part of
upgrade was to update the remote backup exec agent that is used to backup SQL
db's.
This is the event log entries for the job that fails.
Source MSSQL Server
Event ID 17055
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device
'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
-2147024891(Access is denied.).
---
Source Backup Exec
Event ID 57859
An error occurred while executing the following query: "BACKUP DATABASE
[master] TO virtual_device = 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
On server: "CD_PA".
SQL error number: "0BC5".
SQL error message: "Backup or restore operation terminating abnormally.
".
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
The jobs worked until we upgraded... Veritas wants me to make all these
changes... we are only running SQL7.0 no SQL 2000
Anybody have this issue...and had any luck getting it resolved withou
upgrading SQL?
Please advise.
Thanks.
-John
Citigate Cunningham HelpdeskHi
Have you checked account which is running veritas to see whether it has
privileges?
John
"Citigate Cunningham Helpdesk" wrote:
> Help!
> We just upgraded to version 10d of the Veritas/Symantec software - part of
> upgrade was to update the remote backup exec agent that is used to backup SQL
> db's.
> This is the event log entries for the job that fails.
> Source MSSQL Server
> Event ID 17055
> 18210 :
> BackupVirtualDeviceSet::Initialize: Open failure on backup device
> 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> -2147024891(Access is denied.).
>
> ---
> Source Backup Exec
> Event ID 57859
> An error occurred while executing the following query: "BACKUP DATABASE
> [master] TO virtual_device => 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> On server: "CD_PA".
> SQL error number: "0BC5".
> SQL error message: "Backup or restore operation terminating abnormally.
> ".
> For more information, click the following link:
> http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> The jobs worked until we upgraded... Veritas wants me to make all these
> changes... we are only running SQL7.0 no SQL 2000
> Anybody have this issue...and had any luck getting it resolved withou
> upgrading SQL?
> Please advise.
> Thanks.
> -John
> Citigate Cunningham Helpdesk
>|||John,
http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
Veritas has me trying renaming some of the dll's ... I did update the
Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
did not work on the NT40 box.
There were some additonal dlls that it recommended that also get copied
over... this is our finance server... and I don't want to mess it up.
Prior to the upgrade.... from 9.x to 10d it worked fine.
-John
"John Bell" wrote:
> Hi
> Have you checked account which is running veritas to see whether it has
> privileges?
> John
> "Citigate Cunningham Helpdesk" wrote:
> > Help!
> >
> > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > upgrade was to update the remote backup exec agent that is used to backup SQL
> > db's.
> >
> > This is the event log entries for the job that fails.
> >
> > Source MSSQL Server
> > Event ID 17055
> > 18210 :
> > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > -2147024891(Access is denied.).
> >
> >
> > ---
> >
> > Source Backup Exec
> > Event ID 57859
> >
> > An error occurred while executing the following query: "BACKUP DATABASE
> > [master] TO virtual_device => > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > On server: "CD_PA".
> > SQL error number: "0BC5".
> > SQL error message: "Backup or restore operation terminating abnormally.
> > ".
> >
> > For more information, click the following link:
> > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> >
> > The jobs worked until we upgraded... Veritas wants me to make all these
> > changes... we are only running SQL7.0 no SQL 2000
> >
> > Anybody have this issue...and had any luck getting it resolved withou
> > upgrading SQL?
> >
> > Please advise.
> >
> > Thanks.
> >
> > -John
> > Citigate Cunningham Helpdesk
> >|||Hi
If you have the disc space you may want to do away with the agent and just
back up to disc. Then you can schedule the normal file backup to put this
onto tape. Unless absolutly necessary I try an avoid using the agents as they
can cause so many issues like yours!
John
"Citigate Cunningham Helpdesk" wrote:
> John,
> http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
> Veritas has me trying renaming some of the dll's ... I did update the
> Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
> did not work on the NT40 box.
> There were some additonal dlls that it recommended that also get copied
> over... this is our finance server... and I don't want to mess it up.
> Prior to the upgrade.... from 9.x to 10d it worked fine.
> -John
> "John Bell" wrote:
> > Hi
> >
> > Have you checked account which is running veritas to see whether it has
> > privileges?
> >
> > John
> >
> > "Citigate Cunningham Helpdesk" wrote:
> >
> > > Help!
> > >
> > > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > > upgrade was to update the remote backup exec agent that is used to backup SQL
> > > db's.
> > >
> > > This is the event log entries for the job that fails.
> > >
> > > Source MSSQL Server
> > > Event ID 17055
> > > 18210 :
> > > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > > -2147024891(Access is denied.).
> > >
> > >
> > > ---
> > >
> > > Source Backup Exec
> > > Event ID 57859
> > >
> > > An error occurred while executing the following query: "BACKUP DATABASE
> > > [master] TO virtual_device => > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > > On server: "CD_PA".
> > > SQL error number: "0BC5".
> > > SQL error message: "Backup or restore operation terminating abnormally.
> > > ".
> > >
> > > For more information, click the following link:
> > > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> > >
> > > The jobs worked until we upgraded... Veritas wants me to make all these
> > > changes... we are only running SQL7.0 no SQL 2000
> > >
> > > Anybody have this issue...and had any luck getting it resolved withou
> > > upgrading SQL?
> > >
> > > Please advise.
> > >
> > > Thanks.
> > >
> > > -John
> > > Citigate Cunningham Helpdesk
> > >