Hello - I've posted on this before, the webgisdr utility failure at 11.0 due to a federated server web adaptor name 'agsfed' containing at least one letter in the word 'a-d-m-i-n'.
I am happy to report that issue seems to have been resolved. However, the utility is still failing, or rather, it is completing but not producing an output file:
D:\AeScripts\ArcEntAdminTools\webgisdr111\webgisdr>webgisdr --export --file D:\AeScripts\ArcEntAdminTools\webgisdr111\webgisdr\myfullsitebkup.properties
==================================================
Starting the WebGIS DR utility.
==================================================
The configuration and base backup time in the current Web GIS
-------------------------------------------------------------
Portal: https://myorg.net/portal at 5/23/23 5:47 PM
|
|-- Hosting Server: https://myorg.net/server at 5/23/23 5:47 PM
| |
| |-- Relational Data Store: https://mydatastoreFQDN:2443/arcgis
|
|-- Federated Server: https://myorg.net/agsfed at 5/23/23 5:47 PM
Starting the backup process with the WebGIS DR utility.
Starting the backup for Portal for ArcGIS:
Url: https://myorg.net/portal.
Starting the backup for ArcGIS Server:
Url: https://myorg.net/server.
Starting the backup for ArcGIS Server:
Url: https://myorg.net/agsfed.
Starting the backup for Relational ArcGIS Data Store:
Url: https://mydatastoreFQDN:2443/arcgis.
The following ArcGIS Server has been backed up successfully:
Url: https://myorg.net/agsfed.
The following ArcGIS Server has been backed up successfully:
Url: https://myorg.net/server.
The backup of ArcGIS Server has completed in 00hr:02min:08sec.
The following Portal for ArcGIS has been backed up successfully:
Url: https://myorg.net/portal.
The backup of Portal for ArcGIS has taken 00hr:09min:02sec.
The following Relational ArcGIS Data Store has been backed up successfully:
Url: https://mydatastoreFQDN:2443/arcgis.
The backup of Relational ArcGIS Data Store has completed in 00hr:10min:31sec.
Failed to back up Portal for ArcGIS.
Exiting the WebGIS DR utility.
Any ideas? The output says the portal has been backed up successfully and yet the utility still fails to produce the backup file. Its a file share type backup, all of my shares privileges are in place, Java Home environment is in place....
Thanks,
David
Solved! Go to Solution.
Good morning. @ChristopherPawlyszyn was able to supply some internal postgres command options that enabled me to remove these orphan items from the portals' internal postgres gwdb database. I was then able to successfully complete a webgis dr backup.
As a support item, I was asked not to publicize the method for removing orphaned items as it is a bit risky. If others encounter this issue, I'd suggest reaching out to support.
Are you able to review the Portal for ArcGIS logs following the backup failure? I suspect that there are some item IDs that are returned as unable to be exported, which leads to a success with warnings as opposed to a success. If that's the case, we can look at options to remove those corrupt items to get a successful backup created.
Hi @ChristopherPawlyszyn - thanks for the feedback. Yes, I have 2 orphaned items in my content. One is for a hosted feature layer view that no longer exists, and one is for a reference to a geocoder from my federated site. Both items were incorrectly deleted, but in the past (at 10.9.1) the backup would complete with warnings.
Here is the warning:
.....
The following Portal for ArcGIS has been backed up successfully:
During the export operation, some items could not be exported because they appear to be missing from the content directory. Check the portal logs and review the Why do I receive an error about a missing item when creating a backup of my portal? section in the Common Problems and Solutions documentation for more information.
.....
The items do appear in my content - i.e. ..../sharing/rest/content/users/.... as:
Items | ||||
ID - Title | Owner | Type | Size | Uploaded |
19e427fb218442c2be32f77be701f019 - null | me_portal | null | 66 | Nov 20, 2018 |
3d30e4cc6f8c4fb5b0b41dcdb7bec1e5 - null | me_portal | null | 0 | Jul 15, 2021 |
but like the warning says, they are missing. When I try to remove the items via the rest api, this is the json return:
{
"results": [
{
"itemId": "19e427fb218442c2be32f77be701f019",
"success": false,
"error": {
"code": 500,
"message": "Unable to delete item: https://myorg.net/agsfed/admin/GpServices/ScpaWebMap/GPServer"
}
}
]
}
{
"results": [
{
"itemId": "3d30e4cc6f8c4fb5b0b41dcdb7bec1e5",
"success": false,
"error": {
"code": 500,
"message": "Unable to delete item: https://myorg.net/server/rest/services/Hosted/BusStopView2/FeatureServer"
}
}
]
}
So yes, they are truly orphaned . . . .
Thanks again,
David
Good morning. @ChristopherPawlyszyn was able to supply some internal postgres command options that enabled me to remove these orphan items from the portals' internal postgres gwdb database. I was then able to successfully complete a webgis dr backup.
As a support item, I was asked not to publicize the method for removing orphaned items as it is a bit risky. If others encounter this issue, I'd suggest reaching out to support.