Update Blog “getting-started-with-hpe-greenlake-api-for-backup-and-recovery”

rondharma · rondharma · commit 26c0dc7f77f7 · 2024-04-23T16:06:11.000-04:00
diff --git a/content/blog/getting-started-with-hpe-greenlake-api-for-backup-and-recovery.md b/content/blog/getting-started-with-hpe-greenlake-api-for-backup-and-recovery.md
@@ -123,7 +123,7 @@ H﻿ere is the list of the steps required to perform this use case using HPE Gre
 
 ![Discover deployed StoreOnce to create cloud protection store](/img/api-discover-storeonce.png)
 
-2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using t﻿he HPE GreenLake API f﻿or D﻿ata Services [set o﻿f APIs](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/guide/). Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I﻿ the c﻿opied value `﻿"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
+2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using t﻿he HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/operation/ListLocations/) f﻿or D﻿ata Services API set. Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I﻿ the c﻿opied value `﻿"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
 
 ![API to figure out the Azure storage location](/img/figure-out-storage-location.png)
 

-Original file line number
+Diff line change
 ![Discover deployed StoreOnce to create cloud protection store](/img/api-discover-storeonce.png)
 -2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using the HPE GreenLake API for Data Services [set of APIs](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/guide/). Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I the copied value `"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
 +2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using the HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/operation/ListLocations/) for Data Services API set. Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I the copied value `"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
 ![API to figure out the Azure storage location](/img/figure-out-storage-location.png)