This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Grooming a cloud archive?

We are currently doing a continuous incremental cloud archive of a ~5TB repository on Azure. Is there any way to groom the archive? The archive is growing rather quickly, and it took about 6 days for the initial archive build. I'd rather not do a fresh new archive every month or so to keep the size down. Alternatively, a replication to an Azure d3 VM including needed disk space would cost several times more than our current setup per month. Is there any way to groom a cloud archive or otherwise manage its size?

Thanks in advance.

Parents
  • Hi Peter:
    Unfortunately not yet. We have a feature request in this respect. Just for the sake of precisions, archives are supposed to keep immutable data, thus should never be modified. However, if we would have a "long term storage" solution that would grow in a manner similar to an archive and could be "groomed" as you suggested, we would have a solution to address the issue you raised. Normally, this would be addressed by replication. However, due to the cloud hosting costs (that you already pointed out), it makes sense to explore the feasibility of such a solution.

Reply
  • Hi Peter:
    Unfortunately not yet. We have a feature request in this respect. Just for the sake of precisions, archives are supposed to keep immutable data, thus should never be modified. However, if we would have a "long term storage" solution that would grow in a manner similar to an archive and could be "groomed" as you suggested, we would have a solution to address the issue you raised. Normally, this would be addressed by replication. However, due to the cloud hosting costs (that you already pointed out), it makes sense to explore the feasibility of such a solution.

Children
No Data