ArcGIS Enterprise 10.5 backup with WebGIS DR - Failed to generate the ArcGIS Server token from the portal

[AlessandroValra]

Hello,

I need to do a full backup of an AGE 10.5 using the WebGIS DR tool.

The final aim is restoring it on a different machine as described in the guide Migrate to a new machine in ArcGIS Enterprise using the WebGIS DR tool 

My server OS is Windows 2008 R2 64bit.

I am following Create an ArcGIS Enterprise backup—Portal for ArcGIS (10.5.x) | ArcGIS Enterprise.

I have configured my webgis.properties file (called "webgisdir_BAK.properies"), and then I launch from the CMD the command:

   webgisdr --export --file "C:\Program Files\ArcGIS\Portal\tools\webgisdir\webgisdir_BAK.properies"

Unfortunately, I receive the following error:

   Failed to generate the ArcGIS Server token from the portal https://svksi058a.globalnt.it:7443/arcgis/sharing.

   Failed to get the configuration of the web GIS.

   Stopping the webgisdr utility

I attach the encrypted "webgisdir_BAK.properies" and the "webgisdr.log".

I also tried to set the ArcGIS Server to HTTPS Only and have my Web Adaptor allowing administrative access as suggested in Portal Backup with webgisdr: Server is not started, but still I had no luck.

I also opened a case to Esri meanwhile but as this is an important operation, I wanted to post my problem here to see if I had more chances to solve it.

Thanks in advance.

[AlessandroValra]

I successfully exported the server and portal sites with the exportSites methods in the same folder where I would have placed the output of the webgis dr without problems...

[AlessandroValra]

Harrold Sompotan‌

given that mine is just a migration to a new machine and the deployment is very basic with few (3) users, would you suggest going with these methods?

In my opinion, they seem rather straight forward, although I never tried them.

Thanks in advance for any advice.

[AlessandroValra]

Replying to myself. I tried the export/import site from one machine to another and I had issues because in the new machine I came up having a Portal federated with a server with the hostname of the old machine. I managed to fix it but this is of course a good method to recover from a disaster but not to migrate...