Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


mbennett last won the day on March 27 2017

mbennett had the most liked content!

Community Reputation

8 Neutral

About mbennett

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Fair Grove MO

Recent Profile Visitors

307 profile views
  1. What David Hertzberg said. At the suggestion of Retrospect support, I now schedule multiple jobs in multiple scripts one minute apart. You can easily run dozens at a time, and the maximum number is tunable in Preferences. You can't run two jobs at the same time from the same source. You can run multiple scripts to the same destination, but for the sake of clarity and organization you will want to use unique destinations. I believe (but haven't tested this) that you could schedule two scripts to run with the same source, one minute apart. The second one will wait until the first one is complete. Try this and let us know. If you have a script and want to run it immediately, highlight it in Manage Scripts then click the third icon from the left on the toolbar, a little scripty looking sheet of paper with a lightning bolt next to it.
  2. mbennett

    How to skip Dashboard, start directly

    I think this is a good plan, but if you have a Proactive backup setup the program always appears to be running, even if nothing is happening. After the Proactive backup finishes, it will assume that it's idle for 24 hours, or until another job starts. The first window on the Dashboard always tells you if a Proactive or any other backup is actually in operation, so you can ignore the warning about starting the program most of the time. Agree that the Dashboard is slow, and launching it before you need it is the best plan if you're impatient. I'm hoping the web interface administrative tool that's coming sometime or other will make the executable program obsolete in the near future.
  3. An easy way to evaluate this is to get on the Retrospect website and run the configurator. There's no legitimate way I know of to share a single license across multiple installations of Windows. But the VM issue throws a slight wrinkle in things, and it's been a while since I looked at the price list for that. They might offer an option that would do what you want.
  4. mbennett

    Error -1103 after Windows 10 April Update

    Lucky_Phil, According to Microsoft you can't uninstall One Drive in Windows 10, but you can turn it off, disable and hide it. I'm assuming that you're not using W10, but other people might be confused by your advice. FYI, https://support.office.com/en-us/article/turn-off-disable-or-uninstall-onedrive-f32a17ce-3336-40fe-9c38-6efb09f944b0?ui=en-US&rs=en-US&ad=US If that link doesn't work, Google the subject.
  5. mbennett

    Error -1103 after Windows 10 April Update

    Just to throw out an idea after catching up with this thread, you might also want to investigate the settings in Control Panel | Sync Center in relation to One Drive, as well as anything else. Sync Center might have a bearing on this. I saw a bulletin regarding a completely unrelated application yesterday that encountered errors caused by the Sync Center. Then I read another article today discussing how One Drive syncs files and folders to the MS cloud. Now this thread to bring it full circle. I'm going to continue to watch this thread, and want to say that I really appreciate the extremely professional community discussions on this Forum. Bravo.
  6. mbennett

    Error -1103 after Windows 10 April Update

    hevanw, Sorry my suggestion didn't work out, and apologies to Scillonian for the error in the name. Please be sure to share the solution if/when you find it. This error was the bane of my existence for several weeks and I'm really unhappy to see that it might pop up and bite me again.
  7. mbennett

    Error -1103 after Windows 10 April Update

    I fought this error, sometimes frequently and sometimes sporadically, on several systems for quite some time. Filed a support case which came back with several suggestions. Of course I tried them all in what I thought was most-to-least likely to succeed. And the least likely solution, to me at first, was the winner. The solution that works every time and totally stops this error is to move the catalogs out from under the My Documents directory. I could lecture you on the stupid attempt to "virtualize" user files which Microsoft started trying to accomplish with Vista, but I'm convinced that's what creates this problem. Of course it's pointless and unnecessary, and Microsoft keeps bungling around with it. You can search this forum for instructions from a user named Scillian (I recall) to do this, but these are instructions of his I modified and have in my own KB. The catalog files can be moved to another drive or directory. I use C:\Catalogs With Windows Explorer, or your file manger of choice, copy the catalog file to its new location. In the Backup Sets dialog select the Backup Set whose catalog you want to move and click Forget.... Back in Retrospect click More... in the Backup Sets dialog then Open...in the following dialog. Navigate to the new location of the catalog file, select the file then click Open. Then you'll need to go to Manage Scripts and update all sources and/or destinations that are not defined because when you forget/move the catalogs the backup set will be deleted from scripts wherever they're found. This part can be time-consuming and error prone, and it will test your memory, so keep checking the logs for errors until you find them all. Good luck.
  8. mbennett

    New Windows user wants advice

    Retrospect 15 for Windows and Mac was released today. Download it if you enjoy being on the bleeding edge of technology. Last I heard the browser based console is to be released in May~ 2018. I wouldn't bet heavily on that, but that's the marketing projection. We'll see.
  9. Here's the original question: No there doesn't seem to be a way to do that. It isn't a problem with Retrospect, it's a problem with the way Windows services work. When you stop a service, the application that service is running also stops. But as my final word on this thread, I suggest you install 12.6.1 and test the interaction between the Dashboard and program yourself. If it doesn't do what you expect, then communicate with support and present the issue to them. Let us know what happens. If you were comfortable and happy with using the Mac as a Retrospect server and it did what you want to do, why not go back to that? The fundamental operation of the Mac OS is based on Unix, and is definitely different and probably superior to Windows. Expecting them to work in an identical manner, or even in an exactly analogous manner is probably a waste of time. Good Luck
  10. I did get time to install the 12.6.1 version of Retrospect on Monday night, and have observed a couple of things. But to the point of this thread, this version does allow you to launch the Retrospect program without seeming to break anything. When you start the Dashboard, you can click the "Launch Retrospect" link if the program doesn't start at that time. As DavidHertzberg notes, if you're within the look-forward time frame the program seems to launch automatically and you'll barely see the Dashboard screen. If you're not within that time frame, clicking the link will show the message "Waiting for Retrospect to exit" as the services stop and the program launches. To me, this behavior is perfect and resolves the real issue. Blanket recommendation is that if you've paid the ASM fees, you should upgrade to 12.6.1 ASAP.
  11. I remember reading that at the time you wrote it. I don't know if the timeline provided by Ian Dennis in sales is accurate, but I expect it is relatively so. He specifically says "Preview coming" so perhaps the web UI is still going to be in beta, may still be an optional install, may be any number of things. Maybe it will just be a Youtube video showing where they're going and we won't see a live product until 2019. There are major enhancements to both Physical and Virtual Retrospect, but that's for them to announce. I also wouldn't have any reason to believe Jeff was intentionally misleading anybody, but with software development the deadlines and project times change almost daily. I'm still running 12.5 and haven't installed 12.6 which was framed as more of a bug fix. They actually released it a few days after I upgraded from 12 to 12.5 (isn't that always the way?) When I start the Dashboard and get the UAC prompt, then click Launch Retrospect it does briefly display a message at the top of the Dashboard screen that says something along the lines of "Retrospect is exiting", which I take to mean the services are stopping. The following quote is is in the release notes for 12.6, so presumably something is different. I'll try to install 12.6 on my system in the next few days. And last, because I'm really tired and this has been a long day, you seem to be concerned about my name, which is Mark Bennett. At some point when signing up for this forum it asked me to assign a handle for myself, something I don't like to choose at any time. So I picked ProFromGrover which is a callback to the book M*A*S*H* by Richard Hooker. My mbennett login is the first part of my email address. I can't explain why the forum software mixes this up from one time to the next, but it's not really that important to me. I just know it's not me that's causing it to shift from one to the other.
  12. I'm seeing a lot of errors showing "can't read error -1017 insufficient permissions" in the log file you attached. First thing is to reboot the system that's being backed up and run chkdsk /f on that drive. That might fix the problem. The insufficient permissions error probably refers to the directory where the catalog files are located, so you should also try rebuilding all of the catalog files that are concerned in the jobs that aren't working. Also, look up that -1017 error in the knowledgebase on the Retrospect website and see what it says. I didn't do that. It's always possible that the RDX drive is worn out or a cable is bad, but they're pretty reliable. I use one every day. It's also possible the RDX cartridge itself is bad. Do you have any grooming jobs running on these sets?
  13. deredk500, I haven't been following this thread until just now, but I logged in to comment about something that is pertinent. First, as a practical matter in a Windows environment the icon on the taskbar is a myth and hasn't ever worked in my experience. Looking at page 22 of the User's Guide pretty much reveals that feature as an artifact of Windows XP and previous Windows versions. You can go to Preferences | Execution | Startup and set the flag to show the icon in the taskbar, but it will never actually appear. The UAC features introduced with Windows Vista killed that ability. Second, as a practical matter you can't do what you're asking. When the startup preferences are checked to enable the Retrospect services, those services own the program. You can launch the Dashboard and see if anything is running. If no job is running, then clicking the "Launch Retrospect" link in the top right corner of the window (label was renamed for version 12 to make it more accurate) will stop the services and open Retrospect proper. If you take that action when a job is running, killing the services will kill the job. If no jobs are running the program will launch harmlessly and all jobs will run as scheduled even though the services are stopped. If you launch the program while a job is running it will kill the job because launching it will kill the services. If you exit Retrospect while a job is running it will kill the job, because the services will be relaunched when you exit. To summarize this, don't start the Retrospect program while a job is running, and don't exit while a job is running. The Dashboard was envisioned, I believe, as a way to monitor the operation of the program while allowing it to continue running. You can't modify anything but you can see what's happening up to a point. Perhaps you could launch the program from an RDP session and set the session to lock after several minutes of inactivity and require a password to reopen the desktop. Not a great solution but it's pretty simple if it's possible. I don't use RDP a lot and I haven't attempted this. I've recently revised my own policy on using the E-Mail alerts which may help you to not feel that you need to be in the program watching everything. At one time I had every system to send an email every time Retrospect twitched it's nose, and it drove me a little crazy. In Preferences | Notification | E-Mail I now only check "Use e-mail for reporting" and "Send e-mail for failure and media requests". For each Retrospect 'server' that is running normally I get two emails every night, one when the Launcher starts and another when it stops. If no other email comes from that system I know the jobs have run successfully. Retrospect is such a stable program this happens most nights. If I get additional email from a system then I know I have a problem and I can focus on it. Real problems don't get lost in the weeds of meaningless emails. Last, I'm a dealer and I got an email from the sales department yesterday. As I hypothesized last year with DavidHertzberg they've announced that the next release of Retrospect is coming in a couple of months, and the new web-based user interface (which I predicted and was hoping for) will be released this summer. This might also be the fix you're looking for. I believe it will be, so hang in there. There is a long Youtube video about administering the Virtual Retrospect product and I think that is approximately what you can expect to see with the new interface. This simply confirms their direction. I hope this helps you. Mark
  14. mbennett

    Cannot recatalog backups

    Second the motion. Starting another thread on the same issue didn't get you any meaningful results either. I've never seen this error and your situation is too complex for people on the forum to debug. Get on the horn with support. Good luck.
  15. You can usually fix this by running chkdsk on your system. Doesn't always work, but often enough to make it a good first step.