Jump to content

jwright

Members
  • Content count

    114
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jwright

  1. I don't see a link to it here: http://www.retrospect.com/en/support/documentation All of the other versions, including 9 and 11 are available. Can you add 10? Also, is it no longer available in the download package? I recall that I used to be able to get the users guide from my installation package. Version 10 doesn't seem to have it included. Thanks, Jeff
  2. Thanks! I'll double-check the user guide, but I think you are right. Cheers!
  3. I'm upgrading the OS of my Retrospect server and want to copy the bare essentials off in case things don't go well. I'm really only worried about the configuration of my retrospect 10 installation. Any advice? I suspect there is a document on this out there, but I didn't find it. Thanks, J
  4. I've upgraded to v10 and now the retroeventhandler.bat script is not working properly. I've noticed that if I run a backup job on just a single system, the script properly records the number of files, time taken, ans size of backups. I can see this by comparing to the logs. However, if I run a backup script that backs up say 10 clients, the handler will record a successful back up, but lists the number of files backed up as '0', time taken as '0', etc. I use this script for custom logging and have used it as long as I can remember (back to Retrospect v3 or 4 maybe?). Any ideas? Thanks.
  5. jwright

    version 9 hanging

    After another reboot of the client, this client started backing up. Note, we are using the older client and will stick with that one until a new release is available.
  6. I'm running version 9 now w/block level enabled. I've pushed client upgrades to the latest versions (Windows - 9.0.0(187), mac - 11.0.0.191). I'm seeing Retrospect hang, so far only on the first mac client it encounters. Basically if I look at the Executing tab in Retrospect, it will appear to be working on a file, but it will never finish and never update the information on the page. I am able to use the stop button to stop the job. It then says "retrying" and eventually stops. Suggestions? The mac client has been rebooted. Thanks!
  7. jwright

    version 9 hanging

    So oddly enough, a proactive backup of an external drive on this Mac works without a problem. I'd prefer not to have to switch this client to proactive backups. I've rolled the client back to 10.5. Still seeing the same issues, but now it is timing out faster and moving on to other clients. See the execution log entry below: 3/13/2014 1:43:02 PM: Connected to toothpick * Resolved container toothpick to 1 volumes: Macintosh HD on toothpick - 3/13/2014 1:42:54 PM: Copying Macintosh HD on toothpick Backing up 1 out of 12 files using block level incremental backup, storing full backups for remaining 11. Trouble reading files, error -519 ( network communication failed) 3/13/2014 1:59:20 PM: Execution incomplete Remaining: 148704 files, 74.0 GB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 00:16:25 (00:16:14 idle/loading/preparing) This client has about a million files (204.5 GB). Any ideas?
  8. jwright

    Upgrade To 7.7.341?

    Thanks. Based on past experiences, I have learned to let others suffer the consequences of being first adopters of new Retro releases. Too bad there are problems. It has been a long time since I have had a problem-free upgrade. I guess I'll watch and wait before I upgrade.
  9. I am currently running version 7.7.325 and wondering if anyone has any particular issues with 7.7.341. All of my clients are Windows 7 SP1. Thanks in advance.
  10. jwright

    The 'new' Forum

    The usefulness of the older forums is limited to a small window that is shrinking every day -- I suspect after a few months most current issues will be covered. It will just take some time. The new forums look fine. However, if I recall correctly, there used to be specific forums for the different Windows products. Have some of these products gone away? Thanks.
  11. jwright

    Upgrade To 7.7.341?

    OK, I just checked the Roxio Retrospect Support page for updates and noticed "Retrospect 7.7.533 for Windows". This is not being offered by my Server ("Help --> Retrospect Updates"). Can I skip the 7.7341 update and just install 7.7.533? BTW, I am running Multi Server. Thanks.
  12. jwright

    Roxio Retrospect?

    I discovered this news yesterday...just curious, did anyone other than resellers get an announcment about this? I assume customers with support contracts got an e-mail... Perhaps I neglected to subscribe to a mailing list? J
  13. Ugh. Thanks Retrospect for wasting my time -- again! I have been playing with these features trying to get them to work. It really is absurd that a set of options that appears to control all clients only work for very specific and different clients. It is even more absurd that we are expected to comb through the user guide to learn this! My god, just put a note in the dialog box! Really, the engineers need to drop what they are doing and fix the dialog box on this one now. The quick fix is simply to specify which client each option applies to. There is plenty of room under each option.
  14. jwright

    Full Mac 10.6 restore

    Russ: Here is the scenario again, all the details included this time. Here is the scenario: A mac OS X 10.6.2 client (retro client 6.3.028) had a bad disk. Resolution: 1. Replaced the disk with a new disk (identical manufacturer and model). 2. Formatted and partitioned the disk using the mac OS X Snow Leopard 10.6 disk. 3. Connected the system via firewire to a Mac OS X 10.5.8 Server running the retrospect client (6.3.028) and then booted the drive as a firewire drive mounted on the 10.5 Server. 4. Restored all files and folders to the client firewire drive. I had pretty much the same thoughts and concerns that you do regarding the systems I used and the 10.6 support in retrospect, however given the lack of documentation on the process, I wanted to get some validation from others. Next time I will try your suggestion of bringing the system up to current patches before I restore. Also, I will see if I can remove the 10.5.8 box from the process. Currently we don't have a spare 10.6.x server that we can use for this purpose. Jeff
  15. Ugh. I have a Mac 10.6 desktop with either a failing disk or a corrupted file system. Fortunately, I have a few days to prepare for recovery. Has any one done a full restore on a 10.6 system recently? Any suggestions? I assume the process is basically a two-parter: 1. slap a new disk into the system, install 10.6 and the retrospect client. 2. go to the server, add the client and start the restore process. Sound right? Anything to watch out for? Also, on a side note, anyone want to comment on Mac disk tools? Is DiskWarrior any good? Thanks in advance! Jeff
  16. jwright

    Full Mac 10.6 restore

    Answers to your Qs: 1. 10.5 Server 2. latest retro client 3. 10.6 4. yes. Jeff
  17. jwright

    Full Mac 10.6 restore

    I thought I had this one resolved. But I have had to restore several times now. I am wondering if there is a step or two that I have missed. I don't get many opportunities to work with mac restores, so I am hoping for help with the details. Here is the scenario: A mac OS X 10.6 client had a bad disk. Resolution: 1. Replaced the disk with identical manufacturer and model. 2. formatted and partitioned the disk using the mac OS X 10.6 disk. 3. Connected the system via firewire to another mac running the retrospect client and booted it as a firewire drive. 4. Restored all files and folders to the client firewire drive. Issues: We have done several full restores and have encountered different issues each time like permission problems, programs liks sftp reporting missing dlls and now the "grey screen of death" ("version mis-match between kernal and CPU") after and apple update. It feels a lot like we are missing a critical step in the restore process. Suggestions? I couldn't find a detailed document on mac restores. Jeff
  18. Everything went off without a hitch. Of course, I was biting my nails during the first backup. :-/ Also, I backed up my config files before I started the installation, because I have had corruption problems with upgrades/updates in the past. My issues with crashing were resolved with the last patch, but I still had the slow matching issue. I have not looked closely at the backups, but folks should watch the time it takes to do matching and their over all backup time. On the first run, my matching phase seemed at least a factor of 2 times faster, but the backups took about the same amount of time. This could simply be more data on the client though. I'll report back with something more meaningful after a few days. Jeff
  19. We recently upgraded to 7.7.203 from 7.6. I noticed that our backups were not completing, and when I checked the server retrospect had crashed. I have been monitoring it for several days now, and it seems the problem is that Retrospect.exe slow consumes more and more memory until it dies. Has anyone else encountered such an issue? J
  20. jwright

    Mac 10.6 client error -1105

    Russ: Thanks for the info. I suspect the UID issue was to blame. Unfortunately, before I had a chance to test, the user fumbled through their time-machine backup and ran a full restore. :-/ At least I know we have a working full backup from time-machine..that should hold him until Retrospect works out all of their issues. Jeff
  21. I have a Mac 10.6 client that I am trying to back up. The client seems to have a bad disk or file system corruption. The backup starts fine, but after a while, slows down to a few MB per minute. It bounces around and then usually stops with a handful of errors like this: File "Macintosh HD/private/var/db/dyld/dyld_shared_cache": can't read, error -1105 ( improper seek) File "Macintosh HD/Users/person/Desktop/TJC_MIDI files/ShiFolder/Shi_sop.aif": can't read, error -1105 ( improper seek) The machine still runs, but it seems to be having issues. I would love to get one more backup before I attempt a restore. Two questions: 1. Does this seem like a disk issue or a filesystem issue? My guess is a disk issue. Since it is a journaled file system. 2. Is there any way to get a backup? Retrospect keeps stopping because it can't read files, so my guess is "no". Thanks! Jeff
  22. jwright

    Mac 10.6 client error -1105

    All local accounts on the machine. The machine had 6.3.028 on it prior to the restore. To restore the system, I connected it via firewire to another mac server running client version 6.3.028 and did a full restore to the firewire drive. Jeff
  23. jwright

    Mac 10.6 client error -1105

    I managed the restore, but I did get 11,073 errors! All like this one: File "Macintosh HD/Users/*****/Sites/cps296/Lectures(Old_07)/Lecture09.pdf": can't duplicate to "Macintosh HD/Users/*****/Sites/cps296_s09/Lectures(Old_07)/Lecture09.pdf", error -1101 ( file/directory not found) (Of course I replaced the username with "*****") That means that 11,000 files could not be restored...any ideas? Is this a 7.7 issue? A 10.6 issue? BTW, This one of the late 2008 aluminum imacs. It was not too bad to replace the hdd, but it did require two people. I found one great video on youtube...the only one that came close to how the actual cables were connected inside. You can search for "iMac Aluminum Hard Drive Upgrade Pt 1" on youtube and find it. Jeff
  24. Are you opening the app from a short cut or clicking on the executable? It is probably located here: "C:\Program Files\Retrospect\Retrospect 7.7\Retrospect.exe" The monitor is located at "C:\Program Files\Retrospect\Retrospect 7.7\monitor\retromonitor.exe" If it is not something simple like a path issue, then you could try stopping and starting the retrospect services. I had issues with this too, but mine resolved themselves after I restarted the services and rebooted. Jeff
  25. jwright

    Mac 10.6 client error -1105

    It turns out the user purchased "Disk Warrior". We booted the system as an external firewire drive on a macbook. Disk Warrior reported the disk as having mechanical problems, so he is on board with replacing it. Now I get to try my hands at a imac hdd replacement, which looks tricky. Btw way, the disk failure explains the errors I was getting from retrospect while trying to read from the drive. That might be an error to keep an eye out for. Thanks again for the suggestions. Jeff
×