When modifying the WORM retention period, existing policies must be checked for incompatible WORM retention periods.

Problem

When modifying the WORM retention period, existing policies must be checked for incompatible WORM retention periods.

Error Message

Backup Job:

Critical bptm (pid=15921) Failed to validate WORM properties for LSU: error 2060064:WORM invalid min
Critical bptm (pid=15921) image open failed: error 2060064: WORM invalid min
Info bptm (pid=15921) EXITING with status 88 <----------
Info dbclient (pid=24859) done. status: 88: Open Storage WORM lock error
end writing
OpenStorage WORM lock error.  (88)

OR

Critical bptm (pid=23268) Failed to validate WORM properties for LSU: error 2060065:WORM invalid max
Critical bptm (pid=23268) image open failed: error 2060065: WORM invalid max
Info bptm (pid=23268) EXITING with status 88 <----------
Info bpbkar (pid=23250) done
Info bpbkar (pid=0) done. status: 88: Open Storage WORM lock error
end writing
OpenStorage WORM lock error.  (88)
 

Cause

If the WORM retention period is modified after its initial configuration, any backup policy using the WORM storage unit with a retention level outside this new value can cause the backup to fail.

NetBackup Policy Backups can fail if one or more of these configurations are set.

1. If WORM is initially enabled and the minimum or maximum retention values are later changed.
2. If WORM is enabled for a storage unit with existing policies and then later changed.

NetBackup backup policies must specify a retention period that falls within the configured minimum, 14 days or less and maximum, 14 days or more, allowed for the storage unit. If WORM is enabled for the first time or the existing WORM retention period is modified, backups for existing policies will fail if their retention does not meet the requirements. This change would affect all backup policy types being directed to that WORM storage unit.

The issue applies to the all versions of NetBackup that support WORM storage.

Solution

 When directing backups to WORM storage, examine the existing backup policies and policy schedules to make certain there are not any incompatible WORM retention periods set.