Backup to Network Drive: failing

Showing posts with label failing. Show all posts

Sunday, March 25, 2012

basic authentication with olap failing

Hi,
I've got a situation where I am trying to connect from my local PC to
a windows 2003 server that is running SQL Server2k EE with Analysis
Services and IIS.
I have followed a number of Microsoft articles for configuring http
access to the Analysis Services, and my msolap.asp file is located
correctly and I have tested that I can access it with both anonymous
and basic authentication enabled on the site. The connection string I
am using is pointing to the correct directory for my msolap.asp file.
I can type the url to my msolap.asp file into my browser and do not
get any errors, both on anonymous or basic authentication access (I
need to have basic authentication).
The problem lies in the fact that when I try and access my web site
pages that contain the OWC components, if I turn on basic
authentication on msolap.asp I get unspecified errors and cannot load
data. If I leave the msolap.asp file as anonymous access and my web
site virtual directory with basic authentication, I am promted to
login and the data displays correctly. However, if I refresh the
page, I am prompted to login again - which should not be happening.
The frustrating thing is, if I remove the dynamic OWC component from
my page but leave the static OWC component, then I do not get prompted
to log in multiple times and it behaves as it should.
I know I've outlined a few problems in this post, but I'm pretty new
to OLAP and I'm just trying to get it running on a server.
Thanks in advanceTo clear up a few items, it appears there is no impact of the OWC
component being dynamic or static, as either one of them results in
multiple login prompts. If I disable basic authentication on
msolap.asp, then the strange behaviour I notice is that when I have the
site marked as "Trusted" in my browser, I am prompted to login on first
page access (which is correct), but then prompted to login again on any
hyperlink click on the page or on a page refresh. If I remove the
"Trusted" status, then I am only prompted to login on first access to
the site and on any subsequent refresh of the page in the browser.
Is this the correct behaviour for OWC/OLAP components?
Thankssql

Wednesday, March 7, 2012

Backups keep failing?

I used the database maintenance wizard and choose most of the defaults.
Every night my backups fail because of the step to check data indexes and
repair any minor problems. The error I receive is [Microsoft][ODBC SQL
Server Driver][SQL Server]Repair statement not processed. Database needs to
be in single user mode. Does anyone know why this happeneds?
Thanks,
DanSee this page -
http://support.microsoft.com/default.aspx?scid=kb;en-us;290622
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Dan Marth" <danmarth@.earthlink.net> wrote in message
news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
> I used the database maintenance wizard and choose most of the defaults.
> Every night my backups fail because of the step to check data indexes and
> repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs
to
> be in single user mode. Does anyone know why this happeneds?
> Thanks,
> Dan
>|||Thanks, that seemed to clear things up!
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:OTvHYUw2DHA.3196@.TK2MSFTNGP11.phx.gbl...
> See this page -
> http://support.microsoft.com/default.aspx?scid=kb;en-us;290622
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "Dan Marth" <danmarth@.earthlink.net> wrote in message
> news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
> > I used the database maintenance wizard and choose most of the defaults.
> > Every night my backups fail because of the step to check data indexes
and
> > repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> > Server Driver][SQL Server]Repair statement not processed. Database needs
> to
> > be in single user mode. Does anyone know why this happeneds?
> >
> > Thanks,
> > Dan
> >
> >
>

Backups keep failing?

quote:

> I used the database maintenance wizard and choose most of the defaults.
> Every night my backups fail because of the step to check data indexes and
> repair any minor problems. The error I receive is [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs

quote:

> be in single user mode. Does anyone know why this happeneds?
> Thanks,
> Dan
>

|||Thanks, that seemed to clear things up!
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:OTvHYUw2DHA.3196@.TK2MSFTNGP11.phx.gbl...

quote:

> See this page -
> http://support.microsoft.com/defaul...kb;en-us;290622
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "Dan Marth" <danmarth@.earthlink.net> wrote in message
> news:ux0ir6v2DHA.2408@.tk2msftngp13.phx.gbl...
and[QUOTE]
> to
>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
Thanks
Your message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
ChrisR
"Cynthia" wrote:

> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
--
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

Backups Failing on Production Servers

Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being use
d
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge
] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the fil
e
to do a backup.
ChrisR
"Cynthia" wrote:

> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and t
he
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being u
sed
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30
PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEd
ge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>

backups failing

Executed as user: domain\bla. The backup data in 'DevBackupDevice2' is
incorrectly formatted. Backups cannot be appended, but existing backup sets
may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
I got this message this morning when trying to do a full backup. I dropped/
recreated the backup device and then tried again. I got the same message
still.
Any ideas?
SQL2K SP3
TIA, ChrisR
Chris,
Are you backing up to tape? See KB 290787, "PRB: Error Message 3266 Occurs
When Microsoft Tape Backup Format Cannot be Read"
The SQL Server 2000 example references the same error message you are
reporting.
Ron
Ron Talmage
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:O%23VM7h44EHA.3820@.TK2MSFTNGP11.phx.gbl...
> Executed as user: domain\bla. The backup data in 'DevBackupDevice2' is
> incorrectly formatted. Backups cannot be appended, but existing backup
sets
> may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
> I got this message this morning when trying to do a full backup. I
dropped/
> recreated the backup device and then tried again. I got the same message
> still.
> Any ideas?
> --
> SQL2K SP3
> TIA, ChrisR
>

Backups failing

I am running SQL-2000 Standard (SP3) and have created a backup job a while
back to back up several databases, and a seperate job to backup transaction
logs. 2 out of the 3 databases are being backed up and the transaction logs
are backing up, but our largest database (almost 5GB) is failing on the
backup. Where can I look to see why it is failing?
How do you run these jobs, and what types are they of. Maint Wiz? SQL Server Agent jobs, TSQL or
CmdExec? Etc...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup transaction
> logs. 2 out of the 3 databases are being backed up and the transaction logs
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?
|||Tibor Karaszi wrote:

> How do you run these jobs, and what types are they of. Maint Wiz? SQL
> Server Agent jobs, TSQL or CmdExec? Etc...
>
They were created using the Maintenance Wizard and scheduled to run nightly.
|||You may need to look at both the job history (make sure to view step
details) and the MP history.
Andrew J. Kelly SQL MVP
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup
> transaction
> logs. 2 out of the 3 databases are being backed up and the transaction
> logs
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?
|||In addition to Andrew's answer, I suggest you specify a report file in Main Wiz and look for error
messages in there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:estbZJEvEHA.3424@.TK2MSFTNGP09.phx.gbl...
> Tibor Karaszi wrote:
>
> They were created using the Maintenance Wizard and scheduled to run nightly.

backups failing

Executed as user: domain\bla. The backup data in 'DevBackupDevice2' is
incorrectly formatted. Backups cannot be appended, but existing backup sets
may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
I got this message this morning when trying to do a full backup. I dropped/
recreated the backup device and then tried again. I got the same message
still.
Any ideas?
--
SQL2K SP3
TIA, ChrisRChris,
Are you backing up to tape? See KB 290787, "PRB: Error Message 3266 Occurs
When Microsoft Tape Backup Format Cannot be Read"
The SQL Server 2000 example references the same error message you are
reporting.
Ron
--
Ron Talmage
SQL Server MVP
"ChrisR" <bla@.noemail.com> wrote in message
news:O%23VM7h44EHA.3820@.TK2MSFTNGP11.phx.gbl...
> Executed as user: domain\bla. The backup data in 'DevBackupDevice2' is
> incorrectly formatted. Backups cannot be appended, but existing backup
sets
> may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
> I got this message this morning when trying to do a full backup. I
dropped/
> recreated the backup device and then tried again. I got the same message
> still.
> Any ideas?
> --
> SQL2K SP3
> TIA, ChrisR
>

Backups failing

I am running SQL-2000 Standard (SP3) and have created a backup job a while
back to back up several databases, and a seperate job to backup transaction
logs. 2 out of the 3 databases are being backed up and the transaction logs
are backing up, but our largest database (almost 5GB) is failing on the
backup. Where can I look to see why it is failing?How do you run these jobs, and what types are they of. Maint Wiz? SQL Server Agent jobs, TSQL or
CmdExec? Etc...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup transaction
> logs. 2 out of the 3 databases are being backed up and the transaction logs
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?|||Tibor Karaszi wrote:
> How do you run these jobs, and what types are they of. Maint Wiz? SQL
> Server Agent jobs, TSQL or CmdExec? Etc...
>
They were created using the Maintenance Wizard and scheduled to run nightly.|||You may need to look at both the job history (make sure to view step
details) and the MP history.
--
Andrew J. Kelly SQL MVP
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup
> transaction
> logs. 2 out of the 3 databases are being backed up and the transaction
> logs
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?|||In addition to Andrew's answer, I suggest you specify a report file in Main Wiz and look for error
messages in there.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:estbZJEvEHA.3424@.TK2MSFTNGP09.phx.gbl...
> Tibor Karaszi wrote:
>> How do you run these jobs, and what types are they of. Maint Wiz? SQL
>> Server Agent jobs, TSQL or CmdExec? Etc...
>
> They were created using the Maintenance Wizard and scheduled to run nightly.

Backups Failing

I set up a full backup maintenance plan for my databases and the database portion of the backup jobs completes successfully, but the transaction log portion successfully backs up master and model, but fails for the other databases with the message:

Backup can not be performed on database 'msdb'. This sub task is ignored.

What's the problem?

Bob

Check the recovery model of your databases. They are probably in SIMPLE mode so transaction logs are not allowed.

HTH!

|||

I thought this was answered, but it's not. I have never had the master db transaction log backed up. I have set it to full backup as I have with the others and they all work, but master still does not.

Bob

|||

You can only perform transaction log backups on databases in the full or bulk-logged recovery modes (check your db options for this). Master and MSDB databases are always set to simple therefore no transaction log backup can occur on these databases. When configuring your maintenance plans these should be omitted.

|||As said above you can perform only Full backups with Master database regardless of the recovery model ! and full,differential and tran log backups with msdb db if the recovery model is full or bulk logged ! for model db if the recovery is full all 3 backups are possible if its simple only tran logs are not possible in model

|||

Thanks all - I see that now.

Backups failing

I am running SQL-2000 Standard (SP3) and have created a backup job a while
back to back up several databases, and a seperate job to backup transaction
logs. 2 out of the 3 databases are being backed up and the transaction logs
are backing up, but our largest database (almost 5GB) is failing on the
backup. Where can I look to see why it is failing?How do you run these jobs, and what types are they of. Maint Wiz? SQL Server
Agent jobs, TSQL or
CmdExec? Etc...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup transactio
n
> logs. 2 out of the 3 databases are being backed up and the transaction log
s
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?|||Tibor Karaszi wrote:

> How do you run these jobs, and what types are they of. Maint Wiz? SQL
> Server Agent jobs, TSQL or CmdExec? Etc...
>
They were created using the Maintenance Wizard and scheduled to run nightly.|||You may need to look at both the job history (make sure to view step
details) and the MP history.
Andrew J. Kelly SQL MVP
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:%23v8hVlDvEHA.3976@.TK2MSFTNGP09.phx.gbl...
>I am running SQL-2000 Standard (SP3) and have created a backup job a while
> back to back up several databases, and a seperate job to backup
> transaction
> logs. 2 out of the 3 databases are being backed up and the transaction
> logs
> are backing up, but our largest database (almost 5GB) is failing on the
> backup. Where can I look to see why it is failing?|||In addition to Andrew's answer, I suggest you specify a report file in Main
Wiz and look for error
messages in there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Humphrey" <richard@.multicam.com> wrote in message
news:estbZJEvEHA.3424@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Tibor Karaszi wrote:
>
>
> They were created using the Maintenance Wizard and scheduled to run nightly.[/vbco
l]

Saturday, February 25, 2012

Backups

Hello,
Our backups are failing as we have connections to them,
and the error is that the database must be in single mode.
Our recovery plan is set to full, so I was wondering what
the best practise is i.e could we set the database to
single mode killing off all connections, use some SQL
commands to kill off connection, or change the recovery
model to something else.
Any help would be appreciated.
Thanks
PeterHello, Peter!
Is this through a maintenance plan ?
SQL Server backups can be taken with users still on the system. A Database
cannot be restored with users in the database. Is this error being
generated by SQL Server trying to put the DB into Single User mode to fix
minor errors ?
You can quite easily test the BACKUP ni isolation by going to QA and issuing
the statement there.
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
: Our backups are failing as we have connections to them,
: and the error is that the database must be in single mode.
: Our recovery plan is set to full, so I was wondering what
: the best practise is i.e could we set the database to
: single mode killing off all connections, use some SQL
: commands to kill off connection, or change the recovery
: model to something else.
: Any help would be appreciated.
-- Microsoft CDO for Windows 2000|||Thank you, I will change my options.
Peter
>--Original Message--
>Yes, I agree with Allan in that this is due to the fact
you have the option
>checked to do an integrity check before the backups and
that is what needs
>to be in single user mode. This is a bad option anyway
because people
>usually have the integrity jobs running from the other
page of the MP
>dialog. So now it does DBCC's 2 or 3 times.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in
message
>news:enfKY0UQDHA.3016@.TK2MSFTNGP10.phx.gbl...
>> Hello, Peter!
>> Is this through a maintenance plan ?
>> SQL Server backups can be taken with users still on the
system. A
>Database
>> cannot be restored with users in the database. Is this
error being
>> generated by SQL Server trying to put the DB into
Single User mode to fix
>> minor errors ?
>>
>> You can quite easily test the BACKUP ni isolation by
going to QA and
>issuing
>> the statement there.
>>
>>
>> --
>> Allan Mitchell (Microsoft SQL Server MVP)
>> MCSE,MCDBA
>> www.SQLDTS.com
>> I support PASS - the definitive, global community
>> for SQL Server professionals - http://www.sqlpass.org
>> : Our backups are failing as we have connections to
them,
>> : and the error is that the database must be in single
mode.
>> : Our recovery plan is set to full, so I was wondering
what
>> : the best practise is i.e could we set the database to
>> : single mode killing off all connections, use some SQL
>> : commands to kill off connection, or change the
recovery
>> : model to something else.
>> : Any help would be appreciated.
>> -- Microsoft CDO for Windows 2000
>>
>
>.
>

Thursday, February 16, 2012

Backup( thru DB Maintenace plan) to another server failing

We have 4 servers in a workgroup environment. I have created 2 users (
SQLOwner and SQLAgent) on all the four servers with Admin privs. On all the
servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
Service.
I have created a DBMaintenance Plan on 3 servers to backup the user
databases directly onto Server 4 ( Use this directory ->
\\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running fine
(for 2 months). All of a sudden the jobs are failing. From the Job History I
see the following error ...
Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
(Error 22029). The step failed.
I see the following error from SQLServer Logs ...
BackupDiskFile::CreateMedia: Backup device
'\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
Operating system error = 1330(Logon failure: the specified account password
has expired.).
I verified the password for the user SQLAgent (the owner SQLServer Agent
service) on all the servers and it is same. SQLAgent user is setup as non
expiring account.
When I tried to backup a single database (use this directory ->
\\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
verify backup file location. Do you want to use the backup file location
anyway ?"
--
RKLook at
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
Walk through the troubleshooting steps at the bottom. It is likely a
permissions issue or an expured account issue.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> We have 4 servers in a workgroup environment. I have created 2 users (
> SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> the
> servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> Service.
> I have created a DBMaintenance Plan on 3 servers to backup the user
> databases directly onto Server 4 ( Use this directory ->
> \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> fine
> (for 2 months). All of a sudden the jobs are failing. From the Job History
> I
> see the following error ...
> Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error 22029). The step failed.
> I see the following error from SQLServer Logs ...
> BackupDiskFile::CreateMedia: Backup device
> '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> Operating system error = 1330(Logon failure: the specified account
> password
> has expired.).
> I verified the password for the user SQLAgent (the owner SQLServer Agent
> service) on all the servers and it is same. SQLAgent user is setup as non
> expiring account.
> When I tried to backup a single database (use this directory ->
> \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> verify backup file location. Do you want to use the backup file location
> anyway ?"
>
> --
> RK|||Thanks fo r the quick Reply Geoff. I figured what the problem was. SQLOwner
account on SQL 03 server ( where all servers are writing their backups) was
expired. I changed it a non-expiring account
I thought for backup jobs we are only concerned about the user running the
SQLServerAgent service, which is SQLAgent user in my case.
"Geoff N. Hiten" wrote:
> Look at
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> Walk through the troubleshooting steps at the bottom. It is likely a
> permissions issue or an expured account issue.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> > We have 4 servers in a workgroup environment. I have created 2 users (
> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> > the
> > servers SQLOwner runs MSSQLServer service and SQLAgent run SQLSERVERAgent
> > Service.
> >
> > I have created a DBMaintenance Plan on 3 servers to backup the user
> > databases directly onto Server 4 ( Use this directory ->
> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were running
> > fine
> > (for 2 months). All of a sudden the jobs are failing. From the Job History
> > I
> > see the following error ...
> >
> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> > (Error 22029). The step failed.
> >
> > I see the following error from SQLServer Logs ...
> >
> > BackupDiskFile::CreateMedia: Backup device
> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> > Operating system error = 1330(Logon failure: the specified account
> > password
> > has expired.).
> >
> > I verified the password for the user SQLAgent (the owner SQLServer Agent
> > service) on all the servers and it is same. SQLAgent user is setup as non
> > expiring account.
> >
> > When I tried to backup a single database (use this directory ->
> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> > verify backup file location. Do you want to use the backup file location
> > anyway ?"
> >
> >
> > --
> > RK
>
>|||The SQL Agent invokes the backup command. The SQL engine actually runs the
command so you have to be concerned about the login account for the SQL
Server service, not the SQL Agent service.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> Thanks fo r the quick Reply Geoff. I figured what the problem was.
> SQLOwner
> account on SQL 03 server ( where all servers are writing their backups)
> was
> expired. I changed it a non-expiring account
> I thought for backup jobs we are only concerned about the user running the
> SQLServerAgent service, which is SQLAgent user in my case.
> "Geoff N. Hiten" wrote:
>> Look at
>> HowTo: Backup to UNC name using Database Maintenance Wizard
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
>> Walk through the troubleshooting steps at the bottom. It is likely a
>> permissions issue or an expured account issue.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Administrator
>>
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>> > We have 4 servers in a workgroup environment. I have created 2 users (
>> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
>> > the
>> > servers SQLOwner runs MSSQLServer service and SQLAgent run
>> > SQLSERVERAgent
>> > Service.
>> >
>> > I have created a DBMaintenance Plan on 3 servers to backup the user
>> > databases directly onto Server 4 ( Use this directory ->
>> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
>> > running
>> > fine
>> > (for 2 months). All of a sudden the jobs are failing. From the Job
>> > History
>> > I
>> > see the following error ...
>> >
>> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
>> > (Error 22029). The step failed.
>> >
>> > I see the following error from SQLServer Logs ...
>> >
>> > BackupDiskFile::CreateMedia: Backup device
>> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
>> > Operating system error = 1330(Logon failure: the specified account
>> > password
>> > has expired.).
>> >
>> > I verified the password for the user SQLAgent (the owner SQLServer
>> > Agent
>> > service) on all the servers and it is same. SQLAgent user is setup as
>> > non
>> > expiring account.
>> >
>> > When I tried to backup a single database (use this directory ->
>> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
>> > verify backup file location. Do you want to use the backup file
>> > location
>> > anyway ?"
>> >
>> >
>> > --
>> > RK
>>|||Thank you
"Geoff N. Hiten" wrote:
> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> > SQLOwner
> > account on SQL 03 server ( where all servers are writing their backups)
> > was
> > expired. I changed it a non-expiring account
> > I thought for backup jobs we are only concerned about the user running the
> > SQLServerAgent service, which is SQLAgent user in my case.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Look at
> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >>
> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> permissions issue or an expured account issue.
> >>
> >> Geoff N. Hiten
> >> Microsoft SQL Server MVP
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> > We have 4 servers in a workgroup environment. I have created 2 users (
> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> >> > the
> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> > SQLSERVERAgent
> >> > Service.
> >> >
> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> > databases directly onto Server 4 ( Use this directory ->
> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> > running
> >> > fine
> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> > History
> >> > I
> >> > see the following error ...
> >> >
> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> >> > (Error 22029). The step failed.
> >> >
> >> > I see the following error from SQLServer Logs ...
> >> >
> >> > BackupDiskFile::CreateMedia: Backup device
> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> >> > Operating system error = 1330(Logon failure: the specified account
> >> > password
> >> > has expired.).
> >> >
> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> > Agent
> >> > service) on all the servers and it is same. SQLAgent user is setup as
> >> > non
> >> > expiring account.
> >> >
> >> > When I tried to backup a single database (use this directory ->
> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> >> > verify backup file location. Do you want to use the backup file
> >> > location
> >> > anyway ?"
> >> >
> >> >
> >> > --
> >> > RK
> >>
> >>
> >>
>
>|||I am backing up user databases on SQL04, but i am writing the backups to
SQL03 directly (use this directory -> \\SQL03\D$...). How does user account
on SQL03 expiring affect the backup job on SQL04 ?
In my case SQL03 happened to be another SQL Server. What is if the
destination server (SQL03) does not even have a SQL Serer running on it ?
"Geoff N. Hiten" wrote:
> The SQL Agent invokes the backup command. The SQL engine actually runs the
> command so you have to be concerned about the login account for the SQL
> Server service, not the SQL Agent service.
> GNH
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> > SQLOwner
> > account on SQL 03 server ( where all servers are writing their backups)
> > was
> > expired. I changed it a non-expiring account
> > I thought for backup jobs we are only concerned about the user running the
> > SQLServerAgent service, which is SQLAgent user in my case.
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Look at
> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >>
> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> permissions issue or an expured account issue.
> >>
> >> Geoff N. Hiten
> >> Microsoft SQL Server MVP
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> > We have 4 servers in a workgroup environment. I have created 2 users (
> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On all
> >> > the
> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> > SQLSERVERAgent
> >> > Service.
> >> >
> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> > databases directly onto Server 4 ( Use this directory ->
> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> > running
> >> > fine
> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> > History
> >> > I
> >> > see the following error ...
> >> >
> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE 42000]
> >> > (Error 22029). The step failed.
> >> >
> >> > I see the following error from SQLServer Logs ...
> >> >
> >> > BackupDiskFile::CreateMedia: Backup device
> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to create.
> >> > Operating system error = 1330(Logon failure: the specified account
> >> > password
> >> > has expired.).
> >> >
> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> > Agent
> >> > service) on all the servers and it is same. SQLAgent user is setup as
> >> > non
> >> > expiring account.
> >> >
> >> > When I tried to backup a single database (use this directory ->
> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to to
> >> > verify backup file location. Do you want to use the backup file
> >> > location
> >> > anyway ?"
> >> >
> >> >
> >> > --
> >> > RK
> >>
> >>
> >>
>
>|||The fact that the target server is a SQL server does not matter. It is the
SQL service account from the originating server that must have file system
rights to the target server. If the target server also happens to run a SQL
instance it does not matter.
GNH
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
>I am backing up user databases on SQL04, but i am writing the backups to
> SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> account
> on SQL03 expiring affect the backup job on SQL04 ?
> In my case SQL03 happened to be another SQL Server. What is if the
> destination server (SQL03) does not even have a SQL Serer running on it ?
> "Geoff N. Hiten" wrote:
>> The SQL Agent invokes the backup command. The SQL engine actually runs
>> the
>> command so you have to be concerned about the login account for the SQL
>> Server service, not the SQL Agent service.
>> GNH
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
>> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
>> > SQLOwner
>> > account on SQL 03 server ( where all servers are writing their backups)
>> > was
>> > expired. I changed it a non-expiring account
>> > I thought for backup jobs we are only concerned about the user running
>> > the
>> > SQLServerAgent service, which is SQLAgent user in my case.
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> Look at
>> >> HowTo: Backup to UNC name using Database Maintenance Wizard
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
>> >>
>> >> Walk through the troubleshooting steps at the bottom. It is likely a
>> >> permissions issue or an expured account issue.
>> >>
>> >> Geoff N. Hiten
>> >> Microsoft SQL Server MVP
>> >> Senior Database Administrator
>> >>
>> >>
>> >>
>> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
>> >> > We have 4 servers in a workgroup environment. I have created 2 users
>> >> > (
>> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On
>> >> > all
>> >> > the
>> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
>> >> > SQLSERVERAgent
>> >> > Service.
>> >> >
>> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
>> >> > databases directly onto Server 4 ( Use this directory ->
>> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
>> >> > running
>> >> > fine
>> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
>> >> > History
>> >> > I
>> >> > see the following error ...
>> >> >
>> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE
>> >> > 42000]
>> >> > (Error 22029). The step failed.
>> >> >
>> >> > I see the following error from SQLServer Logs ...
>> >> >
>> >> > BackupDiskFile::CreateMedia: Backup device
>> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to
>> >> > create.
>> >> > Operating system error = 1330(Logon failure: the specified account
>> >> > password
>> >> > has expired.).
>> >> >
>> >> > I verified the password for the user SQLAgent (the owner SQLServer
>> >> > Agent
>> >> > service) on all the servers and it is same. SQLAgent user is setup
>> >> > as
>> >> > non
>> >> > expiring account.
>> >> >
>> >> > When I tried to backup a single database (use this directory ->
>> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to
>> >> > to
>> >> > verify backup file location. Do you want to use the backup file
>> >> > location
>> >> > anyway ?"
>> >> >
>> >> >
>> >> > --
>> >> > RK
>> >>
>> >>
>> >>
>>|||It makes sense now. Thank you Geoff.
"Geoff N. Hiten" wrote:
> The fact that the target server is a SQL server does not matter. It is the
> SQL service account from the originating server that must have file system
> rights to the target server. If the target server also happens to run a SQL
> instance it does not matter.
> GNH
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:067D0A4E-5B38-401D-98D5-E4C988DDCC8F@.microsoft.com...
> >I am backing up user databases on SQL04, but i am writing the backups to
> > SQL03 directly (use this directory -> \\SQL03\D$...). How does user
> > account
> > on SQL03 expiring affect the backup job on SQL04 ?
> >
> > In my case SQL03 happened to be another SQL Server. What is if the
> > destination server (SQL03) does not even have a SQL Serer running on it ?
> >
> > "Geoff N. Hiten" wrote:
> >
> >> The SQL Agent invokes the backup command. The SQL engine actually runs
> >> the
> >> command so you have to be concerned about the login account for the SQL
> >> Server service, not the SQL Agent service.
> >>
> >> GNH
> >>
> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> news:2A6987EE-85C1-4DA8-A12E-21FA8B4CB269@.microsoft.com...
> >> > Thanks fo r the quick Reply Geoff. I figured what the problem was.
> >> > SQLOwner
> >> > account on SQL 03 server ( where all servers are writing their backups)
> >> > was
> >> > expired. I changed it a non-expiring account
> >> > I thought for backup jobs we are only concerned about the user running
> >> > the
> >> > SQLServerAgent service, which is SQLAgent user in my case.
> >> >
> >> > "Geoff N. Hiten" wrote:
> >> >
> >> >> Look at
> >> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >> >>
> >> >> Walk through the troubleshooting steps at the bottom. It is likely a
> >> >> permissions issue or an expured account issue.
> >> >>
> >> >> Geoff N. Hiten
> >> >> Microsoft SQL Server MVP
> >> >> Senior Database Administrator
> >> >>
> >> >>
> >> >>
> >> >> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> >> >> news:92226F4B-E76A-42F5-8418-9DA19CCD314F@.microsoft.com...
> >> >> > We have 4 servers in a workgroup environment. I have created 2 users
> >> >> > (
> >> >> > SQLOwner and SQLAgent) on all the four servers with Admin privs. On
> >> >> > all
> >> >> > the
> >> >> > servers SQLOwner runs MSSQLServer service and SQLAgent run
> >> >> > SQLSERVERAgent
> >> >> > Service.
> >> >> >
> >> >> > I have created a DBMaintenance Plan on 3 servers to backup the user
> >> >> > databases directly onto Server 4 ( Use this directory ->
> >> >> > \\SQL03\D$\SQLData...). Until two days ago, the backup jobs were
> >> >> > running
> >> >> > fine
> >> >> > (for 2 months). All of a sudden the jobs are failing. From the Job
> >> >> > History
> >> >> > I
> >> >> > see the following error ...
> >> >> >
> >> >> > Executed as user: SQL04\SQLAgent. sqlmaint.exe failed. [SQLSTATE
> >> >> > 42000]
> >> >> > (Error 22029). The step failed.
> >> >> >
> >> >> > I see the following error from SQLServer Logs ...
> >> >> >
> >> >> > BackupDiskFile::CreateMedia: Backup device
> >> >> > '\\SQL03\D$\SQLData\SQL04\ExIc_db_200503150100.BAK' failed to
> >> >> > create.
> >> >> > Operating system error = 1330(Logon failure: the specified account
> >> >> > password
> >> >> > has expired.).
> >> >> >
> >> >> > I verified the password for the user SQLAgent (the owner SQLServer
> >> >> > Agent
> >> >> > service) on all the servers and it is same. SQLAgent user is setup
> >> >> > as
> >> >> > non
> >> >> > expiring account.
> >> >> >
> >> >> > When I tried to backup a single database (use this directory ->
> >> >> > \\sql03\d$\SQLData\SQL04\test.bak), I get a error message "Unable to
> >> >> > to
> >> >> > verify backup file location. Do you want to use the backup file
> >> >> > location
> >> >> > anyway ?"
> >> >> >
> >> >> >
> >> >> > --
> >> >> > RK
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>

Sunday, February 12, 2012

Backup to USB drive failing

We have a SQL Server (2000, Win2K) that used to backup to a tape drive. The
tape drive was connected through our Domain Controller. DC crashed. As
emergency solution, a 256GB external USB drive was attached to the SQL
Server, and appears in structure as Drive F:\.
I can manually backup my TLog to the USB drive, but scheduled TLog backups
don't even launch, let alone fail.
I can launch a manual Full Database backup, but it fails, error 112, not
enough disk space. My db is only 50GB, and I have 230GB free on my external
USB drive.
Any ideas why my scheduled (Maintenance Plan) TLog backups don't even
launch, and why the Full backup says I am out of space?
We are using the Administrator login, with full permissions.
Thanks!Make sure your drive is formatted using NTFS, not FAT32.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Duane" <Duane@.discussions.microsoft.com> wrote in message
news:346BBF00-0EFA-4929-A452-DACF33FDE7C0@.microsoft.com...
> We have a SQL Server (2000, Win2K) that used to backup to a tape drive.
> The
> tape drive was connected through our Domain Controller. DC crashed. As
> emergency solution, a 256GB external USB drive was attached to the SQL
> Server, and appears in structure as Drive F:\.
> I can manually backup my TLog to the USB drive, but scheduled TLog backups
> don't even launch, let alone fail.
> I can launch a manual Full Database backup, but it fails, error 112, not
> enough disk space. My db is only 50GB, and I have 230GB free on my
> external
> USB drive.
> Any ideas why my scheduled (Maintenance Plan) TLog backups don't even
> launch, and why the Full backup says I am out of space?
> We are using the Administrator login, with full permissions.
> Thanks!|||Geoff, thanks. It is FAT32, and we will reformat Thursday and try again.
HOWEVER, I still have the issue of why my scheduled backups don't even
launch. This shouldn't have anything to do with formatting, as I can
manually backup a TLog, but it doesn't even launch when scheduled.
Suggestions?
Thanks,
Duane
"Geoff N. Hiten" wrote:
> Make sure your drive is formatted using NTFS, not FAT32.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Duane" <Duane@.discussions.microsoft.com> wrote in message
> news:346BBF00-0EFA-4929-A452-DACF33FDE7C0@.microsoft.com...
> > We have a SQL Server (2000, Win2K) that used to backup to a tape drive.
> > The
> > tape drive was connected through our Domain Controller. DC crashed. As
> > emergency solution, a 256GB external USB drive was attached to the SQL
> > Server, and appears in structure as Drive F:\.
> >
> > I can manually backup my TLog to the USB drive, but scheduled TLog backups
> > don't even launch, let alone fail.
> >
> > I can launch a manual Full Database backup, but it fails, error 112, not
> > enough disk space. My db is only 50GB, and I have 230GB free on my
> > external
> > USB drive.
> >
> > Any ideas why my scheduled (Maintenance Plan) TLog backups don't even
> > launch, and why the Full backup says I am out of space?
> >
> > We are using the Administrator login, with full permissions.
> >
> > Thanks!
>
>|||"Duane" <Duane@.discussions.microsoft.com> wrote in message
news:019B2438-DC3D-41D9-992F-C42B2CA300A4@.microsoft.com...
> Geoff, thanks. It is FAT32, and we will reformat Thursday and try again.
> HOWEVER, I still have the issue of why my scheduled backups don't even
> launch. This shouldn't have anything to do with formatting, as I can
> manually backup a TLog, but it doesn't even launch when scheduled.
GENERALLY I've seen that when folks backup to a shared drive and don't have
permissions right.
But if this is a local drive, that shouldn't be an issue... hmm, unless
somehow the user account SQL Admin is running under hasn't picked up the new
drive letter?
Might want to try cycling SQL Admin.
> Suggestions?
> Thanks,
> Duane
> "Geoff N. Hiten" wrote:
> > Make sure your drive is formatted using NTFS, not FAT32.
> >
> > --
> > Geoff N. Hiten
> > Senior Database Administrator
> > Microsoft SQL Server MVP
> >
> >
> > "Duane" <Duane@.discussions.microsoft.com> wrote in message
> > news:346BBF00-0EFA-4929-A452-DACF33FDE7C0@.microsoft.com...
> > > We have a SQL Server (2000, Win2K) that used to backup to a tape
drive.
> > > The
> > > tape drive was connected through our Domain Controller. DC crashed.
As
> > > emergency solution, a 256GB external USB drive was attached to the SQL
> > > Server, and appears in structure as Drive F:\.
> > >
> > > I can manually backup my TLog to the USB drive, but scheduled TLog
backups
> > > don't even launch, let alone fail.
> > >
> > > I can launch a manual Full Database backup, but it fails, error 112,
not
> > > enough disk space. My db is only 50GB, and I have 230GB free on my
> > > external
> > > USB drive.
> > >
> > > Any ideas why my scheduled (Maintenance Plan) TLog backups don't even
> > > launch, and why the Full backup says I am out of space?
> > >
> > > We are using the Administrator login, with full permissions.
> > >
> > > Thanks!
> >
> >
> >

Backup to USB drive failing

Backup to UNC path failing

Hi,

I have been trying to set up log shipping on a database with a backup size of ~190MB. However, I have been getting two error messages as stated below during the initial backup of the DB before it is restored on the warm standby.

1st Error
-----
Windows was unable to save all of the data for the file \Device\LanmanRedirector\<<UNC Path>>. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save the file elsewhere.

2nd Error
----
Write on '<<UNC path>>' failed, status 64. See the Sql Server eror log for more details. BACKUP database is terminating abnormally.

Backing up the database out side of the logshipping set up runs fine if I use a mapped drive, but it fails again when I use a UNC path. All the permissions are correct (I have backed up a smaller DB to the UNC path which completes successfully) so I am a little stumped.

Any help would be greatly appreciated

Thanks

RichI think this is a caching issue - check to see if you have network redirector caching enabled. The following link shows you how to disable:

link (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q163401)

The following is another link that might be helpful if the above information does not solve your problem:

link (http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q321733&)|||Thanks for coming back so quickly. I thought that the cache could be the problem but noticed from the link you sent that it was specific to NT. I forgot to mention in my initial post that I am running on Win 2k SP2 Adv. Server boxes. Could this still be a problem with the more recent OS?

The second link you mentioned relates to a very specific record in the event log. The error I am experiencing is almost identical to that mentioned in the KB article all exceppt for the final staus code. I do not have c0000022 in my event log. Am I correct in therefore assuming that the workaround will not make any difference.

I know this is just more questions, but I do not have access to the boxes for the next couple of days and am trying to workout the best approach so as to try to reolve the problem when I get on site as quickly as possible.

Cheers

Rich

Sunday, March 25, 2012

basic authentication with olap failing

Wednesday, March 7, 2012

Backups keep failing?

Backups keep failing?

Backups Failing on Production Servers

Backups Failing on Production Servers

Backups Failing on Production Servers

backups failing

Backups failing

backups failing

Backups failing

Backups Failing

Backups failing

Saturday, February 25, 2012

Backups

Thursday, February 16, 2012

Backup( thru DB Maintenace plan) to another server failing

Backup( thru DB Maintenace plan) to another server failing

Backup( thru DB Maintenace plan) to another server failing

Sunday, February 12, 2012

Backup to USB drive failing

Backup to USB drive failing

Backup to UNC path failing

Backup to Network Drive

Blog Archive

About Me