I recently came across a situation where one of the drives in production server is almost full.
There are two large databases and they were backed up daily once. No other backup plans were in place. That drive is filled by the log files of these two databases (~200GB each).
This has happened because the databases were in full recovery mode but transaction logs are not backed up.
Here are the steps to solve this issue:
- Take a full backup of the databases (Not required but as a precaution)
- Set the recovery model to simple
- Shrink the log file
- Set the recovery model back to full
- Take a full backup
- Setup a job to backup transaction log frequently
Note: Shrinking the log file is not a good option to do it regularly. I had to use the shrinking option because this is one-off and the log file has grown that big is due to lack of log backups.
Here is the script to perform the above tasks:
-- Full Backup
backup database TestDB to disk = N'H:\Backup\TestDB_20150922_1308.bak'
with name = N'TestDB-Full Database Backup', compression, stats = 10
alter database TestDB
set recovery simple;
-- See the name of the log file
-- shrink the truncated log file to 100 mb.
dbcc shrinkfile (TestDB_log, 100);
-- reset the database recovery model.
alter database TestDB
set recovery full;
There are three types of backups:
- Full backup
- Differential backup
- Transaction log backup
A full backup contains all the data in a specific database or set of file groups or files, and also enough log to allow for recovering that data. It is the base of both differential backup and transaction log backup.
A “Differential” backup is a backup of any extent that has changed since the last “Full” backup was created.
Each time a new differential backup created it will contain every extent changed since the last full backup (NOT since the last differential backup).
When the database needs to be restored to the most recent time the user only need to restore the full backup and the most recent differential backup. All of the other differential backups can be ignored.
Transaction log backup
The transaction log is a serial record of all the transactions that have been performed against the database since the last transaction log back up.
With transaction log backups, you can recover the database to a specific point in time.
Database should be set to “Full” or “Bulk-logged” recovery model for “Transaction Log” backups.
If the database is set to the “Bulk-logged” recovery model and a bulk operation was issued, then the entire transaction log needs to be restored.
A transaction log backup allows the user to back up the active part of the transaction log. So after a “Full” or “Differential” backup the transaction log backup will have any transactions that were created after those other backups completed. After the transaction log backup is issued, the space within the transaction log can be reused for other processes. If a transaction log backup is not taken, the transaction log will continue to grow.