|
|
For the changes to become effective for a backlog of jobs, it may be necessary to cancel the applicable backup or duplication jobs.
When the nbstl command is used to alter an existing version, those changes may not become effective immediately. The images that are managed by the storage lifecycle policy version that was altered may already belong to a duplication job that is Active or Queued, as seen in the Activity Monitor. Once a duplication job is queued, the characteristics (storage lifecycle policy attributes) are fixed for that job and subsequent changes to the definition have no effect. To make changes effective for a backlog of images, cancel the duplication jobs. The storage lifecycle policy manager creates and submits new duplication jobs for those images, using the changes to the configuration.
The following are conditions under which changes to an existing version are not immediately effective:
Changes to a backup destination have no effect because the backup job is already underway or completed.
Changes to a duplication destination do not affect the image copies that previous duplication jobs created.
Changes to a duplication destination do not affect the image copies that have already been submitted and are currently represented by a duplication job in the Activity Monitor, whether it be Active or Queued. If you want your changes to apply to those active duplication jobs, you need to cancel the applicable duplication jobs. Once canceled, nbstserv re-forms and re-submits new duplication jobs for these image copies, using the changes to the appropriate version of the storage lifecycle policy.
Changes to a duplication destination affect the image copies that have not yet been created and have not yet been submitted. That is, they are not yet represented by a duplication job in the Activity Monitor). Your changes become effective for the next duplication session. Whenever nbstserv begins a new session, it re-reads the definitions for processing instructions.
If a duplication job does not complete successfully, unfinished images in the job are submitted as part of a new job. Changes to the version affect the resubmitted job.