May 21, 2014 at 6:33 am
I have a SQL Server 2008 and a management plan that backs up all user databases. Recently, the backups are a fraction of what the good backup is. For instance, I have a database that I just backed manually and it is ~1749 kB, but my backup fired from the management plan is ~194 kB. When I look back through the logs plan executed successfully.
Any help would be greatly appreciated.
Jim
May 21, 2014 at 6:37 am
Is the maintenance plan doing compressed backups?
Is the maintenance plan doing differential backups?
Is the maintenance plan striping the backup over multiple files?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 21, 2014 at 6:38 am
There are two ways:
One you can run RESTORE VERIFYONLY command to check and verify the backup.
Second you can restore the backup in test environment.
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
May 21, 2014 at 7:23 am
RESTORE VERIFY FROM DISK = '<backup_file_location>' returns:
The backup set on file 1 is valid.
This is a full backup
We are not backing up to multiple files.
May 21, 2014 at 7:24 am
GilaMonster (5/21/2014)
Is the maintenance plan doing compressed backups?Is the maintenance plan doing differential backups?
Is the maintenance plan striping the backup over multiple files?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 21, 2014 at 8:02 am
I really don't know what you mean, so here it is:
ON compression
These are FULL backups
NO we are not backing up to multiple files,
Our database use two files (Data and TransactionLog)
May 21, 2014 at 9:19 am
Run:
RESTORE HEADERONLY FROM DISK = '<backup_file_location>';
and see if the backups are compressed.
May 21, 2014 at 11:40 am
James Mace (5/21/2014)
I really don't know what you mean, so here it is:ON compression
These are FULL backups
NO we are not backing up to multiple files,
Our database use two files (Data and TransactionLog)
Have you tried to restore that backup on a Dev environment? If not, do it. Inspect the database and run a DBCC command.
After all, backups are useless if you don't frequently test those with an actual restore.
I do also recommend you to implement Ola's maintenance solution.[/url] It includes backups and provides error log and script capabilities, plus is free!
May 21, 2014 at 1:08 pm
Maybe there's been a recent data removal. That would shrink the size of the backups.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 21, 2014 at 11:50 pm
1. check is it really a full backup?
2. check for compression option in maintenance plan
3. check for table data in last in case of nothing solve the purpose(previous backup after restoring on test environment with current table)
May 22, 2014 at 12:16 pm
I asked our development team about this issue and they added 2 tables for document management unbeknownst to the DBAs; Communication is key. Thanks for all your help.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply