Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
 
Arcserve
Reader comments compiled by Mitch Tulloch
Arcserve 2000 with Exchange Agent. The problem with NT Backup, you cannot schedule the job. We run it here because it was here when I started working here. The company does not like change. The brick level backup worked for a little while no problem. Then stopped. I worked hours on it trying to figure out why it would not work. Nothing changed on my servers for it not to. Their tech support could not help much. Backing up the the private and public stores works just fine. The restore procedure is very simple. The only draw back is that brick level does not work. If you have an r&d server like me, this would not be a problem. All my restores are done on the backup server. The restore went over well. We have moved beyond our current hardware, moving to a 120/240 autoloader system. I would not recommend Arcserve due to their poor tech support. When the product actually works, it is great, when it does not, good luck trying to figure out why......

I have called cai's tech support a few times. Each time, they seem to get slower to respond, or the support is horrible. The consultant that was here prior to me called cai's tech support a couple days after I started here. They called us back 2 weeks later. No bs. I called them 2 weeks ago because the restore was giving me some funky problems. Wanted to find out if they have seen this problem before. I have yet to receive a call back. I ended up figuring it out, but the support is terrible.

I would stay away from Arcserve completely

/Nick


I'd have to agree here. Arcserve was even not that good when it was the flavor of the Novell world! It's even crappier when working with NT!

/Colin

letter.gif (161 bytes) Send me feedback on this article.
back.gif (2457 bytes) Back to Mitch Tulloch's column on OutlookExchange
Disclaimer: I hope that the information in these pages is valuable to you. Your use of the information contained in these pages, however, is at your sole risk. All information on these pages is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by me. I shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008