11-21-2017 11:19 AM
Doubts about how it works
Environment using CAS and two MBES. CAS-Server and MBES-SITE-A are on the same network and MBES-SITE-B is on a different network.
Both MBES are using DEDUP. MBES-SITE-A is the primary server where all backups are run. The primary servers are duplicates for MBES-SITE-B. There is a closed VPN between SiteA and SiteB.
The backup is done in SiteA, storing in DEDUP and duplicating to SiteB stored in DEDUP. In the first backup all data is sent because it is exactly the first backup.
1) In the next backups, the data that will be sent will be just the new data, correct? Or are all the data sent and when does the SiteB get the deduplication done?
A:
2) The "client side deduplication" is not valid for this scenario, correct?
A:
----
3) When defining disk for backup what is the optimal block size? When formatting the disk the default is 4096 bytes.
A:
4) In BackupExec when using DEDUP we have the "Data stream size", the default value is 512 KB. Can we reduce this number to the same size as the disk? In case not the option of 4096 bytes, but if we format and define 32 KB, we will have better performance?
A:
Solved! Go to Solution.
11-22-2017 02:44 AM
I had to check with a deduplication expert and the answers he gave were:
1) In the next backups, the data that will be sent will be just the new data, correct? Or are all the data sent and when does the SiteB get the deduplication done?
A: Yes it is just the new data that is sent
2) The "client side deduplication" is not valid for this scenario, correct?
A: The backup part (at Site A( can still use client side - it has nothing to do with the duplication part to Site B
----
3) When defining disk for backup what is the optimal block size? When formatting the disk the default is 4096 bytes.
A: format it with 64K
4) In BackupExec when using DEDUP we have the "Data stream size", the default value is 512 KB. Can we reduce this number to the same size as the disk? In case not the option of 4096 bytes, but if we format and define 32 KB, we will have better performance?
A: No to both parts
If you need more detail (and have a support agreement) you may be able to get more detailed info with a support case.
11-22-2017 02:44 AM
I had to check with a deduplication expert and the answers he gave were:
1) In the next backups, the data that will be sent will be just the new data, correct? Or are all the data sent and when does the SiteB get the deduplication done?
A: Yes it is just the new data that is sent
2) The "client side deduplication" is not valid for this scenario, correct?
A: The backup part (at Site A( can still use client side - it has nothing to do with the duplication part to Site B
----
3) When defining disk for backup what is the optimal block size? When formatting the disk the default is 4096 bytes.
A: format it with 64K
4) In BackupExec when using DEDUP we have the "Data stream size", the default value is 512 KB. Can we reduce this number to the same size as the disk? In case not the option of 4096 bytes, but if we format and define 32 KB, we will have better performance?
A: No to both parts
If you need more detail (and have a support agreement) you may be able to get more detailed info with a support case.
11-22-2017 11:04 AM
Many thanks for the answers, they helped me a lot.
So to perform backup and have better performance is 64k, very good.
4) What about the Data stream size, is it better to leave the default or change to 64k?
R:
11-22-2017 11:55 PM - edited 11-22-2017 11:59 PM
I thought I already answered that...
11-23-2017 03:04 AM
It was not very clear to me, but okay. Thank you very much for the help.
Fortifying helped their answers a lot.
Thank you.