Hello all,
I have a DataDomain as backup storage and I've been testing different configurations. What surprised me is size of backup when using DDBoost vs CIFS protocol.
Test 1, Active full backup
VM size 868GB
to DDBoost device
Read 44.1GB
Transfered 33.8GB
Bacsk size 32.9GB
to CIFS device
Read 44.1GB
Transfered 9.1GB
Backup size 8.9GB
all configuration (compression, etc) is the same for both jobs, I've triple-checked it. I've tested this for different VMs and run it several times. Results are still the same. Backup to CIFS is always much smaller, then to DDBoost device.
Does anyone know why is that? Shouldn't be DDBoost more efficient?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Apr 04, 2018 6:33 am
- Full Name: backuper
- Contact:
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: DDBoost vs CIFS backup size
Hello backuper.
To see the difference disable deduplication and compression for backup job targeted at Data Domain and make a few test runs. Cheers!
To see the difference disable deduplication and compression for backup job targeted at Data Domain and make a few test runs. Cheers!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Apr 04, 2018 6:33 am
- Full Name: backuper
- Contact:
Re: DDBoost vs CIFS backup size
Hello Dima,
I've disabled dedup and compression and only minor change in size when backing up to DDBoost device. CIFS is still much smaller. I've tested also different VMs and results are always the same CIFS backup being smaller.
So it seems, DDBoost is really not that important with Veeam, or is it?
I've disabled dedup and compression and only minor change in size when backing up to DDBoost device. CIFS is still much smaller. I've tested also different VMs and results are always the same CIFS backup being smaller.
So it seems, DDBoost is really not that important with Veeam, or is it?
Who is online
Users browsing this forum: Semrush [Bot] and 74 guests