+4We have a new environment with HSX setup; we have a single copy of the data going to HSX and we retained some backups for 5 years. I am sceptical of this design; apart from not following the best practices of a secondary copy; what are the impacts of storing this data for long term in the same copy? Would it have any impact on DDB (although with design we do have ddb split across multiple nodes); would the chances of corruption of this data would be more?
+9Hi Rajeev,
You are correct in that this is wouldn’t be considered best practice without having a secondary copy of a different medium (eg. tape, cloud). At the very least you have extended retention configured for your monthly/yearly backup operations which does help. However, you’re not allowing yourself any leeway if a physical disaster were to occur, let alone corruption.
Do you have any plans at all to have a secondary copy?
With regards to deduplication, there is some level of impact as enabling extended retention rules on a deduplication-enabled plan/copy might increase the DDB size.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
