Skip to main content
Question

Data aging on old WORM enabled primary copy

  • March 10, 2026
  • 0 replies
  • 2 views

Forum|alt.badge.img+3

Hello Community,
 

we recently switched our primary copy to an object lock (WORM) enabled storage pool.

After a while we noticed that the storage space will not be sufficient regarding the additional space required for deduplication.

Therefore we switched all clients to a new primary copy without object lock to let the data age out before going back to locked storage.

The data on the locked copy should now already age out but one cycle is stuck with “BASIC_CYCLES” because the copy was created with 1 cycle retention initially.

 

Is there an easy way to clean up this cycle for all clients?

I could already free up the jobs from our VSA backups by disabling the subclients and enabling the option to ignore cycle retention on disabled subclients, but this is not practical for all other clients.

 

Thanks in advance for your thoughts.