We've added a new disk to our server.
When we click through the SQL Server Backup, to select
the "Backup Device Location", the new drive is not
available. The only drive that is available is the one
that existed when SQL was installed.
The same is true for restores.
Any ideas?
TIA,
Sean.
Hi,
Execute the below command from Query Analyzer;
xp_fixeddrives
If you are not able to see the new drive, Check for the existence of that
drive from Windows Explorer, if not contact your system administrator.
Thanks
Hari
MCDBA
"Sean Irving" <sbirving@.hotmail.com> wrote in message
news:178ae01c41dfe$8f99da60$a601280a@.phx.gbl...
> We've added a new disk to our server.
> When we click through the SQL Server Backup, to select
> the "Backup Device Location", the new drive is not
> available. The only drive that is available is the one
> that existed when SQL was installed.
> The same is true for restores.
> Any ideas?
> TIA,
> Sean.
>
|||If SQL Server is clustered, you have to add a dependency (SQL Server has to
depend on the disk). Also make sure you've restarted Enterprise Manager
since the disk was added, it may not have refreshed with the new
information.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label weve. Show all posts
Showing posts with label weve. Show all posts
Thursday, March 8, 2012
Sunday, February 12, 2012
Backup intermittently fails. OS Error:32
Hi,
We've been having an usual problem with our SQL server
backup. The database is around 41Gb, which does a full
database dump to a .bak daily, and then transaction log
dumps every 15mins. However, intermittently the full
backup will fail with the following:
nightlyrun.log
Msg 3201, Level 16, State 1, Server EARTH, Line 24
Cannot open backup device 'dratlas_backup'. Device error
or
device off-line. See the SQL Server error log for more
details.
Msg 3013, Level 16, State 1, Server EARTH, Line 24
BACKUP DATABASE is terminating abnormally.
ERRORLOG
2004-04-28 02:27:58.27 spid58 DBCC CHECKDB (hrlink)
executed by sa found 0 errors and repaired 0 errors.
2004-04-28 02:28:00.77 backup Database log truncated:
Database: hrlink.
2004-04-28 02:28:13.16 spid58
BackupDiskFile::CreateMedia: Backup
device '\\jupiter\dump$\dratlas_backup.bak' failed to
create. Operating system error = 32(error not found).
2004-04-28 02:28:13.18 backup BACKUP failed to
complete the command
The network share is always 100% available to the SQL
server on a 1Gb core network. As I said, this is
intermittent, and may fail once a week, or five times a
week, and nothing has changed on the servers or network.
The knowledge base does not include any information about
the OS error or Msg 3201
Any help will be much appreciated.
Thankyou.
Regards,
David
A single network interruption can an error such as this. With a 41GB file
being backed up over the network there is plenty of time for this to occur.
Another common cause is if you are reusing an existing device (either
appending or initing) and you have a tape backup trying to backup that
device at the same time. If these files are backed up to tape by a
different process you may want to check the timing of it compared to the
backup failure times.
Andrew J. Kelly SQL MVP
"David Meldrum" <david.meldrum@.skilled.com.au> wrote in message
news:526d01c42cb4$07a18da0$a301280a@.phx.gbl...
> Hi,
> We've been having an usual problem with our SQL server
> backup. The database is around 41Gb, which does a full
> database dump to a .bak daily, and then transaction log
> dumps every 15mins. However, intermittently the full
> backup will fail with the following:
> nightlyrun.log
> Msg 3201, Level 16, State 1, Server EARTH, Line 24
> Cannot open backup device 'dratlas_backup'. Device error
> or
> device off-line. See the SQL Server error log for more
> details.
> Msg 3013, Level 16, State 1, Server EARTH, Line 24
> BACKUP DATABASE is terminating abnormally.
> ERRORLOG
> 2004-04-28 02:27:58.27 spid58 DBCC CHECKDB (hrlink)
> executed by sa found 0 errors and repaired 0 errors.
> 2004-04-28 02:28:00.77 backup Database log truncated:
> Database: hrlink.
> 2004-04-28 02:28:13.16 spid58
> BackupDiskFile::CreateMedia: Backup
> device '\\jupiter\dump$\dratlas_backup.bak' failed to
> create. Operating system error = 32(error not found).
> 2004-04-28 02:28:13.18 backup BACKUP failed to
> complete the command
> The network share is always 100% available to the SQL
> server on a 1Gb core network. As I said, this is
> intermittent, and may fail once a week, or five times a
> week, and nothing has changed on the servers or network.
> The knowledge base does not include any information about
> the OS error or Msg 3201
> Any help will be much appreciated.
> Thankyou.
> Regards,
> David
We've been having an usual problem with our SQL server
backup. The database is around 41Gb, which does a full
database dump to a .bak daily, and then transaction log
dumps every 15mins. However, intermittently the full
backup will fail with the following:
nightlyrun.log
Msg 3201, Level 16, State 1, Server EARTH, Line 24
Cannot open backup device 'dratlas_backup'. Device error
or
device off-line. See the SQL Server error log for more
details.
Msg 3013, Level 16, State 1, Server EARTH, Line 24
BACKUP DATABASE is terminating abnormally.
ERRORLOG
2004-04-28 02:27:58.27 spid58 DBCC CHECKDB (hrlink)
executed by sa found 0 errors and repaired 0 errors.
2004-04-28 02:28:00.77 backup Database log truncated:
Database: hrlink.
2004-04-28 02:28:13.16 spid58
BackupDiskFile::CreateMedia: Backup
device '\\jupiter\dump$\dratlas_backup.bak' failed to
create. Operating system error = 32(error not found).
2004-04-28 02:28:13.18 backup BACKUP failed to
complete the command
The network share is always 100% available to the SQL
server on a 1Gb core network. As I said, this is
intermittent, and may fail once a week, or five times a
week, and nothing has changed on the servers or network.
The knowledge base does not include any information about
the OS error or Msg 3201
Any help will be much appreciated.
Thankyou.
Regards,
David
A single network interruption can an error such as this. With a 41GB file
being backed up over the network there is plenty of time for this to occur.
Another common cause is if you are reusing an existing device (either
appending or initing) and you have a tape backup trying to backup that
device at the same time. If these files are backed up to tape by a
different process you may want to check the timing of it compared to the
backup failure times.
Andrew J. Kelly SQL MVP
"David Meldrum" <david.meldrum@.skilled.com.au> wrote in message
news:526d01c42cb4$07a18da0$a301280a@.phx.gbl...
> Hi,
> We've been having an usual problem with our SQL server
> backup. The database is around 41Gb, which does a full
> database dump to a .bak daily, and then transaction log
> dumps every 15mins. However, intermittently the full
> backup will fail with the following:
> nightlyrun.log
> Msg 3201, Level 16, State 1, Server EARTH, Line 24
> Cannot open backup device 'dratlas_backup'. Device error
> or
> device off-line. See the SQL Server error log for more
> details.
> Msg 3013, Level 16, State 1, Server EARTH, Line 24
> BACKUP DATABASE is terminating abnormally.
> ERRORLOG
> 2004-04-28 02:27:58.27 spid58 DBCC CHECKDB (hrlink)
> executed by sa found 0 errors and repaired 0 errors.
> 2004-04-28 02:28:00.77 backup Database log truncated:
> Database: hrlink.
> 2004-04-28 02:28:13.16 spid58
> BackupDiskFile::CreateMedia: Backup
> device '\\jupiter\dump$\dratlas_backup.bak' failed to
> create. Operating system error = 32(error not found).
> 2004-04-28 02:28:13.18 backup BACKUP failed to
> complete the command
> The network share is always 100% available to the SQL
> server on a 1Gb core network. As I said, this is
> intermittent, and may fail once a week, or five times a
> week, and nothing has changed on the servers or network.
> The knowledge base does not include any information about
> the OS error or Msg 3201
> Any help will be much appreciated.
> Thankyou.
> Regards,
> David
Subscribe to:
Posts (Atom)