-
- Expert
- Posts: 206
- Liked: 14 times
- Joined: Jul 23, 2013 9:14 am
- Full Name: Dazza
- Contact:
Exagrid Copy Jobs and Compression
We have backup jobs going to Exagrid with compression set to "Dedupe-friendly" and storage optimisation at 1MB, and this is achieving some compression of x1.4. We then have backup copy jobs for this data to object storage with compression set to AUTO to 'keep the existing compression level'. However, the backup copy job is showing 0 compression (x1). Why is this? And should the backup copy job be changed to "optimal" compression?
-
- Veeam Software
- Posts: 1865
- Liked: 452 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Exagrid Copy Jobs and Compression
Hi Dazza,
Backup copies work by reading the source backups, which are already compressed and deduped; when the data is sent over via the Backup Copy, there just isn't much for the compression algorithm to work on so there likely isn't going to be a meaningful change you can make here since Veeam's inline dedup and compression will already have done most of its work.
So I think nothing to really change here; you can test with increasing the compression level, but I'm not confident you will see significant changes here.
Backup copies work by reading the source backups, which are already compressed and deduped; when the data is sent over via the Backup Copy, there just isn't much for the compression algorithm to work on so there likely isn't going to be a meaningful change you can make here since Veeam's inline dedup and compression will already have done most of its work.
So I think nothing to really change here; you can test with increasing the compression level, but I'm not confident you will see significant changes here.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Semrush [Bot] and 17 guests