NetWorker 19.7 Snapshot Management Integration Guide

Save set IDs and expiration policies

When NSM creates a snapshot, NSM generates a separate save set ID for each snapshot object specified in the Client resource. For example, a single physical snapshot can create save sets for F:\abc and G:\xyz if they both reside on the same LUN or managed volume. Each save set will have a separate save set ID, even if both save sets belong to the same client and both reside on the same LUN. F:\abc and G:\xyz cannot be on the same LUN.

During a clone operation to conventional storage media, NetWorker assigns a different clone ID to each cloned snapshot object.

By having two save set IDs, NSM manages the snapshot data separately from the cloned data. Each save set has an independent expiration policy, and when one save set expires, you can still use the other save set to perform a restore.