Hello Swathy. Thanks for the feedback. We will try to enable it as default in our future videos. You can use subtitles option in the interim for old videos.
Hi Dilip, is it normal Exchange setup or DAG setup you are requesting for? Normal Exchange we can try (by creating one in lab) but DAG might be difficult as we do not have a lab setup for it and creating one will be difficult.
At 4:01 , if signatures are not present in destination DDB, then data is read and signatures are generated on source MA. But We already have the signatures on source MA, right? that we used to send to destination MA for comparison. So why are Signatures generated again?
@@CorpVault Signatures are already present with metadata on primary copy, (that are sent to secondary DDB). Now If secondary DDB doesn't have signature, data is read. Why are signatures generated again when data is read from disk if we already had the signatures??
Actually it is 200 now but It is a guideline to avoid performance issues when running DASH Copy but can be customized as desired (if all tick boxes match). These streams are used by backup and aux copy operations to access DDB using parallel data transfer operations.
Nice Video👍
Thank you 😊
Please add subtitles for all explanation. It will be helpful.
Hello Swathy. Thanks for the feedback. We will try to enable it as default in our future videos. You can use subtitles option in the interim for old videos.
Dear team please make a video of exchange backup configuration
Hi Dilip, is it normal Exchange setup or DAG setup you are requesting for? Normal Exchange we can try (by creating one in lab) but DAG might be difficult as we do not have a lab setup for it and creating one will be difficult.
@@CorpVault thanks for reply
At 4:01 , if signatures are not present in destination DDB, then data is read and signatures are generated on source MA. But We already have the signatures on source MA, right? that we used to send to destination MA for comparison.
So why are Signatures generated again?
The one you are looking at is 'Disk Read Optimized Copy' and it works in such way so your disk read is optimized and no load is there on the Disks.
@@CorpVault Signatures are already present with metadata on primary copy, (that are sent to secondary DDB). Now If secondary DDB doesn't have signature, data is read. Why are signatures generated again when data is read from disk if we already had the signatures??
Why we need to have 50 streams or less in storage policy?
Actually it is 200 now but It is a guideline to avoid performance issues when running DASH Copy but can be customized as desired (if all tick boxes match). These streams are used by backup and aux copy operations to access DDB using parallel data transfer operations.