Jump to content


  • Posts

  • Joined

  • Last visited

rlshew's Achievements


Newbie (1/14)



  1. Is there a way to exit or restart Retrospect gracefully after an error -102, -106, -1023, etc. when End Task or Retrospect.exe > End Process in Windows Task Manager fails? So far, if a script hangs after one of these errors, I can only restart after doing a hard shutdown of my server, which is of course not good for the system. Using: Retrospect Single Server 7.7.562 Windows Server 2008 Foundation, SP2 HP ProLiant ML310 G5 RTX400-UR RAID 5, Ultra-SCSI 320 This may have been asked in some other form -- if so, sorry, just getting a bit worried since I've been encountering these more often in the last month.
  2. I'm having a similar headache after recent Windows updates, including .NET ones: Retrospect 7.7 on Windows Server 2008 Foundation, many error -1017, even with newly created backup sets, even after chkdsk, making sure administrative account used on server and client as before. Happens with Mac OS X 10.4, 10.5 , Windows XP, 7, RHEL 3, and CentOS 5. Same successful scripts and clients I've been using for years. Can't Repair Catalog either in case the problem's there -- I'm dead in the water, essentially.
  3. Have you tried renaming the current config77.dat file in C:\Program Data\Retrospect to preserve it and then restarted Retrospect, forcing it to create a new config77.dat? This strategy, or sometimes copying over a copy of config77.dat from a date before hangs or crashes, sometimes helps me when backups hang. (You do regularly backup your C:\Program Data\Retrospect directory and your directory with all the catalogs in case you need to restore any of these crucial files, right?) Sometimes I have to exit Retrospect using the Task Manager Applications tab or kill the Retrospect process tree if nothing else works and it really seems stuck. Just be aware this forced exit can cause file corruption so verify/ repair active backup set catalogs, etc., before resuming normal backup activity.
  4. We're having the same problem: being unable to connect to Mac clients recently upgraded to Leopard (OS X 10.5) unless we allow all incoming connections on these clients. In the firewall control panel, Retrospect Client 6.3.029 and retroclient are set to allow incoming connections. We are using Retrospect 7.7.562 Single Server for Windows to back up centrally all our lab and office computer clients of varying OSs. It's never been a problem before to have stealth mode and centralized backups with Retrospect. Our lab's in a major university, and we can't install a hardware firewall between our group and the router so we can safely drop Mac clients' firewalls. In fact, our ITS wants everyone to enable stealth mode because of the constant presence of sniffers, rogue PCs, etc. Retrospect needs to be able to work with this constraint or many people would have enough reason to stop using Retrospect for centralized backups. (No, can't upgrade to Snow Leopard yet -- insufficient funds, like a lot of other labs.)
  5. Will Retrospect Express HD 2.5 back up files on a Windows 7 (x32) system if run in Compatibility Mode set for Windows Vista?
  6. Please add the ability to use static IPs when using the Emergency Recovery CD with clients. Some networks do not have DHCP for one reason or other, and backup admins. may not have permission to temporarily connect to one for the purpose of restoring clients.
  7. No, I can't can't get a DHCP address for any machines in my group without high-level network admin participation and some hoops to jump. Like it or not, I have to work with the network architecture that exists. That's why I'm asking about using static IPs, thinking I might have missed some setting in the Disaster Recovery procedure. Would it be possible for EMC/ Dantz to include the ability to use static IPs in a future update? Without that, the entire Disaster Recovery utility is useless. Sure, I could recover machines by finding a complete retail copy of the OS, install Retrospect Client, then use UIR, but I don't always have an appropriate retail copy of the OS to use.
  8. Using Windows Retrospect Single Server 7.7, is it possible to restore networked clients that have static IPs (e.g., not 192.168.xxx.xxx) with the Disaster Recovery CD? We have static IPs on this part of campus (not my decision), and though I've not had any problems adding and backing up clients, I ran into this issue last week when trying to restore a client. Fortunately, I was still able to use the service partition on the client's dying boot drive to make a set of system restore DVDs that way, but it would be nice to be able to use fixed IPs with Disaster Recovery if I don't have a working service partition or system recovery disks next time.
  9. I think grooming is triggered when allotted space has been filled. Have you tried, in a separate backup set just for the Exchange volume, limiting the maximum space for that backup set (in the Members tab) to something less than twice the size of a single backup session which you know? (This in addition to setting "1" for "Groom to remove backups older than x" and providing only one backup set member.)
  10. #25, We have a heterogeneous network in my lab. Though quite a petite group of 17 compared to your 400, I find it easiest to work with groups of relatively similar clients. I have six proactive scripts: Windows Desktops, Mac Desktops, Windows Laptops, Mac Laptops, Linux Desktops, and Servers. I also group my Clients similarly. My scripts, selectors, and sources stay simple this way making it easier to locate problems. Also, the scripts can run simultaneously on any available execution units, and backup speed is limited only by available network bandwidth and the server's processing speed.
  11. For Remote Desktop, I think I automatically enabled Terminal Services on my 2008 R1 SP2 server when I allowed connection by Remote Desktop. (Remote tab via Control Panel > System > Remote Settings > System Properties window.) In Server Manager, I see in Configuration > Services that "Terminal Services," "Terminal Services Configuration," and "Terminal Services UserMode Port Redirector" are all running. In my experience with Remote Desktop and Retrospect 7.6 (Server 2003 R2) and brief experience with Retrospect 7.7 (Server 2008 R1), if Retrospect's running in another user's account or the System account, I get the simple Retrospect Activity Monitor if I try to open Retrospect. To get to the normal user interface, I have to click the green button in the Activity Monitor to gracefully stop Retrospect in the other account, then open Retrospect. If you want enable other users only to stop or pause running scripts, or exit Retrospect, Activity Monitor would be sufficient. I think using VNC (e.g., TightVNC) instead of RDP would be one way to skip the Retrospect Activity Monitor, but I've not had time to verify this yet.
  12. ryany, Have you tried Retrospect 7.7 build 208, which was released on Jan 26,2010? The link to the Knowledgebase seems to be back up after being down for a few days. Build 208 release notes at http://kb.dantz.com/display/2n/articleDirect/index.asp?aid=9729&r=0.2908747. No mention of R2 there (I'm using R1 SP2) but some mention of tape drive, interface, and stability fixes.
  13. Is anyone else seeing a lot of "NetAwakenClient: Sending Wake-on-LAN packet to MAC address" with Windows clients in their log? How can we prevent this from happening, while enabling power saving for clients? I'm seeing this with Retrospect 7.7.208 (in Server 2008) during proactive backups associated with laptop clients that are away for the day. This didn't happen with Retrospect 7.6.x and the same scripts and clients. The stream of Wake-on-LAN messages won't end unless I stop script execution. Clients are using Retro. Client for Win. 7.7.106. "Wake for network activity" in their network card drivers are selected now that it sounds like they can sleep to conserve power yet wake for a backup. The proactive backup strategy's been great for our laptop backups since they do travel. People go to meetings, lunch, etc., and in the past had to disable NIC sleep to allow backup while they were not using their laptop. Wake-on-LAN sounded like it would increase backup efficiency while saving a little energy, but it seems to be causing problems.
  14. Please update the User Guide, Knowledge Base, and Tutorials for Windows, incorporating information necessary to install, update, and configure Retrospect Server 7.7 and optional add-ons in Vista, Server 2008, and Windows 7. The recent User Guide Addendum for 7.7 is a good start, but we need more. I just spent a lot of time figuring out how to make the really useful User Initiated Restore work after a 7.6/Server 2003 to 7.7/ Server 2008 upgrade. The change to IIS 7 is disorienting to those familiar with setting up IIS 6 and pre- Server 2008 for UIR. Together with ASP.NET 3.x installed as a system default now, it's not obvious to novice web administrators like me to know what's required.
  15. Thanks, Mayoff. Before I saw your reply, thinking that something went wrong with my Retrospect 7.7 installation process, I removed it from the Server 2008 "Programs and Features" control panel and reinstalled. Now UIR appears in "Programs and Features." I think what might have happened earlier is installing the 7.7 over 7.6 didn't link components correctly. 7.6 should have been removed first. To make UIR work for clients, I installed IIS 6 in addition to IIS 7, following a tip you gave to a Windows 7 user at another thread. After entering configuration information in Server Manager for the web site, pointing the server's web site to C:\inetpub\myrestore\myrestore, clients can now restore files using their browsers.
  • Create New...