Veritas NetBackup™ Release Notes
- About NetBackup 8.1.2
- New features, enhancements, and changes
- NetBackup 8.1.2 new features, changes, and enhancements
- Operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup API operational notes
- NetBackup Bare Metal Restore operational notes
- NetBackup with Veritas CloudPoint operational notes
- NetBackup database and application agent operational notes
- NetBackup internationalization and localization operational notes
- NetBackup for NDMP operational notes
- NetBackup SAN Client and Fibre Transport operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- NetBackup for VMware operational notes
- NetBackup for VMware operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
GET Policy API response may return an incorrect ScheduleType for policy schedules
When using the GET Policy API to read a policy with schedules, you may notice that the JSON response may have an incorrect value for ScheduleType in the policy schedules. For example:
If a Full Backup schedule in the policy is of the schedule type Calendar, the ScheduleType in the API response may be Frequency.
If a Transaction Log Backup schedule in the policy is of type Calendar, the ScheduleType in the API response may be null.
If you use the schedule detail in the JSON response payload as it is returned from the GET API while updating the policy via the PUT Policy API, it may result in an unexpected change in the schedule. For example, it may change from a Calendar schedule to a Frequency schedule. In certain cases the policy update may result in a validation error.
Note that this issue does not occur in all cases. For example, if a Full Backup schedule in the policy is of type Frequency, the GET Policy API returns the correct ScheduleType, that is,Frequency.
Workaround: If you choose to automate policy updates using the API, Veritas advises that you not use the schedule details from the GET API response in a PUT API request without verifying and modifying the ScheduleType to the desired value.