Ola MS SQL backup solution with compressed option

Hi,

We are using ola backup solution right now and some of the SQL server we are using is SQL 2014 now, so we can make use of the native compression of backup in SQL 2014 right now.

Can ola backup solution take advantage of it? I just added compress = Y option for it, anyway to get the most out of it?
LVL 1
marrowyungSenior Technical architecture (Data)Asked:
Who is Participating?
 
Vitor MontalvãoConnect With a Mentor MSSQL Senior EngineerCommented:
Can ola backup solution take advantage of it?
Yes. As it is in his wepage:
Compress

Compress the backup. If no value is specified, then the backup compression default in sys.configurations is used.


Value Description
NULL Use the backup compression default in sys.configurations. This is the default.
Y         Compress the backup.
N        Do not compress the backup.

The Compress option in DatabaseBackup uses the COMPRESSION and NO_COMPRESSION options in the SQL Server BACKUP command.


any option to make sure that unused log is truncated after ola log backup ?
By definition a transaction log backup will allways truncate the log so you don't need to worry about that.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
also we use this option for log backup using ola:

@BackupType = 'LOG',
@Compress = 'Y',
@CleanupTime = '192'

Open in new window


any option to make sure that unused log is truncated after ola log backup ?
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
hi,

wait, we are already doing this, but no other way to make it compress further ? I heard that compression is native to SQL 2014, right?

what is the diff. ?


I knew if we use SQL safe backup pro or litespeed, we can control it further.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
wait, we are already doing this, but no other way to make it compress further ?
No. Usually you can't compress a compressed file. I mean, technically you can but gain nothing with that.
You can see the compression ratio by running the following command:
USE msdb
GO
SELECT backup_size/compressed_backup_size AS CompressRatio
FROM backupset;

Open in new window


I heard that compression is native to SQL 2014, right?
Backup compression is native since SQL Server 2008R2. By default is off but you can turn it on for all databases by configuring it:
USE master;
GO
EXEC sp_configure ‘backup compression default’, '1';
RECONFIGURE WITH OVERRIDE;

Open in new window


I knew if we use SQL safe backup pro or litespeed, we can control it further.
How's that?
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
"I knew if we use SQL safe backup pro or litespeed, we can control it further.
How's that?

ola allow compress level, actually is the litespeed compression level, from 1 to 8.

my EXEC sp_configure ‘backup compression default’, '1'; is all 1. it is running.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ola's script doesn't work with Litespeed. In SQL Server you only have compression ON or OFF and when it's ON it should compress at the maximum level possible. Why do someone want only to compress half or whatever?

my EXEC sp_configure ‘backup compression default’, '1'; is all 1. it is running.
Good.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
"Why do someone want only to compress half or whatever?"

faster..
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
If you compress at maximum level should be more faster since it will write less bits in the disk. However it may impact the CPU usage but usually you only perform regular backups during less activities window so the CPU consumption should be irrelevant.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
so can't control/compress it further by using ola anyway ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
As far as I know, you can't.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
ok. tks.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
tks victor you are great.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
hi,

right now we ran ola solution in SQL 2012 DR server in AOG group but the ola index rebuild solution seems finish in 1 sec. which is not right.

any parameter we should run ola in SQL 2014 DR ? can't run on DR anyway as it is read only?

the message from ola on that AOG secondary:


Date and time: 2017-03-30 17:31:31
Database: [PlazaWAS]
Status: ONLINE
Standby: No
Updateability: READ_WRITE
User access: MULTI_USER
Is accessible: Yes
Recovery model: FULL
Availability group: WASAG
Availability group role: SECONDARY
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
can't run on DR anyway as it is read only?
No, you can't run a reindex job in a secondary replica. Reindex needs to be run only in the Primary Replica because it needs to move datapages and can't do that on read only databases.
0
 
marrowyungSenior Technical architecture (Data)Author Commented:
tks. that's why.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.