First of all it is very quirky with all the prerequisites that need to be done before you can restore a server to another machine (all the machines need to be registered clients, the source machine has to be configured with explicit remote permissions so that the other machine can perform a directed restore). But that I can get used to.
We have a ton of servers to backup. The Legato server seems to not be able to handle such a number of servers. The admin interface is super slow and very often disconnects when you try to do something. Finally, I have never had a case where an Exchange restore went smoothly. It usually takes a few hours to get the restore going. Currently I have been wrestling with a particular restore for 2 straight days. It is an information store restore to an offline server. It needs two tapes - a full one and an incremental one. Legato perfectly knows what needs to be restored - legato verbose logs indicate that it knows that it first needs to restore the full thing, next the transaction logs from the incremental tape. But right when it is done restoring from the full tape, it tries to do hard recovery without waiting for the transaction logs to come in from another tape!!! Sure in the past I have seen it work fine in this situation, but this time (and a few other times in the past) it is pulling this crap. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
