Jump to content

JamesOakley

Members
  • Content count

    65
  • Joined

  • Last visited

Everything posted by JamesOakley

  1. I was glad to see the release of 7.7 as a "Windows 7 compatible" version. I was only encountering one problem with 7.6 and Windows 7 (and, for that matter, Windows Vista). You can create backup jobs, set them to run on schedule, close Retrospect, and nothing will happen. Then, as soon as you manually start Retrospect, any scheduled jobs that had not been running when they should all start to run. The suggestion on the forums has been that this is down to the User Account Control (UAC) feature in Windows Vista and later. Needless to say, I run Windows logged in as a non-administrative user most of the time. Other than that one problem, 7.6 was not giving me any problems in Windows 7. So I tried Retrospect Pro 7.7 in the hope that the problem I was having was fixed. Sadly, I ran the software, entered a trial license key (as it's not a free upgrade), let any waiting scheduled jobs run through, then closed the application. The hours passed, various scheduled backup times went by, and nothing had run. So I opened Retrospect from the start menu, and they all began to run. Unless I'm doing something amiss, the one compatibility problem I had with 7.6 and Windows 7 is still there in 7.7 and Windows 7. I have left my UAC settings on the default, as that give me the balance I want between the security of UAC and minimising interference to the Windows GUI. Can anyone help?
  2. JamesOakley

    7.7 does not fix failure to launch on schedule

    The user account you have used to run everything under: Does it have full administrative rights?
  3. JamesOakley

    7.7 does not fix failure to launch on schedule

    OK. Try Pete's tip then. (It should work with 7.6 as much as with 7.7). I've not tried it, but I guess it will work. Two steps: 1. Set Retrospect to run as the currently logged in user. 2. Change the Retrospect Launcher service so that it doesn't run as the "Service" account, but runs as the named account you have setup to have NAS access. (Obviously, restart the service) My guess is that the Retrospect Launcher service will then start Retrospect, but that it will do so as the "Currently Logged in User". In this case, that would be the account with the NAS permissions. Please let us all know whether it works. If so, we have a complete work-around for this long-standing problem
  4. JamesOakley

    7.7 does not fix failure to launch on schedule

    He hits the nail on the head! The answer is, indeed, to use "Always run as the logged-in user". That way, UAC never get invoked. My fear was that this would mean Retrospect would run as my own user account when I am logged in, which is not an administrative one. In fact, this is not the case. The small label next to this option in Security Preferences is more helpful: "Retrospect will run in the local system account when automatically launched. Unattended backups of databases and network resources may not work." This is correct. Retrospect fires as the "logged-in user". In the case when Retrospect is launched from the Retrospect Launcher Service, this is the Local System Account. So it runs, UAC does not get in the way, and it has full administrative privileges. As I said, nail on head.] There are only two draw-backs. 1. This method of running still gives no desktop interraction. It is not possible to see how far through a backup it is, how much space is required for the blank media it is asking for, and so on. 2. If I had to backup Databases / Network Shares (without using a Client), I would have problems. This drawback won't apply to many Professional users. In all likelihood, this is not a fix for 7.7, but a workaround that I wish had discovered for 7.6. I may, still, be spared from having to pay to get Windows 7 compatibility. Thanks Pete!
  5. JamesOakley

    7.7 does not fix failure to launch on schedule

    Pete, Did that mean that you also had to be logged in as a user with full administrative rights for Retrospect to run?
  6. JamesOakley

    7.7 does not fix failure to launch on schedule

    Thanks for suggesting that test. Sad to say, disabling UAC meant that it launched "OK". (In quotation marks, because it launched as an administrative account in the background with no UI, which means I can't see if I need new media, or if some other problem has occured. In XP, Retrospect would launch as an administrator but visible to the desktop; click on the application, and you need to enter the relevant Admin password before you can interact with it). The backup ran on schedule; Retrospect exited; I got sent two e-mails - one that confirmed the backup had run, and the other to tell me that Retrospect had quit. I am aware that this has been a problem with 7.6. As I said in my original post, the fact that UAC stops backups launching on schedule was the only incompatibility I had between Windows 7 and Retrospect 7.6. It is a real shame that the new version has finally come out, but that it has the same incompatibility that I had with 7.6. UAC is a necessity not an option for me. :confused2: Now I've finished my test, I'll turn UAC back on...
  7. JamesOakley

    7.7 does not fix failure to launch on schedule

    Well: We'll have to wait until others have had the chance to try this out, and see what their experience is.
  8. JamesOakley

    7.7 does not fix failure to launch on schedule

    Would the fact that I am running as a Standard User account (non-administrative) be relevant? I notice that, in Windows XP, I used to be able to start Retrospect as a local user, or use Run-as to start it as an administrator. The "local user" option was generally a bad idea, as backups would then run without sufficient permission, but it could be done. In Vista and Win7, if I am running as a non-admin, and I go to launch Retrospect from the Start Menu, Windows thinks of Retrospect as a program that must be run with full admin privileges. Quite right too. So what I get is a UAC dialog asking me for an admin password. Running on schedule, I won't be here to enter that password. I'm guessing that is why it fails silently, but I'm only guessing. If others have auto-launch running on non-admin accounts, I would love to hear that because it would rule that theory out. Any ideas as to what other kinds of software might interfere with the auto-launch procedure? In case it's relevant, I'm running Win 7 home premium, although I used the Ultimate edition at RC stage, and it had the same problem with Retrospect 7.6 (By the way, there's nothing in the Windows event logs at the times when the retrorun.exe should have launched Retrospect)
  9. JamesOakley

    retrospect 7 window vista

    I would advise you to download a trial copy of 7.6 to see if it solves your problems. A lot of people have found that there are issues with Retrospect Professional 7.6 and Vista (and, for that matter, Windows 7), whereby the new User Account Control feature stops the scheduler from launching backups. It seems that not everyone has this difficulty, but given the frequency of posts in this forum reporting problems with Vista, I would try before buying.
  10. JamesOakley

    Retrospect Launcher not launching on Win7

    Bill: What settings do you have for UAC on your Win 7 32-bit box to get the scheduling to work like this?
  11. JamesOakley

    Retrospect Launcher not launching on Win7

    Hopefully, then, this thread will report the solution to this problem once Win7 is released on 22 October. From that date on, Windows 7 is the version of Windows that will ship with most new computers, so I'm really hoping that this problem will find a quick solution. For what it's worth, I think the problem relates to the UAC-caused issue that people have been experiencing with Vista and Retrospect. I'm not sure whether there's a way of turning UAC off on Win 7 that solves the problem. There may be, but UAC is much less obtrusive under Windows 7 (compared to Vista) so I want to have it enabled. We need a solution that allows a PC running Windows 7 to spend most of its time logged in as a limited account, with UAC enabled, and scheduled backups still run and can be monitored from the desktop. Windows XP, whilst still supported by MSFT, is soon to be two versions old. Please, EMC, can we have Retrospect 7 such that we can take advantage of the security features of Vista and Win7 and still use Retrospect with the useability we enjoyed under XP?
  12. I know (before anyone points it out) that Retrospect does not yet officially support Windows 7. But, I wanted to see if I would be able to run all the software and drivers I currently use under Windows 7, so I've installed the RC. The bad news is: This problem people have reported with Vista also seems to occur (for me at least) in Win7. That's to say: Scheduled jobs don't start unless you manually start up Retrospect.exe. The launcher is installed, running under the system account, and allowed to interact with the desktop. But nothing. The good news is: It seems relatively easy to work-around. Use the new Task Scheduler to create a task that launches Retrospect.exe; set its login credentials to be that of an administrative user, and tick the box "Run with highest privileges". Set the task to trigger (say) every half an hour, and bingo - the scheduled scripts run. One thing I've noticed is that Retrospect.exe does not close down after all scheduled scripts have completed. This is expected behaviour: If you start Retrospect manually from within Windows, it is set to "Stay in Retrospect" not to "Exit" on completion, so that is all that is happening. That's a shame, but not a disaster. Theoretically this means that one could set the task to trigger only on logon or on system startup, and the Retrospect application would stay running in the background. I've kept it to trigger every 30 minutes just to be safe - in case the application is shut down for some other reason. I hope this helps someone, and I hope there is a new release from the good people behind Retrospect that fixes this properly some time soon.
  13. JamesOakley

    Grooming multiple-disk disk backup sets

    I thought I did, but it was a while ago so maybe I didn't. I certainly didn't do it more than once - the drive took about 20 secs to load or unload a disk. From memory, it asked for disk 1, then for disk 2, ..., disk 9, then went through that whole sequence 2 more times. Only if I told it that I had lost one of the disks would it mark it missing. I think that's what I did. But Pen drives are much easier, so they're both plugged in happily.
  14. I have a problem with grooming disk backup sets that contain more than one disk. Specifically, using Retrospect Professional 7.5 I have a disk backup set that has two members, both USB pen drives. I started with the empty backup set. In time, the first drive filled, and I used the second. Then that filled, and auto-grooming kicked in, leaving a great deal of space on both disks. I was back to storing on the first disk again, but when that filled up... instead of it asking for the second disk, it auto-groomed again. There is space on the second disk (quite a lot), but I never get to use it, because whenever the first disk fills up it grooms. Any advice?
  15. JamesOakley

    Grooming multiple-disk disk backup sets

    Thanks - that'll answer my question! I don't recall ever reading that detail in the documentation, but I'll make sure both are plugged in from now on. Interestingly, when I first bought Retrospect, I was using a ZIP Drive with 250MB disks. I had a 9-disk backup set, and switched the disks one at a time. Grooming took forever! But I had no idea that it wouldn't be possible to groom correctly with this arrangement.
×