I need help to understand how networker expiration process works.
We are executing an incremental backup every working day (retention 1 week) and a full backup on the weekend (retention 2 months) . So, the expiration of our incremental backups depends on the retention time and the cycle depedences.
We clone the backups with the same retention time of the original.
When the expiration date (clretent) is reached, the ssids can NOT expire because they have cycle dependences (future incrementals not expired) but we see that all instances of the ssid are marked recyclable except one of them.
Sometimes the instance of the saveset that remain alive because the dependences is the original instance, but other times is a clone instance.
Can somebody tell me how nsrim works and how it chooses the instance to expire?
Thanks.
We are executing an incremental backup every working day (retention 1 week) and a full backup on the weekend (retention 2 months) . So, the expiration of our incremental backups depends on the retention time and the cycle depedences.
We clone the backups with the same retention time of the original.
When the expiration date (clretent) is reached, the ssids can NOT expire because they have cycle dependences (future incrementals not expired) but we see that all instances of the ssid are marked recyclable except one of them.
Sometimes the instance of the saveset that remain alive because the dependences is the original instance, but other times is a clone instance.
Can somebody tell me how nsrim works and how it chooses the instance to expire?
Thanks.