Hello,
Testing the upgrade from ArcGIS Enterprise 11.3 running on Windows Server 2022 to 11.4 and I am facing an issue after having migrated my tileCache datastore to objectStore using the `MigrateSceneServices` utility.
Here is the workflow:
- From 11.3, upgrade to 11.4 OK
- Export webgisdr backup OK
- Import webgisdr backup OK
- Upgrade scene services using `MigrateSceneServices` utility: OK
- Update the webgisdr.properties to INCLUDE_OBJECT_STORE_CACHES = true and INCLUDE_SCENE_TILES_CACHES = false
- Run the webgisdr export
It systematically fails after 24 hours... (before it was done in 1 hour !):
The tileCache was about 29 Go and composed of 20 scene services (mainly meshes).
Anybody else faced the same issue ?
Thanks,
Nicolas
/cc @JonathanQuinn
Solved! Go to Solution.
Seems like it is still not fixed at 12.0 😕
https://content.esri.com/support/downloads/other_/120-issuesaddressedlist_11192025.pdf
Hi there,
We just upgraded from 11.3 to 11.5 and migrated our tileCache to object Store.
Our WebGIS DR backups have gone from just over 8 hours to approximately 87 hours. Same data volume, same 3D content.
11.3 with Tile Cache:
2026-03-24 21:00:16 INFO [main] com.esri.arcgis.webgis.client.WebGISDR - Starting the WebGIS DR utility.
2026-03-25 05:13:39 INFO [main] com.esri.arcgis.webgis.client.WebGISDR - The WebGIS DR utility completed successfully.
11.5 With Object Store:
2026-03-29 19:32:30 INFO [main] com.esri.arcgis.webgis.client.WebGISDR - Starting the WebGIS DR utility.
2026-04-02 11:19:36 INFO [main] com.esri.arcgis.webgis.client.WebGISDR - The WebGIS DR utility completed successfully.
Clearly this is untenable. It is a business risk as we cannot finish a backup over the weekend and having WebGIS DR running for half of the week is not ideal.
@JonathanQuinn can we please get some information about when this might be improved. You just had Dev Summit, was it discussed there?Thanks,
Marc
@Marc_Graham I´d recommend opening a case in My Esri. You can escalate the case if needed.
Yes please! Ask to be attached to BUG-000173313 and then escalate to complain how critical it is ! It’s still not fixed in 12.1 so already 3 versions after it’s been posted here. Need more users complaining I guess!
We have done this also.
Very frustrating situation.