When do changes to storage lifecycle policies become effective?

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:

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.