Improving Backup Performance using SQL native methodology I am trying to gather some stats on comparison of run time vs performance between Litespeed backups and sql native backups. As we are no longer going to use Lite Speed [even though i personally loved that SW], have to gather metrics how SQL will perform using native compression backup]

So i am looking for a way to reduce CPU usage to X % while taking native compression backups. In Litespeed we just specified this option in advanced tabs and saw everything running fine. I am aware of resource governor, but due to some constraints not able to use it. Will need to work on that. But is there a better and smarter way to do this. Please suggest

Edit.. Have to add, as per security and company policies we cannot use third party or external SP's to be created. I saw this can be achieved using OLa 's script as well, but we wont get approvals to introduce this :(
Resource Governor can control the resource consumption of a backup.

By default, backing up using compression significantly increases CPU
usage, and the additional CPU consumed by the compression process can
adversely impact concurrent operations. Therefore, you might want to
create a low-priority compressed backup in a session whose CPU usage
is limited byResource Governor when CPU contention occurs. This topic
presents a scenario that classifies the sessions of a particular SQL
Server user by mapping them to a Resource Governor workload group that
limits CPU usage in such cases.

Use Resource Governor to Limit CPU Usage by Backup Compression (Transact-SQL)