Jump to content

aaronpriest

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by aaronpriest

  1. I too have started seeing this recently with some customers of mine, for both SQL and Exchange. Any ideas?
  2. 1,154 views and no suggestions huh? That's not real encouraging... hehe! I tried creating a separate proactive script for just this client going to a new backup set just for this client. Still says source not available in the proactive tab and never backs up, even though I can run a manual backup. I guess I'm going to try a normal scheduled script and skip the broke proactive backup until someone has a suggestion. I'd hate to call support for something this stupid.
  3. I added a new client a few days ago. It shows up in the client database. I can see the volumes under client properties, set a new password, etc., There are no communication, network, or firewall issues that I can see. I can run a manual backup with a few -1101 & -1102 errors from the C:\Windows\SoftwareDistribution\ folder, but otherwise it backs up. However, when I add it to our existing proactive backup script, it just sits in the proactive list and says source not available for status. I've forgotten the client, removed and reinstalled the client software (including deleting the \ProgramFiles\Retrospect folder and \ProgramData\Retrospect folders), rebooted server and client computers, and changed the password. What is ailing this thing?! I once read of a similar issue in the old Dantz forums, but I can't find the thread now, and I don't recall if they ever found a resolution either. I'm running 7.7.612 multiserver and 7.7.114 client.
  4. The notes say "Added support for Microsoft Exchange Server 2010 (requires new Exchange Add-on license)". I'm not sure the price. It would be free if you have an ASM contract. Might want to call sales and inquire.
  5. For the record, I've run into these issues with EVERY install of 7.7.553 I've tried. I've rolled them all back except one server which backs up Exchange 2010 database and mailboxes only. I don't think it had much internal testing to be honest, but I welcome the Exchange 2010 support over nothing. :-)
  6. Be careful if you do a recycle, since that will erase all backups in that set. Be very sure you have what you want to restore to in another set somewhere if you recycle. You can add a second DC to an SBS domain, but there are limitations on what it can do, such as promoting it to a PDC and expecting to reinstall SBS like you could if it was a regular DC. Here's a list: http://support.microsoft.com/kb/200866
  7. I should clarify: stepping back a 7.7 build, not a version (like 7.6). :-)
  8. Might want to try stepping back a version until some bugs are resolved in 7.7.533. I've read the demo on the website is a previous build (it will preserve your config and serial if you just install over the newer version). The client version is OK. I'm living with .533 to get Exchange 2010 support on one server.
  9. Well, that does sound like maybe it's more involved than what I ran into. I also think it was WSUS SP2 that did my customer in, but I was able to repair it without a full Retrospect restore. We also lost our company web until it was resolved, in fact that's how we discovered we had a problem to begin with. I think our resolution was to rerun the SharePoint Products and Technologies Configuration Wizard (Psconfig.exe) and reboot, and it was an immediate fix. Here's an article on it: http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx If that still is no resolution and you must roll back, I'm happy to say I've restored many servers for customers using Retrospect--SBS, SQL, Exchange, you name it. I'm very confident in Retrospect, provided you have a good backup and a solid catalog file. I would create a complete backup as you are right now before restoring to a previous state, so you could return to this point if you had to. Maybe even backup to a completely new backup set (temporarily) just to cover all bases. You should be able to restore just Exchange back to this point after rolling back drive C and the system state, so you don't lose data. I'm not sure what documents you might also have to consider on drive C, depends if you redirected folders and what not I suppose. Just in case you need it, have you downloaded the universal disaster recovery CD and burned it to disc?
  10. Yuck, I was in a similar circumstance a few months ago. Why doesn't Microsoft have system restore in server OS's? :-P You might want to look into the error you are getting first, as I was able to find a solution with a little Googling and didn't need to restore to fix Sharepoint. I had to re-run a command on SBS 2008 to fix what the update had done and I just can't remember what it was now. It was a very simple fix though, hopefully you can find it easily. Recovering Exchange data from .OST files can be very challenging. If you are set on doing a system restore, I'd export every user's Outlook data to .PST files first and not expect .OSTs to save you. In my experience Outlook will make you create a new .OST and get a fresh sync from the server after doing a roll back of that magnitude. You could also do a complete system restore, but then do a separate Exchange restore of newer data if you make a new Exchange backup right now before doing a restore. I'd still make .PSTs as a redundant approach though. Depending where Sharepoint is stored, you might need only a restore of drive C, and maybe can leave E entirely alone, I'm not sure where you chose to put your data. I typically keep Exchange and all user data on a separate drive than the OS though, so I can recover from a failed update or something stupid and not lose user data. I don't think SBS has a wizard to relocate Sharepoint data, but it does for Exchange, redirected documents, etc. Good luck! I'd look for the solution I found for Sharepoint first though, it was a very quick, simple solution and didn't require anything as dramatic as a restore.
  11. That's good to hear BRF, thanks for the update and glad you got a resolution. As a reseller and supporter with a lot invested in Retrospect, I was starting to cringe at where the conversation was going. Ramon, you have a silver tongue, very politely said. I sincerely trust and hope many of these issues are being taken seriously by Roxio and will be resolved in the long run.
  12. Yes, correct. I boot off it, click restore locally, confirm the date/time, click the restore button on the first menu, and then click switch to advanced mode on the next dialog box. From there I choose restore an entire volume and choose my source and destination manually. I think this might avoid what you are seeing with the wizard (which I don't typically use).
  13. Very interesting, since you are the second person to ask a similar question this week. I'm using the universal recovery CD and I don't see that option or message, so I'm unsure. I'd call tech support for a faster answer. Sure doesn't sound like a warning you'd want to ignore.
  14. Yeah, 7.7.533 does fix a few legitimate problems like the tape one you just mentioned and Exchange 2010 for me, so I'm living with the bugs on one server that needs it. I suspect this will all be resolved with a new build within a month. You can install the previous version over the newer one with no issues, no uninstalling first or anything. If you had to step way down to 7.6 that's a different story since the catalog file structure has changed with 7.7. I took a few servers back to 7.7.341 with no issues at all though, very quick and painless. You might be stuck in my shoes with needing 533 to resolve an issue and living with the errors for a little bit.
  15. Just the server needs to be downgraded; 7.7.341 server with 7.7.114 client is OK.
  16. I had to do that once quite awhile ago, and I don't recall the particulars. I think the catalog files had to be recreated for every backup set because 7.7 used a different format. I can't remember if anything else special had to be done.
  17. This is very good news. I've been struggling with grooming issues and corrupt catalog files for a couple years. Good to see development again!
  18. Unless you need .533 for Exchange 2010, I'd step back to .341. I had a lot of errors like that with .533, and clients that would hang and never finish. I have one server that needs .533 for Exchange 2010, but all the rest I took back to .341 in the meantime. Many errors disappeared.
  19. I guess several people have had trouble when choosing "Install updates on shutdown" and Win7 SP1 gets applied. Since I typically install it manually I've never had this issue myself. Most of my customers have had it applied automatically at 3AM and there is no problem with that either. Apparently it's only when they click shutdown and the update gets installed that it sometimes hiccups and won't boot again. It doesn't finish writing some files before powering off. I've seen it four times already with customers. http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/1c9a7151-b48c-4a98-aae7-a4b82682ea8e/#bcabda57-7338-499f-aee2-d708e76df315 Anyway, the system state should have been backed up by default unless you purposely unchecked it in your scripts (Options, Windows, System, Back Up System State). When doing a restore, if you choose Rollback everything on x to be exactly as it was on x date it will include the system state as well. If you are in advanced mode instead of the wizard, the option would be restore an entire volume, and under Options, Windows, System it is already checked by default to restore the system state too.
  20. The activity monitor has been around for awhile. It's useful when Retrospect is running as a different user or in the background and you want to restart it safely, but I've found it can't always cancel a task properly and I have to crash Retrospect anyway to open it back up, especially if it is waiting on a prompt to be answered. Sometimes this corrupts a catalog file and requires a repair or rebuild of it, which is easy but takes some time. I wish it ran better as a service. Retrospect has many strengths, but that is one weakness. Hopefully you did have 7.7, as 7.6 and earlier won't handle Windows 7 hidden boot partition properly for a restore. The Windows 7 machines and 2008 Servers that I've restored with 7.7 have gone very smoothly though. It will probably prompt you to reboot a time or two after doing a full volume restore with system state, but it has been very solid for me every time that I had a good backup to begin with. It's why I keep using Retrospect in spite of a couple shortcomings. What good is a backup if the restore is not solid? And in that department it has saved my butt on many occasions! Just this weekend we had a laptop that failed miserably with a Windows 7 SP1 install, even though all the other identical ones in the building were successful. After several minutes of messing around, it was easier just to restore from the previous night's backup and call it good. We had no data on the laptop that hadn't already been stored to the server, and I already had the universal disaster recovery CD burned, so it was far cheaper in man hours to just restore than to attempt fixing the issue. Reinstalling SP1 worked fine the second time around incidentally. :-)
  21. I've done this successfully quite a few times with 7.7. If you don't have a disaster recovery CD, you'll have to load Windows and Retrospect first to do a restore. Your first hurdle will be to get the drive structure (partitioning) setup the way it was. Typically Windows 7 has a hidden 100MB partition that holds the boot and recovery information (it has no drive letter, but you'll see the volume in disk management); Drive C will be the second larger system volume where Windows, Program Files, and everything else goes. Your Lenovo recovery disk will probably put this all back. Some OEMs also have their own utility partition either before or after the system volume (C:\) that may be hidden or may not be. Your recovery disk may take care of that as well if one existed, I dunno. The Retrospect recovery itself is pretty painless. You may have to recreate a catalog file from your external drive before you can restore if you don't have access to it. Afterward try restoring the entire volume with Retrospect, including the system state. It's worked very well for me in the past, good luck!
  22. I recommend reading the user guide if you are new to Retrospect. It is quite a powerful program with a lot of options once you are familiar with it. http://img.roxio.com/retrospect/en_rug_win.pdf Also, here is an article specifically on grooming recommendations for better performance: http://kb.roxio.com/search.aspx?URL=/content/000066RT&PARAMS=set-locale=en For a quick overview though, you probably want to go to Configure, Backup Sets, and Properties for the one that is too large. Under the Options tab, check "Groom to remove backups older than x" and enter a suitable number, depending on how much storage space you have and data retention you want. There you can also click Action and Groom to clean out the older files that are taking up too much space. We run a grooming script on backup sets every weekend to keep the drives from filling up. You could do this less often if you have more space, but I would caution against doing it more often (like nightly). Some do it manually with no automated script, but I find once a drive fills up you risk needing to recreate a catalog file, which takes more time than grooming would have. :-)
×
×
  • Create New...