Well, since the loading of the backups was so slow I just assumed restoring would be causing the same bandwidth troubles, so i never went down that path and hopped straight on the restore appliance option ... sorry about that
Both work arounds where not really an option, but your previous post did get me thinking.
I was running the console on the server in the Datacenter so restore paths where like this:
- Launched restore, backup files are mounted to the DC Server, (resulted in 15 minutes waiting time before I could select files)
- Restored files which was done by the Mount server (which also is the proxy) and acceptable speeds
So now I've done a test where I installed the console on a computer in the location and this indeed reduced the initial loading times drastically. To get to the file select view is just a minute or so.
I always assumed that a full install would be required to work with the backup files, so now I just installed the console on the proxy which is a good solution for us. Maybe there can be an option when deploying the proxy that the console is also installed (with a optional tick-box, check to also deploy the console) ?