I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.
What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' and
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fine
> before.
> Any kind of help is greatly appreciated.
|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
[vbcol=seagreen]
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
|||Specify a report file for the maint plan and check the report file for the error messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...[vbcol=seagreen]
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Thursday, March 29, 2012
Backup Failure - Delete old files
I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' and
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fine
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
> > I have setup my backup job to delete file older than 12 hours. I want to
> > keep atleast 2 backup files saved. The backup runs every night.
> > My backup job fails on alternate days.
> >
> > The day it fails, it completes just 2 steps 'backup database' and 'verify
> > database'.
> >
> > The day is completes sucessfully, it completes 4 steps 'backup database' and
> > 'verify database' and 'delete old backup files' and 'check data and index
> > linkage'.
> >
> > It started failing for last few months. The same setting used to work fine
> > before.
> >
> > Any kind of help is greatly appreciated.|||Specify a report file for the maint plan and check the report file for the error messages.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>> What is the error message you get at 3rd step?
>>
>> "helpplease" wrote:
>> > I have setup my backup job to delete file older than 12 hours. I want to
>> > keep atleast 2 backup files saved. The backup runs every night.
>> > My backup job fails on alternate days.
>> >
>> > The day it fails, it completes just 2 steps 'backup database' and 'verify
>> > database'.
>> >
>> > The day is completes sucessfully, it completes 4 steps 'backup database' and
>> > 'verify database' and 'delete old backup files' and 'check data and index
>> > linkage'.
>> >
>> > It started failing for last few months. The same setting used to work fine
>> > before.
>> >
>> > Any kind of help is greatly appreciated.
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' and
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fine
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
> > I have setup my backup job to delete file older than 12 hours. I want to
> > keep atleast 2 backup files saved. The backup runs every night.
> > My backup job fails on alternate days.
> >
> > The day it fails, it completes just 2 steps 'backup database' and 'verify
> > database'.
> >
> > The day is completes sucessfully, it completes 4 steps 'backup database' and
> > 'verify database' and 'delete old backup files' and 'check data and index
> > linkage'.
> >
> > It started failing for last few months. The same setting used to work fine
> > before.
> >
> > Any kind of help is greatly appreciated.|||Specify a report file for the maint plan and check the report file for the error messages.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>> What is the error message you get at 3rd step?
>>
>> "helpplease" wrote:
>> > I have setup my backup job to delete file older than 12 hours. I want to
>> > keep atleast 2 backup files saved. The backup runs every night.
>> > My backup job fails on alternate days.
>> >
>> > The day it fails, it completes just 2 steps 'backup database' and 'verify
>> > database'.
>> >
>> > The day is completes sucessfully, it completes 4 steps 'backup database' and
>> > 'verify database' and 'delete old backup files' and 'check data and index
>> > linkage'.
>> >
>> > It started failing for last few months. The same setting used to work fine
>> > before.
>> >
>> > Any kind of help is greatly appreciated.
Backup Failure - Delete old files
I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' a
nd
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fin
e
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
[vbcol=seagreen]
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
>|||Specify a report file for the maint plan and check the report file for the e
rror messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...[vbcol=seagreen]
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on
:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' a
nd
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fin
e
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
[vbcol=seagreen]
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
>|||Specify a report file for the maint plan and check the report file for the e
rror messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...[vbcol=seagreen]
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on
:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>
Sunday, March 25, 2012
Backup everything except data
We have a SQL2000 database that is created via a dump from a third party
product. Being as this dump runs every day, we don't need to back up the
data. However we need the schema, views, triggers, etc. Everything except
the actual data in the tables. Is there a way to make a backup of this?
Thanks!
BrianYes, use some tool that generates DDL script for the database:
http://www.karaszi.com/SQLServer/info_generate_script.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Brian" <me@.here.there> wrote in message news:O%2323gnK8HHA.484@.TK2MSFTNGP06.phx.gbl...
> We have a SQL2000 database that is created via a dump from a third party product. Being as this
> dump runs every day, we don't need to back up the data. However we need the schema, views,
> triggers, etc. Everything except the actual data in the tables. Is there a way to make a backup of
> this?
> Thanks!
> Brian
>
product. Being as this dump runs every day, we don't need to back up the
data. However we need the schema, views, triggers, etc. Everything except
the actual data in the tables. Is there a way to make a backup of this?
Thanks!
BrianYes, use some tool that generates DDL script for the database:
http://www.karaszi.com/SQLServer/info_generate_script.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Brian" <me@.here.there> wrote in message news:O%2323gnK8HHA.484@.TK2MSFTNGP06.phx.gbl...
> We have a SQL2000 database that is created via a dump from a third party product. Being as this
> dump runs every day, we don't need to back up the data. However we need the schema, views,
> triggers, etc. Everything except the actual data in the tables. Is there a way to make a backup of
> this?
> Thanks!
> Brian
>
Tuesday, March 20, 2012
Backup Device error or device off-line.
I received the error message listed below when the SQL
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.
Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.
Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Backup Device error or device off-line.
I received the error message listed below when the SQL
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx
.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx
.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Backup Device error or device off-line.
I received the error message listed below when the SQL
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>
Monday, March 19, 2012
Backup Database Maintenance Plan eats up too much disk space
I created a basic DB maintenance plan to routinely backup our database.
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove
files
than
Run through the maint wiz again and you will find just that option :-).
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
name,
files
than
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...
http://groups.google.com/groups?oi=...ublic.sqlserver
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove
quote:
> the older backup files. Is there an automated way to have SQL delete
files
quote:
> older than a given number of days - for example, remove all files older
than
quote:
> 3 days.
Run through the maint wiz again and you will find just that option :-).
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
quote:
> I created a basic DB maintenance plan to routinely backup our database.
> Every backup job that runs through this plan is created using a unique
name,
quote:
> putting the date into the back file name, as in
> DBProduction_db_200401120000.bak.
> The problem is this creates a new backup file each day - our backups our
> faily large and after only a few days, the drive space is completely used
> up.
> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
quote:
> older than a given number of days - for example, remove all files older
than
quote:|||D-oh! I feel so stupid...
> 3 days. When we do a log ship using a maintenance plan, it asks for this
> information, but I haven't seen it when just running basic back ups and
> transaction log back ups.
> What about changing the default name to something like 'DailyDBBackup.bak'
> so that it just overwrites previous backup everytime?
>
>
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...
quote:
remove[QUOTE]
> files
> than
> Run through the maint wiz again and you will find just that option :-).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=...ublic.sqlserver
quote:
>
> "Dave Slinn" <dslinn@.gms.ca> wrote in message
> news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> name,
used[QUOTE]
remove[QUOTE]
> files
> than
this[QUOTE]
'DailyDBBackup.bak'[QUOTE]
>
Backup Database Maintenance Plan eats up too much disk space
I created a basic DB maintenance plan to routinely backup our database.
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days.
Run through the maint wiz again and you will find just that option :-).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> I created a basic DB maintenance plan to routinely backup our database.
> Every backup job that runs through this plan is created using a unique
name,
> putting the date into the back file name, as in
> DBProduction_db_200401120000.bak.
> The problem is this creates a new backup file each day - our backups our
> faily large and after only a few days, the drive space is completely used
> up.
> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days. When we do a log ship using a maintenance plan, it asks for this
> information, but I haven't seen it when just running basic back ups and
> transaction log back ups.
> What about changing the default name to something like 'DailyDBBackup.bak'
> so that it just overwrites previous backup everytime?
>
>|||D-oh! I feel so stupid...
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days.
> Run through the maint wiz again and you will find just that option :-).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Dave Slinn" <dslinn@.gms.ca> wrote in message
> news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> > I created a basic DB maintenance plan to routinely backup our database.
> > Every backup job that runs through this plan is created using a unique
> name,
> > putting the date into the back file name, as in
> > DBProduction_db_200401120000.bak.
> >
> > The problem is this creates a new backup file each day - our backups our
> > faily large and after only a few days, the drive space is completely
used
> > up.
> >
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days. When we do a log ship using a maintenance plan, it asks for
this
> > information, but I haven't seen it when just running basic back ups and
> > transaction log back ups.
> >
> > What about changing the default name to something like
'DailyDBBackup.bak'
> > so that it just overwrites previous backup everytime?
> >
> >
> >
>
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days.
Run through the maint wiz again and you will find just that option :-).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> I created a basic DB maintenance plan to routinely backup our database.
> Every backup job that runs through this plan is created using a unique
name,
> putting the date into the back file name, as in
> DBProduction_db_200401120000.bak.
> The problem is this creates a new backup file each day - our backups our
> faily large and after only a few days, the drive space is completely used
> up.
> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days. When we do a log ship using a maintenance plan, it asks for this
> information, but I haven't seen it when just running basic back ups and
> transaction log back ups.
> What about changing the default name to something like 'DailyDBBackup.bak'
> so that it just overwrites previous backup everytime?
>
>|||D-oh! I feel so stupid...
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days.
> Run through the maint wiz again and you will find just that option :-).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Dave Slinn" <dslinn@.gms.ca> wrote in message
> news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> > I created a basic DB maintenance plan to routinely backup our database.
> > Every backup job that runs through this plan is created using a unique
> name,
> > putting the date into the back file name, as in
> > DBProduction_db_200401120000.bak.
> >
> > The problem is this creates a new backup file each day - our backups our
> > faily large and after only a few days, the drive space is completely
used
> > up.
> >
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days. When we do a log ship using a maintenance plan, it asks for
this
> > information, but I haven't seen it when just running basic back ups and
> > transaction log back ups.
> >
> > What about changing the default name to something like
'DailyDBBackup.bak'
> > so that it just overwrites previous backup everytime?
> >
> >
> >
>
Sunday, March 11, 2012
backup 'creep'
SQL runs on a clustered server and during the week the time it takes for the
transactional backup slowly increases, and as it does it takes the majority
of the system resources. the backup is sent to a drive on a remote system.
In cluster admin if i take the service off-line and then back on-line it's
back to running fast again. THe transactional backups take ~1minute after a
off/on line and work their way to 7/8 minutes.
any suggestions?
Richard
Are you using any third part tools to do the backup? What is your memory
configuration like?
Andrew J. Kelly SQL MVP
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
> SQL runs on a clustered server and during the week the time it takes for
> the
> transactional backup slowly increases, and as it does it takes the
> majority
> of the system resources. the backup is sent to a drive on a remote
> system.
> In cluster admin if i take the service off-line and then back on-line it's
> back to running fast again. THe transactional backups take ~1minute after
> a
> off/on line and work their way to 7/8 minutes.
> any suggestions?
> --
> Richard
|||pretty standard maintainence plan from w/in SQL server; Agent; doing
transaction backups every 2 hours;
2gb memory on server; letting SQL manage it's memory desires
"Andrew J. Kelly" wrote:
> Are you using any third part tools to do the backup? What is your memory
> configuration like?
> --
> Andrew J. Kelly SQL MVP
>
> "Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
> news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
>
>
|||Have you looked to see if you are doing any paging at the OS level and if
this increases when the log file time increases? Are you running any other
apps on this server? it almost sounds like you have a memory leak
somewhere. While this is rare these days it does happen, especially if you
are running xp's or dlls outside of sql server. Anything with XML by any
chance?
Andrew J. Kelly SQL MVP
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:65EFE346-1F7F-4036-B60A-1C939C19EC89@.microsoft.com...[vbcol=seagreen]
> pretty standard maintainence plan from w/in SQL server; Agent; doing
> transaction backups every 2 hours;
> 2gb memory on server; letting SQL manage it's memory desires
> "Andrew J. Kelly" wrote:
|||You might also want to have a look at
FIX: Performance decreases over time when you back up files in SQL Server
2000
http://support.microsoft.com/?kbid=824430
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
> SQL runs on a clustered server and during the week the time it takes for
> the
> transactional backup slowly increases, and as it does it takes the
> majority
> of the system resources. the backup is sent to a drive on a remote
> system.
> In cluster admin if i take the service off-line and then back on-line it's
> back to running fast again. THe transactional backups take ~1minute after
> a
> off/on line and work their way to 7/8 minutes.
> any suggestions?
> --
> Richard
|||Thanks Jasper. I was sure there was a KB on that but i could not find it
for some reason. I couldn't remember the exact reasons but remembered there
was a KB related to this.
Andrew J. Kelly SQL MVP
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ORb9sAxAFHA.3016@.tk2msftngp13.phx.gbl...
> You might also want to have a look at
> FIX: Performance decreases over time when you back up files in SQL Server
> 2000
> http://support.microsoft.com/?kbid=824430
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
> news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
>
|||I also remember a KB, and it was nearly two years ago. The long and the
short was run your backups locally, then use a script to "transfer" to the
remote storage. That way SQL Server does not have to handle the file
detatils in keeping a remote connection alive.
Larry
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23p08tGxAFHA.1392@.tk2msftngp13.phx.gbl...
> Thanks Jasper. I was sure there was a KB on that but i could not find it
> for some reason. I couldn't remember the exact reasons but remembered
> there was a KB related to this.
> --
> Andrew J. Kelly SQL MVP
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:ORb9sAxAFHA.3016@.tk2msftngp13.phx.gbl...
>
transactional backup slowly increases, and as it does it takes the majority
of the system resources. the backup is sent to a drive on a remote system.
In cluster admin if i take the service off-line and then back on-line it's
back to running fast again. THe transactional backups take ~1minute after a
off/on line and work their way to 7/8 minutes.
any suggestions?
Richard
Are you using any third part tools to do the backup? What is your memory
configuration like?
Andrew J. Kelly SQL MVP
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
> SQL runs on a clustered server and during the week the time it takes for
> the
> transactional backup slowly increases, and as it does it takes the
> majority
> of the system resources. the backup is sent to a drive on a remote
> system.
> In cluster admin if i take the service off-line and then back on-line it's
> back to running fast again. THe transactional backups take ~1minute after
> a
> off/on line and work their way to 7/8 minutes.
> any suggestions?
> --
> Richard
|||pretty standard maintainence plan from w/in SQL server; Agent; doing
transaction backups every 2 hours;
2gb memory on server; letting SQL manage it's memory desires
"Andrew J. Kelly" wrote:
> Are you using any third part tools to do the backup? What is your memory
> configuration like?
> --
> Andrew J. Kelly SQL MVP
>
> "Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
> news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
>
>
|||Have you looked to see if you are doing any paging at the OS level and if
this increases when the log file time increases? Are you running any other
apps on this server? it almost sounds like you have a memory leak
somewhere. While this is rare these days it does happen, especially if you
are running xp's or dlls outside of sql server. Anything with XML by any
chance?
Andrew J. Kelly SQL MVP
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:65EFE346-1F7F-4036-B60A-1C939C19EC89@.microsoft.com...[vbcol=seagreen]
> pretty standard maintainence plan from w/in SQL server; Agent; doing
> transaction backups every 2 hours;
> 2gb memory on server; letting SQL manage it's memory desires
> "Andrew J. Kelly" wrote:
|||You might also want to have a look at
FIX: Performance decreases over time when you back up files in SQL Server
2000
http://support.microsoft.com/?kbid=824430
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
> SQL runs on a clustered server and during the week the time it takes for
> the
> transactional backup slowly increases, and as it does it takes the
> majority
> of the system resources. the backup is sent to a drive on a remote
> system.
> In cluster admin if i take the service off-line and then back on-line it's
> back to running fast again. THe transactional backups take ~1minute after
> a
> off/on line and work their way to 7/8 minutes.
> any suggestions?
> --
> Richard
|||Thanks Jasper. I was sure there was a KB on that but i could not find it
for some reason. I couldn't remember the exact reasons but remembered there
was a KB related to this.
Andrew J. Kelly SQL MVP
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ORb9sAxAFHA.3016@.tk2msftngp13.phx.gbl...
> You might also want to have a look at
> FIX: Performance decreases over time when you back up files in SQL Server
> 2000
> http://support.microsoft.com/?kbid=824430
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Richard Roche" <RichardRoche@.discussions.microsoft.com> wrote in message
> news:93EE3C78-6686-4E18-A3BC-5B5A66EFB2A6@.microsoft.com...
>
|||I also remember a KB, and it was nearly two years ago. The long and the
short was run your backups locally, then use a script to "transfer" to the
remote storage. That way SQL Server does not have to handle the file
detatils in keeping a remote connection alive.
Larry
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23p08tGxAFHA.1392@.tk2msftngp13.phx.gbl...
> Thanks Jasper. I was sure there was a KB on that but i could not find it
> for some reason. I couldn't remember the exact reasons but remembered
> there was a KB related to this.
> --
> Andrew J. Kelly SQL MVP
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:ORb9sAxAFHA.3016@.tk2msftngp13.phx.gbl...
>
Friday, February 10, 2012
Backing up the SQL server 2000 database using tape drives
Dear sir/madam,
I am from NTU, Singapore and we have a windows 2003 server edition installed on a DELL server and it also runs MS SQL server 2000 for a project of ours. We have installed a HP tape drive on the dell server and it works fine if ntbackup is used at the command prompt but then the SQL enterprise manager does not recognize the tape drive and backing up of our database is of high priority as it contains sensitive information. But the tape drive is installed properly as the device manager does not show any error and ntbackup also recognizes it. I cant seem to figure out why SQL server 2000 cannot recognize it. It would be very helpful if you could kindly guide me on this issue.
Thanking you
Regards
Lavanya Janardhanan
There are two things that you can try here:
The first is to create a logical backup device for your tape device.
From Enterprise Manager, open the Query Analyzer and use the following command:
USE master EXEC sp_addumpdevice 'tape', 'tapedump1', '\\.\tape0' Where tapedump1 is the logical name for your tape drive, and \\.\tape0 is the physical path to your tape drive. You should use values for these parameters as appropriate to your configuration. You should then be able to use the logical device as a destination for your backups.
Alternatively, you can specify the tape path explicitly in TSQL, again in Query Analyzer:
BACKUP DATABASE MyDatabase TO TAPE = '\\.\Tape0' WITH FORMAT, NAME = 'My Backup Name';
This technique can help to determine where the issue is with recognizing your tape device.
Kevin Farlee
Subscribe to:
Posts (Atom)