Hi Kavya,
For option one : there is no need to create a secondary copy and we can utilise something as extended retention on the same primary copy for full backup jobs. the only cost inolved will the storage cost assocaited with the Azure immutable library.
For option 2 : you will have to purchase the DD box which is expensive, if you already have a DD box then it would make sense. if you are looking to purchase a new DD box then you will have to consider the size of data on cloud, if it is huge, then purchasing the DD box will make sense and it would eliminate cloud storage cost and provide better deduplication (as its hardware based deduplication.)
For Example
I have 100 TB of data to be backed up.
In the long Run and never ending backups with daily schedules
- Azure immutable with 30 Days basic retention with DDB sealing is cost effective?
- one time purchase of DD is effective?
Also please help me decide on other parameters apart from COST, like Space, Dedup Parameters, Throughputs, Bandwidth, Network throttle
Hi Kavya,
Sealing the DDB will maintain the jobs twice the retention dates (Because on the sealed DDB Micro pruning does not work), so if we have 100TB of Data it might go till 200TB because twice the retention.
Whenever DDB is sealed, a new baseline is created which will consume twice the Library space.
In comparision with commvault deduplication, Data Domain will provide better deduplication savings because they have a dedicated hardware for it.
So till now cost, space , dedeuplication is all better with DD.
note:
DD is a one-time investment , whereas for cloud you will have to pay on a monthly basis
Throughput , Bandwidth and Networt throttle is solely dependent on the internet speeds, the highier the speeds the better the throughput.
note:
Micro pruning : Deletes the chunks as and when they are aged
Macro Pruning : Deletes the entire data when all the jobs are aged