I tried CASO, and although it's a really good product, having sites in Africa and remote locations in Asia meant this wasn't working well, and I uninstalled it.
What's happening here is probably exactly what's happening with me...slow links.
What I did was set up all the servers to be distributed. They kept control of their own databases and media set information (hardware too), and simply reported back to the CASO server with job status. In theory, great idea. In practice, although I set it up as such, my CASO server STILL grabbed the details I wanted kept locally for itself on the majority of servers! Leading to failed backups, jobs not running etc.
If you still want to use it, I would recommend the following:
1. Open up BEutility.exe, and go to your server. You can right-click it and choose to localise all your data (database/media informatione etc). let it run. if it gives you an error, go to #2...
2. Go into Media Servers on your CASO server, right-click your server, and choose the option to keep your data on your remote server. This will push the information back again. If this doesn't work...
3. Remove your server from the CASO, and readd it, making sure that you select the option to keep details local.
Like I said, nice in theory, but in practice it became a nightmare. Took me 1.5 weeks to get 34 sites working again after I pulled it out, and I still have legacy information doing the rounds.
