Jump to content

ken2johnson

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

3 Neutral

About ken2johnson

  • Rank
    Newbie
  1. See the release notes for version 8.5. It supports Exchange 2013 and Exchange 2010 on Server 2012. http://retrospect.com/en/documentation/user_guide/win8/release_notes
  2. Does anyone know if Retrospect Windows Server 7.7 supports backing up Exchange 2010 with Service Pack 3? Can Retrospect Windows Server 8.1 back it up? We currently have clients using 7.7 and 8.1 to backup databases and mailboxes. We just want to know for sure that it will still work after we install Service Pack 3. Anyone running this currently? Thanks. -Ken
  3. It's been awhile, but here's an update on this. We upgraded to Retrospect 8 on the backup server and installed the 8.0 client on the Exchange 2007 server along with .Net 4 to get Exchange to back up. We also ran Isinteg -s server -fix -test alltests on the mailbox database. We then removed the exchange license from Retrospect and added it back in. We ran a backup last night and we still get a service transaction error on 1 mailbox. Anyone else have a suggestion?
  4. According to other posts on the forum the solution for Retrospect 8 seeing Exchange 2007 on a Windows 2003 64-bit server is to install .Net 4.0 on the Exchange server. This worked for us.
  5. SBS Interface Performance Issues

    I'm not sure this helps or not, but we had slowness with SBS 2011. I noticed with Retrospect 7.7 and Exchange 2010 there is an Exchange Cmd-Let error in the System log every 15 seconds only when the interface is running in the console session. It is accompanied by a pause in the interface for a few seconds where it doesn't seem to be doing anything except waiting. Depending on your hardware this can vary in duration. We also noticed in SBS 2011 that Retrospect would consume more and more RAM over time until other services on the server would crash for lack of available RAM. Since you are on 2003 none of this may apply, but it is worth noting that Retrospect 7.7 has definite interface performance issues with SBS and Exchange. One thing I have noticed is that version 8 no longer has the pause in the interface and no longer consumes RAM uncontrollably for SBS 2011. The error still appears in the logs every 15 seconds, but we can live with that for now. So, as far as interface responsiveness and performance for us, Retrospect 8 is much better. We are not using the SQL Add-In. So, the situation may be different for that. Perhaps you could try the Retrospect 8 trial to see if the performance of the interface improves for you or not. I'd recommend backing up your 7.7 catalog and config files first to make it easier to roll back if you decide not to purchase 8.0.
  6. Error -523 (service transaction error)

    This sounds just like my post from a couple weeks ago. I can't say that anthing fixed this. I just thought I'd link it since it's the same issue. http://forums.retrospect.com/index.php?/topic/149975-trouble-reading-files-error-523-service-transaction-error/page__fromsearch__1
  7. Backup exchange 2010 mailboxes

    The best thing to do is to follow the KB article on how to configure Retrospect to see Exchange. My guess is that you are using an account that doesn't have a mailbox on the serve ror the mailbox is not initialized.See the following KB for more details: http://kb.retrospect.com/articles/en_US/Retrospect_Article/Exchange-Backup-Requirements/?q=exchange&l=en_US&fs=Search&pn=1 This has always worked for us, except for version 8. Version 8 also requires .Net 4 to be installed on the Exchange server.
  8. We had the same problem when upgrading from 7.7 to 8.0. I saw this forum post and installed the .Net 4 on the 2003 64-bit server that has Exchange 2007 on it. After that I restarted the Retrospect client and re-added the Exchange license in the Retrospect server and voila! It can see Exchange. This really should be documented somewhere in the Exchange installation instructions for Retrospect 8. A forum post is not where we should find install instructions. Mayoff, can you recommend a new KB article for this or update the existing Exchange KB article? Can it also be put in the User guide?
  9. In response to the original question, we have been looking off and on for the last two years for a Multi-Server replacement and we keep coming back to Retrospect. No one else really seems to care about backing up Mac, Windows, and Linux at a reasonable price point. We also require Exchange backups. So, we have checked ArcServe, BackupExec, Bacula, AppAssure, MS Storage Server Essentials, and a host of others. They either cost too much or don't support backup for MacOS X or Exchange. If you don't need advanced virtual machine backups and you need multiple platforms backed up then Retrospect is still the best one out there for the price. Yes, you could get a backup solution that has more features and is more reliable, but you will pay a lot more for it. You could also get cloud backup that does just as much and pay a monthly fee for it. But we still find that the majority of companies do not have the Internet bandwidth to spare to back up everything to the cloud. For small businesses, Retrospect is still our recommended backup product. It's a shame that development has been hampered by company acquisitions over the last 5 years. However, there really seems to be some progress being made now that Retrospect is its own company. I really hope they keep it that way and can give some badly needed attention to the Windows server product. Retrospect 8 is a step in the right direction, but it still has a long way to go to be a rock solid backup product. Here's my top wish list for 8.1: 1. Fix the myriad of Exchange mailbox backup issues. 2. Separate the server and console so you can launch the console and see what is going on even while the server is backing up under another user session. Use ArcServe as an example of how this should work. 3. Make it play nice with SBS 2011. There are still DCOM errors on the server from MacOS X clients, and Exchange Cmd-Let errors generated by Retrospect all the time. 4. Fix whatever causes the config76.dat file to get corrupted over time.
  10. Thanks for the response Lennart. Chkdsk is a long shot for a single mailbox backup error since there are no file system errors reported in the system logs on the server. ESEUtil is for the DB level of Exchange and probably will not find any issues. Since we are running Exchange 2007 I'll go ahead and try Isinteg to see what it comes up with. However, I was really wondering if anyone knew what the error actually meant. This is the first time I've ever seen it. Part of troubleshooting is to identify and define the problem. I dislike shotgun approaches to troubleshooting. And here's a little side point. For anyone that's trying to repair mailboxes in Exchange it's good to note that IsInteg is no longer a separate program in Exchange 2010 SP1. It's now a powershell cmd-let. http://blogs.technet.com/b/nawar/archive/2010/08/19/exchange-2010-sp1-new-mailboxrepairrequest.aspx
  11. Exchange Mailbox Backup Error -3420

    I'll run the checks and see. Thanks.
  12. Retrospect 8 Deduplication Questions

    This is pretty much what I expected. I don't think we are going to have multiple computers backup to one backup set because of the difficulty of removing the old snapshots for computers that are decommissioned. If they somehow make that easier then we may start combining computers into 1 backup set. That's the only way I see that we can fully benefit from the de-duplication feature. With each computer in its own backup set we are basically getting Incremental backups for each computer with no cross-computer de-dupe. Does that sound correct to everyone? Thanks.
  13. Exchange Mailbox Backup Error -3420

    It's English. Sorry for the long delay in responding.
  14. Retrospect 8 Server for Windows is being marketed as having Automatic Deduplication features. So, here are some questions about this. Is this a new feature in version 8 or just new marketing for something that was in previous versions? How do we know if this "automatic" feature is running? Is it really automatic or is there some check box we need to set or some specific way of doing backups to take advantage of this? In older forum posts, I read that you need to backup several clients to the same backup set in order to get deduplication. Is that still the case or will this work across multiple backup sets? Any help with these questions is appreciated.
  15. We are backing up mailboxes on an Exchange 2007 server and have recently started seeing a backup error on one mailbox out of about 25. T-597: PtSend: cmd MbeF/msg RdBg: byte count 1041 exceeds maximum of 1024 Trouble reading files, error -523 ( service transaction error) Anyone know what this means or what we can do to resolve it? Exchange is on a different server than Retrospect. We are running Exchange 2007 with the latest service packs and updates. Retrospect is version 7.7.620 and the server with Exchange has client version 7.7.114. Let me know if you need any other information. Thanks.
×