July 26, 2015 at 4:48 pm
I am wanting to use backup compression on a few sql servers (2008R2 and 2012).
I have never touched compression before and always just gone with the default.
I use Ola Hallengren's scripts to do the backups which, if not specifically specified, will use the server default.
Backups (FULL and LOG) have been happening successfully on these servers for years.
So my question is: Is there anything else I need to know?
Is it simply a case of turning it on?
SQL won't care that the previous backup in the set was uncompressed or that the hourly transaction log backups previously taken were uncompressed?
Restore statements (T-SQL) will be identical?
From everything I am reading it is simply a case of setting the configuration and acting like nothing changed but I just wanted to be 100% certain.
1 of the servers is a SharePoint backend.
All of the backup files from all servers are picked up by Commvault backup system.
I doubt either of these last 2 points make a shred of difference but I just included them for completeness in case it raises anything.
Thanks.
July 26, 2015 at 5:24 pm
Just turn the compression on, no other changes needed although you might want to check if Commvault is also compressing the files.
😎
July 26, 2015 at 5:46 pm
Cool thanks.
July 27, 2015 at 4:38 am
Yeah, compressing a compressed file, I've found, results in a bigger file. So watch commvault.
Nothing special needed with native backup compression other than telling it to do it.
"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
July 27, 2015 at 1:54 pm
Thanks, I've sent them an email asking if there is anything I should be wary of.
Will post back their advice.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply