Jump to content

Cygnis

Members
  • Posts

    152
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Cygnis

  1. Update: the issue appears to have been fixed now. Thanks!
  2. Not familiar with this problem, but here are the first questions that spring to mind: Are the users logged in or logged out? Does logging a user in/out before the backup starts make a difference? Do any of the Mac's Energy Saver features (e.g. hard disks powering down) kick in while a backup takes place? Do the problems only occur in Proactive mode, or in standard scripts or manual immediate backups as well? Are the other Macs (that do work okay) all running 10.6 as well, or a different OS version?
  3. Go to Configure -> Backup Sets. If you remove your sets from the list (using "Forget..."), then add them back in (using "More..."), they should stay in the order in which you add them. The catch: you'll also need to add them back into your scripts (since the scripts will lose their references at the point when you ask the program to "Forget" the sets). Alternatively, I was able to drag and drop multiple catalogs into the list (from the Windows Explorer) and they went in alphabetically, which is quicker than doing them one-by-one using the "More..." button. This might work for you too. Hope this helps! I agree that they should be alphabetical, particularly when there's no way for the user to directly sort/re-order them.
  4. This freeware tool would be worth trying: WakeupOnStandBy I haven't used it recently, but never had any problems in the past when using it on my home WinXP-based computer.
  5. What have you selected as your backup 'Source'? The whole computer? If so, try just selecting the drives you want to backup (i.e. all of them except for the destination drive) instead. Let us know if you need a more detailed description of how to do this.
  6. Do you use Retrospect's "Open File Backup" feature? That involves VSS even if you aren't using Shadow Copy.
  7. In fairness, Robin made that post over six weeks ago... Did the sales staff disclose any more information about it (e.g. what improvements it will contain)?
  8. As far as I know, you can't pick a specific tape to verify, but you can do the following: (1) Remove any tapes that you don't want to verify. (2) Click "Verify Media" then choose the appropriate backup set. (3) When prompted for tape 1, click "Choices", then click "OK" to mark the tape as 'Missing'. Do this for each tape you don't want to verify, then insert the one you do want to (or, if it is already inserted, hopefully Retrospect will find it immediately). If there are any tapes after that, mark them as missing via Choices->OK, as before. (4) When the verify operation is over, go to Configure -> Backup Sets -> (select the backup set) -> Properties -> Media, then click "Set Found" for all the tapes that you had set to missing (except for any that actually are missing ). While cumbersome, this has always worked for me with a single tape or disc drive, and I assume it would work with an autoloader as well. Before starting, you may also wish to temporarily disable any scheduled scripts that use this backup set, then re-enable them AFTER the tapes have all been set back to found. (So that they don't start under the mistaken idea that tapes are missing, and hence behave incorrectly.)
  9. Well spotted. I found it on the Retrospect Facebook page. Thanks for the info.
  10. Great to hear, especially given the simplicity of that solution compared to the others being considered. Enjoy!
  11. By the way, is the Windows installation on your Mac bootable via Boot Camp? Or only as a Parallels virtual machine? Booting the Mac into Windows directly (rather than virtually) might give Retrospect a better chance of 'seeing' the drive on that system.
  12. Yeah, a backup and re-installation of Windows seems like the logical next step, albeit a pretty big one to have to take. Maybe a 'repair' installation would help, as a potentially less time-intensive alternative to a full re-installation (unless you already repaired after changing the motherboard). But there's no guarantee that will work either. In any case, backing up the current system first (as you have suggested) is a sensible idea. I wonder if the presence of both v6.5 and v7.6 could be causing some sort of conflict? There are USB DVD drives listed as being compatible, but unfortunately the search function of the Hardware database is broken, making them hard to find. I complained about this last week; no response so far (although admittedly, I have only complained on this forum, and not to Roxio Support directly): http://forums.support.roxio.com/topic/77047-device-support-database/ Anyway, I have no idea whether such a drive would help. Well, that's about all I can think of. I hope you get it working! If you do, it would be great to hear what did the trick, if you have the time/inclination.
  13. No problem. Glad to hear you've made some progress by finding the v6.5 install. I did a quick search of the Retrospect hardware database for "106", and found two entries: Pioneer DVR-106 Pioneer DVR-106 (Apple version) (not qualified under Windows) Maybe the drive you bought was the Apple version? Not sure what the difference is, but if it's just firmware, you might be able to flash it to a non-Apple version. Also, did you check the "Environment" tab when you had the new DVD drive installed? Or only with the DVR-106? Maybe the new drive can be auto-configured from the Environment tab.
  14. The next thing I would try would be to start Retrospect with a new set of preferences. Here is the process: (1) Write down your Retrospect license code (found in Configure -> Licenses), then exit Retrospect. (2) Find the Retrospect settings folder. On my computers, it is a folder called "Retrospect" in one of the following locations: - Windows XP: C:\Documents and Settings\All Users\Application Data\ - Windows 7: C:\ProgramData\ - (I don't know about Vista, but I assume it would be the same as Win7) (3) Move this folder to somewhere else, e.g. your Desktop. (4) Start Retrospect, entering your license code when prompted. (5) Try looking in "Storage Devices" again (including the Environment tab), and see if the drive is now visible. If the drive is now visible, you'll unfortunately need to re-configure your Volumes, Scripts, etc. and re-add your Backup Sets, as these settings were all defined in the Retrospect folder we moved. But at least you'll (hopefully) be able to use and access the drive. (Note: There may be a better alternative, involving moving only a specific preference file so that you don't have to re-do everything, but I'm not familiar enough with the inner workings of the program to know which file(s) that would be. You could wait and see if someone more experienced chimes in with a suggestion, if you'd rather not go through the process of re-configuring everything.) If the drive is still not visible, you have the option of restoring your previous settings by shutting down Retrospect, then copying the original "Retrospect" folder back to its previous location (over-writing the new one that will have been created). Or, you could try un-installing and re-installing Retrospect, to see if the drive will show up then. If you do this, I would suggest leaving the backed-up "Retrospect" settings folder on your Desktop, then copying your folder of catalog files to the Desktop as well (usually a folder called "Retrospect Catalog Files" in my Documents), before proceeding to uninstall. If this still doesn't work, you could try installing a trial version of Retrospect 7.7. I hope one of the above suggestions works! Good luck.
  15. (Note: I am not familiar with v7.6 specifically, but will try to help based on my experience with v7.7.) Have you tried clicking the "Environment" tab in "Storage Devices"? Does either drive show up then? If so, try selecting the device, then clicking the "Configure Optical Drive" button above the list. You'll need a blank disc of whatever media you intend to use (e.g. DVD+R) to run the configuration process. As far as I know, you'll need one of each type if you intend to use multiple types (e.g. DVD+R and DVD-R and CD-R). This process isn't supposed to be necessary for qualified drives, but from memory, some users have had to do it to get theirs working. If the drive doesn't show up in "Environment", then there may be a deeper problem. Is it showing up and working fine in other software (and the Windows Explorer)? Did your PC upgrade involve re-installing Windows and/or Retrospect?
  16. Sorry to hear. It might help to schedule a regular backup of the "Retrospect" location (identified above by Lennart) and the location of your catalog files (usually called "Retrospect Catalog Files") to a backup set on a different disk. That will make it easier to set things back up should this ever occur again.
  17. It turns out that the Retrospect settings are actually stored in C:\ProgramData\Retrospect, which *has* been getting backed up. "C:\Users\...\AppData" is just a 'junction' to \ProgramData, as outlined here: http://www.svrops.com/svrops/articles/jpoints.htm So, it would appear that my unfamiliarity with Vista/Win7 is to blame in this particular instance, not Retrospect. Regarding the UAC issue, here is an article describing a possible workaround: http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/6822b712-8fc3-4253-8856-25e99f144262 However, when I tried this approach, it made Retrospect significantly slower to start (and close), despite not having to deal with the UAC prompt. Anyone know why?
  18. This is the answer I got, in case anyone else is interested: "There is no notification of the ASM period ending, it simply ends. You would need to monitor the status yourself. We appreciate the opportunity to assist you. The Roxio Support Team"
  19. Are you referring to the Retrospect Client password? If so, have you tried changing it on the client itself (i.e. in the Retrospect Client software)? Whether that works or not, I would definitely upgrade to the latest client software now that you're using the latest Retrospect version on the server. Retrospect 6.5 came out several years before Windows 2008.
  20. The "Open File Backup" feature does utilise VSS, so I'd guess you're correct about how/why the files are generated. These large "System Volume Information" files never appear in backups of my Windows XP machine, but do on my Windows 7 machines. Perhaps this is due to differences between the two Windows versions in terms of how Shadow Copy works, as outlined here: http://en.wikipedia.org/wiki/Shadow_Copy#Windows_XP_and_Windows_Server_2003 Not sure about whether it's important or useful to keep these files backed up, but I'll post back here if I find out anything of interest.
  21. Which version number(s) of Retrospect are you using?
  22. When defining the Rule, do you have the scope setting (above your defined conditions) set to "Any" or "All"? Are you putting both conditions in the "Include" panel? Or one in the "Include" and one in the "Exclude"? (Note: I am a user of the current Windows version and pre-v8 Mac versions only, so not familiar with v8 yet, but will try to help based on my understanding of other versions.)
  23. Which type of Retrospect "Backup Set" are you trying to open? A "File" backup set? What is the filename of the file you are trying to open?
  24. Could you please elaborate on this? That's very concerning. One other problem I noticed on the Win7 box I referred to above is that certain folders simply aren't visible when picking a "Subvolume"... including the "Retrospect" settings folder in AppData. I need to run some tests to see whether such folders can be backed up by selecting the parent folder (or entire disk).
  25. Thanks. Have now sent them an e-mail.
×
×
  • Create New...