Jump to content

ken2johnson

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by ken2johnson

  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. 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. 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. 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. 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.
  12. It's English. Sorry for the long delay in responding.
  13. 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.
  14. 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.
  15. I know this thread is a little old, but just in case anyone is still looking for a solution here I thought I would post something helpful. The error cybor462 saw after the full restore is not as scary as it sounds. It happens sometimes if the windows boot files don't get restored properly. I've only seen this issue with Win 7 and Win 2008 R2. After doing the full restore follow the steps in this MS KB to get the machine to boot again. http://support.microsoft.com/kb/314477. That should be all you need to do.
  16. Thanks for the response. Below is a more complete example of the errors in the log. And there are now 8 of these errors for just this one user. The Errors button is grayed out. Could that be because we are using the Open File Backup add-in and these are not "file" backup errors? Is there a how-to for figuring out which email item this is and determining if it is truly corrupt or not? Thanks. T-685: TMailboxFolder::OpenEntry: bad hr = 0x8004010f File "User Name\Inbox\00000000204f28774f828d4bba15a8afd4cdf2dd0700f858374a47df2d4f94aabf32aba8ad740008064b29730000f858374a47df2d4f94aabf32aba8ad740011805820150000": can't read, error -3420 ( unknown)
  17. You're correct. No one ever responded to our forum post. We eventually found a solution, but you probably won't like it. We formatted the hard drive and reinstalled Windows and the Retrospect client. It never got this backup error again. The best we were able to figure out is that the Microsoft Shadow Copy service on the computer was corrupt. We couldn't find any way to fix it other than reinstall Windows. I know this isn't a great solution, but it's the only one we found.
  18. I think this post might help answer question 1: http://forums.dantz.com/showtopic.php?tid/30721/ In answer to your second question here's what we do. We use a 2 drive rotation where one drive is onsite and the other is offsite. Each drive has two backup sets on it. One drive stays the whole week and the script does a Recycle at the start of the week and then regular backups for the rest of the week to backup set 1 on that drive. A second schedule in the script backs up to the second drive using backup set 2. The following week we swap drives again and another schedule in the backup script backs up to backup set 3 on the first drive. The next week is to backup set 4 on the second drive. The fifth week starts back with backup set 1 on drive 1. This simplifies the rotation to only once a week, provides an emergency offsite backup that is less than a week old, and allows for up to 4 weeks of backups available for restores. This solution works if you don't have really large amounts of data to backup and you have large external drives. It also speeds up the backups we do during the week since they are not doing Full Recycle backups every night of the week. Lastly, buying two really large backup hard drives is cheaper than buying 5-7 smaller external backup drives. This is just one solution. Retrospect is very flexible in what it can do with backup schedules and backup sets. Just plan out how many backups you want available for restore, how much space the backups will take up, how big the external drives need to be, and how it fits in to your emergency recovery plan. Hope this helps.
  19. We were backing up Exchange 2003 Standard and found that the only way is to restore over the top of the existing Storage group, which means overwriting the mailbox and public folder stores. We needed to restore only one public folder. So, here's what we did after working hours: Stop the SMTP, POP, IMAP, and IIS services (To prevent users from accessing mailboxes and keep new items being delivered) Do a full backup of Exchange server only to a new/temp backup set Dismount both Mailbox and Public Folder stores Restore Exchange from the backup you want the public folder from Mount the public folder and mailbox stores Run Outlook on a computer and export the public folder to a pst file Dismount both Mailbox and Public Folder stores Restore Exchange from the backup you made in step 2 Mount the public folder and mailbox stores Start the SMTP, POP, IMAP, and IIS services You should now have a pst file that contains the items you wanted to restore. You can now put them back into the live public folder using Outlook. In our case, the user wanted to look through it and compare it to what was in the live public folder. So, we added it as a personal folder in Outlook for them. NOTE: In Exchange 2007 Standard this is a little easier since it stores the mailbox and public folders in two separate Storage Groups. For that you can do the same basic steps, but you will only have to backup and restore the public folder storage group. So, that should save time. NOTE: We had to do a repair of the stores we restored with eseutil before it would mount. I can't remember the command line switch right now, but if you look up the error when it doesn't mount you can search on the internet and get the right switch to repair and mount the stores. Just don't panic if it doesn't mount the first time. Also, the later restore in step 8 mounted with no problem.
  20. We are using Retrospect Multi-Server 7.7 and have the Open File Backup option installed. We are backing up 3 servers and about 20 desktops. One desktop refuses to backup using the Open File option. It gives the error "Can't use Open File Backup option for OS (C:) on COMPUTERNAME, error -1017 ( insufficient permissions)". We have tried uninstalling, rebooting, and reinstalling the Retrospect client, but we get the same message each time it tries to backup. We are pretty sure it isn't a Retrospect configuration problem, but we would like to know how to troubleshoot this error. What can we do to get this desktop to backup properly? Any help to point us in the right direction would be appreciated.
  21. We have Retrospect Multi-Server 7.7 and are backing up Exchange 2007 that is installed on another server. We have one mailbox that is giving an error on three items. We also have the Open File Backup option so these errors stick out in the logs. The error is "can't read error -3420 (unknown)". What causes this and how can we get it to backup this mailbox with no errors?
  22. We also got this error with one XP client computer. It turned out to be a conflict with two firewalls running on the computer. We have Symantec Endpoint that includes a firewall. We normally have the Windows firewall disabled, but for some reason it got re-enabled on this computer. After disabling the windows firewall, we removed the client from retrospect and then added it again. This cleared up the -557 backup error and an error we got trying to view the volumes for that client in Retrospect. Hope this helps anyone running into this in the future.
  23. I renamed the config77.dat and config77.bak files and started over from scratch. I added only the Exchange server as a backup client and then went straight to adding the Exchange license and it worked this time. I have a theory on why this didn't work the first time. When we first setup Retrospect to backup this server it didn't have Exchange installed on it. We installed Exchange 2007 later. I noticed that the Exchange license number is the same as one of the server client license numbers. Could it be that this server was originally assigned a non-Exchange license and when I asked it to apply the Exchange license it didn't match up and got confused somehow? That's my only guess for the engineers if they want to try and reproduce this. In any case, it's working now and I'm rebuilding the other scripts. Hopefully it won't crash after I get everything else setup again.
  24. I am trying to apply a license to an Exchange Server in Retrospect Multi-Server so that I can add Exchange to the Backup script we have. When I click on Exchange Server (not licensed) it asks if I want to use the available Exchange license I've already entered into Retrospect to this server. I click on Ok. After that it asks what user account I want to specify. I'm using the domain Administrator account which should have full rights to the Exchange server. After about 10 seconds I get "Retrospect encountered a serious error: Assertion failure at elem.cpp-1084". Here is the top part of the assert_log.utx. Let me know if anyone wants me to post the whole thing. OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 2, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.7\Retrospect.exe, version 7.7.325 Exception occurred on 4/20/2010 at 4:55:41 PM Error info: Assertion failure at "elem.cpp-1084" Exception code: E0000000 ASSERTION Fault address: 77E4BEF7 0001:0000AEF7 kernel32.dll
×
×
  • Create New...