Repost: Need Help with "System.Data.SqlClient.Sqlerror: Cannot open backup device (DLT tape) ...

microsoft.public.sqlserver.tools

17 Apr 2006 8:57 PM

frostbb

We are having problems using the same DLT Tape to backup 2nd named Sql
Server 2005 instance.
Could really use some help.

We have a Win2003 Enterprise Server (SP1) running two named instances of Sql
Server
2005 (RTM) on the same physical server.

The first instance has been successfully backing up to the DLT tape system
attached to the server. We have successfully recoverd a database from the
tape.

The second instance of Sql Server is now up and running.   I created a
backup device pointed to the DLT tape drive in the same manner as I created
the backup device for the 1st instance. However, when I try to "view the
contents" from the 2nd instance backup device properties screen I get the
following error message.

[ System.Data.SqlClient.SqlError: Cannot open backup device 'DLT-Tape'
(\\.\Tape0). Operating ]
[ system error 32(The process cannot access the file because it is being
used by another process.). ]
[
                          ]

Running "SELECT * FROM sys.dm_io_backup_tapes" from the 2nd instance returns
no information.

Running "SELECT * FROM sys.dm_io_backup_tapes" from the 1st instance returns
the following ...

physical_device_name    \\.\Tape0,
logical_device_name      DLT-Tape,
status                             1,
status_desc                    AVAILABLE,
mount_request_time       NULL,
mount_epiration_name   NULL,
database_name              sde,
spid                               NULL,
command                      NULL,
command_desc             NULL,
media_family_id            1,
media_set_name           NULL,
media_set_guid             9nnnnn9-1nnF-4nn5-Bnn5-57nnnnn4E,
media_sequence_nbr     1,
tape_operation              1,
tape_operation_desc     READ,
mount_request_type      NULL,
mount_request_type_desc NULL

The issue here is that I want to back the databases within both instances up
to the DLT tape drive attached to the server.

Can't seem to find much about this type of error from Google searchs. Can
anyone give me a clue as how to start working on a resolution of this
problem ?

Thanks in advance.

Barry
in Oregon