Migrating NetBackup 8.2 Asset DB to NetBackup 8.3 Asset Service
Several NetBackup 8.2 Asset DB endpoints are discontinued or deprecated with the introduction of Asset Service in NetBackup 8.3.
The following table provides the mapping functionality in NetBackup 8.3 for the discontinued or deprecated APIs.
Table: Migrating NetBackup 8.2 Asset DB endpoints to NetBackup 8.3 Asset Service endpoints
Serial number / NetBackup 8.2 Asset DB endpoint / State in NetBackup 8.3 | Similar NetBackup 8.3 Asset Service endpoint | ||
|---|---|---|---|
1 GET /assets Discontinued | Execution of Named Query assets with workloads vmware, rhv, cloud should give the similar behavior. This also can be achieved with workload context GET /asset-service/workloads/{workload}/assets Where the {workload} should be vmware, rhv, cloud. The following example requests a payload for Named Query assets with multiple workloads. assets Named Query request payload {
"data": {
"type": "query",
"attributes": {
"queryName": "assets",
"workloads": [
"vmware", "rhv", "cloud"
]
}
}
} | ||
2 POST /assets Discontinued | Assets can be created by using the Named Query create-assets for workloads vmware, rhv, cloud. Assets can be updated by using the Named Query update-assets for workloads vmware, rhv, cloud. Assets can also be created or updated (if not present) by using the Named Query create-or-update-assets for workloads vmware, rhv, cloud. Note: These Named Queries are allowed to be executed only with one workload. Therefore you can not create/update assets across the workloads in single Named Query execution. Refer to the request payload schemas for the specific workload and availability of the Named Query. For example, to get the schema for "create-assets" Named Query for workload rhv: GET /asset-service/workloads/rhv/schemas?filter=schemaName eq 'create-assets' | ||
3 GET /assets/{GUID} Discontinued | GET /asset-service/workloads/{workload}/assets/{assetId} Where the {workload} should be vmware, rhv, cloud. | ||
4 GET /assets/{GUID}/asset-groups Discontinued | Asset group information for an asset can be fetched by executing: GET /asset-service/workloads/{workload}/assets/{assetId}/asset-groups Where the {workload} should be vmware, rhv | ||
5 POST /assets/asset-cleanup Discontinued | Execution of Named Query delete-assets for workloads vmware, rhv, cloud should clean the assets. Note: Please review the workload specific schemas for more details. | ||
6 POST /asset-groups Discontinued | Assets can be created by using the Named Query create-assets for workloads vmware, rhv. Assets can be updated by using the Named Query update-assets for workloads vmware, rhv. | ||
7 POST /preview-asset-group Discontinued | GET /asset-service/workloads/{workload}/assets?filter=assetType eq 'vmGroup'`) Where the {workload} should be vmware, rhv. | ||
8 PATCH /asset-groups/{assetGroupGuid} Discontinued | Assets can be updated by using Named Query update-assets for workloads vmware, rhv. | ||
9 DELETE /asset-groups/{assetGroupGuid} Discontinued | Execution of Named Query delete-assets should give the similar behavior. | ||
10 GET /asset-groups Deprecated | This end point will continue functioning in NetBackup 8.3. In NetBackup 8.3, this also can achieved by new endpoint GET /asset-service/workloads/{workload}/assets?filter=assetType eq 'vmGroup'`) Where the {workload} should be vmware, rhv. | ||
11 GET /asset-groups/{assetGroupGuid} Deprecated | This end point will continue functioning in NetBackup 8.3. In NetBackup 8.3, Asset group information for an asset can also be fetched by executing: GET /asset-service/workloads/{workload}/assets/{assetId} Where the {workload} should be vmware, rhv | ||