Best way to handle Retention Set in a Back-end license environment.

fredric

ADSM.ORG Member
Joined
Aug 23, 2007
Messages
42
Reaction score
0
Points
0
PREDATAR Control23

We will begin with Retention Set to tape due to Ransomware threats.
When the Retention Sets data is copied to tape it's hydrated, it will take more space and licenses when the archived data become inactive.
We will perform a weekly offline backup(Retention Sets) of VMware VM's to tape. Today we store the VM backups 45 days(1/day) in a container pool. As long the data is active in the container pool, there are no extra licenses for the archive data. But after a while more and more data will be inactive, special after the retention of the backup data expire(45 days). We will archive the data up to 6 months, so it can be quick much inactive data.
Is it better to extend the retention(number of backups to keep) for the ordinary backup to the container pool (will require some extra Back-end licenses and some archive licenses) or only buy many archive licenses? The archive licenses are cheaper (about 1/5).
I know it depand on the change rate off the data etc. but does anyone have any similair experince?
 
Top