Showing posts with label trans. Show all posts
Showing posts with label trans. Show all posts

Tuesday, March 27, 2012

Backup failed: Operating system error 112(error not found).

Hi,
I keep getting this error message for a trans.log backup.
Operating system error
112(error not found).
The disk has about 6GB space free, and the backup should only take up
about 550 MB, so I would think it is not space related but...
The disk is NTFS.
Any ideas?smeagol (carlamichelle1@.hotmail.com) writes:
> I keep getting this error message for a trans.log backup.
> Operating system error
> 112(error not found).
> The disk has about 6GB space free, and the backup should only take up
> about 550 MB, so I would think it is not space related but...

... but NET HELPMSG 112 says

There is not enough space on the disk.

> The disk is NTFS.
> Any ideas?

Not many. I would perform all sorts of sanity checks that you are looking
on the right disk, that the transaction log is small as you believe it
to be etc.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Did you ever get this sorted ?
I'm having the same problem and have heaps of free disk space ? :confused:sql

Sunday, February 12, 2012

Backing up trans log of system dbs

Guys,

Should the transaction log of the system databases be backed up and if so, how often should this be done, generally?

Currently, we are backing up the system databases daily. The transaction log of the system databases, however, is not backed up.

Recently, I was wondering what exactly could happen, which would imply that we need to back up the transaction log of the system databases.

As far as I understand, 'msdb' contains things like jobs, dts. As such, if no jobs/dts are added in the middle of the day, there is no need to back up the trans log of this db - there could even be no reason, in such case, to back this db up at all!

'master' db would change if we add/modify objects/properties and so on ... so unless many changes are made, no need for backing up its trans log.

Having said that, could anyone enlighten me as to whether it is necessary to back up the transaction log of the system dbs and/or what it depends on and/or when it is suggested to do so?

Thanks youBy default, master and msdb are set to simple recovery, so the transaction log backups would error out. I would strongly suggest not tampering with these databases. For myself, I back them up in full once a week to disk, and every night in full to tape. They are small by today's standards.|||Thanks Mcrowley