Skip to main content

Error : Full Backup Failed for server ,, due to Log File is Full

After New Installation of SQL Server database will be in Full Recovery Mode by default. When our Application Goes Live and Transaction started processing we should have a proper Backup-DR plan otherwise We can face below error in SQL server in future. Because it is necessary to Truncate the TLOG in Full Recovery Mode.




Error:

Full Back up failed for Server 0.0.0.0'.  (Microsoft.SqlServer.SmoExtended)
The transaction log for database '<dbname>' is full due to 'LOG_BACKUP'.  (Microsoft SQL Server, Error: 9002)


Solution:

 1.) 1st take the Transaction Log Backup.
 2.) If you have permission to shrink the Database just shrink Log File till the initial size.
 3.) Finally now try to take the Full backup. It will definitely work.



Note: - If there is fixed size of Log File just put simple as auto growth with 10% .

Comments

Popular posts from this blog

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.)    Creation of Application/Proxy user where Application is hosted. 2.)    Give appropriate access to the user. 3.)    Create Database Login user on database. 4.)    Authenticate User and provide credential on IIS. 5.)    Then Configure web.config on Application.

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription