Strange OWA timeouts?
By default the OWA extensions timeout a request to restore an item after 30 seconds. This was previously not configurable. In some environments this has posed a problem in the past, where some internal Windows API calls were taking a little bit of time to come back, with, for example, user->group membership details. A fix for this was introduced and can be used with version EV 8 and onwards The fix is slightly dependent on whether you are using Exchange 2003, or Exchange 2007. If it is Exchange 2003, edit your EVBackend.ini file to include a line like this : exch1.1.exchange.restorerequesttimeout=45 (where exch1 is the name of the Exchange Server) If it is Exchange 2007, edit the web.config file so that it has the following line added : You will see a line in the EV OWA Diagnostic log file similiar to this when you've implemented the change : 1/8/2010 5:13:58 AM: [OWAPage::RestoreItem] Item needs restoring 1/8/2010 5:13:58 AM: [OWAPage::RestoreItem] Web app url from session:http://evserver.ev.local/EVAnon 1/8/2010 5:13:58 AM: [OWAPage::RestoreItem] Restore url:http://evserver.ev.local/EVAnon/restoreo2k.asp?vaultid=1E5850B2EA77101459FCD56CBC4D3A5871110000evsite&savesetid=200912080000000~200912080938300000~Z~609C0CD6ACE107F935F3891156085F41&mbx=TCowper@EV.Local&server=exch1&restorelocation=3&foldername=Deleted Items 1/8/2010 5:13:58 AM: [OWAPage::RestoreItem] IWA authentication, using DefaultCredentials 1/8/2010 5:13:58 AM: [OWAPage::RestoreItem] Set timeout: 45000 1/8/2010 5:13:58 AM: [OWAPage::GetUserString] User is already domainuser format It is not advised to change this to a high value, but some customers have had success in changing this to 45, as an example.
Backup Exec: The challenge of updating RAWS with push wizard
Many users of Backup Exec are annoyed by the recommendation to apply all hotfixes made to the server also to the remote agent. I think this is quite understandable, because in daily business it is in most cases simply not easy to do it because of other, higher priority topics.
Backup Exec Remote agent for windows will not install on citrix server and fails with the Error 1603 in the install log
Solution you can switch to install mode while lusers are on the server. However I would recommend that you disable log on for new users till you installed the stuff: Please use the following command before you start with the remote agent installation. change logon /disable change user /install
